# Engineering change export: missing context | SourceX

Canonical: https://refer.sourcex.si/guides/engineering-change-to-effectivity-missing-context
Last updated: 2026-11-04

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.

This before-and-after reading is part of the guide on [engineering change order process records](/data-types/engineering-change-order-process). The [record chain page](/guides/engineering-change-to-effectivity-record-linkage) 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 export | Value |
|---|---|
| Change notice | CN-7720, approved Sep 9 |
| Affected item | Fan motor assembly, revision D to revision E |
| Effectivity | Lot effectivity from lot 2291 |
| Change tasks | Update 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:

| Date | Source | What it adds |
|---|---|---|
| Jul 22 | Jira requirement | A utility rebate program requires a minimum fan efficiency for units shipped to one region from Oct 1 |
| Aug 4 | Jira design review | Revision E chosen; the motor mount needs a new bracket, which the CN does not mention |
| Sep 9 | Windchill | CN-7720 approved, effectivity from lot 2291 |
| Sep 11 | ERP | Lot 2288 released against the old BOM; ERP BOM valid-from date keyed Sep 16 |
| Sep 30 | Quality | Hold on 18 units from lot 2288 bound for the rebate region |
| Oct 3 | ERP | 18 units retrofitted with revision E motors and brackets; rework order cites CN-7720 |
| Nov 14 | Service | First 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 context | Why a reviewer needs it | Where it usually lives | Who can describe it |
|---|---|---|---|
| The triggering requirement | Shows the business reason and deadline | Jira or another requirement tracker | Product or application engineering |
| Design alternatives and dependencies | Shows judgment, such as the bracket | Design review tasks, meeting notes, email | Design engineering lead |
| Orders released near the cut-in | Shows exposure to the old revision | ERP order release history | Production planning |
| Holds and inspections | Shows how the gap was caught | Quality management system | Quality manager |
| Disposition and cost | Shows the outcome of the gap | Rework orders, scrap records | Plant controller |
| Field result | Shows whether the fix held | Service or warranty system | Service 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](/questions/what-data-is-missing-from-ai-training) and [why AI agents need work data](/proof/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](/resources/a-metadata-only-jira-inventory-template-for-company-introductions) helps describe the tracker without exporting anything, and the [metadata packet](/resources/engineering-change-to-effectivity-metadata-packet) collects the answers into one page. If a PLM migration is under way, the [PLM migration consultant guide](/guides/plm-migration-consultant) 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](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce its decision-maker.

## Sources

- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/ChgMgmtEffectivityAbout.html
- https://support.atlassian.com/jira/kb/how-to-export-issues-from-jira-cloud-in-csv-format/
- https://support.atlassian.com/jira/kb/export-over-10-000-work-items-in-jira-cloud/
- https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a7738186eebceaa7/5e07c453f57eb44ce10000000a174cb4.html
- https://refer.sourcex.si/terms
