Failure Mode and Effect Analysis (FMEA) is a structured way to find and fix possible problems before they cause harm. The method looks at how a product, process, or system might fail and how those failures will affect the business.
By examining each possible failure and rating its severity, occurrence, and detection, you can address high-risk issues before they happen.
FMEA started in the United States military. Procedures for a more detailed failure mode and effect and criticality analysis (FMECA) were described in 1949 in the MIL-P-1629 military procedures document.
NASA adopted FMEA in the 1960s for space programs. Since then, industries such as automotive, aerospace, medical devices, renewable energy, and consumer electronics have used FMEA to improve quality and safety.
A proactive FMEA can reduce costs and increase reliability. A 2025 industry guide notes that identifying risks early can cut warranty claims by about 20 % and reduce production delays by fixing design flaws before manufacturing. Another reliability study reports that using a risk-based maintenance strategy lowers expenses linked to rework, recalls, and warranty claims.
These figures show how effective FMEA can be when it is part of a quality management system.
What Is FMEA?
Failure Mode and Effect Analysis (FMEA) is a systematic technique used to identify potential failure modes in a design, process, or system and evaluate the effects of those failures on users or operations.

A failure mode describes how something can fail, such as breaking, leaking, or providing wrong information. An effect explains what happens when a failure occurs, such as a machine stopping working, a product being defective, or a customer being dissatisfied.
FMEA documents each failure mode, its cause, its effect, and the current controls in place to detect or prevent it. By assigning ratings for severity, occurrence, and detection, teams calculate the Risk Priority Number (RPN) to prioritize actions. The goal is to reduce or eliminate high-risk failure modes.
FMEA differs from general risk analysis because it looks deeply at specific failure points and applies structured ratings. This makes it useful for design reviews, process improvement, and preventive maintenance.
History and Evolution of FMEA
- Military Origins: In 1949, the U.S. Armed Forces published MIL-P-1629, a procedure for conducting Failure Mode, Effects, and Criticality Analysis (FMECA). This document aimed to predict component failures in weapons and reduce risks.
- NASA Adoption: By the early 1960s, NASA used FMEA and its variations in programs such as Apollo, Viking, and Voyager. The method helped engineers analyze complex spacecraft systems.
- Spread to Industry: The civil aviation industry adopted FMEA in the late 1960s, and by the 1970s, it was common in automotive and manufacturing sectors. Standards such as ARP926, ARP4761, and the AIAG/VDA FMEA handbook now guide implementation.
- Modern Use: Today, FMEA is part of many quality management and reliability programs. It supports industry standards like ISO 9001, ISO 13485 (medical devices), and IATF 16949 (automotive). Advancements in software make it easier to track and update FMEA data.
What is the Importance of FMEA?
Using FMEA offers several benefits for projects and organizations:
- Enhanced Reliability: Early identification of potential failure points allows engineers to correct issues before products reach customers. This improves reliability.
- Cost Reduction: Spotting risks during design reduces expenses associated with recalls, warranty claims, and reputation damage. Proactive analysis can cut warranty claims by about 20%.
- Improved Safety: FMEA focuses on the consequences of failures, helping organizations avoid accidents in high-risk industries like automotive and aerospace.
- Regulatory Compliance: Many standards require documented risk analysis. FMEA helps meet these requirements and demonstrates due diligence.
- Continuous Improvement: Recording failure modes and corrective actions supports a culture of improvement. It also creates a knowledge base for future projects.
- Team Collaboration: The process brings together cross-functional teams (engineering, manufacturing, quality, supply, customer service) to share insights and build consensus..
Types of FMEA
Various types of FMEA focus on detecting and reducing potential failures in design, process, or system operations before they occur.

The following different types of FMEA address unique stages of the product or process life cycle:
1. Design FMEA (DFMEA)
DFMEA focuses on identifying failure modes in product or system design before production. It considers material properties, tolerances, geometry, and design features that could cause problems. DFMEA helps improve reliability and performance by addressing issues early.
Common design failure factors:
- Incorrect tolerances or dimensions
- Weak materials or wrong material selection
- Complex geometry that increases stress
- Unintended interactions between components
2. Process FMEA (PFMEA)
PFMEA examines potential failures during manufacturing, assembly, or service processes. It looks at machinery, people, procedures, and environment. By finding process-related failures, PFMEA helps ensure consistent quality and reduces defects.
Common process failure factors:
- Human errors or operator mistakes
- Equipment malfunctions or incorrect settings
- Inadequate procedures or training
- Poor inspection methods
3. System FMEA (SFMEA) or Functional FMEA
System FMEA analyses interactions among subsystems or functions. It is helpful for complex products like aircraft or power plants. SFMEA explores how failures in one subsystem can affect the whole system, ensuring that safety functions remain reliable.
FMEA Process Step-by-Step
The FMEA Process shows how to uncover failure modes, prioritize risks, and apply actions for continuous quality improvement.

