# Engineering change exception: a worked hard case | SourceX

Canonical: https://refer.sourcex.si/guides/engineering-change-impact-review-exception-examples
Last updated: 2026-11-04

The records that explain an engineering change exception link the problem, each decision and the checked result. Here that means the requirement that started the change, the design review choice and the board-approved change request. It also means the change notice with its effectivity date, the production order released before that date, the quality hold that caught it and the disposition that closed the gap. In the Illustrative case below, an order slipped between approval and effectivity, and every decision that followed left a dated record.

This worked case is part of [engineering change order process records](/data-types/engineering-change-order-process). That page describes the ECR, ECO and ECN records. This one follows a single hard case from first requirement to closure, then shows how to spot similar cases at a client.

## What went wrong

Illustrative and invented for this page. A fictional 520-person maker of industrial pumps tracks requirements in Jira, runs change management in PTC Windchill and builds in its ERP.

A customer that pumps hot process fluid raises its required seal temperature rating. Engineering picks a new seal material, revision B, and the change review board approves the change. The change notice sets date effectivity for the seal assembly at March 2. PTC describes effectivity as the planned date, lot or serial number at which old versions are replaced by new ones in production, and planned effectivities on a change notice become actual when the notice is approved.

On February 27, three days before the cut-in, planning releases a production order for 40 pumps. The ERP explodes the bill of materials as it stood that day, with revision A seals. Nothing is broken in any one system: the change is approved, the effectivity is correct and the order is valid. The problem sits between them. The order was released for a customer who needed the new seal, before the new seal was effective.

## Step by step: who decided what

Each row is one decision, the person who made it and the system that recorded it.

| Date | Decision | Decided by | System | Record left |
|---|---|---|---|---|
| Feb 3 | Accept the customer's higher temperature rating as a requirement | Applications engineer | Jira | Requirement issue |
| Feb 10 | Change seal material to revision B | Design engineer, at design review | Jira | Design review issue, linked to the requirement |
| Feb 12 | Approve the change on the full track | Change review board | Windchill | Change request with board approval |
| Feb 17 | Set date effectivity for Mar 2 to use up revision A stock | Manufacturing engineer | Windchill | Change notice and tasks |
| Feb 27 | Release 40 pumps to keep the delivery date | Production planner | ERP | Production order stamped with the BOM in force |
| Mar 4 | Stop shipment after final test flags the old seal | Quality engineer | ERP and quality module | Quality hold |
| Mar 6 | Rework 12 pumps to revision B; use 28 as is for standard-temperature orders | Material review board | Windchill and ERP | Disposition, rework order, reallocation |
| Mar 20 | Close the requirement | Applications engineer | Jira | Closure linked to the change and the rework |

Two decisions carry the exception. The manufacturing engineer chose a later effectivity date to consume existing stock, a reasonable cost decision. The planner released an order before that date, a reasonable schedule decision. Only together did they put old seals into pumps for the one customer who could not take them.

## The records that captured each decision

A reviewer needs four kinds of record to follow the case, and each comes from a different place.

- **Why:** the Jira requirement and design review, which hold the customer's need and the engineering choice. PTC documents that Windchill change management runs from optional problem reports through change requests and change notices to change tasks, but the reason for a change often lives upstream in the requirements tool.
- **What and when:** the Windchill change request, board approval and change notice with its effectivity date.
- **What was built:** the ERP production order and the BOM state it used. SAP documents that in its standard model a change's effectivity depends on its valid-from date, with the BOM stored as a pre-change state ending at that date and a post-change state starting there, so an order released before the date picks up the old state. Other ERPs differ.
- **What was done about it:** the quality hold, the disposition and the rework order, ideally each citing the change number.

If any of the four is missing, the case stops making sense. Without the production order, the hold looks random; without the effectivity date, the release looks like an error rather than a timing gap. The [system map](/guides/engineering-change-impact-review-records-across-systems) shows the keys that join them.

## Why this sequence is useful evidence

Clean changes teach one rule: approve, set effectivity, build. This case shows how people handled a gap the rule did not cover. It has a trade-off between stock and schedule, an order caught by a test, a split disposition and a closure that links back to the start. Each judgment can be checked against a dated record made by the person responsible.

That is the kind of history AI developers describe needing when they need examples of real work rather than idealized procedures; [why AI agents need work data](/proof/ai-agents-need-work-data) explains the demand in general terms. It does not mean any buyer wants a given company's records. That is decided only after SourceX's review. The same reasoning applies to [QA and QC records](/data-types/engineering-qa-qc-process) and to [logistics exceptions and their resolutions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions).

## Recognizing similar cases at a client

PLM integrators see the signs of these cases during ordinary project work. Without opening a record, ask the head of engineering operations:

- **Do changes often use date effectivity set days or weeks after approval?** The gap is where orders slip.
- **Does the production order keep the BOM version it was built with?** If it only links to the current item, the case cannot be reconstructed.
- **Do quality holds and rework orders cite the change number?**
- **Do requirement issues get closed with links to the change and its outcome?**
- **Roughly how many changes a year touch open orders?** A range is enough.

Then ask who can authorize a licensing discussion, which is the CEO (in an owner-run company, usually the owner); the [who-can-license decision tree](/questions/who-can-license-engineering-change-impact-review-records) maps that path. The company needs 50+ full-time employees at peak (contractors excluded), 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. Customer-owned designs and export-controlled data stay out, and what remains licensable is unknown until SourceX's rights review. For a broader method, see [how to assess engineering issue histories](/guides/how-to-assess-engineering-issue-histories-and-review-decisions).

## 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 work with can follow a case like this from requirement to disposition, [register as a partner](/register), check it against [who qualifies](/who-qualifies) and read the [program terms](/terms) before introducing its decision-maker.

## Sources

- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/CCMOviewChangeMgmtIntro.html
- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/ChgMgmtEffectivityAbout.html
- https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a7738186eebceaa7/5e07c453f57eb44ce10000000a174cb4.html
- https://refer.sourcex.si/terms
