Unified Namespace (UNS): what it is and how MQTT fits
A Unified Namespace (UNS) is an architecture pattern in which all systems publish their current state and events to one central, event-driven hub, organised by a shared hierarchy such as ISA-95. It is most often built on an MQTT broker, so machines, MES, ERP and analytics read from and write to one source instead of many point-to-point links.
What is a Unified Namespace?
A Unified Namespace (UNS) is a single, event-driven hub that holds the current state of the business and that every system can publish to and subscribe to. Instead of connecting each application to each data source, every producer publishes once to the hub, and every consumer subscribes to what it needs.
The idea is closely associated with Walker Reynolds, who popularised the term in industrial automation. It is an architecture pattern, not a formal standard. There is no certification and no single specification. In practice, most implementations share three properties:
- One hub: one logical place where current data lives, usually an MQTT broker or a cluster of brokers.
- One structure: a topic hierarchy that models the business, most often based on ISA-95.
- Event-driven: data is published when it changes, not polled on a schedule.
Why point-to-point integration breaks down
A UNS replaces the many direct links of the classic automation pyramid with one hub. In a traditional plant, the PLC talks to the SCADA system, SCADA talks to the historian, the MES queries the historian, and the ERP receives exports from the MES. Each link is a custom integration.
With n systems, the number of possible point-to-point links grows roughly with n². Every new application needs new interfaces, and data passes through several layers before it reaches the people who need it. A UNS changes this to n connections: each system connects to the hub once.
| Aspect | Point-to-point | Unified Namespace |
|---|---|---|
| Connections | Each pair of systems | Each system to one hub |
| Data flow | Request/response, polling | Publish on change, subscribe |
| Adding a consumer | New interface per source | New subscription |
| Where is current state? | Spread across systems | In the hub |
| Coupling | Producers know their consumers | Producers and consumers are decoupled |
How MQTT fits the Unified Namespace
MQTT is the usual transport for a UNS because its publish/subscribe model matches the pattern directly. A few MQTT features do most of the work:
- Hierarchical topics: levels separated by
/map naturally to a plant hierarchy. - Wildcards: a dashboard can subscribe to
enterprise/site-frankfurt/+/+/+/tempand see every temperature on the site. - Retained messages: the broker keeps the last message on each topic and sends it to new subscribers immediately. This is what makes the hub hold current state rather than only a stream of changes.
- Last Will: if a gateway drops off the network, the broker publishes its will message, so consumers know the data is no longer live.
- Lightweight clients: MQTT runs on PLC gateways, edge devices and cloud services alike.
The broker is the hub, but it is not the whole UNS. Edge gateways translate field protocols such as OPC UA or Modbus into MQTT, and consumers such as MES, historians and analytics platforms subscribe to the parts they need.
Structuring the namespace with ISA-95
Most UNS topic trees follow the ISA-95 equipment hierarchy, because it gives everyone in the company the same mental model of where data belongs. ISA-95 (IEC 62264) defines levels from enterprise down to individual work units.
| ISA-95 level | Example topic segment | Typical data |
|---|---|---|
| Enterprise | enterprise |
Company-wide KPIs |
| Site | site-frankfurt |
Site energy use, shift calendar |
| Area | pressing |
Area output, staffing |
| Line (work center) | line-3 |
OEE, current order |
| Cell (work unit) | press-07 |
Machine state, sensor values |
A full topic then reads from left to right like an address:
enterprise/site-frankfurt/pressing/line-3/press-07/temp
enterprise/site-frankfurt/pressing/line-3/press-07/state
enterprise/site-frankfurt/pressing/line-3/order/current
Keep a few rules in mind:
- Agree on names and casing before you start, and document them.
- Put the hierarchy in the topic and the values in the payload.
- Use a consistent payload format, for example JSON with value, unit and timestamp.
- Separate raw data from derived data, for example with a dedicated branch for KPIs.
Current state, history and commands
A UNS holds current state; it is not a historian. MQTT brokers deliver messages and keep the last retained value per topic, but they do not store time series for queries. For history, a historian or database subscribes to the UNS and stores every change.
Commands need care. Writing setpoints back to machines through the UNS is possible, but it should use dedicated topics, strict access control and confirmation by the receiving system. Many teams start with read-only data flows and add writes later.
Getting started with a Unified Namespace
Start small and grow the namespace along real use cases:
- Pick one site or one line and define the topic hierarchy for it.
- Connect existing data sources through edge gateways that publish on change.
- Use retained messages for state values so new consumers see current data at once.
- Set up access control per topic branch: who may publish where, who may read what.
- Connect one consumer with clear value, for example a live line dashboard or an OEE calculation.
- Extend the hierarchy to more lines and sites with the same naming rules.
The value of a UNS grows with every system that joins, because each new producer is immediately available to every existing consumer.