FMEA Process
FMEA Process
FMEA Process
fashion since each step builds on the previous one. Here’s an overview of
the 10 steps to a Process FMEA.
Review existing documentation and data for clues about all of the
ways each component can failure.
The list should be exhaustive – it can be paired down and items can
be combined after this initial list is generated.
There will likely be several potential failures for each component.
The effect is the impact the failure has on the end product or on
subsequent steps in the process.
There will likely be more than one effect for each failure.
10 Steps of FMEA
In Chapter 8 of The Basics of FMEA by Robin E. McDermott, et. al. discusses the
ten steps for an FMEA. I find it to be an excellent summary for describing and
conducting a failure mode and effect analysis.
Therefore based on the work of McDermott and others, plus my own experience
here are the ten steps with my descriptions.
This can be a lot of fun. Use a variety of brainstorm techniques to get as broad a set
of ideas as possible. A good technique is to individually create ideas the collate
them using affinity grouping. Mix up the process with live brainstorming,
anchoring, and focused concerns (i.e. high temperature, user abuse, etc).
For most products, you may want to focus on one function or feature at a time.
Consider the possible failures and imagine what could then happen to the
surrounding environment and people.
For example, if a staircase handrail fails to provide support, it may result in the
effect of a staircase falling injury. Or, it may result in the closing of the staircase
for repair. Or, it may require a maintenance action to re-anchor the handrail.
Common practice is to assign 9 or 10 for those effects that cause injury or death, or
major damage to its surroundings.
Document the scale actually used so others can interpret the study results properly.
The worksheet includes a column of causes, which may help the team judge the
relative frequency of occurrence of failure modes. Keep in mind that a failure
mode may have many potential causes.
Detection can include one or both of the following methods for alerting of potential
failure.
1. During product development and manufacturing can we find the defect that
would lead to a failure? Can we find the problem before it is shipped?
2. During normal use does the product provide some means to detect an
upcoming failure?
I use the example of car brakes to illustrate. During design and manufacture, we
can test the brake assembly for braking force. If insufficient, we can redesign or
adjust the brake assembly before installation in a vehicle.
One failure mechanisms that leads to brake failure is the wearing away of the brake
pad. Therefore, the insertion of a piece of metal that creates a warning sound
before the brake pads have worn too far, alerts the vehicle operator to replace the
brake pads before brake failure occurs.
Items that high dire consequences (high severity), occur often and provide no
warning result in the highest RPN numbers relative to other potential failures.
The idea is to do something with the study. The prioritized list provides a guidance
document that the entire team can use to focus on the highest risk areas first.
While the basic steps for conducting an FMEA are the same regardless of
the focus of the FMEA, some of the tactics are different if it is a DFMEA or
PFMEA. This table highlights the key differences between the two.
To uncover potential
To uncover potential process
failures associated with the
failures that can:
product that could cause:
Impact product quality.
Product
Reduce process
Primary malfunctions.
reliability.
Objectives Shortened product
Cause customer
life.
dissatisfaction.
Safety hazards
Create safety or
while using the
environmental hazards.
product.
prototype.