Container genealogy, licence plates, and the honest traceability gap
How Plex MES's container-level identity and lot/serial genealogy compare with D365 warehouse management and batch/serial tracking, where the two systems genuinely diverge, and the architectural decisions a client faces when moving off Plex's traceability model.
What you will be able to do
Explain the Plex MES licensing boundary and why inventory traceability is not part of Plex ERP
Describe the Plex container model and how it differs from a D365 licence plate
Map Plex lot and serial genealogy to D365 batch/serial tracking and item tracing
Evaluate the four architectural options for reproducing shop-floor genealogy after Plex
Design an opening-balance migration that carries quantities, values, and tracking dimensions
Compare Plex SCP planning with D365 master planning and Planning Optimization
Introduction
This is the hardest chapter in the Plex path, because it confronts an honest gap rather than a straightforward translation. Plex tracks physical inventory as identified containers — each carrying its own history: where the material came from, every transaction it passed through, and every shop-floor operation performed on it.
The licensing boundary — inventory lives under Plex MES
Rockwell's product taxonomy is unambiguous on this point. The URL path for Plex Inventory Management is plex.rockwellautomation.com/en-us/products/manufacturing-execution-system/inventory-management.html — under Manufacturing Execution System, not ERP.
What Plex does — the container model
Based on Rockwell's primary marketing material and secondary aggregator sources, Plex MES tracks inventory through an identified-container model. Each container:
What D365 offers — warehouse management and tracking dimensions
D365's inventory and traceability capabilities are built from several interlocking modules:
Where they genuinely differ
The critical gap is in the first two rows. D365 can trace batch-to-batch relationships through production — that is not the issue. The gap is that D365 does not natively hold a permanent, operation-level identity record for a physical unit of inventory in the way Plex's container does.
The decision the client actually faces
There are four architectural paths. Each has different cost, complexity, and traceability fidelity:
Costing and the opening-balance migration
Regardless of which traceability path is chosen, the programme must migrate opening inventory balances from Plex to D365. This is a coordinated exercise involving quantities, values, and tracking dimensions, reconciled at a frozen cut point.
Planning — Plex SCP versus D365 master planning
Plex SCP (Supply Chain Planning) is a separately licensed product that provides demand/supply planning, ATP/CTP, and consensus master scheduling. It links inventory positions, supplier lead times, production capacity, and demand forecasts into a planning engine.
Knowledge check
Summary
The Plex inventory chapter is defined by an honest gap: D365 is a strong inventory and warehouse management platform, but it does not natively replicate Plex MES's container-level, operation-level genealogy.