FMEA
Quick facts
| Category | Structured failure mode risk analysis |
|---|---|
| Used by | Manufacturing, medical devices, aerospace, automotive and other regulated industries |
| Also called | FMEA, DFMEA, PFMEA, RPN, AP |
| Related standards | ISO 9001, IATF 16949, AIAG-VDA FMEA Handbook, ISO 13485 |
| Related processes | Risk assessment, product design controls, control plans, CAPA |
| Semantic match | failure mode effects analysis, FMEA process, DFMEA PFMEA, risk priority number action priority |
What is FMEA?
FMEA is a proactive risk analysis method used to identify how a product design or manufacturing process could fail, understand the potential effects of each failure, and prioritize which risks need action first. Design FMEA, or DFMEA, focuses on potential failures built into a product's design. Process FMEA, or PFMEA, focuses on potential failures in how the product is made.
An FMEA team, typically cross-functional, identifies potential failure modes for each function or process step, then evaluates each failure mode's severity, its likelihood of occurrence, and how likely existing controls are to detect it before it reaches the customer.
Historically, these three factors were multiplied together into a Risk Priority Number, or RPN, to rank failure modes. The automotive industry's harmonized AIAG-VDA FMEA Handbook replaced this approach with an Action Priority, or AP, method, which uses severity, occurrence and detection ratings together in a lookup table to classify each failure mode as high, medium or low priority for action, addressing known inconsistencies in the older RPN approach.
Why is FMEA important?
FMEA allows organizations to identify and address failure risks before they occur, rather than discovering them through a nonconformance, complaint or field failure after the product is already in use.
Because FMEA is structured and cross-functional, it captures risks that individual departments might miss on their own, drawing on design, manufacturing, quality and sometimes supplier or field service perspectives in one analysis.
In regulated and safety-critical industries, a well-documented FMEA also provides evidence that potential failure modes, including those affecting safety or regulatory compliance, were considered and addressed during design or process planning rather than discovered later.
How does FMEA work?
A typical FMEA process includes:
- Scope and team. Define the product or process being analyzed and assemble a cross-functional team.
- Function and failure identification. Identify each function or process step and how it could fail.
- Effects analysis. Determine the potential effect of each failure mode on the customer or downstream process.
- Cause identification. Identify potential causes for each failure mode.
- Rating. Score severity, occurrence and detection, or apply the AIAG-VDA Action Priority method.
- Prioritization. Identify the highest-priority failure modes for action.
- Action planning. Define and assign actions to reduce risk for prioritized failure modes.
- Follow-up. Re-evaluate risk after actions are implemented and update the FMEA as a living document.
Risk Priority Number (RPN) vs. Action Priority (AP)
| Comparison | Risk Priority Number (RPN) | Action Priority (AP) |
|---|---|---|
| Calculation | Severity × Occurrence × Detection | Lookup table combining severity, occurrence and detection |
| Output | A numeric score, often 1 to 1000 | A High, Medium or Low action priority rating |
| Known limitation addressed | Different rating combinations can produce the same score | Prioritizes based on the relative importance of severity first |
| Current status | Still used in many industries and legacy FMEAs | Recommended by the AIAG-VDA FMEA Handbook for automotive |
Real-world examples of FMEA
An automotive supplier performs a Process FMEA on a new welding operation, identifying a high-priority failure mode related to inconsistent weld penetration and adding an automated inspection control to improve detection.
A medical device manufacturer conducts a Design FMEA during product development, identifying a potential failure mode involving battery depletion and revising the design to include a low-battery warning before the failure could affect the user.
An electronics manufacturer updates an existing PFMEA after a customer complaint reveals a failure mode that was previously rated low risk, adjusting the occurrence rating and adding a new detection control.
Regulations and standards related to FMEA
FMEA is not explicitly required by ISO 9001, but it supports the standard's risk-based thinking requirements under Clause 6.1 and its process control expectations under Clause 8.5. IATF 16949 places much stronger emphasis on FMEA, commonly requiring both Design and Process FMEAs as part of automotive product and process approval.
The AIAG-VDA FMEA Handbook, jointly developed by the Automotive Industry Action Group and the German Association of the Automotive Industry, harmonizes FMEA methodology across U.S. and European automotive requirements and introduced the Action Priority method in place of the traditional Risk Priority Number.
ISO 13485 and medical device risk management practices commonly incorporate FMEA-style analysis as one tool for meeting broader risk management expectations, often alongside ISO 14971.
Required by
How QT9 helps with FMEA
QT9 QMS FMEA capabilities
- Identify design and process failures early with structured, guided templates.
- Calculate and prioritize risks with automated RPN or Action Priority scoring.
- Assign actions and track their effectiveness over time.
- Link FMEA records to audits, CAPA and risk assessments for full traceability.
- Support collaboration across cross-functional teams on one platform.
- Align FMEA documentation with ISO and IATF requirements.
See QT9 Software in Action
Discover how QT9 Software helps manufacturers improve efficiency, strengthen compliance and connect quality management and ERP processes within one integrated platform.
Common mistakes with FMEA
Common mistakes include treating FMEA as a one-time exercise completed before launch rather than a living document updated as new failure data becomes available, and using a small, non-cross-functional team that misses key failure modes.
Other problems include continuing to rely on outdated RPN thresholds without adopting current Action Priority guidance where applicable, and failing to follow through on planned actions for high-priority failure modes.
Frequently asked questions
Related quality management terms
Related content
Ready to Transform Your Business?
See how QT9 Software helps manufacturers simplify operations, improve traceability and drive continuous improvement with integrated quality management and ERP software.