Safety laser scanner and light curtain
Detects a person entering a hazard zone and tells the safety controller to stop the machine; a safety function, not a sensor.
How the register reads it
| Also called | light curtain, safety laser scanner, area scanner |
|---|---|
| Family | Inspection and vision |
| What a wrong action costs | person. A person not detected, which is the case the machine relies on it for. |
| Zone class and SL-T | safety SL-T 3 by default. Part of the safety zone with the controller it reports to. Never above 3; the paste may state its own zone name and SL-T. |
| Networked by default | No. Wired to the safety controller; networked only where the paste says so. |
| Remote access by default | No. Not by default. |
| Behaviour by default | fixed. Fixed fields. |
| Machinery Regulation | A machine or safety component: the declaration, the technical documentation and the instructions are demanded at purchase and held; a substantial modification makes the owner its manufacturer. |
| Safety references |
|
What each regime attaches, and who it binds
42 clauses across 4 regimes, on the class defaultsShown on a register for the regimes you tick; with none ticked, the IEC 62443 asset-owner rows are the default. The CRA row is informational on every connected asset. Requirement text drawn from a human-verified compliance corpus under licence: the corpus statement of each clause, not the instrument verbatim.
IEC 62443
Binds Part 2-1 binds the asset owner; Part 3-2 is the owner's zoning and risk assessment; Part 3-3 is what the owner specifies for the system. Part 2-4 binds the service provider and Parts 4-1 and 4-2 the product supplier, so those rows are rendered as what to ask. Source framework: IEC 62443.
| Asset owner duty | On every asset (Part 2-1) IEC 62443 2-1 AC · 2-1 BCP · 2-1 CSMS · 2-1 IR · 2-1 MOC · 2-1 NSEG · 2-1 PHY · 2-1 PM · 2-1 RA · 2-1 TRN Whatever the zone, these ten programme duties are the owner's for every asset in the system under consideration. |
|---|---|
| Asset owner duty | System requirements to specify for the safety zone (Part 3-3) IEC 62443 3-3 SR 1.2 · 3-3 SR 2.8 · 3-3 SR 3.1 · 3-3 SR 3.4 · 3-3 SR 5.1 · 3-3 SR 5.2 The safety zone accepts no command from the process side: device authentication, auditable events, communication and program integrity, and a boundary that only carries status out. |
| Ask the integrator | Part 2-4 binds the service provider, not the owner IEC 62443 2-4 SP-01 · 2-4 SP-02 · 2-4 SP-03 · 2-4 SP-04 · 2-4 SP-05 · 2-4 SP-06 The owner owes none of these rows; the owner asks the integrator and the maintenance provider for the evidence of each before commissioning and at every substantial change. |
| Ask the supplier | Part 4-1 binds the supplier, not the owner IEC 62443 4-1 DM · 4-1 SG · 4-1 SUM The owner asks the maker of the controller or the machine for the hardening guide, the vulnerability handling process and the signed update channel. |
NIST SP 800-82 Rev 3
Binds guidance addressed to the operator of the OT environment: it binds nobody in law and is what most OT security programmes are assessed against. Source framework: NIST SP 800-82 Rev 3.
| Asset owner duty | The OT overlay on every asset SP 800-82 GOV-3 · HOST-4 · HOST-6 · IR-1 · MON-2 SP 800-82 is guidance for the operator of the OT environment: an inventory that holds firmware and location, safety and security run together, change and patch management, and an incident plan with OT scenarios. |
|---|---|
| Asset owner duty | Safety system isolation SP 800-82 ARCH-4 The safety instrumented system is separated from the control system and every other network. |
The EU Machinery Regulation
Binds the manufacturer of the machine, and whoever substantially modifies it; the owner's row is what to demand at purchase and hold, and what it becomes liable for on a substantial modification. Source framework: the EU Machinery Regulation.
| Asset owner duty | What to demand at purchase and hold (the Regulation binds the manufacturer) Machinery Reg Art. 10 · Art. 20 · Art. 21, 22 · Art. 51, 52, 53, 54 The declaration of conformity, the technical documentation and the instructions are the manufacturer's to draw up. The owner's row is to demand them at purchase, to hold the declaration and the instructions for the life of the machine, and to know that the Regulation applies to machines placed on the market from its application date, with the Directive before it. |
|---|---|
| Asset owner duty | At every substantial modification Machinery Reg Art. 17, 18, 19 An owner that substantially modifies a machine becomes its manufacturer for the modification and takes on the Article 10 duties: the risk assessment, the technical file and the declaration are then the owner's to produce. |
| Ask the supplier | What the manufacturer shows (Articles 8 and 9 bind the manufacturer) Machinery Reg Art. 8, 9 · Art. 25 The essential health and safety requirements, including protection against corruption of the control system and the provisions for autonomous behaviour, and the conformity assessment route the machine went through. |
ISO/IEC 27001:2022
Binds the organisation that holds the certificate, through the Annex A controls it declared applicable. Source framework: ISO/IEC 27001:2022.
| Asset owner duty | Supplier and change controls on every asset ISO 27001 5.19 · 5.20 · 5.22 · 8.32 The integrator and the maintenance provider are suppliers; the change to a machine is a change. |
|---|
The EU AI Act
A fixed-program machine is not an AI system: it does not infer from input how to generate its output and it does not learn or re-plan at runtime. No AI Act row attaches to it; the Machinery Regulation and IEC 62443 do.
Ask the integrator
- What the protective field was set to and who validated the stop distance
- Whether the field configuration can be changed over the network
- Where the configuration is recorded
Findings this class can raise
- End of support or unpatched
The paste says the asset is out of support, unpatched or at end of life, or its commissioning year is older than the support threshold in the preamble. The asset owner's row is patch management with a recorded risk acceptance for what cannot be patched; the supplier's row is what to ask about updates and the support period. - Vendor share at or above a third
One vendor behind a third or more of the assets, or behind every asset in a zone class. Concentration is often the right engineering choice; the regimes ask that the dependence be recorded and the supplier relationship managed, not avoided. The register names the share and never rates the vendor. - Machinery declaration or technical file not held
A machine bought or modified after the preamble's threshold date for which the owner records no declaration of conformity or technical file. The declaration is the manufacturer's to draw up and the owner's to hold; a substantial modification makes the modifier the manufacturer, and the file is then the owner's to produce. - Safety zone shares a conduit with a business asset
A safety-function asset listed on the same network name as an asset in the site business zone. The safety conduit exists so that nothing on the process or office side can command a safety controller; a shared network name says the register cannot show that separation.
Do this for every asset on your floor
Paste the list and get this classification for every asset at once, with the zone and SL-T, the behaviour, the connectivity, the findings and the obligation rows per regime. Eight assets free, no account.
Build my cell register