Failure Mode and Effects Analysis (FMEA)
Systematic method for identifying potential failure modes, their causes, and effects to prioritize risk mitigation efforts.
Failure Mode and Effects Analysis (FMEA)
What is FMEA?
FMEA is a systematic, proactive method for evaluating a process to identify where and how it might fail and to assess the relative impact of different failures.
Types of FMEA
Design FMEA (DFMEA)
Focuses on potential design weaknesses
- Component failures
- System interactions
- Design specifications
Process FMEA (PFMEA)
Focuses on process failures
- Manufacturing/operational processes
- Service delivery
- Administrative procedures
System FMEA
Focuses on system-level failures
- System functions
- Subsystem interactions
- Interface failures
FMEA Process
Step 1: Identify Functions
List all functions of the process/product
Step 2: Identify Potential Failure Modes
For each function, how could it fail?
- Complete failure
- Partial failure
- Intermittent failure
- Degraded function
Step 3: Determine Effects
What happens if each failure occurs?
- Local effects
- System effects
- End user effects
Step 4: Identify Causes
What could cause each failure mode?
- Root cause analysis
- Multiple causes possible
Step 5: Assess Current Controls
What controls exist to prevent/detect?
- Prevention controls
- Detection controls
- Current effectiveness
Step 6: Calculate Risk Priority Number (RPN)
RPN = Severity × Occurrence × Detection
| Rating | Severity | Occurrence | Detection | |--------|----------|------------|-----------| | 1 | None | Very rare | Almost certain | | 5 | Moderate | Occasional | Moderate | | 10 | Hazardous | Very high | No detection |
Step 7: Prioritize and Act
- Focus on highest RPNs
- Develop action plans
- Assign responsibilities
- Track to completion
Step 8: Recalculate RPN
After implementing actions, reassess to confirm improvement
FMEA Worksheet Columns
- Item/Function
- Potential Failure Mode
- Potential Effect(s)
- Severity (S)
- Potential Cause(s)
- Occurrence (O)
- Current Controls
- Detection (D)
- RPN (S×O×D)
- Recommended Actions
- Responsibility/Target Date
- Actions Taken
- Revised RPN
Best Practices
- Cross-functional team
- Start early in design/planning
- Use lessons learned from past failures
- Update regularly
- Link to continuous improvement