Cell Register
For the operations manager who runs the floor, and the OT security lead who answers for it

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.

Paste your own listEight assets free, no account. Every zone, every count and every finding is arithmetic on the lines you paste, in your browser. Nothing leaves it until you choose to save.
An engineer working beside an automated machine on a production floor
Walk into the next change review knowing every machine's zone, its owner duties and the questions for the integrator, from the equipment list you already keep. Paste a plain asset list and get it read against IEC 62443, NIST SP 800-82 and the AI Act in your browser, cited so you can check it, with no platform installed on your network.
Specimen: a 550-person food manufacturer, one siteeight of 36 assets
AssetZoneSL-TBehaviourRemote
Line 2 case packing arm remote into zone no zone namedcell3fixedyes
Cobot at station 9 no oversight noted no safety function notedcell2adaptiveno
AGV fleet, 12 units remote into zoneline3fixedyes
Autonomous forklift no oversight notedline2adaptiveno
Safety PLC line 2 shares a conduit vendor sharesafety3fixedno
SCADA server vendor sharesupervisory3fixedyes
Steam boiler end of support no zone namedsafety3fixedno
Crumb reclaim vortex unit unrecognisednot placedn/afixedno
36 assets, 50 units5 zone classes4 adaptive3 remote
Zone class, SL-T (the IEC 62443 target security level), behaviour and remote access as the register reads them from the pasted columns or derives them from the class default. The full register adds what each asset acts on, the vendor share, nine findings, the obligation rows under IEC 62443, the AI Act and the Machinery Regulation, and the integrator questions per class.
One asset per line: Asset | type | vendor | what it does | zone or network | networked | remote access | adaptive | oversight | safety function | commissioned | last change | support status | declaration held. Tabs, commas or pipes; a header row is optional and its column names are recognised in any order; Asset, type alone works. A first line iec 62443: yes | as at: 2026-09-20 | support threshold: 2014 ticks the regime and pins the dates.
Classification and every figure run in your browser against a published dictionary. Nothing is sent anywhere until you choose to save.
01

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.

02

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.

03

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 in our own words, read clause by clause from the published standards. 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.

The dictionary and the obligation table are ours and published in full: every machine class it recognises, in seven families, and what each regime attaches and who it binds. The requirement text behind every obligation is in our own words, read clause by clause from the published standards; the safety standards per class are named with their clause topic and never quoted. The register classifies your own list and states the obligation in our words; it never rules on a machine or a vendor.

Cell Register: the questions buyers ask

What is Cell Register?

Cell Register takes the list of automated equipment on your floor and places each asset in its zone, with the target security level, what it can act on and what a wrong action costs. It is for the operations manager who runs the floor and the OT security lead who answers for it.

What do I paste into Cell Register?

One asset per line, with the type and, where you have them, the vendor, what it does, the network it sits on, whether it is reached remotely, whether its controller adapts, who oversees it and what safety function guards it. Tabs, commas or pipes work, a header row is optional, and `Asset, type` alone works.

How many assets can I run for free?

Eight assets are free and no account is needed. Every zone, count and finding is arithmetic on the lines you paste, in your browser, and nothing leaves it until you choose to save.

How does it decide which zone an asset belongs in?

Each line is matched against a published dictionary of 49 machine classes in seven families, and the zone class comes with the IEC 62443-3-2 reasoning. The zone classes are cell, line, plant supervisory, site business and safety.

What is SL-T and how is it set?

SL-T is the IEC 62443 target security level. It is derived from the asset's class and raised where the asset is reached remotely.

What does it mean when a controller is adaptive?

The register records whether a controller is adaptive or fixed-program. Where a controller adapts, the asset carries the EU AI Act deployer duties alongside the others, and the register shows the adaptive count across the list.

Which regimes does it read against?

The IEC 62443 asset-owner duties and the system requirements by zone, the NIST SP 800-82 overlay, the EU AI Act deployer duties, the EU Machinery Regulation and ISO/IEC 27001. A first line such as `iec 62443: yes | as at: 2026-09-20 | support threshold: 2014` ticks the regime and pins the dates.

Does it rate my machines or my vendors?

No. Vendor names are kept as labels and the register never rates a vendor or a machine. It classifies your own list and states the obligation in our words, cited to its clause.

What do I get to take to the integrator?

The integrator and supplier rows are rendered as what to ask, never as your duty. Every asset carries the questions to put to the integrator before the next change, grouped by class on the RFI page and exportable on Solo.

What happens with an asset it does not recognise?

A line that matches nothing is marked unrecognised and never guessed. Its zone is left not placed and it is counted among the findings.

How many findings does it raise?

The register raises nine findings on the pasted list. The full register adds what each asset acts on, the vendor share, the obligation rows under IEC 62443, the AI Act and the Machinery Regulation, and the integrator questions per class.

What can I export?

On Solo the zone and conduit sheet, the integrator question list and the Machinery document checklist export. The register states each obligation in our words, cited to its clause, and never rules on a machine.

What this does, and what a spreadsheet, a consultant or an AI assistant does better

A spreadsheet is better for keeping the maintenance asset list as the operations team's own record, with the fields and history a CMMS export does not carry, and it needs no dictionary of machine classes. An OT security consultant or the integrator is better on the site's own network, its risk and the engineering behind a zone, and can advise on what to change. A general AI assistant is better for drafting the questions to the integrator or the safety narrative around a machine. What this does that they do not is place each pasted asset in a zone class with the IEC 62443-3-2 reasoning, derive a target security level raised for remote access, and set out the asset-owner duties and the AI Act deployer duties with the clause behind each; it never rates a machine or a vendor, and an asset it does not recognise is marked unrecognised rather than guessed.

Primary source: IEC 62443