Engineering change to effectivity completeness scorecard: eight checks before you promise anything

Short answer

An engineering change trail breaks in predictable places: a requirement key that was never carried into the change, effectivity that lives only in the PLM, release dates overwritten on closed orders, production orders that do not record which BOM version they used, rework that does not cite the change, and older history left behind at a system migration. This scorecard turns each break into a check a partner can ask about, scored pass, partial or fail, without anyone opening a record.

Visual briefFull-size diagram
A checklist of eight checks ticks down one by one, six passing in green and two marked partial in orange, while a completeness meter beside it rises to 7 of 8 points.
Illustrative score for a fictional conveyor maker: 6 passes and 2 partials give 7 of 8 points.

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

CheckAsk, at metadata levelPassPartialFail
1. CoverageWhich years does each system hold, and do they overlap?Requirement, PLM and ERP history overlap for several yearsOverlap is short or one system is recentOne system has no history for the period
2. Requirement linkIs the requirement or issue key a required field on the change request?Required and system-validatedTyped by habit, sometimes missingNot recorded
3. Effectivity transferHow does effectivity reach the ERP BOM?Interface carries the change numberManual entry citing the changeManual entry with no reference
4. Release timestampsDo closed orders keep their original release date?Kept as a field or in change historyKept only in a log that is purgedOverwritten by the current status
5. Version stampDoes each production order store the BOM version it used?Stamped at releaseStamped for some plants or yearsOrder links to the item only
6. Outcome linkDo rework, scrap and holds cite the change number?Required referenceCited in free textNot linked
7. Archive accessAre archived orders still retrievable with their links?Retrievable with BOM version and datesRetrievable as summariesDeleted or unreadable
8. Pre-PLM historyWhere are changes from before the current PLM?Migrated with linksScanned and indexedUnindexed 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 orderChecks 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.

CheckScoreReason given
1. CoveragePassRequirement tracker, PLM and ERP overlap from 2018
2. Requirement linkPartialIssue key typed by habit; required only since 2022
3. Effectivity transferPassInterface carries the change number
4. Release timestampsPassRelease date kept in order change history
5. Version stampPassBOM version stamped at release in both plants
6. Outcome linkPartialRework orders cite the change in free text only
7. Archive accessPassArchived orders retrievable with dates and BOM version
8. Pre-PLM historyPassEarlier 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.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. 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.

Common questions

What score is good enough to introduce a company?

There is no threshold. The scorecard helps you describe the records honestly; SourceX decides fit after its own review. A company with several partials can still be worth introducing.

Can the scorecard be filled in without the company's IT team?

Usually not fully. The engineering operations head can answer most checks, but the linkage and archiving checks often need the IT integration lead.

Should the partner share the score with the company?

Yes, if it helps. It shows the company what it already knows about its own records and what is still open, without anyone having handled data.

Sources

  1. support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_…
  2. help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a…
  3. help.sap.com/saphelp_46C/helpdata/EN/b1/c04f06439a11d1894…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment