Automotive Compliance

Ford’s FMEA Requirements for PPAP in 2025: What Suppliers Need to Know

Tacit AI · 7 min read

Your PPAP was rejected. Your quality team is pulling weekend shifts trying to figure out what Ford wants. The STA is asking for a revised FMEA with traceability you never built in. This is happening to Tier 1 and Tier 2 suppliers across North America, and the reason is consistent: Ford’s updated Customer-Specific Requirements (CSRs) and the industry-wide move to the AIAG-VDA FMEA method raised the bar on FMEA content, and many supplier teams didn’t adjust until a submission came back red.

What Ford Actually Changed

Across its 2024–2025 Customer-Specific Requirements (CSR) releases, Ford tightened how FMEAs are expected to be built, formatted, and maintained. The requirements apply to new program awards and to carry-over parts with design or process changes.

The key changes:

AIAG-VDA FMEA format is accepted — and expected. Ford’s CSR (September 2024 release) confirms it will accept the AIAG & VDA FMEA Handbook format. In practice that means Action Priority (AP) methodology and the structured seven-step approach, not legacy RPN-only worksheets.
Current APQP and Control Plan editions are required. Ford’s CSR requires the AIAG APQP 4th Edition and Control Plan 1st Edition, effective December 31, 2024. Your FMEA has to line up with a control plan built to the current manual.
FMEAs must live in FMEA software, aligned. Ford requires Foundation and part-specific FMEAs to be maintained in FMEA software that keeps FMEAs, control plans, and work instructions aligned. Disconnected spreadsheets don’t meet the requirement.
Control plan expectations tightened for sub-tier characteristics. Ford’s February 2025 CSR update (effective 6 February 2025) clarified control plan expectations for sub-tier critical characteristics and updated Level 3 and 5 PPAP approval requirements.
Special and critical characteristics must be traceable. They have to be documented and communicated (for example, via the SCCAF form), with failure modes tracing back to specs, drawings, and test evidence.

This is not a suggestion or a best-practice recommendation. It is a gate. Suppliers who do not meet these requirements do not get program awards.

What Gets Rejected

Ford’s supplier quality reviewers consistently reject FMEAs that show any of these patterns:

Generic failure modes. Entries like “wear and tear,” “operator error,” or “material defect” without specificity to the actual part or process. These tell the reviewer you didn’t analyze anything. You filled in cells.
Severity ratings without justification. A severity of 8 means nothing if there’s no evidence linking it to a specific failure effect. Ford wants to see the logic, not just the number.
Missing source traceability. If a failure mode doesn’t reference the spec, drawing, or test data it came from, it gets rejected. “Engineering judgment” alone is no longer sufficient documentation.
Copy-pasted FMEAs from previous programs. Reusing a prior program’s FMEA without updating it for the current design, tooling, and process parameters is the fastest path to rejection. Reviewers check for this.
No DFMEA-to-PFMEA linkage. If your DFMEA identifies a high-severity failure mode but your PFMEA doesn’t show corresponding process controls, the entire submission is questioned.

These are not edge cases. They are among the most common FMEA-related rejection reasons suppliers run into.

What Passes the Quality Gate

Submissions that clear Ford’s updated gate share a consistent set of characteristics:

Failure modes specific to your design and process. Not generic industry lists. Modes that reflect the actual geometry, material, tolerances, and manufacturing steps of the part being submitted.
Severity ratings justified by evidence. Each severity score ties to a documented failure effect, backed by test data, field returns, or simulation results.
Source traceability on every row. Each failure mode references the specification, drawing revision, or test report it derives from. Reviewers can trace any row back to its origin in under a minute.
DFMEA → PFMEA → control plan chain intact. Design-level severity carries through to process-level controls. Detection methods in the control plan map directly to the PFMEA. No gaps, no orphans.
Action Priority (AP) or RPN with consistent logic. Whether you use AIAG-VDA Action Priority or traditional RPN, the methodology is applied uniformly. Mixed approaches within the same document are flagged.

The bar is not impossible. It requires FMEAs that are actually built from the current program’s data instead of recycled from the last one.

Beyond Ford: BMW, VW, Toyota, Stellantis

