Failure Mode and Effects Analysis (FMEA)
Failure Mode and Effects Analysis (FMEA) is a systematic, proactive method for identifying potential failures in a product, process, or system, evaluating their possible consequences, and prioritising actions to mitigate risk. Originating in the aerospace industry in the 1940s, FMEA has become a standard riskassessment tool across automotive, medical, manufacturing, software, and many other sectors.
Why Use FMEA?
- Improves reliability: By spotting weaknesses early, designers can incorporate corrective measures before a product reaches the market.
- Reduces cost: Preventing defects is far less expensive than repairing them after release.
- Enhances safety: Critical failures that could endanger users are identified and mitigated.
- Supports compliance: Many standards (e.g., ISO26262, IEC60812) require documented risk analysis.
Basic Concepts
| Term | Definition |
| Failure Mode | The way in which a component or process could fail (e.g., cracked housing, software timeout). |
| Effect | The direct outcome of the failure on the system or user (e.g., loss of pressure, incorrect display). |
| Cause | The underlying reason for the failure (design flaw, wear, human error, environmental stress). |
| Severity (S) | Rating (110) of how serious the effect is on safety, performance, or cost. |
| Occurrence (O) | Rating (110) of how likely the cause is to happen. |
| Detection (D) | Rating (110) of the ability of current controls to detect the failure before it reaches the customer. |
| Risk Priority Number (RPN) | RPN = S O D. The higher the RPN, the greater the priority for corrective action. |
Types of FMEA
- Design FMEA (DFMEA): Focuses on potential failures of a products design.
- Process FMEA (PFMEA): Analyzes manufacturing or service processes.
- System FMEA: Considers interactions among multiple subsystems.
- Software FMEA: Applies the same principles to code, algorithms, and user interfaces.
Typical FMEA Workflow
- Define scope and objectives: Decide which product, subsystem, or process will be examined and what the desired outcomes are.
- Assemble a multidisciplinary team: Include designers, engineers, quality specialists, production staff, and sometimes customers.
- Identify functions and requirements: List what each component or step must accomplish.
- List potential failure modes: Brainstorm how each function could fail.
- Determine effects and severity: For each failure mode, describe the local and systemlevel effects and assign a severity rating.
- Identify causes and occurrence: Find root causes (e.g., material defect, operator error) and rate their likelihood.
- Assess existing controls and detection: Evaluate current inspections, tests, or safeguards and rate detection capability.
- Calculate RPNs: Multiply S, O, and D. Sort the list from highest to lowest RPN.
- Develop and implement actions: Target highRPN items with design changes, process improvements, or additional controls.
- Reevaluate: After actions are taken, update the ratings and verify that RPNs have been reduced to acceptable levels.
- Document and maintain: Keep the FMEA worksheet current throughout the product lifecycle; update when design changes or new data become available.
Tips for an Effective FMEA
- Keep it focused: Limit the scope to manageable sections; very large matrices become unwieldy.
- Use clear, concise language: Ambiguities lead to inconsistent ratings.
- Apply historical data: Failure statistics from similar products improve occurrence estimates.
- Encourage open discussion: Team members should feel free to challenge each other's assumptions.
- Prioritise actions, not just numbers: A high severity with moderate occurrence may merit a different approach than a lowseverity, very frequent issue.
- Integrate with other tools: Link FMEA results to rootcause analysis, correctiveaction tracking, and reliability prediction models.
Common Pitfalls
- Assigning the same rating to all items out of habit, which obscures real risk.
- Skipping detection evaluation; without it, the RPN loses meaning.
- Treating FMEA as a onetime document rather than a living record.
- Neglecting to verify that corrective actions actually reduce risk.
Software Support
Many organisations use specialised FMEA software (e.g., ReliaSoft, IQTools, or opensource spreadsheets) to streamline data entry, automatically calculate RPNs, and generate reports. Features often include version control, risktrend charts, and export to compliance documentation.
Example of a Simple DFMEA Entry
| Item | Function | Failure Mode | Effect | Severity (S) | Cause | Occurrence (O) | Current Controls | Detection (D) | RPN |
| Vent Valve | Relieve excess pressure | Stuck closed | Pressure buildup rupture | 9 | Corrosion of valve seat | 3 | Visual inspection, corrosionresistant coating | 4 | 108 |
| Vent Valve | Relieve excess pressure | Leak at seal | Pressure loss underperformance | 5 | Improper assembly torque | 5 | Torque verification, seal test | 3 | 75 |
References & Further Reading
- IEC 60812 Analysis techniques for system reliability Guidance
- SAE J1739 Potential Failure Mode and Effects Analysis (PFMEA) Guide
- AIAG & VDA FMEA Handbook Collaborative industry standard
- Effective FMEA Ralph N. F. Hall, 2020 (book)
By integrating FMEA early in design and maintaining it throughout production, organisations can transform potential failures into opportunities for improvement, achieving higher quality, safety, and customer satisfaction.
We use cookies to enhance your browsing experience and analyze site traffic. By clicking 'Accept all cookies', you agree to the use of these cookies. You can manage your preferences or learn more in our [Privacy Policy/Cookie Policy.