An engineering change order, an ECO, is the record that alters a design, its bill of materials (BOM) and everything built from it.
At 09:10 the product engineer moves a change request on controller board 7741-X into impact analysis: a voltage regulator is replaced by a pin-compatible part from Acme Components GmbH. Juno reads the where-used across SAP S/4HANA and the Oracle Fusion division, where the same board carries a different item number, and finds 14 assemblies at three plants.
It also finds 2,150 units of the old regulator in stock at plant 1210, six open purchase order lines with Acme Components GmbH worth $86,000, and two sales orders whose delivery dates fall inside the use-up. The draft proposes an effectivity date after use-up, seven weeks out, and two order changes for the buyer.
P. Sharma, master-data steward, approves the affected-item list at 10:20 after moving one assembly the draft had placed at the wrong plant. D. Okafor approves the two order changes. The change board on Thursday sees one page, with the query on show and each figure traced to its system. showcase estate
The PLM and ERP vendors now ship change agents, and each works inside its own system. Siemens introduced a Teamcenter AI BOM agent that finds impacted assemblies, evaluates alternatives and executes updates across occurrences, with a person confirming each update (Siemens, 23 June 2026) 1; Teamcenter 2606 adds recommendations for change workflow templates and task assignment (Siemens, 12 June 2026) 2.
SAP’s Joule Change Record Management Agent analyses problem reports and change requests, recommends next steps and initiates changes, planned for the second quarter of 2026; SAP claims up to 20% less time creating change requests, a vendor figure (SAP, 7 October 2025; SAP, January 2026) 3, 4. Oracle’s Component Replacement Assistant reads part numbers from change notices, runs where-used across every impacted structure and adds use-up analysis to the change request (Oracle, 30 July 2026) 6. PTC’s Arena AI Engine compares files across revisions (PTC, 9 December 2025) 10, and Dassault Systèmes’ Aura companion orchestrates requirements, projects and changes (Dassault Systèmes, 11 February 2026) 20.
The pain is measured across thousands of companies. The median engineering change order takes 7.0 days from request to production across 4,075 companies, and change orders take a median 10% of new product development cost across 325 companies (APQC, checked 23 September 2026) 28, 29. 90% of engineering leaders delay launches because of late design changes, and 10% launch every product on time (CoLab, 26 July 2024) 30; 70% of chip respins trace to specification changes (Semiconductor Engineering, 27 March 2025) 31.
The gap the vendors’ agents leave is the one Juno is built for. Each agent sees one system, and a change touches PLM, two ERPs, the planning suite, the supplier portal and the quality system at once. 400 senior manufacturing professionals ranked PLM the top system for agents to reach and named change histories among the data agents need (ASSEMBLY, 25 August 2026) 15. Gartner expects PLM AI to evolve into agent-driven capabilities that automate cross-functional workflows, as quoted by one vendor (PTC Arena, 11 August 2026) 18.
The engineer raises a change request in the PLM system. A change analyst runs where-used in PLM and again in each ERP, because bills of materials differ by plant, and pastes the results into a spreadsheet. A planner checks stock, open purchase orders, planned orders and work in progress for each affected part at each plant.
A buyer e-mails suppliers and contract manufacturers about open orders and tooling. Quality checks the qualification status of any alternate. Finance estimates scrap and rework. The change board meets weekly and approves the change with an effectivity date, and the master-data steward updates the ERP change master, BOM validity and routing. Eight people, five systems and a median of 7.0 days per change (APQC, checked 23 September 2026) 28.
Change request, affected item, bill of materials, where-used, effectivity, stock, purchase order line and sales order line are objects the supply chain ontology already holds, so this use case starts from the map the rest of the site describes. The six stages below say what would be registered, asked, taught and written back, and who would approve each draft.
The market runs this at draft-and-approve: the PLM and ERP vendors’ change agents analyse, recommend and initiate, and a person confirms each BOM or record update (2025 to 2026) 1, 3, 6. The blueprint designs the write-back roles here at A2 as well, with the change analyst as the named approver: ECO tracking and propagation, product change notice issuance and spec baseline control at A2, and the two impact assessment roles at A3, because an assessment reads and a propagation writes.
| Element | Setting | Set by | Changes |
|---|---|---|---|
| Objective | Every change request reaches the change board with its full impact across PLM, both ERPs, the planning suite and the supplier portal, and a drafted effectivity date | The engineering change manager, in a sentence | New version |
| Data scope | PLM change and BOM tables; SAP S/4HANA and Oracle Fusion BOM, change master, stock, purchasing and sales; planned orders; supplier confirmations; qualification records | A. Novak, data lead | New version |
| Rules | The impact policy and its planning table: list what the change touches; effectivity after use-up where stock covers demand; draft order changes under $25,000 | The change manager with the Planner Agent | New version, simulated first |
| Trigger | When a change request enters impact analysis; when a PCN arrives; a daily scan at 07:00 for open changes with impact data missing | The change manager | At once |
| Actions permitted | Attach the impact report · write the affected-item list and effectivity proposal · draft a purchase order change · set a use-up flag · notify a supplier · draft a PCN | The change manager, owner | New version |
| Limits | Order changes above $25,000 go to the buyer with the reason · 40 drafts a day · confidence floor 0.85 on a where-used match · a routing change always waits for the steward | The change manager and J. Harrison, finance | New version |
| Escalation | A change with an alternate, to the quality engineer · a change touching a product in ramp, to the programme manager at once · a failed write-back, to the owner | The change manager | At once |
| Level | A2 Supervised with the change analyst as the named approver; D. Okafor approves order changes; the change board decides | The engineering director | Up on evidence, down in one step |
| Feedback | Every edited date, moved assembly and rejected draft is recorded and used | Always on | Fixed |
Every row is a setting or a versioned rule; the level and the limits are the ones a manager signs.
Lima’s agent blueprint is a design of 960 agent roles across five end-to-end chains. It is the map of what Juno can be configured to do, and the first agents are built from it one at a time, the way the PO cancellation agent was.
Additional capability in Idea-to-Market lists the rest of the map for this chain.
| Measure |
|---|
| Change order cycle time, baseline 7.0 days median (APQC) |
| Change order cost share of new product development cost, baseline 10% median (APQC) |
| Hours of impact analysis per change |
| Share of changes with complete impact data before the change board |
| Open-order and stock exposure per change, in currency |
| Launches delayed by late design changes, baseline 90% of companies report delays (CoLab, 2024) |
| Time to create a change request, vendor claim of up to 20% less (SAP, 2026) |
Baseline the share of changes with complete impact data before the change board first. It is a count the board secretary can take from the last quarter’s minutes, it is the number the board feels, and it moves in the first month. Change order cycle time follows, against APQC’s 7.0-day median 28; the cost share moves over a year of programmes, so it is read per programme.
The PLM system holds the engineering bill of materials, and each ERP holds its own manufacturing bill per plant with its own item numbers. Juno maps all three to one bill-of-materials object, so one query reads them together.
The change analyst confirms the affected-item list and the date. D. Okafor approves order changes above $25,000. The change board approves the change. P. Sharma approves the master-data update. Each approval is recorded by name.
The impact report and the affected-item list to PLM, which returns the revision; order changes and the use-up flag to the ERP, which returns the change number and the material status; the supplier notice through the portal, which records the acknowledgement.
This change was the company’s own decision. What happens when the change comes from outside: a supplier ends a part that sits on nine active bills of materials?
Every end-of-life notice caught, the exposure and the last-time buy sized, and a qualified alternate proposed while the last order date is still open.
Bring two systems and one decision your planners make every week. In the first week we register the data, confirm the mapping with your team, answer your questions in ChatLima and run the first agent at the level you choose.