Unified Namespace
The Unified Namespace (UNS) is the core messaging backbone of UMH Core, providing a standardized, event-driven architecture that eliminates point-to-point integration complexity.
Key Concepts
Traditional manufacturing systems create "spaghetti diagrams" with point-to-point connections between every system. The UNS flips this model:
Event-driven: Devices publish data as events happen
Standard hierarchy: Flexible location paths (supports ISA-95, KKS, or custom naming)
Schema enforcement: Data contracts ensure consistent payload formats
Publish-regardless: Producers don't need to know about consumers
Documentation Structure
Overview - Core UNS concepts and benefits
Topic Convention - Hierarchical naming structure (ISA-95 compatible)
Payload Formats - Message structure and data types
Producing Data 🚧 - How to publish data to the UNS
Consuming Data 🚧 - How to subscribe and process UNS data
Related Documentation
Data Modeling - Structure your industrial data with reusable models
Data Flows - Connect external systems via Bridges and Stand-alone Flows
Configuration Reference - YAML configuration for UNS integration
Learn More
For deeper understanding of UNS concepts, see our educational content:
The Rise of the Unified Namespace - Core UNS principles
NAMUR Open Architecture versus Unified Namespace - Industrial standards context
What is MQTT? Why Most MQTT Explanations Suck - MQTT vs UNS comparison
Last updated