A unified namespace (UNS) is an architecture pattern in which plant and business systems publish their current data to one shared, hierarchically organized hub, usually an MQTT broker, instead of exchanging it through point-to-point integrations.
In a UNS, every source publishes to a common topic tree. The tree usually follows the ISA-95 equipment hierarchy: enterprise/site/area/line/cell/asset. PLCs, SCADA, MES, quality systems and ERP publish events and states as they change. Any consumer subscribes to what it needs. The goal is one place to find the current state of the operation, and fewer custom interfaces to maintain.
Typical building blocks are an MQTT broker, edge gateways that translate from PLC protocols or OPC UA, a naming convention, and often the Sparkplug specification to standardize payloads and report data only when it changes. A historian or data lake subscribes to keep the history, because the broker itself holds mainly current values.
UNS is not a formal standard. It is a design approach built on existing standards, and it was popularized largely by practitioners and integrators rather than a standards body. Implementations vary. The hard part is not the broker but governance: agreeing on names, units, ownership of topics, and who may publish what. A UNS also creates a central point that needs security and availability planning.
Questions about Unified namespace
Is the unified namespace a standard?
No. It is a design approach built on existing standards. It was popularized largely by practitioners and integrators, not by a standards body, and implementations vary.
Is a unified namespace the same as an MQTT broker?
The broker is one of the typical building blocks, alongside edge gateways, a naming convention and often the Sparkplug specification. The hard part is not the broker but governance: agreeing on names, units, ownership of topics and who may publish what.
Does a unified namespace replace a historian?
No. The broker holds mainly current values. A historian or data lake subscribes to the UNS to keep the history.
Unified namespace in real plants
- Gousto and HighByte: Meal-kit maker Gousto uses HighByte Intelligence Hub to model data from its factory PLCs at the edge and publish it to AWS, with a unified namespace on AWS IoT Core.
- Siemens Gamesa and HighByte: Siemens Gamesa uses HighByte Intelligence Hub to model plant data into a local unified namespace, used by engineers to monitor the blade casting mold control system.
- Catalent and HighByte: Catalent uses HighByte Intelligence Hub in its process development labs to model bioreactor and at-line equipment data and publish it to a HiveMQ broker for analytics and remote monitoring.
- VOSS Automotive and Litmus: VOSS Automotive uses Litmus Edge to connect old and new production machines, model data in a unified namespace, calculate KPIs such as OEE at the edge and send them to the cloud.
Related terms
MQTT
MQTT is a lightweight publish/subscribe messaging protocol, an OASIS standard, in which devices send messages to named topics on a broker and any subscribed application receives them.
ISA-95
ISA-95 is an international standard series, also published as IEC 62264, for integrating enterprise business systems with manufacturing control systems.
OPC UA
OPC UA (OPC Unified Architecture) is a platform-independent, open standard for exchanging industrial data securely between machines, controllers and software, published by the OPC Foundation and standardized as IEC 62541.
IT/OT convergence
IT/OT convergence is the integration of information technology, the systems that handle business data, with operational technology, the systems that monitor and control physical equipment, so data and practices flow between them.
Industrial IoT (IIoT)
Industrial IoT (IIoT) is the network of sensors, instruments, and machines in industrial settings that are connected to computers and software to collect and use operational data.