How to Do a PFMEA, Step by Step

To do a PFMEA, start from the process flow diagram and work one process step at a time. For each step, list its function and requirements, then the ways it can fail, the effect on the customer, and the cause. Rate severity, occurrence and detection on 1–10 scales, prioritise with Action Priority (or RPN if your customer still uses it), and assign actions that lower occurrence or improve detection. The AIAG & VDA FMEA Handbook organises this into seven steps, from planning to documenting results. The steps below follow that order.

By Coplain Team

Last updated

Step by step

  1. Plan and prepare — define the scope (which part, line and process steps), the team, the timing and the tools. A PFMEA needs people who run the process: an operator, a setup technician, manufacturing engineering, quality and maintenance. Gather inputs: the process flow diagram, drawings, past NCRs and complaints, and any DFMEA.
  2. Build the structure — list the process items: the process, each process step from the flow diagram (with its number), and the work elements in each step, often grouped as machine, person, material, method and environment.
  3. Describe the functions and requirements — for each step, write what it must do and the product and process characteristics it must meet. “Drill hole Ø6.0 +0.1/0 mm at position ±0.1” is a function with requirements; “drill” is not.
  4. Analyse failures: mode, effect, cause — for each function, list how it could fail (the failure mode), what that does to the next operation, the customer and the end user (the effect), and why it could happen (the cause, usually in a work element). Link them as a chain: cause → mode → effect.
  5. Rate the risk — record the current prevention controls (which stop the cause) and detection controls (which find the failure). Rate severity of the effect, occurrence of the cause given the prevention controls, and detection given the detection controls, each on a 1–10 scale from your customer’s or the handbook’s criteria. Then determine Action Priority. RPN vs Action Priority explains why AP replaced S × O × D in the 2019 handbook.
  6. Optimise with actions — for high-priority rows, assign actions with an owner and a date. Prefer prevention (error-proofing, fixture design, parameter limits) that lowers occurrence; then detection improvements. Severity usually changes only with a design change. Re-rate after actions are implemented and verified.
  7. Document and connect — record the results and carry each control into the control plan with the same step number. Update the PFMEA whenever the process changes or a new failure appears in production, and review it with customer complaints.

What a PFMEA is for

A process FMEA finds the ways a manufacturing or assembly process could produce a bad part, before it does. It is one of the automotive core tools, and it connects the process flow diagram to the control plan. The quality core tools guide, the pillar for this cluster, shows how they fit, and PFMEA vs DFMEA covers the design-side version.

The ratings scales and the Action Priority table belong to the AIAG & VDA FMEA Handbook and to customer manuals. Use the edition your customer requires and do not invent your own scales without agreement.

Prevention controls vs detection controls

The most common confusion is between the two control columns. A prevention control acts on the cause before a part is made: a poka-yoke that stops a part loading the wrong way, a validated program, a tool-life counter. A detection control finds the failure mode or cause after it happens: a gauge, a vision check, an inspection. Ratings follow: prevention lowers occurrence, detection lowers the detection rating.

Detection ratings depend on whether the measurement can be trusted. A gauge with poor repeatability does not earn a strong detection rating, so check it with the gauge R&R calculator. Occurrence ratings are easier to defend with data: process capability from the process capability calculator or scrap history.

Running the sessions

Keep sessions short and focused on a few process steps at a time, and have the facilitator fill in the worksheet live on a shared screen so everyone sees the wording. Agree on the rating scales at the start and keep them visible; most arguments in a PFMEA are about ratings, and pointing back to the agreed criteria settles them faster. Record assumptions, such as which controls are already in place, so later reviewers understand why a rating was given.

Use real data wherever it exists. Scrap and rework history, customer complaints, warranty returns and capability studies are better evidence for occurrence than opinion. When there is no data for a new process, rate conservatively and plan to revisit the rating after the first production runs. End each session by reading back the actions, owners and dates, and record them in the PFMEA worksheet before anyone leaves.

Worked examples

Example: One PFMEA row for a fictional drilling step, rated before and after action

  1. Step 30 Drill: function “drill Ø6.0 +0.1/0 mm hole at true position ±0.1”.
  2. Failure mode: hole mislocated. Effect: bolt cannot be assembled at the customer; line stoppage. Cause: part loaded rotated 180° in the fixture.
  3. Current controls: prevention none; detection visual check by operator. Example ratings from the team: S = 7, O = 6, D = 7.
  4. For a customer that still asks for RPN: 7 × 6 × 7 = 294.
  5. Action: add a locating pin so the part only loads one way (error-proofing). After implementation, the team re-rates occurrence to 2; detection stays 7.
  6. New RPN: 7 × 2 × 7 = 98, a drop of (294 − 98) ÷ 294 = 67%.

Result: Example result: the locating pin lowers occurrence from 6 to 2 and the RPN from 294 to 98, while severity stays 7 because the effect has not changed. Look up the Action Priority before and after in the handbook table your customer uses. All ratings are example values set by the fictional team.

Common mistakes

Frequently asked questions

How long does a PFMEA take?

It depends on the number of steps and the team’s preparation. Plan several short sessions rather than one long one, and come with the flow diagram and failure history ready.

What is the difference between PFMEA and DFMEA?

A DFMEA looks at how the design could fail to meet its function. A PFMEA looks at how the process could fail to make the design. [PFMEA vs DFMEA](/blog/pfmea-vs-dfmea) compares them.

Is RPN still used?

Some customers still ask for it. The 2019 AIAG & VDA handbook replaced it with Action Priority, which considers severity first. Follow your customer’s requirement.

What are the seven steps of a PFMEA?

In the AIAG & VDA handbook: planning and preparation, structure analysis, function analysis, failure analysis, risk analysis, optimisation, and results documentation.

Who owns the PFMEA?

Usually manufacturing or process engineering, with quality as a reviewer. It should be under document control and kept in step with the control plan.

Sources

  1. AIAG & VDA FMEA Handbook (2019), AIAG and VDA
  2. Potential Failure Mode and Effects Analysis (FMEA) reference manual, 4th edition, AIAG
  3. IEC 60812:2018 Failure modes and effects analysis (FMEA and FMECA), IEC

See also

COPLAIN AI PLATFORM

Generate yours automatically from your existing docs

Coplain turns PFMEA prevention controls into clear operator steps, so the controls you rated are the controls people actually follow.

Generate yours automatically with Coplain →

Related Tools & Templates