Product lifecycle in D365 F&O: Engineering Change Management

A recurring architecture discussion in manufacturing deployments: an organization running multiple plants on Dynamics 365 Finance and Operations wants a unified product lifecycle process. Design, approval, release, and production all managed in one system. The architecture needs version control, approval workflows, and integration with engineering tools like AutoCAD. The ask is to keep the process inside the Dynamics ecosystem as much as possible.

The reflexive answer is "build a custom module". It's almost always wrong.

Why custom is the wrong starting point

Custom product management modules in F&O tend to start small ("just a form to track engineering revisions") and grow into shadow PLM systems that duplicate what the platform already ships. Three specific costs:

• Overlap with product master and variants - F&O already has a rich released-product structure. A custom module that doesn't hook into it ends up with two sources of truth for the same item.
• Lost upgrades - custom modules drift behind One Version updates. Features like attribute-based configuration, product variants, and global item sharing all get added to standard F&O; a custom module has to be re-engineered to stay current.
• Integration refactoring - external PIM and CAD systems need to talk to the authoritative item, not to a parallel custom table.

The standard feature that earns its place

Engineering Change Management (ECM) in Dynamics 365 Supply Chain Management is the feature built for this problem. ECM covers:

• Revision control on released products - every engineering change creates a tracked revision linked to the product master
• Approval workflows - multi-stage, role-based, with rollback if rejected
• Change types - engineering change request (ECR), engineering change order (ECO), with configurable transitions
• Impact analysis - which BOMs, routes, and production orders are affected before a change is released
• Integration hooks - ECM exposes events the solution architect can wire to external PIM or CAD systems via the business events framework

ECM doesn't replace engineering-side tooling like AutoCAD; it becomes the release record of truth for what the manufacturing side consumes.

Integrating CAD and PIM

External engineering tools stay external. The integration pattern:

• CAD side - engineering designs products in AutoCAD or similar. Drawings are stored in the engineering PLM/PDM system.
• Release event - when a drawing is approved for manufacturing, the PDM system calls F&O's ECM endpoint via OData or a custom service to create/update the released product revision.
• F&O side - ECM carries the approval, the manufacturing team picks up the new revision in BOMs, routes, and production orders.
• Attachments - drawing files are linked to the product record via Document Management, but the drawings themselves stay in the PDM system (don't duplicate storage).

This keeps engineering tooling in engineering hands and manufacturing tooling in manufacturing hands, with a clean release boundary between them.

Multi-plant considerations

Across multiple plants, the architecture holds if:

• Products are global via released product master data with plant-specific attributes (lead time, production methods) configured through product dimensions or site-specific parameters, not duplicate product records per plant
• Engineering changes are global - ECM lives at the product-master level, not per-plant
• Production is local - each plant has its own BOMs, routes, and production orders referencing the globally released item

The alternative - one product per plant - breaks down the moment a customer orders the same item across sites and finance tries to consolidate reporting.

What the other "solutions" cost

• Excel for version tracking - fragile, no audit trail, no integration path, fails any regulatory inspection
• Separate item records per version - explodes master data, breaks BOM explosion logic, forces costly reconciliation
• Custom module tailored to engineering - years of maintenance debt, loses upgrade path, needs rebuilding the next time Microsoft ships a PLM enhancement

None of these pass the "will this still work after three One Version cycles" test.

What ships with ECM

A working ECM implementation has: standard ECR/ECO types configured with an approval workflow, the PDM-to-F&O integration (OData endpoint on released products with authorization), business-event subscribers for revision release and change completion, and a runbook for how engineering requests revisions and how manufacturing consumes them.

The feature exists precisely so teams don't have to build a custom PLM. Use it.