Services
EU Machinery Regulation 2023/1230 for manufacturers and OEMs
From 20 January 2027 the Machinery Regulation applies without an optional parallel transition. Manufacturers need a defensible risk assessment, a clear conformity path, software and update governance, and documented decisions at the interface to the AI Act and CRA.
Check regulatory readinessOld vs new
Machinery Directive vs Machinery Regulation
Source: MRO (EU) 2023/1230 vs. Machinery Directive 2006/42/EC
| Machinery Directive 2006/42/EC (OLD) | Machinery Regulation 2023/1230 (NEW) |
|---|---|
| Software was not addressed with the same explicit structure | Software and digital functions are explicitly addressed as part of the machine |
| No equally explicit digital substantial-modification rule; safety-relevant changes and reasonably foreseeable misuse still had to be considered in the risk assessment | Article 3 point 16 explicitly defines substantial modification, including digital changes after placing on the market |
| AI in safety functions had no dedicated interface logic to the AI Act | The AI Act interface must be documented per machine and conformity path |
| Directive required national transposition | Regulation applies directly across EU member states |
Substantial modification
Article 3 point 16: when does a substantial modification exist?
Source: MRO 2023/1230 Article 3 point 16
A substantial modification exists where a physical or digital change after placing on the market or putting into service was not foreseen by the manufacturer and affects safety by creating a new hazard or increasing an existing risk, so that additional protective measures or a change to the safety-related control system become necessary.
- Was the change foreseen or planned by the manufacturer?
- Does it affect safety functions, operating limits, or safety-relevant use?
- Does it create a new hazard or increase an existing risk?
- Does the documented analysis show a need for added protective measures or changes to the safety control system?
Decision rule
Not every update to a safety function automatically triggers a new CE procedure. The result depends on a documented case-by-case decision tree and updated risk assessment.
OTA updates: document first, escalate only where needed
An OEM has 3,000 installed machines across several EU markets and improves an ML-based safety-monitoring function via OTA.
That update may constitute a substantial modification under Article 3 point 16 and can require reassessment depending on the documented analysis.
Before rollout, the version, safety impact, test evidence, and risk-assessment outcome should be traceable.
Applicability
Applies from 20 January 2027 with no optional parallel transition
Planning implication
Once the Regulation applies, the normal product path under the old Machinery Directive ends. There is no optional parallel transition route, so product and documentation planning should work backwards from the applicability date.
Roles
These roles should be assigned clearly per product
Manufacturer
Owns design, risk assessment, technical file, declaration of conformity, and CE marking.
Importer
Checks before EU market placement that conformity documents, marking, and manufacturer information are in place.
Distributor
May only make compliant products available and must escalate issues and cooperate with market-surveillance authorities.
Substantial modifier
A party making a substantial modification takes on manufacturer duties for the affected machine or affected part.
Annex I
Annex I Part A and Part B at a high level
Part A
Categories with a stronger third-party conformity-assessment implication and tighter procedural expectations.
Part B
Additional listed categories where the conformity path depends on product category and standards coverage.
Conformity assessment
Article 25: path depends on category, standards coverage, and product change
- Start by identifying the product category and economic-operator role.
- Then check whether harmonised standards or common specifications cover all relevant essential requirements.
- For substantial modifications, document again which conformity path applies to the modified machine or the affected part.
- The decision should be traceable in the technical file and risk assessment.
Cyber safety
Annex III: make software, updates, and remote-access risks visible
- Version and log software releases, changes, and approvals in a traceable way.
- Protect safety-relevant software and configuration data against corruption or tampering.
- Explicitly assess risks from remote access, networking, and update mechanisms.
- Check how corruption, unauthorised changes, or faulty updates can affect safety functions.
Interfaces
AI Act and CRA without blanket claims
AI Act Article 6(1)
Not automatically high-risk. Document whether the AI system is a safety component of an Annex I product and whether that product requires a third-party conformity assessment under the applicable harmonisation legislation. Record that classification per machine.
EU AI Act for machinery OEMs →Check CRA scope per product
Not every firmware build is automatically a CRA product. Scope depends on product boundaries, digital elements, interfaces, market placement, and the operator role.
CRA for embedded systems →What Solvetronix delivers
Regulatory readiness for machinery OEMs
- Analysis of substantial modifications for software updates under Article 3 point 16 MRO
- Conformity-path analysis for software-based or AI-enabled safety functions
- Risk-assessment update for remote access, updates, and digital failure modes
- Documentation structure for versioning, evidence, and change decisions
- Alignment of MRO, AI Act, and CRA on the same product boundary
FAQ
Frequently asked questions
Is there still a choice between the Directive and the Regulation after 20 January 2027?
No. There is no optional parallel transition for the normal product path. Technical and documentation work should be completed before that date.
Does every OTA update automatically trigger a new CE assessment?
No. A safety-relevant update may constitute a substantial modification, but the outcome depends on a documented case-by-case analysis under Article 3 point 16.
Is AI in a safety function automatically high-risk under the AI Act?
No blanket answer is reliable. The classification should follow Article 6(1) AI Act and the actual conformity path of the machine concerned.
Is every embedded firmware automatically in CRA scope?
No. CRA scope must be assessed per product and depends on the digital product boundary, interfaces, and market role.
Primary sources
Legal sources behind this page
The statements on this page are based on primary legal texts and should always be matched against your concrete machine type, operator role, and planned conformity path.
Background and guidance
Check regulatory readiness
We assess your risk assessment, OTA/software changes, and the interface to the AI Act and CRA through a documented decision path.
Check regulatory readiness