Helicopter Machine Configuration Data Set (MCDS) Management. Process…
Helicopter Machine Configuration Data Set (MCDS) Management. Process Improvement Project
Issues / Weaknesses
Traceability of changes relies on manual intervention
Not in a controlled configuration system such as RCS_Pro or Genesis
There is no WI for how to analyse collected flight data
Too many parts of the process dependent on manual interventions
There is no defined high level process flow
The Rotortuner-5JS+ utilises the "Genesis" control system software. This software automatically provides the required QA procedures to enable strict management of the MCDS for this equipment type. Therefore, parts of this WI do not apply to the production and testing of MCDS for RT-5JS+ (see Appendix A for relevance). However, Genesis is not used for other Rotortuner equipment such as the Rotortuner-2000, RT-Balancer or Rotortuner -6. Consequently, there is a need for a strict management control procedure when editing and subsequently releasing those MCDS.
For Rotortuner that use the RT-HHT or RT-Flitepad the requirement also includes the need for an Access Control File (ACF) system. The process for the management and control of ACF is contained in WI-1124.
Genesis in Vision
Vision version: 6+
Genesis is only available now for internal use, not formally a released version
Genesis only works for RT-5 series. It checks inputs
QA configuration management tool
No such tool for RT-2000 or RT-6. This process is less controlled with free editing.
WI 1132 Data Card Management and Control.
Main work instruction. When a requirement to create an MCDS for a particular aircraft or machine has been identified it is first necessary to determine if a released MCDS already exists for that aircraft or machine type. If there isn’t then it is necessary to either create a new MCDS or amend one that is close to the aircraft or machine type of interest.
WI 1031 Provides information on how to manually edit the MCDS for RT-2000 and RT-6. Esentially free edit version of what Genesis provides for the RT-5 series
WI 1132 outlines MCDS save location and high level control of file set
WI 1089 outlines how to prepare for flight trial
BI 086 Customer Data Proforma and then WI 1147 describes the way how to gather the data and then WI 1089 outlines the flight trial process
Location of MCDS files on a controlled access network drive e.g. U drive
Legacy data is kept with current data in an archive area as it's provenance cannot be categorically verified
Sensitivity analyser software
is in place however it needs improvement
Personality editing *
validation* tool needs to be updated to work with RT-6 setups.
WI 1143 Aircraft sensitivity analysis written for GmbH
WI 1131 is designed to define the part numbering conventions for the MCDS files used to create Helitune Data Cards
WI 1030 is designed to define the processes involved when utilising the Genesis system for Data and Application Programme file sets utilised in the Rotortuner
Each MCDS produced is archived under the Customer Database folder on the FlightData U: drive. Access to the folder is strictly controlled ensuring only authorised personnel can create or edit the MCDS. Logs for the control of MCDS are saved under the “Logs for Customer Database” folder on the same drive.
Confirm categorically that we have the correct MCDS about variant of the aircraft
Configuration management encompasses the administrative activities concerned with the creation, maintenance, controlled change and quality control of the MCDS files.
Automated version control process with a configuration management tool such as GIT and / or Sharepoint
Updated sensitivity analysing software to support analysis process and reduce misinterpretation of the data
MCDS file editor with built in verification to avoid human errors
Traceability of requirements. Key requirements are traceable back to a template / document
Editing, checking configuration management in one package
Accessible from anywhere in the world
Simple summary of the history of the MCDS for a specific helicopter type / variant
Successful Verification of MCDS
Successful Validation of MCDS
Productionisation of ACF creation
Aircraft Maintenance Manual Compliance is checked before proceeding
Regression testing for MCDS including solutions
Trial report and not visit report
Genesis in RT Vision? Is it too old and require too much effort to update? NO
RCS_Pro. RCS_Pro will be phased out in the near future by Sharepoint. NO
Sharepoint? Could this be implemented? Consult Steve Pollard
Another dedicated configuration management software? NO
Lineal to make recommendations? NO
In house developed software solution (MCDS editor)? For the checker function. To be decided later.
Technology and Customer Service Manager
QHSE Department, Internal Auditors, DNV GL
Sales / Commercial
Process Improvement. Yes
Wrongly implemented new feature?
Subject Matter Experts (Qualified Aerospace Engineering Certificate)
Update Mind Map and share with DG - BB
Consult S. Pollard about GIT? D Graham
PRR project. Project Manager: P. Morrish / B. Bagi
Level 0 project. If tools required then Level 1. Flight Support to specify inputs for checking tool.
Product Matter Experts (Bridge)
Competency to Lead a Flight Trial?
Competency to Lead a Demo on a green / amber / red aircraft
Competency to train customers how to use the RT-6 kit
Scenario #1: Military Customer / End User
Scenario #2: OEM
Scenario #3: Civil Helicopter End User / MRO (Maintenance and Repair Organisation EASA P 145)
MCDS File Management Process Improvement Project