REL103; Slide 1 Introduction to FMECA n What is a FMECA? –An Analysis technique which facilitates the identification of potential design problems by examining the effects of lower level failures on system operation. “Obviously, a major malfunction.” - Stephen A Nesbitt NASA Public Affairs Officer

REL103; Slide 2 Why is it Important? n Provides a basis for identifying root failure causes and developing effective corrective actions n Identifies reliability/safety critical components n Facilitates investigation of design alternatives at all stages of the design n Provides a foundation for other maintainability, safety, testability, and logistics analyses

REL103; Slide 3 Definitions n FMECA - Failure Mode, Effects, and Criticality Analysis. n FMEA - Failure Mode and Effects Analysis. n COMPENSATING PROVISIONS - Actions available or that can be taken to lessen or eliminate the effect of a failure on a system. n NEXT HIGHER EFFECT - The consequence a failure mode has upon the operation, function, or status at the next higher level of assembly. n END EFFECT - The consequence a failure mode has upon the operation, function, or status at the highest level of indenture.

REL103; Slide 4 How is it Done? What are the effects of part failures on the board? What are the effects of board failures on the box? What are the effects of box failures on the system? Note: This is a bottoms up example. Top down examples are possible.

REL103; Slide 5 Simple Example: Flashlight This flashlight is for use by special operations forces involved in close combat missions (especially hostage rescue) during low visibility conditions in urban areas. The light is to mounted coaxially with the individual's personal weapon to momentarily illuminate and positively identify targets before they are engaged. The exterior casing including the transparent light aperture are from an existing ruggidized design and can be considered immune to failure.

REL103; Slide 6 Simple Example: Flashlight (cont.) How can it fail? What is the effect? Note that Next Higher Effect = End Effect in this case. Part

REL103; Slide 7 Severity n SEVERITY classifies the degree of injury, property damage, system damage, and mission loss that could occur as the worst possible consequence of a failure. For a FMECA these are typically graded from I to IV in decreasing severity. n The standard severities defined in MIL-STD1682 may be used or equipment specific severities may be defined with customer concurrence (recommended).

REL103; Slide 8 Simple Example: Flashlight (cont.) n Severity –Severity ILight stuck in the “on” condition –Severity IILight will not turn on –Severity IIIDegraded operation –Severity IVNo effect

REL103; Slide 9 Simple Example: Flashlight (cont.)

REL103; Slide 10 Criticality n CRITICALITY is a measure of the frequency of occurrence of an effect. –May be based on qualitative judgement or –May be based on failure rate data

REL103; Slide 11 Simple Example: Flashlight (cont.)

REL103; Slide 12 Simple Example: Flashlight (cont.) Can circled items be designed out or mitigated? (There may be others that need to addressed also.)

REL103; Slide 13 Integrated FMECA n FMECAs are often used by other functions such as Maintainability, Safety, Testability, and Logistics. –Coordinate your effort with other functions up front –Integrate as many other tasks into the FMECA as possible and as make sense (Testability, Safety, Maintainability, etc.) l Integrating in this way can save considerable cost over doing the efforts separately and will usually produce a better product. l If possible, use the same analyst to accomplish these tasks for the same piece of hardware. This can be a huge cost saver.

REL103; Slide 14 FMECA Facts and Tips n FMECAs should begin as early as possible –This allows the analyst to affect the design before it is set in stone. –If you start early (as you should) expect to have to redo portions as the design is modified. n FMECAs take a lot of time to complete. n FMECAs require considerable knowledge of system operation necessitating extensive discussions with software/hardware Design Engineering and System Engineering. n Spend time developing groundrules with your customer up front.