Unified Namespace
Prerequisite: Complete the Getting Started guide to see the UNS in action with real devices and data.
The Unified Namespace (UNS) is where ALL your industrial data lives in one organized, accessible place. Instead of hunting through 50 different systems to find a temperature reading, everything flows through one central hub.
The Problem: Spaghetti Diagrams
Traditional manufacturing IT looks like this:
100 devices × 100 systems = 10,000 point-to-point connections
Every new dashboard means updating PLCs. Every new sensor means modifying databases. Every integration breaks when you upgrade. It's a maintenance nightmare that gets worse with scale.
The Solution: One Central Hub
The UNS flips this architecture:
100 devices → 1 namespace ← 100 systems = 200 total connections
All data flows through one place with consistent structure, validation, and access patterns.
How It Works
Publish Regardless
Your PLC doesn't care if anyone is listening. It publishes "pump is running" to the UNS and moves on. When someone needs that data next week, it's already there. No reprogramming required.
Structured Topics
Every piece of data has an address that answers three questions:
WHERE:
enterprise.site.area.line
- the location pathWHAT:
_pump_v1
- the data contract defining structureWHICH:
inlet_temperature
- the specific data point
Result: umh.v1.enterprise.site.area.line._pump_v1.inlet_temperature
Bridges Handle All Data Flow
Data enters and exits the UNS exclusively through bridges. This ensures every message gets proper context, validation, and organization.
From Device to Business
Start simple, add complexity as needed:
_raw
- Mirror device 1:1 for initial exploration and debugging_pump_v1
and similar - Apply business names directly in bridges for production_maintenance_v1
and similar - From stream processors (aggregating device models) OR directly from ERP/MES systems
The progression: Use _raw
temporarily to understand your data, then apply device models directly in bridges for production. Business models can be created by aggregating device models via stream processors OR by connecting directly to business systems like ERP/MES.
Documentation Structure
Topic Convention - How data is addressed in the namespace
Payload Formats - Time-series vs relational message structure
Metadata and Tracing - Original tags and data lineage
Topic Browser - Explore your namespace in real-time
Next Steps
Explore your data: Open the Topic Browser
Connect devices: Create bridges
Model your data: Define data models
Create KPIs: Build stream processors
Last updated