FMEA Reference Architecture: Aligning DFMEA/PFMEA Data with AIAG-VDA, SAE J1739 and IEC 60812 for Interoperable Exchange

An FMEA tool sits between requirements/design data and the Control Plan, so the key architecture decisions are which standard defines your data model and which file format carries it across system boundaries. FMEA Tool follows the 7-step structure and Action Priority (AP) logic of the AIAG & VDA FMEA Handbook (1st edition, 2019). SAE J1739:2021 uses the same approach for North American programs, and IEC 60812:2018 remains the general method reference outside automotive. The Excel export (Office Open XML, ISO/IEC 29500) is where data leaves the tool: treat it as a controlled snapshot for audit evidence under IATF 16949:2016, not as a live sync channel.

Choosing the governing standard

Use AIAG-VDA (AP with 1–10 S/O/D tables) when OEM customers expect IATF 16949 evidence. Use SAE J1739:2021 when a customer-specific requirement names it, and check which rating-table edition applies. Use IEC 60812:2018 for non-automotive work, where RPN or criticality ranking may be acceptable. Never mix RPN and AP in one analysis; record the chosen method in the header before Step 1.

Pre-implementation checklist

Before structure analysis, gather the system boundary and interfaces (block/boundary diagram), requirement IDs to reference in function text, the customer's rating-table edition, the Control Plan template and the named owner of the master record. Decide up front whether the FMEA Tool project or a PLM item is the system of record. The other side receives exports only, which keeps the two copies from drifting apart.

Illustrative scenario (analytical example, not measured data)

A supplier with 3 product lines and about 40 process steps per line keeps one PFMEA per line, exports Excel at each design freeze, and stores the file with a revision ID and checksum in document control. Limit: if several engineers edit the same line at the same time, or the OEM requires two-way PLM/requirements links, move to a server-integrated workflow. Recovery: each frozen export is the authoritative baseline. If the working project diverges, compare it row by row against the baseline and check that the High/Medium/Low AP counts match before re-releasing.

Can the FMEA Tool Excel export serve both as IATF 16949 audit evidence and as an interchange file for PLM/QMS systems?

As evidence, yes, if you add revision, date, approver and team under your own document control (ISO 9001:2015, clause 7.5). The export is a frozen snapshot of the 7-step analysis with S/O/D ratings and Action Priority, which matches the documentation expected by the AIAG & VDA Handbook. As an interchange file, treat it as one-way only. Any spreadsheet or ETL tool can read OOXML, but the column meanings are not a standardized schema. Map the columns explicitly before importing, then check that row counts and the AP distribution match. No certification is implied: conformance stays the organization's responsibility and is checked in its own audits.

Back to FMEA Tool · Domains

← Back to FMEA Tool
Engineering & Architecture Brief

FMEA Reference Architecture: Aligning DFMEA/PFMEA Data with AIAG-VDA, SAE J1739 and IEC 60812 for Interoperable Exchange

An FMEA tool sits between requirements/design data and the Control Plan, so the key architecture decisions are which standard defines your data model and which file format carries it across system boundaries. FMEA Tool follows the 7-step structure and Action Priority (AP) logic of the AIAG & VDA FMEA Handbook (1st edition, 2019). SAE J1739:2021 uses the same approach for North American programs, and IEC 60812:2018 remains the general method reference outside automotive. The Excel export (Office Open XML, ISO/IEC 29500) is where data leaves the tool: treat it as a controlled snapshot for audit evidence under IATF 16949:2016, not as a live sync channel.

Choosing the governing standard

Use AIAG-VDA (AP with 1–10 S/O/D tables) when OEM customers expect IATF 16949 evidence. Use SAE J1739:2021 when a customer-specific requirement names it, and check which rating-table edition applies. Use IEC 60812:2018 for non-automotive work, where RPN or criticality ranking may be acceptable. Never mix RPN and AP in one analysis; record the chosen method in the header before Step 1.

Pre-implementation checklist

Before structure analysis, gather the system boundary and interfaces (block/boundary diagram), requirement IDs to reference in function text, the customer's rating-table edition, the Control Plan template and the named owner of the master record. Decide up front whether the FMEA Tool project or a PLM item is the system of record. The other side receives exports only, which keeps the two copies from drifting apart.

Illustrative scenario (analytical example, not measured data)

A supplier with 3 product lines and about 40 process steps per line keeps one PFMEA per line, exports Excel at each design freeze, and stores the file with a revision ID and checksum in document control. Limit: if several engineers edit the same line at the same time, or the OEM requires two-way PLM/requirements links, move to a server-integrated workflow. Recovery: each frozen export is the authoritative baseline. If the working project diverges, compare it row by row against the baseline and check that the High/Medium/Low AP counts match before re-releasing.

Technical FAQ: Can the FMEA Tool Excel export serve both as IATF 16949 audit evidence and as an interchange file for PLM/QMS systems?

As evidence, yes, if you add revision, date, approver and team under your own document control (ISO 9001:2015, clause 7.5). The export is a frozen snapshot of the 7-step analysis with S/O/D ratings and Action Priority, which matches the documentation expected by the AIAG & VDA Handbook. As an interchange file, treat it as one-way only. Any spreadsheet or ETL tool can read OOXML, but the column meanings are not a standardized schema. Map the columns explicitly before importing, then check that row counts and the AP distribution match. No certification is implied: conformance stays the organization's responsibility and is checked in its own audits.

Related Architecture Specifications (FMEATOOL): fmeatools.com · freefmea.com

More Technical Articles on fmeatool.com

Using FMEA for Autonomous Diagnostics, Predictive Maintenance and Cross-Layer Security: A Reference Architecture →DFMEA for Edge Compute Offloading: Deadlines, Protocol Conformance and SLA Evidence →Architecture Decision Guide: Local-First DFMEA/PFMEA Execution, Fault-Isolated Storage, and Zero-Trust Data Portability →Timing Failure Modes in DFMEA: Deterministic Telemetry, Sub-Millisecond Latency Budgets and HIL vs. Digital-Twin Detection Controls →