Maps every Plex integration surface — EDI via third-party brokers, Plex APIs, MES material-consumption events, IAM, Flex custom-field access, and Plex Reporting — to the D365 integration estate, and designs the permanent ERP/MES boundary that defines this programme's architecture if Plex MES is retained.
If Plex MES stays live while D365 replaces Plex ERP, integration is not a workstream — it is the programme's permanent architecture. Every material-consumption event, every production-completion posting, every inventory truth question and every reconciliation query will cross that boundary every day, forever.
Before mapping Plex patterns to D365 mechanisms, you need the full target landscape. D365 F&SCM provides six distinct integration surfaces, each designed for a specific workload profile:
Plex's EDI capability is delivered through third-party brokers — Cleo, Cogential IT and Infoconn are the three most commonly cited. Specific transaction-set support (850/855/856/810/997 and automotive-specific 830/862/866) is sourced only from those brokers' marketing pages, not from Rockwell primary documentation.
Plex references "several options for APIs" for customer orders, shipping and just-in-sequence parts delivery. A public developer portal exists in principle at developers.plex.com.
If Plex MES is retained as the shop-floor system of record while D365 replaces Plex ERP, the boundary between these two systems is not a migration artefact — it is a permanent architectural decision that will carry operational load every day. Four questions define it:
Plex uses its own tenant-scoped IAM — documented informally via a public Postman collection — with flat roles and permissions. D365 authenticates via Microsoft Entra ID and authorises through a hierarchical model: permissions → privileges → duties → security roles, with extensible data security policies for row-level and field-level…
Plex's "Flex" customisation layer provides custom fields across multiple data types, a drag-and-drop workflow builder, and — recently — API access to custom fields. No primary Rockwell page documents Flex's object model, governance limits or upgrade-safety guarantees;
Plex Reporting and Analytics offers self-service, role-based dashboards with prebuilt templates across supply chain, sales, HR, finance, production and procurement. Its data-warehouse refresh latency and underlying data model are undocumented publicly.
The integration inventory is a first-class discovery artefact — not a nice-to-have appendix. A Plex tenant with active MES, EDI brokers, Flex custom-field integrations, reporting feeds, and third-party middleware can easily have forty or more active integration touchpoints.
Integration is either a workstream or the permanent architecture, depending on whether Plex MES stays live. Either way, the integration inventory is the gating discovery artefact, the ERP/MES boundary must be designed rather than discovered, and the asymmetric documentation maturity of the Plex API surface is a first-order programme risk…