You can follow the following steps to conduct FMEA for your process:
Step 1: Define the Scope and Assemble the Team
Start by defining the system, process, or product you will analyze. Gather a cross-functional team with design, production, and quality experts. Make sure everyone understands the goal, which is to identify potential failures before they occur. This step ensures that the analysis focuses on the right area and benefits from multiple perspectives.
Step 2: Identify Potential Failure Modes
List all possible ways a component, system, or process could fail. Use brainstorming, past data, or design reviews to find failure modes. Think about what could go wrong, how it could happen, and how often it might occur. Keep the list detailed enough to cover every key function and interface of the system.
Step 3: Analyze Effects and Causes of Each Failure
For every failure mode, describe its possible effects on the product, user, or process. Identify the root causes behind each effect. Assess how severe each effect could be, how often it may happen, and how easily it can be detected. This step helps visualize the full risk impact of each potential problem.
Step 4: Calculate the Risk Priority Number (RPN)
Assign numerical ratings for Severity (S), Occurrence (O), and Detection (D) on a scale of 1 to 10. Multiply these values to get the Risk Priority Number (RPN = S × O × D). A higher RPN shows greater risk. Rank failure modes based on their RPN values to decide which issues need urgent corrective action.
Step 5: Develop and Implement Corrective Actions
Create and apply action plans to reduce or eliminate high-risk failure modes. Focus on reducing severity, lowering occurrence, or improving detection. Update the FMEA sheet once actions are complete. Recalculate RPNs to confirm improvement. Share the results with all stakeholders and maintain FMEA as a living document for future updates.
Risk Priority Number (RPN)
The Risk Priority Number helps rank failure modes for action. It is calculated as:
RPN = Severity × Occurrence × Detection
- Severity (S): Rate the impact of the failure on the user or system. A score of 1 means negligible effect; 10 means catastrophic.
- Occurrence (O): Rate how often the failure is expected to happen. A score of 1 means extremely unlikely; 10 means very likely.
- Detection (D): Rate how well existing controls detect the failure. A score of 1 means easy to detect; 10 means difficult to detect.
Multiply these three numbers to obtain the RPN. The maximum RPN is 1,000 (10×10×10). High RPNs indicate failure modes that require urgent attention. Reducing severity, occurrence, or detection ratings lowers the RPN.
FMEA Example
The table below shows a simplified FMEA for an equipment failure in a workshop. The project team listed the failure mode, assigned ratings, and suggested corrective actions.
| Function | Failure Mode | Effect (Impact) | Severity (S) | Cause | Occurrence (O) | Detection (D) | RPN | Recommended Action |
| Hammer drill | The tool breaks during use | Production stops; potential injury | 9 | Hard rock encountered | 3 | Detect a break by listening for unusual noise | 81 | Repalce the tool. |
| Conveyor belt | Motor overheats | Belt stops, causing a production halt | 8 | Dust buildup is blocking ventilation | 4 | Inspection only when a breakdown occurs | 160 | Add temperature monitoring sensors to detect early overheating & regular visual check. |
To prioritize actions, the team compares RPNs. The conveyor belt has a higher RPN (160), so improving maintenance and detection is a priority.
Limitations of FMEA
While FMEA is valuable, be aware of its limitations:
- Time-Consuming: Conducting a thorough FMEA can be slow, especially for complex systems.
- Relies on Existing Knowledge: It identifies known or anticipated failure modes and may miss unknown issues.
- Subjective Scoring: Severity, occurrence, and detection ratings depend on team judgment and may vary.
- Limited Scope: FMEA focuses on failures; it does not evaluate positive improvements or cost-benefit trade-offs.
- Needs Regular Updates: Without updates, the analysis becomes outdated and loses relevance.
Real-World Applications
FMEA is used across many industries:
- Automotive: Manufacturers use DFMEA and PFMEA to design safer vehicles and meet IATF 16949 standards. Analyzing brake systems prevents catastrophic failures.
- Aerospace: FMEA ensures spacecraft and aircraft systems meet strict reliability requirements. NASA has used FMEA since the Apollo program.
- Medical Devices: Regulatory bodies like the FDA require risk analysis. FMEA helps identify possible device failures and plan corrective actions.
- Manufacturing: PFMEA improves assembly lines by reducing downtime. A study notes that early identification of potential failures can slash warranty claims by 20 %.
- Energy and Utilities: System FMEA assesses safety instrumented systems in power plants. It reduces dangerous failures and supports proof test procedures.
- Consumer Electronics: Companies analyze battery packs, circuit boards, and connectors to avoid overheating, short circuits, and product recalls.
Frequently Asked Questions
Q1. What are the different types of FMEA?
There are three main types: Design FMEA analyzes product design, Process FMEA studies manufacturing or service processes, and System FMEA examines interactions between subsystems.
Q2. How long does FMEA take?
The duration depends on complexity. A simple design may take days, while a complex system could require weeks or months.
Q3. What is the Risk Priority Number (RPN)?
RPN is calculated by multiplying severity, occurrence, and detection ratings. Higher RPNs indicate higher risk and the need for quick action.
Q4. How often should FMEA be reviewed?
Review and update your FMEA whenever major design or process changes occur, new risks emerge, or at least annually for critical systems.
Q5. How does FMEA differ from general risk analysis?
Risk analysis is broad, covering all risks. FMEA is a structured method focusing on specific failure modes and their effects, using ratings to prioritize actions.
Conclusion
FMEA is a vital tool for identifying and preventing potential failures before they impact product quality, safety, or performance. By systematically analyzing risks in design, process, or systems, you can strengthen reliability, enhance customer satisfaction, and reduce costly issues.
Continuous use of FMEA promotes proactive thinking and supports a culture of quality improvement. When applied effectively, it helps teams anticipate problems early, prioritize corrective actions, and ensure long-term operational excellence across all stages of production.
Further Reading
- What is FMECA?
- What is Event Tree Analysis?
- What is Fault Tree Analysis?
- What is the Ishikawa Diagram?
- What is 5-Why Analysis?
References:
This topic is important from a PMP exam point of view.

