A migration map from 2006/42/EC to 2023/1230.
Focus: route changes, documentation modernization, and software/control-system evidence.
Structured answer sets in this page tree.
Cited legal and guidance references.
Directive 2006/42/EC harmonized machinery safety through national transposition. Regulation (EU) 2023/1230 replaces it with directly applicable rules and adapts the framework to new risks, including software and connected machinery. The practical impact is not just legal references - it's route selection (Annex I + Article 25), evidence expectations (Annex IV), and safety-related software integrity and logging controls.
A directive required national transposition. A regulation is directly applicable across Member States. That reduces legal divergence but raises the bar for one consistent EU-wide evidence model.
The migration should therefore be designed around one controlled technical-file and declaration architecture, not country-by-country rewrites.
Research Copilot can take Machinery Regulation vs Machinery Directive What changes operationally from how this topic compares with adjacent regulations or standards to a reusable workflow inside Sorena. Teams working on Machinery Regulation vs Machinery Directive can keep owners, evidence, and next steps aligned without copying this guide into separate documents.
Start from Machinery Regulation vs Machinery Directive What changes operationally and answer scope, timing, and interpretation questions with cited outputs.
Review your current process, evidence gaps, and next steps for Machinery Regulation vs Machinery Directive What changes operationally.
The Regulation adapts definitions to reflect digital machinery and software-driven safety functions.
Operational implication: software can be a safety component; machinery can be in scope even when missing only the upload of software intended for the specific application.
The Regulation's Annex I categories and Article 25 procedures create clear route logic: Part A requires third-party routes; Part B has conditional Module A; not listed defaults to Module A.
Operational implication: re-run Annex I classification for each product family - don't assume the directive-era route still holds.
Annex IV makes the technical documentation minimum elements explicit and includes software/control-system evidence items in certain contexts.
Operational implication: build a stable index and evidence mapping (EHSR -> protective measures -> tests).
A successful migration is product-family based: scope, route, safety case, evidence, and declarations move together.
Operational output: a transition tracker with "done looks like" criteria.