Introduction
Failure Mode and Effects Analysis (FMEA) is a structured preventive method for identifying how a product or process might fail, evaluating the consequences of those failures, and prioritizing actions before defects reach customers or patients. Design FMEA (DFMEA) focuses on risks created by product or system design, while Process FMEA (PFMEA) examines how manufacturing, assembly, inspection, packaging, or service processes could fail. The two methods are related but should not be merged into one undifferentiated risk table because they address different causes and controls. A design weakness may require a material, geometry, tolerance, or interface change, whereas a process weakness may require revised tooling, work instructions, mistake-proofing, maintenance, or inspection. The current AIAG VDA FMEA Handbook, published by the Automotive Industry Action Group and Verband der Automobilindustrie (AIAG-VDA), provides a harmonized automotive approach to DFMEA and PFMEA, including a structured analysis process and Action Priority rather than reliance on risk-priority number alone (AIAG, 2022). Used well, FMEA is not a paperwork exercise; it is a living record of risk reduction, design knowledge, process learning, and verification.
DFMEA, PFMEA, and the Logic of Failure Analysis
DFMEA begins with intended functions and requirements and asks how the design could fail to satisfy them. Teams examine interfaces, materials, loads, tolerances, software behavior, operating environments, foreseeable misuse, and user interactions, then connect each failure mode with its effects and causes. PFMEA starts from the production or service process and asks how each step could produce a defect or unsafe condition. A seal may fail in DFMEA because its geometry or material cannot tolerate pressure, while the same seal may fail in PFMEA because it is installed backwards, contaminated, damaged, or assembled with incorrect force. This distinction is important because effective actions must address the cause at the correct level. Design controls may include simulation, design review, testing, and tolerance analysis; process controls may include fixtures, sensors, automated checks, standardized work, and statistical monitoring. Linking the two analyses allows design risk to inform process planning and process experience to feed back into future design decisions, creating a connected prevention system rather than isolated documents.
From Risk Ranking to Action Priority
Traditional FMEA practice often multiplied severity, occurrence, and detection ratings to create a risk-priority number (RPN). Although easy to calculate, RPN can be misleading because different combinations of ratings can produce the same number even when their consequences differ substantially. A severe safety effect with low occurrence should not automatically receive the same management response as a minor inconvenience with a different numerical combination. The AIAG-VDA approach therefore uses Action Priority, which considers severity, occurrence, and detection through defined decision logic and places stronger emphasis on what action is needed rather than on one multiplied score (AIAG, 2022). Teams should still document the rationale for each rating and use consistent criteria. Severity describes the consequence of the effect, occurrence estimates how likely the cause is, and detection reflects the ability of existing controls to identify the failure or cause before it escapes. Ratings are not measurements of absolute truth; they are structured judgments that should be supported by field data, test results, capability studies, complaints, audits, or engineering evidence whenever available.
Tracking Improvement and Verifying Effectiveness
An FMEA becomes valuable only when identified risks lead to action and the effectiveness of those actions is verified. Each recommended action should have an owner, due date, intended risk-reduction mechanism, and evidence required for closure. After implementation, the team should reassess the relevant ratings and record what changed rather than merely lowering a number. A new fixture that prevents reversed assembly, for example, should be supported by validation showing that the error cannot reasonably occur under intended use; additional inspection may improve detection without reducing occurrence. Trend data can also show whether corrective action works in production. Scrap, rework, complaints, warranty returns, process capability, audit findings, and nonconformities may reveal that the assumed risk reduction was too optimistic. Version control is essential because the document should show when it was reviewed, which assumptions changed, and why. The Failure Mode and Effects Analysis similarly emphasizes FMEA as a proactive method for prioritizing and reducing potential failures rather than as a one-time scoring exercise (American Society for Quality [ASQ], n.d.).
Relationship With ISO 14971 and Other Risk Systems
In medical-device work, DFMEA and PFMEA can support the broader risk-management process required by ISO 14971, but they are not substitutes for the standard. ISO 14971:2019, confirmed as current in 2025, establishes a life-cycle process for identifying hazards, estimating and evaluating risks, implementing controls, and monitoring production and post-production information (International Organization for Standardization [ISO], 2019). FMEA is particularly useful for analyzing failure modes associated with components, functions, and manufacturing steps, while ISO 14971 also requires consideration of hazardous situations, reasonably foreseeable sequences of events, benefit-risk questions where applicable, and risk information that may not fit neatly into an FMEA table. Similar integration is needed in automotive and other regulated industries, where FMEA should connect with design verification, control plans, process capability, corrective action, change control, reliability testing, and complaint or field data. A risk file is strongest when these systems share assumptions and evidence rather than producing contradictory rankings maintained by separate departments.
Common Weaknesses and a Practical Improvement Cycle
FMEA programs fail when teams copy generic failure modes, assign ratings without evidence, use RPN thresholds mechanically, close actions without verification, or update documents only before an audit. Another weakness is starting too late, after the product or process has already been fixed by expensive tooling or validation decisions. Effective practice begins early and involves cross-functional participants who understand design, manufacturing, quality, service, suppliers, and user needs. A practical cycle is to define scope and functions, identify failure modes and effects, analyze causes, evaluate existing prevention and detection controls, prioritize action, implement improvements, verify results, and update the analysis when changes or new evidence arise. Production and field information should be fed back continuously. If an unexpected failure appears in complaints, warranty data, or audit results, the team should determine whether the failure mode was absent, underrated, or poorly controlled. This learning function is central because FMEA is meant to preserve organizational knowledge and prevent recurrence across future designs and processes.
Conclusion
DFMEA and PFMEA provide a disciplined way to anticipate failure before it becomes a customer, safety, or regulatory problem. DFMEA examines whether a product’s design can meet intended functions under expected conditions, while PFMEA examines whether the process can produce that design consistently. Their value lies not in generating a risk score but in connecting effects, causes, controls, actions, and verification. Modern practice has moved beyond simple dependence on RPN toward structured prioritization such as the AIAG-VDA Action Priority approach, while regulated industries also integrate FMEA with broader systems such as ISO 14971. Improvement tracking should therefore document owners, deadlines, evidence, revised controls, and post-action performance rather than merely lowering ratings on paper. The strongest FMEA process is iterative: design learning informs process planning, production experience informs future design, and field evidence continually tests earlier assumptions. When maintained as a living risk-management tool, FMEA supports safer products, more capable processes, stronger change control, and more transparent decisions across the product life cycle (AIAG, 2022; ISO, 2019).
References
Automotive Industry Action Group. (2022). AIAG & VDA FMEA Handbook. https://www.aiag.org/training-and-resources/manuals/details/FMEAAV-1
American Society for Quality. (n.d.). Failure Mode and Effects Analysis (FMEA). https://asq.org/quality-resources/fmea
International Organization for Standardization. (2019). ISO 14971:2019 Medical devices—Application of risk management to medical devices. https://www.iso.org/standard/72704.html
Cite This Work
To export a reference to this article please select a referencing stye below:
Academic Master Education Team is a group of academic editors and subject specialists responsible for producing structured, research-backed essays across multiple disciplines. Each article is developed following Academic Master’s Editorial Policy and supported by credible academic references. The team ensures clarity, citation accuracy, and adherence to ethical academic writing standards
Content reviewed under Academic Master Editorial Policy.
