What does the C in FMECA stand for?

Criticality. FMECA is failure mode, effects, and criticality analysis. The criticality analysis is a specific added step, defined in MIL-STD-1629A, that ranks each failure mode by the combined influence of severity and probability of occurrence, rather than a fancier version of the same FMEA work.

How do you calculate a criticality number?

The MIL-STD-1629A mode criticality number is Cm = beta times alpha times part failure rate lambda-p times operating time t. Beta is the conditional probability the failure effect occurs, alpha is the mode's share of the part's failures, lambda-p is the part failure rate, and t is operating time. Summing Cm across a part's modes gives its item criticality.

Is FMECA better than FMEA?

Not better, more. FMECA adds a criticality ranking that is worth its extra effort when failures carry severe consequences and you have credible failure-rate data to defend the ranking. For lower-consequence work, or where you lack failure-rate data, a plain FMEA with RPN or Action Priority is proportionate. A thorough FMEA beats a rushed FMECA.

What is the difference between qualitative and quantitative FMECA?

Qualitative FMECA plots each failure mode on a criticality matrix of severity versus probability and reads the high-criticality corner, needing no failure-rate data. Quantitative FMECA computes a numeric criticality number from actual part failure rates, as MIL-STD-1629A specifies. Use the quantitative route only where reliable failure-rate data exists; otherwise the matrix is the honest choice.

When should you use FMECA instead of FMEA?

Use FMECA when a mistaken ranking would be dangerous or expensive and you can support a defensible criticality, typically in aerospace, defense, medical, and nuclear work, or high-consequence design reviews. Use a plain FMEA when team judgment is proportionate to the stakes and you lack or do not need hard failure-rate data.

Does FMEA still use RPN?

Traditional FMEA prioritizes with a Risk Priority Number, severity times occurrence times detection. The 2019 AIAG-VDA FMEA handbook replaced the single RPN with an Action Priority scheme of High, Medium, and Low for automotive practice, to avoid the RPN's habit of giving very different risks the same number. FMECA sidesteps the issue with its criticality ranking.

FMEA vs FMECA: What's the Difference?

Q: What is the difference between FMEA and FMECA?

An FMEA identifies how something can fail, the effect of each failure, and prioritizes the modes, usually with a Risk Priority Number. An FMECA is an FMEA plus a criticality analysis: a formal ranking of each failure mode by severity combined with its probability of occurrence. FMECA is a superset, so every FMECA contains an FMEA.

One added step separates them: a criticality analysis. What it adds, how the criticality number is built, and a straight test for when the extra effort is worth it.

FMEA and FMECA differ by one added step. An FMEA (failure mode and effects analysis) lists how something can fail, the effect of each failure, and prioritizes the modes. An FMECA is an FMEA plus a criticality analysis a formal ranking of each failure mode by severity combined with its probability of occurrence. FMECA is a superset: every FMECA contains an FMEA.

That is the whole difference in one paragraph, and for many teams it is enough. But the two acronyms get used loosely, and the choice matters because the extra criticality step costs real effort and pays off only when you have the data and the consequences to justify it. This guide draws the line cleanly: what each method produces, exactly what the criticality analysis adds, the qualitative and quantitative ways to do it, and a straight test for when to add it.

What is the core difference between FMEA and FMECA?

The difference is the criticality analysis (CA). An FMEA answers “how can this fail, what happens when it does, and which modes matter most?” It typically prioritizes with a Risk Priority Number (RPN), severity × occurrence × detection, or, in the newer automotive method, an Action Priority rating. An FMECA answers all of that and then adds a dedicated step that ranks each failure mode by the combined influence of severity and probability of occurrence, producing a criticality that lets you sort modes by how much risk they truly carry.

The distinction comes straight from the founding standard. In MIL-STD-1629A FMEA is the analysis performed without criticality analysis, and FMECA is an FMEA with criticality analysis bolted on. So the letter C is not decoration, it names a specific added procedure, not a fancier version of the same work.

Every FMECA is an FMEA with one more step. The criticality analysis ranks failure modes by severity combined with probability, so the highest-risk modes rise to the top on evidence, not judgment alone.

What does the criticality analysis actually add?

It adds a disciplined ranking that does not lean on the RPN’s detection term. Plain-FMEA prioritization multiplies severity, occurrence, and detection into one RPN, and that number has a well-known weakness: very different risks can share an RPN, and a good inspection (low detection score) can mask a severe, frequent failure. Criticality analysis sidesteps that by ranking on severity and probability of occurrence directly, the two dimensions that describe how much damage a mode does and how often. The result is a ranking you can defend to a safety auditor or a design-review board.

There are two accepted ways to produce it. The qualitative route plots each mode on a criticality matrix, severity on one axis, probability on the other, and reads the high-criticality corner. It needs no failure-rate data, which is why maintenance and process teams reach for it; it is the same logic as an asset criticality matrix. The quantitative route computes a criticality number from actual failure rates, and it is what MIL-STD-1629A specifies for design work where the data exists.

How is the quantitative criticality number calculated?

MIL-STD-1629A defines a failure-mode criticality number, Cₘ, built from four factors:

The quantitative criticality number multiplies how likely the effect is, the mode’s share of the part’s failures, the part’s failure rate, and the operating time. Summing Cₘ across a part’s modes gives an item criticality.

