Can manufacturing data stay on our own servers during a data license?

Short answer: what stays in your environment and what moves#

Almost everything stays in your environment until delivery, and even then the handover can start from your own storage. The table shows each stage of a typical license and what, if anything, leaves.

The row many IT directors miss is the last one. A license gives the buyer a copy of the prepared dataset for the permitted use, so if company policy says no copy may ever leave, raise that at the fit check; it narrows what is possible.

The three delivery options compared#

The three delivery options are seller storage, an encrypted drive and a managed transfer, and the right one depends on size, bandwidth and policy. SourceX never hosts multi-terabyte datasets, so large packages use the first two.

Each option ends the same way: the handover is recorded so both sides can show what was delivered, when and under which authorization.

Which plant records are usually small, and which are large?#

Text-heavy plant records such as work orders, NCRs and quotes are usually small, while historian, image and CAD archives are usually large, and size decides the delivery route more than anything else.

Size also shapes preparation. Text needs careful review for names and customer details, while large sensor archives need checks for network and security details and decisions about which tags and time ranges matter. Scoping a narrower slice often removes the need for a drive at all.

• 1Usually compact: work orders, NCRs, CAPAs, ECO text, complaint cases, quotes and maintenance notes exported from the ERP, QMS or CMMS
• 2Moderate: ERP transaction history with operation-level detail, plus the text of attachments
• 3Usually large: process historian archives, machine vision images, inspection scans, CAD vaults and video

What your production network does not need to allow#

A data license does not need inbound access to your production network. No one outside the company needs a VPN into the plant, credentials to the ERP or MES, or a connection to the OT network; your team creates extracts and stages them where policy allows.

OT exports deserve a second look before they leave. Historian tags, PLC exports and network configuration files can reveal IP addresses, controller models and network topology, which are security details rather than training value, and they are removed or excluded.

• 1Extract from a reporting replica or restored backup, not the live production database.
• 2Use a read-only service account scoped to the tables in the inventory.
• 3Stage extracts in a storage location separate from production systems.
• 4Encrypt at rest and keep the keys under your own management.
• 5Produce a file manifest with record counts and checksums for every delivery.
• 6Revoke any buyer access and log the revocation once handover is confirmed.

How a buyer confirms what it received#

A buyer confirms receipt against a manifest, not by looking inside your systems. The manifest lists each file, its record count and its checksum, alongside the data dictionary that explains fields, codes and any values that were masked or banded.

The SourceX Evidence Packet travels with the package. It records provenance, licensing rights, permitted use, the privacy record and release authorization, so the buyer can see what was approved without any access to the source environment.

This also protects the supplier. If a question about scope comes up later, the manifest and the Evidence Packet show exactly which records were released, which makes the license easier to audit and defend.

Illustrative: a foundry that kept everything on site#

Illustrative: a fictional gray and ductile iron foundry runs an on-premises ERP, a QMS and a process historian on its furnaces and molding lines. Its IT director had a firm rule that production data does not go to third-party clouds, and the plant's upload bandwidth is modest.

The fit check covered system names and years of history only. After rights review and preparation, the text-heavy package of maintenance work orders and nonconformance reports was small enough for a managed transfer. The historian archive, far larger, was written to an encrypted drive, shipped with a chain-of-custody record and unlocked with a key sent separately.

At no point did anyone outside the company connect to the plant network. The IT director kept the extraction scripts, the manifest and the revocation log as the company's own record of the license.

How SourceX handles delivery#

Delivery is the last stage of the SourceX five-step transaction, after Supply, Rights, Preparation and Approval. No files move during the initial assessment, the supplier signs off at every step, and large datasets stay in the supplier's own storage or ship on encrypted drives because SourceX never hosts multi-terabyte datasets.

Every delivery records how the handover happened, whether through uploaded files, the supplier's storage or a drive. That record, with the manifest, is what both sides rely on if a question about scope or timing comes up later.