Ford is not alone in raising the standard. Every major OEM is tightening supplier quality requirements, and FMEA is at the center of it.

BMW maintains its own supplier quality manual with specific FMEA expectations that go beyond AIAG-VDA baseline. Suppliers targeting BMW programs need to meet both the standard and BMW’s additional requirements.
VW Group mandates VDA Volume 4 compliance for all FMEA submissions. The VDA approach to failure mode analysis has its own structure and terminology that differs from AIAG in key areas.
Toyota expects FMEAs linked to reliability targets and field performance data. Toyota’s quality culture puts heavy weight on prevention over detection, and their FMEA reviews reflect that philosophy.
Stellantis is under J.D. Power pressure to improve initial quality scores. That pressure flows directly to suppliers through stricter PPAP reviews and more rigorous FMEA scrutiny.

If you supply to more than one OEM, you are already managing multiple FMEA standards. The bar is rising across all of them, and it will not come back down.

The Real Cost of a Rejected PPAP

A rejected PPAP is not just a rework item. It has compounding effects that hit the business hard:

Program delays. A rejected FMEA means resubmission, re-review, and potentially re-validation. Timelines slip by weeks to months depending on the severity of the gaps.
Lost contract potential. OEMs track supplier quality performance. Repeated rejections put you on watch lists and cost you future program bids.
Reputation damage with OEM quality teams. STA engineers talk to each other. A supplier known for weak FMEAs gets harder scrutiny on every subsequent submission.

At Tier 1 margins of 3–7%, a single quarter delay on a program launch can cost millions in deferred revenue, expediting charges, and engineering overtime. For Tier 2 suppliers, the margins are even thinner and the impact is proportionally worse.

The math is straightforward: investing in FMEA quality up front costs a fraction of what a rejected PPAP costs downstream.

How to Fix Your FMEA Process

If your current process produces FMEAs that would fail Ford’s updated gate, here is what needs to change:

Stop copy-pasting from the last program. Every new program needs FMEAs generated from the current design, current tooling, and current process parameters. Carry-over analysis is a starting point, not a finished product.
Generate failure modes from current specs. Read the actual drawings, material specs, and process flow diagrams for this program. Extract failure modes that are specific to what you are building now.
Trace every row to its source. Every failure mode, every severity rating, every occurrence estimate should reference a document. If you cannot point to the source, the row is not defensible.
Link DFMEA severity through PFMEA to control plan. Build the chain explicitly. A high-severity design failure mode must produce a corresponding process control, and that control must appear in the control plan with a defined detection method.
Use AIAG-VDA Action Priority, not just RPN. The industry is moving away from simple RPN multiplication toward structured Action Priority assessment. Ford’s updated requirements align with this direction. If you are still using raw RPN without the AP framework, update your methodology.

None of this is new engineering. It is discipline. The teams that do it well build it into their process rather than treating FMEA as a document to fill out before submission.

How Tacit AI Approaches This

Tacit AI is built for the problem Ford’s update exposed: FMEA quality at supplier speed. But generation is only the on-ramp. The real value is that the FMEA stays alive.

AIAG-VDA native, 80% draft-ready in hours. Upload specs and process data. Get a structured FMEA draft with Action Priority scoring, correct column structure, and source traceability from the first row. Engineers review and refine, not rebuild from blank worksheets.
DFMEA → PFMEA → control plan chain. Design severity flows through to process controls. Gaps are flagged before submission, not after rejection. The linkage Ford demands is maintained structurally, not manually.
Field data closes the loop. Warranty claims and quality alerts are matched to FMEA rows. When a failure contradicts the risk assessment, the system flags it. When a control is verified but the failure recurs, it’s marked as a regression. Your FMEA knows before your next PPAP submission that the risk assessment needs updating.
The FMEA stays current. Every other FMEA tool creates a document that decays from the moment it’s approved. Tacit AI creates a living system that tells your engineers when reality disagrees with the analysis. That’s what separates a PPAP that passes from one that gets rejected on the next audit cycle.

If you are an automotive supplier facing tighter FMEA scrutiny from Ford or any other OEM, see how Tacit AI supports automotive FMEA workflows or request a working session with our team.