I am Mohammad Fahad Usmani, B.E. PMP, PMI-RMP. I have been blogging on project management topics since 2011. To date, thousands of professionals have passed the PMP exam using my resources.

Excellent !! Very easy to understand.
Sir, I have done my Diploma in Mechanical Engineering & presently doing AMIE course. For AMIE course I have selected ‘Process FMEA for TATA Hybrid bus’ at ACGL-Goa as my project. Can I do project individually by collecting the required data from company or it is a team project?
I cannot say anything on it. Please consult with your mentor.
Very effective and so clear.thank you so much.examples are very clear to understand easily.
You are welcome Santhosh.
WOULD you please give an example for FMEA of an aircraft? or link of it?
Sorry Sara, I don’t have any FMEA on aircraft.
I especially liked the idea of linking risk to economic consequences.
One other problem I have run into over the years lies with the determination of occurrence When evaluating a new process or system, the true rate of failure is unknown.
If the team is composed of individuals with prior understanding of similar systems or historic performance, it is easy to estimate the new occurrence rating by examining historic experience. Often though, the default is to rank occurrence with a high number due to lack of experience.
In a risk adverse environment, the result is that high risk is everywhere due to high occurrence or detection numbers. The FMEA then becomes unmanageable and loses any advantage of prioritization.
http://manufacturing.cioreview.com/whitepaper/why-is-fmea-cost-effective-wid-577.html
Well said John.
Very good explanation.
Thanks Deepak for your comment.
Brief but comprehensive..Easy to understand..Thank u :-) Expecting more topics from you:-)
Thanks Jeya for your comment.
Let me know what topics you want me to write.
Welcome :) Could u pls write on APQP phases, Root cause analysis and Why-why analysis
I have noted your requests, will surely write blog posts on these topics.
Thank you..
Hi,
Can you please differentiate between occurrence and detection. According to me, occurrence means issue has occurred but not detected by people. Detection means issue occurred and also got detected . Please clarify
You are right.
Here the occurrence mean how many frequently this issue is likely to happen, and detection implies how easily you can detect it.
Excellent. Very short and to the point. Very easy to learn and implement. Please continue to educate us.
Thanks for your comment and visit Jay.
Nice topic. Well explained. Thanks
You are welcome Maan.
You have done a terrific job on preparing these blogs. Thank you for preparing them very concise and clear.
Thanks Sara for your comment.
Very clear and concise, thanks so very much.
You are welcome Bonos.
Very good session. simple and effective . thanks
You are welcome Mathew for stopping by and leaving your comment.
good and simple.
Thanks Venkatesh.
Very good session. simple and effective .
Thanks
You are welcome Varun.