Audi press-shop inspection

What this models

This example runs on the Press-inspection-class that inherited the whole duty network: 6 components and 12 pathways between them. Every context in the Lab is a stylized model, never a reconstruction of any actual deployment, and each assumption behind it carries a provenance label.

Evidence base: 3 assumed · 1 published baseline. In the Lab, the shaded evidence band behind each headline readout draws its width from the least-established class below.

• assumed

  This deployment's defining governance fact is replacement: the network inherits crack inspection from both prior generations - the manual visual check and the fixed-rule cameras - so no per-part human judgment runs alongside it, and the surviving human touchpoint sees only what the network rejects. The cross-plant image corpus is drawn as its own inbound source at full strength because it is the record's documented defining input: several terabytes from seven presses and several plants, which is what makes the model general and its blind spots correlated. The in-house team is its own group of staff because this is a documented in-house build running since mid-2016 - improve-model is genuinely this organization's lever. A heavy workload against limited capacity: line-speed part flow met by a giant manufacturer's resourced quality organization - the replacement thinned where the human looks (the rejected fraction only), not how staffed the function is.

• assumed

  The two latent checks are the human eyes that remain possible after the replacement. Drift monitoring is the empty model-side check: dies wear, part designs change, and a model trained on yesterday's presses degrades with no inspector left to notice first. Sampled re-inspection of passed parts is the empty oversight check: a flagged part is examined by construction, but an escape is invisible unless the quality system deliberately re-performs a fraction of the inspection it retired. Both are ordinary quality-system machinery; the replacement is what makes them the only remaining coverage of this defect class.

• baseline

  Honesty caveat carried on the diagram: the record is a reprint of the manufacturer's own press material - it documents the development lineage, the data scale, and what the system replaced, and publishes no quantitative defect-rate figures, so the benefit magnitude is a corporate claim rather than an audited measurement. Consistent with the domain caveat, no named manufacturer has publicly attributed a shipped-defect escape to its AI inspection, so the failure regime here is mechanism-level, never a claim that this manufacturer's network let a defect ship.

• assumed

  No product-safety or defect-escape outcome is modeled here. This Lab reads institutional propagation only, and the parts and the people who ride in the vehicles are boundary-only. The development lineage, the data scale, the replacement, and the unpublished magnitudes live in the case file, and are never computed from anything in this diagram.

What this example does not show

• No product-safety or defect-escape outcome is modeled. The Lab reads institutional propagation only; the parts and the people who ride in the vehicles are boundary-only, and the development lineage, data scale, and replacement live in the case file, never computed on this diagram.
• The record is a reprint of the manufacturer's own press material with no quantitative defect figures, so the benefit magnitude is a corporate claim entered as such; per the domain caveat, no named manufacturer has publicly tied a defect escape to its AI inspection, and nothing here claims this one did.

Sources and evidence

What this example rests on, claim by claim. Every entry resolves to the same ledger the Evidence Registry publishes.

• A large automaker developed an in-house deep-learning system to detect hairline cracks in pressed sheet-metal parts, trained on several terabytes of images drawn from seven presses at its home plant plus several sister plants, in development since mid-2016 and tested for series deployment. The documented change is a generational replacement: the system takes over an inspection duty previously performed by manual visual checks plus fixed-rule camera systems, rather than augmenting a human inspector's judgment on each part. The record — a reprint of the manufacturer's own press material with its CIO quoted — documents the development lineage, the data scale, and what the system replaced; it publishes no quantitative defect-rate figures, so the deployment's benefit magnitude is a corporate claim, not an audited measurement.

  empirical
  • Trade press Just Auto (2018, October 17). Audi develops AI software for quality inspections in press shops. https://www.just-auto.com/news/audi-develops-ai-software-for-quality-inspections-in-press-shops/

• The governance shape of this deployment is inheritance rather than assistance: by replacing the manual visual check and the fixed-rule camera generation, the learned system inherits the whole inspection duty for the defect class it covers, so there is no per-part human judgment running alongside it to catch what it misses. Its training data is pooled across presses and plants, which means one model's blind spots are correlated across every line it inspects. The failure regime is mechanism-level — drift as dies wear and parts change, complacency over an inspection nobody re-performs — because no named manufacturer, including this one, has publicly attributed a shipped-defect escape to its AI inspection.

  empirical
  • Trade press Just Auto (2018, October 17). Audi develops AI software for quality inspections in press shops. https://www.just-auto.com/news/audi-develops-ai-software-for-quality-inspections-in-press-shops/

Where this connects

Institutional pressures in this domain

• Reviewer bottleneck — One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.
• Austerity & recovery incentives — Cost-cutting and overpayment-recovery targets tilt the system toward denial and enforcement errors.
• Data & policy drift — The world, the intake process, and the rules change under a system trained on how things used to be — two mechanisms with different remedies: the statistical properties of what the system processes move (concept drift), or the mixture of inputs arriving in deployment differs from the mixture it was trained on (covariate shift).
• Vendor opacity — The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
• Compliance over substance — Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.

All of them in context on the Industrial QA & operations AI domain page.

Levers available here and the patterns behind them

• Upgrade model — Improve the model
• Check with a second model — Cross-model verification
• Review on schedule — Oversight cadence & retrospectives
• Review the riskiest first — Risk-tiered oversight
• Check copied records — Reconcile copied records
• Keep skills sharp — Deskilling-arrest mandate
• Escalate checks — State-feedback vigilance
• Pause AI on alarms — Deployment circuit-breaker

Documented case histories

• The inspection the model inherited
• The maintenance contract that prices every miss
• The AI flags and the line worker responds
• A ninety-percent cut in false alarms and the loop that made it
• Tuned to over-reject and the miss it still has to guard