Manufacturing
Who owns machine data from shop-floor equipment?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Who owns machine data from shop-floor equipment is usually decided by contracts, not by who owns the machine. Purchase terms, software licenses and connectivity agreements set who may access, use and share sensor readings. Records your people create, such as maintenance logs and quality decisions, usually start as yours. Check OEM clauses before licensing anything a machine generates.
Key takeaways
- Owning a machine does not automatically mean controlling every data stream it produces.
- Maintenance logs and quality decisions written by your staff usually start as company records.
- Sensor data sent to an OEM cloud often comes with license limits on export and reuse.
- Machine programs and process data for customer parts may be restricted by customer contracts.
- Licensing process data only under confidentiality terms can help preserve its trade secret status.
Who owns machine data from shop-floor equipment?#
Machine data from shop-floor equipment is rarely owned in a simple property sense; control usually comes from contracts. In the US, raw readings such as temperatures, cycle counts and spindle loads are facts, and copyright generally does not protect facts. What decides who can access, use and license them is the paperwork around the machine.
That paperwork includes the purchase or lease agreement, the software license for the controller and HMI, any remote monitoring or connectivity subscription, and service contracts. A plant that bought a machine outright may still have agreed that the OEM controls data on its platform. A plant that reads signals over its own network has broad practical control, but it may still be bound by a software license that limits extraction.
Rights by data type#
Rights differ by data type, so scope machine-related records one stream at a time. The table gives a general starting point; your contracts decide the actual answer.
Where one stream depends on another, the narrower right tends to control in practice. A fault log may clearly be yours, but if it only makes sense alongside OEM fault code documentation you cannot share, it will be far less useful to a buyer.
| Data type | Usual starting point | What to check |
|---|---|---|
| Signals the plant reads from PLCs over its own network | Plant has practical control | Controller software license and any terms on data extraction |
| Sensor data streamed to an OEM or vendor cloud | Governed by the platform agreement | Who may export, retain and reuse it, including after termination |
| Alarm and fault logs stored on the machine | Often accessible to the plant | OEM terms on diagnostic data and fault code documentation |
| Maintenance logs in the plant's CMMS | Company records | Notes written by contractors or OEM service technicians |
| Quality decisions, NCRs and inspection results | Company records | Customer quality agreements and specifications |
| Machine programs and recipes for customer parts | Depends on customer contracts | Who owns programs, tooling and part designs |
| OEM remote service reports | Often OEM documents | Service agreement terms on reports provided to the plant |
| Operator logins and HMI activity | Company records containing personal data | Privacy notices and employee data rules |
OEM contract clauses to check#
OEM contract clauses decide most machine data questions, and they are often spread across several documents. Gather the purchase terms, the software license, any connectivity or subscription agreement and the service contract before deciding scope, then read them for the points below.
- Data definitions: how the agreement defines machine data, usage data, customer data or diagnostic data
- License to the OEM: whether the OEM may use your data to improve products or share it in aggregate
- Restrictions on you: limits on extracting data from the controller, reverse engineering or building competing products
- Confidentiality: whether OEM-provided analytics, reports or fault code documentation count as OEM confidential information
- Export and access: formats, API access and whether history is available on request
- Termination: what happens to cloud-stored history when a subscription ends
- Assignment: whether rights transfer if the plant or the equipment is sold
- Changes to terms: whether the OEM can update platform terms on its own
Customer contracts and machine programs#
Customer contracts can limit machine data even when the OEM terms do not. A CNC program, robot path or molding recipe written to make a customer's part may be tied to the customer's design, and many quality agreements restrict how production data for their parts may be used.
Review the customer's purchase order terms, quality agreement and any tooling or IP agreement before including programs or part-level process data. Customer-owned designs and drawings stay out of scope. Export control is a separate gate: under the Export Administration Regulations, technology includes information necessary for the production, operation and maintenance of an item, so process data for controlled parts may itself be controlled. SourceX excludes export-controlled work.
Trade secrets and your own process data#
Process data from your own machines can be a trade secret, and licensing it carelessly can weaken that protection. Under the Defend Trade Secrets Act, information qualifies as a trade secret only if its owner takes reasonable measures to keep it secret and it derives independent economic value from not being generally known.
DOJ guidance describes reasonable measures as practical steps such as limiting access on a need-to-know basis and requiring confidentiality agreements. A data license with confidentiality terms, permitted use limits and access controls fits that pattern. Even so, some plants leave their most sensitive process windows, such as a proprietary heat treat or coating recipe, out of scope entirely.
Plants with operations in the EU should also ask counsel whether the EU Data Act affects their access to data from connected equipment there. US plants are assessed under their own contracts and state law, deal by deal.
Illustrative: an extrusion plant sorts its machine data#
Illustrative: a fictional plastic profile extrusion plant runs extruders from two OEMs. One OEM's lines stream process data to a vendor portal under a monitoring subscription; the other's are read directly by the plant's own historian. Maintenance and quality records live in the plant's CMMS and QMS.
The plant leader gathers every contract. The monitoring subscription lets the plant view and download its data but grants the OEM broad rights to use it, and it says nothing about the plant licensing the data to others. The second OEM's software license prohibits extracting controller data except for the plant's internal operations. Customer quality agreements for automotive profiles restrict use of part-level production data.
Counsel advises scoping CMMS work orders and QMS dispositions first, with customer identifiers removed and automotive part data excluded. The historian and portal data are held until each OEM confirms in writing whether licensing is permitted. Nothing is ruled out permanently; streams are sequenced by how clear their rights are.
How SourceX approaches machine data rights#
SourceX makes rights the second step of the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. During the fit check the plant describes its equipment, systems and contracts as metadata, and nothing is shared.
Rights review maps each data stream to the agreements that govern it and records the result in a SourceX Evidence Packet, alongside provenance, permitted use, the privacy record and release authorization. Streams with unclear rights wait until they are resolved. The supplier approves every release, and the data is licensed, not sold.
Frequently asked questions
Can an OEM use our machine data without telling us?
It may already have permission in terms you accepted. Many connectivity and software agreements give the OEM rights to use operating data for product improvement or analytics. Read the data sections of each agreement, and ask the OEM in writing how it uses your data if the terms are unclear.
Do we lose history if we end an OEM monitoring subscription?
Possibly. Termination clauses vary: some allow a final export, others delete data after a period or keep it under the OEM's control. Export what you are entitled to before ending a subscription, and treat your own historian and CMMS as the long-term archive.
Are leased machines different?
Often, yes. A lease or rental agreement may add the lessor's terms on top of the OEM's, including rights to monitor the equipment and to collect its data. Check both documents, and treat data from leased equipment as a separate stream in your rights review until both are cleared.
Is reading data from our own PLCs enough to license it?
Technical access is not the same as permission. Controller and HMI software licenses can restrict extracting or reusing data even on your own network. Where the terms are silent the plant is usually in a stronger position, but counsel should confirm before the data is included.
Do operator logins on HMIs create privacy issues?
They can. Login records tie machine events to named employees, which turns a machine log into a record about people. Replace user IDs with role labels before release, and have counsel check whether state privacy laws covering employee data apply.
Sources
- Under 18 U.S.C. 1839(3), information qualifies as a trade secret only if the owner has taken reasonable measures to keep it secret and it derives independent economic value from not being generally known to, and not readily ascertainable through proper means by, another person who can obtain economic value from its disclosure or use. Source
- DOJ guidance states that trade secret protective measures need not be absolute but must be reasonable under the circumstances, citing examples such as advising employees of the trade secret's existence, limiting access on a need-to-know basis, requiring confidentiality agreements, and keeping documents locked. Source
- BIS describes EAR technology (15 CFR 772.1) as information necessary for the development, production, use, operation, installation, maintenance, repair, overhaul, or refurbishing of an item. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.