Engineering approves a new bracket, but an open production order still points to the old drawing. An engineering change order needs to control that cutover: identify the affected objects, approve the proposed revision, state when it applies, decide what happens to existing work and verify the production records after implementation. A signed approval alone does not show which revision a specific order should build.
PTC’s engineering change process overview describes analysis, approval and implementation of product changes. Product names and sequences differ across systems, so map your change request, change notice and change order to actual decision rights before relying on their labels. This workflow focuses on the evidence an operations lead needs to implement an approved change across engineering, planning and purchasing.
Name every affected object and its current revision
The engineering change owner records a stable identifier, reason, request owner and affected product scope. List each part, assembly, drawing, specification and operation that must change. For every object, retain the current revision and the proposed revision. The failure at this stage is an affected object omitted from the change scope. A description such as updated bracket cannot tell a buyer which supplier drawing to send or a planner which assembly version to release.
Start from the affected item’s where-used relationships, then have the engineering owner confirm the list. The same component may appear in several assemblies with different requirements. Preserve the parent-child relationship and quantity basis from the bill of materials so the impact review can distinguish a direct replacement from a change that also affects lower-level components.
Record the interfaces that need review: fit with mating parts, inspection characteristics and supplier specifications, for example. Assign an owner to each unresolved item and prevent an open question from becoming an assumed approval. This is an implementation checklist to adapt to your change policy; it does not replace the engineering analysis required for the product.
Keep review approval separate from applying the revision
The change owner assigns reviewers for design, manufacturing feasibility, quality requirements and commercial consequences under the approved policy. Retain each decision, its timestamp and the revision reviewed. If the content changes after an approval, the change owner should determine which decisions need to be repeated. The failure is carrying approval forward without checking its scope: a person’s approval of revision B does not establish approval of a later revision C.
Odoo’s approval documentation distinguishes approved changes awaiting application from changes already applied. Use that distinction when defining your own status model. A dashboard should show an approved but unapplied change as pending implementation, with an owner, instead of presenting approval as evidence that production already uses it.
Keep testing or review copies distinguishable from the released production definition. Odoo’s engineering change order documentation describes a non-production BOM version and a later application step. That documented behavior is specific to Odoo; verify the equivalent release controls in the system your plant uses.
State the exact boundary between old and new builds
Engineering and production planning agree whether the revision applies by date, serial range, lot or another supported rule. Include the time zone for a date-based cutover and the product or site scope. PTC’s effectivity documentation separates the affected objects and effectivity controls. The failure is applying one change-level date to objects with different rules. Confirm the object and range each rule governs.
Assume an illustrative plant approves a revision on November 19 for new orders released from November 23. Order A was released on November 18 and has started; Order B is scheduled for release on November 24. Under the stated release-date policy, B should use the new revision. A needs an explicit disposition under the old-order policy. Its scheduled finish after November 23 does not, by itself, decide whether it should be rebuilt.
List the orders that straddle the boundary and let the authorized owner choose among continuing, reworking, holding or canceling them. Keep those decisions at the order level with the reason and approver. The example dates illustrate a policy, not a default rule for every ERP. Verify which date and status the production system uses when selecting a revision.
Revision and reviewers
Effectivity and disposition
Orders and source records
Trace an approved change into an open order
Use approved engineering and planning extracts to locate a revision mismatch and its source.
Resolve stock, supplier orders and work in process
Production planning coordinates dispositions for finished stock, unissued components and work in process; purchasing owns the supplier handoff. Each decision must match engineering approval and commercial terms. The failure is leaving old-revision material available under an assumed disposition. Do not infer that old stock is scrap because a new revision exists, or that it is acceptable because the part number has not changed. Record the actual approved use or restriction.
Consider a hypothetical change affecting 80 old-revision components on hand, a purchase order for 120 and 30 units already issued. Those are separate populations. Reconcile the 30 issued units to work orders before adding them to any exposure total (they may already be excluded from the on-hand balance). Ask purchasing to confirm which portion of the open order the supplier can change, and preserve the supplier’s acknowledgment.
Link the revised operation or inspection instruction to its effective production definition. The manufacturing routing establishes the operation sequence, while this change record explains why a revision is authorized and where it applies. If new tooling, training or inspection evidence is required, leave implementation open until the named owner supplies it.
Close on implemented evidence, with exceptions retained
The implementation reviewer checks representative affected orders and known boundary exceptions after application. Compare the order’s BOM revision, drawing reference and routing against the approved effectivity rule. Verify that obsolete copies have been handled through the document-control process. The failure is closing on an acknowledgment without checking the resulting objects. Record the source evidence and check date; an email saying done cannot establish which production objects changed.
Keep the before-and-after revisions, approval record, implementation timestamp and unresolved deviations together. For concurrent changes to the same assembly, verify that applying one has not overwritten the other’s intended result. Escalate inconsistent source records to the change owner, and keep the order on hold where the approved procedure requires it. Do not repair the report by silently replacing the historical revision.
How Permute connects revision and order evidence
Permute is the connected-data platform we sell for analysis and custom business applications. We can connect approved NetSuite records and engineering extracts in Google Drive or Google Sheets, reconcile item and order identities, and preserve source references. Unsupported source connections require their own verification; an engineering system named in an article is not a promise of a native integration.
We define the customer’s approved effectivity rule and exception categories once for repeated analysis. An operations lead can ask which open orders disagree with an approved revision and inspect the matching logic, source revision and extraction time. Ambiguous part mappings or missing approvals remain visible for review instead of being filled with a guessed revision.
Leave engineering authority with the change owner
This review does not approve a design, certify a product or release an ERP change. It compares authorized records under declared rules. Engineering and quality owners retain disposition authority, and any supported external action needs its own explicit permission and approval path. Analytical refresh also cannot guarantee that a shop-floor document changed at the same instant.
Accept the change when the production boundary is evidenced
An engineering change order is ready to close when the approved revision, effectivity rule and affected production records agree. Keep open orders, existing stock and supplier commitments in separate disposition paths. Preserve the old definition and the evidence that the new one was applied. A remaining exception needs a named owner and decision, even when the rest of the cutover is complete.
Review one revision cutover across your records
Bring an approved change and the open orders whose revision status is disputed.
Questions about engineering change implementation
Are an engineering change order and change notice always different?
No. Systems and company procedures use those labels differently. Map each record to its purpose, approval authority and implementation behavior before comparing statuses across applications.
What evidence should be retained if implementation is reversed?
Retain the original approval and implementation evidence, then link the authorized reversal or superseding change. Record which orders or stock were affected during the interval. Replacing the old record with the final state would remove the history needed to explain those builds.
Can a drawing correction follow a smaller review path?
Your approved change policy may define different review paths by risk and scope. The responsible owner must classify the correction and preserve that decision. A small visual edit can still affect a requirement, so its appearance alone does not establish that production impact is absent.