Machinery Regulation 2027:
Is your PLC software ready?
From 14 January 2027, Regulation (EU) 2023/1230 replaces the Machinery Directive. For the first time it sets explicit requirements for the software and cybersecurity of machinery. For machine builders this means: if you change control software, you should be able to prove every change.
Software moves centre stage.
The key points of the new regulation for everyone who develops and maintains control software – in brief.
Regulation instead of directive
It applies directly in all EU member states, without national transposition. Machinery placed on the market from 14 January 2027 must comply with it.
Protection against corruption
Safety-related software and data must be protected against accidental and intentional corruption. The software needed for safe operation must be identifiable, and legitimate and illegitimate interventions must be evidenced.
Safe, reliable control systems
Control systems must, among other things, enable tracing logs of interventions and of versions of safety software uploaded after placing on the market – for a period of five years.
Digital changes count too
A substantial modification of machinery can also be made digitally – for example through software. Whoever makes it may take on manufacturer obligations. If you know your changes, you can assess them.
Documentation that lasts
Technical documentation must be kept available to the authorities for years. For software-controlled machinery, a traceable software state naturally belongs to it.
Tampering becomes an issue
Connections to other devices and remote access must not lead to hazardous situations. Unnoticed changes to control code are exactly the risk the regulation addresses.
Can you answer these questions in five minutes today?
At acceptance, in service or after an incident, exactly these questions get asked. With project copies and file names like _final_new, it gets hard.
- Which software state runs on which machine?
- What has changed since acceptance – and by whom?
- Which safety-related blocks were affected?
- Has the collective F-signature changed?
- Can the accepted state be restored exactly?
Complete evidence from engineering.
CodeShuttle makes the engineering side of your control software traceable – automatically, with every sync.
| What you want to prove | How CodeShuttle helps |
|---|---|
| Which software runs – clearly identified | Every state is a commit with a unique ID. Device details document order number, firmware and modules per device. |
| Who changed what, and when | Every sync is recorded with author, timestamp and affected files; the change itself is visible line by line. |
| Changes to safety software | F-blocks are versioned from TIA V21. The collective F-signature is shown before and after every run; a change is clearly highlighted. |
| Protection against unintended changes | Nothing is written without preview and confirmation. Conflicts stop the run; deletes and F-changes must be chosen explicitly. |
| Restore the accepted state | Any earlier state can be retrieved from the history and transferred back into TIA by a sync. |
| Keep evidence for the long term | The history lives as a Git repository on your own drive or server – for as long as you need it. |
Five steps to traceable PLC software.
Done in a few days for most teams – well before 14 January 2027.
Take stock
Which projects, which TIA versions, who works on them?
Secure the baseline
First sync with CodeShuttle – the first commit is your documented starting point.
Connect the team
Set up a shared repository on a network share or Git server.
Define the workflow
Every change through a sync, F-changes with signature check.
Use the evidence
Use history and diffs for acceptance, service and documentation.
When does the new Machinery Regulation apply?
Does the regulation require version control?
Does it affect existing machinery too?
Does CodeShuttle replace conformity assessment?
- Regulation (EU) 2023/1230 of the European Parliament and of the Council of 14 June 2023 on machinery, OJ L 165 of 29.6.2023, in particular Art. 54 (date of application) and Annex III, points 1.1.9 and 1.2.1: eur-lex.europa.eu/eli/reg/2023/1230/oj
- This page summarises requirements in simplified form and is not legal advice. Only the text of the regulation is authoritative. To assess your machinery, consult your specialist department, a notified body or legal counsel. As of October 2026.