AIAG-VDA FMEA: The 7-Step Approach

The AIAG-VDA FMEA is the harmonized failure mode and effects analysis method published jointly by the Automotive Industry Action Group and Germany's VDA in 2019. It restructures FMEA into a seven-step approach and replaces the traditional Risk Priority Number (RPN) with Action Priority (AP), a High/Medium/Low rating driven by the combination of Severity, Occurrence, and Detection. It applies to both design FMEA and process FMEA.

For years, North American suppliers ran FMEA to the AIAG 4th Edition and German suppliers ran it to the VDA method, and a supplier serving both markets kept two formats for the same analysis. The 2019 AIAG-VDA handbook merged them into one. If your team learned FMEA from the old blue AIAG manual, the thinking is familiar, but the structure, the worksheet, and the way risk is prioritized all changed. This guide walks the seven steps and the shift from RPN to Action Priority. For the fundamentals of the tool itself, start with our guide to FMEA.

What changed in the 2019 AIAG-VDA handbook?

The headline changes are a seven-step process and the retirement of RPN. The old approach asked teams to fill in a worksheet and multiply three 1-to-10 ratings, Severity, Occurrence, and Detection, into a single Risk Priority Number from 1 to 1000, then chase the biggest numbers. That produced two well-known problems: very different risk profiles could share the same RPN (a 9-2-5 and a 5-6-3 both give 90), and teams gamed the detection score to pull an RPN under an arbitrary action threshold. The AIAG-VDA method replaces RPN with Action Priority, which does not multiply anything. It reads the combination of S, O, and D against a published table and returns High, Medium, or Low, with Severity weighted first. A severity of 9 or 10 draws attention regardless of how rare or detectable the failure is.

The method also formalizes the analysis into a repeatable seven-step flow, adds structure and function analysis as explicit early steps (often drawn as trees and nets rather than jumped over), and introduces a supplemental FMEA-MSR (Monitoring and System Response) for analyzing how a system detects and responds to failures during customer operation. The result is more front-loaded work and a clearer line from function to failure to action.

What are the seven steps?

The seven steps run in order because each one produces the input the next one needs. Skipping the early structure and function work is the most common way an AIAG-VDA FMEA turns back into an unfocused list of failure guesses.

1. Planning and preparation. Define scope, boundaries, and the team. Set the "5T": InTent, Timing, Team, Task, and Tool. Decide what is in and out of the analysis before anyone lists a failure. This step is where a good FMEA is won or lost.
2. Structure analysis. Break the system or process into its elements and show how they relate, usually as a structure tree. For a process FMEA this is the process steps and their sub-operations; for a design FMEA it is the system, subsystems, and components.
3. Function analysis. Assign the functions and requirements to each element, and show how functions connect across the structure (a function net). You cannot analyze how something fails until you have stated clearly what it is supposed to do.
4. Failure analysis. For each function, identify the failure effect (FE), the failure mode (FM), and the failure cause (FC), and link them into a failure chain across the structure levels. This is the core of the analysis and where the structure and function work pays off.
5. Risk analysis. Rate Severity of the effect, Occurrence of the cause, and Detection of the current controls, document prevention and detection controls, and assign an Action Priority (High, Medium, or Low) from the AP table.
6. Optimization. For High and Medium AP items, define and assign actions to reduce risk, lower occurrence with prevention controls, or improve detection, then re-rate once actions are complete. This is where the FMEA changes the product or process rather than just describing it.
7. Results documentation. Summarize and communicate what was analyzed, what actions were taken, and the residual risk, to management and the customer. The FMEA is a living document that feeds the control plan and gets revisited when the design or process changes.

How does Action Priority replace RPN?

Action Priority is a lookup, not a multiplication. Instead of computing S x O x D and comparing the product to a threshold, the team reads the specific combination of Severity, Occurrence, and Detection against the AIAG-VDA Action Priority table, which returns High, Medium, or Low. The logic weights Severity first, then Occurrence, then Detection, because a rare, easily detected failure that is catastrophic when it happens still deserves attention, something the old RPN could bury under a low product. High AP means action is required to reduce risk or a justification for taking none must be documented; Medium AP means action should be taken; Low AP means action is at the team's discretion.

The practical effect is that teams can no longer make risk disappear by inflating the Detection score, and two failures with the same math are no longer treated as equal when their severity differs. AP is about deciding where to act, not producing a leaderboard number. It pairs naturally with the way risk is managed downstream in a control plan and verified through statistical process control.

Does AIAG-VDA replace DFMEA and PFMEA?

No. The seven-step approach is the method; design FMEA and process FMEA are still the two main applications of it. A design FMEA analyzes failures in the product's design, and a process FMEA analyzes failures in the manufacturing or assembly process. Both now follow the same seven steps and use Action Priority, which is part of the point: a single, consistent structure across design and process, and across the North American and European supply chains. The handbook also adds the supplemental FMEA-MSR for monitoring and system response, aimed mainly at systems that diagnose and react to faults in the field.

What are the most common AIAG-VDA mistakes?

The failure patterns are consistent. Teams skip or rush the structure and function steps and jump straight to listing failure modes, which produces a shallow, unfocused analysis with no clear link from function to failure. They treat the FMEA as a one-time document created to satisfy a customer, then never revisit it when the process changes or field data shifts the occurrence of a cause. They write vague failure causes like "operator error" instead of the specific mechanism, which makes the occurrence rating meaningless. And they close out High and Medium Action Priority items without re-rating after the actions are complete, so the residual risk is never actually confirmed. A useful audit is to check whether every High AP item has either a completed action with a re-rating or a documented justification for taking none, which is exactly what the handbook expects.

What do the standards say?

How does a connected floor strengthen a process FMEA?

A process FMEA is only as good as the failure and occurrence data behind it, and in most plants that data lives in memory and on paper. When downtime reasons, defect codes, and process parameters are captured digitally at the station, the FMEA team can rate Occurrence from real history instead of gut feel, and the optimization actions can be verified against a live stream rather than a one-time audit. Trends in the floor data also tell you when a failure mode's occurrence has shifted enough to justify revisiting the FMEA, keeping it the living document the handbook intends. That is the shift a processor made in our CLS case study moving from paper logs to real-time operational data and grounding quality decisions in evidence. The same discipline feeds naturally into advanced product quality planning where the FMEA is a required deliverable. See how Harmony captures floor data without a rip-and-replace on our features overview.