FMEAFailure Mode and Effects Analysis
A systematic, bottom-up methodology to identify potential failures in a design or process, assess their impact, and prioritise mitigations based on severity, occurrence, and detection.

On this page · 9 sections
- 1Proactive Risk: The Origins of FMEA
- 2Design FMEA (DFMEA) vs. Process FMEA (PFMEA)
- 3The Scoring Trinity: Severity, Occurrence, and Detection
- 4The AIAG-VDA 2019 Approach: A New Standard
- 5FMEA in Regulated Industries: ICH Q9(R1) and ISO 14971
- 6Facilitation: The Art of the FMEA Workshop
- 7The 'Living Document' Mandate vs. Stale Files
- 8Common Failure Modes of FMEA Itself
- 9How V5 Ultimate Modernizes FMEA
How does FMEA apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01Proactive Risk: The Origins of FMEA
Failure Mode and Effects Analysis (FMEA) is a structured, step-by-step approach for identifying all possible failures in a design, a manufacturing or assembly process, or a product or service 1. It is a 'bottom-up' technique, meaning it starts at the lowest level of a system—individual components or process steps—and works upward to understand how those local failures might impact the entire system and, ultimately, the end-user.
The methodology originated in the late 1940s within the U.S. military (documented in MIL-P-1629) as a way to improve the reliability of mission-critical systems. It gained widespread industrial prominence through NASA’s Apollo program and was later adopted by the automotive industry in the 1970s (specifically by Ford) to prevent safety and quality issues before they reached the assembly line. Today, FMEA is a cornerstone of quality management in highly regulated sectors like medical devices, aerospace, and pharmaceuticals.
"FMEA is used during design to prevent failures. Later, it can be used for process control, as well as before and during ongoing operations."
Unlike reactive tools like root-cause-analysis, which look backward at what already went wrong, FMEA is inherently prospective. Its primary goal is to identify and mitigate risks before they manifest as defects, deviations, or patient harm. In the V5 ecosystem, FMEA is treated as a living digital artifact rather than a static spreadsheet, ensuring that risk assessments remain synchronized with the actual state of the design and shop floor.
02Design FMEA (DFMEA) vs. Process FMEA (PFMEA)
In most manufacturing environments, FMEA is split into two distinct but related activities: Design FMEA and Process FMEA. While they share the same underlying scoring mechanics, their scopes and objectives differ significantly.
Design FMEA (DFMEA)
DFMEA focuses on the product itself. It analyzes the components, sub-assemblies, and interfaces to identify potential design-related failures. The goal is to ensure the product meets its intended functions under all expected conditions. For example, a DFMEA for a medical syringe would look at the material properties of the plunger, the seal integrity of the gasket, and the sharpness of the needle. Failure modes in a DFMEA typically stem from design weaknesses, such as incorrect material selection, insufficient tolerances, or unforeseen environmental stressors.
Process FMEA (PFMEA)
PFMEA focuses on the manufacturing or assembly process. It assumes the design is 'correct' and instead asks how the manufacturing steps might fail to reproduce that design consistently. The analysis follows a process flow diagram, examining each step for potential deviations. In the same syringe example, a PFMEA would look at the injection molding step, the sterilization cycle, and the automated packaging line. Failure modes here typically include human error, machine malfunction, or variability in raw materials.
| Feature | DFMEA | PFMEA |
|---|---|---|
| Primary Focus | Product design and functions | Manufacturing and assembly steps |
| Typical Failure Mode | Inadequate strength, wear, leakage | Misaligned part, contamination, missing step |
| Typical Cause | Design error, material choice | Operator error, machine drift, setup error |
| Owner | Design / R&D Engineering | Manufacturing / Process Engineering |
| Timing | Before design freeze | Before process validation (IQ/OQ/PQ) |
03The Scoring Trinity: Severity, Occurrence, and Detection
The core of FMEA risk quantification lies in three distinct axes, typically rated on a scale of 1 to 10. These scores allow teams to move beyond subjective 'gut feelings' toward a more standardized assessment of risk.
- **Severity (S):** Measures the impact of the failure mode on the customer or end-user. A score of 1 indicates no discernible effect, while 10 indicates a catastrophic failure involving safety or regulatory non-compliance.
- **Occurrence (O):** Estimates the frequency or likelihood that the specific failure mode will happen during the product's life or the process operation. A 1 indicates an extremely unlikely event, while a 10 indicates the failure is almost certain to occur.
- **Detection (D):** Assesses the ability of current controls (design verification or process inspection) to catch the failure before it reaches the customer. A 1 indicates the failure is almost certain to be detected, while a 10 indicates there is no known way to detect it.
Historically, these three numbers were multiplied to create the **Risk Priority Number (RPN)**: S × O × D. In this classical model, the maximum RPN is 1000. Organizations would often set 'RPN thresholds' (e.g., an RPN above 150 requires action), but this approach is now widely criticized and has been largely replaced in modern standards.
04The AIAG-VDA 2019 Approach: A New Standard
In 2019, the Automotive Industry Action Group (AIAG) and the German Verband der Automobilindustrie (VDA) released a harmonized FMEA handbook. This update introduced the **7-Step Approach**, which provides a more rigorous framework than the traditional 'fill-in-the-spreadsheet' method 2 4.
- **Planning and Preparation:** Define the scope, team, and boundaries of the analysis.
- **Structure Analysis:** Create a visual breakdown of the system (e.g., a tree structure for design or a flow chart for process).
- **Function Analysis:** Describe what each element is supposed to do and how it relates to the higher-level system.
- **Failure Analysis:** Identify failure modes (loss of function), effects (the consequence), and causes (the mechanism of failure).
- **Risk Analysis:** Assign S, O, and D scores and determine the Action Priority (AP).
- **Optimization:** Define and track actions to reduce risk, then re-score the items.
- **Results Documentation:** Communicate the results and archive the findings.
Perhaps the most significant change was the official retirement of RPN thresholds in favor of **Action Priority (AP)** tables. AP uses the combination of S, O, and D to assign a priority level of High, Medium, or Low. This ensures that even low-RPN items with high Severity are flagged for mandatory review and mitigation.
05FMEA in Regulated Industries: ICH Q9(R1) and ISO 14971
In life sciences, FMEA is not just a best practice; it is often the primary tool used to satisfy regulatory requirements for Quality Risk Management (QRM).
Pharmaceuticals: ICH Q9(R1)
The ICH Q9(R1) guideline provides a framework for QRM throughout the pharmaceutical lifecycle. FMEA is explicitly listed in Annex I as a formal risk management tool 1. The 2023 revision, R1, emphasizes the need for 'science-based' decision-making and warns against high levels of subjectivity in risk assessments. Regulators expect pharma companies to justify their S, O, and D scoring with data—such as historical deviation rates or statistical process capability—rather than mere expert opinion.
Medical Devices: ISO 14971
For medical device manufacturers, ISO 14971 is the mandatory standard for risk management. While ISO 14971 focuses on the 'Hazard' (source of harm) and 'Harm' (physical injury), FMEA is the bridge that connects the device's technical failure modes to those hazards. In a device risk file, the PFMEA is often used to ensure that process-related failures do not lead to the release of non-conforming products that could cause patient harm. The relationship is symbiotic: FMEA provides the bottom-up technical detail, while ISO 14971 provides the top-down safety framework.
06Facilitation: The Art of the FMEA Workshop
A common failure of FMEA is the 'authoring silo'—where a single quality engineer writes the entire document in isolation. This almost always results in a weak analysis that misses critical failure modes known only to the people doing the actual work.
An effective FMEA requires a cross-functional team, including:
- **The Facilitator:** Typically a Quality Engineer who knows the FMEA methodology and keeps the team focused on the scope.
- **Design/Process Owners:** The engineers responsible for the system being analyzed.
- **Operations/Operators:** The 'ground truth' experts who see how the equipment behaves on the third shift or how components fit together in real-world conditions.
- **Customer/Downstream Representative:** Someone who understands how a failure in this step will impact the next operation or the end-user.
The facilitator's role is to manage the group dynamics, preventing 'scoring stalemates' where the team spends hours debating whether an Occurrence is a 4 or a 5. In a digital environment like V5, the facilitator can capture these discussions in the audit trail, providing the 'formality' and 'reasoning' required by ICH Q9(R1).
07The 'Living Document' Mandate vs. Stale Files
A recurring finding in regulatory audits is the 'Stale FMEA.' This occurs when a company performs an FMEA during initial development, files it away in the document-control system, and never touches it again. In reality, an FMEA must be a living document that evolves with the product lifecycle.
There are three primary triggers for updating an FMEA:
- **Change Control:** Any change to the design or process (even minor ones) must be evaluated for its impact on existing failure modes or the introduction of new ones. A change-control package without an FMEA review is incomplete.
- **Quality Signals:** When a deviation, ncr, or customer complaint occurs, the team should ask: 'Is this failure mode in our FMEA?' If it is, were the S, O, or D scores accurate? If it isn't, the FMEA must be updated immediately.
- **Periodic Review:** As specified in ICH Q9(R1) and ISO 14971, risks must be reviewed periodically to ensure the original assumptions still hold true as the process matures.
"The effectiveness of FMEA is directly proportional to its accuracy at the moment of the next change or failure."
Manual systems make this linkage nearly impossible to maintain. V5 Ultimate solves this by treating the FMEA as a database of linked risks. When a deviation is closed, the system can automatically flag the related FMEA line for re-evaluation, ensuring the 'living document' mandate is met through workflow rather than manual memory.
08Common Failure Modes of FMEA Itself
Ironically, the FMEA process itself is prone to several failure modes that can undermine its value as a risk management tool.
- **Gaming the Scores:** Teams often feel pressured to keep RPNs low to avoid expensive mitigations. This leads to 'Detection creeping'—assigning a low D score based on a visual inspection that isn't actually capable of catching the defect.
- **Scoping Failures:** If the FMEA boundary is too narrow, it misses system-level interactions. If it's too broad, the team gets lost in the weeds and never finishes the analysis.
- **Generic Failure Modes:** Using vague terms like 'human error' or 'equipment failure' without specifying the mechanism prevents effective mitigation. 'Operator skips step 4 due to cluttered workspace' is a much better failure mode than 'Operator error.'
- **Missing the 'Effects':** Teams often describe the failure mode but fail to trace the effect all the way to the end-user. If the effect isn't clear, the Severity score cannot be justified.
To avoid these pitfalls, organizations should implement an FMEA 'Quality Check' process, where an independent reviewer (often a senior Quality Manager or Risk Lead) audits the FMEA for logical consistency and evidence-based scoring.
09How V5 Ultimate Modernizes FMEA
V5 Ultimate moves FMEA from the world of spreadsheets and PDFs into a structured, relational data model. This transformation addresses the core pain points of traditional risk management.
- **Traceability by Design:** Every failure mode is linked to a process step or design requirement. When a step changes, V5 alerts the risk owner to re-evaluate the specific linked risks.
- **Embedded Logic:** AIAG-VDA Action Priority tables are built directly into the interface. Users don't need to consult external lookups; the system calculates the priority level and flags 'High' items automatically.
- **Closed-Loop Mitigation:** When the team identifies a needed mitigation, V5 creates a linked capa or task. The FMEA record remains in an 'Open' or 'Interim' state until the mitigation is validated and the CAPA is closed.
- **Real-Time Sentiment:** V5 can surface shop-floor data—like yield loss or deviation frequency—next to the Occurrence score, helping teams move from subjective estimates to data-driven 'science-based' scoring as required by ICH Q9(R1).
- **Single Source of Truth:** No more searching through shared drives for 'FMEA_Final_v3_revB_Copy.xlsx'. The current, approved risk assessment is always visible and auditable.
Frequently asked questions
Q.Is FMEA mandatory for FDA compliance?+
FMEA is not explicitly named in the 21 CFR regulations, but it is considered a 'state-of-the-art' method for satisfying the risk management requirements in 21 CFR 820.30 (Design Controls) for medical devices. For pharmaceuticals, ICH Q9 (which the FDA has adopted as guidance) lists FMEA as a primary tool for Quality Risk Management.
Q.Can I use FMEA for software?+
Yes, this is often called Software FMEA (SFMEA). It focuses on how software functions, interfaces, or subroutines might fail (e.g., buffer overflows, timing errors, or incorrect logic). While the mechanics are the same, the 'causes' are almost always design-related, as software does not 'wear out' like mechanical components.
Q.What is the difference between FMEA and FMECA?+
FMECA (Failure Mode, Effects, and Criticality Analysis) adds a 'Criticality' component, which involves quantitative calculations of failure rates and their impact. FMEA is the qualitative foundation; FMECA is the more data-intensive extension often used in aerospace and defense.
Q.How often should we update our FMEA?+
At a minimum, FMEAs should be reviewed annually. However, they should be updated 'real-time' whenever a significant change is made to the product/process or when a high-severity quality event occurs that wasn't previously analyzed.
Q.Do we have to use the 1-10 scoring scale?+
While 1-10 is the industry standard (endorsed by AIAG and VDA), some organizations use 1-5 or even qualitative scales (Low/Medium/High). The key requirement is that your scoring definitions are clearly documented, consistently applied, and justifiable to a regulator.
Primary sources
Further reading
- ISO 14971 — Risk management for devicesThe foundational standard for medical device risk files where FMEA is a core tool.
- ICH Q9(R1) — Quality risk managementThe global pharmaceutical framework for science-based risk decision-making.
- CAPA — Corrective and Preventive ActionHow FMEA-identified mitigations are tracked and validated in the quality system.
- Root Cause AnalysisThe retrospective counterpart to FMEA’s prospective risk assessment.
- Change ControlThe critical trigger for updating and maintaining FMEA documents throughout the lifecycle.
Explore this topic
FMEA sits inside this topic cluster in our glossary. Every neighbour is one click away.
Root-cause toolkit, SPC, capability and the rest of the QA practitioner's bench.
Want to see how FMEA could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
