Who owns machine and equipment data: the manufacturer or the customer?

Short answer: the contract decides#

Machine and equipment data is usually controlled by contract, not by who built the machine or who paid for it. US law generally does not treat raw machine data as property in the way it treats the machine itself; control comes from agreements, trade secret protection and practical access to the data stream.

The answer for any one machine therefore lives in its paperwork: the purchase or lease agreement, the embedded software license, any remote monitoring or connectivity subscription, and the service contract. When those documents are silent, both sides may have arguments, and neither has a clean basis to license the data to a third party.

Rules outside the US can differ. The EU Data Act, for example, addresses access to and sharing of data from connected products, so companies that sell equipment into the EU or run plants there should ask counsel whether and how it may apply.

Four clauses that decide control#

Four clause types decide who controls equipment data, and each can be drafted to favor the OEM or the customer. The table compares common versions and what each means for licensing.

Most real contracts mix these versions, and the definitions matter as much as the operative clauses. Check how each agreement defines machine data, usage data, customer data and aggregated data, because the same telemetry can fall into different categories under different agreements.

What an OEM can usually consider licensing#

An OEM can usually consider licensing the data its contracts clearly let it use beyond servicing each customer: fleet-level telemetry, de-identified fault and alarm histories, field service reports written by its own technicians, and warranty claim records. These show how equipment behaves across many sites, which matters to AI developers building diagnostic and maintenance models.

The limits come from the customer side. Telemetry can reveal a customer's production volumes, shift patterns and process settings, which customers may regard as confidential. Contracts signed before connectivity was added may say nothing about data at all, and terms introduced later through a software update or portal click-through may be open to challenge.

What a plant can usually consider licensing#

A plant, as the equipment's customer, can usually consider licensing records of how it ran and maintained the equipment: CMMS work orders, downtime logs, operator shift notes, changeover records and production data collected through its own systems. These are the plant's own operational records, even when they describe a machine someone else built.

The limits come from the OEM side. The embedded software license may restrict extracting data from the controller, reverse engineering protocols or using OEM diagnostic codes outside the service relationship. OEM manuals and service bulletins pasted into work orders are the OEM's content and generally stay out.

Data that sits in between#

Some equipment data belongs cleanly to neither side and needs explicit terms before anyone licenses it. These categories cause most disputes.

Leaving these categories undecided is the most common drafting gap. A clause that states who may use recipes and jointly developed models, and whether either side may license them in de-identified form, settles most of the uncertainty before it turns into a dispute.

• 1Process parameters and recipes the customer developed on OEM equipment, often the customer's trade secret but stored in the OEM's system.
• 2Alarm and fault codes, defined by the OEM but triggered by the customer's operation.
• 3Condition monitoring models the OEM trained on one customer's data.
• 4Root-cause reports written jointly after a major failure.
• 5Data from leased or financed equipment, where the lessor may hold rights as well.

Illustrative: a packaging equipment maker and a food plant#

Illustrative: a fictional maker of case packers and palletizers added remote monitoring to its machines several product generations ago and now holds fault histories from equipment at many customer sites. One of its customers, a fictional snack food plant, keeps detailed CMMS work orders and downtime logs for the same machines.

The OEM's counsel finds that newer contracts allow use of de-identified data for product improvement but say nothing about third-party licensing, while older contracts predate monitoring entirely. The OEM limits any licensing review to fault histories under the newer contracts, asks counsel whether product improvement covers licensing at all, and drafts a clear data clause for future sales.

The plant's counsel finds its CMMS records are its own, but its recipes and line speeds sit in the OEM's monitoring platform under the OEM's terms. The plant considers licensing work orders and downtime logs with OEM manual excerpts removed, and leaves recipe data out.

Checklist before either side licenses equipment data#

A short document review answers most equipment data questions before anyone exports a file. Work through it per equipment family, since terms often differ by product line and contract vintage.

• 1Collect every agreement for the equipment: sale or lease, software license, connectivity, service and warranty.
• 2Find the definitions of machine data, customer data and aggregated data.
• 3Map who has raw access, who has dashboards only and where the data is stored.
• 4Separate process parameters and recipes, and decide them explicitly.
• 5Check for consent requirements, and whether they survive termination.
• 6Write down the basis for each record family you plan to include.

How SourceX handles equipment data rights#

SourceX handles equipment data rights in the Rights step of the SourceX five-step transaction, before any preparation starts. The supplier, whether OEM or plant, describes its record families and the agreements behind them, and counsel confirms which families have a clear basis.

In the SourceX Enterprise Data Value Framework, rights are a value driver in their own right: clear rights raise value, and uncertain rights can keep an otherwise strong dataset out of scope. Families that proceed are documented in a SourceX Evidence Packet covering provenance, licensing rights, permitted use, the privacy record and release authorization.