Components of an Industrial Unified Namespace (UNS)


Which connectors does i-flow support?

In a rapidly evolving world of Industrial IoT, the concept of the Unified Namespace (UNS) has established itself as a strategic step towards efficient data management and interoperability. Successful implementation of the concept includes the design and development of the UNS architecture. The following functional components are crucial when implementing an Industrial Unified Namespace (UNS):

Components of an Industrial Unified Namespace (UNS)


Connectivity Layer: Integrate Everything to your UNS

The connectivity layer is of crucial importance as a component of an Industrial Unified Namespace (UNS), as this layer serves as a fundamental element for the seamless integration of various components within the industrial ecosystem. In industrial environments, various IT systems, machines, sensors and devices work with different protocols and communication standards. The connectivity layer acts as a universal translator that enables these systems to communicate effectively with the Industrial UNS.


Harmonization Layer: The Real Hero for a scalable UNS architecture

The harmonization layer is the real hero and forms the backbone of a scalable UNS architecture. This is because in the heterogeneous world of OT systems, data sources speak different languages and work with manufacturer-specific data structures and semantics. Without their harmonization, no UNIFIED namespace – and you end up with individual OT / IT integration projects again. Just like the old world of point-to-point integration of OT / IT systems. By creating a unified language space, the Harmonization Layer eliminates potential data chaos and enables consistent and effective data processing within your UNS.


Message Broker: Core Component of a Industrial Unified Namespace (UNS)

In the field of industrial communication, MQTT and/or Kafka brokers form the core of a UNS architecture. The message brokers enable bidirectional OT/IT communication in “real time”. The lightweight nature of MQTT is suitable for connecting IoT devices such as machines, while Kafka provides a reliable backbone for event processing and streaming analytics.


Microservices: Scalability despite dynamic use-cases

Microservices form an agile data processing layer within the UNS architecture. They divide complex functions into modular and manageable components. Each microservice fulfills a specific function (e.g. the calculation of a live OEE), which keeps the architecture flexible, efficient and easy to maintain. This makes it possible to react to changes, for example in the requirements of agile data analytics projects.



Each component of the UNS architecture plays an important role in the implementation of a scalable Industrial Unified Namespace (UNS) architecture. The connectivity layer ensures the seamless integration of your OT and IT systems. The harmonization layer ensures standardization, the message broker enables real-time communication and the microservices ensure scalability despite dynamic use cases. A basic understanding of the importance of these critical components is the basis for a robust and sustainable implementation of an Industrial Unified Namespace (UNS) architecture.


i-flow – Unified Namespace (UNS) for the Industrial IoT

The i-flow software offers an Industrial Unified Namespace (UNS) – tailor-made for use in factories. It provides the key components for implementing a UNS architecture.

i-flow Industrial Unified Namespace (UNS)

Connectivity Layer: With over 200 connectors, you can integrate common OT and IT systems into your UNS with just a few clicks – whether in the shopfloor or in IT.

Harmonization Layer: The i-flow software harmonizes and standardizes system interfaces and source data before the data is made available to other systems in the Message Broker.

Message-Broker: i-flow provides a fully integrated and powerful MQTT broker. If the infrastructure already exists, the software supports existing message brokers such as MQTT and Kafka.

Microservices: Combine, aggregate and transform OT and IT data via i-flow microservices. Example: Instead of a cycle time, a machine only provides a time stamp at the start and end of the process. Using an i-flow microservice, the cycle time can be calculated and published in standardized form in the UNS.

Try it out now - free trial version

Take a test and see for yourself the unlimited possibilities that i-flow offers. 30 days free trial, on your systems.

Your question has not been answered? Make a non-binding inquiry now.

Our data policy applies.