FMECA (Failure Mode, Effects, and Criticality Analysis)

What Is FMECA?

FMECA is an analytical method used by reliability engineers and maintenance managers to systematically examine a system, identify every potential failure mode, determine what effect each failure has on overall system function, and calculate a Criticality Number that ranks failure modes by their combined probability and consequence.

The method was developed in the 1940s by the U.S. military as a tool for evaluating weapons systems. It was later codified in MIL-STD-1629A and adopted across aerospace, nuclear, and medical device sectors. Today it is applied in any industry where failure consequences are severe enough to warrant formal, quantified risk prioritisation.

Where FMEA asks "what can go wrong and what happens if it does?", FMECA asks the additional question: "how critical is each failure mode relative to all others?" That additional step transforms a long list of failure modes into a ranked, actionable hierarchy that maintenance and engineering teams can work through in order of risk.

FMECA vs FMEA: Key Differences

FMEA and FMECA are closely related. FMECA is best understood as FMEA with a formal criticality analysis layer added on top. The table below shows where they align and where they diverge.

How Criticality Analysis Works: The Criticality Number Formula

The criticality analysis component of FMECA assigns each failure mode a Criticality Number (Cm). This number is calculated using the formula defined in MIL-STD-1629A:

Cm = β × α × λ_p × t

Each term in the formula has a specific meaning:

• β (beta): The conditional probability that the failure mode will cause the identified critical effect. Values range from 0 to 1. A value of 1.0 means the failure mode always produces the stated effect; 0.1 means it does so in 10% of cases.
• α (alpha): The failure mode ratio, which represents the fraction of all failures for that component attributable to this specific failure mode. All failure mode ratios for a component should sum to 1.0.
• λ_p (lambda-p): The part failure rate, typically expressed in failures per million hours. Values are sourced from reliability handbooks (such as MIL-HDBK-217), manufacturer data, or field history.
• t: The operating duration being analysed, expressed in hours or mission cycles.

A higher Cm indicates a failure mode that demands immediate attention. Teams plot all failure modes on a criticality matrix, with severity categories on one axis and Cm values on the other. Failure modes in the upper-right quadrant (high severity, high criticality number) receive the highest priority for corrective action.

When quantitative failure rate data is unavailable, MIL-STD-1629A also provides a qualitative approach that uses probability level categories (frequent, reasonably probable, occasional, remote, extremely unlikely) to assign relative criticality rankings without numerical calculation.

MIL-STD-1629A: The Governing Standard

MIL-STD-1629A, "Procedures for Performing a Failure Mode, Effects, and Criticality Analysis," is the foundational document for FMECA. Originally published by the U.S. Department of Defense and last formally revised in 1980, it remains the primary reference for FMECA methodology in defence, aerospace, and many adjacent industries.

The standard defines two analysis tasks:

• Task 101 (FMEA): The qualitative identification of failure modes and their effects on system and mission success, divided into hardware and functional FMEA approaches.
• Task 102 (Criticality Analysis): The quantitative extension that calculates Criticality Numbers and produces the criticality matrix for prioritisation.

MIL-STD-1629A also defines severity categories that classify the consequence of each failure effect:

NASA applies similar methodology through its own guidelines (NASA SP-2016-6119), and civil aviation programmes reference FMECA within the broader framework of SAE ARP4761, which governs aircraft system safety assessments.

FMECA Worksheet Structure

The FMECA worksheet is the primary working document. Each row represents a single failure mode for a specific component. A complete worksheet contains the following columns:

The completed worksheet feeds into the criticality matrix, where each failure mode is plotted by severity category and Criticality Number to create a visual risk map for the system.

When to Use FMECA

FMECA is the right choice in the following situations:

• Prioritisation is required. When the number of identified failure modes exceeds the team's capacity to address all of them, the Criticality Number provides an objective ranking to guide resource allocation.
• Regulatory documentation demands it. Defence contracts (MIL-STD-1629A), nuclear safety cases, and medical device regulatory submissions often require a formal FMECA as part of the safety evidence package.
• High consequence of failure. Systems where a single failure mode can cause loss of life, mission failure, or catastrophic environmental damage warrant the additional effort of full criticality quantification.
• New system design. FMECA applied during the design phase can identify high-criticality failure modes early enough to change architecture, add redundancy, or specify more reliable components before production.
• Maintenance strategy development. When combined with reliability centred maintenance, FMECA output identifies which components require condition monitoring, scheduled replacement, or on-condition tasks based on their criticality rankings.

