Unified Namespace
3 min
what is a unified namespace (uns)? a unified namespace (uns) is an architectural pattern for industrial data integration it defines a single, centralised logical space where every data producer in a plant (sensors, machines, controllers, business systems) publishes its data, and every consumer reads from that same space there is no point to point wiring between systems all data flows through one shared namespace (most commonly a shared centralised message broker) topics in the uns follow a hierarchical naming convention that reflects the physical and logical structure of the plant, commonly based on the isa 95 enterprise hierarchy enterprise / site / area / line / workcell / device / datapoint this naming structure makes data self describing and discoverable any consumer can browse the namespace to understand what data exists, where it comes from, and what it represents — without needing to consult external documentation or negotiate a private interface with the producer the uns acts as the single source of truth for the current and historical state of the plant why use a uns? traditional manufacturing it landscapes grow into a tightly coupled mesh of point to point integrations each system talks directly to the systems it needs scada reads from plcs, mes reads from scada, erp reads from mes, reporting reads from everything every new system added to the plant requires new integrations with every existing system it needs to interact with the result is an integration architecture that is fragile, expensive to change, and nearly impossible to scale the uns pattern solves this by inverting the relationship systems do not talk to each other; they all talk to the centralized namespace problem (point to point) solution (uns) n systems → n² potential integrations n systems → n integrations (each connects once to the uns) adding a new system requires re wiring existing ones new systems subscribe to existing topics; nothing else changes data is siloed per system all data is available to all authorised consumers integrations are fragile and version sensitive producers and consumers are fully decoupled beyond integration simplification, the uns enables real time visibility any system can subscribe to any topic and receive data as it is produced, without polling digital twin foundation the uns holds the live state of the plant, making it the natural data source for digital twin implementations ai and analytics readiness all data flows through a single point, making it straightforward to connect analytics engines, machine learning models, or agentic ai systems without custom data pipelines for each scalability new production lines, new sensors, and new systems are added by publishing to new topics — no architectural changes required
