Study guide

8.2 Failure Mode and Effects Analysis (FMEA/FMECA)

PECB Certified ISO 31000 Risk Manager Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Principles and Core Concepts of ISO 31000

1.1 ISO 31000 Overview, Purpose, and Scope 1.2 Core Risk Terminology and Definitions 1.3 The 8 ISO 31000:2018 Risk Management Principles 1.4 The Risk Management Standards Landscape and PECB Exam Structure 1.5 Comparing ISO 31000 with COSO ERM, NIST RMF, and Sector Frameworks 1.6 Risk Categories and Risk Management vs. Risk Assessment

2 Chapter 2: Enterprise Risk Governance and Leadership

2.1 Leadership and Top Management Commitment 2.2 Integrating Risk Management into Organizational Governance 2.3 Building a Risk-Aware Culture and the Three Lines Model

3 Chapter 3: Designing and Implementing the Risk Framework

3.1 Framework Design and Context Analysis 3.2 Framework Implementation and Resource Allocation 3.3 Framework Evaluation and Continual Improvement 3.4 The Risk Management Plan and Framework Documentation Architecture

4 Chapter 4: Establishing Context and Risk Identification

4.1 Communication and Stakeholder Consultation 4.2 Defining Scope, Context, and Risk Criteria 4.3 Risk Identification Methods and Risk Register Construction 4.4 The Consultation Process, Communication Principles, and Risk Escalation 4.5 Asset Identification and Evaluation of Existing Controls

5 Chapter 5: Risk Analysis, Evaluation, and Decision Making

5.1 Risk Analysis: Assessing Likelihood, Consequence, and Controls 5.2 Risk Evaluation and Prioritization 5.3 Inherent Risk vs. Residual Risk and Risk Aggregation

6 Chapter 6: Risk Treatment, Monitoring, and Reporting

6.1 The Seven ISO 31000 Risk Treatment Options 6.2 Designing and Implementing Risk Treatment Plans 6.3 Monitoring, Review, Recording, and Reporting Systems

7 Chapter 7: Qualitative and Scenario Risk Assessment Techniques (IEC 31010)

7.1 IEC 31010 Framework and Selection Criteria 7.2 Qualitative Techniques: Delphi, SWIFT, HAZOP, and Brainstorming 7.3 Root Cause Analysis (RCA), Fishbone, and 5 Whys

8 Chapter 8: Quantitative and Predictive Risk Assessment Techniques (IEC 31010)

8.1 Bow-Tie Analysis: Cause and Consequence Diagramming 8.2 Failure Mode and Effects Analysis (FMEA/FMECA) 8.3 Fault Tree Analysis (FTA) vs. Event Tree Analysis (ETA) 8.4 Advanced Quantitative Methods: Monte Carlo, Decision Trees, and LOPA

8.2 Failure Mode and Effects Analysis (FMEA/FMECA)

Key Takeaways Explain This Topic AI

FMEA is a bottom-up, inductive hazard identification technique used to analyze component failure modes, failure mechanisms, and their local and end effects.

The Risk Priority Number (RPN) is calculated as the product of Severity (S), Occurrence (O), and Detection (D), ranging from 1 to 1,000.

Relying solely on RPN thresholds can obscure high-severity critical risks; ISO 31000 best practices mandate prioritizing high Severity (S >= 8) regardless of total RPN.

FMECA extends FMEA by incorporating quantitative Criticality Analysis (Cm = alpha * beta * lambda_p * t) to map failures on a semi-quantitative Criticality Matrix.

Last updated: July 2026

8.2 Failure Mode and Effects Analysis (FMEA/FMECA)

Standardized under IEC 60812 and referenced in IEC 31010 , Failure Mode and Effects Analysis (FMEA) is a rigorous, inductive, bottom-up quantitative and qualitative risk assessment technique. Originally developed by the military (MIL-STD-1629A) and extensively adopted across aerospace, automotive, manufacturing, and healthcare sectors, FMEA provides a systematic process for identifying how equipment, software, or business processes can fail, evaluating the operational impacts of those failures, and prioritizing corrective actions.

When quantitative failure rate data is integrated with severity ratings, the technique expands into Failure Mode, Effects, and Criticality Analysis (FMECA) .

