SCADA and HMI platforms delivered and licensed as a cloud service, with the visualization and historian layer hosted off-premises rather than on a local server.
Unified Namespace & MQTT Sparkplug B architectures
Control Systems — DCS · PLC · ESD · HMI
Over-Promise
Near-term · 2–5 yrs
Evidence E3 · First production use
An architecture in which plant systems publish their data once, to a shared event-driven namespace, instead of being wired together pair by pair. The messaging standards are settled; the governance needed to make it work across an enterprise is not.
The problem it addresses
In most plants, data moves through point-to-point integrations. The historian polls the DCS, the MES has its own interface to the historian, a quality system reads from both, and each new analytics project adds another connection. Each link is configured, secured and maintained separately, and nobody has a complete picture of what depends on what. The cost of adding a new consumer of data rises with every system already connected.
A unified namespace (UNS) replaces this with a hub. Each system publishes its data to a central broker, organised in a common hierarchy such as enterprise, site, area, line and asset, and any authorised consumer subscribes to what it needs. The term was popularised through industry training and conferences rather than by a standards body, and in practice it means different things to different suppliers.
| Point-to-point | Unified namespace | |
|---|---|---|
| Adding a new data consumer | A new interface to each source | Subscribe to existing topics |
| Where data structure is defined | Inside each interface | Once, in the namespace |
| Knowing when data is stale | Depends on each interface | Session state, e.g. Sparkplug birth and death messages |
| Main risk | Integration sprawl | A shared dependency that needs governance |
MQTT and Sparkplug
Most UNS implementations use MQTT, a lightweight publish-and-subscribe protocol that is itself an international standard, ISO/IEC 20922. MQTT moves messages efficiently but deliberately says nothing about their content, so two MQTT systems can be connected and still not understand each other.
Sparkplug fills that gap for industrial data. It defines a topic namespace designed for OT, a payload format for process variables, and rules for managing session state 1. Devices announce themselves with a "birth" message, and a "death" message is published when a connection is lost, so consumers know when data is stale rather than merely unchanged. Sparkplug 3.0 was published as international standard ISO/IEC 20237, announced by the Eclipse Foundation in November 2023 12.
Sparkplug is not the only option. Some architectures use plain MQTT with a site-defined JSON schema, or OPC UA PubSub over MQTT, which brings OPC UA's information models with it. The choice matters less than making it once and enforcing it.
Why governance is the hard part
A namespace that everyone depends on needs rules: who may publish to which part of the hierarchy, which naming conventions and units apply, how a change to a data structure is approved, and who is responsible when a publisher sends bad data. These are the same problems master-data management has long faced in business IT, and they do not disappear because the transport is elegant.
Security needs the same care. A broker that every system talks to is an attractive target and a single point of failure. It needs redundancy, authentication of every client, topic-level access control and a defined place in the IEC 62443 zone design, typically on the OT side or in the industrial DMZ with tightly controlled conduits. It should never become a path from the business network into control.
Finally, a UNS does not replace the control system's own networks. It sits above control, carrying data for monitoring, analytics and coordination. Control loops and safety functions should not depend on it.
A realistic way in
Projects that succeed tend to start with a defined use case, such as an energy dashboard or equipment effectiveness across several lines, build the namespace for that scope with naming rules agreed up front, and extend it as new consumers appear. Projects that start by trying to publish everything usually end up with a large broker full of poorly described data.
Evidence timeline
- 2016MQTT 3.1.1 published as ISO/IEC 20922.
- Nov 2023Eclipse Foundation announces Sparkplug 3.0 as international standard ISO/IEC 20237. 1
Why it sits at the Over-Promise stage
Attention from conferences and suppliers since 2023 has been intense, and the label is applied to almost any MQTT-based project. Enterprise-wide production deployments with mature governance are still the minority, and public evidence on lifecycle cost is limited. That is the Over-Promise stage.
The underlying standards are mature and inexpensive to adopt, which is why we expect the entry to move through the cycle faster than most, once governance practice settles.
Adoption signals to watch
- Published enterprise-wide deployments with data-governance models, not only single-plant demonstrations.
- Control-system and historian suppliers shipping native, certified Sparkplug or OPC UA PubSub interfaces.
- Common namespace conventions emerging across companies, for example aligned with ISA-95 hierarchies.
Questions to ask before committing
- Who owns the namespace, and what is the process for approving new topics and changes to data structures?
- Which payload convention will be used everywhere: Sparkplug, OPC UA PubSub or a site schema?
- How is the broker made redundant, and what happens to consumers when it fails?
- Where does the broker sit in the security zone design, and how is every client authenticated?
- Which first use case will prove the value before the namespace is extended?
Terms used on this page
- MQTT
- A lightweight publish and subscribe messaging protocol built around a central broker.
- Sparkplug B
- An open specification, published as ISO/IEC 20237, that standardises MQTT topics, payloads and state for industrial data.
- Report by exception
- Sending a value only when it changes, rather than at a fixed interval.
Sources
- The Eclipse Foundation announces Sparkplug as an international standard for a plug-and-play Industrial IoT
- Sparkplug now an official ISO/IEC standard
- IIoT milestone as Sparkplug becomes international standard
Related technologies
See this entry on the full maturity map · All Control Systems entries · How placements are made. Stage and time-horizon placements are editorial judgements based on the public sources listed above, as of October 2026. They are not engineering, safety or investment advice; see the Terms of Use.