FMEA – Failure Mode and Effects Analysis

Revision as of 14:59, 9 May 2023

Abstract

Failure Mode and Effect Analysis (FMEA) is a widely used technique for identifying and mitigating potential failures in products, systems, and processes ^[1]. FMEA is used in various industries, including automotive, aerospace, medical devices, and electronics, to minimize the risk of product and process failures ^[2]. The structured approach helps to first identify the potential failure modes, whose influence and probability of occurrence is then evaluated. This information is then further used to prioritize and implement corrective actions that reduce the risk of the failure modes occurring. The benefits of FMEA include identifying potential sources of defects in a product or process, reducing risks and costs through early defect detection and correction, improving the quality and reliability of products and processes, and assisting in decision-making and prioritization of improvement actions ^[3]. There are several types of FMEA, including Design FMEA, Process FMEA, and System FMEA, each of which targets specific aspects of a product or process. Design FMEA focuses on potential sources of failure in the design process, while process FMEA targets sources of failure in the production process. System FMEA examines the entire system and identifies potential failure sources that can impact the entire system ^[4].

This article provides a comprehensive overview of FMEA, including its origin, the different types of FMEA, the steps involved in conducting an FMEA, an example of application, and the benefits and limitations of an FMEA.

Definition and Origin

FMEA stands for "Failure Mode and Effects Analysis". The step-by-step approach is a quality management tool for analyzing and identifying possible failure modes in a system as well as their causes and effects (DIN EN 60812:2006-11., 2006). It is used to determine the ways in which a product or process can fail, estimate the risk associated with specific causes and prioritize the actions that should be taken to reduce the risk (Schulze et al., 2011). Through the application of FMEA, project managers may detect possible issues at an early stage of product or process development and take action to evaluate, reduce, and eliminate risks. This process contributes to a functioning quality management system in which the cost of eliminating errors and the impact of an error are minimized (Brüggemann & Bremer, 2015, p. 29–31).

FMEA found its beginnings when the U.S. military developed a method called „Procedures for Performing a Failure Mode, Effects and Criticality Analysis” to inspect their equipment in 1949 (Werdich, 2012). The term itself was created by NASA. The tool was widely used in 1963 when the first moon landing occurred. The application of FMEA contributed to NASA's success (KVP Institut GmbH, 2018). Ford introduced the quality management tool to the automotive industry in 1977. At that time Ford was driven to use FMEA after the gasoline tank of the Ford Pinto model experienced issues with light vibrations. This launched the tool's extensive use in the automotive sector. Manufacturers used various procedures and internal corporate norms at the time because there was no standard guideline (Werdich, 2012, p. 7).

The German Association of the Automobile Industry (VDA) first gathered the various standards together and established a standard that was subsequently applied in the businesses. FMEA was no longer limited to the automotive industry once the German Association for Quality (DGQ) issued a universal and industry-independent explanation of the tool in 1990. Among others, it was then used in the field of services and project management (Werdich, 2012, p. 6-7). Subsequently, the standard was given a more thorough definition. In order to provide a globally consistent standard, the VDA standard and the Automobile Industry Action Group standard were aligned in 2019 (KVP Institut GmbH, 2018).

Types of FMEA: Design FMEA and Process FMEA

Among other things, a distinction is made between Design- and Process-FMEA. While the Design-FMEA (DFMEA) is used to find failures in the design of a product, the Process-FMEA (PFMEA) analyzes possible errors in new or existing processes (Brüggemann et al., 2015).

The Design FMEA or DFMEA, is applicable to the development, design and planning of a product, particularly during the early stage or end-stage of the development of a new product. Nevertheless, DFMEA can also be used to correct already existing products. The goal of DFMEA is to uncover potential failures in the design of the individual components of a product and evaluate possible errors on the basis of development specifications which could have a negative impact on health, safety and the environment. The System-FMEA, which is a variant of the DFMEA does not examine individual components but the entire system with regard to the functional interaction of the individual parts (Brüggemann et al., 2015).

The Process FMEA or PFMEA has the goal to uncover risks within a new or an existing process. It is used in particular for the investigation of manufacturing and assembly processes in the context of product development but also in the service and project management area. PFMEA is carried out before a new process is implemented or before changes made to existing processes take effect. Both scenarios for doing PFMEA intend to find any risks that could negatively impact the product, quality, safety, and customer satisfaction (Brüggemann et al., 2015).

FMEA Process

There are seven steps in the process of performing an FMEA. The various steps are handled systematically and in chronological order. This framework allows multiple FMEAs to be compared due to the creation of an understandable and transparent approach (Werdich, 2012, p. 21).

The following lists and explains each of the seven steps in detail.

Planning and preparation (1)

Every FMEA starts with the planning and preparation phase. Here, it is first specifically determined which production area the FMEA will examine and what outcomes or insights are expected from the FMEA. At this step, expectations for the investigation subject are defined in terms of the desired characteristics and functions. In order to prevent future issues with specific questions that are unrelated to the intended goal, the desired level of detail for the FMEA and the expected depth should also be determined (Werdich, 2012, p. 23–31). The organization of the project team that will conduct the FMEA is a key component of the planning. Depending on the type of FMEA and the subject of examination, experts from various departments should be chosen for this task to ensure a range of perspectives and approaches. Professionals from research and development, design, production, and quality assurance will often be involved. Representatives of the supplier and the customer may also be invited if processes are being looked into in which they have a key role. A firm representative who is already familiar with the FMEA approach acts as the project team's leader and leads the group through each phase and takes over the time management (Brüggemann & Bremer, 2015, p. 47).

Structure Analysis (2)

Function Analysis (3)

Failure Analysis (4)

Risk Analysis (5)

Optimization (6)

Results Documentation (7)

Example of application

Benefits and Limitations

Benefits

Limitations

Annotated Bibliography

References

1. ↑ Stamatis, D. H. (2013). Failure mode and effect analysis: FMEA from theory to execution. ASQ Quality Press.
2. ↑ Annarelli, A., & Sperandini, A. (2016). FMEA: A practical guide to Failure Mode and Effects Analysis. Springer.
3. ↑ Schulze, S, & Schultmann, F. (2011). Falure Mode and Effects Analysis (FMEA) from theory to execution. John Wiley & Sons.
4. ↑ Vose, D. (2008). Risk analysis: A quantitative guide. John Wiley & Sons.

Cite error: <ref> tag with name "Brueggemann" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "DIN" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "Werdich" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "Agile" defined in <references> is not used in prior text.