Risk-Based Failure Mode and Effects Analysis (RBFMEA)
Risk-Based Failure Mode and Effects Analysis · Also known as: RBFMEA, Risk-based FMEA, Risk-prioritised FMEA, Quantitative FMEA
Risk-based failure mode and effects analysis (RBFMEA) is a structured engineering technique that identifies every way a system or process can fail, assesses the risk of each failure mode using a numerical Risk Priority Number (RPN = Occurrence × Severity × Detectability), and prioritises corrective actions accordingly. Rooted in MIL-STD-1629A and standardised in IEC 60812:2018, it is the dominant proactive reliability and safety tool in aerospace, automotive, pharmaceutical, and manufacturing industries.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
+2 more
When to use it
Use RBFMEA during the design or process development phase, before a product enters production or a process goes live, when proactive identification of failure risks is possible. It is particularly powerful in safety-critical domains (aerospace, medical devices, automotive) and any context governed by regulatory requirements (FDA 21 CFR, IATF 16949, ISO 13485). It is also used retrospectively after a field failure to prevent recurrence. Do not use RBFMEA as a substitute for physics-of-failure analysis when failure mechanisms are unknown or highly complex — in those cases, accelerated life testing or fault tree analysis may be needed first. It is also inappropriate when failure data are too sparse to score Occurrence meaningfully.
Strengths & limitations
- Provides a structured, auditable record of proactive risk identification that satisfies regulatory and customer quality-system requirements.
- The RPN score enables objective prioritisation of limited engineering resources on the highest-risk failure modes.
- Cross-functional team involvement transfers knowledge and builds shared ownership of reliability outcomes.
- Living document: the FMEA can be updated throughout the product lifecycle as design changes, field data, or process improvements occur.
- Flexible and scalable — applicable from a single component to a complex system, and across hardware, software, and process domains.
- RPN arithmetic can be misleading: a failure mode with S=10, O=1, D=1 (RPN=10) is potentially more dangerous than one with S=3, O=3, D=3 (RPN=27), yet scores lower.
- Score ratings depend heavily on expert judgment and team consensus; results are not fully objective or reproducible across different teams.
- FMEA assumes single-point failures and does not inherently capture multi-failure interactions or common-cause failures — fault tree analysis is needed for those.
- Maintaining the FMEA as a living document requires sustained effort; outdated FMEAs misrepresent actual risk profiles.
Frequently asked
How is Risk-based FMEA different from standard FMEA?
Classical FMEA identifies failure modes and their effects without necessarily quantifying risk. Risk-based FMEA explicitly calculates a Risk Priority Number (RPN = Occurrence × Severity × Detectability) for each failure mode, enabling objective ranking and prioritisation of corrective actions. Modern standards such as IEC 60812:2018 and AIAG-VDA FMEA (5th ed.) embed risk quantification as a core step, making virtually all contemporary FMEA practice risk-based.
What is a good RPN threshold for action?
There is no universal threshold; it depends on the industry, product risk class, and organisational risk tolerance. A common practice is to act on the top 20% of RPNs, or to set a threshold such as RPN > 100 or RPN > 125. More importantly, any failure mode with a Severity score of 9 or 10 (safety or regulatory impact) must be addressed regardless of overall RPN.
Can FMEA replace fault tree analysis?
No — they are complementary. FMEA is a bottom-up, inductive method: it starts with individual failure modes and traces their effects upward. Fault tree analysis (FTA) is a top-down, deductive method: it starts with an undesired top event and identifies combinations of lower-level failures that could cause it. FMEA is better for comprehensive failure cataloguing; FTA is better for analysing how multiple failures interact to cause a critical event.
What team size is recommended for an FMEA?
Typically four to eight cross-functional experts: design or process engineers who understand the failure mechanisms, manufacturing or operations staff who know real-world process variation, quality engineers familiar with detection controls, and a subject-matter expert on customer or regulatory requirements. Larger teams risk losing focus; smaller teams risk missing important failure modes.
How often should an FMEA be updated?
Whenever a design change, process change, or field failure occurs that could affect any of the failure modes, effects, or controls documented in the FMEA. Many organisations also schedule periodic reviews (e.g., annually) to ensure the document remains current. An FMEA that is not updated is a compliance artifact, not a living risk-management tool.
Sources
- International Electrotechnical Commission. (2018). IEC 60812:2018 — Failure modes and effects analysis (FMEA and FMECA). IEC. link ↗
- Stamatis, D. H. (2003). Failure Mode and Effect Analysis: FMEA from Theory to Execution (2nd ed.). ASQ Quality Press. ISBN: 978-0873895989
How to cite this page
ScholarGate. (2026, June 3). Risk-Based Failure Mode and Effects Analysis. ScholarGate. https://scholargate.app/en/experimental-design/risk-based-failure-mode-and-effects-analysis
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- Failure Mode and Effects AnalysisExperimental design↔ compare
- Fault Tree AnalysisReliability↔ compare
- Reliability AnalysisReliability↔ compare
- Risk-based fault tree analysisExperimental design↔ compare
- Six Sigma DMAICQuality Management↔ compare
- Statistical Process ControlExperimental design↔ compare