RTLS & IoT integrations — by the platform, not by the spec sheet.
Location data that doesn't reach your WMS, MES, ERP, EHR, CMMS or OT layer is decoration. Each page below covers the integration patterns, common pitfalls and architecture decisions for a specific target platform.
The platforms your operation already runs.
SAP EWM
Extended Warehouse Management — events, master data, streaming patterns
SAP WM
Legacy WM — RF transactions, IDocs, migration considerations
Manhattan WMS
Manhattan Active — event subscriptions, microservices architecture
Blue Yonder
Luminate Logistics, WMS, Cognitive Decision Engine
MES platforms
Siemens Opcenter, Rockwell FactoryTalk, SAP MII, GE Proficy, Aveva
SCADA & OPC UA
OT-side integration via OPC UA, namespace design, IEC 62443 alignment
CMMS
IBM Maximo, SAP PM, Infor EAM — condition-based work orders
Digital twin platforms
NVIDIA Omniverse, Siemens Xcelerator, Azure Digital Twins
Frequently asked questions
Which integration is most complex?
Usually MES or legacy SAP WM, where the API surface is older and ABAP work is needed. SAP EWM and Manhattan Active expose modern event-driven interfaces. We size effort at gate 1 per target platform.
Who builds the integration — TRACIO, the platform vendor, or our SI?
Combination. TRACIO designs the architecture and event flow. The platform vendor or your existing SI delivers the platform-side configuration. The RTLS vendor provides their interface. We orchestrate the three-way delivery.
Can RTLS integrate with multiple targets simultaneously?
Yes — typical enterprise deployments hit 2-4 systems (WMS + MES + CMMS, or EHR + CMMS + ADT). We design the integration layer with a canonical event schema and per-target adapters.
Does TRACIO build custom integration code?
Yes through build & integration. We deliver in partnership with your incumbent SI where one exists, or end-to-end where one doesn't.
Last updated: