Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document FMEA and control plans while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
IATF 16949:2016
IATF 16949 defines automotive-sector QMS requirements in conjunction with ISO 9001 and sits within a separately governed certification scheme. Automotive buyers need core-tool, supplier, customer-specific, audit, traceability, control-plan, and change workflows—not a generic ISO 9001 label.
AIAG APQP 3rd Edition and Control Plan 1st Edition
AIAG separated Control Plan into its own first edition and updated APQP in a third edition addressing sourcing, change management, metrics, risk mitigation, gated management, and traceability. Software mappings need edition-aware phases, gates, deliverables, risk, sourcing, traceability, and control-plan relationships rather than a static checklist labeled APQP.
AIAG & VDA FMEA Handbook
The handbook provides a harmonized seven-step approach for design FMEA, process FMEA, and supplemental FMEA for monitoring and system response. FMEA tools need structure, function, failure, risk, optimization, result, and control-plan lineage; a risk-priority number field alone does not establish method support.
AIAG-VDA SPC Manual 2026
AIAG and VDA published a harmonized SPC manual covering process monitoring, capability studies, production-equipment and process qualification, and connection with FMEA, Control Plan, and measurement-system methods. SPC product mappings, templates, training, and analytics need an explicit method version and migration decision instead of silently relabeling historical charts or capability studies.
Operating domains
Design and process risk planning
The connected planning domain for product and process requirements, advanced product quality planning, failure-mode analysis, control plans, launch gates, lessons learned, and later changes that alter risk or control assumptions.
Supplier quality, APQP, and part approval
The intercompany operating domain for qualifying suppliers, communicating technical and customer requirements, coordinating launch evidence, reviewing production-part submissions, controlling supplier changes, and closing supplier-caused nonconformance.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should FMEA and control plans produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
AIAG and VDA publish a harmonized SPC manual — Automotive manufacturers, suppliers, training owners, and software providers need edition-aware method, template, calculation, and migration decisions.
Octave launches Reliance Advanced Manufacturing — The package increases competition around APQP and production-quality depth, while buyers still need module, configuration, content, integration, service, and availability evidence.