The Machinery Regulation intervention log. Ready to install.
An agent on the machine's gateway, or a small DIN-rail module next to the router: nothing to develop, no remote-service system to change. Ormatrace logs and signs every intervention and gives you the evidence for sections 1.1.9 and 1.2.1(f).
Regulation (EU) 2023/1230 · applies from 20 January 2027
Four moments that leave a footprint.
These are the cases the Machinery Regulation asks you to be able to demonstrate, and the ones that usually leave no trace.
Remote session
Who connected, from where and for how long. Everything that happens is attributed to the session.
PLC change
Program, parameters and mode: state before and after, safety relevance, authorisation.
Firmware update
Version and hash of the safety software, kept for five years as section 1.2.1(f) requires.
Signed report
Per machine and period, with signed roots for independent verification. Ready for the technical file.
From 20 January 2027 — every intervention on safety software must be logged and kept for five years.
The machine belongs to the customer. The responsibility stays with you.
After delivery, the machine lives in a plant you don't control. Technicians, integrators and updates all pass through it, and when something goes wrong the first question is always the same: who touched what? Ormatrace gives you the answer, signed.
Intervention log · 21 Oct
- Safety module firmwareSAFE 2.1.0 → 2.2.0 · safety-relevantsha256:11aa…e4 → 22bb…9c
- Machine behaviourvibration within normal range · 2.0 → 2.1 mm/s
Two sections of Annex III, one answer.
Protection against corruption. Intended or accidental interventions on safety-relevant software and hardware must be prevented or, where that is not possible, made evident.
Intervention log. Data generated in relation to an intervention, and the versions of safety software uploaded after placing on the market, must be logged and kept for five years.
Ormatrace provides the technical evidence for these two sections. Conformity of the machine remains with the manufacturer and its risk assessment.
Read the guide to both sections →Machines already sold do not become non-compliant: the new rules cover machines placed on the market from that date. But the first models delivered in January are already in production today.
Collect, chain, sign.
A lightweight agent on the machine's gateway, or a small Edge unit next to the service router. No commands to the machine: observation only.
Observe
Remote sessions, PLC and configuration changes, firmware updates, file integrity.
Chain
Each message carries the hash of the previous one: a gap or a change shows up.
Correlate
Physical behaviour before and after the intervention is compared automatically.
Sign
Every day the log root is signed and can be sent to the machine builder.
Prove
Report per machine and period, in PDF and JSON, to attach to the technical file.
Not just who touched the PLC. What happened next.
A log tells you a program changed. Ormatrace also watches the machine: vibration, temperatures, cycle times and currents in the hour before, compared with the minutes after the intervention.
- Harmless intervention: the machine behaves as before, and the evidence says so.
- Intervention with effects: the deviation is flagged and linked to the session and the user.
- No dedicated sensors needed: it uses data the machine already produces, or Box4AI sensors.
A deleted or altered message breaks the chain and raises an alert. Illustrative example.
Built for the people who build the machine.
OT security platforms cover the whole plant, for whoever runs it. Ormatrace covers the single machine, for whoever designed it and is accountable for it.
Technical file
Evidence for sections 1.1.9 and 1.2.1(f), under your brand towards the end customer.
For machine builders →Attributed interventions
Every remote session becomes a report: who, when, what changed, what effect it had.
Remote sessions →One more tool
Concrete technical evidence to bring into your machine-builder clients' risk assessment.
Become a partner →Already using ConnectBox OEM? Ormatrace is already on board.
Ormatrace is part of the Box4AI platform for machine builders. ConnectBox OEM connects machines in the field, discovers PLCs and HMIs and runs VPN remote service with separate access for builder, technician and customer. Ormatrace adds the signed log of what passes through it.
- One gateway: the Ormatrace agent comes ready on ConnectBox OEM and is switched on without extra hardware.
- Sessions already attributed: technicians' VPN certificates become the identity of the logged sessions.
- Vibration included: with VBox4AI sensors, the before/after comparison works even on machines without process data.
What Ormatrace does not do.
An evidence tool should be the first not to overclaim.
It does not certify the machine
It provides technical evidence. Conformity stays with the manufacturer and its risk assessment.
It does not control the machine
It observes and records. It never writes to PLCs or drives and never blocks traffic.
It does not watch the plant network
It works only on the machine and its service connection, never on the customer's IT network.
It does not replace remote service
It sits alongside the VPN or router you already use and makes what passes through it verifiable.
It deletes nothing
Intervention evidence is kept for five years. The log only accepts additions.
It does not profile people
Interventions are attributed to IDs; the link to a name stays with the manufacturer.
One machine, thirty days, a real report.
We start from your best-selling model: an assessment of both Annex III sections, installation on a real machine and a month of evidence collected in the field.
Analysis of the model against sections 1.1.9 and 1.2.1(f), with an action plan.
Log, correlation, five-year retention and reports.
Want to see Ormatrace on one of your machines?
A 20-minute demo: a remote session, a PLC change, how the machine behaved, and the signed report that comes out of it.