The unified namespace (UNS) is a hot topic in manufacturing right now, largely because it is a key component to digital transformation success. We’ll explain what UNS is in this blog and why it is so important. At a high level, it is about data, integration, and communication.
Data, Integration, and Communication
Data is at the center of all digital transformation projects and initiatives. The aim is to make better use of your organization’s data to help achieve operational goals. Some examples include:
- Optimizing processes, including digitalizing processes and transitioning from paper to glass.
- Improving data-driven decision-making.
- Facilitating automated decision-making.
- Enhancing the visibility of your operations.
- Enabling predictive analytics and scenario modeling.
Digital transformation success relies on the integration of data. Depending on the project, different machines, devices, endpoints, applications, platforms, and systems must be integrated so data can be exchanged, accessed, and used.
The problem is that integrating data using traditional approaches is not as efficient and effective as it could be. UNS is the solution.
So, what is UNS?
In a sentence, UNS is an industrial architecture approach that simplifies and optimizes the integration of data through two core principles: centralization and standardization.
The Traditional Approach
Let’s start with an overview of the traditional architecture approach. The technology stack in manufacturing organizations has traditionally been based on the ISA-95 model.
This is a model that has served manufacturers well for years, facilitating process improvements and enhancing automation. Technologies have evolved, however, as have business expectations and market conditions.
A data-driven approach to managing operations is today’s reality, and there is one key feature of the traditional model that makes that difficult to achieve. That feature is the hierarchical structure of the traditional model, where data can only move one layer at a time.
To integrate components in the stack using a hierarchical structure requires point-to-point connections and lots of them.
Limitations of the Traditional Model
To fully understand the importance of UNS, it is helpful to first look at the limitations of the traditional model described above. Those limitations include:
- Multiple point-to-point connections require engineering expertise while often adding layers of complexity.
- The creation and maintenance of multiple point-to-point connections is costly.
- It is expensive and difficult to scale using the traditional model.
- Data can be incomplete or inaccurate.
- Data formats differ across the various levels, so data must be converted, multiple times in some situations.
The UNS Architectural Approach Explained
In a UNS architecture, there is a single data environment that can be accessed by all components – systems, machines, applications, endpoints, etc: