The Data Act Reaches Equipment You Haven't Bought Yet

The access-by-design duty applies only to connected products placed on the EU market after 12 September 2026, and it buys a plant less than the briefings suggest.

On 12 September 2026 the one obligation the EU legislature had held back in the Data Act came into force. Regulation (EU) 2023/2854 has applied since 12 September 2025, but its closing article defers the duty in Article 3(1) to connected products, and the services related to them, placed on the market after 12 September 2026. Anything placed on the market before that date never falls under it. The duty itself: connected products have to be designed and manufactured, and related services designed and provided, so that the data they generate, together with the metadata needed to interpret and use it, is accessible to the user by default, easily, securely, free of charge, in a structured, commonly used and machine-readable format, and, where relevant and technically feasible, directly.

For a processing plant that lands in the purchase order long before it lands in a compliance file. The next CIP skid, the next screw compressor that arrives with an OEM telemetry package, the next gearbox shipped with a vibration module and a portal login: if it goes onto the EU market after that date, the data it produces is meant to reach you without a negotiation and without an invoice. That shifts what you can reasonably demand at the quotation stage. It also delivers less than the briefings circulating this autumn imply, because several of the things engineers now expect from the Act are not in its text.

"Nothing changed until 12 September 2026."

The deferral covers Article 3(1) and nothing else. The rest of Chapter II has been live for over a year, and the Commission's own Data Act policy page puts the application date at 12 September 2025 without qualification. Two of those provisions reach a plant today.

Article 3(2) is a pre-contractual disclosure duty on whoever sells, rents or leases you a connected product. Before the contract is concluded you're entitled to the type, format and estimated volume of product data the thing can generate; whether it can generate data continuously and in real time; whether it stores data on-device or on a remote server, and for how long; and how you access, retrieve or erase that data, including the technical means, the terms of use, and the quality of service. Article 3(3) puts a longer list on the provider of a related service, and two items on it are worth reading before you sign anything: whether the provider expects to use the data itself and for which purposes, and whether trade secrets sit inside the data it will hold.

Article 4(1) is the request route for everything already running. Where you can't pull the data straight out of the product, the data holder has to make readily available data, plus the metadata needed to interpret it, accessible to you without undue delay, at the same quality it holds itself, free of charge, machine-readable, and where relevant and technically feasible continuously and in real time. A simple electronic request is the mechanism, where that's technically feasible.

So the compressor package you commissioned in March 2026 is already inside the regime. You don't need new equipment to exercise anything.

Identifying the counterparty is the awkward part in practice. The Regulation's data holder is whoever has the right or the obligation to use and make the data available, and on a plant that can be the OEM, the integrator who built the skid around the OEM's drive, or the service company whose platform the telemetry lands in (on a retrofitted skid, frequently all three in sequence). "Related service" is defined separately and narrowly: a digital service other than an electronic communications service, connected with the product at purchase, rent or lease in such a way that its absence would prevent the product performing one or more of its functions, or one subsequently connected by the manufacturer or a third party to add to, update or adapt those functions. A condition-monitoring portal that merely draws trends from data you already receive sits in a different place from one the compressor needs in order to run its own load-sharing logic. Work out which description fits before you draft a request, because it decides who has to answer it.

"We'll have to retrofit the installed base."

You won't. Article 50 ties the design duty to placement on the market, so a 2014 transfer-pump skid and a 2019 induction furnace stay outside it regardless of what telemetry they carry. The installed base sits under Article 4 instead, which asks the data holder to hand over what it can already obtain without disproportionate effort, not to rebuild a product.

If anyone tells you the Act was written for consumer gadgets, recital 14 lists agricultural and industrial machinery among its examples of connected products, next to vehicles, ships, aircraft, medical devices and home equipment. Prototypes are the category it carves out, and that one is worth knowing if you run a pilot line: a skid built as a prototype and never placed on the market is not a connected product for these purposes.

Two further limits matter more than the cut-off date, and both carry forward into new equipment.

Recital 20 draws the boundary around "readily available data". It excludes data generated by the use of a connected product where the design doesn't provide for that data being stored or transmitted outside the component in which it's generated, or outside the product as a whole, and it states that the Regulation imposes no obligation to store data on a product's central computing unit. Translated to a bearing housing: a sensor that integrates acceleration to an overall velocity value every ten minutes and throws the time waveform away owes you the velocity trend and nothing beneath it. The waveform never left the component, so it was never readily available, and no clause obliges the vendor to add memory so that it could be. Recital 20 does allow the manufacturer and the user to agree such an adaptation voluntarily, which makes it a procurement item, priced like one.

