About FMEA (Failure Mode and Effects Analysis)?
Failure Mode and Effects Analysis (FMEA) is a structured method for identifying how an asset or process can fail, what effect each failure would have, and which failures deserve attention before they happen. It works asset by asset, listing every plausible way something could go wrong, then rating how severe, how likely, and how detectable each failure mode is so effort goes where the risk is highest. Done well, FMEA turns failure analysis from a reactive exercise, run after a breakdown, into a proactive one, run before a failure ever occurs. This article defines FMEA and the terminology cluster around it, including FMECA, the Risk Priority Number, and how the analysis connects to root cause analysis and reliability-centered maintenance.
How does FMEA work?
FMEA breaks equipment or a process into its individual functions or steps and asks three questions of each one: how could this fail, what would happen if it did, and why would it happen. A failure mode is the specific way a component or step could fail to perform its function, such as a bearing seizing or a valve failing to close. A failure effect is the consequence of that failure mode on the asset, the process, or the operation, and a failure cause is the mechanism that triggers it, such as wear, corrosion, or contamination. A failure mode is written as the failure itself: "bearing seizes" is the failure mode, "insufficient lubrication" is its cause, and "unplanned line stoppage" is its effect.
FMEA comes in two common forms, and asset-intensive operations typically care most about one of them. Design FMEA (DFMEA) reviews a product or system design before it goes into production, a one-time exercise run by an engineering team. Process FMEA (PFMEA) reviews the ongoing steps of a manufacturing or maintenance process, and it is the version most relevant to maintenance and operations teams, since it is revisited as failure history accumulates and can be tied directly to the work orders it informs, rather than closed out once at launch like DFMEA.
Each failure mode is then scored on three factors: severity, occurrence, and detection. These three ratings feed the scoring mechanism below.
What is the Risk Priority Number (RPN)?
The Risk Priority Number (RPN) is the score that ranks failure modes against each other, typically calculated by multiplying severity, occurrence, and detection together, so a team knows which ones to address first. A high RPN does not always mean the most likely failure. A failure mode with moderate likelihood but severe consequences and poor detectability can outrank one that happens more often but is caught early and causes little damage. Multiplying the three factors together, rather than looking at any one alone, forces a team to weigh probability, consequence, and visibility at the same time. RPN is a prioritization tool, not a precise probability: two organizations rating the same failure mode may land on different numbers depending on how they define their scales, so what matters is the relative ranking within one analysis, not the exact odds of a specific failure occurring next quarter.
What is the difference between FMEA and FMECA?
FMECA, Failure Mode, Effects, and Criticality Analysis, is FMEA with a formal criticality analysis added on top. Where standard FMEA scores and ranks failure modes largely through the RPN calculation, FMECA adds a structured criticality assessment, often plotted on a severity-versus-probability matrix, that classifies failure modes into defined risk categories and ties each one more explicitly to operational impact. The practical difference: FMEA answers what can fail and how it should be ranked, while FMECA answers the same question and then formally classifies how critical each failure mode is to the operation as a whole. That distinction is why FMECA is the version most commonly required in safety-regulated, mission-critical, or capital-intensive environments such as chemical processing or utilities, even though many industrial reliability teams use the two terms close to interchangeably day to day.
How does FMEA differ from root cause analysis?
Root cause analysis (RCA) identifies why a failure that has already happened occurred, working backward from an observed breakdown to its underlying cause. FMEA and RCA are mirror images of each other, answering the same question, why does this fail, from opposite directions. FMEA is proactive, anticipating what could fail before anything has gone wrong, using engineering knowledge and historical failure data. RCA is reactive, starting from an actual failure event and working backward to find what caused it. The two feed each other in a mature reliability program: findings from RCA investigations become new failure modes in the next FMEA update, and a well-built FMEA narrows the list of likely causes an RCA investigation checks first.
How does FMEA feed reliability-centered maintenance?
Reliability-centered maintenance (RCM) is a structured method for selecting the right maintenance strategy for each asset based on how it can fail and the consequence of that failure, rather than applying the same approach to every asset regardless of risk. FMEA and FMECA are the analysis techniques that feed an RCM program, not a substitute for it. RCM asks a broader question: given what the analysis surfaced about how an asset can fail, should the maintenance strategy be time-based, condition-based, run-to-failure, or something else. FMEA and FMECA supply the failure modes, effects, and criticality rankings that make that decision defensible instead of guesswork.
Why FMEA matters
The cost of skipping FMEA and FMECA shows up later and larger: unplanned downtime, safety incidents, or capital spent maintaining low-risk assets while high-risk ones go unaddressed, because no one ranked which failure modes actually mattered. Reliability teams without a structured criticality analysis tend to spread maintenance effort evenly, or reactively toward whatever broke most recently, rather than toward the failure modes with the highest severity, likelihood, and consequence.
Kisuma Chemicals demonstrated the alternative: applying an FMECA strategy supported a 40 percent reduction in downtime. That outcome reflects what a criticality-ranked failure analysis is meant to produce: maintenance effort directed at the failure modes that actually drive downtime, instead of spread thin across the asset base.
From FMEA to executed work
FMEA and FMECA identify and rank failure modes, but they do not, on their own, schedule a task, order a spare part, or close out a work order. The analysis produces a prioritized list; turning that list into prevented failures still requires a maintenance program that acts on it. This is the handoff Ultimo's Proactive Maintenance module supports: it takes reliability-centered and risk-based maintenance strategies, including FMECA, and translates criticality rankings into planned maintenance intervals rather than leaving them in a spreadsheet. Work Order Management then plans, prioritizes, and tracks the resulting work through to completion, so a ranked failure mode becomes a scheduled task rather than a documented risk that sits unaddressed.
FMEA in Ultimo
Reliability and maintenance teams running FMEA or FMECA analyses use Ultimo to keep that work connected to the maintenance program it is meant to inform, rather than sitting in a separate document disconnected from day-to-day execution. Failure modes and criticality rankings inform Proactive Maintenance's planning, and Reporting and Dashboards, built on Power BI integration, give reliability engineers, maintenance directors, and operations leaders cross-departmental visibility into which failure modes are driving downtime over time.
Ultimo supports this as part of Intelligent Asset Management, its category across EAM, CMMS, analytics, and AI-native experiences. FMEA and FMECA supply the risk ranking; Ultimo supports turning that ranking into planned, executed, and tracked maintenance work.
Frequently Asked Questions
What is the difference between FMEA and FMECA?
FMEA identifies failure modes, their effects, and ranks them using a Risk Priority Number. FMECA does the same analysis and adds a formal criticality classification, often on a severity-versus-probability matrix, that ties each failure mode more explicitly to operational or safety consequence. FMECA is the more rigorous version, common in regulated or high-consequence industries.
What is the difference between DFMEA and PFMEA?
Design FMEA (DFMEA) reviews a product or system design before production begins, typically as a one-time engineering exercise. Process FMEA (PFMEA) reviews an ongoing manufacturing or maintenance process instead, and it is the version maintenance and reliability teams use most, since it stays tied to accumulating failure history and connects to real work orders.
What does RPN stand for and how is it calculated?
RPN stands for Risk Priority Number. It is typically calculated by multiplying a failure mode's severity, occurrence, and detection ratings together, producing a single score used to rank failure modes against each other for prioritization.
Is FMEA a Lean or Six Sigma tool?
Neither exclusively. FMEA predates both methodologies and is used as a risk-analysis technique within Lean, Six Sigma, and other quality frameworks alike. It is not owned by any single methodology, which is part of why it appears across so many industries and standards.
What are the steps of the FMEA process?
A typical FMEA follows a set sequence: define the scope, identify failure modes, identify their effects, identify the causes, score severity, occurrence, and detection, then calculate the RPN to prioritize and act.
Does FMEA replace root cause analysis?
No. FMEA anticipates failure modes before they occur, while root cause analysis investigates the cause of a failure after it happens. A mature reliability program uses both together: RCA findings feed the next FMEA update, and FMEA findings narrow what an RCA investigation checks first.
Can FMEA and FMECA reduce downtime?
Applied consistently and connected to an active maintenance program, yes. Kisuma Chemicals demonstrated a 40 percent reduction in downtime by applying an FMECA strategy, an outcome of directing maintenance effort at the failure modes ranked highest for severity, likelihood, and consequence.