malfunctions

21
Malfunctions They drive everything! Written and presented by: Jacqui Chapman

Upload: maille

Post on 22-Feb-2016

40 views

Category:

Documents


0 download

DESCRIPTION

Malfunctions. They drive everything! Written and presented by: Jacqui Chapman. Introduction. The number and complexity of malfunctions are the cornerstone to the depth of simulation required. The Question. Why is it different from operator training? - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Malfunctions

Malfunctions

They drive everything!

Written and presented by: Jacqui Chapman

Page 2: Malfunctions

Introduction

The number and complexity of malfunctions are the cornerstone to the depth of

simulation required.

29th April 2009 3WATS 2009

Page 3: Malfunctions

The Question

Why is it different from operator training?What is the function of maintainer training?

29th April 2009 WATS 2009 4

Page 4: Malfunctions

Operator vs. Maintainer Training

Cause and EffectWhere 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.

29th April 2009 WATS 2009 5

Page 5: Malfunctions

Training

Form, Fit, Feel, Fidelity and FunctionForm – shape of..Fit – well suitedFeel – ascertain by touchFidelity – precision in reproductionFunction – mode of activity by which a thing

fulfils its purposeMalfunction requirements will help drive

the final solution

29th April 2009 WATS 2009 6

Page 6: Malfunctions

Maintenance Tasks

Scheduled MaintenanceMalfunction Diagnosis

Malfunction Rectification

29th April 2009 WATS 2009 7

Page 7: Malfunctions

Level of Maintenance

1) Confirm that there is a malfunction and isolate

2) Interpretation of monitoring data3) Identify the component that has

malfunctioned

29th April 2009 WATS 2009 8

Page 8: Malfunctions

Malfunction Simulation1) Confirmation of Failure

29th April 2009 WATS 2009 9

Page 9: Malfunctions

Malfunction Simulation2) Interpretation of Health and Usage Monitoring System

29th April 2009 WATS 2009 10

Page 10: Malfunctions

Malfunction Simulation3) Use of test equipment, failure flow charts

29th April 2009 WATS 2009 11

Page 11: Malfunctions

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

29th April 2009 WATS 2009 12

Page 12: Malfunctions

29th April 2009 WATS 2009 13

Page 13: Malfunctions

Confirmation of Failure

29th April 2009 WATS 2009 14

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

IFENDELSE IF fault applied THEN

Pressure Indicators = 0 psi

Trigger the CWS

Flying Controls, Landing Gear & Brakes do not respond

END IF

Page 14: Malfunctions

Interpretation of HUMSIf HUMS connected and switched on then

HUMS unit = ON

ProceduralIf no fault applied then

If HUMS O/P = thenSystem responseHUMS displayElse if fault a then If HUMS O/P = thenSystem responseHUMS display …

Freeplay

• Switching off systems• Disconnecting connectors• Incorrect selection of

HUMS unit• Failures in other system

impacting original system

29th April 2009 WATS 2009 15

Page 15: Malfunctions

Use of Test Equipment

29th April 2009 WATS 2009 16

If STTE connected and switched on thenSTTE unit = ON

ProceduralIf no fault applied then

If STTE O/P = thenSystem responseSTTE display

Else if fault a then If STTE O/P =

thenSystem responseSTTE display …

Freeplay

• Switching off systems• Disconnecting connectors• Incorrect selection of

HUMS unit• Failures in other system

impacting original system

Page 16: Malfunctions

One Solution

Object Orientated Design

– All components emulated

Get propagation automatically

29th April 2009 WATS 2009 17

Page 17: Malfunctions

29th April 2009 WATS 2009 18

Page 18: Malfunctions

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.

29th April 2009 WATS 2009 19

Page 19: Malfunctions

29th April 2009 WATS 2009 20

Page 20: Malfunctions

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

29th April 2009 WATS 2009 22

Page 21: Malfunctions

Malfunctions

They drive [email protected]

www.pennantplc.co.uk

29th April 2009 WATS 2009 23