FMEA as tool in Project Management
| Line 21: | Line 21: | ||
== Big Idea == | == Big Idea == | ||
=== What is FMEA - Evolution of FMEA === | === What is FMEA - Evolution of FMEA === | ||
| + | Failure mode and effects analysis can be characterized as an easy to implement and yet powerful pro-active engineering quality method that helps to identify and counter the weak points in the early conception phase of products and processes [4]. In other words, FMEA is a systematic method / predictive maintenance method which allows to evaluate a process to identify where and how it might fail, identify and ranking the risks associated with various product (or process) failure modes (both existing and potential), prioritizing them for remedial action, acting on the highest ranked items, revaluating those items and returning back to the prioritizing step in a constant loop until marginal returns set in [5]. FMEA is trying to anticipate potential problems before they occur, so it can be said that, from a time perspective FMEA is essential in the earliest development phases and thus, an early and accurate implementation of the method can be crucial for reducing the corrective actions as well eliminating the cost of a non-compliance identification. The measures that are taken into consideration when FMEA is being implemented is: the probability of failure occurrence (O), the severity of the failure (S) and finally the capacity to detect the failure before it occurs – detection (D) [4]. The multiplication of these measures generates the RPN (RPN = Occurrence * Severity * Detection). The special and professional workforce that will implement the FMEA consists of a multidisciplinary team of people from different educational backgrounds and areas (design, management, engineering, manufacturing) skilled with specific product / process know how. | ||
| + | |||
| + | The first application of FMEA dates back to the end of 1940s when the US Army used it in the aeronautic sector in order to solve safety and reliability problems in the production and design phases. After this, NASA continued the implementation of FMEA in the early 1960s through the Apollo Program and some years later, FMEA adopted by the automotive industry and specifically from Citroen and Peugeot. In 1993 AIAG incorporates FMEA into the QS9000 and since then, this technique is usefulness for all organizations. | ||
| + | |||
| + | FMEA can be divided in sub methods throughout the product development phases. For example, DFMEA (Design Failure Mode & Effects Analysis) is used to create new products and analyze product designs before they are released to production. It focuses on potential failures and problems that can be occurred through the design process. On top of that, PFMEA (Process Failure Mode & Effects Analysis) is used to identify and examine risk in process changes and problems with the function of a product caused by the problem in the process. SFMEA (Software Failure Mode & Effects Analysis) focuses on identifying the causes and consequences of possible software failure modes. Last but not least, RFMEA (Risk Failure Mode & Effects Analysis) focuses on the risk contingency planning required early in the project on critical risks. RFMEA will be analyzed in detail throughout the article. | ||
| + | |||
=== Why FMEA === | === Why FMEA === | ||
=== FMEA as a Project Risk Managemnt Tool === | === FMEA as a Project Risk Managemnt Tool === | ||
Revision as of 20:15, 7 February 2022
Author: Periklis Aprilis
Contents |
Abstract
In our days, with the constant surge of global competition and the globalization of markets, the success of project implementation and management depends largely from the organization’s business performance. These affairs have brought many changes in terms of economic, technological and marketing basis. The investment and implementation of a new technology requires a serious effort from the organization because most of the times, deals with factors such as risk, complexity, innovation and lacking of resources. All these factors, among others, can be considered as extremely important challenges from the special workforce of the companies, that’s why it is very common for them to set up and implement new special projects in order to face them as effective and as quick as possible [1,2].
Based on that, identifying and alleviate project risks are very important steps in achieving successful project management and therefore successful projects programs and portfolios. Nevertheless, methods and tools for risk assessment and risk management that have been developed and implemented to increase the possibilities of project success are not yet extensive or easily adopted [3]. However, one of the most well-known and widespread methods is the method called Failure Modes and Effects Analysis (FMEA). FMEA as Project Management tool allows to:
•Evaluate a process to identify where and how it might fail
•Identify the failure causes
•Assess the relative impact of different failures
•Anticipate potential problems before they occur
On top of that, it is generally accepted that when FMEA is used as a Project Risk Management tool, it can be labeled also as project risk FMEA or RFMEA. So, the RFMEA technique is not just another way of analyzing project risks but helps focus the risk contingency planning, required early in the project on critical risks [3]. Finally, this method is highlighted as crucial and important in the engineering management community.
Big Idea
What is FMEA - Evolution of FMEA
Failure mode and effects analysis can be characterized as an easy to implement and yet powerful pro-active engineering quality method that helps to identify and counter the weak points in the early conception phase of products and processes [4]. In other words, FMEA is a systematic method / predictive maintenance method which allows to evaluate a process to identify where and how it might fail, identify and ranking the risks associated with various product (or process) failure modes (both existing and potential), prioritizing them for remedial action, acting on the highest ranked items, revaluating those items and returning back to the prioritizing step in a constant loop until marginal returns set in [5]. FMEA is trying to anticipate potential problems before they occur, so it can be said that, from a time perspective FMEA is essential in the earliest development phases and thus, an early and accurate implementation of the method can be crucial for reducing the corrective actions as well eliminating the cost of a non-compliance identification. The measures that are taken into consideration when FMEA is being implemented is: the probability of failure occurrence (O), the severity of the failure (S) and finally the capacity to detect the failure before it occurs – detection (D) [4]. The multiplication of these measures generates the RPN (RPN = Occurrence * Severity * Detection). The special and professional workforce that will implement the FMEA consists of a multidisciplinary team of people from different educational backgrounds and areas (design, management, engineering, manufacturing) skilled with specific product / process know how.
The first application of FMEA dates back to the end of 1940s when the US Army used it in the aeronautic sector in order to solve safety and reliability problems in the production and design phases. After this, NASA continued the implementation of FMEA in the early 1960s through the Apollo Program and some years later, FMEA adopted by the automotive industry and specifically from Citroen and Peugeot. In 1993 AIAG incorporates FMEA into the QS9000 and since then, this technique is usefulness for all organizations.
FMEA can be divided in sub methods throughout the product development phases. For example, DFMEA (Design Failure Mode & Effects Analysis) is used to create new products and analyze product designs before they are released to production. It focuses on potential failures and problems that can be occurred through the design process. On top of that, PFMEA (Process Failure Mode & Effects Analysis) is used to identify and examine risk in process changes and problems with the function of a product caused by the problem in the process. SFMEA (Software Failure Mode & Effects Analysis) focuses on identifying the causes and consequences of possible software failure modes. Last but not least, RFMEA (Risk Failure Mode & Effects Analysis) focuses on the risk contingency planning required early in the project on critical risks. RFMEA will be analyzed in detail throughout the article.
