Data Act and CRA preparation for machine manufacturers.

Your EU customer needs to use its data, approve maintenance access and understand how the machine will be supported. Bring Data Act and CRA preparation into the way you design, sell and service connected equipment.

Discuss your machine architecture See how Connect works

Answer the questions behind the customer's specification

A tender may ask for a data interface, remote maintenance and a long support period. Engineering, sales and service need a consistent answer. Define what the customer receives, which resources a technician can reach and how an installed machine stays connected to its release and support records.

A customer handover that can be demonstrated

Consider a packaging-machine customer that wants production data in its own MES and has appointed a local maintenance company. The production team needs counts and machine states. The maintenance company needs a diagnostic application. These are separate tasks, so establish separate access decisions and show each team how to complete its work.

During acceptance, load an agreed export into the customer's tool. Check machine identifiers, time and units against a known production period. Then open the diagnostic application as the approved partner, try a resource outside its permission and test a new connection after access is removed. Record the configuration and results with the delivery documents.

Keep the commercial promise connected to engineering

Sales should be able to answer what the customer can export, how long records are retained and how a service partner obtains permission. Service should know who receives a vulnerability report and where to find the installed software version. Purchasing should know when component support ends. These answers should describe the same product configuration.

The Data Act covers data-access and sharing duties and service-switching obligations. The CRA covers product cybersecurity through its lifecycle. An export demonstrates part of the data workflow; a tested permission demonstrates part of the access design. Keep both results in the manufacturer's wider product records, alongside the risk assessment, release evidence and support decisions.

Three parts of the customer handover

Data the customer can use

Specify the measurements, timestamps, units and retention. Show how the customer can obtain the records and authorize a chosen third party to use them.

A named person responsible for service access

Give engineers the applications or devices their task requires. Establish who approves partner access, who removes it and how the team identifies the installed version.

Support that matches the machine

Connect product lifetime, software maintenance and replacement planning. State the support end and update method in the customer information.

Use shared controls across the machine's life

Orenda Connect provides encrypted access to selected resources over Diode's peer-to-peer network. It needs no dedicated hardware. Add Orenda Box for local data collection and applications, with a TPM root of trust, signed update releases and 10-year hardware availability. App Market applications use shared identity and administrator-approved permissions. Customers retain ownership of their data, supported by open APIs, standard exports and no data exit fees.

  1. Define the delivered hardware, applications, data interfaces and remote functions.
  2. Assign responsibility for data requests, customer permissions, software releases and support.
  3. Verify a customer export and the allowed and denied operations in the service connection.
  4. Deliver the field definitions, access instructions, tested configuration and support contacts with the machine.

Useful answers for each team

Engineering

Interfaces, permissions and tested configurations tied to the delivered release.

Service

An approved connection, an identifiable installation and a defined update route.

Sales and customers

A working data handover and clear answers about access, support and data portability.

Questions from machine builders

How do Data Act and CRA work fit together?

The same machine can need both. Data Act preparation establishes access to covered data and how it can be shared or transferred. CRA preparation addresses product cybersecurity, updates, vulnerability handling and support. Coordinate the teams and records, while keeping each obligation clear.

Does the machine need an Orenda Box?

Connect does not require dedicated hardware. Orenda Box is an option when you need local machine-data collection and a managed environment for applications. The choice follows the functions the machine and customer actually need.

Go deeper into the requirement

EU Data Act Define usable data delivery and provider switching. Cyber Resilience Act Connect private service access to the product support plan. Machine manufacturers Build remote support into delivery and after-sales service.

Bring the customer's requirements and your machine architecture.

We can work through the data interface, service permissions and local applications together, then define what the customer will receive.

Discuss your EU machine project
Explore all Orenda solutions →
EU Data Act 2027: machine data and cloud switchingUnderstand the Data Act 2027 switching milestone, machine-data access and practical export tests. Build a clear data handover for connected industrial systems.Cyber Resilience Act 2027: a practical plan for machine buildersPrepare connected machines for CRA 2027. Organize secure access, product records, updates, support and the reporting duties already in force.