Skip to content

Follow an approved change into every record that still shows the old revision

An ECN can be approved while a supplier still builds to revision B and the line still works from the old instruction. Duvo finds the open orders, item records and documents the change touches, and follows each owner's update until the record matches.

Book a process call

Engineering change coordination

Change-owner decision needed

EC-401 · Bracket revision

Revision status
Mismatch
Affected record
PO-71 still references revision B
Boundary
Buyer update under approved effectivity

Change CN-41 approves revision C, but purchase order PO-71 retains revision B. The buyer needs the approved effectivity before updating the order.

Next action

Route buyer update: send the approved request and keep it open until the buyer confirms the order now shows revision C.

Return for clarification: pause the update and ask the change owner to resolve effectivity; no item revision or production release changes.

Coordinator releases every request

No update request reaches a buyer, supplier or document owner until the change coordinator approves it against the approved change.

View the wider product queue

Engineering change coordination

An approved engineering change followed through BOMs, routings and open orders.

Adds cases
Approved change notices
Processes cases
Revision handoffs
Total

24

Pending

5

Postponed

2

In progress

4

Needs input

3

Failed

0

Completed

10

Add filter
Case
Case Status
Handoff gap
Scope
Decision
Exceptions
Next action
EC-401 · Bracket revision
Needs Input
Old revision on order
Purchase order PO-71
Request buyer update
1
EC-402 · Housing drawing
In Progress
Document owner missing
Plant instruction WI-42
Assign owner
0
EC-403 · Label artwork
Completed
Destination updated
Item record IT-43
Record completion
0
EC-404 · Fastener reference
Pending
Effectivity unclear
Change notice CN-44
Ask change owner
1
EC-405 · Packing instruction
Postponed
Plant response pending
Document WI-45
Await acknowledgement
0

Showing 5 of 24 cases

  1. 1

    Approval

    Exceptions pause for the named owner

    Each exception carries the source records, applied rule, recommended action, and the person authorised to decide.

  2. 2

    Handoff gap

    Handoff gap is visible before the action

    The approved revision and the affected record stay visible until the destination owner confirms the update.

From approved change notice to confirmed updates

Carrying out an approved change means updating the BOM and item master in the ERP, telling suppliers with open orders on the old revision, and replacing the work instruction on the line, each by a different owner. Effectivity may be set by date, by serial number or by use-up of existing stock, and every owner has to apply it the same way. An email notification says nothing about whether the receiving record changed, so coordinators often find a missed update only when a part at the old revision arrives at goods receipt.

  1. 0101

    Read the approved change

    Duvo reads the approved change notice from the PLM system or change log: affected items, old and new revisions, effectivity and named owners.

  2. 0202

    Find what still references the old revision

    ERP item records and BOMs, open purchase orders and scheduling agreements, and the plant's document register are searched for the old revision.

  3. 0303

    Draft the owner requests

    Duvo drafts an update request for each owner with the approved change and the record to update, and sends unclear effectivity back to the change owner.

  4. 0404

    Your team decides

    Approve the update requests

    The change coordinator checks the requests against engineering's instructions and releases them.

  5. 0505

    Confirm each target record

    Duvo routes the requests, collects supplier acknowledgements and re-reads each target record. An update counts as done only when the record shows the new revision; missing replies stay open.

Change records and the systems that carry revisions

Systems and control details

Change notices come from PLM or the change log, item, BOM and purchasing data from the ERP, and work instructions from the plant's document register. Suppliers usually acknowledge by email or portal, which Duvo reads alongside.

Engineering change notices, PLM affected-item lists, ERP item master and BOMs, Open purchase orders, Supplier acknowledgements, Work instruction register

  • Coordinator releases every request

    No update request reaches a buyer, supplier or document owner until the change coordinator approves it against the approved change.

  • Administrative rollout only

    Scope and effectivity come from the approved change, and unclear instructions go back to the change owner. Duvo does not approve designs, decide what happens to old-revision stock or release production.

  • Old revision, request and result linked

    The original revision, the approved change, each routed request and the confirmed target record stay linked.

What teams ask about Engineering change coordination

  • Does Duvo decide what happens to stock at the old revision?

    No. Use-up, rework or scrap decisions stay with engineering and the plant. Duvo routes only the updates the approved change calls for.

  • What if the change notice has unclear effectivity?

    The affected updates pause and the question goes back to the change owner. Duvo does not pick an effectivity date.

  • Which records does Duvo search for the old revision?

    ERP item records and BOMs, open purchase orders and scheduling agreements, and the plant's work instruction register. The list for your rollout is agreed from the systems your change process already touches.

  • How do we know an owner actually made the update?

    Duvo re-reads the target record after the owner replies. Until the record shows the new revision, the update stays open.

Related processes