Standard FMEA is sufficient when the objective is simply to document failure modes and their effects without the need for quantified prioritisation. Use FMECA when ranking and justifying corrective actions matters.

Steps to Conduct an FMECA

Step 1: Define the Scope and Indenture Level

Establish which system, subsystem, or assembly is being analysed. Choose the indenture level (the depth of decomposition: system, subsystem, assembly, component) at which the analysis will be performed. Define the operating modes (normal operation, startup, shutdown, emergency) that will be covered.

Step 2: Develop the System Block Diagram

Create a functional block diagram showing how system elements interact. This diagram defines the boundaries of the analysis and ensures every function is linked to at least one hardware item. Reliability block diagrams may also be used to map dependencies and redundancies.

Step 3: Identify All Failure Modes

For each item at the chosen indenture level, list every conceivable failure mode. Common sources include engineering judgement, reliability databases, historical maintenance records, field failure reports, and FRACAS data. Each failure mode must be described in functional terms (e.g. "fails open," "fails closed," "intermittent output").

Step 4: Analyse Effects and Assign Severity

Trace each failure mode through three levels of effect: local effect (impact on the item itself), next higher effect (impact on the assembly or subsystem), and end effect (impact on the overall system or mission). Assign the MIL-STD-1629A severity category (I through IV) based on the worst-case end effect.

Step 5: Collect Failure Rate Data

Source the part failure rate (λ_p) for each component from approved reliability data sources: MIL-HDBK-217F for electronic components, NSWC-11 for mechanical components, manufacturer qualification data, or validated field history. Assign failure mode ratios (α) based on historical data or engineering judgement, ensuring they sum to 1.0 per component.

Step 6: Calculate Criticality Numbers

For each failure mode, assign the conditional probability (β) based on the likelihood that the failure mode produces the identified end effect. Apply the formula Cm = β × α × λ_p × t to calculate each Criticality Number. Aggregate all Criticality Numbers for a given severity category to produce the Item Criticality Number for each component.

Step 7: Build the Criticality Matrix

Plot each failure mode on a criticality matrix with severity categories on the vertical axis and the Criticality Number (or probability level for qualitative analysis) on the horizontal axis. Failure modes in the upper-right region of the matrix require immediate corrective action.

Step 8: Define and Implement Corrective Actions

For every failure mode in the high-criticality region, define a corrective action. Options include design changes (adding redundancy, changing materials, improving tolerances), maintenance task additions (increasing inspection frequency, adding condition monitoring), changes to operating procedures, or acceptance of residual risk with documented rationale.

Step 9: Re-evaluate and Document

After corrective actions are implemented, reassess the Criticality Numbers to verify risk has been reduced to acceptable levels. Maintain the FMECA as a living document that is updated when design changes are made, new failure data becomes available, or operating conditions change.

Industries That Require FMECA

Aerospace and Defence

FMECA is contractually required on virtually all U.S. military hardware programmes under MIL-STD-1629A. It is also embedded in civil aviation safety assessment through SAE ARP4761, which applies to aircraft systems and equipment. Every failure mode with a Category I or II end effect must have corrective actions documented and verified before a system can achieve airworthiness certification or programme acceptance.

Nuclear Power

Nuclear facilities use FMECA as part of their probabilistic safety assessment processes. The criticality analysis component supports the formal safety case by demonstrating that the probability and consequence of safety-relevant failure modes are within regulatory limits. Results feed directly into the maintenance rule and surveillance testing programmes.

Medical Devices

ISO 14971 (Risk Management for Medical Devices) requires manufacturers to identify hazards, estimate risk, and demonstrate risk reduction. FMECA provides the structured framework to meet these requirements, and the criticality matrix maps directly to the risk acceptability criteria defined in the device's risk management file.

Oil, Gas, and Process Industries

High-consequence process plants use FMECA alongside HAZOP and fault tree analysis to satisfy process safety management requirements. FMECA is particularly useful for analysing rotating equipment and safety instrumented systems where individual component failure modes must be ranked to inform test intervals and preventive maintenance task selection.

