Unified Namespace
Set up the Unified Namespace with a single click — message broker and protocol converters included.
Benefits
Simplify Integration: Centralize all real-time data into a single source of truth.
Reduce Maintenance Costs: Eliminate complex point-to-point system connections.
Minimize Vendor Lock-In: Use an open, standard-based message broker architecture.
Features
Centralized Real-Time Data Hub
The Unified Namespace (UNS) acts as a central hub where all devices and applications publish and subscribe to real-time data. This event-driven architecture prevents “spaghetti diagrams” while enabling real-time data exchange (compared to point-to-point connections or using a database/historian).
Protocol Converters
Connect the Automation Pyramid to the UNS using our Protocol Converter. Structure and re-format the tags to your individual asset structure.
Combined MQTT and Kafka Architecture
Our architecture leverages MQTT for device communication and Kafka for scalable data processing, combining the strengths of both technologies.
- MQTT: Ideal for reliable, lightweight communication with devices. We include HiveMQ
- Kafka: Suitable for high-throughput stream processing and data analytics. We include Redpanda
Data is automatically bridged between them using “data bridges” (see also Data Flow Components).
Flexible Data Model
Our UNS uses a topic structure based on the ISA-95 standard, providing consistency while allowing flexibility to adapt to your specific asset hierarchy.
Topic Structure:
umh.v1.<enterprise>.<site>.<area>.
<productionLine>.<workCell>.<originID>.
<schema>.<schema-specific>
You can customize this hierarchy to match industry-specific models, such as the KKS system in power plants or your individual asset ID in your SAP, ensuring the data model fits your organization’s needs.
Tag Browser for Easy Navigation
The Tag Browser displays the tag/topic structure in a hierarchical view from all of your UMH instances. It validates data against known schemas and highlights errors, and for known schemas will also visualize and provide you the history of them. For _historian, it will also generate the SQL query for you so that you can fetch the data from the Historian. Last but not least, it will show the “raw” information on how the message actually looks in MQTT and Kafka.
Integration with Historian
Data sent using the _historian schema is automatically stored in the UMH Historian (TimescaleDB), enabling long-term storage and analysis of historical data.
Management Console
Accessible
Unite all data in a single point with our real-time and event driven architecture: the Unified Namespace
Manageable
Gain full control and transparency over your IT and OT systems
Resilient
Built with scaleable & proven cloud native technologies on top of established automation standards
-min.webp)
-min.webp)
