An $18M round landed this week for a start-up called Magentic, which promises to build an AI workforce for industrial operations. KPMG has taken to describing AI as a force multiplier for manufacturing organisations. Gartner warns of a trust hurdle between today's pilots and genuinely autonomous operations. I read all three in one sitting and noticed what none of them mentioned: your plant is about to receive new headcount with no personnel file. The agent will not walk through the security gate or sit the induction. It arrives the way software arrives – through the IT door – and within a month somebody will hand it write access to product dispositions.
I built the personnel side of a greenfield plant for 900-plus people, so forgive me for reading a Silicon Valley storyline as an HR problem.
Your plant already knows how to hire
When I set up the QA/QC department for SNOP's greenfield plant, inspector onboarding was among the first things I designed – before the first coordinate measuring machine was installed, before the first control plan was signed off. The ladder was unglamorous and non-negotiable. A competency matrix mapped every inspector to the characteristics they were permitted to disposition, station by station and control-plan revision by revision. Nobody dispositioned alone for roughly three months; no decision left the building without a qualified senior countersigning it. Sign-off gates ran observer, assisted, supervised, solo. And the training records were written so a VDA 6.3 auditor could open the file and find evidence rather than intention.
That discipline was one of the levers behind a 70% reduction in defect costs, because escape prevention is cheaper than every alternative. I once watched a VDA 6.3 auditor park an entire line's sign-off matrix because a welding parameter change had silently triggered requalification for two operators and nobody had noticed. IATF 16949 is blunt on the point – competence, evidence, records – and clause 7.2 does not care whether the employee is made of carbon. Yet the same plants that run this ladder for people will grant an agent autonomous disposition rights on day one, because the agent arrived as a licence rather than a CV.
The trust hurdle is a qualification problem
Trust is not a sentiment. Trust is a file.
Plants do not run on trust; they run on qualification. When a new gauge arrives, nobody asks the vendor how confident it feels. We run measurement-system analysis: repeatability, reproducibility, bias against known standards. An agent that dispositions parts is a measurement system with opinions, so it clears the same bar. Blind gauge R&R against your best human dispositioners on the same part mix. Track the escape rate – the bad parts it waved through – and the false alarms, priced in € of sorting hours and stopped lines. Then boundary conditions, in writing: qualified inside the envelope it was validated on – part families, surface finishes, sensor firmware, control-plan revision – and unqualified outside it, like an inspector trained on stampings who wanders into a weld cell.
I build multi-agent AI systems myself, and my orchestration platform runs 63+ models in parallel with consensus synthesis precisely because individual models disagree – and the disagreements cluster exactly where a single agent would have been confidently wrong. If I want 63 second opinions before acting on an output, I am not handing one agent unsupervised write access to a QMS on the strength of a demo.
Open a personnel file for the agent
The file writes itself, because industry has been writing these files for decades:
- Decision rights in writing. Which part families, which characteristics, which disposition codes – plus hard limits: may place product on hold, may not scrap above a defined value.
- Validation evidence. The data set the agent was qualified on, sample sizes, escape rate at qualification, boundary conditions. A vendor who refuses to hand over the validation envelope would be a hiring red flag in any other context.
- A named supervisor of record. A person whose signature sits on the file and on every periodic review. "The IT department" is not a supervisor.
- Requalification triggers. Every control-plan change, every process parameter change, every sensor swap, every model update. Agents change silently under you; an operator's drift you can at least see coming.
Then the appraisal nobody schedules. Quarterly, on the record: escape-rate drift, false-alarm cost, decision latency, escalations to the supervisor of record. One wiring-harness maker is already co-developing agents meant to learn skilled techniques at production facilities. Fine – learned skills belong on a training record with a revision level, not in a press release. Schedule the review anyway.
Key takeaways
- Qualify agents through the gate you built for people: competency scope, a supervised release period with countersigned decisions, recorded sign-off before any solo authority.
- Validate like a measurement system: blind R&R against your best dispositioners, escape rate and false-alarm cost tracked in €, boundary conditions published and enforced.
- Keep a personnel file: written decision rights, a named supervisor of record, requalification triggered by control-plan and model changes – evidence a VDA 6.3 auditor can actually read.
- Run the full employment cycle: appraise drift quarterly, and retire agents whose numbers would get an operator dismissed. Autonomy is earned in releases, not granted in a demo.
The workforce framing cuts both ways, and that is the useful part of it. Call agents headcount and they fall under hiring discipline: probation before authority, appraisal after it, dismissal when the arithmetic justifies it. No plant keeps an operator whose escapes the customer is feeling; the same maths retires an agent. Gartner's trust hurdle dissolves the moment we stop treating agents as software to be adopted and start treating them as employees to be qualified. The matrices, the gates, the records, the triggers – we already built them for people, and they work on anything we let touch product. A demo gets an agent an interview. Only the file gets it a badge.