Appearance
Production Engineering Change
Engineering change control is used when a product, BOM, routing, operation, inspection plan, document preset, or order-specific build rule needs a controlled revision.
Use it for ECO/ECN workflows such as replacing a component, changing a routing step, adding a quality gate, revising a specification, limiting a change to a customer, serial range, lot range, or specific production order, and reviewing the impact before production release or activation.
When a quotation or sales order is the source demand for a production order, link the document transaction to the engineering change so the quote-to-engineering handoff stays traceable through release.
Engineer-To-Order Context
Engineer-to-order manufacturing can link an engineering change to a Project and WBS/work package when the tenant has enabled the optional ETO capability. This is an optional setup for customer-specific or project-based builds.
Use Project/WBS context when a customer build, configured assembly, prototype, installation, or commissioning scope needs engineering traceability from change request through production release. The WBS node must belong to the selected project. Targets can inherit the header Project/WBS context or override it when a change affects a different work package.
The impact report includes Project and WBS references so production, project control, and finance teams can review the same build scope before approval.
What To Review
| Area | What To Check |
|---|---|
| Change Header | Title, change type, effective dates, reason, and change notes. |
| Targets | BOM, routing, routing operation, inspection template, inspection gate, stock item, document transaction, production order, or production supply suggestion affected by the change. |
| Effectivity | Date, serial range, lot range, customer scope, Project/WBS context, or order-specific applicability. |
| Freeze Policy | Whether open production should snapshot the current definition, block open orders, allow planned orders only, or treat the target as reference-only. |
| Impact Report | Open orders, planned production suggestions, BOMs, routings, operations, and quality gates affected by the change. |
Impact Analysis
Run the Engineering Change Impact Analysis report before approval and activation.
The report shows the change number, target, impacted production record, effectivity status, risk level, freeze policy, policy action, and recommended action. Use it to decide whether to:
- revise or supersede a BOM or routing
- refresh planned production supply
- block release until the change is reviewed
- freeze the current production snapshot for active shop-floor work
- update quality gates or inspection templates before output release
- keep a reference-only target outside the production release blocker path
- route project-specific build changes to the right WBS/work package before release
- verify the source demand handoff before releasing quotation-driven production orders
Controls
Confirm these before activating a change:
- planned production supply has been regenerated, firmed, frozen, cancelled, or converted intentionally
- Project/WBS context is present and valid for engineer-to-order work
- released or in-progress orders have a frozen production definition snapshot
- blocking quality gates and numeric specs still match the revised process
- cost simulations or standard-cost versions have been reviewed when BOM/routing changes affect material, labor, machine, or overhead assumptions
- customer, serial, lot, or order-specific effectivity is clear enough for production and traceability teams to apply consistently