# Engineering change to production order trails | SourceX

Canonical: https://refer.sourcex.si/guides/moment-engineering-system-modernization-plm-partners
Last updated: 2026-11-05

Often only partly, and modernization is when the gap shows. A full trail runs from the engineering change order to its effectivity (a date, serial or lot), to the BOM revision that took effect, to the production orders built before and after, and the disposition of work in progress. The PLM usually holds the first half and the ERP or MES the second. PLM partners can ask the owner whether that bridge survives the new system. If it does and the company qualifies, the owner may want an introduction to SourceX.

## Can an engineering change be traced to affected production orders?

Ask it plainly, then find out where the link lives. In some manufacturers the ERP stamps a revision on every production order, so the trail is a query. In others, effectivity is a note on the ECO, and matching it to orders means a planner's memory or a spreadsheet.

One documented model shows what the link can look like. In Microsoft's Dynamics 365 Supply Chain Management, a change request can be checked against open transactions such as sales orders, production orders and on-hand inventory; affected production orders can be blocked or production notified, and the notification is marked resolved once the orders are canceled or modified. Engineering versions carry effective-from and effective-to dates, and a product category can be set to track versions in transactions, stamping the specific version on documents such as sales orders. Other platforms model it differently, so treat this as an example, not an assumption about the client's stack.

### Trace matrix: one change, five orders

The trace matrix below is the evidence asset to sketch with the client, at metadata level. Illustrative: a 420-person maker of hydraulic valve assemblies, one change from revision B to revision C, five orders.

| Production order | Released | Revision built | Relation to effectivity date | Disposition recorded | Traceable after modernization? |
|---|---|---|---|---|---|
| PO 1 | Before change | Rev B | Before; completed | None needed | Yes, if order history moves |
| PO 2 | Before change | Rev B | Before; in progress | Use as is | Only if the disposition is stored with the order |
| PO 3 | Before change | Rev B, reworked to Rev C | Straddles the date | Rework | Only if rework links back to the change number |
| PO 4 | After change | Rev C | After | None needed | Yes, if the revision is stamped on the order |
| PO 5 | After change | Rev C | After; scrap of old stock | Scrap Rev B parts | Only if scrap links back to the change number |

Orders 2, 3 and 5 are the valuable ones: they show an engineering decision meeting real production, with a cost and an outcome. They are also the rows most likely to lose their link when the old integration is switched off. The [engineering change order process](/data-types/engineering-change-order-process) page explains the ECR, ECO and ECN records on the engineering side.

Why anyone would license this: a change, its reasoning, the orders it touched and what happened to them form a multi-step operational record with a known result, a kind of record that rarely appears on the public web. Whether a buyer wants a particular company's trail is only known after SourceX reviews it.

## Why is the effectivity and design-change trail easy to overlook?

Because modernization projects are scoped as engineering projects. The team migrates parts, BOMs, documents, CAD vaults and change objects into the new platform, and rebuilds the integration to the ERP for current and future releases. The historical join between a past change and the orders it touched sits across the two systems, so neither the PLM workstream nor the ERP workstream owns it.

Three patterns make the gap wider. Effectivity is often recorded loosely: a date typed into an ECO description rather than held as a field, or a serial break agreed in a meeting and kept in a planner's spreadsheet. Dispositions such as use as is, rework and scrap are posted in the ERP or MES against the order, not against the change, so the link back depends on someone having typed the change number. And the new integration is usually built forward: it publishes new releases to the ERP but does not rebuild the history of what the old one published.

The existing guide for [PLM migration consultants](/guides/plm-migration-consultant) covers keeping ECO and BOM history in the move. This page adds the production side of that history, which is the part that turns a list of design changes into a record of what each change did on the shop floor.

## Four metadata questions for the owner

Stay at metadata level: what exists, how much, how long, which system and who owns it. Four questions answer the kept question without opening a record:

1. **Where does effectivity live?** In the PLM as a field, in the ERP as an engineering version with dates, in a spreadsheet, or in more than one place?
2. **Is the revision on the order?** Does each production order record which revision it built, or only the current item number?
3. **Are dispositions tied to change numbers?** When work in progress is used as is, reworked or scrapped, is that transaction linked back to the ECO?
4. **How much, and whose?** Roughly how many years of change history and production orders exist, and are some designs owned by customers or covered by export controls?

Note each answer as yes, no, partly or unknown, with ranges rather than counts. Customer-owned and export-controlled designs are for the company's counsel to judge; flag them and move on. Do not request drawings, BOM extracts or order samples. If the production system is being replaced in the same program, note it, because closed production orders then face their own migration decision. Partners working on the ERP side can compare the [NetSuite project guide](/guides/how-erp-consultants-spot-referral-opportunities-during-netsuite-projects), and the [engineering and design screening worksheet](/resources/a-referral-screening-worksheet-for-engineering-and-design-businesses) helps with size and rights.

## How do you disclose the reward and get the owner's permission?

Ask first, then disclose. For example: "Separate from the modernization, that trail may have value outside the company. May I mention one option? I should say I am a referral partner and may receive a reward if it leads anywhere."

If the owner agrees, explain that SourceX licenses approved business data directly from companies for AI training and evaluation and pays the company under a license agreement if one is signed, and that your reward is funded separately and never reduces the company's payout. If the owner declines, record that the archive decision was raised before cutover and carry on with the project.

Describe the reward exactly. The default on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the Actual Supplier Payout is the amount SourceX actually pays the company. Illustrative only: a USD 400,000 payout would mean a USD 70,000 reward, and a further qualifying transaction first agreed within 12 months of the first Closing would pay 15% of its payout. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. The [rewards page](/rewards) walks through the order.

## Who owns engineering change records, and who can authorize a licensing discussion?

The manufacturer normally owns its change history and production records, but customer-owned designs and export-controlled technical data limit what can be licensed, and the company's counsel decides. The person who can open a licensing discussion is the CEO (in an owner-run company, usually the owner), not the engineering systems lead running the project.

| What you can note | Who confirms it | What stays unknown until SourceX reviews it |
|---|---|---|
| Systems, years of change history, order volumes in ranges | Engineering systems or IT | Whether the records match current dataset demand |
| Customer-owned or export-controlled design data | The company's counsel | The rights review outcome |
| The authorized decision-maker | CEO, often the owner | Any offer, its terms and timing |
| Full-time headcount at peak | Owner or HR | Final eligibility confirmation |

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact; [who qualifies](/who-qualifies) has the detail, and the [engineering and design industry page](/industries/engineering-and-design) covers sector specifics. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Sign the Channel Partner Agreement before submitting. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Other partner roles are on the [partner hub](/for).

## Go deeper on engineering system modernization records

- [Engineering system modernization meeting agenda](/resources/engineering-system-modernization-meeting-agenda): a timed agenda for the owner conversation about change-to-order traceability and the referral option.
- [Engineering system modernization archive context checklist](/resources/engineering-system-modernization-archive-context-checklist): a checklist of decommission dates, integration scope and retention points to confirm before cutover.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's changes still trace to the production orders they touched and the owner opts in before cutover, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and review the [program terms](/terms) before you make the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/engineering-change-management/engineering-change-management
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/engineering-change-management/engineering-versions-product-category
