Failure Modes and Effects Analysis (FMEA)

Publication Status#

This page is the owner-authorized public-release preparation record for `KN-4003`.

This article is published as part of the Reliability Method Knowledge Library at `https://reliabilitymethod.com/knowledge/failure-modes-and-effects-analysis-fmea`.

The templates, calculators, AI tools, Facility Manager features, dashboards, reports, SOPs, training assets, and consulting offers named below are planned opportunities only. They are not currently available product assets.

Plain-English Definition#

Failure Modes and Effects Analysis (FMEA) is a structured method for identifying how an asset, system, process, or component can fail, evaluating the consequences of those failures, and prioritizing actions that reduce risk before failures occur.

FMEA is a proactive risk assessment tool.

Rather than waiting for equipment to fail and then performing a Root Cause Analysis, FMEA asks:

"What could fail, what would happen if it did, and what should we do about it before it happens?"

Executive Summary#

FMEA is one of the most widely used reliability engineering methodologies.

It provides a systematic approach for identifying potential failures, evaluating their business impact, and selecting actions that reduce operational risk.

A well-executed FMEA helps organizations:

• Improve equipment reliability
• Reduce safety risks
• Improve product quality
• Optimize maintenance strategies
• Reduce unplanned downtime
• Prioritize engineering improvements
• Improve capital planning
• Support Reliability-Centered Maintenance (RCM)

FMEA converts engineering knowledge into structured risk-reduction decisions.

Why FMEA Matters#

Maintenance resources are limited.

Organizations cannot eliminate every possible failure.

FMEA helps determine where resources will create the greatest reduction in business risk.

Instead of treating all failures equally, FMEA identifies:

• Which failures are most severe
• Which failures occur most frequently
• Which failures are least likely to be detected
• Which improvements should receive the highest priority

This allows maintenance and engineering teams to focus on the failures that matter most.

What FMEA Is#

FMEA is a proactive reliability analysis process.

For every asset or process, it asks:

• What is the intended function?
• How can it fail?
• What causes the failure?
• What happens when it fails?
• How severe are the consequences?
• How often is it likely to occur?
• How likely are we to detect it before failure?
• What actions reduce the risk?

The result is a prioritized improvement plan.

What FMEA Is Not#

FMEA is not:

• A Root Cause Analysis
• A maintenance schedule
• A preventive maintenance program
• A design review alone
• A one-time exercise
• A spreadsheet completed for compliance

FMEA should directly influence maintenance strategy, engineering improvements, and operational decision-making.

Objectives of FMEA#

An effective FMEA should:

• Identify potential failure modes
• Evaluate failure effects
• Understand business consequences
• Prioritize risks
• Recommend risk-reduction actions
• Improve maintenance strategies
• Improve equipment design
• Improve safety
• Reduce lifecycle cost

The FMEA Philosophy#

Every asset has potential failure modes.

Not every failure presents the same level of risk.

Risk should be evaluated before failure occurs.

The greatest opportunity for improvement exists before equipment fails.

FMEA helps organizations shift from reactive maintenance toward proactive reliability management.

Types of FMEA#

Several forms of FMEA are commonly used.

Design FMEA (DFMEA)#

Evaluates risks associated with equipment or product design.

Typical users:

• Design Engineers
• Capital Project Teams
• OEMs

Process FMEA (PFMEA)#

Evaluates risks associated with manufacturing or maintenance processes.

Typical users:

• Manufacturing Engineers
• Operations
• Maintenance

Equipment or Maintenance FMEA#

Evaluates equipment failure modes and maintenance strategies.

Typical users:

• Reliability Engineers
• Maintenance Leaders
• Asset Managers

This is the primary focus of the Reliability Method Knowledge Library.

Relationship to Reliability Engineering#

FMEA is one of the core analytical tools used within Reliability Engineering.

Reliability Engineering establishes the improvement strategy.

FMEA evaluates where risk exists.

The findings influence:

