Every machine on the floor, placed in its zone, with its duties and the questions for the integrator.
Paste the list of automated equipment on your floor. Get, per asset, what it can act on and what a wrong action costs, the zone and conduit it belongs in and the security level to target, the duties the asset owner carries under IEC 62443 and NIST SP 800-82, whether an adaptive controller makes it a high-risk AI system, the safety standards that govern its class, and the questions to put to the integrator before the next change.
| Asset | Zone | SL-T | Behaviour | Remote |
|---|---|---|---|---|
| Line 2 case packing arm remote into zone no zone named | cell | 3 | fixed | yes |
| Cobot at station 9 no oversight noted no safety function noted | cell | 2 | adaptive | no |
| AGV fleet, 12 units remote into zone | line | 3 | fixed | yes |
| Autonomous forklift no oversight noted | line | 2 | adaptive | no |
| Safety PLC line 2 shares a conduit vendor share | safety | 3 | fixed | no |
| SCADA server vendor share | supervisory | 3 | fixed | yes |
| Steam boiler end of support no zone named | safety | 3 | fixed | no |
| Crumb reclaim vortex unit unrecognised | not placed | n/a | fixed | no |
| 36 assets, 50 units | 5 zone classes | 4 adaptive | 3 remote |
Paste the list you already have
The CMMS export, the maintenance asset list or the commissioning register: one asset per line, with the type, the vendor, what it does, the network it sits on, whether it is reached remotely, whether its controller adapts, who oversees it, what safety function guards it and when it last changed, in any order the header names. Every line is matched against a published dictionary of 49 machine classes in seven families; a line that matches nothing is marked unrecognised and never guessed. Vendor names are kept as labels: the register never rates a vendor or a machine.
Read the zone drawing and the reach of each asset
Per asset: the zone class it belongs in (cell, line, plant supervisory, site business, safety) with the IEC 62443-3-2 reasoning and a target security level derived from the class and raised for remote access, what it acts on physically and what a wrong action reaches (a person in the cell, a batch, a line, a release), whether it is adaptive or fixed-program, and the days since its last change. Per register: assets by zone class, by vendor with the share, by family; the adaptive count, the remote-access count, the assets whose wrong action reaches a person, and the findings.
Take the duties and the questions to the integrator
Tick the regimes that reach you and each asset carries the rows that attach, each saying who it binds: the asset-owner duties of IEC 62443-2-1 and the system requirements of 62443-3-3 by zone, the NIST SP 800-82 overlay, the AI Act deployer duties where a controller adapts, and what the owner demands and holds under the Machinery Regulation. The integrator and supplier rows are rendered as what to ask, never as your duty. Requirement text drawn from a human-verified compliance corpus under licence. The zone and conduit sheet, the integrator question list and the Machinery document checklist export on Solo.
Why a register and not an OT security platform
The platforms are built for the utility with a sensor budget and a security operations centre. The operations manager at a 550-person plant has a maintenance asset list, an integrator on the phone and a board that has just read that physical automation is the next place capital goes and that its security and runtime integrity are now the question. Before the platform conversation, somebody has to say what each machine can act on, which zone it belongs in, who can reach it, whether its controller learns, and what to ask the integrator before the next change. That is the register this builds, in your browser, from the list you already hold.