Can electronics manufacturers and PCB assemblers license their data?

What can an EMS provider license?#

An EMS provider can usually license its own records about how boards were built, inspected, tested and repaired, after a rights review, but not the designs it built to. The process knowledge belongs to the manufacturer; the board design belongs to the OEM customer.

Contract manufacturers build almost entirely to customer designs, so their rights map is more detailed than most. Each record has to be sorted by how much of the customer's design it carries. OEMs that design and build their own products face far fewer of these questions, because the designs and the records are both theirs.

Data is licensed, not sold outright. The manufacturer keeps ownership, and each customer program can be included, de-identified or left out on its own terms.

Record map for an SMT and test operation#

An SMT and test operation produces records that range from pure process data to direct images of the customer's design. The third column is the one that decides scope.

The customer-design exclusion#

The customer-design exclusion means Gerber files, schematics, BOMs, placement files, firmware and test programs supplied by the OEM stay out of any package unless that customer agrees in writing. Manufacturing services agreements commonly treat those files as the customer's intellectual property and confidential information.

The harder cases are records derived from those designs. An AOI image of a defect shows part of the board layout, a repair note names a reference designator and a test failure log reflects the test program. Each one needs a decision: remove the design element, obtain consent, or leave the record out.

Some teams consider cropping images to the defect area. Even small crops can reveal component choices and layout details, so cropping is a rights question for counsel and the customer, not a technical workaround.

Which electronics records carry the most value?#

The most valuable electronics records follow one defect from detection to outcome. A solder paste measurement, the AOI call that followed, the operator's confirmation or override, the rework step, the retest result and any later field return form one complete example.

Operator verification of AOI calls is a good case. Every time an operator confirms a real defect or overrides a false call, they create a labeled example. Those labels are what inspection model developers look for, provided the images can be used.

• 1Serial-level links from SPI and AOI through test, repair and RMA.
• 2Operator verification decisions on machine inspection calls.
• 3Repair notes that explain the cause, not just the action.
• 4Defect codes mapped to IPC-A-610 acceptability criteria, alongside your own finer codes.
• 5Feeder, nozzle and changeover history tied to placement errors.

Preparing electronics records without losing the links#

Preparing electronics records means removing customer and personal identity while keeping serial-level links intact. Serial numbers, work orders and customer part numbers are replaced with consistent pseudonymous IDs, so a board can still be followed from paste inspection to RMA without revealing whose board it is.

Reference designators and component values in repair notes are generalized where they would reveal a design, for example to component type and package. Operator IDs in verification and repair logs become role labels. The mapping tables stay with the manufacturer and never ship with the package, which keeps re-identification in the company's hands.

Illustrative: an EMS provider sorts its records by customer#

Illustrative: a fictional EMS provider builds boards for industrial control and instrumentation customers and also sells its own line of power supply modules. Its MES tracks serial numbers through SMT, AOI, flying probe and functional test, and its repair stations log each repair with a defect code and a note.

The rights review sorts programs into groups. The in-house power supplies are clear. Some customers' agreements allow de-identified process data to be used, others prohibit any use, and one program falls under export controls. The COO asks for a scope that respects every one of those lines.

The resulting scope covers line performance data across permitted customers with customer identity removed, AOI images and verification labels only for in-house products and consenting customers, repair records with reference designators generalized, and test outcomes by failure category. The restricted and export-controlled programs are left out entirely.

Questions to answer before a fit check#

Questions about contracts, products and system settings decide most of the scope, and each can be answered without exporting anything. The answers shape a package more than any record count.

• 1Which customer agreements permit de-identified use of process data, and which prohibit any use?
• 2Which programs involve ITAR-controlled or other export-controlled technical data?
• 3Do you design and build any products of your own?
• 4Where are AOI and X-ray images retained, and how far back do they go under your current settings?
• 5Do serial numbers link SMT, test, repair and RMA records?
• 6Where do operator IDs appear in verification and repair logs?

How SourceX approaches electronics manufacturing records#

SourceX handles electronics records through the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. Because so much EMS data derives from customer designs, the Rights step does most of the work, mapping each program to its agreement before any preparation begins. The fit check itself collects only metadata.

Image libraries and test databases stay in the manufacturer's own storage or ship on encrypted drives. The SourceX Evidence Packet records provenance, licensing rights by program, permitted use, the privacy record and release authorization.