In words: Cₘ = β × α × λₚ × t, where β is the conditional probability the failure effect occurs, α is the fraction of the part’s failures that take this mode, λₚ is the part’s failure rate and t is the operating time. Sum Cₘ across all of a part’s modes and you get the item criticality, Cₕ. The math is only as good as λₚ, which is why quantitative FMECA lives where reliable failure-rate data exists, and why the qualitative matrix is the honest choice when it does not.

FMEA vs FMECA at a glance

Dimension	FMEA	FMECA
Core question	How can it fail and what happens?	Same, plus how critical is each mode?
Prioritization	RPN or Action Priority	Criticality (severity × probability)
Extra step	None	Criticality analysis
Data needed	Team judgment, ratings	Adds failure-rate data (for quantitative)
Effort	Lower	Higher
Typical home	Process and design teams, quality	Aerospace, defense, high-consequence design

When should you add criticality analysis? A decision test

Weigh the consequences. If a failure can hurt someone, breach a regulation, or scrap a mission, the formal criticality ranking earns its cost. For low-consequence process tweaks, a plain FMEA with RPN or Action Priority is usually proportionate.
Check whether you have failure-rate data. Quantitative FMECA needs credible λₚ values. With a solid failure mode library and MTBF history you can compute criticality numbers; without them, use the qualitative matrix instead of inventing precision.
Look at your industry’s obligations. Aerospace, defense, medical, and nuclear work often mandate FMECA. Most automotive and general-manufacturing programs run FMEA under the AIAG-VDA method and add criticality only where a customer or standard requires it.
Judge whether RPN is misleading you. If your FMEA keeps producing tied RPNs or hiding severe failures behind good detection scores, the criticality ranking’s severity-and-probability focus is the fix.
Match the effort to the stakes. Criticality analysis is more work per line. Spend it where a mistaken ranking would be expensive or dangerous, and keep the lighter FMEA everywhere else. A thorough FMEA beats a rushed FMECA.

When is a plain FMEA the right call?

A plain FMEA is right when the team’s judgment-based ratings are proportionate to the stakes and you do not have (or do not need) hard failure-rate data. That covers most process FMEAs on a production line and many design FMEAs early in development, where the goal is to surface and rank risks fast and drive actions, not to defend a quantified criticality to a regulator. If your prioritization already changes behavior, the top modes get countermeasures and the RPNs fall on re-scoring, the FMEA is doing its job, and adding criticality would be ceremony.

When do you genuinely need FMECA?

You need FMECA when a mistaken ranking has serious consequences and you can support a defensible one. That is the aerospace, defense, medical-device, and nuclear world, where a formal criticality analysis is often mandated and where reliable failure-rate data exists to feed the quantitative number. It also fits high-consequence design reviews in any industry: when a safety board must see that the highest-criticality modes were identified and mitigated on evidence, the criticality column is what carries the argument. If you have the consequences but not the data, run the qualitative matrix version, it delivers most of the discipline without pretending to a precision you cannot back.

Where does maintenance use FMEA and FMECA?

Reliability engineers use both to decide maintenance strategy, not just design. In a maintenance FMECA, the failure modes come from equipment history, the criticality ranking sorts which modes deserve proactive attention, and the output feeds the PM plan: high-criticality modes with a measurable warning get condition monitoring high-criticality modes without one get scheduled replacement, and low-criticality modes are deliberately run to failure with a spare on the shelf. This is the analytical core of reliability-centered maintenance, and it is why a maintenance FMECA and an asset criticality ranking so often sit side by side.

The practical caution on the floor is data. A design FMECA in aerospace draws on qualified component failure rates; a plant rarely has that for its own mixed, aging equipment. So maintenance teams lean on the qualitative criticality matrix, using their coded failure history and known failure modes to place each mode by severity and how often it actually happens. That is a defensible FMECA built from the data a plant really has, rather than borrowed numbers dressed up as precision.

What the numbers say

The distinction originates in MIL-STD-1629A which defines FMEA as the analysis without criticality and FMECA as FMEA with a criticality analysis that ranks each mode by the combined influence of severity and probability of occurrence (MIL-STD-1629A, Procedures for Performing a Failure Mode, Effects and Criticality Analysis). Its quantitative criticality number Cₘ = β·α·λₚ·t is still the reference formula.
The current international standard, IEC 60812:2018 covers both FMEA and FMECA and treats criticality analysis as the optional extension that turns one into the other (IEC 60812:2018, Failure modes and effects analysis (FMEA and FMECA)). The 2019 AIAG-VDA FMEA handbook, meanwhile, replaced the single RPN with an Action Priority (High/Medium/Low) scheme for prioritization in automotive practice.

The short version: reach for FMEA to surface and rank failure modes with team judgment, and add the criticality analysis of FMECA when the consequences are severe and you can defend the ranking, quantitatively where failure-rate data exists, qualitatively where it does not. Both methods run on a clear list of failure modes, which is exactly what a failure mode library supplies and what a predictive maintenance and reliability program acts on. For the operator-led care that keeps the highest-criticality modes from ever reaching the floor, see total productive maintenance and for how trustworthy failure data gets captured in a real plant, the CLS case study.