For teams running the machines, not building them

You did not change the firmware. You will still be asked to explain what did.

A safety controller update, a re-zoned scanner, a PLC project patch — often pushed by an integrator or a remote service call you were not in the room for. When something goes wrong, the plant is where the questions land first.

Run the offline kit See pricing

Night-shift operator at a palletising cell after remote service has left, with only a coiled cable on the bench.

⏱

The clocks that apply to youMachinery Reg. Annex III 1.1.9 requires the machine to identify its safety-relevant software and record evidence of intervention — applying 20 Jan 2027. If your integrator or OEM can’t produce that evidence, you are the one standing in front of the inspector.

Why this matters for plant operators

What the paperwork stops telling you

You inherit somebody else’s change

Interventions on safety-bearing items happen without your sign-off, and nothing re-runs the verification that used to cover them.

"It still works" is not evidence

A machine running fine today says nothing about whether its safety functions still have valid evidence behind them.

You need your own record, independent of the OEM

The offline enrolment kit runs on your machine, into your own ledger — you do not have to trust anyone else’s bookkeeping.

What this checks

Proof, not a pitch

Inspector and plant operator reviewing a local paper ledger at a yellow safety fence.

The staleness join

A sign-off from February, a firmware change in March, and the named safety functions whose evidence stopped applying — dated, not argued.

Offline enrolment kit

Your ledger, your disk. No account, no upload, and a guard that proves nothing left your network.

You did not change the firmware. You will still be asked to explain what did.

Verification stays free, forever, at every tier. Start there.

Run the offline kit See pricing