Engineering change impact review system map: the Jira, Windchill and ERP keys that join one change

Short answer

An engineering change impact review is reconstructed across systems by four identifiers, each held by a different owner. The Jira issue key goes into the PLM change request. The change number goes onto the new part and BOM revision with its effectivity. The PLM-to-ERP interface carries the change into an ERP BOM version, and the BOM version is stamped on each production order. The map below lists every system, the record it holds, the identifier it hands on, and the person who can describe that system.

Visual briefFull-size diagram
Six system nodes, Jira, PLM change, PLM structure, interface, ERP BOM and ERP orders, pass ENG-4471, CN-2291, revision B effective March 2 and version 11 along the path, with the interface-to-ERP link marked unconfirmed, and join into one change ending in 12 pumps reworked.
Illustrative map at a fictional pump maker. The interface link is the one most companies cannot yet confirm.

This map is part of engineering change order process records. The worked exception case tells the story of one change; this page is an inventory of the systems behind it, organized by owner.

The map: system, record, linking key and owner

Six nodes, in the order a change passes through them. Each row also records how far back the system usually goes, because coverage differs by node.

NodeRecord it holdsIdentifier handed onOwner who can describe itCoverage question
Jira (requirements)Requirement and design review issues with commentsIssue keyApplications or systems engineeringSince which year, and which projects?
PLM change managementProblem reports, change requests, board decisions, change notices, tasksChange numberEngineering operations, change analystSince go-live, or earlier history loaded too?
PLM product structurePart and BOM revisions with effectivityRevision with its cut-in date, lot or serialConfiguration managerAre past effectivities kept?
Interface or manual rekeyingMessages or hand-entered BOM changesChange number on the ERP changeIT integration teamIs the message log retained?
ERP bill of materialsBOM states with valid-from datesBOM versionManufacturing engineeringHow far back do BOM states go?
ERP shop floor and qualityProduction orders, holds, rework, dispositionsBOM version on the order, change number on reworkPlanning, quality managerDo closed orders keep these fields?

The owner column answers "who can explain this node", not "who can approve its use". Approval sits with the executive covered in who can license these records.

Node by node: what each owner can tell you

Jira owner. Whether the issue key is a required field on the PLM side, how projects are archived, and roughly how many requirement issues exist per year. Atlassian documents that Jira Cloud can export search results to CSV with all fields, so the requirement side is usually easy to describe in volume terms.

Change analyst. Which change tracks the company uses and how many change notices close each year. PTC's Windchill documentation describes the flow from optional problem reports through requests and notices to tasks, with a full track and review board for complex changes; other PLM platforms use similar objects under other names.

Configuration manager. Whether effectivity is set by date, lot or serial, and whether old effectivities survive once superseded. PTC treats effectivity as the point where production switches from old to new versions.

IT integration lead. The node most partners forget. Whether the interface passes the change number to the ERP, how long its logs live, and whether there were periods of manual rekeying.

Manufacturing engineering. How the ERP stores BOM history. In a standard SAP model, a BOM changed under a change number keeps a state ending at the valid-from date and another starting there, so the ERP can show what an order used, if history is retained.

Quality manager. Whether holds, rework and dispositions cite the change number, which is what ties outcomes back to the decision.

One change read across all six nodes (Illustrative)

Invented for this page. A fictional 520-person pump maker changes a seal material. Identifiers are made up. Each row is what that node's owner would see on screen.

NodeWhat the owner seesIdentifier valuesJoined to the previous node?
JiraCustomer temperature requirement and design review choosing seal revision BENG-4471Starting point
PLM change managementChange request approved by the board; change notice with tasksCR-2291, CN-2291, citing ENG-4471Yes, key typed by hand
PLM product structureSeal assembly revision B, date effectivity Mar 2Revision B under CN-2291Yes, in Windchill
InterfaceMessage sending the BOM change to the ERPCN-2291 in the payloadUnknown until IT checks the log
ERP bill of materialsNew BOM state valid from Mar 2BOM version 12Depends on the interface row
ERP shop floor and qualityOrder for 40 pumps released Feb 27 on version 11; hold; rework of 12Version 11 on the order; CN-2291 on the reworkYes, by quality policy

Read down the last column. Three of the five joins hold with confidence, and the other two hang on one interface log nobody has looked at. That is a normal and honest map. The preservation timeline explains why that interface log is often the first thing lost when a PLM system is replaced.

Gaps by owner: who to ask about each weak spot

Weak spotOwner to askPlain-language question
Requirement not cited on the changeChange analystCan a change be saved without the issue key?
Rekeyed BOM changesIT integration leadWere there months when BOM changes were typed in by hand?
Orders without BOM versionPlanningCan you tell which bill a closed order was built from?
Outcomes not tied backQuality managerDoes rework name the change that caused it?
History before the current PLMDocument controlWhere do changes from before go-live live?

What a partner notes at metadata level

The six node names, the owner of each, the years each covers, which identifiers the owners say are carried, and rough volumes in ranges. Never part numbers, drawings, BOMs, customer names or exports. The Jira metadata inventory template covers the requirements node, and the PLM migration consultant guide covers how integrators raise the topic. The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact, usually the CEO, COO or owner. 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 and export-controlled data stays out, and SourceX's data requirements are unknown until SourceX reviews it. Broader questions are answered in manufacturing data monetization and the systems hub.

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 name the owner of each node on this map and say which identifiers they carry, register as a partner, confirm the company on 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

Does the company need a PLM-to-ERP integration for the map to be useful?

No. Many manufacturers re-key BOM changes into the ERP by hand. That still works as a join if the change number is entered with it; what matters is whether the key survives, not how it got there.

Can a partner ask for a sample export to confirm a join?

No. A partner records what the company's systems lead says about each key. Exports, part numbers and BOMs stay inside the company until it applies and a rights review approves any use.

What if requirements are tracked in email, not Jira?

Then the first key on the map is weak or missing. Note it as a gap; the rest of the map can still hold, and SourceX decides fit after its own review.

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. support.atlassian.com/jira/kb/how-to-export-issues-from-jira-cloud…
  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