RPN & Action Priority Calculator (FMEA)
Prioritize FMEA failure modes with AIAG-VDA 2019 Action Priority (RPN shown for reference). AIAG-VDA 2019 replaced RPN thresholds with the Action Priority (AP)…
AIAG-VDA 2019 replaced RPN thresholds with the Action Priority (AP) matrix — a High/Medium/Low priority from Severity, Occurrence, and Detection band lookup. RPN (S×O×D) is still shown for reference.
What is Action Priority (AP) in FMEA, and how does it relate to RPN?
Action Priority (AP) is the AIAG & VDA FMEA Handbook (2019) method for ranking failure modes. Instead of multiplying Severity (S), Occurrence (O), and Detection (D) into a single Risk Priority Number (RPN) and comparing it to a threshold, AP looks up S, O, and D independently in banded reference tables and assigns a High (H), Medium (M), or Low (L) priority directly from the combination of bands.
Severity rates the impact of the failure on the customer (10 = hazardous without warning). Occurrence rates the likelihood of the failure cause occurring (10 = almost certain). Detection rates the ability of current controls to catch the failure before it reaches the customer (10 = no detection capability). Each factor is still rated 1-10, but AP groups the ratings into bands (for example Severity 7-8, Occurrence 2-3, Detection 2-4) before consulting the AP table — a high Severity rating can drive a High priority even when the multiplied RPN is unremarkable.
RPN threshold prioritization — treating any RPN above 100 or 125 as an automatic trigger for action — is the older, now-deprecated practice from the AIAG 4th Edition FMEA manual. It is unreliable because the same RPN value can hide very different risk profiles (S=10, O=10, D=1 vs. S=5, O=4, D=5). This calculator computes and displays AP as the primary result; RPN is shown only as a secondary reference number, not as the basis for prioritization.
Formula: AP = lookup(Severity band, Occurrence band, Detection band) -> H | M | L RPN (reference) = Severity x Occurrence x Detection Severity (S): 1-10 scale Occurrence (O): 1-10 scale Detection (D): 1-10 scale
Example Calculation
A brake pad wear failure mode: Severity = 8 (loss of braking performance), Occurrence = 3 (low probability with current materials), Detection = 4 (inspection catches most issues). The AP table returns Low priority for this Severity/Occurrence/Detection band combination — even though RPN = 8 x 3 x 4 = 96 looks close to the old 100 threshold, AP shows the true priority is Low because Occurrence and Detection are both well-controlled.
When to Use This Calculator
- During DFMEA sessions when the design team needs to prioritize potential failure modes in a new product design using the current AIAG-VDA Action Priority method
- During PFMEA reviews to evaluate and rank process risks before production launch or after a process change
- When allocating limited engineering resources — Action Priority ranking helps focus corrective actions on the failure modes the standard actually classifies as High first, not just the ones with the highest RPN
- After implementing a corrective action to recompute AP (and RPN for reference) and verify that the priority has dropped to Medium or Low
- During customer or regulatory audits when demonstrating AP-based risk assessment per the AIAG & VDA FMEA Handbook (2019)
Common Mistakes to Avoid
- Using the RPN threshold rule (e.g., >100) to decide on action instead of Action Priority — this is the deprecated AIAG 4th Edition practice; AIAG-VDA 2019 replaced it because the same RPN can hide very different risk profiles
- Ignoring a High Action Priority because the reference RPN looks low — a high Severity rating alone can drive AP to High even when Severity x Occurrence x Detection is unremarkable
- Inflating Detection scores to lower RPN or shift AP without actually improving detection capability — this gaming reduces the number on paper but does nothing to reduce real risk
- Treating Severity, Occurrence, and Detection as a mathematical formula without team consensus — each rating should be discussed and agreed upon by a cross-functional team, not assigned by one person
- Not documenting the rationale behind each Severity/Occurrence/Detection rating — without documented reasoning, future teams cannot understand or update the FMEA effectively
- Failing to re-evaluate Action Priority after corrective actions — the FMEA is a living document; updated ratings confirm whether the action truly reduced priority
How to Interpret Results
- Action Priority: Low (L) — document the current controls and rating; no further action needed unless Severity alone is high (9 or 10)
- Action Priority: Medium (M) — review recommended; evaluate whether additional controls are justified based on team judgment
- Action Priority: High (H) — action required; identify the root cause and implement corrective and preventive controls, then re-evaluate
- RPN (reference) — shown alongside AP for continuity with legacy FMEA records, but it is not the basis for the priority decision
- Any Severity = 9 or 10 regardless of AP or RPN — safety-critical failure modes warrant close review; the AP table already accounts for this by weighting high-Severity bands toward High priority
Related Standards & References
- AIAG & VDA FMEA Handbook (2019) — joint standard introducing the Action Priority (AP) methodology as the primary prioritization method, replacing RPN threshold ranking from the AIAG 4th Edition
- SAE J1739 — recommended practice for design and process FMEA in automotive and heavy-vehicle applications
- IEC 60812 — international standard for FMEA methodology applicable across all industries
- IATF 16949:2016 §8.3.5.1 — automotive quality requirement mandating DFMEA and PFMEA for all new products and processes
Frequently Asked Questions
Which result should I act on, AP or RPN?
Act on Action Priority (AP). It is the current AIAG-VDA 2019 standard method and evaluates Severity, Occurrence, and Detection band combinations directly rather than collapsing them into a single multiplied number. RPN is shown for reference and backward compatibility with legacy FMEA records, but it should not be used as the sole prioritization criterion — the deprecated "RPN > 100 means act" rule can rank a high-Severity, well-detected failure mode below a low-Severity, poorly-detected one that happens to share the same RPN.
Why did AP replace RPN thresholds?
The same RPN value can represent very different risk profiles: S=10, O=10, D=1 (a hazardous, almost-certain, but easily detected failure) multiplies to RPN=100, the same as S=5, O=4, D=5 (a moderate, less likely, less detectable failure). A single numeric threshold cannot distinguish these cases. AIAG-VDA 2019 replaced the threshold with AP tables that look up Severity, Occurrence, and Detection bands independently, so a high Severity rating alone can drive a High action priority regardless of the multiplied RPN.
What is the difference between FMEA and FMECA?
FMEA identifies failure modes and their effects. FMECA (Failure Mode, Effects, and Criticality Analysis) adds a criticality analysis step that quantifies failure probability and severity in a more rigorous way using MIL-STD-1629A methodology. FMEA with AP/RPN is more common in automotive and manufacturing; FMECA is used in aerospace, defense, and nuclear industries.