Home · Solutions · Operations & quality
Solution · Operations & qualityOne released change, every BOM, routing, plant and supplier updated, with proof
Engineering changes propagated to ERP, plants and suppliers
An ECN released in the PLM starts an orchestrated flow that updates SAP, collects plant sign-offs, notifies suppliers and closes only when every step has evidence.
Executive summary
Stop losing engineering changes between the PLM, the ERP, three plants and forty suppliers.
The change flow itself becomes software: an executable process in UiPath Maestro.
Bills of materials and routings in all three plants carry the new revision on the day of release, with one effectivity date.
SAP S/4HANA (change master, BOM, routing, material master); SharePoint drawing library and change register; PLM implementation status
Business problem
Engineering change management
An engineering change is approved once, in the PLM, and then has to happen in half a dozen other places: the change master, bills of materials and routings in SAP for every plant that builds the part, the material revision level, the records of every supplier that makes it. The PLM workflow ends at release. Everything after that is coordination.
Coordination means a change coordinator, plant master-data specialists, buyers and quality engineers exchanging emails around a tracker that is accurate on the day it is updated. Each participant works in their own order and at their own pace, and the effectivity date in the PLM is a wish rather than an instruction.
At scale the failure is quiet. With 180 changes a month, one missed plant or one unread supplier email a week is statistically certain. The consequences arrive later as obsolete stock, rework, express freight and a difficult call with the customer, and none of them are booked against the change process.
How it works today
- PersonThe change coordinator exports the released ECN from the PLM, adds a row to the Excel tracker and emails the package to the plant, purchasing and quality lists
- PersonMaster-data specialists in each plant update the change master (CC02), the bill of materials (CS02) and the routing (CA02) by hand, each in their own order and time
- WaitingSuppliers receive the new drawing as an attachment; whether anyone read it is unknown until the next delivery or the next PPAP question
- PersonA buyer checks stock, open orders and scheduling agreement lines in SAP when asked; use-up, rework and scrap decisions live in email threads
- Risk of errorOne plant updates the BOM after the effectivity date, or not at all, and production builds to the old revision
- WaitingSign-offs are collected in a Teams chat and at the Friday change meeting; the tracker is updated afterwards from memory
- Risk of errorAt the customer audit, the evidence that the change reached every plant and supplier is reconstructed from mailboxes
Why the current process costs more than it appears
The cost grows where nobody is looking.
- Three and a half hours of coordination per change is the countable part: exporting, distributing, entering data three times, checking stock, emailing and chasing suppliers, updating the tracker. Uncountable is everyone who asks "has this been done?" in Teams.
- Building to a superseded revision is the expensive failure: rework or scrap, obsolete purchased parts, express freight to the customer. Each incident is a one-off, so nobody adds them up.
- Suppliers who never confirmed a drawing keep producing the old part until receiving inspection or a line stop reveals it. Chasing acknowledgements is nobody's job.
- Every plant keeps its own version of the truth: a local tracker, a local convention for effectivity, a local person who knows which changes are open.
- Audit exposure grows quietly: automotive customers and IATF 16949 auditors ask for evidence of change control, and a process run on email produces it only after an investigation.
Cost of inaction
Every new plant, product line and supplier lands on the same coordinator; the usual answer is a second one who inherits the same tracker. The third row is a deliberately modest illustration: four escaped changes a year at €30,000 each for obsolete purchased stock, rework of units built to the old revision and express freight. The real figure depends on part value and detection time; a wrong-revision delivery reaching the customer is outside this model and far more expensive.
Evidence does not improve by itself either: every audit and escalation means reconstructing who was told what and when, by the one coordinator the company cannot lose.
A plausible organisation with realistic proportions. The figures are there to be recalculated on your data; they are not a client result.
A European automotive tier-1 supplier: three plants, around 3,200 employees, a PLM system for design data, SAP S/4HANA with Engineering Change Management, Microsoft 365 E3. Illustrative, not a client.
180 engineering change notices a month; roughly 70% touch more than one plant and 40% affect purchased parts from about 40 active suppliers.
The coordinator distributes the package by email, plant specialists enter the changes in SAP, buyers notify suppliers with attachments, sign-offs are gathered in a Teams chat and a weekly meeting; an Excel tracker holds the status.
About 210 minutes of coordination per change, spread over one to two weeks, with no reliable view of which plant or supplier has not yet acted.
A UiPath Maestro process per released change: robots update SAP for every affected plant with one effectivity date, compile the stock and open-order impact report and send suppliers a SharePoint link to the new drawing; sign-offs are Action Center tasks in Teams; timers chase overdue steps.
In the modelled case SAP is consistent across the three plants on the day of release, every supplier notice has a recorded acknowledgement or an escalation, and coordination per change falls from 210 minutes to the 30 to 45 minutes spent on decisions. The figures are a model, not a measurement.
Proposed solution
The change flow itself becomes software: an executable process in UiPath Maestro. The model is a BPMN diagram your change coordinator can read: a start event for the PLM release, service tasks for the robots that update SAP, user tasks for the people who must confirm, timers for deadlines, and an end event reached only when every branch is complete. Each ECN is one instance with its own timeline, so "where is change 26-0417?" has an answer.
The robots do the data work that today is repeated in every plant: change master, bills of materials, routings and material revision levels in SAP, through BAPI where one exists and SAP GUI activities where it does not, with the effectivity date the PLM specified. Before that date they query stock, open orders and production orders for every affected part and plant and attach the impact report. A DMN decision table derives the required sign-offs from the change class, so a documentation-only change does not wake up three plants.
People keep the decisions, as tasks in UiPath Action Center completed from Microsoft Teams: plant readiness, disposition of affected stock and orders, first-article or PPAP requirements for suppliers. Suppliers receive an email with a SharePoint link to the released revision, restricted to their registered contacts, and acknowledge by reply; the flow matches the reply and chases after three working days. No AI is involved; the process is deterministic, and it should be.
UiPath Maestro BPMN (service, user and business rule tasks, timer events, Instance Management, Process Intelligence); UiPath Orchestrator queues, API triggers and audit; UiPath Action Center tasks completed in Microsoft Teams; UiPath Integration Service connectors for SAP BAPI, Microsoft Outlook 365, Microsoft Teams and Microsoft OneDrive & SharePoint; SharePoint versioning, metadata and sharing links
The BPMN model and decision tables, the SAP robots, the impact report, supplier notification and acknowledgement matching, escalation rules, the change register, the PLM integration and the runbook
PLM release event, change package and status write-back through the PLM's API or release export (no vendor assumed); SAP steps without a suitable BAPI through UiPath SAP GUI activities
How the automated process works
- AutomationA released ECN in the PLM starts one Maestro instance, keyed by the change number, carrying affected parts, plants, suppliers and the effectivity date
- SystemA robot files the drawings in a SharePoint library with change, part and revision metadata; a decision table sets the required sign-offs
- SystemRobots update change master, BOMs, routings and material revisions in SAP for every affected plant with the same effectivity date and attach the SAP change documents
- AutomationA robot compiles the impact report (stock per plant, open orders and scheduling agreement lines per supplier, open production orders) and posts it to the plant and purchasing channels in Teams
- PersonPlant engineers, buyers and quality complete their sign-off tasks in Action Center from Teams: readiness confirmed, disposition chosen, first-article requirement set
- AutomationSuppliers of affected parts receive the notice with a SharePoint link to the released revision; replies are matched and recorded, reminders follow after three working days, then the buyer is brought in
- WaitingTimers watch the effectivity date; anything still open two working days before it is escalated to the plant manager or the purchasing lead
- AutomationWhen SAP updates, sign-offs and acknowledgements are complete, the record is closed on SharePoint and the PLM status is set to implemented
Human-in-the-loop model
Automation handles
- One process instance and one timeline per released change
- All SAP data entry across plants: change master, BOM, routing and material revision with effectivity dates
- The impact report, supplier notifications, acknowledgement matching, reminders and escalations
- The change record, the PLM status write-back and the dashboards
People decide
- Readiness of each plant: tooling, work instructions and whether the effectivity date can be held
- Disposition of affected stock and open orders: use up, rework, scrap or cancel
- Whether a supplier must resubmit a first article or PPAP before the new revision ships
- Changes to the decision tables and escalation rules, owned by engineering and quality
Before and after
Systems and integrations
Every entry can be checked in vendor documentation. The evidence class is stated next to each one.
Inputs
- ECN release event and change package from the PLM (API or release export)
- SAP BOMs, routings, stock, purchase and production orders
- supplier contact master
Automation layer
- UiPath Maestro
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- UiPath Action Center
Target systems
- SAP S/4HANA (change master, BOM, routing, material master)
- SharePoint drawing library and change register
- PLM implementation status
Human touchpoints: Action Center sign-off tasks in Microsoft Teams; Teams channel posts for impact reports and escalations; supplier notices and acknowledgements by email
Technologies used
one instance per change: service and user tasks, DMN decision tables, timer escalations, Instance Management, Process Intelligence dashboards
Achange master, BOM, routing and material revision updates in SAP; stock and order queries; queues, retries, audit
Aplant, purchasing and quality sign-offs with owners and due dates, completed from Teams
ASAP calls; supplier emails and replies; channel alerts; drawing library and register
Aversion-controlled drawing library with metadata; per-supplier sharing links; change register
Aimpact reports and escalations in plant and purchasing channels; Action Center tasks
Atarget for change data with effectivity; source of stock, order and production impact
Asource of the released change, drawings and revisions; receives the implementation status
CIllustrative economic model
The arithmetic is open, so it can be argued with.
The 210 minutes per change is a sum, not a stopwatch reading at a client: coordinator, plant, purchasing and quality time for distribution, three SAP entries, stock and order checks, supplier emails and chasing, tracker updates, sign-off collection. The ranges are illustrative ones from multi-plant manufacturers. €40 is a blended fully loaded hourly cost for engineering, master-data and purchasing roles in Central Europe. We model capacity released; how it is used is your call.
Run the numbers on your data
An illustrative estimate from your own inputs. It models released capacity; it is not a promise of savings.
Business benefits
- Bills of materials and routings in all three plants carry the new revision on the day of release, with one effectivity date, entered once by a robot instead of three times by hand
- Every supplier of an affected part receives the released drawing the same day; acknowledgements are recorded and unanswered notices are chased automatically
- Affected stock and open orders are listed before the effectivity date, so use-up, rework and cancellation are decided in time, not discovered at receiving inspection
- Sign-offs are tasks with an owner and a deadline; a change cannot close while one plant has not confirmed
- In the modelled case, 630 hours a month of coordination return to work that needs judgement
- One record per change for the customer audit: what changed, where, by whom, when, against which revision
The management view
- Every open change is visible by stage, plant and age on the Process Intelligence dashboard; the bottleneck plant or supplier is named, not guessed
- Effectivity dates become commitments the process enforces; escalation follows the rule, not the loudest email
- Adding a plant, a supplier group or a change class is an edit to the decision table, not a new coordination habit
- The process is documented in the executable model itself, not in the coordinator's head
Board-level KPIs
Security and governance
Control is not an add-on.
- Every update lands in Orchestrator logs and SAP change documents, written by robots on their own SAP accounts, limited to the change, BOM, routing and material master transactions they need
- Drawings reach suppliers as SharePoint links restricted to named external contacts, with expiry; no drawing leaves the tenant as an attachment, and access ends when a supplier is replaced
- Segregation of duties is built into the model: the engineer who releases in the PLM cannot give the plant sign-off, and disposition is a separate task with its own owner
- The process runs in the UiPath Automation Cloud EU region; drawings, register and sign-off history stay in your Microsoft 365 tenant within the EU Data Boundary
- SAP and PLM secrets sit in Orchestrator's credential store backed by Azure Key Vault, invisible to the people who operate the process
Why now
Product programmes change faster than plant structures: platform updates, material substitutions and electrification variants push change volumes up while the method stays the tracker and the distribution list
In the modelled case the current method consumes €25,200 of coordination capacity a month before a single escaped change is counted
The building blocks are standard, not custom: Maestro BPMN with user tasks completed in Teams, timer escalation and Instance Management, and SAP BAPI connectivity through Integration Service, all generally available on UiPath Automation Cloud
Relevant executive roles
Plants build the released revision from the effectivity date; a missed plant becomes an escalation before production, not a discovery after it
Released changes are actually implemented, and engineering time stops going into chasing plants and suppliers
Suppliers are notified and acknowledgements recorded on the day of release; obsolete purchased stock is decided, not discovered
Change control evidence exists per change, complete and time-stamped, before the customer or the auditor asks
Common questions and objections
It should keep it. This flow begins where the PLM workflow ends, at release: the PLM stays the authority on what changed; the Maestro process makes the ERP, plants and suppliers act on it and keeps the evidence.
The robots use it. They add one pass with one effectivity date across every plant, and the process orchestrates the confirmations and supplier acknowledgements that SAP does not track.
They do not have to. They receive an email with a link to the released drawing and confirm by replying; the flow records the reply, chases when it does not arrive and escalates to the buyer.
When this is not the right solution
- A single plant with a few dozen changes a month and a handful of suppliers, where a disciplined PLM workflow and a SharePoint list are enough
- Changes are not released through the PLM reliably, or BOM and routing ownership per plant is undefined; the process needs fixing before it is orchestrated
- Part numbers and revision conventions differ between plants for the same item; master-data alignment comes first
A question for the next management meeting
For the last ten engineering changes, can we show within an hour which plants and suppliers implemented them, when, and how much stock was built or bought to the superseded revision?
Implementation approach
Delivery runs in stages, so it can be stopped at any point.
We deliver
- A walk-through of one quarter of your ECNs with the change coordinator: change classes, plants and suppliers affected, effectivity practice, where changes stalled
- The Maestro process model: service and user tasks, decision tables for required sign-offs, timers and escalation paths
- Robots for SAP: change master, BOM, routing and material revision updates with effectivity, plus the impact queries
- The PLM integration: release event, change package retrieval and status write-back
- Supplier notification: drawing library and sharing links, email templates, acknowledgement matching and reminders
- The change register, dashboards, the coordinator's runbook and hypercare
We need from you
- One quarter of ECN history with the corresponding SAP change documents and supplier notifications
- A change process owner plus one BOM and routing owner per plant
- Access to the PLM's API or release export, and technical SAP accounts for test and production
- The supplier contact master and the current escalation matrix
Stages
Discovery
ECN sample, plant and supplier map, effectivity practice, exception categories, volumes
Design
BPMN model, decision tables, SAP update rules, notification content, security model
Build
Robots, Maestro process, PLM and SAP integrations, SharePoint library and register, Teams touchpoints
Validation
Replay of historical changes in the SAP test system, sign-off rehearsal with the plants, supplier pilot
Go-live
One change class or product family first, supervised, then all classes and plants
Optimisation
Dashboard review, escalation tuning, extension to further plants or the customer notification step
Enterprise. Effort is driven by the number of plants and company codes, the PLM's interface, the share of changes touching purchased parts and how consistently effectivity dates and revision levels are used today.
ECN 26-0417 left the PLM on Tuesday and reached the supplier after the weekend.
Send us one quarter of your ECN log: change numbers, affected plants, release and effectivity dates, supplier notifications sent. We return a written assessment of where changes stall and a first estimate of the coordination hours that can be released.
Walk us through one changeThe neighbouring process usually has the same problem
Stop learning that a launch has slipped from the carton supplier's delivery note.
View solution Supply chainProduct and price master data published to every channelStop retyping every new product and price change into the ERP, the PIM, the web shop and each marketplace.
View solution Supply chainOrder confirmations and delivery dates chased automaticallyBuyers spend their mornings chasing suppliers for dates, and planners plan on dates that are already wrong.
View solutionIndustries we deliver this in most oftenManufacturing & industry