# Engineering change system map: Jira, PLM, ERP | SourceX

Canonical: https://refer.sourcex.si/guides/engineering-change-impact-review-records-across-systems
Last updated: 2026-11-04

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.

This map is part of [engineering change order process records](/data-types/engineering-change-order-process). The [worked exception case](/guides/engineering-change-impact-review-exception-examples) 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.

| Node | Record it holds | Identifier handed on | Owner who can describe it | Coverage question |
|---|---|---|---|---|
| Jira (requirements) | Requirement and design review issues with comments | Issue key | Applications or systems engineering | Since which year, and which projects? |
| PLM change management | Problem reports, change requests, board decisions, change notices, tasks | Change number | Engineering operations, change analyst | Since go-live, or earlier history loaded too? |
| PLM product structure | Part and BOM revisions with effectivity | Revision with its cut-in date, lot or serial | Configuration manager | Are past effectivities kept? |
| Interface or manual rekeying | Messages or hand-entered BOM changes | Change number on the ERP change | IT integration team | Is the message log retained? |
| ERP bill of materials | BOM states with valid-from dates | BOM version | Manufacturing engineering | How far back do BOM states go? |
| ERP shop floor and quality | Production orders, holds, rework, dispositions | BOM version on the order, change number on rework | Planning, quality manager | Do 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](/questions/who-can-license-engineering-change-impact-review-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.

| Node | What the owner sees | Identifier values | Joined to the previous node? |
|---|---|---|---|
| Jira | Customer temperature requirement and design review choosing seal revision B | ENG-4471 | Starting point |
| PLM change management | Change request approved by the board; change notice with tasks | CR-2291, CN-2291, citing ENG-4471 | Yes, key typed by hand |
| PLM product structure | Seal assembly revision B, date effectivity Mar 2 | Revision B under CN-2291 | Yes, in Windchill |
| Interface | Message sending the BOM change to the ERP | CN-2291 in the payload | Unknown until IT checks the log |
| ERP bill of materials | New BOM state valid from Mar 2 | BOM version 12 | Depends on the interface row |
| ERP shop floor and quality | Order for 40 pumps released Feb 27 on version 11; hold; rework of 12 | Version 11 on the order; CN-2291 on the rework | Yes, 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](/guides/preserve-engineering-change-impact-review-records) 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 spot | Owner to ask | Plain-language question |
|---|---|---|
| Requirement not cited on the change | Change analyst | Can a change be saved without the issue key? |
| Rekeyed BOM changes | IT integration lead | Were there months when BOM changes were typed in by hand? |
| Orders without BOM version | Planning | Can you tell which bill a closed order was built from? |
| Outcomes not tied back | Quality manager | Does rework name the change that caused it? |
| History before the current PLM | Document control | Where 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](/resources/a-metadata-only-jira-inventory-template-for-company-introductions) covers the requirements node, and the [PLM migration consultant guide](/guides/plm-migration-consultant) 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](/questions/manufacturing-data-monetization-ai) and the [systems hub](/systems).

## 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](/register), confirm the company on [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://support.atlassian.com/jira/kb/how-to-export-issues-from-jira-cloud-in-csv-format/
- https://refer.sourcex.si/terms
