1. Malfunctions  They drive everything! Written and presented by: Jacqui Chapman

2.  Introduction  The Question  One Solution  Emulating Malfunctions  Data  Conclusion 29 th April 2009WATS 20092

3. Introduction The number and complexity of malfunctions are the cornerstone to the depth of simulation required. 29 th April 20093WATS 2009

4. The Question  Why is it different from operator training?  What is the function of maintainer training? 29 th April 2009WATS 20094

5. Operator vs. Maintainer Training Cause and Effect  Where the emphasis is on the effects of a malfunction and it is how an operator reacts to it that is all important  Where the cause of the malfunction is what a maintainer is trying to discover, using the effect as part of a fault diagnosis procedure. 29 th April 2009WATS 20095

6. Training Form, Fit, Feel, Fidelity and Function FForm – shape of.. FFit – well suited FFeel – ascertain by touch FFidelity – precision in reproduction FFunction – mode of activity by which a thing fulfils its purpose MMalfunction requirements will help drive the final solution 29 th April 2009WATS 20096

7. Maintenance Tasks  Scheduled Maintenance  Malfunction Diagnosis  Malfunction Rectification 29 th April 2009WATS 20097

8. Level of Maintenance 1)Confirm that there is a malfunction and isolate 2)Interpretation of monitoring data 3)Identify the component that has malfunctioned 29 th April 2009WATS 20098

9. Malfunction Simulation 1)Confirmation of Failure 29 th April 2009WATS 20099

10. Malfunction Simulation 2)Interpretation of Health and Usage Monitoring System 29 th April 2009WATS 200910

11. Malfunction Simulation 3)Use of test equipment, failure flow charts 29 th April 2009WATS 200911

12. Procedural vs. ‘Free Play’  Fault Propagation –Does the simulation need to display secondary effects?  Diagnosis and Rectification –Does the simulation need to react to deviation? No – procedural Yes – Free play 29 th April 2009WATS 200912

13. 29 th April 2009WATS 200913

14. Confirmation of Failure 29 th April 2009WATS 200914 IF Engine > x rpm AND Power > 24V dc THEN Pressure Indicators = 3000 psi No Trigger to CWS Flying Controls, Landing Gear & Brakes respond correctly IFEND IF Engine > x rpm AND Power > 24V dc AND no fault applied THEN Pressure Indicators = 3000 psi No Trigger to CWS Flying Controls, Landing Gear & Brakes respond correctly IFEND ELSE IF fault applied THEN Pressure Indicators = 0 psi Trigger the CWS Flying Controls, Landing Gear & Brakes do not respond END IF

15. Interpretation of HUMS If HUMS connected and switched on then HUMS unit = ON  Procedural If no fault applied then If HUMS O/P = then System response HUMS display Else if fault a then If HUMS O/P = then System response HUMS display …  Freeplay Switching off systems Disconnecting connectors Incorrect selection of HUMS unit Failures in other system impacting original system 29 th April 2009WATS 200915

16. Use of Test Equipment 29 th April 2009WATS 200916 If STTE connected and switched on then STTE unit = ON  Procedural If no fault applied then If STTE O/P = then System response STTE display Else if fault a then If STTE O/P = then System response STTE display …  Freeplay Switching off systems Disconnecting connectors Incorrect selection of HUMS unit Failures in other system impacting original system

17. One Solution  Object Orientated Design –All components emulated Get propagation automatically 29 th April 2009WATS 200917

18. 29 th April 2009WATS 200918

19. Simulate vs. Emulate  Simulate is to have the appearance, form, feel and function of…  Emulate is to attempt to equal functionality without necessarily providing form and feel. 29 th April 2009WATS 200919

20. 29 th April 2009WATS 200920

21. Data  Emulation/Simulation is only as good as the data that goes to build it –Develop from technical data –Use real equipment software Develop a good working relationship with the data provider 29 th April 2009WATS 200921

22. Conclusion  Understand the level of malfunction coverage required  Understand what the maintainer is being trained to do in reaction to a malfunction  Form, Fit, Feel, Fidelity and Function 29 th April 2009WATS 200922

23. Malfunctions  They drive everything  Jacqui.chapman@pennantplc.co.uk Jacqui.chapman@pennantplc.co.uk  www.pennantplc.co.uk www.pennantplc.co.uk 29 th April 2009WATS 200923