FMEA

Failure Mode and Effects Analysis (FMEA) is an industrial strength risk assessment tool which gives a step-by step approach to recognize and evaluate all potential failures in a design manufacturing or assembling process of a product or a process. FMEA identifies actions that could eliminate or reduce the chances of the occurrence of the potential failure and tracks the corrective actions and their effects. It also document the entire decision process

FMEA can be viewed as an assessment tool, as it is used to diagnose the opportunities or as a prevention tool, as it used to prevent high level risks.

Purpose of FMEA

The purpose of FMEA is to recognize and evaluate the failure and the effects that failure has on the system and take actions to eliminate or reduce failures, starting with the highest-priority failures. FMEA also aims to reduce the time and cost of the operation by improving the teamwork and promoting accountability.

Elements of FMEA

FMEA consists of following elements, as

Severity(S) – Severity is the worst potential outcome of a failure, which is determined by the degree of injury, system damage etc. Severity is the impact of failure, numbers from 1 to 10 are assigned to each failure effect, where 1 refers to the failure with no/slight effect and 10 refers to that failure with most critical effect with most critical effect. The range of Severity is 1 <S <10. The following table gives the different values in the Severity scale and corresponding effects.

RankEffect
10Hazardous without warning
9Hazardous with warning
8Very High
7High
6Moderate
5Low
4Very Low
3Minor
2Very Minor
1None

Occurrence (O) – Occurrence refers to the number of times a cause of a failure will occur. Occurrence is considered to be a design weakness, numbers from 1 to 10 are assigned to each failure, where 1 refers to that failure which is unlikely to occur and 10 refers to that failure which is most likely to occur failure which is most likely to occur The range of Occurrence is 1 <O <10. The following table represents the different values in occurrence scale and the corresponding effect.

RankEffect
10Very High (1 in 2)
9Very High (1 in 3)
8High(1 in 8)
7High(1 in 20)
6Moderate(1in 80)
5Moderate (1 in 400)
4Moderate (1 in 2,000)
3Low(1 in 15,000)
2Low( 1 in 150,000)
1Remote ( 1 in 1,500,000)

Detection (D)– Detection refers to the ability of designed checks and inspections to detect and remove defects of failure modes. Numbers from 1 to 10 are assigned to each failure effect, where 1 refers to that failure which is easy to detect and 10 refers to that failure is easy to detect and 10 refers to that failure which is almost certain that we can’t detect. The range of detection is 1 <D <10. The following table represents the different values in the detection scale and the corresponding effect.

RankEffect
10Absolute Uncertainty
9Very Remote
8Remote
7Very low
6Low
5Moderate
4Moderately High
3High
2Very High
1Almost Certain

Important FMEA Terms

  • Risk Priority Numbers (RPN) – RPN is the product of severity(s), Occurrence (O) and Detection (D). The range of RPN is 1 <RPN <1000. It is calculated as    RPN = Severity x Occurrence x Detection
  • Failure effect – Failure effect refers to the consequence of a failure mode on the part of the product/process as perceived by the internal and external customers
  • Failure mode – Failure mode refers to the manner in which a component, subsystem, system, process, etc. probably fails to adhere to the design intent.
  • Failure cause – Defects in plan, process, quality, etc. that result in a failure or initiate a process that leads to failure.

Important Measures

  • RPN has to be calculated for the entire process
  • Highest priority is given to that failure with highest RPN, since higher the RPN values higher the risks involved
  • We should consider the less RPN values in some cases, because there can be some failures which are less severe and less detective but occurs most often.

FMEA Procedure

The basic procedures involved in FMEA are listed below

  • The first step in the FMEA methodology is to describe the product/process and its functions.
  • Create a block diagram which includes all major components of the product/process. Connect the blocks logically.
  • Identify the failure modes in terms of component, subsystem, system, process, etc.
  • Identify the effects of failure mode on the product/process as perceived by the internal and external customers.
  • Assign severity – Numbers from 1 to 10 can be used to rank the severity of the effects.
  • Brainstorm the root causes of the failure – the sources for each failure mode have to be discovered and recorded.
  • Occurrence – This is followed by entering the probability factor, which is the numerical weight assigned to each failure mode effect cause, indicating ‘the probability that the failure mode effect cause may occur’.
  • The next step is to identify the current controls. Current Controls are the devices that detect and check the failure mode causes from occurring before the customer gets access to the product or service.
  • Detection – Likelihood of detection has to be ascertained in this step. Detection refers to the probability that the current controls will detect the cause of the failure mode before the customer gets access to the product.
  • Calculate RPN – After ascertaining the likelihood of detection, the Risk Priority Number (RPN) has to be created and reviewed. RPN is the product obtained after multiplying severity, probability, and detection ratings. RPN = (Severity) x (Probability) x (Detection). The RPN is used to rank the items that require supplementary quality planning or corrective measures.
  • Recommend actions – This is followed by determination of recommended actions to deal with potential failures that have a high RPN.
  • Document changes of RPN – After the recommended actions are implemented, the implemented actions have to be documented. This can be used to reassess the severity, probability, and detection and review the revised RPNs. This is done to explore the possibility of the requirement of supplementary actions.
  • Review Periodically – Finally, the FMEA has to be updated as and when the design or process changes or the assessment changes or new information becomes known. FMEA is an ongoing activity
Share this post
[social_warfare]
Maintenance Optimization
Financial Management Basics

Get industry recognized certification – Contact us

keyboard_arrow_up