Machine data ownership when the machine is on lease
Ask who owns the data coming off a leased press and you will get three confident answers from three people in the same company. The lawyer says the contract decides it, the engineer says whoever can reach the port, and the supplier says the data is needed for support. European law now takes a position on this, and the position is narrower and more useful than either side usually expects.
Industrial data rarely belongs to anybody in the way a machine does. There is no ownership in the property sense of a temperature series, and attempts to write one into a contract tend to produce clauses that describe an intent without creating a right. What exists instead is a set of practical questions with contractual and now statutory answers: who can read the data, who can stop somebody else reading it, who may pass it to a third party, and what happens to all of that when the lease ends.
Where the data actually sits
On a financed or leased installation the physical answer is usually unflattering. Telemetry leaves the controller over the supplier's own channel, lands in the supplier's cloud, and is presented back to the lessee through a portal with a login. The lessee sees dashboards. The supplier sees the series. Nobody at the lessee has a copy, which means that when the relationship ends the operating history of a machine the company has been running for years leaves with the vendor.
That arrangement is not usually the result of a negotiation. It is the default configuration of the product, agreed implicitly when the connectivity option was accepted during commissioning, and it survives because nobody has a reason to revisit it until there is a dispute or a tender.
What the Data Act changed
Regulation (EU) 2023/2854, the Data Act, addresses exactly this shape of relationship. Its second chapter is about connected products and related services, and it gives the user of such a product a right of access to the data the product generates, together with a right to have that data shared with a third party of the user's choosing. The user in that definition is the party that owns, rents or leases the product, which covers the lessee of an industrial machine directly.
Two features of that drafting matter more than the headline. First, the right attaches to the user rather than to the owner, so a finance lease does not park it with the funder. Second, the right to nominate a third party is the one with commercial consequences: it is what allows an independent service company, or a competing supplier bidding for the next contract, to be handed the data needed to make a credible offer. A right of access that stopped at the user's own screen would change very little. A right to redirect it changes who can compete for maintenance.
| Question | Where the answer lives |
|---|---|
| Who may read the series at all | Chapter II of the Data Act, plus the access clauses of the lease |
| Who may hand it to a third party | The user's sharing right, exercised against the data holder |
| What format it must arrive in | The regulation's requirements on the data holder, not the supplier's portal design |
| What survives the end of the lease | Contract. Unless it says otherwise, assume nothing does |
The clause that is usually missing
Statutory rights do not remove the need to write things down, and the gap in most industrial leases is not a missing ownership clause but a missing exit clause. A lease that says nothing about termination leaves the lessee asking for its own operating history as a favour, at the moment it has least leverage. The clause worth adding is dull: on expiry or termination, the data holder provides the generated data in an agreed machine-readable form, within an agreed period, for the whole term and not for a rolling window.
The rolling window deserves its own attention. Supplier platforms frequently retain high-resolution data for a limited period and aggregates thereafter, which is a reasonable engineering decision and a quiet amputation of exactly the record needed to argue about a warranty claim or to train anything. Retention periods are a specification item. They are almost never in the specification.
What to do before the next order
The useful work here is unglamorous and happens before signature. Establish which party the regulation treats as user for each connected installation on site, because on mixed fleets with multiple funders the answer varies by asset. Ask each supplier, in writing, what data its platform holds, at what resolution, for how long, and in what form it can be exported. Put the answer in the contract rather than in the email thread. Then test the export once, early, while the relationship is good: a right that has never been exercised is a right whose practical shape nobody knows.
None of this requires taking a position on the philosophical question of data ownership, which is fortunate, because the question does not have a settled answer and the machines are running now. It requires knowing which document decides each practical question, and reading that document before the invoice is approved rather than after the relationship ends.