1. System Decomposition and Methodology

FMEA begins with system decomposition. Analysts break a complex process or system down into subsystems, assemblies, and individual functional components. For each component, the team systematically evaluates four core dimensions:

Item / Function : The intended operation of the component within the system.

Failure Mode : The specific physical or operational manner in which the component fails to perform its intended function (e.g., failure to open, short circuit, software memory leak, seal leakage).

Failure Mechanism & Cause : The underlying physical, chemical, or operational driver causing the failure (e.g., thermal fatigue, oxidation, input validation failure).

Failure Effects : The consequences of the failure mode across three hierarchical tiers:

Local Effect : Impact restricted directly to the specific component.

Next Higher Level Effect : Impact on the immediate assembly or sub-system.

End Effect : Impact on the total system, end-user, environment, or enterprise safety.

2. The FMEA Scoring Framework: Severity, Occurrence, and Detection

To quantify risk, FMEA assigns standardized numerical scores ranging from 1 to 10 across three distinct risk parameters:

Severity ( S S S )

Measures the intensity of the worst-case End Effect of a failure mode on the system or user.

1 (Negligible) : No discernible effect on system performance or safety.

4 to 6 (Moderate) : System performance degraded; minor downtime or customer dissatisfaction.

9 to 10 (Catastrophic) : High safety hazard, regulatory non-compliance, or total system destruction occurring without prior warning.

Occurrence ( O O O )

Measures the estimated frequency or probability that a specific failure mode will occur during the planned operational lifespan of the system.

1 (Extremely Remote) : Probability < 1 in 1 , 500 , 000 < 1 \text{ in } 1,500,000 < 1 in 1 , 500 , 000 operating cycles ( < 10 − 6 < 10^{-6} < 1 0 − 6 ).

5 (Moderate) : Occasional failures; approximately 1 in 2 , 000 1 \text{ in } 2,000 1 in 2 , 000 operating cycles.

10 (Almost Inevitable) : High failure rate; > 1 in 2 > 1 \text{ in } 2 > 1 in 2 operating cycles.

Detection ( D D D )

Measures the capability of existing internal controls, automated diagnostic monitors, or inspection procedures to detect the failure mode before the component is deployed or before the End Effect manifests.

1 (Certain Detection) : Automated, 100% fail-safe inline diagnostic detection.

5 (Moderate Detection) : Manual inspection or periodic testing with moderate detection likelihood.

10 (Absolute Uncertainty) : No control mechanism exists; failure mode is completely undetectable until catastrophic failure occurs.

3. Risk Priority Number (RPN) Calculation and Limitations

The fundamental metric generated by an FMEA is the Risk Priority Number (RPN) , calculated as the mathematical product of Severity, Occurrence, and Detection: RPN = S × O × D \text{RPN} = S \times O \times D RPN = S × O × D

Because each factor ranges from 1 to 10, the RPN spans a dynamic scale from 1 to 1,000 .

Mathematical Comparison and RPN Pitfalls

A common error in enterprise risk management is using an arbitrary RPN threshold (e.g., "remediate only items with RPN > 120 \text{RPN} > 120 RPN > 120 ") as the sole criterion for corrective action. Relying solely on RPN can mask critical safety hazards due to mathematical non-uniqueness:

Consider two distinct component failure modes:

Failure Mode Alpha : S = 10 , O = 2 , D = 6 ⟹ RPN = 10 × 2 × 6 = 120 S = 10, O = 2, D = 6 \implies \text{RPN} = 10 \times 2 \times 6 = 120 S = 10 , O = 2 , D = 6 ⟹ RPN = 10 × 2 × 6 = 120

Failure Mode Beta : S = 4 , O = 5 , D = 6 ⟹ RPN = 4 × 5 × 6 = 120 S = 4, O = 5, D = 6 \implies \text{RPN} = 4 \times 5 \times 6 = 120 S = 4 , O = 5 , D = 6 ⟹ RPN = 4 × 5 × 6 = 120

