# PFMEA: Template, Worked Example and the Control Plan Link

> A process FMEA (PFMEA) template with a worked example, how severity, occurrence and detection are scored, and how the PFMEA feeds the control plan.

Canonical: https://origindatapartners.com/guides/pfmea-template
By: Origin Data Partners
Status: Published
Published: 2026-11-15
Updated: 2026-11-15
Sources checked: 2026-11-15

## Quick answer

A PFMEA is a process failure mode and effects analysis: a table that lists, for each step of a manufacturing process, how the step could fail, what the failure would do, what causes it and how it is prevented or caught. Each line is rated for severity, occurrence and detection, the worst risks get actions, and the controls flow into the control plan.

## Key points

- One row per failure mode per process step, using the same step numbers as the process flow diagram.
- Severity rates the effect, occurrence rates the cause, detection rates the control.
- The older method multiplies the three into an RPN; the AIAG & VDA handbook uses Action Priority instead.
- Every control in the PFMEA should appear in the control plan with a reaction plan.

## What is a PFMEA, and when does a plant need one?

PFMEA stands for process failure mode and effects analysis. One supplier handbook says it "is used to show evidence that potential failure modes and risks have been assessed at the manufacturing process level" ([Prestolite](https://prestolite.com/wp-content/uploads/2020/12/Prestolite-Supplier-PPAP-Handbook-Rev-D.pdf)). A cross-functional team walks the process step by step and asks three things at each step: what could go wrong here, what would that do to the part or the customer, and what in our process stops it or catches it.

Automotive suppliers need one for every part they submit for approval, because the process FMEA is one of the 18 elements of a [PPAP package](https://origindatapartners.com/guides/ppap-in-manufacturing). The reference is the AIAG & VDA FMEA Handbook, which AIAG calls "the new automotive industry reference manual for Failure Mode and Effects Analysis" ([AIAG](https://www.aiag.org/training-and-resources/manuals/details/FMEAAV-1)). One Tier 1 guide tells its suppliers the PFMEA "must be done according to AIAG & VDA FMEA Handbook per Customer Specific Requirements" ([Tenneco](https://www.tenneco.com/content/dam/tenneco/doc/pdf/supplier-documents/Supplier%20Tenneco_PPAP_Guidelines%2011-05-2024.pdf.coredownload.pdf)). Aerospace, medical device and general industrial plants use the same method, often because a customer or a quality standard asks for documented process risk analysis.

A PFMEA is written before production starts and then kept alive. It should be revisited when the process changes, when a new failure shows up in a non-conformance or a customer complaint, and when a corrective action adds a control.


## PFMEA template: what columns does it need?

The columns below are a workable template in our own words. They follow the logic every FMEA form shares: step, failure, effect, cause, controls, ratings, action. The AIAG & VDA handbook has its own form sheets, and your customer may require those or its own format.

| Column | What to enter |
| --- | --- |
| Process step number and name | The same number and name as the process flow diagram and the control plan |
| Function or requirement | What the step must achieve, with the specification where there is one |
| Potential failure mode | How the step could fail to meet the requirement, stated as a defect you could find on the part |
| Potential effect | What the failure does at the next operation, at the customer's plant and for the end user |
| Severity (S) | A rating of the worst effect |
| Special characteristic | The customer's or your own symbol, if the characteristic is flagged |
| Potential cause | Why the failure would happen: one cause per row, stated as something you can control |
| Prevention control | What stops the cause from happening |
| Occurrence (O) | A rating of how often the cause is expected, given the prevention control |
| Detection control | What catches the cause or the failure before the part leaves |
| Detection (D) | A rating of how well the detection control works |
| Risk result | The RPN or the Action Priority, depending on the method your customer requires |
| Recommended action, owner and date | What will reduce the risk, who owns it and by when |
| Action taken and new ratings | What was done, with evidence, and the ratings after the action |


## PFMEA example: a torque operation, three rows

A fictional example shows how the rows read. A plant assembles a pump housing. At operation 40 an operator drives four M8 bolts to 25 Nm with a DC electric tool. The ratings are illustrative, on scales of 1 to 10 where 10 is worst.

| Failure mode | Effect | S | Cause | Prevention control | O | Detection control | D | RPN |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Bolt under torque | Joint loosens in service; leak at the customer | 8 | Tool programme set for the wrong part number | Barcode scan selects the programme | 3 | Tool monitors torque and angle on every bolt and stops the line on a fault | 2 | 48 |
| Bolt missing | Leak found at the customer's end-of-line test | 7 | Operator skips a position | Tool counts four good rundowns before it releases the fixture | 2 | Vision check at operation 50 | 3 | 42 |
| Thread stripped | Housing scrapped in plant | 5 | Cross-threading from a misaligned start | Bolts started by hand in a locating fixture | 4 | Angle window on the tool flags an early torque rise | 4 | 80 |

Fictional data. Read row one: severity is high, so the team looks at it first even though its RPN is not the largest. The action it took was to lock programme selection to the scan and remove the manual override.

Row three has the highest RPN but the lowest severity. That difference is the reason the newer method does not rank by the product of the three numbers.


## How are severity, occurrence and detection scored?

Each rating answers a different question. Severity is about the effect and does not change unless the design or the effect changes. Occurrence is about the cause and falls when prevention improves. Detection is about the control and falls when the check gets better or moves closer to the cause. The rating tables come from the handbook or from your customer, and the plant should apply one set consistently.

The older method multiplies the three. One supplier handbook gives the formula as "RPN = Severity (S) x Occurrence (0) x Detection (D)" and describes an RPN threshold as "a specific number chosen as the point when action on a failure mode is required" ([Prestolite](https://prestolite.com/wp-content/uploads/2020/12/Prestolite-Supplier-PPAP-Handbook-Rev-D.pdf)). The weakness is visible in the example above: a severe failure with good controls can score lower than a minor one.

The AIAG & VDA handbook changed this. AIAG lists among its main changes "totally revised Severity, Occurrence and Detection Tables" and "the Action Priority (AP) methodology and Tables to replace RPN", along with a seven-step approach to building the analysis ([AIAG](https://blog.aiag.org/new-aiag-vda-fmea-handbook-and-trainings-available)). Action Priority is read from a table using the three ratings, with severity weighted first, and it tells the team how urgently a line needs action. Customers add their own rules. One guide tells suppliers that a step with severity 9 or 10 "must be highlighted in the pFMEA for team focus" whatever the other ratings are ([Tenneco](https://www.tenneco.com/content/dam/tenneco/doc/pdf/supplier-documents/Supplier%20Tenneco_PPAP_Guidelines%2011-05-2024.pdf.coredownload.pdf)).


## How does the PFMEA link to the control plan?

The PFMEA decides what must be controlled and the control plan says how it is controlled on the floor. Reviewers check the link before anything else. One customer guide requires that "the link between PFMEA, Process Flow and Control Plan (same step numbers, names and processes) is confirmed" ([Tenneco](https://www.tenneco.com/content/dam/tenneco/doc/pdf/supplier-documents/Supplier%20Tenneco_PPAP_Guidelines%2011-05-2024.pdf.coredownload.pdf)), and another states that "the primary process steps must match both the Control plan and the Process FMEA" ([Prestolite](https://prestolite.com/wp-content/uploads/2020/12/Prestolite-Supplier-PPAP-Handbook-Rev-D.pdf)).

In practice each prevention and detection control in the PFMEA becomes a line in the control plan with a specification, a measurement method, a sample size and frequency, and a reaction. The same handbook wants every step to have "a defined 'Control Method' and 'Reaction Plan' outlined on the control plan" and says the control plan "should be a living and active part of your overall quality system" ([Prestolite](https://prestolite.com/wp-content/uploads/2020/12/Prestolite-Supplier-PPAP-Handbook-Rev-D.pdf)). AIAG now publishes the control plan as its own manual, with "detailed guidance on how to develop control plans" ([AIAG](https://www.aiag.org/training-and-resources/manuals/details/CP-1)).

| PFMEA row (operation 40) | Control plan line |
| --- | --- |
| Prevention: barcode scan selects the tool programme | Characteristic: programme number. Method: scan interlock. Frequency: every part. Reaction: line stops; supervisor resets. |
| Detection: torque and angle monitored on every bolt | Characteristic: final torque 25 Nm, tolerance per drawing. Method: tool transducer, verified against a calibrated tester each shift. Reaction: quarantine parts since the last good check. |
| Detection: vision check for four bolts at operation 50 | Characteristic: bolt presence. Method: camera. Frequency: every part. Reaction: reject to the rework lane and log the non-conformance. |

The reaction plan is where the PFMEA meets the rest of the quality record: a failed check opens a [non-conformance report](https://origindatapartners.com/guides/non-conformance-report-template), and a repeat or a customer complaint opens an [8D](https://origindatapartners.com/guides/8d-report-example).


## PFMEA vs DFMEA: which one covers what?

A design FMEA asks how the product design could fail. A process FMEA asks how the manufacturing process could fail to make the design. The supplier that designs the part owns the DFMEA; the plant that makes it owns the PFMEA. The two are connected: one handbook notes that the results of the DFMEA "should be used in the creation of the Process FMEA" ([Prestolite](https://prestolite.com/wp-content/uploads/2020/12/Prestolite-Supplier-PPAP-Handbook-Rev-D.pdf)), because the severity of an effect and the special characteristics are set by the design. Our [PPAP guide](https://origindatapartners.com/guides/ppap-in-manufacturing) has a side-by-side table.


## Where do PFMEAs live, and who owns them?

Most plants keep PFMEAs in one of three places: spreadsheets on a shared drive, a module of the quality management system, or dedicated FMEA software that links the process flow, the FMEA and the control plan. Whatever the tool, keep the revision history. A PFMEA with its dated revisions, the reason for each change and the non-conformance or complaint that triggered it is far more useful than the latest version alone.

The PFMEA is the supplier's own analysis of its own process. Customers review it but do not always receive a copy. One customer guide allows for that directly: if the supplier does not want to upload the PFMEA "due to confidentiality", a cover page is submitted instead and the document is reviewed at the supplier's site ([Tenneco](https://www.tenneco.com/content/dam/tenneco/doc/pdf/supplier-documents/Supplier%20Tenneco_PPAP_Guidelines%2011-05-2024.pdf.coredownload.pdf)). The drawing, the special characteristics and any design FMEA from the customer are a different matter: those belong to the customer and stay under the supply agreement's confidentiality terms.


## Common mistakes in a PFMEA

Auditors and customer quality engineers see the same faults again and again.

- Step numbers that differ between the process flow, the PFMEA and the control plan.
- Writing the cause as "operator error" instead of the condition that lets the error happen.
- Mixing up failure mode, effect and cause in the same cell.
- Lowering severity after adding a control. Controls change occurrence and detection, not the effect.
- Listing a detection control that does not exist on the control plan, or has no gauge study behind it.
- Copying a PFMEA from a similar part and never revisiting the ratings.
- Closing actions with no evidence and no new ratings.
- Leaving out rework, material handling, labelling and packing steps.


## Your PFMEA history is also a data asset

A PFMEA revision history joined to the defects that followed is rare. It records what experienced engineers expected to go wrong, what did go wrong, and what they changed. Almost none of that is public. According to one buyer's public listings, read 15 November 2026, the request to manufacturers is for production or maintenance records the company owns, with at least one of CAM programs with setup sheets, work orders with inspection reports, or machine alarm logs and process data, over several years. Quality and SPC data, and checklists and correction letters, add to it. The same listings put the published range for a manufacturing company at $100,000 to $1.5 million. Read that as a ceiling that depends on record types and history, not a typical outcome. Origin Data Partners is an independent data partner that helps a plant find out whether its records fit a request like this.

Customer contracts decide much of the answer. The listings name "data restricted by customer contracts" as not a fit. Your own process analysis, control plans and inspection results are usually yours, but customer drawings, specifications and part numbers are not, and supply agreements often cover anything made for the programme. Export-controlled technical data has to come out before anything leaves the company; the [ITAR and EAR checklist](https://origindatapartners.com/guides/itar-ear-checklist-cad-data-ai) walks through that review. Names and signatures on the forms are personal data. This page is general information, not legal advice.

Related guides: [licensing manufacturing quality records](https://origindatapartners.com/guides/license-manufacturing-quality-records-ai), [PPAP in manufacturing](https://origindatapartners.com/guides/ppap-in-manufacturing), the [first article inspection report](https://origindatapartners.com/guides/first-article-inspection-report) and [engineered product manufacturer data](https://origindatapartners.com/guides/engineered-product-manufacturer-data).

Does your company hold records like these? [See what your data is worth](https://origindatapartners.com/check-fit).


## Questions and answers

### What does PFMEA stand for?

Process failure mode and effects analysis. It is a structured table of how each step of a manufacturing process could fail, what the failure would cause, and how the process prevents or detects it.

### What is the difference between a PFMEA and a control plan?

The PFMEA is the risk analysis: it decides which failures matter and which controls are needed. The control plan is the shop-floor instruction: for each control it gives the specification, the measurement method, the frequency and what to do when a check fails.

### How is the risk priority number worked out in a PFMEA?

Multiply the severity, occurrence and detection ratings. With 1 to 10 scales the result runs from 1 to 1,000. The AIAG & VDA handbook replaces this with Action Priority, which is read from a table and gives severity the most weight.

### Who owns the PFMEA, the supplier or the customer?

The supplier that runs the process owns its PFMEA, and some customers accept an on-site review instead of a copy. Customer drawings, specifications and any design FMEA the customer supplied remain the customer's, under the supply agreement.

### How often should a PFMEA be updated?

Whenever the process, the tooling, the material or the design changes, when a new failure appears in a non-conformance or complaint, and when a corrective action adds or changes a control. Many plants also review it on a fixed cycle.

### Do quality records such as PFMEAs and control plans have value to AI companies?

They can, mainly when they are joined to work orders, inspection results and corrective actions over several years, and when the company owns them. Records restricted by customer contracts are generally excluded.

## Sources

- [AIAG: AIAG & VDA FMEA Handbook, publication page](https://www.aiag.org/training-and-resources/manuals/details/FMEAAV-1)
- [AIAG: announcement of the AIAG & VDA FMEA Handbook and its main changes](https://blog.aiag.org/new-aiag-vda-fmea-handbook-and-trainings-available)
- [AIAG: Control Plan manual, 1st edition, publication page](https://www.aiag.org/training-and-resources/manuals/details/CP-1)
- [Tenneco: PPAP guidelines for suppliers (PDF, November 2024)](https://www.tenneco.com/content/dam/tenneco/doc/pdf/supplier-documents/Supplier%20Tenneco_PPAP_Guidelines%2011-05-2024.pdf.coredownload.pdf)
- [Prestolite Electric: Supplier PPAP Handbook, North America (PDF)](https://prestolite.com/wp-content/uploads/2020/12/Prestolite-Supplier-PPAP-Handbook-Rev-D.pdf)

## Related reading

- [License Manufacturing Quality Records to AI Companies](https://origindatapartners.com/guides/license-manufacturing-quality-records-ai)
- [PPAP in Manufacturing: 18 Elements, Levels and the PSW](https://origindatapartners.com/guides/ppap-in-manufacturing)
- [Non-Conformance Report (NCR): Template and Examples](https://origindatapartners.com/guides/non-conformance-report-template)
- [8D Report: Example, Template and 8D Problem Solving](https://origindatapartners.com/guides/8d-report-example)
- [CAD Data and Quality Records for AI: Manufacturer Guide](https://origindatapartners.com/guides/engineered-product-manufacturer-data)
- [First Article Inspection Report: AS9102 Forms and Example](https://origindatapartners.com/guides/first-article-inspection-report)
