UNS or Unified Namespace is an architectural concept created to enable industrial information to flow in real time, already contextualized, normalized, and aggregated. This way, different areas and applications can consume the same data with consistency.
In this logic, the central challenge of digitalization is no longer just data acquisition but rather the transformation of dispersed measurements into reliable operational information. This avoids scenarios where each new integration generates additional complexity, hindering maintenance and scalability.
Context becomes fundamental in this scenario, since industrial data, in isolation, does not explain everything that is necessary. For example, the same value can represent temperature, count, current, or pressure if it is not associated with the location, asset, stage, and condition in which it was collected.
Luana Pinheiro explains: “[…] UNS functions as a ‘single source of truth,’ enabling devices, sensors, machines, and software to exchange information efficiently, eliminating data silos and promoting interoperability in complex industrial environments.”
For example, in a plant that produces industrial adhesives, where mixing occurs in batches, the mixer PLC can provide signals such as:
- Status (running/stopped/alarm);
- Recipe phase;
- Temperature;
- Rotation speed;
- Current/torque;
- Level;
- Cycle time.
The value of UNS lies in making these signals cease to exist as isolated numbers and instead represent contextualized information, indicating which plant/area, which equipment, which process phase, and which event is occurring at that moment.
This form of contextualization is a requirement to generate real understanding from data, enabling more accurate analysis, faster decision-making, and the development of truly scalable and interoperable industrial applications.
Enabling Unified Namespace in a Manufacturing Plant
One of the most common approaches to implementing UNS is to build it on top of an MQTT broker, using a topic structure to represent it. This way, systems can publish and consume data through subscription, with real-time updates.
This is possible because MQTT was designed as a lightweight protocol, based on the publish/subscribe pattern, reducing coupling between publishers and consumers, facilitating data distribution.
From a normative standpoint, MQTT has specifications as ISO/IEC 20922:2016 (v3.1.1) and as an OASIS standard (v5.0). It is described as a client-server protocol based on publish/subscribe, lightweight and suitable for resource-constrained environments:
Walker Reynolds cites four main requirements for UNS implementation, one of them being the ‘report by exception’ function. This requirement means that data will only be transmitted when relevant changes occur, being a decisive approach to enable scalability.
Within this pattern, it makes a difference to separate three things:
- The transport medium (MQTT);
- The organization of meaning (namespace, topics and model);
- The content (what goes inside the message).
The MQTT protocol is responsible for transporting messages but does not impose meaning or content structure. Therefore, UNS requires additional discipline: defining a topic structure and a minimum data contract (such as unit, timestamp, quality/status, and consistent naming). Otherwise, the ecosystem may be connected but still of little use.
At this stage, ISA 95 typically serves as a guide for organizing what is published. This standard provides a widely recognized hierarchy for structuring assets and operations, supporting integration between corporate and industrial domains.
In the example of the mixer that manufactures industrial adhesives, the difference between having data and having information becomes evident when the PLC stops being just a tag list and starts publishing changes with context, such as:
- Transition from one recipe phase to another;
- Alarm initiation;
- Speed drop;
- Current/torque increase signaling process load variation.
UNS implemented: structure, governance and security
For UNS to be more than a message repository, it is necessary to define a naming structure that reflects the organization’s operations and allows any consumer to find what they need with clarity. In this context, the ISA-95 protocol acts as a guide, organizing the industrial environment into a consistent hierarchy and establishing a common foundation for systems integration.
Bringing this into the context of an adhesives manufacturing plant, a UNS tree can be structured to represent plant, area, line, equipment. And within it, different types of information, such as state, process variables and events are aggregated. Although logically separated, all this data remains associated with the same asset, enabling intuitive reading and navigation:
However, even a well-defined structure cannot sustain itself without a minimum level of governance. In broker-centric UNS architectures, the challenge lies not only in connecting systems, but in ensuring that topics and published data are organized in a consistent and usable manner. This consistency is essential so that different consumers can interpret real-time information reliably.
In practice, this requires some fundamental definitions: who is responsible for each data point or event (that is, who has authority to publish), which attributes are mandatory (such as unit, timestamp and quality/state) and how changes to the structure will be controlled over time, avoiding impacts on already integrated systems.
As data volume and number of consumers increase, concerns about security and availability become more relevant. In this context, the IEC 62443 standard consolidates itself as a reference for industrial environments, establishing guidelines and boundaries that enable the expansion of data circulation without compromising operational resilience, in alignment with UNS principles.
Learn more about ST-One.