Engineering change to effectivity, before and after: what a standalone Windchill export loses

Short answer

A single-system export of an engineering change usually keeps the what and the when: the affected part, the new revision, the approval and the effectivity date or serial. It loses the why and the so-what: the customer requirement that started the change, the design reasoning, the production orders that missed the cut-in, the units held or reworked, and whether the fix worked. That context lives in the requirement tracker, the ERP, the quality system and email, not in the PLM.

Visual briefFull-size diagram
A change notice card with five blank rows labeled why, orders hit, units, done and fix held; context pieces from Jira, the ERP, quality and service slide in and fill each blank.
Illustrative. The same change notice before and after its surrounding context is attached.

This before-and-after reading is part of the guide on engineering change order process records. The record chain page names the keys that join the systems; this page shows what a reader actually sees with and without them.

Before: the change notice on its own

Illustrative case, invented for this page. A 410-person maker of commercial rooftop air handlers changes the supply fan motor from one frame size to a higher-efficiency model. The engineering team exports change notice CN-7720 from PTC Windchill. Read alone, it says:

Field in the exportValue
Change noticeCN-7720, approved Sep 9
Affected itemFan motor assembly, revision D to revision E
EffectivityLot effectivity from lot 2291
Change tasksUpdate drawing, update BOM, notify purchasing
Reason"Efficiency improvement"

PTC documents that effectivity is the planned date, lot or serial number at which old versions are replaced by new ones in production, and that planned effectivities on a change notice become actual when the notice is approved. So the export is precise about the cut-in. A reviewer reading it would conclude that lot 2291 onward has the new motor and nothing else happened. That reading is tidy, and in this case it is wrong.

After: the same change with its context attached

Now the same change, with records from the other systems joined by key and date:

DateSourceWhat it adds
Jul 22Jira requirementA utility rebate program requires a minimum fan efficiency for units shipped to one region from Oct 1
Aug 4Jira design reviewRevision E chosen; the motor mount needs a new bracket, which the CN does not mention
Sep 9WindchillCN-7720 approved, effectivity from lot 2291
Sep 11ERPLot 2288 released against the old BOM; ERP BOM valid-from date keyed Sep 16
Sep 30QualityHold on 18 units from lot 2288 bound for the rebate region
Oct 3ERP18 units retrofitted with revision E motors and brackets; rework order cites CN-7720
Nov 14ServiceFirst field reports from the region show no motor complaints; requirement closed

The PLM record was correct; it was just incomplete. The deadline that drove the change, the hidden bracket dependency, the lot that slipped through, the hold and the retrofit are all outside it. SAP documents that in its standard model a BOM changed under a change number is stored as a pre-change state ending at the valid-from date and a post-change state starting there, which is how the ERP shows lot 2288 still on the old state. Only the joined view shows that it mattered.

What is lost, and where it lives

This table is the core of the page. Each row is a piece of context a standalone export drops, with the system that usually holds it and the person who can describe it.

Lost contextWhy a reviewer needs itWhere it usually livesWho can describe it
The triggering requirementShows the business reason and deadlineJira or another requirement trackerProduct or application engineering
Design alternatives and dependenciesShows judgment, such as the bracketDesign review tasks, meeting notes, emailDesign engineering lead
Orders released near the cut-inShows exposure to the old revisionERP order release historyProduction planning
Holds and inspectionsShows how the gap was caughtQuality management systemQuality manager
Disposition and costShows the outcome of the gapRework orders, scrap recordsPlant controller
Field resultShows whether the fix heldService or warranty systemService manager

Atlassian documents that Jira Cloud can export search results to CSV with all fields and each comment in its own column, and that exports run up to 10,000 work items at a time, so long requirement histories come out in batches. That makes the first row available in principle. But if the Jira issue does not carry CN-7720, or the change notice does not carry the issue key, the two exports sit side by side without a join.

Why the missing pieces matter to AI developers

AI developers evaluating business data look for sequences in which a decision, its reasons and its consequences can be followed. A change notice alone is a fact. The joined history is a worked problem: a constraint arrives, people choose between options, something slips, someone catches it, and the outcome is recorded. Background on that difference is in what data is missing from AI training and why AI agents need work data.

That does not mean every company with a PLM qualifies, or that SourceX has a buyer for any particular history. It means a partner who can tell the company where its context lives is giving the most useful kind of introduction.

Asking about context without seeing records

Partners never open drawings, BOMs or exports. Ask the engineering operations head or engineering systems lead, and note the answers:

  • Requirement side: Which tracker holds customer and regulatory requirements, since when, and does each change carry its key?
  • Order side: Does the ERP keep release dates and the BOM version used on closed orders?
  • Quality side: Do holds and rework orders cite the change number?
  • Service side: Can field reports be tied to the revision installed?
  • Ownership: Who owns each system, and who can authorize a licensing discussion? The CEO (in an owner-run company, usually the owner), not an administrator.
  • Unknowns: Customer-owned designs, export-controlled programs and personal data in email are for SourceX's rights review, not the partner.

The Jira metadata inventory template helps describe the tracker without exporting anything, and the metadata packet collects the answers into one page. If a PLM migration is under way, the PLM migration consultant guide covers how context is often lost at cutover. The company also 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.

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 you know keeps the requirement, order and quality context around its changes and can say where each piece lives, register as a partner, check the company against who qualifies, and read the program terms before you introduce its decision-maker.

  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

Is a Windchill export worthless without the other systems?

No. It is an accurate record of what changed and when. It simply cannot explain why, or what the change did to orders already in flight, without the neighboring systems.

Can the missing context be rebuilt from people's memories?

Not reliably for old changes. Memory can point to where context lives, such as a mailbox or a quality database, but the evidence has to come from records the company holds.

Who decides whether context outside the PLM can be included?

The company, through its CEO, and then SourceX's rights review. A partner only notes where the context lives.

Sources

  1. support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_…
  2. support.atlassian.com/jira/kb/how-to-export-issues-from-jira-cloud…
  3. support.atlassian.com/jira/kb/export-over-10-000-work-items-in-jir…
  4. help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a…
  5. 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