Unified Namespace, explained
Industrial data from different systems. One shared way to use it.
A Unified Namespace (UNS) is an architectural approach for organising and sharing industrial data with consistent names and context. It helps machines, applications and teams use the same operational information.
From isolated signals to usable operational information
A machine signal alone rarely tells the whole story.
When data includes its source, location, timestamp, units and status, other systems and teams can interpret it more consistently.
- Machine connections Local or isolated exchanges.
- IoT Local or isolated exchanges.
- Industrial IoT Operational use cases.
- UNS & IIoT A composable architecture.
- Systemic view Optimisation and AI/ML at scale.
Shared information.
Different decisions.
-
Leadership
A consistent operational view for strategic decisions.
-
Finance
Understand integration costs and the assumptions behind investment value.
-
Site management
See relevant production events and investigate anomalies.
-
Quality
Follow production context and trace the information behind a quality question.
-
IT
Use maintainable interfaces and shared definitions across applications.
-
OT
Make equipment information useful beyond the machine or production cell.
UNS and industrial connectivity, explained
No. UNS is an architectural approach, not a product you buy. It requires appropriate technologies, data definitions, governance and ownership.
MQTT is a lightweight messaging protocol. Systems publish data to a broker and others subscribe to the topics they need.
OPC UA is a common way to read structured data from machines and controllers. It often feeds information into the namespace.
i3X is an open interface for exchanging contextualised industrial information between applications.
No. A Unified Namespace can run on site, in the cloud or across both, depending on your needs.
Start with one
useful data flow.
Choose a problem your team recognises. We can help assess how UNS may support it.