Then there's Article 7. Chapter II doesn't apply at all to data generated through connected products manufactured or designed, or related services provided, by a microenterprise or a small enterprise, unless that firm has a partner or linked enterprise above that size, or was subcontracted to do the design, the manufacture or the related service. The same exemption extends to an enterprise that has qualified as medium-sized for less than a year, and to any connected product for one year after a medium-sized enterprise places it on the market. Plenty of process equipment comes from houses that small. The agitator builder with eighteen people, the dosing-skid integrator, the panel shop that wrote your PLC code: their kit can be every bit as instrumented as something from Siemens or Emerson and still sit outside the obligation entirely.

"Now the OEM has to hand over its health index."

This is the expectation that will waste the most time, and the text leaves little room. Recital 15 places information inferred or derived from product data outside the scope of the Regulation where it is "the outcome of additional investments into assigning values or insights from the data", in particular by means of proprietary, complex algorithms, and it names sensor fusion across multiple sensors in the product as the example.

The remaining-useful-life estimate, the asset health score, the "stage two inner-race defect" classification, the anomaly flag the OEM portal raises at 03:40 on a Sunday: none of it is covered. Absent a contract term, it stays with the vendor.

What the Act does deliver is the measurement layer. Vibration in its engineering unit with the sampling rate that produced it, winding and bearing temperatures, motor current, valve travel and position feedback, flow, differential pressure, the time base, and the metadata that says what each tag means. That's the half worth having. A health index is one number produced by somebody else's thresholds against a population you have never seen, where an acceleration record is something you can re-window, re-filter and re-label on the day you discover that your own induced-draught fans fail differently from the fleet average. So for a team that intends to build models on its own plant's signals, the measurement layer is comfortably the more valuable of the two outcomes. A team that planned to buy a verdict and own it gets nothing here.

Who owns that data once it reaches site is a different question, and an earlier piece on OT data ownership works through it.

One clause runs in the opposite direction and deserves more attention than it gets. Article 4(13) lets a data holder use non-personal readily available data only on the basis of a contract with you, and bars it from deriving insights about your production methods in any manner that could undermine your commercial position in the markets you compete in. Article 4(14) stops it passing your non-personal product data to third parties beyond what that contract covers. Think about what actually rides inside a telemetry stream from a packaging line: batch timings, changeover durations, run rates against nameplate, the hours your plant does and doesn't operate. And all of it travels whether anyone intended it to. Reading your own service agreement against Article 4(13) is a better use of an afternoon than reading another summary of the deadline.

"The vendor will just say it's proprietary."

Trade secrets are protected under the Act. But Article 4 turns the protection into a procedure, with steps and a paper trail.

Under Article 4(6), trade secrets are preserved and disclosed only where the data holder and the user have first taken the measures needed to keep them confidential. The obligation that follows is specific. The data holder, or the trade secret holder where those are different parties, has to identify which data are protected as trade secrets, including in the relevant metadata, and has to agree proportionate technical and organisational measures with you: model contractual terms, confidentiality agreements, strict access protocols, technical standards, codes of conduct.

Only after that does withholding become available. Article 4(7) permits the data holder to withhold or suspend sharing where no agreement on those measures was reached, or where the user failed to implement them or undermined the confidentiality of the secrets. The decision has to be substantiated, given to you in writing without undue delay, and notified to the competent authority designated under Article 37. Article 4(8) adds a narrow case-by-case refusal for the data holder that can demonstrate, on objective elements, that it is highly likely to suffer serious economic damage from disclosure despite the measures you've put in place. That refusal goes to the authority as well.

A blanket "all machine data is proprietary" in a quotation letter is therefore a claim the Regulation doesn't support. What it does support is an identification exercise, and the moment to run that is at quotation, tag by tag, while you still hold commercial leverage. Asking which rows of a four-hundred-tag list the vendor regards as trade secrets has a cheap answer before award and an expensive one after commissioning.

A genuine carve-out sits beside this and attracts far less comment. Article 4(2) lets you and the data holder contractually restrict or prohibit access, use or further sharing where such processing could undermine security requirements of the connected product laid down in Union or national law, resulting in a serious adverse effect on the health, safety or security of people. On a furnace, a pressure system or a safety-instrumented function, that is a real argument rather than a dodge, and the data holder still has to notify the Article 37 authority when it refuses on that ground. Whether a specific tag genuinely falls inside it is an IEC 62443 and safety-case discussion, and it belongs with the people who wrote the safety case rather than with whoever is negotiating the data clause.

"Legal will handle it; send us the clause."

