AIAG & VDA FMEA Handbook — First Edition
The handbook provides a harmonized seven-step approach for design FMEA, process FMEA, and supplemental FMEA for monitoring and system response.
What the authority record establishes
The handbook provides a harmonized seven-step approach for design FMEA, process FMEA, and supplemental FMEA for monitoring and system response.
Industry method; required use depends on customer, contract, and organization policy
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
FMEA tools need structure, function, failure, risk, optimization, result, and control-plan lineage; a risk-priority number field alone does not establish method support.
Affected operating stages
- Planning And Preparation
- Structure Analysis
- Function Analysis
- Failure Analysis
- Risk Analysis
- Optimization
- Results Documentation
Capabilities to examine
FMEA And Control Plans
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for FMEA and control plans.
Advanced Product Quality Planning
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for advanced product quality planning.
Quality Risk Management
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for quality risk management.
Change Control And Configuration Traceability
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for change control and configuration traceability.
Affected buyer audiences
- design and process engineers
- quality planners
- supplier-quality teams
- FMEA software providers
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
A provider's claimed handbook support does not establish correct organizational method application or customer acceptance.