AIAG-VDA PFMEA and Action Priority: What Changes in Your FMEA Practice

The AIAG-VDA 2019 harmonized FMEA handbook changed how automotive suppliers do process FMEA. The biggest change isn’t in the analysis methodology — it’s in how you score and prioritize failure modes. Risk Priority Number (RPN) is out. Action Priority (AP) is in.

If you’re still scoring PFMEAs with RPN and using 100 or 120 as your action threshold, you’re working to a deprecated standard. Stellantis CSR June 2025 explicitly requires AP-only scoring for new FMEAs submitted after that date.

Why RPN was replaced

RPN (Severity × Occurrence × Detection) has three known problems that the automotive quality community agreed were significant enough to warrant replacing:

Non-uniqueness: S=10, O=2, D=1 gives RPN=20. S=2, O=2, D=5 also gives RPN=20. These are radically different risk profiles. A failure that is catastrophic-but-rare-and-detected is not the same as a failure that is minor-but-frequent-and-sometimes-missed. RPN treats them identically.
Threshold arbitrariness: “Action required above 100” is not grounded in any risk model — it was a heuristic that became convention. Different organizations use 80, 100, 120, or 150. None is derivable from first principles.
Detection gaming: Teams learned to inflate Detection scores (lower D = better detection = lower RPN) to bring failures below the action threshold without actually improving the process.

How Action Priority works

AP is derived from a 1000-cell S×O×D lookup matrix defined in the AIAG-VDA handbook. The matrix returns one of three values: High, Medium, or Low.

The logic is based on priority rules, not arithmetic:

A failure with Severity 9 or 10 gets a High AP for almost any Occurrence score — because catastrophic consequences require action regardless of probability
A failure with very high Occurrence and moderate Detection gets a Medium or High AP even at lower Severity scores
Low Severity, low Occurrence failures are typically Low AP regardless of Detection

This eliminates the RPN gaming pattern: you can’t bring a S=9 failure to a “low priority” result by claiming perfect detection. The matrix won’t let you.

What changes in your PFMEA practice

Column changes: RPN columns are removed. Add AP (High/Medium/Low) to each failure analysis row. Optionally add a “Revised AP” column after action items are completed.

Action thresholds: Replace “RPN > 100 requires action” with “AP=High requires action within [defined timeframe], AP=Medium requires documented rationale for no action, AP=Low may be accepted as-is with documentation.”

Approval criteria: The 7-step AIAG-VDA framework requires cross-functional review at Step 7. The standard specifies that the team should include representatives from at least Quality, Process Engineering, and Manufacturing — three distinct disciplines. This is not a suggestion.

Control plan derivation: Control plans are derived from PFMEA rows with Critical or Significant classification (the AIAG “SC” and “CC” characteristic flags). High AP failures without a detection control should trigger a control plan characteristic.

What stays the same

The S, O, D rating tables (1–10) are substantially unchanged — the criteria for each level are aligned between AIAG and VDA. If you’ve been rating S/O/D consistently for years, your historical assessment records are valid inputs to the new process.

The 7-step framework (Planning, Structure Analysis, Function Analysis, Failure Analysis, Risk Analysis, Optimization, Results Documentation) maps closely to what most teams were already doing. The structure is formalized, not invented.

The audit implication

IATF 16949 §6.1.2.4 requires PFMEA as part of the risk analysis process. In a surveillance audit, your CB auditor will check:

That each manufacturing process has a PFMEA
That the PFMEA uses current methodology (AP-based, not RPN-only)
That high-priority failure modes have documented actions or rationale for no action
That the control plan reflects PFMEA critical and significant characteristics

If you’re presenting a PFMEA with RPN scores and an “action above 100” policy to an auditor in 2026, expect a finding.

PFMEA software and the AP scoring problem

Most standalone PFMEA tools (Excel, some legacy QMS modules) support RPN natively but require manual workarounds for AP. You need either a lookup table in a cell formula or a sidebar reference card. Neither is reliable under production conditions.

MES-integrated PFMEA gives you AP scoring natively — the 1000-cell matrix is embedded in the application. When you enter S, O, and D scores, AP is calculated automatically and consistently across every PFMEA in your system.

See how Qontiv implements PFMEA and Control Plan with AIAG-VDA 2019 AP scoring. If you’re evaluating for an IATF 16949 re-certification or a Stellantis CSR compliance project, request a demo and we’ll run the session around your PFMEA requirements.

← Back to blog Request a demo