Every data point, event or status is assigned a unique location in the namespace. This is comparable to a file structure, but for data.


πŸ”§ Implementation and technologies

Component Role in UNS
MQTT broker (e.g. HiveMQ, Mosquitto) Central publish-subscribe engine for data packets
SCADA connections Publishes statuses and receives setpoints via UNS
Edge Devices Publish measurement data from field level via IoT protocols
MES and ERP Can subscribe to events or modify data via standard topics
Historian/Analytics Subscribe to UNS data for storage and analysis

πŸ”„ Difference from traditional OT integration

Traditional model Unified Namespace model
Point-to-point connections A single publish/subscribe layer with central topic structure
Push-pull integrations Event-driven, real-time
Ad-hoc data flows Standardised hierarchy and topic structure
IT–OT separated silos OT convergence via a shared namespace

UNS does not replace systems, but makes them accessible and interoperable through a shared data model.


πŸ” Security in UNS

  • Access to topics through authentication and authorisation (e.g. TLS + ACLs in MQTT)
  • Segmentation of sensitive topics (e.g. /OT/Safety/** or /Secure/**)
  • Audit trail of who publishes or subscribes to what
  • Integration with Security by Design and IEC 62443 principles

🏭 UNS in practice: applications

Application How UNS helps
Batch production Real-time sharing of batch data between PLC, MES, LIMS
Predictive Maintenance Sensors publish vibration data β†’ AI system subscribes and predicts
Energy management Real-time energy consumption shared via UNS with dashboards & reports
KPI monitoring SCADA publishes live status β†’ Power BI subscribes
IT–OT data lake Historian and analytics tools collect via a single uniform data layer

πŸ“Œ In summary

A Unified Namespace is the modern backbone of real-time industrial data sharing. It provides scalable, standardised, event-driven access to all information β€” without the proliferation of hundreds of point-to-point connections.