AIAG and VDA publish a joint statistical process control manual

What changed in the maintained record

AIAG's official announcement identifies a new joint AIAG–VDA statistical process control manual and describes it as a harmonized approach intended for the global automotive supply chain. The source names process monitoring, capability studies, production-equipment and process qualification, and relationships with related quality methods.

Quality Systems Index records the named source, status, date, affected operating layer, and claim class separately. The source establishes the announced standard or product record; it does not establish a buyer's implementation, conformity, statistical validity, production outcome, or customer acceptance.

The production-system consequence

Quality teams should inventory the SPC procedures, training, templates, calculation services, control-chart configurations, capability-study assumptions, and supplier requirements that currently cite an older or region-specific method. Software records need an explicit method version rather than a generic SPC label.

The practical review should follow the change into controlled methods, data definitions, product and process context, responsible roles, integration handoffs, historical records, and exception behavior. That is where a release note or standard edition becomes an operating decision rather than a headline.

What quality and manufacturing leaders should test

Request the proposed product's exact method and release version. Demonstrate how it distinguishes specification limits from control limits, tests stability before capability interpretation, preserves study populations and exclusions, versions reaction rules, and prevents a method update from silently relabeling historical analysis.

Ask for a representative part, process, supplier, characteristic, lot or serial, user, and exception. Preserve which facts came from the source, which behaviors were demonstrated, which depend on configuration or services, and which remain not established.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Quality Systems Index will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.