This agenda belongs to the PLM partner guide to change-to-order trails, which explains why the trail is worth asking about. This page is the meeting itself: who to invite, the run sheet, how to read the answers and how to close.
Set up the meeting before the cutover plan freezes
Timing matters more than polish. Hold the meeting once the upgrade scope is agreed but before the integration cutover plan is signed off, while people still remember how the old engineering-to-ERP link works and before anyone has scheduled its retirement.
- Invite line. "Thirty minutes on what the current change and shop-floor history can show before go-live. Description only; nobody will be asked for files." That line tells the planner and the shop-floor systems administrator they will not be asked to pull data.
- Pre-read. The five block questions in one list, nothing else.
- Whiteboard. Draw the empty columns of a trace matrix: change number, effectivity, revision built, disposition, link survives. Use it to prompt answers, never to fill in real order numbers.
- Notes. Keep a four-column table yourself: block, answer, who said it, follow-up. You will read from it at minute 25.
- Parking lot. Design questions about the new system go to the project team. This meeting is only about the history the old setup leaves behind.
Who sits at the table
Four roles cover the five blocks. If a role is absent, its block becomes a named follow-up rather than an answer.
| Role | Why they are needed | Blocks |
|---|---|---|
| Engineering systems administrator | Knows how changes, effective dates and revisions are held today | 1 and 2 |
| Planner or shop-floor systems administrator | Knows what each work order records and where use-as-is, rework and scrap are posted | 2 and 3 |
| ERP lead or IT manager | Knows how the current integration passes revisions to orders | 3 and 4 |
| Owner or CEO, with the COO or plant general manager | Can speak to ownership and customer designs; the CEO can authorize a licensing discussion | 4 and 5 |
For build-to-print manufacturers, ask the owner to bring whoever manages customer contracts. Customer-owned drawings are common, and block 4 cannot be closed without knowing which designs the company itself owns.
Run sheet: five blocks in 30 minutes
Illustrative. A 380-person maker of industrial pump assemblies is replacing a 15-year-old engineering system and rebuilding its ERP link. The partner runs this agenda two weeks before the cutover plan is approved.
| Minutes | Question for the block | Who answers | What a good answer sounds like |
|---|---|---|---|
| 0-6 | Where are effective dates held: a field on the change, an ERP version with dates, a spreadsheet, or several? | Engineering systems administrator | "Dates are fields on the ECO since 2016; before that they are in the description text." |
| 6-12 | Does each work order record which revision it built, or only the item number? | Planner | "The order carries the revision letter; the router does too." |
| 12-18 | When work in progress is used as is, reworked or scrapped, is that transaction tied to the change number? | Shop-floor systems administrator and ERP lead | "Rework orders reference the ECO; scrap does not, it only has a reason code." |
| 18-25 | How many years of changes and orders exist, and which designs belong to customers or carry export controls? | Owner and ERP lead | "Around 14 years of orders; three product lines are build-to-print for one customer." |
| 25-30 | Does the company want to hear how licensing approved records works, and who would lead it? | Owner | "Yes. Our COO is the working contact; leave the build-to-print lines out." |
Facilitator notes for blocks 1 to 3
The first three blocks are where vague answers creep in. Each has a follow-up probe for when the first reply is "it depends", and a line to write in your notes so nobody has to remember the conversation later.
| Block | Follow-up probe if the reply is vague | What to write in your notes |
|---|---|---|
| 1. Effective dates | "If I asked for every change that took effect in March 2019, would someone run a report or read through change descriptions?" | Field, free text, spreadsheet or mixed, plus the year the field was introduced |
| 2. Revision on the work order | "Could the traveler or router from a 2018 job tell you which letter it was built to?" | Revision stamped on order, on router only, or not recorded |
| 3. Disposition link | "When a batch of housings was scrapped after a change, what would point an auditor back to that change?" | Which of use as is, rework and scrap carry the change number, and which carry only a reason code |
A public reference point helps when people struggle to picture block 1 or 2. Microsoft documents that Dynamics 365 Supply Chain Management holds effective-from and effective-to dates on each engineering version and can write the exact version onto each transaction; it can also test a change request against open production orders and close the notification once those orders are canceled or modified. Mention it only as an illustration of what "held as a field" means. The client's platform may work quite differently, and the planner's description of their own setup is what goes in the notes.
Blocks 4 and 5: ownership, scale and the decision
Ranges are enough: years, rough order volumes, how many product lines. Customer-owned and export-controlled designs are for the company's counsel to judge; flag them and move to block 5. If the owner hesitates, offer the second outcome below rather than pressing for a yes.
Signals to listen for in each block
Not every answer is yes, and some answers should change the rest of the meeting.
| What you hear | What it usually means | What to do |
|---|---|---|
| "Effectivity is whatever the ECO description says." | Dates exist but are not structured | Note "partly" and the years; carry on |
| "Orders only show the current item number." | Past revisions may not be matchable | Ask whether routers or travelers kept the revision |
| "Scrap has a reason code, nothing else." | Disposition links are weak | Note which disposition types do link |
| "We are not migrating closed orders." | The production half may stay in the old ERP | Note the old system's planned end date for the archive context checklist |
| "Most designs belong to our customer." | Rights to license may be narrow | Ask which lines are the company's own; stop for the rest |
A meeting that closes with "partial trail since 2016, own designs only, CEO to decide" is a good result. The engineering change order process page explains the ECR, ECO and ECN records behind block 1, and the PLM migration consultant guide covers carrying ECO and BOM history into the new platform.
Closing the meeting: the decision and the notes
Before asking for the decision in block 5, say three things plainly.
What SourceX does. SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. Attending this meeting shares nothing.
Your interest. You are a SourceX referral partner and may receive a reward if a qualifying license completes and every payment condition in the terms is met. SourceX funds it separately; it never reduces the company's payout. Illustrative only: a $400,000 payout to the company on its first qualifying transaction would mean a USD 70,000 reward (USD 50,000 plus 5%, which is more than 15%); there is no cap, and a repeat transaction agreed within 12 months would pay 15%. The rewards page lists every condition.
Whether the company can qualify. It needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. 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. The engineering and design industry page covers sector specifics.
Then record one of three outcomes in your notes, with the owner's own words beside it:
- Introduce now. Name the authorized contact, confirm you have signed the Channel Partner Agreement, and submit. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application.
- Revisit after cutover. Note the date the old integration is due to be retired, because that is when the decision closes.
- Stop. Record that the history question was raised and declined, and carry on with the modernization.
What stays unknown until SourceX reviews it: SourceX's current data needs for change and production trails, the rights review result, de-identification needs and any offer. For a different setting that uses the same meeting discipline, see the sell-side kickoff meeting agenda.
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 block 5 ends with the owner choosing an introduction before the old integration is retired, register as a partner, check the company against who qualifies, and read the program terms before you submit.