FMEA · editor
Step 1 of 3
Design & Setup
Frame the document before you fill it in: the brand it carries and the page it prints on. Everything updates the preview instantly.
This document uses your workspace brand kit for its logo, colors, and fonts. Add more brand kits to switch between them here.
| FMEA type | Process FMEA (PFMEA) |
| Company / plant | |
| Program / model year | |
| Subject / part name | |
| FMEA ID number | |
| Cross-functional team | |
| Start date / revision date | |
| Confidentiality level |
Define the process, its steps and functions, and the analysis boundary (structure & function analysis).
| Risk analysis | Optimization | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Process step / Function | Failure mode | Effect(s) | S | Cause / mechanism | Prevention control | O | Detection control | D | AP | Recommended action | Responsibility | Target date | Status | Action taken & evidence | S′ | O′ | D′ | AP′ |
| [Process step / function] | [Potential failure mode] | [Effect on customer / next operation] | 8 | [Potential cause / mechanism] | [Current prevention control] | 4 | [Current detection control] | 6 | H | [Recommended action] | [Owner] | [Target date] | Open | [Action taken + evidence + completion date] | 8 | 2 | 4 | L |
| […] | […] | […] | 9 | […] | […] | 3 | […] | 4 | H | […] | ||||||||
| Rating | Severity (S) | Occurrence (O) | Detection (D) |
|---|---|---|---|
| 9–10 | Safety / regulatory | Very high: failure inevitable | Very low: control unlikely to detect |
| 7–8 | Loss of primary function | High | Low |
| 4–6 | Loss of secondary function | Moderate | Moderate |
| 2–3 | Minor / annoyance | Low | High |
| 1 | No discernible effect | Failure eliminated by control | Certain: control will detect |
Action Priority (High / Medium / Low) is derived from Severity, Occurrence and Detection per the AIAG-VDA AP table. High priority requires action, Medium should be actioned, Low is at the team's discretion.
Requirements and official formats can change. Before you release this document, you are responsible for verifying its final structure, required sections and fields, content accuracy, applicability, approvals, and that the regulation, standard, customer requirement, or official template you are following is the current version. DataSheets Pro gives you a structured starting point; it does not certify compliance or guarantee that a template is complete, legally sufficient, or current.