Level 4 made you accountable for how a manufacturing company uses AI. Level 5 makes you the person who builds the thing that runs every day without anyone watching it, and who can explain exactly what it is allowed to do, what it cannot reach, and what happens the morning it goes wrong.
The course is written for the practitioner in a small or mid-size manufacturer who will actually specify and stand up automation: the operations or IT manager, the continuous-improvement engineer, the systems administrator, the ERP or MES owner, or the outside integrator working with them. It assumes the governance from Level 4 exists, and it assumes you will build within it rather than around it.
Five modules. The first is about agents: what an agent actually is once the marketing is removed, how to write a bounded authority statement before any tool is connected, and how to reason about the failure mode the OWASP list calls excessive agency, where a system that could take an action eventually does. The second is orchestration: decomposing a plant workflow into steps with explicit state, designing idempotent and retry-safe steps so a duplicate trigger cannot create a duplicate purchase order, and building the human-in-the-loop approval gates that carry real information rather than a yes button. The third is integration: reading an API contract, choosing between polling, webhooks, and scheduled batch, authenticating with service accounts scoped to least privilege, and connecting to ERP, MES, QMS, and CMMS while the boundary between the enterprise network and the control network stays exactly where it is. The fourth is defence: role-based access derived from the plant's data classification, prompt-injection defences against supplier documents and machine-generated text, secrets handling, logging that would actually let you reconstruct a bad day, monitoring with thresholds someone answers, and an incident runbook including the kill switch. The fifth is delivery: measuring an automation honestly, costing it including the review time it creates, running a staged rollout with a rollback, and the implementation capstone.
You will not need to be a programmer. Every exercise can be completed with a specification, a diagram, a spreadsheet, and the configuration screens of tools you already have. What the course insists on is precision: a step that cannot be described exactly cannot be automated safely, and an authority that has not been written down has not been bounded.
The capstone is a complete automation implementation: the design, the authority statement, the integration specification, the security and access design, the test evidence, the staged rollout with rollback, the monitoring plan, the incident runbook, and the measured results. This is an independent educational course offered by AI Coalition Network. It does not replace engineering judgment, a quality management system, an operational-technology security programme, or the laws and regulations that apply to your plant, and nothing in it authorises an AI system to control equipment.