SCADA & OPC UA integration with RTLS / IoT.
RTLS and IoT data has real value inside the SCADA / control layer — where it can drive interlocks, dispatch and operator HMIs. OPC UA is the dominant interoperability standard. This is the operator-level summary of how to integrate cleanly.
OPC UA as the universal OT interface
OPC UA (IEC 62541) is the modern standard for OT-IT interoperability and is widely supported by Siemens (SIMATIC, WinCC), Rockwell (FactoryTalk Linx, RSLinx), Schneider (EcoStruxure), AVEVA (System Platform, InTouch), Honeywell (Experion), Yokogawa (CENTUM) and ABB (Ability).
RTLS platforms increasingly expose OPC UA servers or clients, making OT-side integration meaningfully easier than five years ago. Where OPC UA is not available, the integration uses gateway middleware (Kepware, Matrikon).
Tag-mapping and namespace design
OPC UA structures data in addressable namespaces — getting the namespace right is the most important up-front design decision. RTLS position events typically map to a /Plant/Zone/Asset hierarchy with attributes for position, dwell, last-seen and meta-data.
The wrong namespace design forces every consuming system to re-implement mapping logic; the right one is reused across SCADA, MES and historian. We design this at gate 1.
Real-time control implications
OPC UA can carry RTLS events at high frequency, but the OT side has timing implications. SCADA HMIs typically refresh at 1-10 Hz; PLC scan cycles are 10-100 Hz. RTLS events at 10+ Hz must be downsampled or windowed appropriately.
Conversely, safety-critical events (lone-worker duress, collision warning) must propagate within sub-second latency — different design constraint. We size the architecture for both flows.
Security — IEC 62443 alignment
OPC UA supports mutual TLS, X.509 certificate-based authentication, role-based access and audit logging — but support is configurable. Default settings are rarely IEC 62443-aligned.
We design the OPC UA security profile as part of the OT cybersecurity scope — see our IEC 62443 page for the surrounding framework.
Frequently asked questions
Do RTLS platforms natively support OPC UA?
Increasingly yes. Most enterprise RTLS platforms now expose OPC UA servers (or have a roadmap). Industrial-focused RTLS vendors (Ubisense, Sewio, Pozyx) generally have more mature OPC UA support than retail-focused vendors.
When do we need a gateway like Kepware or Matrikon?
When the RTLS platform doesn't have a native OPC UA server, or when you need to bridge multiple OPC UA endpoints with consistent namespace and security. We scope gateway need at gate 1; it's often the right call for heterogeneous environments.
Can SCADA drive interlocks based on RTLS events (e.g., lockout based on worker presence)?
Yes, with appropriate latency and safety considerations.
Safety interlocks usually require certified safety-PLC channels in addition to OPC UA — we don't recommend RTLS as the sole signal for safety-critical functions, but we do integrate RTLS as a higher-level safety augmentation.
How does this integrate with historian data?
RTLS events can stream into PI System, AVEVA Historian, GE Proficy Historian or Honeywell Uniformance via OPC UA. The historian becomes the time-series foundation for location-aware OEE, downtime analysis and digital-twin enablement.
Last updated: