The FMEA standard that applies to your work depends on your industry and, often, the specific requirements written into your customer contracts. Automotive suppliers follow the AIAG & VDA FMEA Handbook, sometimes alongside SAE J1739. General engineering, aerospace, energy, and consumer electronics default to IEC 60812. Medical device manufacturers operate under ISO 14971, using FMEA as one input into a broader risk management process. Quality management certifications such as ISO 9001 and IATF 16949 sit on top of these, requiring risk analysis without always naming FMEA as the method.
Picking the wrong framework, or ignoring the one your customer expects, can disqualify a supplier before production starts. The sections below map each standard to its industry, explain what it actually requires you to produce, and flag the documentation rules that come with it.
Automotive Suppliers: AIAG and VDA FMEA Handbook
The AIAG & VDA FMEA Handbook was developed by a global team of OEM and Tier 1 supplier experts to combine North American (AIAG) and German (VDA) methodologies into a single harmonized approach.1Automotive Industry Action Group. AIAG and VDA FMEA Handbook It covers Design FMEA, Process FMEA, and the newer Supplemental FMEA for Monitoring and System Response (FMEA-MSR).
For automotive suppliers, this handbook is effectively mandatory. IATF 16949, the quality management system standard for the automotive industry, explicitly requires both design risk analysis through FMEA and manufacturing process FMEA as part of its design and development output requirements. If you supply any tier of the automotive production chain, your customer almost certainly expects AIAG & VDA.
SAE J1739 as a Companion or Alternative
SAE J1739 is a complementary automotive FMEA standard providing terms, rating charts, and worksheets for Design FMEA, Process FMEA, and FMEA-MSR. It aligns with ISO 26262 for road vehicle functional safety. Some automotive OEMs specify J1739 in their customer-specific requirements, either instead of the AIAG & VDA Handbook or alongside it. Check the contract before assuming one covers the other.
General Engineering, Aerospace, Energy: IEC 60812
Outside automotive, IEC 60812:2018 (Edition 3.0) is the broadest international standard for FMEA and FMECA. It applies to hardware, software, processes including human action, and their interfaces in any combination.2International Electrotechnical Commission. IEC 60812:2018 Industries ranging from aerospace to energy to consumer electronics use IEC 60812 when no sector-specific standard exists or when contracts reference it directly. Defense contractors also typically reference IEC 60812 today, since the older U.S. military standard MIL-STD-1629A has been cancelled, though its methodology shaped every modern FMEA framework.3Reliability Analysis Center. Failure Mode, Effects and Criticality Analysis (FMECA)
One practical difference: IEC 60812 still accepts the traditional Risk Priority Number approach, where automotive customers following AIAG & VDA now expect the Action Priority method instead. More on that distinction below.
Medical Devices: ISO 14971, With FMEA as One Input
Medical device manufacturers work under ISO 14971:2019, which specifies a complete risk management process covering all phases of a device’s life cycle, from initial design through post-production monitoring. FMEA is one tool used within this framework, but it does not satisfy ISO 14971 on its own.
The standard requires identifying hazards (not just failure modes), defining hazardous situations where people are exposed to those hazards, estimating both severity and probability of harm, implementing risk controls, and evaluating whether overall residual risk remains acceptable. A device can pose real risks to patients even when it functions exactly as designed. Biocompatibility reactions and ergonomic issues that lead to use errors are not failure modes, and a standard FMEA worksheet will not capture them.
The FDA’s Quality System Regulation at 21 CFR 820.30 requires manufacturers of Class II and Class III devices, and certain Class I devices, to establish design control procedures that include documented design reviews and verification activities.4eCFR. 21 CFR 820.30 – Design Controls The regulation does not name FMEA specifically, but risk analysis is a standard part of demonstrating compliance, and FMEA is among the most common tools device makers use during design verification. The FDA recognizes ISO 14971:2019 as a consensus standard, so aligning your risk management process with it strengthens both regulatory submissions and liability defense.
The practical takeaway for device teams: use FMEA as one input into the larger ISO 14971 risk management file rather than as a standalone deliverable.
ISO 9001 and IATF 16949: The Quality System Overlay
ISO 9001:2015 introduced risk-based thinking as a core requirement, meaning organizations pursuing certification must systematically identify and address risks throughout their quality management system.5International Organization for Standardization. ISO 9001 2015 and Risk The standard does not prescribe FMEA specifically, but FMEA is one of the most common methods organizations use to demonstrate compliance.
IATF 16949 builds on ISO 9001 with automotive-specific additions and goes further by explicitly requiring FMEA as a design and process output. If you hold or are pursuing IATF 16949 certification, you need both DFMEA and PFMEA, and they need to align with the AIAG & VDA methodology your customers expect.
How to Confirm Which Standard Applies
Three things determine the answer. First, your industry sets the default: automotive points to AIAG & VDA, medical devices to ISO 14971, most other manufacturing sectors to IEC 60812. Second, your quality system certification can add requirements on top of the industry default, as IATF 16949 does by mandating FMEA explicitly. Third, your customer-specific requirements can override or supplement both. An automotive OEM may require J1739 instead of AIAG & VDA, or require both. A defense program may reference IEC 60812 or impose its own specification. Read the contract before deciding.
What Every FMEA Standard Asks You to Produce
The AIAG & VDA Handbook structures FMEA around seven sequential steps. Even under a different standard, this sequence captures logic that virtually all modern FMEA approaches share:
- Planning and preparation: define the scope, assemble a cross-functional team, decide whether a Design FMEA or Process FMEA is called for.
- Structure analysis: break the system into layers using a structure tree or block diagram, or for a process, a process flow diagram.
- Function analysis: assign functions and requirements to each element identified above.
- Failure analysis: identify how each function could fail, following the chain of failure effect, failure mode, and failure cause.
- Risk analysis: rate each failure chain using severity, occurrence, and detection, then determine the Action Priority level. Document current preventive and detection controls.
- Optimization: assign and track improvement actions for high and medium priority items, each with a responsible owner, target date, and status.
- Results documentation: archive the completed analysis with risk ratings before and after optimization, action completion records, and management sign-offs.
Design FMEA vs Process FMEA
These two types target different sources of failure, and confusing their scope is a common mistake.
A Design FMEA (DFMEA) focuses on the product itself and how a component or system might fail to perform its intended function because of a design weakness. Teams conduct DFMEAs early in product development, typically during the second phase of the Advanced Product Quality Planning (APQP) process. Inputs include block diagrams, parameter charts, and the bill of materials.
A Process FMEA (PFMEA) focuses on how the manufacturing, assembly, or logistics process could introduce failures into a product that was correctly designed. PFMEAs happen during the third phase of APQP. Inputs include the process flow diagram and the completed DFMEA. The underlying assumption is that the product design is already sound.
The two documents feed each other. A DFMEA might identify a tight tolerance that, if not held during machining, causes a functional failure. That risk carries forward into the PFMEA, where the team evaluates whether the machining process can reliably hold the tolerance. If one document changes, the other needs review.
FMEA-MSR for Monitored Systems
The AIAG & VDA Handbook added a third type, FMEA-MSR, which supplements the Design FMEA. A standard DFMEA asks how a design might fail. An FMEA-MSR asks whether, if a failure occurs during customer use, the monitoring system will detect it and the system will respond safely.
FMEA-MSR applies only when a design includes active or passive monitoring and response components, such as a vehicle stability control system that detects a skid and adjusts braking. If the product has no diagnostic monitoring capability, FMEA-MSR is not needed. The risk evaluation uses Severity-Frequency-Monitoring (S-F-M) in place of Severity-Occurrence-Detection, and its Action Priority tables differ accordingly. FMEA-MSR connects directly to ISO 26262 functional safety requirements, making it important for any automotive system where a failure could affect safe vehicle operation.
Action Priority vs Risk Priority Number
Which prioritization method you use depends on the standard. For decades, FMEA practitioners calculated a Risk Priority Number by multiplying Severity by Occurrence by Detection, producing a value between 1 and 1,000.6ScienceDirect. Total Quality Management – 26.8 Risk Priority Number Teams set a threshold, often 100 or 125, above which corrective action was required.
The AIAG & VDA Handbook moved away from RPN because treating all three factors as equally important produces misleading results. A failure with severity 10, occurrence 2, and detection 2 generates an RPN of 40, below most thresholds, yet the failure itself is a life-threatening safety hazard. A nuisance failure with severity 2, occurrence 10, and detection 5 produces an RPN of 100 and triggers action despite posing no real danger. Different companies also used different thresholds, making cross-supply-chain comparisons unreliable.
The Action Priority method replaces the single RPN with a logic-based table that assigns each failure chain High, Medium, or Low priority. Severity is always the first filter: a safety-critical failure (severity 9 or 10) is always rated High regardless of occurrence and detection. The three levels drive different responses. High priority requires action, sometimes with management review and approval; if no action is taken, a documented justification is mandatory. Medium priority calls for action or a written justification for not acting. Low priority is at the team’s discretion.
Organizations still using RPN are not necessarily wrong. IEC 60812 and some customer-specific requirements still reference it. If your customer follows the AIAG & VDA Handbook, the AP method is the expected approach, and submitting RPN-based analyses may not satisfy their requirements.
Documentation, Submission, and Retention
A completed FMEA becomes a controlled quality record with contractual and legal significance.
Automotive PPAP
In automotive, both the Design FMEA and Process FMEA are required elements of the Production Part Approval Process (PPAP) submission. The DFMEA, process flow diagram, PFMEA, and control plan are linked documents: when one changes, all four need review. Submitting a PPAP without current FMEA documentation, or with FMEAs that do not align with the control plan, is one of the faster ways to get a submission rejected.
Sign-Off and Electronic Records
Finalized FMEA documents require formal approval from management and the responsible department heads. The completed package is uploaded to the organization’s quality management system or submitted directly to the customer as part of the PPAP or equivalent approval process.
For industries regulated by the FDA, electronic records and signatures must comply with the underlying predicate rule requirements. The FDA’s guidance on 21 CFR Part 11 applies when electronic records are required to be maintained or submitted under existing regulations. Even where the agency exercises enforcement discretion on certain Part 11 specifics, organizations must still ensure the integrity, authenticity, and reliability of their electronic FMEA records.7Food and Drug Administration. Part 11, Electronic Records; Electronic Signatures – Scope and Application
Retention Periods
Under IATF 16949, product and process design records, including FMEA documents, must be retained for the entire period the product is active in production and service, plus one additional calendar year. Customer-specific requirements or regulatory agencies may extend that period. Many organizations retain FMEA records indefinitely because they serve as evidence of due diligence if a product liability claim or regulatory audit surfaces years after production ends. Destroying records that could demonstrate your risk analysis process was thorough is a risk in itself.