• Preventive Maintenance
• Predictive Maintenance
• Root Cause Analysis
• Reliability-Centered Maintenance
• Asset Criticality
• Capital Planning
• Equipment Design

Relationship to Failure Modes#

Failure Modes are the foundation of FMEA.

An FMEA cannot be completed without understanding:

• Asset functions
• Functional failures
• Failure modes
• Failure mechanisms
• Failure effects
• Failure consequences

The quality of an FMEA depends on the quality of its failure mode analysis.

Inputs#

Typical inputs include:

• Asset Register
• Asset Criticality Analysis
• Failure Mode Library
• CMMS History
• OEM Documentation
• Equipment Drawings
• Reliability Data
• Technician Experience
• Operations Feedback
• Industry Standards

Outputs#

An FMEA typically produces:

• Failure Mode Register
• Failure Effects
• Risk Evaluation
• Recommended Actions
• Maintenance Strategy Improvements
• PM Recommendations
• PdM Recommendations
• Engineering Recommendations
• Risk Priorities

The FMEA Process#

FMEA should follow a standardized process to ensure consistency across assets and facilities.

Recommended process:

1. Define the asset or process.
2. Define the intended functions.
3. Identify functional failures.
4. Identify failure modes.
5. Identify failure effects.
6. Evaluate failure consequences.
7. Assign Severity, Occurrence, and Detection ratings.
8. Calculate risk priority.
9. Recommend actions.
10. Implement improvements.
11. Re-evaluate risk after improvements.

The value of FMEA comes from the quality of discussion, not simply completing a worksheet.

Building the FMEA Team#

FMEA should be completed by a cross-functional team.

Typical participants include:

• Reliability Engineer
• Maintenance Supervisor
• Maintenance Planner
• Maintenance Technician
• Operations Representative
• Process Engineer
• Quality Representative
• Safety Representative
• OEM or Vendor (when appropriate)

Different perspectives improve the quality of risk identification.

Defining Asset Functions#

Every FMEA begins by defining what the asset is expected to do.

Questions include:

• What function does the asset perform?
• What performance standards are required?
• What operating conditions exist?
• What business process depends on this asset?

Failure cannot be understood until the intended function is clearly defined.

Identifying Functional Failures#

A functional failure occurs when the asset cannot perform its intended function.

Examples:

• Pump cannot maintain required flow.
• Motor cannot produce required torque.
• Conveyor cannot transport product.
• Compressor cannot maintain system pressure.

Functional failures become the starting point for identifying failure modes.

Identifying Failure Modes#

Failure modes describe how the functional failure occurs.

Examples include:

• Bearing fatigue
• Seal leakage
• Gear tooth wear
• Shaft misalignment
• Loose electrical connection
• PLC communication failure
• Belt breakage
• Corrosion

Failure modes should be specific enough to support maintenance decisions.

Failure Effects#

Failure effects describe what happens when the failure mode occurs.

Examples:

• Production stops
• Product quality declines
• Safety device becomes unavailable
• Equipment overheats
• Energy consumption increases
• Environmental release occurs

Understanding effects helps determine business impact.

Failure Consequences#

Failure consequences evaluate the significance of the failure.

Consider:

• Safety
• Environmental impact
• Regulatory compliance
• Production loss
• Customer impact
• Maintenance cost
• Asset damage

Consequences influence maintenance strategy selection.

Severity Rating#

Severity measures the seriousness of the failure consequences.

Typical scale:

1–3 Minor impact

4–6 Moderate impact

7–8 Major operational impact

9–10 Catastrophic safety, environmental, or business impact

Severity should evaluate the consequence—not the likelihood.

Occurrence Rating#

Occurrence estimates how frequently the failure mode is expected to occur.

Typical scale:

1–2 Extremely unlikely

3–4 Infrequent

5–6 Occasional

7–8 Frequent

9–10 Very frequent

Historical CMMS data should be used whenever possible.

Detection Rating#

Detection measures the likelihood of identifying the failure before it produces consequences.

Low number:

Failure almost certainly detected.

High number:

Failure unlikely to be detected before functional failure.