Article 3(2) reads like an instrument data sheet once you stop treating it as a clause. It asks for the type, format and estimated volume of data; whether the product can produce that data continuously and in real time; whether it stores on-device or remotely, and for how long; and the means of access, their terms of use, and their quality of service. None of those is a legal question. They're the questions you'd put to a vendor about a Coriolis meter, and the answers belong in the technical part of the bid evaluation.

The wording of Article 3(1) is where a weak answer hides. "Structured, commonly used and machine-readable" describes no particular format. A supplier can satisfy that phrase with a daily CSV export behind a web login, stay inside the letter of the obligation, and leave you nowhere near a usable integration. But the requirement that decides whether the data is worth receiving is the other one: the relevant metadata necessary to interpret and use it. That means units, engineering range, sample rate, tag semantics, and a time base with a stated source.

So what does that look like in a bid document? Five items, all of them engineering deliverables rather than contract language:

  1. The tag list, with units, engineering range and sample rate, delivered before award rather than at FAT. A tag list you can't see is a specification you can't evaluate.
  2. Which signals leave the component and which never do. Recital 20's boundary determines what you will ever be in a position to request, so ask explicitly whether raw waveforms, high-rate current signatures or internal controller states are externalised at all, and at what rate.
  3. The access mechanism and its quality of service: push or poll, which protocol, what rate, what retention on the vendor's side, and what becomes of your access when the related-service subscription lapses (usually it stops, which is why retention on your own historian is the line to specify).
  4. The trade-secret identification, tag by tag, under Article 4(6), signed before the order rather than discovered during commissioning.
  5. Whether derived values are in scope or out, and if they're on offer, at what price. Recital 15 puts them outside the Regulation, so they're a commercial line item and should be quoted as one.

Protocol choice stops being abstract at the first item. An OPC-UA information model carries the data type, the engineering unit and the tag's meaning in band, so the metadata travels with the value; a Modbus register map gives you a holding-register address and an integer, and the units live in a PDF that someone has to locate. Both are machine-readable. Only one is self-describing, a distinction worked through in an earlier comparison of plant protocols.

Where all of this stops helping is worth being precise about, because the Act governs exactly one boundary: the one between you and whoever sold you the equipment. It has nothing to say about the boundary inside the fence. A PLC that holds the data and a historian that never got the tag. Two plants in the same group running incompatible naming conventions with no agreement to share each other's figures. A SCADA trend archive sized for six months that rolls over in silence (nobody notices until someone asks for last year's startup curve). Article 3 has no opinion on any of that, and for most sites that's precisely where access to their own process data is lost.

The scale conditions bite too. A site whose critical assets are a 1990s induction furnace, a transfer-pump skid from a twelve-person builder, and a gearbox whose OEM has been absorbed twice since commissioning gets very little out of this regulation: the furnace predates the design duty by three decades, the skid builder probably sits inside the Article 7 exemption, and there is no data holder left to send an Article 4 request to. For that plant the route to the data is unchanged, and it runs through a gateway on the panel door, a tag list that someone has to write by hand, and a patient conversation with whatever protocol the controller will speak.

Notes

Article 50 turns on when a product is placed on the EU market, not on when you install it, so a unit manufactured and sold into distribution in mid-2026 can arrive on site well into 2027 still outside the design duty. Ask for the placing-on-market date in writing instead of inferring it from the delivery note. Sector-specific Union law can also narrow or widen what has to be accessible for a given class of equipment, and Member States designate their own competent authorities under Article 37, so what a refusal costs a supplier in practice still varies by country.

References

  1. Regulation (EU) 2023/2854 (Data Act), Official Journal text — Articles 3, 4, 7 and 50 with recitals 14, 15 and 20
  2. European Commission — Data Act policy page (application date 12 September 2025)

Reuse & license

This article is published by Zoniax OÜ under a Creative Commons Attribution 4.0 International (CC BY 4.0) license. You are free to share and adapt it for any purpose, including commercially, as long as you give appropriate credit to Zoniax and link back to the original article.

Disclaimer

These Field Notes are general technical information, published as-is for industry peers. They are not professional, engineering, safety, legal, or financial advice, and nothing here is a recommendation to buy, sell, or act. Figures are cited from public sources believed reliable but are not independently guaranteed - verify them against the primary sources and your own plant conditions before acting. Zoniax OÜ and the author accept no liability for decisions made from this content. Naming a standard, product, or vendor is not an endorsement.

Cite this article

Nõmm, A. (2026). The Data Act Reaches Equipment You Haven't Bought Yet. Zoniax. https://zoniax.com/blog/posts/data-act-connected-product-access-by-design