MES integration with RTLS / RFID.
RTLS without MES integration is decoration. RTLS with MES integration changes scheduling, OEE attribution, traceability and shop-floor decision-making. This is the patterns-and-pitfalls summary for major MES platforms.
MES platforms and their integration surfaces
The dominant MES platforms each expose RTLS-friendly surfaces but at different levels of maturity.
Siemens Opcenter (formerly Camstar / SIMATIC IT) has well-defined REST and OPC UA interfaces; Rockwell FactoryTalk uses CIP and OPC UA with FactoryTalk InnovationSuite for analytics;
SAP MII is OData-based and tightly coupled to S/4HANA; GE Proficy uses OPC UA and Webspace REST; Aveva (formerly Wonderware) is moving toward Aveva System Platform with OPC UA.
The right integration pattern is platform-specific.
WIP traceability and genealogy
The highest-value MES-RTLS integration is WIP traceability: which physical part, with which lot, was on which fixture, at which station, with which operator, at which time. RTLS captures the where-and-when automatically; MES captures the what-and-who; the integration ties them.
This is the foundation of IATF 16949 and AS9100 traceability without operator overhead — see our IATF 16949 page for the compliance angle.
OEE attribution at the right granularity
MES typically calculates OEE at the line or asset level. RTLS adds station, fixture and operator-flow context that makes OEE attribution actionable.
The integration delivers: real cycle-time variability per station, dwell-time-per-part, idle-vs-active per asset, and the location-aware decomposition of unplanned-downtime root cause. Without this layer, OEE is a number; with it, OEE is a tool.
Pitfalls — protocol mismatch and timing
Two recurring pitfalls. Protocol mismatch: OPC UA, CIP and proprietary MES protocols don't carry the same semantic richness as RTLS event models; the integration layer translates carefully.
Timing: MES is transactional at production-cycle frequency (seconds), RTLS is continuous (sub-second). Alignment requires explicit windowing rules and idempotency. We design both as gate-1 deliverables.
Frequently asked questions
Which MES platform is easiest to integrate with?
Siemens Opcenter and GE Proficy expose the most modern API surfaces. Older Rockwell and SAP MII installations require more bespoke integration. Aveva is in transition. We design the specific integration per platform version.
Can we feed RTLS data to multiple MES instances across plants?
Yes — common in multi-site organisations with regional MES variation. The integration architecture uses a canonical event schema with per-MES adapters. This is also a foundation for digital twin enablement across the manufacturing network.
How does this interact with OEE reporting tools?
Most enterprises run OEE reporting in Power BI, Tableau, Qlik or a dedicated OEE platform. The integrated MES+RTLS event stream feeds these tools with the location-aware context that makes drill-down possible. We design the data layer to support both.
Who builds the integration — TRACIO, the MES vendor, or the SI?
Typically TRACIO designs the architecture and event flow; the MES SI partner builds the platform-side configuration; the RTLS vendor provides the source interface. We orchestrate the three-way delivery.
Last updated: