FMEA Example (Process FMEA — Practical Guide)

This is a real Process FMEA (PFMEA) example based on CNC machining. This PFMEA example reflects a typical manufacturing risk analysis used in automotive and industrial production. You'll see how failure modes are identified, scored, and prioritized using the AIAG-VDA Action Priority method.

If you are looking for a real FMEA example or PFMEA example, this page shows how it is applied step by step. This example follows the standard FMEA steps used in AIAG-VDA methodology.

If you are starting from scratch, read the complete FMEA methodology guide first.

What a Good FMEA Looks Like

A well-structured FMEA is not just a spreadsheet — it's a disciplined risk analysis. Key characteristics:

• Clearly defined failure modes tied to specific process steps
• Traceable cause-effect logic (each failure → effect → root cause)
• Actions prioritized by risk, not by arbitrary scoring

Process FMEA Example: CNC Machining of Aluminum Housing

Below is a realistic Process FMEA for a CNC-machined aluminum housing used in an automotive powertrain assembly. Each row represents a potential failure mode evaluated against Severity, Occurrence, and Detection.

Why These Ratings?

• High Severity values (8–9) indicate failures that impact function, safety, or customer requirements
• Medium Occurrence reflects controlled but not fully eliminated process variability
• Detection scores highlight limitations in current inspection or control methods
• These combinations lead to High Action Priority, requiring immediate action
• In real projects, these ratings are typically defined during cross-functional reviews involving quality, production, and engineering teams

Flexible Output — Work the Way You Want

While this example shows a structured FMEA, you are not locked into a single format. You can export your FMEA as:

• CSV (raw data for analysis)
• Excel (.xlsx unformatted) for quick edits
• Excel (.xlsx formatted) aligned with AIAG-VDA structure

This allows you to combine structured generation with familiar Excel workflows — without starting from scratch.

How to Read This FMEA

• Severity (S) — rates the impact of the failure effect on the end customer or system. A score of 9 (e.g., sealing failure) indicates a potential safety or functional risk.
• Occurrence (O) — estimates how likely the root cause is to occur under current process conditions.
• Detection (D) — rates the ability of current controls to detect the failure before it reaches the customer. Higher values mean weaker detection.
• Action Priority (AP) — replaces the traditional RPN. Items marked High require immediate corrective action regardless of individual scores, because the AIAG-VDA method weighs Severity first.

Learn more about how Severity, Occurrence, and Detection scales work in our FMEA guide.

Common Mistakes in FMEA

• Treating FMEA as documentation instead of active risk management
• Inconsistent scoring across team members without calibrated scales
• Listing vague failure modes (e.g., "defect") instead of specific mechanisms
• Missing root causes — jumping from failure mode directly to action
• Using RPN thresholds instead of AIAG-VDA Action Priority logic

Frequently Asked Questions

Why FMEA Is Important in Manufacturing (Real Risks Without FMEA)

• Defects are detected only at final inspection instead of prevention
• Increased scrap, rework, and production downtime
• Customer complaints and warranty claims
• Audit findings due to missing or weak risk analysis
• Uncontrolled process variation leading to inconsistent quality

FMEA shifts risk detection upstream — before failures reach the customer.

Industry-Specific PFMEA Examples

The CNC walkthrough above covers the core methodology. For specific processes, use the worked row-by-row PFMEAs below — each has 10 realistic failure modes with calibrated S/O/D and Action Priority.

Browse all on the FMEA examples hub.

Process Context, Scope, and Assumptions

This PFMEA covers the machining cell that produces an aluminum housing for an automotive powertrain assembly. Defining the scope is the single most important step — most weak PFMEAs are weak because the scope was too broad.

• Part: Aluminum housing, 6061-T6, machined from forging.
• Customer: Tier 1 automotive, IATF 16949 + customer-specific requirements.
• Volume: 480,000 pcs / year, 3 shifts.
• Process scope: raw material clamping through anodizing (outsourced).
• Out of scope: incoming forging inspection (covered by supplier PFMEA), final assembly.
• Special characteristics: sealing surface Ra ≤ 1.6 µm, locating bore Ø8 H7, coating thickness 15–25 µm.

Rating Justification — Why These S, O, D Values?

A rating without recorded justification cannot survive an audit challenge. Below is the reasoning for the most critical rows. Use this as a template for your own PFMEA rationale column.

For the full rating logic see the Severity, Occurrence, and Detection rating guides, plus the Action Priority logic.

Prevention vs Detection Controls — Worked Example

The single most common audit finding on PFMEAs is mixing Prevention and Detection controls in the same cell. AIAG-VDA separates them because they influence risk differently.

See FMEA vs Control Plan for how these controls flow into the Control Plan.

Auditor Perspective — What They Will Challenge

Experienced IATF 16949 and customer SQA auditors typically focus on the same five areas in a CNC PFMEA. Prepare evidence for each before the opening meeting.

Run the full FMEA audit checklist 48 hours before any IATF or customer audit.

How Teams Score This Wrong

• D=2 on surface-finish sampling — sampling can never deserve D≤3; only 100% automated inspection with GR&R <10% does.
• O=2 with no Cpk evidence — Occurrence must be anchored to capability data, not optimism.
• S downgraded because "we'd catch it" — Severity is independent of controls; only the customer impact changes S.
• Prevention and Detection in one cell — must be separated per AIAG-VDA.
• No residual rating after action — every closed action requires a re-rated S/O/D and effectiveness evidence.

Full list in Common FMEA mistakes.

Implementation Notes — From Example to Production

1. Map your actual process flow first — every step must have at least one PFMEA row.
2. Reuse this table as a calibration anchor, not as content. Your S/O/D will differ based on your data.
3. Add a rating-rationale column next to each S, O, D — this single change removes most audit findings.
4. Sync step IDs and characteristic IDs across PFMEA, Process Flow Diagram, and Control Plan.
5. Define a written company rule capping Detection by control type (visual → D≥7, sampling → D≥6, 100% automated → D=2–3).
6. Re-rate after every closed action and store the effectiveness evidence (Cpk, ppm, audit).
7. Trigger a PFMEA review on every 8D, engineering change, supplier change, or tooling change.

See the FMEA best practices playbook for the full rollout sequence, or generate a structured PFMEA directly with the automated FMEA generator.