Manufacturing
Can engineering change orders (ECOs) be licensed for AI?
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Yes, engineering change order data can often be licensed for AI when the changes concern your own products, because the ECO history is your record of engineering decisions. Customer-directed changes to build-to-print parts are different: the design, and often the change itself, belongs to the customer. Split the history by who owns the design before anything else.
Key takeaways
- ECOs on your own products are usually licensable after a rights review; customer-directed changes usually are not without consent.
- The reasoning sits in the change request and impact analysis, and the value sits in the link to what happened after release.
- ECO packages can carry requests, approvals and outcomes without including CAD models or drawings.
- Engineer names, customer identity, supplier pricing and trade secrets are removed or generalized during preparation.
- Jointly developed products follow the development agreement, which may give either party rights in change records.
Can ECO history be licensed?#
ECO history can usually be licensed when the product being changed is yours. A change request, the impact analysis, the review and approval trail and the result after release together record how your engineering team reasons about cost, risk and quality. Those are your company's records, and they are hard for an AI developer to find anywhere else.
The answer changes when someone else owns the design. Build-to-print manufacturers implement changes their customers direct, and the change content, such as new dimensions, materials or revisions, belongs to the customer's design. Jointly developed products, supplier-initiated deviations and export-controlled programs each add their own conditions.
Licensing does not transfer the history. The company keeps ownership of its change records, approves what goes into any package, and the license defines what a developer may do with them.
The rights split: your ECOs vs customer-directed changes#
The rights split depends on who controls the design that the change modifies. Sort the change history into these groups before reviewing any individual record.
| Change type | Who usually controls the design | Licensable? | What to check |
|---|---|---|---|
| ECO on your own product | Your company | Usually, subject to review | Supplier and co-development agreements |
| Customer-directed change on a build-to-print part | The customer | Usually not without written consent | Customer agreements and NDAs |
| Your proposal to change a customer's design | The customer owns the design | Possibly the reasoning, without the design content | Agreement terms on suggestions and improvements |
| Supplier-initiated change or deviation | Shared with the supplier | Case by case | Supplier agreement confidentiality |
| Change on a jointly developed product | As the development agreement sets out | Depends on the agreement | Joint development and IP clauses |
| Change on an export-controlled product | Varies | No; scoped out | ITAR or EAR classification |
What an ECO history contains#
An ECO history contains a chain of linked documents, not a single form. The request explains why, the order explains what and the notice tells the rest of the business when. Records are most useful when that chain stays intact.
- Engineering change request: the problem or opportunity, who raised it and the evidence behind it, such as an NCR, warranty claim or cost review.
- Impact analysis: effects on cost, inventory, tooling, suppliers, documentation and certification.
- Review and approval trail: change board comments, objections, conditions and sign-offs.
- Engineering change order: affected parts, old and new revisions, markups and instructions.
- Effectivity and disposition: when the change takes effect and what happens to work in process and stock.
- Engineering change notice: communication to purchasing, production, quality and service.
- Follow-up: whether the change solved the problem, seen in later NCRs, warranty claims or field reports.
What makes an ECO history worth more#
An ECO history is worth more when it links back to the trigger and forward to the outcome. A change raised from a cluster of warranty claims, approved after a documented debate about cost and tooling, and followed by a drop in the same failure mode is a complete example of engineering judgment. A bare list of part revisions is not.
Written discussion matters. Change board comments, rejected alternatives and conditions attached to approval show how engineers weigh trade-offs, which is the reasoning AI developers building engineering assistants want to learn from. Systems that kept those comments, whether a PLM such as Arena, Windchill or Teamcenter or an ERP engineering change module, hold more than systems that kept only the final state.
Consistency over time also counts. Change categories, reason codes and approval roles that stayed stable across years make a history easier to describe and use. Where categories changed during a PLM migration, a mapping between old and new values keeps the history usable.
Preparing ECO records: what to keep and what to change#
Preparing ECO records keeps the reasoning and the links while removing people, customers and secrets. The table shows how the common elements of a change record are usually handled, though the final call on each sits with the company.
Keep the mapping between pseudonymous part IDs and real part numbers inside the company. Questions from the developer can then be answered later without exposing the original identifiers or the customers behind them.
| Element | Usually kept | Usually removed or generalized |
|---|---|---|
| Change request text | Problem description, evidence and reason code | Customer names and complaint contacts |
| Impact analysis | Affected areas, risk notes and cost direction | Supplier names and pricing |
| Approval trail | Roles, comments, conditions and the decision | Engineer and manager names |
| Revision detail | Descriptions of old and new revisions | Exact values or formulas that are trade secrets |
| Markups and drawings | Text descriptions of the change | Drawing files, unless you choose to include your own |
| Outcome evidence | Summaries of linked NCRs, warranty claims and field reports | End-customer and site identities |
Illustrative: a pump maker separates its change history#
Illustrative: a fictional maker of industrial pumps designs its own product line and also builds subassemblies to print for an equipment OEM. Recent ECOs live in a PLM system; older ones sit in an ERP engineering change module, with markups saved as PDFs on a file server.
The VP of engineering sorts the history by design ownership. Changes to the company's own pumps, many linked to warranty claims and field service reports, go into scope. Changes directed by the OEM customer are excluded. The company's own improvement proposals to the OEM's parts are set aside for counsel to review against the supply agreement.
The company also decides to keep its own CAD models out of the package to protect product IP, licensing the change requests, impact analyses, approval comments, revision descriptions and outcomes instead. Engineer names become role labels, and supplier names in impact analyses are replaced with neutral labels.
How SourceX approaches ECO records#
SourceX starts an ECO review by splitting the history by design ownership. In the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery, that split happens in the Rights step, before any record is prepared, and it follows the change types in the rights table above. The fit check collects only metadata, such as the PLM or ERP in use, years of history and the share of work that is build-to-print.
For each change family that proceeds, the SourceX Evidence Packet documents provenance, licensing rights, permitted use, the privacy record and release authorization, so the company, its counsel and the buyer all see which changes were included and why.
Frequently asked questions
Do we have to include CAD files with ECOs?
No. ECO packages can carry the change request, impact analysis, approvals and outcome without the models or drawings. Including CAD for your own products is a separate decision about intellectual property and value, and customer CAD stays out unless the customer agrees.
Are ECRs and ECNs licensed separately from ECOs?
They are usually licensed together because they form one chain: the request, the order and the notice. Splitting them loses the reasoning at one end and the outcome at the other. What matters is that the identifiers linking them survive the export.
Could licensing ECO history expose trade secrets?
It can if the scope is careless. Review ECOs for formulas, proprietary processes and supplier pricing, and exclude or generalize them. The license also limits permitted use and sets confidentiality terms, and the company approves the prepared records before delivery. Where a single change reveals a core trade secret, leave that change out rather than redacting it heavily.
What if changes were handled by email before we had a PLM?
Email-era changes can still be useful if they can be tied to part revisions. Index them by part number and revision, remove personal and customer details, and note the change in format in the data documentation so a developer understands the gap.
Do regulated or certified products change the answer?
They can. Change records for products that need certification or agency filings may be tied to submissions and customer notifications, and they can carry extra confidentiality and retention rules. Review those change families separately with counsel and quality before deciding whether they belong in scope.
How is this different from construction change orders?
Construction change orders and RFIs record changes on a building project, where the owner and design team usually control the design. Manufacturing ECOs record changes to a product that a manufacturer may own outright. The rights analysis differs, so treat them as separate record types.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.