In application
Ecodesign Regulation: Framework for the Digital Product Passport in force
Requirements per product follow in delegated acts.
Manufacturing & Industry
We work with pharma, medtech and electronics manufacturers and other industrial sites. We connect IT and OT without touching the control layer, turn operational data into quality and maintenance insight, put service know-how in front of the technician and prepare the product data that new EU rules ask for.
For manufacturers with sites in Ireland, from multinationals’ Irish operations to indigenous Irish companies scaling up, that need one view across plants and systems.

1 January 2026
CBAM moves to its definitive phase
Importers of goods in scope leave transitional reporting behind and enter the definitive regime.
12 September 2026
Connected products must open up their data
Data generated by new connected products has to be available to their users by design.
11 December 2027
Cyber Resilience Act in full application
To carry the CE mark, products with digital elements need secure design and a process for handling vulnerabilities.
Product design is shaped by the Data Act, the Cyber Resilience Act, the Ecodesign Regulation and the battery passport. Access to data, security updates and product passports are now part of the product you deliver.
The business wants plant data in the cloud, while control systems have to remain safe and running. NIS2 covers several manufacturing sectors, medical devices and electronics among them, and IEC 62443 gives the terms for zones and conduits. In Ireland the National Cyber Security Bill is still at General Scheme stage, so S.I. No. 360 of 2018 applies for now.
SourceDirective (EU) 2022/2555
Seasoned technicians and process engineers know things that are in no manual. Getting that knowledge into a form people can search has become an operational priority.
CBAM and sustainability reporting ask for energy, emissions and material data per site and per product, captured once and reused. On Revenue’s published timeline, large corporates also issue EN 16931 e-invoices from 1 November 2028 (planned), which puts the ERP in scope.
SourceRegulation (EU) 2023/956
Each link between MES and ERP is built as a separate project.
A unified namespace over MQTT and OPC UA, with an information model based on ISA-95, lets machines, MES and ERP publish and subscribe rather than being connected pair by pair.
Quality data and maintenance data live apart.
One operational data platform combines process, quality and maintenance data with its context, so engineers can trust the analysis. A prediction is shown with its measured accuracy, or not shown.
Technicians spend too long hunting through manuals and service records.
A knowledge assistant across manuals, work instructions and earlier interventions that names the document and revision behind every answer.
Connected products have to satisfy the Cyber Resilience Act and the Data Act.
We build secure update pipelines, software bills of materials, vulnerability handling and documented APIs for data access into the product platform itself.
Compliance data for each product is spread over many suppliers.
Supplier data comes in over EDI and APIs and lands in a single product data model, which can then feed Digital Product Passports, battery passports and CBAM reports.
Orders, delivery dockets and certificates are still typed in by hand.
Document intelligence reads and checks trade documents and certificates of conformity; staff confirm the exceptions before anything is posted to the ERP.
The ISA-95 levels are left as they are. A unified namespace publishes plant data above the zone boundary, where analytics, knowledge and compliance services pick it up.
Plant data passes the zone boundary a single time, via the namespace, and every service above it reuses it.
Five ISA-95 levels are stacked from top to bottom. Level 4 is business planning and logistics in the ERP, SAP S/4HANA or Odoo. Level 3 is manufacturing operations: MES, quality and maintenance. Level 2 is supervisory control through SCADA and HMI. Level 1 is control by PLCs and drives. Level 0 is the process itself: sensors, machines and lines.
Between level 4 and the levels underneath runs a zone boundary designed to IEC 62443.
Levels 1 to 4 send their data to a unified namespace over MQTT and OPC UA. From there it flows into an operational data platform that serves quality and maintenance analytics, a knowledge assistant for service and engineering staff, and product compliance data such as the Digital Product Passport.
Analytics and assistants only read from the namespace. Anything that would change production passes through the MES and needs an operator’s approval.
Networks are segmented along IEC 62443, with defined conduits between the control and enterprise sides.
Each model reports how accurate and how uncertain it is. If the data cannot support a prediction, we tell you.
ERP, passports and reports all draw on the same product and material data, not on three separate spreadsheets.
Rules on products, data and reporting follow one another quickly. Delegated acts under the Ecodesign Regulation will set dates for each product group.
In application
Requirements per product follow in delegated acts.
In application
Machinery, electronics, medical devices and vehicles are among the sectors covered. Ireland’s Bill had not been enacted by autumn 2026.
In application
Users get rights to the data their connected products generate.
In application
In application
Large companies that were in the second wave now report from financial year 2027.
In application
Vulnerabilities that are actively exploited, and severe incidents, have to be reported.
In application
Position at 2 October 2026
Upcoming
With requirements for safety functions that depend on software and connectivity.
Upcoming
For industrial batteries, electric-vehicle batteries and batteries for light means of transport in scope.
Upcoming
The legal texts that shape most product, plant and data programmes, and what each one changes for your engineers.
Use this overview to prepare planning discussions; it is not legal advice, and duties for a given product depend on delegated acts and harmonised standards. Dates checked on 2 October 2026.
A product with digital elements sold in the EU has to be secure by design, receive security updates throughout its support period and come with a process for handling vulnerabilities. The reporting duties start on 11 September 2026, the bulk of the obligations on 11 December 2027.
Secure development, software bills of materials and update pipelines become features of the product. We build them into your platform and your release process.
SourceRegulation (EU) 2024/2847, EUR-Lex (opens external site)
People who use connected products and related services may access and share the data those products produce. For connected products placed on the market from 12 September 2026, that data has to be accessible by design.
A product platform needs documented interfaces for data access and contract terms for sharing data. We design both.
SourceRegulation (EU) 2023/2854, EUR-Lex (opens external site)
The Ecodesign for Sustainable Products Regulation is the framework for product requirements and for the Digital Product Passport. The actual duties come product group by product group, through delegated acts.
If your product data model already holds materials, origin and repair details, each new delegated act becomes a mapping exercise and not a new system.
SourceRegulation (EU) 2024/1781, EUR-Lex (opens external site)
From 20 January 2027 it takes over from the Machinery Directive. Its requirements extend to safety functions that run on software, to connected machines and to protecting safety-relevant software from corruption. Where AI is part of such a product, Irish law lists the Health and Safety Authority among the sector market surveillance authorities (S.I. No. 366 of 2025, as amended by S.I. No. 405 of 2026).
Software that affects safety functions needs traceable requirements and change control. We keep it clearly apart from analytics and assistance.
SourceRegulation (EU) 2023/1230, EUR-Lex (opens external site)
The sectors in scope include makers of medical devices, computers and electronics, electrical equipment, machinery and vehicles, with duties on risk management, incident reporting and supply-chain security. As of autumn 2026 Ireland has not enacted its NIS2 law; the National Cyber Security Centre has published draft guidance on risk-management measures.
OT security, segmentation and incident handling become topics for the board. Our IT/OT integration is designed with them already in place.
SourceDirective (EU) 2022/2555, EUR-Lex (opens external site)
Since 1 January 2026 the Carbon Border Adjustment Mechanism has been in its definitive period for imports of goods in scope. The 2026 Omnibus limited CSRD sustainability reporting to the largest companies and pushed back their first reporting years.
Capture emissions, energy and material data once, where it originates, with lineage an auditor can trace.
SourceRegulation (EU) 2023/956, EUR-Lex (opens external site)
A technician asks a question and gets the matching manual section, work instruction and earlier fixes, each with its source.
Certificates of conformity and material declarations are read, compared with the purchase order and filed with the batch record.
Customer orders and delivery dockets are read and checked before posting; staff approve each exception.
The legacy MES of an electronics manufacturer is wrapped in documented APIs and swapped out function by function while the lines keep running.
Customers and distributors find the right part and check stock; anything that needs technical judgement goes to the service team.
SAP S/4HANA for production and supply chain across the group, linked to MES and plant data through the namespace, with VAT modernisation e-invoicing in scope for Irish operations.
Odoo manufacturing for mid-sized plants and owner-managed businesses, often as the second tier under SAP at group level.
Sales agreements, distributor networks and field service, tied to the installed base and its service history.
The partner levels shown are FromNine’s own. Product names belong to their owners as trademarks.
Ireland
Many manufacturing sites in Ireland belong to international groups, with an MES on site and an ERP instance run by a group function abroad; others are indigenous Irish companies growing from a single plant. EU product rules such as the Cyber Resilience Act, the Data Act and the Ecodesign Regulation apply to each of them in the same way, while NIS2 still waits for Ireland’s National Cyber Security Bill.
Revenue’s VAT modernisation adds a further reason to look at the ERP: on its published timeline, large corporates issue EN 16931 e-invoices for domestic B2B from 1 November 2028 and every business must be able to receive them (planned).
We design one information model and integration pattern that each site can take up at its own pace, with service content its technicians can use on the line.
Not as a rule. Analytics and assistants read plant data via the namespace. A change to production goes through the MES or your control engineers, with an operator’s approval and under change control, which a GxP site needs anyway.
In some cases. It comes down to the failure modes, the sensors fitted and how much history exists. We test first, show the measured accuracy and uncertainty, and suggest condition-based rules wherever a model would not hold up.
For plant data, OPC UA and MQTT; for the information model, ISA-95; for zones and conduits, IEC 62443; and EDI or APIs to connect suppliers and customers.
We build the product platform to support it: secure development, software bills of materials, a way to take in vulnerability reports, and update pipelines. The conformity assessment and the legal reading of the Act remain with you and, where one is required, your notified body.
Yes, two-tier ERP is a familiar pattern, for example when a multinational’s Irish operation and its group run different systems. We agree which master data and transactions belong where and connect the two so group reporting, and the e-invoicing planned under VAT modernisation, stay consistent.
Linking plant data, getting connected products ready for the CRA or giving technicians better access to know-how? Begin with one line, one product or one site.