Detection should evaluate current controls—not future improvements.

Risk Priority Number (RPN)#

Many organizations calculate a Risk Priority Number.

Formula:

RPN = Severity × Occurrence × Detection

Higher RPN values indicate higher overall risk.

The RPN should support prioritization but should not replace engineering judgment.

High severity failures often deserve attention regardless of RPN.

Ranking Improvement Opportunities#

Recommended priorities include:

• High Severity failures
• High RPN values
• Safety risks
• Regulatory risks
• Critical assets
• Repeat failures
• High maintenance cost assets

Resources should focus on the greatest business risk.

FMEA Worksheet Structure#

A typical worksheet contains:

• Asset
• Function
• Functional Failure
• Failure Mode
• Failure Effect
• Failure Consequence
• Current Controls
• Severity
• Occurrence
• Detection
• RPN
• Recommended Action
• Action Owner
• Target Date
• Residual Risk

Standardized worksheets improve consistency and auditing.

Implementing FMEA#

Completing an FMEA worksheet is only the beginning.

Real value is created when the findings are converted into engineering, maintenance, and operational improvements.

Recommended implementation process:

1. Prioritize high-risk failure modes.
2. Assign action owners.
3. Implement corrective actions.
4. Update maintenance strategies.
5. Revise PM and PdM tasks.
6. Update engineering standards.
7. Verify effectiveness.
8. Recalculate risk.

An FMEA that never changes field execution provides little business value.

Integrating FMEA with Maintenance Strategy#

FMEA helps determine the most appropriate maintenance strategy for each failure mode.

Examples:

• Time-based Preventive Maintenance
• Predictive Maintenance
• Condition-Based Maintenance
• Run-to-Failure
• Failure Finding
• Equipment redesign

The objective is selecting the strategy that provides the greatest reduction in business risk.

FMEA and Preventive Maintenance#

Many PM tasks originate from FMEA.

Examples:

Failure Mode: Bearing lubrication breakdown

Recommended PM: Lubricate bearing every 2,000 operating hours using the approved procedure.

Failure Mode: Drive belt wear

Recommended PM: Inspect belt condition, alignment, and tension monthly.

Every PM task should address one or more documented failure modes.

FMEA and Predictive Maintenance#

FMEA identifies failure modes that can be detected before functional failure.

Typical technologies include:

• Vibration Analysis
• Infrared Thermography
• Oil Analysis
• Ultrasound
• Motor Circuit Analysis

FMEA helps justify where PdM technologies provide the highest value.

FMEA and Root Cause Analysis#

FMEA is proactive.

Root Cause Analysis is reactive.

FMEA asks:

"What could fail?"

RCA asks:

"Why did it fail?"

The two processes strengthen one another.

Recurring RCA findings should update future FMEAs.

FMEA and Reliability-Centered Maintenance#

Reliability-Centered Maintenance uses FMEA information to determine whether proactive maintenance is technically feasible and economically justified.

FMEA provides:

• Failure modes
• Failure effects
• Failure consequences
• Risk information

RCM converts that information into maintenance decisions.

FMEA and CMMS#

The CMMS should support FMEA by storing:

• Failure modes
• Failure codes
• Components
• Asset history
• PM tasks
• PdM inspections
• Corrective actions
• Equipment criticality

Reliable CMMS data improves future FMEAs.

Tracking Improvement Actions#

Each recommended action should include:

• Description
• Responsible owner
• Priority
• Target completion date
• Current status
• Verification method
• Residual risk review

Tracking actions is as important as identifying risks.

Verifying Risk Reduction#

After improvements are implemented, verify:

• Failure frequency decreased.
• Downtime decreased.
• Repeat failures declined.
• PM effectiveness improved.
• PdM findings increased.
• Asset availability improved.

Recalculate Severity, Occurrence, Detection, and RPN where appropriate.

Auditing FMEA#

Periodic audits should confirm:

• Critical assets have current FMEAs.
• Ratings are consistently applied.
• High-risk actions are completed.
• PMs align with failure modes.
• PdM technologies target documented risks.
• FMEAs reflect actual operating conditions.
• Lessons learned have been incorporated.

Case Study#

The following is an illustrative composite drawn from common patterns across maintenance organizations, not a specific documented case.

A packaging facility completed an FMEA on a critical conveyor system.

The analysis identified gearbox bearing contamination as a high-risk failure mode.

Recommended improvements included:

• Improved seals
• Oil analysis program
• Breather upgrades
• Lubrication procedure revisions
• Precision alignment

Within one year:

• Gearbox failures declined significantly.
• Downtime was reduced.
• Maintenance costs decreased.
• Equipment availability improved.

The greatest improvement came from reducing risk before failures occurred.

Continuous Improvement#

FMEAs should be reviewed after:

• Major failures
• RCA completion
• Equipment redesign
• Capital projects
• Process changes
• Significant PM revisions
• Annual reliability reviews

FMEA is a living document that should evolve with equipment knowledge.

Related Concepts for Future Expansion#

These related concepts may become separate Knowledge Library records or supporting resources later. They are listed as conceptual extensions only, not as claims that public pages or tools currently exist:

• Risk Priority Number (RPN)
• Severity Ratings
• Occurrence Ratings
• Detection Ratings
• Design FMEA
• Process FMEA
• FMEA Facilitation
• Risk Registers
• Functional Analysis
• Reliability Decision Making
• Severity Assessment
• Occurrence Analysis
• Detection Controls
• Risk Priority Number
• Residual Risk
• FMEA Worksheets
• Risk-Based Decision Making
• Residual Risk Management
• Reliability Improvement Actions
• FMEA Auditing
• Action Tracking
• Risk-Based Maintenance
• Engineering Controls
• Maintenance Optimization
• Reliability Governance

Industry Applications#

Food Manufacturing#

FMEA helps food manufacturers identify equipment and process risks before they result in product loss, food safety concerns, or unplanned downtime.

Typical applications include:

• Refrigeration systems
• Packaging equipment
• Process pumps
• Conveyors
• Steam systems
• Utilities

FMEA supports both reliability and regulatory compliance.

Distribution and Warehousing#

Distribution facilities commonly apply FMEA to:

• Conveyor systems
• Sortation equipment
• Dock levelers
• Forklifts
• Battery charging systems
• HVAC systems

The objective is reducing shipping interruptions and improving operational reliability.

Municipal Utilities#

Utilities use FMEA to evaluate:

• Pumps
• Lift stations
• Blowers
• Chemical feed systems
• Electrical distribution
• Standby generators

FMEA supports uninterrupted public service and regulatory compliance.

Commercial Facilities#

Typical applications include:

• HVAC equipment
• Boilers
• Chillers
• Cooling towers
• Fire protection systems
• Elevators
• Building automation

Small Manufacturing#

Small manufacturers should prioritize FMEA on equipment that directly impacts production capacity, customer deliveries, and safety.

FMEA for Small Business Owners#

Small businesses rarely require formal engineering-level FMEAs.

However, the same concepts can be applied by asking:

• What can fail?
• What happens if it fails?
• How serious would the impact be?
• Can the failure be detected early?
• What simple action reduces the risk?

This approach helps prioritize limited maintenance resources.

FMEA Maturity Model#

Level 1 — Reactive#

• Failures repaired after breakdown
• No formal risk assessment

Level 2 — Developing#

• Informal identification of common failure modes
• Limited documentation

Level 3 — Managed#

• Standard FMEA process
• Cross-functional participation
• Risk-based maintenance decisions
• Action tracking

Level 4 — Optimized#

• Enterprise FMEA standards
• Continuous updates from RCA
• Integrated with Reliability Engineering and RCM
• Risk reduction measured over time

FMEA KPIs#

Recommended metrics include:

• High-Risk Failure Modes Identified
• High-Risk Actions Completed
• Average Risk Priority Number (RPN)
• Residual Risk Reduction
• Repeat Failure Rate
• PM Tasks Created from FMEA
• PdM Tasks Created from FMEA
• Corrective Actions Completed
• FMEA Review Compliance
• Critical Assets with Current FMEA