Rail and Mass Transit

EN 50126 (RAMS for railway applications) and EN 50128/50129 reference FMECA as part of the safety and reliability demonstration process for rolling stock, signalling systems, and infrastructure. Rail operators apply FMECA during both new build programmes and fleet life-extension studies.

Benefits of FMECA

• Objective prioritisation. The Criticality Number removes subjectivity from decisions about which failure modes to address first. Teams can justify resource allocation with numerical evidence.
• Optimised maintenance strategy. FMECA output identifies which assets genuinely require intensive monitoring or short task intervals and which can safely be maintained less frequently, reducing unnecessary maintenance cost.
• Design improvement before production. When applied during the design phase, FMECA reveals high-criticality failure modes while design changes are still inexpensive to implement.
• Regulatory and contractual compliance. A completed FMECA provides the documented evidence required by MIL-STD-1629A, ISO 14971, nuclear safety cases, and other regulatory frameworks.
• Spare parts planning. Components with high Criticality Numbers for Category I or II effects are prime candidates for maintained stock levels, ensuring parts are available when a high-priority failure occurs.
• Foundation for RAM analysis. The failure rate and severity data developed during FMECA feed directly into reliability, availability, and maintainability modelling.
• Support for risk-based maintenance. FMECA provides the quantified risk foundation that risk-based maintenance programmes require to assign inspection intervals and maintenance tasks proportionate to actual risk.

FMECA and Related Analysis Methods

FMECA does not operate in isolation. It is one of several complementary analytical tools used in reliability engineering programmes:

• Fault Tree Analysis (FTA) takes a top-down approach, starting from an undesired event and tracing all combinations of failures that could cause it. FMECA is bottom-up (starting from component failure modes). The two methods are complementary and are often used together on complex systems.
• Root Cause Analysis (RCA) investigates failures that have already occurred. FMECA is prospective and investigates failures that could occur.
• Failure Lifecycle Management tracks how assets degrade over time, using the P-F curve to plan interventions. FMECA defines which failure modes on that curve are most critical to monitor.
• Failure Prediction Models use sensor data to forecast when specific failure modes will occur. FMECA identifies which failure modes justify the investment in predictive monitoring.
• PFMEA (Process FMEA) applies the same methodology to manufacturing and process steps rather than hardware components. Organisations sometimes run both PFMEA and hardware FMECA in parallel on the same programme.

Common Challenges in FMECA

Availability of Failure Rate Data

The quantitative criticality analysis requires part failure rates (λ_p). When reliable field data or manufacturer data is unavailable, teams must use generic handbook values (MIL-HDBK-217F, NSWC-11), which may not accurately reflect the actual operating environment. Sensitivity analysis should be performed to understand how uncertainty in failure rate data affects the criticality rankings.

Scope Creep and Analysis Depth

FMECA can become extremely large when applied to complex systems without clear boundaries. Defining the indenture level and scope at the outset and resisting the temptation to decompose every element to piece-part level are essential to keeping the analysis manageable and useful.

Keeping the Document Current

A completed FMECA quickly becomes outdated if design changes, operating condition changes, or new failure data are not fed back into the analysis. Organisations that treat FMECA as a one-time deliverable rather than a living document lose most of its long-term value. Integrating FMECA reviews into the engineering change process solves this problem.

Team Competency

FMECA requires multidisciplinary input: reliability engineers for data and calculations, design engineers for system knowledge, and maintenance engineers for operational insight. Gaps in any discipline produce an incomplete or inaccurate analysis. Cross-functional facilitation is a prerequisite for a high-quality FMECA.

Frequently Asked Questions

The Bottom Line

FMECA adds the quantitative rigor of criticality ranking to FMEA's qualitative failure mode identification. By calculating criticality numbers and plotting them against severity, it gives maintenance and reliability engineers a defensible, data-driven basis for prioritizing which failure modes to address first, which assets need the most robust maintenance strategies, and where design changes or redundancy would reduce unacceptable risk.

FMECA is most valuable as a living document that is updated as failure data accumulates. Initial criticality rankings are based on estimates and engineering judgment; actual failure rate data from CMMS records and field analysis progressively refines those estimates into accurate predictions. Organizations that feed real failure history back into their FMECA analyses build increasingly reliable predictive models for their asset portfolios over time.