Although both yield an identical RPN of 120, Failure Mode Alpha represents a potential catastrophic fatality ( S = 10 S = 10 S = 10 ), whereas Failure Mode Beta represents a moderate operational inconvenience ( S = 4 S = 4 S = 4 ). ISO 31000 best practices mandate that any item with a high Severity score ( S ≥ 8 S \ge 8 S ≥ 8 ) must receive mandatory risk treatment and engineering re-design regardless of how low its Occurrence or Detection scores might be.

4. FMECA: Quantitative Criticality Analysis

Failure Mode, Effects, and Criticality Analysis (FMECA) enhances basic FMEA by adding quantitative failure rate calculations to build a rigorous Criticality Index .

Failure Mode Criticality ( C m C_m C m ​ )

The criticality metric for a specific failure mode ( C m C_m C m ​ ) is calculated using component failure rate data: C m = α × β × λ p × t C_m = \alpha \times \beta \times \lambda_p \times t C m ​ = α × β × λ p ​ × t

where:

α \alpha α = Failure Mode Ratio : The fraction of the total component failure rate attributed to this specific failure mode (where ∑ α i = 1.0 \sum \alpha_i = 1.0 ∑ α i ​ = 1.0 ).

β \beta β = Conditional Probability of Loss : The conditional probability that the failure mode will actually result in the identified End Effect (ranging from 0 to 1.0).

λ p \lambda_p λ p ​ = Part Failure Rate : The total failure rate of the component (typically failures per million operating hours, 10 − 6 hrs 10^{-6} \text{ hrs} 1 0 − 6 hrs ).

t t t = Operating Time : The total operational mission duration (in hours).

Worked FMECA Calculation

A critical cooling pump seal operates continuously for one year ( t = 8 , 760 hours t = 8,760 \text{ hours} t = 8 , 760 hours ).

Total Part Failure Rate ( λ p \lambda_p λ p ​ ): 20 failures per 10 6 hours = 2.0 × 10 − 5 failures/hour 20 \text{ failures per } 10^6 \text{ hours} = 2.0 \times 10^{-5} \text{ failures/hour} 20 failures per 1 0 6 hours = 2.0 × 1 0 − 5 failures/hour .

Failure Mode under evaluation: Fluid Seal Leakage.

Failure Mode Ratio ( α \alpha α ): 0.35 0.35 0.35 (35% of pump failures are seal leaks).

Conditional Loss Probability ( β \beta β ): 0.80 0.80 0.80 (80% of seal leaks lead to total pump shutdown).

Calculating C m C_m C m ​ : C m = 0.35 × 0.80 × ( 2.0 × 10 − 5 ) × 8 , 760 C_m = 0.35 \times 0.80 \times (2.0 \times 10^{-5}) \times 8,760 C m ​ = 0.35 × 0.80 × ( 2.0 × 1 0 − 5 ) × 8 , 760 C m = 0.28 × 0.00002 × 8760 = 0.049056 C_m = 0.28 \times 0.00002 \times 8760 = 0.049056 C m ​ = 0.28 × 0.00002 × 8760 = 0.049056

This quantified criticality index ( C m = 4.91 × 10 − 2 C_m = 4.91 \times 10^{-2} C m ​ = 4.91 × 1 0 − 2 ) allows risk engineers to plot the failure mode precisely on a quantitative Criticality Matrix (plotting Probability/Frequency against Severity) to justify safety investments to executive leadership.

Loading diagram... FMEA/FMECA Iterative Execution Lifecycle

Representative FMEA Worksheet

The table below illustrates a standard FMEA operational worksheet tracking baseline scoring, recommended engineering controls, and post-treatment re-evaluations:

Item / Function Failure Mode End Effect Baseline S Baseline O Baseline D Baseline RPN Recommended Action Revised S Revised O Revised D Revised RPN

Fuel Injection Valve Nozzle Clogging Engine stalling & total power loss 9 4 7 252 Install dual redundant inline filters & pressure sensor 9 1 2 18

Data Ingestion API Buffer Overflow System crash & data corruption 8 5 6 240 Implement input sanitization & rate limiting 8 2 2 32

Backup Generator Battery Failure Failure to auto-start during blackouts 7 6 5 210 Weekly automated self-test & bi-annual replacement 7 2 2 28