Key takeaways
Short answer: FMEA and FMECA are closely related reliability tools, and the difference is the final letter. FMEA (failure mode and effects analysis) is a structured method for identifying the ways a product or process can fail (failure modes), the effects of each failure, and its causes. FMECA (failure mode, effects, and criticality analysis) is FMEA with an added criticality analysis — a more quantitative step that ranks each failure mode by the severity of its effect and the probability of its occurrence, so resources go to the failures that matter most. Every FMECA contains an FMEA; the criticality analysis is what FMECA adds on top.
FMEA — failure mode and effects analysis — is a structured, systematic method for anticipating how a product or process can fail before it does. Working item by item or function by function, a team identifies each potential failure mode (the specific way something can fail — a seal can leak, a weld can crack, a step can be skipped), the effects of that failure (what happens downstream and to the customer), and the causes that could produce it. Many FMEAs then rate each failure mode on severity, occurrence, and detection, often combining these into a risk priority number (RPN) to help prioritize. FMEA exists in flavours — design FMEA for products, process FMEA for manufacturing processes — but the core is always the same: a disciplined, mostly qualitative-to-semiquantitative inventory of what can go wrong, how badly, how often, and how likely it is to be caught, used to drive preventive action. Its great value is forcing a team to think through failure systematically rather than reacting after the fact. It answers "what can fail, how, why, and with what effect?"
FMECA — failure mode, effects, and criticality analysis — is FMEA extended with a criticality analysis. It does everything an FMEA does (identify failure modes, effects, and causes) and then adds a structured, more quantitative step that assesses the criticality of each failure mode by combining the severity of its effect with the probability (or rate) of its occurrence. The criticality analysis can be qualitative (placing each failure mode on a criticality matrix of severity against likelihood) or quantitative (computing a criticality number from failure-rate data), but either way it produces a ranking of failure modes by how critical they are. FMECA has its roots in military and aerospace reliability practice (notably the MIL-STD-1629A standard) where rigorous, defensible prioritization of failures is essential. The "C" — criticality — is the whole of the difference: FMECA takes the failure modes the FMEA identified and subjects them to a formal criticality assessment, so the output is not just a list of what can fail but a prioritized ranking of which failures are most critical and deserve attention first.
The entire distinction between the two methods is the criticality analysis that FMECA adds. An FMEA tells you what can fail, how, why, and with what effect — and, if it uses RPN, gives a rough prioritization. FMECA adds a dedicated, more rigorous criticality step that explicitly ranks failure modes by combining severity and probability of occurrence, often using actual failure-rate data and a criticality matrix or criticality number. In other words, FMEA is the foundation and criticality analysis is the superstructure: you cannot do the criticality analysis without first having done the FMEA, because criticality is assessed on the failure modes the FMEA identified. This is why "every FMECA contains an FMEA" is exactly true — the FMECA is an FMEA plus the C. The practical effect of adding criticality is sharper, more defensible prioritization: instead of a flat list (or a sometimes-criticized RPN), you get an explicit ranking of which failures are most critical, grounded where possible in quantitative likelihood, so reliability effort flows to the failure modes that genuinely matter most.
A useful way to see the difference is in how each prioritizes. FMEA commonly prioritizes through the risk priority number — severity times occurrence times detection — which is simple and widely used but has well-known weaknesses: it mixes three different scales into one number, can rank very different risks equally, and depends on subjective ratings. FMECA's criticality analysis aims for a more rigorous prioritization, focusing on severity and the probability of occurrence and, in its quantitative form, drawing on actual failure-rate data to compute criticality rather than relying solely on subjective scores. This makes FMECA more demanding — it needs reliability data and more analytical effort — but more defensible where the stakes justify it. The trade-off is effort versus rigour: FMEA's qualitative-to-semiquantitative approach is faster and lighter and sufficient for many situations, while FMECA's criticality analysis is heavier but gives a stronger, data-grounded ranking. Choosing between them is largely a choice about how rigorous and quantitative your prioritization needs to be, and whether you have the failure-rate data to support the criticality analysis.
Take a process pump. An FMEA lists its failure modes and works through each: the mechanical seal can leak (effect: fluid loss and contamination; cause: seal wear), the bearing can seize (effect: pump stops, possible motor damage; cause: loss of lubrication), the impeller can wear (effect: reduced flow; cause: abrasive fluid). The team rates severity, occurrence, and detection and perhaps computes an RPN for each. A FMECA takes those same failure modes and adds a criticality analysis: it assigns each a severity category (bearing seize, which can damage the motor and stop production, is high severity; a slow seal leak is moderate) and a probability of occurrence drawn from failure-rate data, then plots them on a criticality matrix or computes a criticality number. The result is an explicit ranking — bearing seizure comes out as the highest-criticality mode (high severity combined with a meaningful failure rate), so it is the first to be designed out or protected with condition monitoring. The FMEA found and described the failure modes; the FMECA's criticality analysis ranked them so the team knows, defensibly, which one to tackle first.
Use a plain FMEA when a qualitative-to-semiquantitative analysis is sufficient — which covers most automotive, general manufacturing, and process applications, where RPN-based prioritization and a systematic failure inventory give enough to act on, and where detailed failure-rate data may not exist. FMEA is faster, lighter, and widely standardized, making it the default for everyday design and process risk work. Use FMECA when you need rigorous, data-driven criticality ranking — typically in aerospace, defense, nuclear, and other high-consequence domains where failures can be catastrophic, where standards or customers require a formal criticality analysis, and where failure-rate data is available to support quantitative criticality. The decision framework is to ask how high the stakes are and how rigorous the prioritization must be: if a defensible, quantitative ranking of which failures are most critical is essential — and you have the data — invest in FMECA; if a systematic qualitative analysis with RPN prioritization meets the need, FMEA is the efficient choice. Many organizations use FMEA broadly and reserve FMECA for their most safety- or mission-critical items.
FMEA and FMECA are preventive tools that protect OEE by anticipating and designing out the failures that cause losses. Failure modes that lead to equipment stoppages attack the Availability factor; those that lead to defects attack the Quality factor; those that degrade speed attack Performance. By identifying these failure modes before they occur and — in FMECA — ranking them by criticality, the analysis directs reliability and maintenance effort at the failures that would do the most OEE damage. This is where criticality ranking pays off: it aligns prevention with the biggest losses, much as a Pareto analysis of downtime does, so you design out or monitor the high-criticality modes first. The findings feed directly into maintenance strategy — high-criticality failure modes are prime candidates for condition-based maintenance or redesign — and into the preventive action that stops failures before they recur. Real downtime data closes the loop by validating which failure modes actually cost the most OEE.
Fabrico provides the real-world failure and downtime data that makes an FMEA or FMECA honest. By capturing which failures actually occur and what they cost in OEE — through downtime reason codes against live Availability, Performance, and Quality — it shows whether the criticality ranking on paper matches reality, and which failure modes are genuinely draining production. That feedback turns a predictive analysis into a validated one and points maintenance effort at the failures that matter most. Book a demo to ground your reliability analysis in real loss data.
FMEA identifies failure modes, their effects, and causes. FMECA adds a criticality analysis that ranks each failure mode by severity and probability of occurrence. FMECA is FMEA plus the criticality step — every FMECA contains an FMEA, and the criticality analysis is what it adds on top.
Criticality. The criticality analysis assesses each failure mode by combining the severity of its effect with the probability of its occurrence, producing a ranking of which failures are most critical — often using a criticality matrix or, with failure-rate data, a quantitative criticality number.
Use FMECA when you need rigorous, data-driven criticality ranking — typically in aerospace, defense, nuclear, and other high-consequence domains, or where a standard or customer requires formal criticality analysis and failure-rate data is available. Use FMEA when a qualitative, RPN-based analysis is sufficient.
Essentially yes. FMECA is not a separate method but an FMEA extended with a criticality analysis. The failure-mode identification work is the same foundation; FMECA adds a structured, more quantitative step to rank the failure modes by criticality so prioritization is more defensible.
They anticipate and help design out the failures that cause OEE losses — stoppages that hurt Availability, defects that hurt Quality, and slowdowns that hurt Performance. FMECA's criticality ranking directs reliability effort at the failure modes that would do the most OEE damage, aligning prevention with the biggest losses.
Connexion
Blog
