Versatile AI Risk Assessment
Manufacturing, retail and logistics

Visual and acoustic quality inspection

Also known as: AI-based visual inspection

Cameras or microphones capture components and products on the production line; a model checks defects, completeness and correct variants.

Explore the interactive model

Export handout

A concise PDF covering how the system works, its data flows and points to investigate, ready to share.

The explanations and measures describe the typical system design. Extensive personal changes add an appendix.

Understand the use case

What defines this use case?

The model learns from recordings labelled by specialists as good or defective, then checks each item at line speed. BMW states that it uses this in its plants, including driving sound analysis at Dingolfing; Audi has trialled sheet-metal crack detection.

This page describes a typical system design. Actual data flows and permissions depend on your implementation.

System design
Analysis and processing
Ability to act
Action permissions depend on integration
Fields of use
automotive industry
Also known as
automated visual inspection, machine vision inspection, visual inspection

How it works, step by step

System design and data flows

  1. Input data

    Cameras, microphones or other sensors record each item on the line.

    Some stations analyse image and audio together. Line cameras can also capture workers.

  2. Processing

    A model compares the recording with patterns learned from labelled examples.

    The model compares a product's visual or acoustic signals with learned or specified quality characteristics. This produces a classification or flagged anomalies. Whether a product is rejected is determined by subsequent inspection or equipment control, according to its rules.

  3. Results

    The result is “acceptable” or identifies defects, missing parts or an incorrect variant.

    The result describes the defined model task. A match, category or forecast acquires its professional significance only in conjunction with the underlying data and intended use.

  4. Use and impact

    Defective parts are reinspected, reworked or rejected; others go to assembly or customers.

    Integration determines whether the result is simply displayed, adopted after approval or written directly into a business application. These variants differ in their data flows and permissions.

Explore the system design: Select a component to see its task, incoming and outgoing data, and role in the use case. The guided walkthrough explains each phase. Then use Yes, Uncertain and No to represent your specific system variant.

How the system is built

5 review first12 clarify7 baseline threats

InputProcessingResultImpact Externalaccess 04 Input 03 Third-partycontent 00 AI model 10 Providerservice 03 Documentcollection 00 Memory 00 Training andfeedback 30 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 01 person 10 Affectedperson 00 AI serviceswithout approval 01 Externalaccess 04 Input 03 Third-partycontent 00 AI model 10 Providerservice 03 Documentcollection 00 Memory 00 Training andfeedback 30 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 01 person 10 Affectedperson 00 AI serviceswithout approval 01
  • Present
  • Depends on your system
  • Absent
  • Review first
  • To clarify

In this system design: 5 to review first, 12 to clarify, 7 baseline threats.

Architecture as a list

How it differs from similar use cases

Data and information

Input data and information sources

Line cameras can also capture workers. Inspection images and defect data reveal design and manufacturing progress and can be trade secrets.

Processing and operating environment

Alongside in-house development, suppliers offer systems with pretrained models.

Storage and further use

Models learn from the organisation's own components; Audi developed its system itself. Staff reinspection findings can feed back as new training examples.

Results and data sharing

Depending on integration, it blocks an item in manufacturing control or only flags it for reinspection. A system controlling a diverter or gripper to reject defective parts directly acts on the line.

Using a provider does not automatically determine where processing takes place. Storage location, subcontractors, deletion periods and use for training must be checked for the specific deployment.

Assess risks and determine measures

From understanding the system to analysing risks

  1. Define the system boundary

    Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.

  2. Investigate threats

    Relate review candidates to actual data flows: what could happen, and who would be affected?

  3. Assess risk

    Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.

  4. Provide evidence of measures

    Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.

Key threats in the application context

  • 3 particularly important
  • 2 typical
  • 12 depending on the system
  • 7 additional threats for every AI system

A total of 24 threats from the threat catalogue may be relevant to this use case.

Priority review points

  1. Model Drift & Degradation

    A new variant, supplier or lighting changes recordings without model retraining. The inspection then passes defects or rejects good parts.

  2. Targeted Poisoning / Label Poisoning

    Someone with training data access deliberately labels certain defect images as acceptable. The model then passes that defect, sending parts unnoticed into assembly or to customers.

  3. Overreliance

    Relying on the camera to find every defect can lead to dropping manual sampling. Defect types the model has never seen remain undetected.

2 further review candidates in the typical design

Other relevant threats

  1. Training Data Poisoning

    Your own training or operational feedback can introduce manipulated data into training datasets.

    Listed because of this characteristic

    • Learns from your own data
  2. Backdoor ML Model

    Training data or an adopted base model can introduce hidden triggers for misbehaviour.

    Listed because of this characteristic

    • Learns from your own data

Up to 12 further threats may apply, depending on your system design. Nine threats need to be reviewed for every AI system. Two of these are particularly important here and are therefore listed above.

System features and open questions

Each Yes adds further threats to your checklist, up to 12 in total. If you cannot yet answer a question, include its threats in your review.

How many threats a Yes adds
  • Added by this Yes

How your system is built

Can the system change things itself, such as storing data, sending messages, initiating transactions or granting permissions?

Depending on integration, it blocks an item in manufacturing control or only flags it for reinspection.

If yes, add

Does the system directly move or control something physical, such as motors, valves, vehicles or temperatures?

A system controlling a diverter or gripper to reject defective parts directly acts on the line.

If yes, add

How you operate the system

These questions arise for almost every AI system.

Controls and implementation

Measures for the priority review areas are expanded. Each linked measure explains how to implement it.

Controls for the remaining threats are available on their pages in the threat catalogue.

AI Act provisions

Applies to every AI system

Art. 4: AI literacy

Applies if staff or appointed representatives operate or use AI systems.

Applies since 2 February 2025.

Obligations and details for Art. 4: AI literacy
Who bears the obligations
Provider, Deployer, Product manufacturer, Provider of a general-purpose AI model

Detailed obligations

Generally does not apply

Art. 6 para. 1, Annex I Section A: Safety component of an assessed product

An end-of-line inspection that only reports defects is generally not a machine safety component. This may differ if it intervenes in machine control.

Obligations and details for Art. 6 para. 1, Annex I Section A: Safety component of an assessed product
The general condition is
Applies if the system is itself a product or a safety component of a product requiring third-party assessment under Annex I legislation, such as machinery, lifts, medical devices or toys.
Exception
Systems improving only operation, performance or comfort without a safety role are not safety components under Article 6(1a)–(1c).
Who bears the obligations
Provider, Deployer, Product manufacturer

Detailed obligations

Classify your system with the quick checker All obligations in the obligations compass

Cross-cutting threats

Review these threats for every AI system, whatever its purpose.

Why these threats always belong on the checklist

Atypical system features

View 17 further questions

If any of these features does apply to your system, add the listed threats.

Sources

Related use cases

Also in the field of Manufacturing, retail and logistics

Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured