Risk Priority Number (RPN) is the product of three ratings used in Failure Mode and Effects Analysis (FMEA): Severity (how bad is the effect of the failure?), Occurrence (how often is the failure cause expected to occur?), and Detection (how likely is the failure to be detected before reaching the customer?). Each factor is rated on a 1-10 scale, making RPN range from 1 (lowest risk) to 1,000 (highest risk). Teams set a threshold (commonly 100-200) above which corrective actions are required.
RPN has known limitations. Two failure modes with identical RPNs can have very different risk profiles: Severity=10, Occurrence=2, Detection=5 (RPN=100) represents a catastrophic failure mode with low occurrence, while Severity=2, Occurrence=10, Detection=5 (RPN=100) represents a minor nuisance that occurs frequently. Best practice is to always address any failure mode with Severity≥9 regardless of RPN, because the potential consequences are unacceptable even if occurrence is low.
The 2019 AIAG-VDA FMEA handbook introduced Action Priority (AP) to supplement or replace RPN-based prioritization. AP uses lookup tables that assign High, Medium, or Low priority based on the combination of S, O, and D ratings, ensuring that high-severity failure modes receive appropriate attention regardless of their calculated RPN. Many organizations have transitioned to AP for new FMEAs while maintaining RPN for legacy FMEAs to preserve comparability over time.
Practical Example
Motor driver FMEA: Failure mode 'Gate driver undervoltage lockout during startup,' Severity=7 (motor stall), Occurrence=4, Detection=6. RPN=168 — above threshold of 150. Corrective action: Add soft-start delay sequence in firmware. After corrective action: Occurrence=2, Detection=3. New RPN=42.
How SpecZero handles this
RPN-driven corrective actions in FMEA become design requirements in SpecZero. When an FMEA identifies a high-RPN failure mode, the corrective action — whether a design change, additional test, or protective feature — should be captured as a requirement to ensure it is implemented and verified.
Related terms
Failure Mode and Effects Analysis(FMEA)
A systematic method for identifying potential failure modes, their causes, their effects, and their risk priority.
Verification and Validation(V&V)
Verification confirms a design meets its specifications; validation confirms the product meets user needs.
Acceptance Criteria
The measurable conditions a system or component must meet to be considered complete and accepted.