# The manufacturing AI rulebook: what actually applies to your plant
A vision system on a welding line flags defective chassis welds with 98% accuracy. A cobot on the same line adjusts its grip force in real time based on part weight, sensed by a camera. One of these systems faces almost no direct AI-specific regulation. The other can trigger conformity assessments, technical documentation requirements, and CE marking obligations under two overlapping EU frameworks. Most plant managers cannot tell you which is which. That gap is where regulatory exposure hides.
This lesson gives you the mapmapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition →: which manufacturing AI use cases actually trigger hard legal obligations, and which are lower-risk despite sounding scary in a boardroom slide.
Manufacturing AI does not answer to one law. It typically sits under three layers at once:
1. The EU AI Act (Regulation (EU) 2024/1689, the first comprehensive horizontal AI law, entered into force August 2024, with obligations phasing in through 2027). This classifies AI systems by risk level, not by industry.
2. Machinery safety law: the EU Machinery Regulation (EU) 2023/1230, replacing the old Machinery Directive, effective January 2027, which governs physical safety of machines including those with AI-driven "safety functions."
3. Sector and technical standards, like ISO 10218 (industrial robot safety) and ISO/TS 15066 (collaborative robots), which are not laws themselves but are the technical benchmark regulators and courts point to when deciding if you met a legal "state of the art" duty.
In the US, there is no direct equivalent to the AI Act yet. Manufacturers there answer mainly to OSHA (Occupational Safety and Health Administration) general duty clauses, product liability law, and voluntary NIST AI Risk Management Framework guidance. If you export to the EU, though, EU rules follow the product, not just the factory location.
The AI Act sorts systems into four tiers: prohibited, high-risk, limited-risk (transparency duties), and minimal-risk. Most plant AI lands in the last bucket. The trap is the high-risk category, defined mainly by Annex III of the Act.
For manufacturing, two Annex III triggers matter most:
What does *not* automatically qualify: predictive maintenance models forecasting bearing failure, quality-inspection vision systems flagging defects for human review, and demand-forecasting AI for production planning. These affect cost and quality, not physical safety or employment decisions directly, so they usually sit outside Annex III, though transparency duties may still apply if the system interacts with people (Article 50).
Worked example. A stamping press uses a vision model to detect hand intrusion and stop the press. That is a safety component of machinery: high-risk under the AI Act, and it must also satisfy Machinery Regulation essential health and safety requirements, likely demonstrated via conformity with ISO 13849 (safety-related control systems) or ISO 10218 for robotic cells. Two regulatory regimes, one system.
Compare: a vision model on the same line that photographs finished parts and scores paint-finish quality for a rework queue. No safety function, no worker-management scoring. Minimal-risk under the AI Act, though you should still document it for internal quality assurance and customer audits.
The EU Machinery Regulation lists "safety functions" that, when performed partly or wholly by AI, force a third-party conformity assessment rather than manufacturer self-certification. This is the sharpest teeth in the whole stack for factory-floor robotics.
ISO 10218 (parts 1 and 2, industrial robots and robot systems) and ISO/TS 15066 (collaborative robot force and speed limits) are the reference standards insurers, auditors, and notified bodies use to judge whether your robotic cell meets the "state of the art." Following them does not exempt you from the AI Act, but it is strong evidence of compliance for the machinery side and generally accelerates a high-risk AI Act conformity assessment because your technical file already exists.
Practical rule of thumb for a plant engineer:
Teams can encode this logic into an intake checklist before any AI project starts. A simplified version:
def classify_ai_use_case(controls_physical_hazard,
influences_worker_employment_decisions,
interacts_directly_with_humans):
if controls_physical_hazard:
return "HIGH-RISK: AI Act Annex III + Machinery Regulation"
if influences_worker_employment_decisions:
return "HIGH-RISK: AI Act Annex III (worker management)"
if interacts_directly_with_humans:
return "LIMITED-RISK: transparency duties (Art. 50)"
return "MINIMAL-RISK: internal governance only"This will not replace legal review, but it stops 80% of low-risk quality-control and forecasting projects from being routed through an expensive compliance process they don't need, and flags the 20% that genuinely do.
Knowledge check
1. Why might a vision system that flags defective welds face less direct AI-specific regulation than a cobot that adjusts grip force based on sensed data?
2. What is the primary basis the EU AI Act uses to classify and regulate an AI system?
3. What role do technical standards like ISO 10218 and ISO/TS 15066 play in manufacturing AI compliance?
4. Select ALL correct answers about how manufacturing AI regulation works in the EU versus the US as described in the lesson.
Select all the correct answers.
5. Select ALL correct answers about why a plant manager might fail to recognize regulatory exposure from AI on the factory floor.
Select all the correct answers.
If a system lands in Annex III high-risk, the AI Act obligations (mostly binding from August 2026) include:
This is real engineering and paperwork overhead, not a checkbox. A mid-size automotive supplier deploying AI-controlled robotic welding cells across multiple lines should budget for a dedicated compliance owner, not a side task for the safety engineer.
For low-risk systems (most predictive maintenance and demand planning tools), the practical governance need is lighter: document intended use, monitor for model drift, keep a human-in-the-loop for high-cost decisions, and retain training data lineagedata lineageData lineage maps how data moves and transforms across systems, from origin to consumption, showing where it came from, what changed it, and where it goes.View full definition → in case you later need to prove non-bias or explain an error.
Two useful anchors as you build internal policy: