StandardISO/IEC 17025 testing & calibration labs — diagnosis · documents · review · uncertainty
← labkitpro.com Academy

Academy › Practical guides › Quality tools

AIAG-VDA FMEA: why Action Priority replaced the RPN (and what to do differently)

The same RPN can hide two completely different risks. The AP table is a lookup, not a multiplication.

Updated 13 November 2026 · 7 min read · Written for working labs and quality teams

Short answer

In the AIAG-VDA 2019 FMEA handbook, Risk Priority Number (S × O × D) was replaced by Action Priority (AP): H, M or L is determined by looking up the combination of Severity, Occurrence and Detection in the official table. It is not a product and not a weighted score. The change exists because a high-severity failure with moderate occurrence and good detection can score the same RPN as a trivial but poorly detected one — while deserving completely different action.

On this page

  1. The worked example that killed RPN
  2. How to apply AP correctly
  3. Where AP fits in the seven-step method
  4. Where this goes wrong in practice
  5. Frequently asked

The worked example that killed RPN

Both rows score 120 under the old method, so an RPN threshold rule ("act on everything above 100") would treat them identically. Look up S/O/D in the AIAG-VDA AP table instead: (10, 4, 3) lands in the high-severity band and returns H, while (3, 4, 10) lands in the low-severity band and returns L — the same RPN, two completely different actions. That is the whole reason the multiplication was dropped.

A second flaw in RPN: it is not an ordinal scale. Gaps between products are uneven, many different S/O/D triples produce the same number, and a team can "improve" an RPN by shaving a point off Detection without reducing any real risk.

Failure modeSODRPN = S×O×DAP from the official table
Loss of braking function (safety, special characteristic)1043120H — action needed (or a documented justification)
Cosmetic scuff on a non-visible surface3410120L — monitoring may be enough

How to apply AP correctly

  1. Score S from the effect of the failure, on the team's agreed 1–10 scale. Severity belongs to the function and its consequence, not to how good your inspection is.
  2. Score O from the occurrence of the failure cause with the current prevention controls in place; score D from the current detection controls' ability to find the cause or failure mode before it escapes.
  3. Look up S/O/D in the official AP table to get H / M / L. Do not average, multiply or invent your own weighting — the table is the method.
  4. For H, take action or document why no action is possible; for M, actions should be considered; for L, monitoring may be enough. Some organisations and customers require action on every H — check the customer-specific requirements.
  5. Record the recommended action, owner, due date, evidence of completion and the re-scored S/O/D, then re-derive AP. An FMEA with no re-scored column is a snapshot, not a living document.

Practical note. Severity can only come down when the design or process function changes so the effect is less serious. Adding a camera, a sensor or a second inspection reduces Detection, not Severity. If a team reports a lower S after adding inspection, the scoring is wrong.

Where AP fits in the seven-step method

The AIAG-VDA method runs: planning & preparation → structure analysis → function analysis → failure analysis (failure chain of effect / mode / cause) → risk analysis (S, O, D, AP) → optimisation (actions and re-assessment) → results documentation. AP sits in risk analysis and drives optimisation; it is not a final grade for the part.

Product and process FMEAs are linked: special characteristics identified in the DFMEA must flow into the PFMEA and then into the control plan, with the corresponding control method and reaction plan. When a customer audit finds a "special characteristic" that exists in the FMEA but not on the control plan, the AP discussion is moot — the loop was never closed. IATF 16949 is published by the International Automotive Task Force, not by ISO, and its customer-specific requirements govern which FMEA reference edition applies.

Where this goes wrong in practice

Computing both AP and RPN and sorting by RPN anyway. This reintroduces exactly the problem AP was designed to remove.

Reducing Severity by improving detection controls, or re-scoring S to make an H row become M.

Filling the action column with "increase inspection" for every H row. For high-severity failure modes, prevention (design or process change) is the meaningful action.

Leaving the special-characteristics chain unclosed between DFMEA, PFMEA and control plan, or never re-scoring after an action is completed.

Quoting the AP table from memory. Use the published table in the handbook your customer requires; the H/M/L boundaries are specific combinations, not a formula.

Frequently asked

Is RPN still allowed under AIAG-VDA 2019?
The harmonised AIAG-VDA method uses Action Priority rather than RPN. Some customers, legacy internal procedures and older SAE J1739-based systems still ask for RPN — follow the customer-specific requirement and do not mix the two scoring systems in one analysis.

What do H, M and L actually mean?
They are action priorities, not risk rankings. H means action is needed (or a documented justification for no action), M means action should be considered, L means action could be taken or the risk may be accepted. The exact wording and any mandatory-action rule come from your customer-specific requirements.

Can a low-AP item still need action?
Yes. Very high severity, regulatory requirements, special characteristics and customer-specific requirements can mandate action regardless of the AP letter. AP is a prioritisation tool inside the FMEA, not a substitute for those obligations.

Does ISO 9001:2026 require FMEA?
No. FMEA is not an ISO 9001 requirement; it is expected through IATF 16949 and automotive customer-specific requirements, and used voluntarily elsewhere as a risk-based-thinking tool.

Score it with the real table

Build a DFMEA / PFMEA with the official H/M/L Action Priority

Enter S, O and D for each row and the tool returns the AIAG-VDA Action Priority from the published lookup table — alongside RPN for legacy comparison, so you can see exactly where the two methods disagree.

Open the free FMEA tool →

Runs in your browser. Export the report free. No sign-up needed.

LabKitPro guides are written from published standards and accreditation-body documents — references, clause numbers and paraphrased intent only, never verbatim standard text. They are for preparation and study, not a certification or accreditation decision, and not legal advice. ISO standards are trademarks of ISO; IATF 16949 is published by the International Automotive Task Force and is not an ISO standard. The current laboratory standard is ISO/IEC 17025:2017; there is no 2025 edition. Global ACI replaced IAF and ILAC on 1 January 2026.

Academy by standard · All practical guides · Free browser tools