Are you using the unified OT data layer to bridge the natural gap between IT and OT?

 

Unified data layer insights

• OPC Foundation provides the OPC Unified Architecture (OPC UA) basic information model.

• A unified data layer for operational technology use should have five basic functions.

• Unified operational technology data layer software can provide easier integration among OT, IT and cloud resources.

---

OPC Foundation provides the OPC Unified Architecture (OPC UA) basic information model.

A unified data layer for operational technology use should have five basic functions.

Unified operational technology data layer software can provide easier integration among OT, IT and cloud resources.

As information technology (IT) and operational technology (OT) have long been independent of each other, there is a “natural gap” between the two, and convergence is not an easy task. Recently, Matrikon, a company that has been focusing on OPC data communication for more than 20 years, has proposed the concept of Unified OT Data Layer (UODL), which adds a data layer between IT and OT to bridge that natural gap between IT and OT.

The convergence of IT and OT makes it necessary for OT data to flow between the various layers of the enterprise, so interconnection, interoperability and semantic interoperability between IT and OT have become an inevitable requirement.

“When organizations need to rely on data to make decisions, you want to make sure that everyone has access to real-time or near-real-time accurate data to make decisions, rather than waiting a long time for reports and then trying to figure out what’s going on,” said Darek Kominek, marketing director of Matrikon. He also suggested that one of the most important aspect of data is to have contextual meaning, which means it must have semantics, otherwise the data will have no meaning.

OPC Unified Architecture (OPC UA) provides a basic information model

To make the data semantic, OPC Unified Architecture (OPC UA) provides a basic information model, including the semantics transmitted by the underlying bus that can be defined according to unified standards, and vertical industry information models can also be collaborative. The infrastructure of OPC UA includes several levels of information models, including embedded information models, industry information models and supplier information models. These information models have standardized encapsulation of data at different levels, and users can even create their own information models.

But with it, more devices include OPC UA servers for external access. Although using physical devices such as OPC UA gateways can integrate data, this solution is not suitable for situations where multiple OPC UA servers are located in multiple locations, and it also incurs additional equipment installation and maintenance costs. More importantly, accessing source data directly at all levels, or uploading OT data directly to the cloud, are extremely unsafe practices.

Therefore, Kominek proposed adding a unified OT data layer (UODL) so that OT data can be aggregated on a platform in the form of OPC UA open standards, and people at all levels of the enterprise can access this platform to obtain valuable data with semantics.

Not only that, with this UODL, data maintenance and upgrading also will become easier. Users can easily replace data sources by updating the data model to make the view of the address space meet the requirements of the updated application.

Five basic functions of a unified data layer

Kominek pointed out that the construction of UODL actually introduces a type of technology called data technology (DT) between IT and OT, which provides UODL with five basic functions:

1. It needs to have connectivity and be able to communicate with underlying data sources.

2. It is necessary to have the ability to integrate and aggregate different data sources into a unified public address space.

3. It is necessary to support the ability to endow and manage data semantics, to present meaningful data to various applications.

4. It is necessary to be able to share information across the entire enterprise, promoting smooth cooperation between IT and OT.

5. It is also easy to integrate with cloud platforms.

 

Unified operational technology data layer software

UODL provides a new approach for the integration of IT and OT. It is no longer just a concept. After more than two years of research and development, Matrikon, with experience in OPC technology, has launched an out-of-the-box UODL platform called Matrikon Data Broker (MDB).

From the beginning of design and development, MDB has integrated every functional module of UODL into every software function of MDB. Kominek said this functionalized design allows users to choose which functional modules to add and retain based on their own project needs and development, helping enterprise users solve OT data challenges at various levels and achieve enterprise-wide OT data communication.

According to Kominek, MDB has been applied in a famous U.S. chemical company, and in less than 12 weeks, has securely connected real-time production data from nine factories around the world to the cloud for later processing and analysis.

Stone Shi is executive editor-in-chief, Control Engineering China. Edited by Mark T. Hoske, content manager, Control Engineering, CFE Media and Technology, mhoske@cfemedia.com.

KEYWORDS

Unified data layer, industrial OT and IT integration

CONSIDER THIS

If OT data integration seems difficult, how can information management among OT, IT and cloud be easier?

ONLINE

See other international coverage at www.controleng.com/international

Do you have experience and expertise with the topics mentioned in this content? You should consider contributing to our WTWH Media editorial team and getting the recognition you and your company deserve. Click here to start this process.