Skip to content
FMEA and Control Plan | Part 1 of 6

What FMEA Does and When to Use It

What a process FMEA is, what it costs to find a failure late, when an FMEA is due and what the seven steps deliver.

Every failure is found at some point. The only question is who finds it and what it costs by then. An FMEA, failure mode and effects analysis, is the method that moves the finding to the earliest and cheapest moment: a meeting room, before the first part is made.

A structured conversation

A process FMEA asks three questions for every step of a process. What can go wrong? What happens then? Why could it happen? Each cause is rated, the ratings lead to a priority, and the priority leads to an action.

The form is the least important part. The value lies in the conversation between the people who know the process: the engineer who designed it, the setter who will run it, the maintenance technician who knows what wears, and the quality engineer who has read the complaints. Each of them knows failures the others have never seen.

What late costs

A plant makes hydraulic hose assemblies for mobile machinery. Its cell H1 produced 92,000 assemblies last year. A new cell H2 is planned for the same hose family. The figures of H1 show what the new cell will inherit if nothing changes:

Where the failure was found Cost
At the test bench: 460 rejects EUR 25 each
At the customer: 12 complaints EUR 3,500 each
Total per year EUR 53,500

The complaints were ordinary: leaks at the crimp, particles in the hose, wrong lengths, wrong fittings, a wrong label. Each could have been a line in an FMEA, with an action that costs less than one complaint.

And these are the cheap failures. A hose that comes off its fitting at 280 bar is not a complaint. It is an injury.

When an FMEA is due

  • New process, new product or new site. A full FMEA, started when the process concept exists and nothing is ordered yet. In the example that was 10 weeks before the start of production.
  • Changed process, material, tool or location. A review of the steps that change, before the change goes live.
  • Complaint or new failure. A review of the affected rows within two weeks. Was the failure in the FMEA? If not, why not?
  • Nothing happened for a year. A short review against the reject data, because occurrence ratings age.

The timing matters more than anything else. An FMEA written after the equipment is installed can only add checks. An FMEA written before the order can still change the fixture, the sensor or the sequence.

Seven steps

The current method, described in the joint handbook of the American and German automotive associations, has seven steps:

  1. Planning and preparation: scope, team, dates, data, rules.
  2. Structure analysis: the process, its steps and the work elements in each step.
  3. Function analysis: what each step must achieve, with a measurable requirement.
  4. Failure analysis: failure mode, effect and cause as a chain.
  5. Risk analysis: current controls, three ratings, action priority.
  6. Optimization: actions, proof of effect, new ratings.
  7. Results documentation: report to management, handover to the control plan.

Steps 1 to 3 look like paperwork and are the reason good FMEAs find what weak ones miss. A failure is a function that is not fulfilled. Without a written function, a failure is whatever somebody dislikes.

What comes out

For cell H2, six people needed five sessions of two hours. They found 24 failure causes in 7 process steps, gave 8 of them high priority and decided 12 actions for EUR 26,400. Six months after the start, the cell had 2 complaints in 46,000 assemblies and a reject rate of 0.20 percent instead of 0.50.

The Six Sigma series shows a short FMEA inside an improvement project. This series covers the full process FMEA for a new process and the control plan that follows from it. The next part starts with the scope, the team and the structure.

Newsletter

One Lean idea.
Every two weeks.