RPN vs Action Priority: Why the AIAG-VDA FMEA Handbook Changed How We Prioritize Risk

If you have been doing FMEA for any length of time, you know the Risk Priority Number. Severity times Occurrence times Detection. A single number that tells you which failure modes to fix first.

Except it doesn't. And that is why the AIAG-VDA harmonized FMEA handbook introduced Action Priority.

The Problem with RPN

Consider two failure modes:

Failure Mode A: Severity 9 (safety-critical), Occurrence 2 (unlikely), Detection 3 (good controls). RPN = 54.

Failure Mode B: Severity 3 (minor inconvenience), Occurrence 6 (moderate), Detection 6 (poor controls). RPN = 108.

Under RPN-only prioritization, Failure Mode B gets attention first because 108 > 54. But Failure Mode A is a safety hazard. If it occurs, people could be hurt. The mathematical equality of 9 x 2 x 3 and 3 x 6 x 6 obscures the fact that these are fundamentally different risks.

This is not a theoretical concern. It is the reason why FMEA practitioners have argued about RPN thresholds for decades. What is the cutoff? 100? 125? 200? There is no universal answer because the question itself is flawed.

How Action Priority Works

The AIAG-VDA handbook provides a lookup table that maps every S-O-D combination to one of three action priorities:

• High (H): Action required
• Medium (M): Action should be taken
• Low (L): Action is optional

The table is designed so that:

• Any failure mode with Severity 9 or 10 (safety-critical) gets HIGH priority regardless of Occurrence and Detection
• Moderate severity with high occurrence gets MEDIUM or HIGH even if detection is good
• Low severity with good controls gets LOW even if occurrence is moderate

This is what experienced FMEA practitioners have always done intuitively — they override the RPN when severity is high. The AP table codifies that intuition into a repeatable, auditable process.

What This Means in Practice

RPN is not eliminated. It is still calculated and included in the FMEA worksheet. Some organizations use it for trending — tracking how RPN changes over time as actions are implemented.

AP drives the action decision. When the team reviews the FMEA, the first filter is AP, not RPN. All HIGH items must have actions. MEDIUM items should have actions. LOW items are at the team's discretion.

Rating scales must be consistent. The AP table assumes the standard AIAG-VDA 1-10 scales. If your organization uses custom scales, you need to map them to the standard scales or create a custom AP table.

Training matters. Teams accustomed to RPN-only prioritization need to understand why an RPN of 54 can be more urgent than an RPN of 200. The AP table makes this explicit, but the reasoning needs to be communicated.

The Takeaway

RPN is a useful metric for tracking risk reduction over time. Action Priority is the right metric for deciding what to fix. The AIAG-VDA standard recognized this distinction and gave teams a structured way to make better prioritization decisions.

If your FMEA process still uses RPN as the sole prioritization mechanism, it is time to adopt Action Priority. The methodology is documented in the AIAG-VDA FMEA Handbook (1st Edition, 2019), and modern FMEA tools like NirmIQ calculate both RPN and AP automatically.

For the full methodology including all 7 steps, structure analysis, and control plan generation, read The Complete Guide to AIAG-VDA FMEA. For the difference between design and process FMEA, see DFMEA vs PFMEA: When to Use Each.