BOM versioning and engineering change in Dynamics 365 Supply Chain

A manufactured product's Bill of Materials isn't static — components change, suppliers swap parts, design teams improve assemblies, regulations force substitutions, cost pressures drive material changes. Dynamics 365 Supply Chain Management handles this evolution through BOM versioning and Engineering Change Management — controlling who can change what, when changes apply, and how downstream operations honour the new design.

BOM versions. Each finished item can have multiple BOM versions — distinct BOM records for the same finished good, each with a validity window:

• From date — when this version becomes effective.
• To date — when this version is retired.
• Site — different versions can apply per site (US production uses one BOM, EU production uses another).
• Status — Approved, Active, Discontinued.

When a production order is created for a date, the engine selects the BOM version valid for that date. Changing the design means activating a new version with a future effective date; production orders before the date use the old, after use the new. The transition is automatic.

Multi-level BOMs. Most real products are assembled from sub-assemblies, which have their own BOMs. Each level is versioned independently. A change to a sub-assembly's BOM cascades up — every parent BOM that references the sub-assembly is affected (though the engine resolves which version to use based on the date hierarchy).

Routing versions. Same model applies to routings. The same finished item can have multiple routing versions over time as operations change — new equipment, faster setup, restructured workflow.

Engineering Change Management (ECM). Beyond simple versioning, Engineering Change Management adds formal control of the change process. Used in regulated, engineering-heavy, or PLM-integrated environments. The model:

• Engineering Change Request (ECR) — someone proposes a change. Captured as a request with description, justification, scope (which products affected), priority.
• Review and approval — workflow routes the ECR through stakeholders (design, manufacturing, procurement, quality, regulatory) for input and approval.
• Engineering Change Order (ECO) — once approved, the ECR becomes an ECO that authorises specific changes to specific BOMs, routings, items, or formulas.
• Implementation — the ECO drives the actual changes: new BOM versions created, items updated, routings revised, with effective dates aligning across the affected scope.
• Audit trail — every step of the ECR/ECO lifecycle is logged with who, when, what.

For pharma, medical devices, aerospace, automotive, and regulated industries, ECM is essential. For consumer goods or simpler manufacturing, basic BOM versioning may suffice.

Item versioning. Beyond BOMs, individual items can also be versioned in F&O — though more loosely. The item master holds the current value of each field; historical changes log to the change history rather than producing parallel item records. For "this item evolved" semantics, customers often create a new item rather than evolve the existing one.

Integration with PLM. Larger manufacturers run a dedicated Product Lifecycle Management (PLM) system — PTC Windchill, Siemens Teamcenter, Autodesk Fusion 360 Manage, Dassault Enovia — for design, CAD, document management, regulatory submission. PLM is the source of truth for design; F&O receives BOMs from PLM via integration. The pattern:

• Design happens in PLM.
• Approved designs export to F&O.
• F&O production execution uses the released BOM version.

Integrations exist for major PLM systems; the exchange typically covers BOMs, item masters, and engineering changes.

Co-products / by-products and versioning. Process manufacturing's co-product and by-product structures are versioned alongside formulas. A formula version captures the proportional ingredients, yields, and co/by-products as a unit; activating a new version changes them all together.

Common pitfalls.

• Skipping versioning — editing the same BOM repeatedly loses history. Production orders running with "current" BOM produce inconsistent results when the BOM changed mid-order.
• Future-dated versions without communicating — the floor doesn't know the change is coming; surprises at the cutover date.
• ECM bypass for "quick" changes — informal changes outside the ECM process undermine the audit trail and regulatory compliance.

Operational reality. Version discipline scales with manufacturing maturity. Smaller operations get by with basic BOM versions; complex products in regulated industries need full ECM. Match the rigour to the requirement.