Engineering change exception, worked step by step: an order released between approval and effectivity

Short answer

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.

Visual briefFull-size diagram
A vertical case timeline from the February 3 requirement through board approval and a March 2 effectivity, branching at the February 27 order released with revision A seals into a quality hold, then splitting into 12 pumps reworked and 28 used as is, each step labeled with its record.
Illustrative case at a fictional pump maker. The branch is the order that slipped between approval and effectivity.

This worked case is part of engineering change order process records. 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.

DateDecisionDecided bySystemRecord left
Feb 3Accept the customer's higher temperature rating as a requirementApplications engineerJiraRequirement issue
Feb 10Change seal material to revision BDesign engineer, at design reviewJiraDesign review issue, linked to the requirement
Feb 12Approve the change on the full trackChange review boardWindchillChange request with board approval
Feb 17Set date effectivity for Mar 2 to use up revision A stockManufacturing engineerWindchillChange notice and tasks
Feb 27Release 40 pumps to keep the delivery dateProduction plannerERPProduction order stamped with the BOM in force
Mar 4Stop shipment after final test flags the old sealQuality engineerERP and quality moduleQuality hold
Mar 6Rework 12 pumps to revision B; use 28 as is for standard-temperature ordersMaterial review boardWindchill and ERPDisposition, rework order, reallocation
Mar 20Close the requirementApplications engineerJiraClosure 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 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 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 and to logistics exceptions and their 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 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.

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, check it against who qualifies and read the program terms before introducing 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

Why use a case where the process slipped?

Because a clean change has one decision and an exception has several, each made by a different person and recorded in a different system. That sequence of judgment is what makes the history useful as evidence of how work is really done.

Does the company have to admit a mistake to be introduced?

No. A partner asks whether cases like this exist and whether the records connect, at metadata level. Nobody describes a specific incident, customer or product in an introduction.

What if the company uses a PLM system other than Windchill?

The pattern is the same in any change management system: a request, an approval, an effectivity point and production orders that fall either side of it. Only the record names change.

Sources

  1. support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_…
  2. support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_…
  3. help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a…
  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