KPIs should demonstrate measurable reductions in operational risk.

Common Mistakes#

Organizations frequently:

• Complete FMEAs only for compliance.
• Skip cross-functional participation.
• Assign inconsistent ratings.
• Ignore high-risk recommendations.
• Never review completed FMEAs.
• Fail to integrate findings into PM and PdM.
• Focus only on RPN while ignoring high-severity failures.
• Treat FMEA as a one-time exercise.

Best Practices#

• Define asset functions before evaluating failures.
• Build FMEAs from documented failure modes.
• Use actual maintenance history whenever possible.
• Standardize rating criteria.
• Review FMEAs after major failures.
• Integrate findings into maintenance strategies.
• Track corrective actions to completion.
• Update FMEAs as equipment and operating conditions change.
• Use FMEA to support capital planning and design improvements.

Recommended Action Documentation#

Each recommendation coming out of Ranking Improvement Opportunities above should include:

• Description
• Responsible owner
• Target completion date
• Expected risk reduction
• Required resources
• Verification method

FMEA Governance#

Failure Modes and Effects Analysis should operate under documented governance with clearly defined responsibilities, review requirements, and engineering standards.

Governance should establish:

• Program ownership
• FMEA selection criteria
• Team responsibilities
• Review frequency
• Documentation standards
• Approval authority
• Continuous improvement expectations

A governed FMEA program ensures consistency across assets and facilities, and connects to Auditing FMEA above.

Potential Future Resource Concepts#

The items below are potential future resource ideas for roadmap and planning purposes. They are not existing Reliability Method products, features, or services.

Templates#

• FMEA Worksheet
• FMEA Facilitation Guide
• Risk Register
• Action Tracking Log
• Severity Rating Matrix

Calculators#

• Risk Priority Number Calculator
• Residual Risk Calculator
• Criticality Calculator
• Risk Reduction Calculator

Potential Future AI Tool Concepts#

• FMEA Assistant
• Failure Mode Generator
• Risk Ranking Advisor
• Maintenance Strategy Recommender
• Action Plan Generator

Potential Future Facility Manager Concepts#

• FMEA Module
• Risk Register
• Failure Mode Library
• Action Tracking Dashboard
• Residual Risk Reporting
• Reliability Analytics

Training#

• FMEA Fundamentals
• Advanced FMEA Facilitation
• Risk Assessment Workshop
• Maintenance Strategy Selection
• Reliability Engineering Applications

Consulting#

• FMEA Facilitation
• Risk Assessments
• Maintenance Strategy Optimization
• Reliability Improvement Planning
• Asset Criticality Workshops

Related Knowledge Topics#

• Reliability Engineering
• Failure Modes
• Root Cause Analysis
• Reliability-Centered Maintenance
• Preventive Maintenance
• Predictive Maintenance
• Asset Criticality Analysis
• Maintenance Strategy
• Work Order Management
• CMMS Fundamentals

References#

• SMRP Body of Knowledge
• ISO 55000 — Asset Management
• ISO 14224 — Reliability and Maintenance Data
• SAE JA1011
• SAE JA1012
• IEC 60812 — Failure Modes and Effects Analysis (FMEA and FMECA)
• OEM Maintenance Documentation
• Reliability Method Internal Standards

Revision History#

Version 1.0 Initial FMEA foundation created.

Version 1.1 Expanded methodology, ratings, implementation, and maintenance integration.

Version 1.2 Completed industry guidance, maturity model, KPIs, product alignment, references, and revision history.

Version 1.3 Merged unique content (Recommended Action Documentation, FMEA Governance) from the retired duplicate record `failure-modes-and-effects-analysis-fmea-kn-8003` into the main article flow; removed redundant overlapping subsections.

Version 1.4 Removed internal merge notes from article flow and reframed knowledge-graph/product-roadmap language for public-release preparation.