The scorecard is part of the guide on engineering change order process records. Use it after the metadata packet, which describes the systems; this page tests whether what they hold is complete enough to discuss.
How to score
Ask each question of the engineering operations head or the engineering systems lead. Score each check:
- Pass (1 point): the company says the condition holds across the period that matters, and can say how it knows.
- Partial (half a point): it holds for part of the period, or for some product lines, or by manual habit rather than a required field.
- Fail (0 points): it does not hold, or nobody knows.
Add the points out of 8. Write down the reason for every partial and fail; the reasons matter more than the total. Keep the conversation at metadata level: you are asking how the systems behave, never for an example record.
The scorecard
| Check | Ask, at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|
| 1. Coverage | Which years does each system hold, and do they overlap? | Requirement, PLM and ERP history overlap for several years | Overlap is short or one system is recent | One system has no history for the period |
| 2. Requirement link | Is the requirement or issue key a required field on the change request? | Required and system-validated | Typed by habit, sometimes missing | Not recorded |
| 3. Effectivity transfer | How does effectivity reach the ERP BOM? | Interface carries the change number | Manual entry citing the change | Manual entry with no reference |
| 4. Release timestamps | Do closed orders keep their original release date? | Kept as a field or in change history | Kept only in a log that is purged | Overwritten by the current status |
| 5. Version stamp | Does each production order store the BOM version it used? | Stamped at release | Stamped for some plants or years | Order links to the item only |
| 6. Outcome link | Do rework, scrap and holds cite the change number? | Required reference | Cited in free text | Not linked |
| 7. Archive access | Are archived orders still retrievable with their links? | Retrievable with BOM version and dates | Retrievable as summaries | Deleted or unreadable |
| 8. Pre-PLM history | Where are changes from before the current PLM? | Migrated with links | Scanned and indexed | Unindexed or discarded |
Two of these checks rest on documented system behavior. PTC describes effectivity as the planned date, lot or serial number at which old versions are replaced in production, set on the change notice and made actual on approval, so check 3 is about whether that cut-in survives the trip to the ERP. SAP documents that a BOM changed under a change number keeps a pre-change state ending at the valid-from date and a post-change state starting there, which is what makes check 5 answerable when the order stamps its version.
The hard test: an order released under the old revision
Every scorecard should be read against one case: a production order released after the change was approved but built to the old revision. Ask the company to walk through how it would answer these questions for such an order, in words:
| Question about the order | Checks it depends on |
|---|---|
| Should this order have used the new revision? | 3 and 4 |
| Which revision did it actually use? | 5 |
| Why did the change matter for this customer? | 2 |
| What was done about the units built? | 6 |
| Can the same be shown for an order from five years ago? | 1, 7 and 8 |
If the company can answer all five, the trail is strong. If it stalls at "which revision did it actually use", check 5 is the gap, and that single gap makes most old-revision cases unprovable.
Illustrative scored result
Invented for this page. A 600-person maker of package-handling conveyors, with PLM since 2018 and the ERP since 2010.
| Check | Score | Reason given |
|---|---|---|
| 1. Coverage | Pass | Requirement tracker, PLM and ERP overlap from 2018 |
| 2. Requirement link | Partial | Issue key typed by habit; required only since 2022 |
| 3. Effectivity transfer | Pass | Interface carries the change number |
| 4. Release timestamps | Pass | Release date kept in order change history |
| 5. Version stamp | Pass | BOM version stamped at release in both plants |
| 6. Outcome link | Partial | Rework orders cite the change in free text only |
| 7. Archive access | Pass | Archived orders retrievable with dates and BOM version |
| 8. Pre-PLM history | Pass | Earlier changes migrated with item links |
Six passes and two partials make 7 of 8. The reasons point to what SourceX would want to understand: requirement links are reliable from 2022, and outcome links depend on free text.
Check 7 deserves care. SAP documents that production orders are archived in stages, a deletion flag, a deletion indicator after a residence time and then an archiving run that removes them from the database, with a retrieval function to display archived orders. Whether links survive that process depends on how the company configured it, so ask rather than assume.
What a score does not tell you
A score is a description, not a verdict. It does not establish SourceX's current data needs, the rights position, the value of the records or whether SourceX will make an offer; those stay unknown until SourceX reviews them with the company. It also does not authorize anything. Who owns the records and who can approve a licensing discussion (the CEO, or in an owner-run company the owner) are separate questions from how complete they are. The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license 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.
For how the links fit together, see the record chain. Comparable change histories in construction are covered under change order data, and why multi-step sequences matter is explained in long-horizon tasks for AI agents. If a PLM replacement is planned, the PLM migration consultant guide explains when checks 7 and 8 can change.
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 manufacturer can answer the eight checks and explain its partials, register as a partner, confirm the company against who qualifies, and read the program terms before introducing the CEO, who can authorize the discussion.