Manufacturing data readiness checklist for AI, including data rights

How licensing readiness differs from internal AI readiness#

Licensing readiness differs from internal AI readiness because an outside party will use the records. Internal projects ask whether data is clean and connected enough for your own model; licensing asks the same questions and then whether you control the records, may permit outside use and can document what was shared.

That is why most vendor-written checklists, which assume data stays inside your own systems, stop short. They cover sensors, data quality and integration well, and leave ownership, customer designs and contract limits to someone else.

The 12-point checklist#

The 12-point checklist below tests usability first and transferability second. Points one to seven ask whether the records can teach anything; points eight to twelve ask whether they can leave the company. Score each point ready, partial or not ready for every record family, not for the company as a whole.

How to read the scores#

Reading the scores is about deciding scope, not passing or failing the company. A record family that is ready on linkage, depth and rights can move forward even while other families are still not ready.

Maintenance work orders and nonconformance records often score well early, because they are company-authored and describe the company's own equipment and processes. Quote and job records tend to score high on linkage but need more contract review, since they reference customer parts.

• 1Ready on location, linkage, depth, export path and contract rights: a strong candidate for a first package.
• 2Partial on free text or completeness: still useful, but describe the gaps in the data dictionary.
• 3Not ready on export path: resolve with IT or the software vendor before any further scoping.
• 4Not ready on contract rights or exclusions: narrow the scope to the record families that pass.
• 5Not ready on approvals: settle who signs before spending effort on preparation.

Which rights checks do vendor checklists skip?#

Vendor-written checklists usually skip the rights checks because they treat AI as an internal project. Once records go to an outside developer, the questions below decide what is in scope.

The list is general information, not legal advice; counsel weighs the contracts and laws that may apply to each deal.

• 1Customer purchase terms, NDAs and quality agreements that restrict outside use of anything referencing their parts.
• 2Customer-owned drawings, models and specifications attached to quotes, travelers and NCRs.
• 3Export-controlled programs, which are removed in full.
• 4Software vendor terms that limit bulk export or third-party access to data in the system.
• 5Employee notices and policies covering names, IDs and free-text mentions in operational records.
• 6Earlier licenses, data-sharing agreements or exclusivity granted to a software vendor or partner.
• 7Lender, investor or parent-company consents that apply to licensing company assets.

Who should run the checklist?#

The COO or VP of operations should run the checklist, because it cuts across systems, functions and contracts. Their job is to coordinate the answers, not to produce them all.

IT or the OT lead answers location, export path and history depth. The quality manager answers linkage and completeness for NCRs and corrective actions. The controller or CFO knows which contracts and lender documents matter, and counsel reviews rights and exclusions. The CEO confirms the signer and whether the company wants to proceed at all.

Keep the answers in one shared inventory, with one row per record family, so scores, owners and open questions sit together. That inventory becomes the input for any later fit check and saves asking the same questions twice.

Illustrative: a packaging converter runs the checklist#

Illustrative: a fictional flexible packaging converter prints and laminates film for food brands. It runs an ERP for orders and jobs, an MES on its presses and laminators, and tracks nonconformances and maintenance in separate databases. The COO runs the checklist with IT, quality and the controller.

Location, linkage and history depth come back ready for press downtime, maintenance and nonconformance records. Free text is partial: maintenance notes are detailed, but nonconformance descriptions are short. Contract rights fail for printed artwork and customer specifications, which belong to the brands.

The company scopes maintenance, downtime and nonconformance records for a first package, excludes artwork and customer specifications entirely, and asks quality to write fuller nonconformance descriptions from now on. Job records are parked until the controller confirms which customer agreements allow outside use.

How SourceX uses a readiness checklist#

SourceX uses the same twelve points during Supply, the first stage of the SourceX five-step transaction, to decide which record families deserve a deeper look. The answers are metadata only, so a COO can complete them without sending a single file.

Families that pass are weighed with the SourceX Enterprise Data Value Framework and then move through Rights, Preparation, Approval and Delivery. Points nine to twelve carry straight into the SourceX Evidence Packet, which records provenance, licensing rights, permitted use, the privacy record and release authorization for each package, so the company can show later what was released and on whose authority.