EU Data Act: give customers usable machine data.

Make the dataset understandable, the export usable and the customer's sharing decision practical. Orenda supports local collection, controlled access and data portability through open APIs and standard exports.

Discuss your customer's data request See machine-data collection

A chart is useful. The underlying records need to travel too.

Your customer may want to feed its own MES, investigate a stoppage with a maintenance firm or move historical records to another system. Define the data and access method before the request becomes a custom service project. With Orenda, customer data remains theirs and there are no data exit fees.

When a customer connects its own MES

Suppose a customer wants counts and machine states from a packaging machine in its existing MES. The source has a cumulative counter, while the receiving system expects the output for each interval. Document the counter's meaning and reset behavior before mapping the fields. State whether timestamps use UTC or local time and how gaps appear.

Use an agreed production period to compare the machine record with the imported result. Check a normal run, a restart and a missing interval. The handover should explain why totals agree or where records are absent. That gives the customer an interface it can maintain when staff, software or service providers change.

Separate machine-data access from switching a service

The connected-product rules address covered data generated through use of the product and related services. A request for machine readings does not necessarily mean the customer is ending a cloud contract. Establish which request you are handling, then apply the relevant data scope, access method and contractual process.

For covered data-processing services, the standard switching transition must finish without undue delay and within 30 calendar days after the notice period ends. Notice can be up to two months; defined extensions can apply. Agree the destination, transfer responsibilities and retrieval arrangements. From 12 January 2027, covered providers cannot impose switching charges, including necessary data-egress charges.

Make the delivered records understandable

Describe every field

Identify the machine, measurement, unit and time basis. Explain counter resets, sampling intervals and missing records so another system can interpret the values.

Provide a usable delivery method

Use the appropriate API or standard export for the agreed dataset. Include field definitions and retention information; check the output in the recipient's tool.

Respect the customer's sharing decision

Identify the recipient and needed resource. Keep historical data access separate from permissions to change equipment, and make removal of access part of the process.

Keep data ownership practical

Orenda Box collects configured machine data on site. MES and SCADA use that data in production and monitoring. Open APIs and standard exports let customers use their records in other systems without data exit fees. Connect controls access to selected private resources, so the customer can share access for the work that needs to be done.

Turn the customer's intended use into a defined list of records and metadata.
Document identifiers, units, timestamps, sampling, retention and the delivery method.
Load an export into the destination tool and reconcile a known operating period.
Record who approves sharing, who handles access requests and how permissions are removed.

Which Data Act date applies to your work?

12 September 2025

General application began, including the service-switching framework.

After 12 September 2026

Article 3(1) access-by-design duties apply to connected products and related services placed on the market after this date.

Two milestones in 2027

12 January 2027 ends switching charges for covered data-processing services. From 12 September 2027, unfair-term rules also cover contracts signed on or before 12 September 2025 that run indefinitely or at least until 11 January 2034.

Questions about customer data

Does the customer need direct access to the controller?

The useful route depends on the data and task. A machine-readable export or an approved application may meet the request without controller access. Identify the covered records and recipient, then choose an access method that supports the intended use.

Is every analysis treated like raw machine data?

The connected-product access rules cover readily available raw and preprocessed data and the metadata needed to interpret it. Highly enriched information inferred or derived through additional investment falls outside those rules. Keep raw measurements, preprocessing and analytical results distinct in the data inventory.

Prepare the data handover

Data Act dates and an export example A practical guide to machine records and service switching. Orenda Box Collect configured measurements and run applications locally. Access for a service partner Give the chosen partner permission for the needed resource.

What does your customer want to do with the data?

Bring the requested fields, a sample record and the destination system. We can define the collection, delivery and permission steps around that use.

Discuss machine-data delivery

Explore all Orenda solutions →