DFMEA vs PFMEA
6 min read · Updated 2026-08-17
Both are Failure Mode and Effects Analysis. The difference is what they hold responsible: the design, or the way it is made.
The short version
| DFMEA | PFMEA | |
|---|---|---|
| Analyses | The product design | The manufacturing process |
| Structured around | Functions of the part | Operations in the sequence |
| A failure mode is | The part failing to perform a function | An operation producing a nonconformance |
| Controls are | Design decisions, analysis, testing | Process controls, checks, error proofing |
| Usually owned by | Design engineering | Manufacturing and quality engineering |
| Timing | During design | During process design, before launch |
| Feeds | Drawing, specifications, special characteristics | Control plan |
Where the distinction actually bites
In the controls column, and this is where most badly-written FMEAs go wrong.
Consider a bore that must be 24.00 mm with a tolerance of +0.02 / −0.00.
In the DFMEA, the failure mode is functional: the bore does not retain the bearing. The cause might be that the specified tolerance is too loose for the interference fit required. The prevention control is a design decision — a tolerance stack analysis, a materials choice, a design standard. "Operator checks the bore every hour" is not a DFMEA control. It does not make the design better; it catches a manufacturing deviation.
In the PFMEA, the failure mode is a manufacturing outcome: bore diameter oversize at operation 20. The cause is a process cause — tool wear not compensated. The prevention control is something that stops it occurring, like a tool-life change interval. The detection control is something that catches it if prevention fails, like an air gauge check every twenty-five pieces. Both belong here, and they are different things.
The mistake to avoid: writing manufacturing checks into the DFMEA. It inflates the design analysis with process content, and it hides the fact that nobody actually improved the design.
Prevention and detection are not interchangeable
Worth stating separately because it is the second most common error. A prevention control reduces the chance of the cause occurring. A detection control finds the problem after it has occurred. Prevention is always better — a part that was never made wrong costs nothing to scrap. An FMEA whose controls are all detection is describing an inspection department, not a capable process.
How the two connect
Through special characteristics. The DFMEA decides which features of the part matter most — which are critical, which are significant. That classification then constrains the process side: a critical characteristic has to be controlled more tightly in the PFMEA and the control plan than an ordinary dimension.
This is the hand-off that most often breaks in practice, because the two analyses are usually maintained in separate files by separate functions. When the classification is carried on the characteristic itself rather than re-typed into each document, the constraint travels with it.
Do you need both?
If you are design-responsible for the part, yes. If the customer owns the design and you make to their drawing, you will typically be asked for a PFMEA and may not owe a DFMEA — though the customer’s design decisions still constrain your process, and their special characteristics still apply.
On AIAG-VDA
The current harmonised AIAG-VDA method applies the same seven-step structure to both, and replaces the older single risk number with Action Priority as its evaluation output. The structural distinction between design and process analysis is unchanged. The manuals are licensed material and their rating tables are not reproducible here.