FMEA guide

How to Write a PFMEA (Process FMEA)

A clear, step-by-step method for building a Process FMEA that actually helps you prioritize risk — not just pass an audit.

A PFMEA (Process Failure Mode and Effects Analysis) is a structured way to find how a manufacturing process could fail, how serious each failure would be, how often it might happen, and how likely you are to catch it before it reaches the customer — then rank those risks so you fix the worst ones first. It's a core requirement of IATF 16949 and PPAP, and it's used across aerospace, medical, and general manufacturing.

What goes in a PFMEA

A Process FMEA is built row by row. The standard columns are:

• Process step and its requirement (a product characteristic or a process requirement).
• Potential failure mode — a specific way the requirement is not met (there are usually several per step).
• Potential effect(s) and a Severity (S) rating, 1–10.
• Potential cause(s) and an Occurrence (O) rating, 1–10.
• Current controls (prevention and detection) and a Detection (D) rating, 1–10.
• RPN (S × O × D) and/or an Action Priority (High / Medium / Low).
• Recommended actions, owners, and target dates.

How to write a PFMEA, step by step

1. Break the process into steps. List every operation in sequence — receiving, machining, drilling, deburring, inspection, packing, and so on.
2. Define each step's requirement. What must the part or the process achieve at this step? Keep it specific but don't guess exact tolerances you don't have.
3. List the potential failure modes. For each requirement, brainstorm the genuinely different ways it can fail (e.g. "diameter too big" and "diameter too small"), not one vague "non-conformance".
4. Describe the effects and rate Severity. What happens downstream or to the customer if this failure escapes? Rate S from 1 (no effect) to 9–10 (safety or regulatory).
5. List the causes and rate Occurrence. Why would the failure happen? Rate O from 1 (very unlikely) to 10 (very frequent).
6. Document current controls and rate Detection. What prevents the cause, and what would catch the failure? Rate D from 1 (almost certain to detect) to 10 (cannot detect).
7. Calculate the risk. RPN = S × O × D. Many teams now use the AIAG-VDA Action Priority (High / Medium / Low) instead of, or alongside, RPN.
8. Act on the high risks. Add recommended actions for the top items, assign owners and dates, implement them, and re-rate.

Tips that separate a good PFMEA from a checkbox one

• Use the real knowledge of the people who run the process — S/O/D should reflect your data, not a guess.
• Not everything is a 10. Honest ratings make the priorities meaningful.
• Keep it a living document — revisit it when the process, tooling, or a problem changes.

← Back to Dropfeed