About FMECA (Failure Mode, Effects, and Criticality Analysis)
FMECA (Failure Mode, Effects, and Criticality Analysis) is FMEA with a formal criticality analysis added on top. It identifies how an asset can fail and what effect each failure would have. It then quantifies how critical each failure mode is, using a severity-versus-probability assessment. The failure modes that matter most are the ones that get acted on first. This article covers the criticality matrix at the center of the method, a full worked example, and the military standard FMECA traces back to. It also covers where FMECA is expected or required today. Finally, it shows how a finished criticality ranking connects to a maintenance program instead of sitting in a document.
How does FMECA differ from FMEA?
FMEA identifies and ranks failure modes, typically through a Risk Priority Number. FMECA performs the same analysis, then adds a structured criticality classification on top, usually plotted on a severity-versus-probability matrix. That extra layer ties each failure mode more explicitly to operational or safety consequence. For the fuller FMEA definition, including the Risk Priority Number calculation and the design-versus-process distinction, see FMEA (Failure Mode and Effects Analysis).
Where does FMECA come from?
FMECA traces back to US military and aerospace reliability engineering in the 1940s and 1950s, formalized in MIL-STD-1629A, "Procedures for Performing a Failure Mode, Effects, and Criticality Analysis." That standard is why FMECA carries a more rigorous, audit-ready structure than a general FMEA. It was written for programs where a missed failure mode has safety or mission consequences, not just cost. In practice, that traceability requirement often shows up as a contractual deliverable: a defense or aerospace program review may require a completed FMECA report before a design proceeds to the next milestone, not simply as internal engineering documentation.
The military standard is the origin, not the boundary. FMECA is now applied well beyond defense and aerospace, wherever a formal, auditable criticality ranking is expected rather than an informal risk list. Chemical processing, utilities, and other asset-intensive, safety-regulated, or capital-intensive operations all use the same discipline for the same reason: a documented criticality classification holds up to an audit in a way an informal RPN estimate does not.
The criticality matrix: how FMECA classifies risk
The criticality matrix is the tool FMECA uses to classify risk by plotting a failure mode's severity against its probability of occurrence, so the position on the matrix, not a single blended score, determines how urgently it needs action. Each failure mode is rated on two axes:
Severity: the consequence if the failure happens, typically categorized on a defined scale such as catastrophic, critical, marginal, and negligible
Probability (or occurrence): how likely the failure mode is to happen over a defined period, based on failure history, design margins, or operating conditions
Where a failure mode lands on the matrix sets its criticality category, from failure modes that demand immediate attention (high severity, meaningful probability) down to ones that can be monitored rather than acted on immediately (low severity, regardless of how often they occur). Underneath the matrix sits the criticality number, a single figure built from a failure mode's probability, the fraction of failures attributable to that specific mode, and an operating-time factor, so its contribution to overall system risk can be added up alongside every other failure mode in the analysis.
The matrix earns its place over a single RPN-style score because it separates two questions that a blended number collapses into one: how bad, and how likely. A rare but catastrophic failure mode can outrank a frequent but minor one on the matrix, exactly the ranking a maintenance team needs and exactly the ranking a single averaged score can obscure.
A worked FMECA example
Consider a feed pump on a production line, one asset with two different failure modes under analysis.
Failure mode 1: pump seal fails.
Failure mode: the seal fails and the pump loses containment
Effect: unplanned line stoppage and lost product
Cause: seal wear from abrasive particulates in the process fluid
Severity: critical, a full line stop
Probability: moderate, it has happened a handful of times a year on this asset class
Detection: poor, there is no condition monitoring in place, so the failure is typically found only after it happens
Plotted on the criticality matrix, critical severity combined with moderate probability and poor detectability places this failure mode in a high-criticality category. It gets prioritized for action ahead of failure modes with a lower consequence, regardless of how the raw frequency compares.
Failure mode 2: cosmetic panel fastener loosens.
Severity: negligible, no effect on output or safety
Probability: high, it happens more often than the seal failure
Detection: good, it is visible on routine inspection
Even though this failure mode occurs more often, its negligible severity places it in a low-priority quadrant of the matrix. Frequency alone never overrides severity in a criticality ranking.
This is exactly the output FMECA is meant to produce: a ranked list where the pump seal, not the fastener, sits at the top, and where that ranking is defensible against an audit rather than a gut call about what "feels" urgent.
Where FMECA is expected or required
Beyond its aerospace and defense origin, several asset-heavy sectors treat a formal criticality analysis as standard practice, not an optional exercise:
Chemical and process manufacturing, where safety-critical process equipment failures carry consequences beyond lost output
Utilities, where grid and infrastructure asset failures carry public-safety or service-continuity consequences
Other capital-intensive, safety-regulated operations, where a plain FMEA with an informal Risk Priority Number is often not considered sufficient audit evidence on its own
In these environments, a documented criticality classification is closer to a compliance expectation than a nice-to-have. Kisuma Chemicals, a chemical manufacturer, demonstrates the payoff of doing the exercise properly: "The FMECA strategy in Ultimo has helped us reduce downtime by 40% and realize considerable cost savings," according to Jan Wolf, Reliability Engineer at Kisuma Chemicals. That outcome reflects the same principle the worked example above shows: ranking failure modes by criticality, not frequency, directs maintenance effort where it actually reduces downtime.
Why a criticality ranking fails if it stays on paper
A completed FMECA is a document, not a maintenance program. A criticality ranking that lives in a spreadsheet or a one-time report does not, by itself, reschedule a preventive maintenance task, reorder a spare part, or reprioritize a work order. This is the gap reliability teams run into even after doing the analysis correctly: the findings sit ranked and accurate, and unaddressed. That gap is not a failure of the analysis itself; the ranking is usually correct. It is a failure of the handoff between the analysis and the maintenance system that is supposed to act on it.
The value of an FMECA is only realized once its high-criticality failure modes are translated into planned maintenance intervals, confirmed spare-parts availability, and prioritized work, ahead of the failures the analysis already flagged as likely and severe. Getting from a ranked list to that outcome takes a maintenance program built to act on the ranking, not a better spreadsheet.
FMECA in Ultimo
Reliability and maintenance teams running an FMECA use Ultimo to keep the criticality ranking connected to the maintenance program it is meant to inform, instead of leaving it in a separate document disconnected from day-to-day execution. Ultimo's Proactive Maintenance capability offers AI-embedded suggestions for proactive maintenance planning and failure prevention, supporting reliability-centered and risk-based maintenance strategies. That is the direct mechanism that turns a criticality ranking into planned maintenance intervals rather than a static report.
Work Order Management then plans, prioritizes, and tracks the resulting work through to completion, so a high-criticality failure mode becomes a scheduled task, not an unaddressed risk sitting in a document. Reporting and Dashboards runs on Power BI integration and surfaces which failure modes are driving downtime over time, for reliability engineers, maintenance directors, and operations leaders alike.
FMECA itself is a method, not an Ultimo feature name. Ultimo supports the execution of an FMECA-driven maintenance strategy as part of Intelligent Asset Management, the category that connects EAM, analytics, and AI-embedded workflows into one system rather than a set of disconnected tools.
Frequently Asked Questions
What does FMECA stand for?
FMECA stands for Failure Mode, Effects, and Criticality Analysis. It identifies how an asset can fail, what effect each failure would have, and how critical each failure mode is. It builds on FMEA by adding a formal criticality classification, typically a severity-versus-probability matrix. That lets failure modes be ranked and prioritized on an auditable basis rather than an informal estimate.
What is the difference between FMEA and FMECA?
FMECA adds a formal criticality classification on top of standard FMEA scoring. Where FMEA ranks failure modes through a Risk Priority Number, FMECA also plots each one on a severity-versus-probability matrix. That classification ties each failure mode more explicitly to operational or safety consequence. See FMEA (Failure Mode and Effects Analysis) for the fuller FMEA definition, including the RPN calculation.
What is a criticality number in FMECA?
A criticality number is a single figure showing a failure mode's contribution to overall system risk. It combines the failure mode's probability of occurring, the share of that asset's failures caused by that mode, and an operating-time factor. Criticality numbers across all of an asset's failure modes can be added together. That gives a defensible, auditable basis for ranking risk, rather than a subjective estimate of what feels most urgent.
Where is FMECA required or expected?
FMECA originated in US military and aerospace reliability engineering, formalized in MIL-STD-1629A, and remains standard practice in those sectors. It is now also expected in chemical and process manufacturing, utilities, and other capital-intensive or safety-regulated operations, where a documented criticality classification is often treated as necessary audit evidence rather than an optional exercise.
Can an FMECA reduce downtime?
Applied consistently and connected to an active maintenance program, yes. Kisuma Chemicals, a chemical manufacturer, demonstrated a 40 percent reduction in downtime by applying an FMECA strategy. That outcome came from directing maintenance effort at the highest-ranked failure modes, not spreading effort evenly across the asset base.