Validate OPC UA Address Spaces Before Integration

An OPC UA server can be reachable, browsable, and able to return values while its address space is still modeled incorrectly. A mandatory component may be missing, a Variable may use the wrong DataType, or a node may appear at the wrong place in the hierarchy. These problems are easy to overlook in a client browser, but they often surface later when another application relies on the information model instead of only reading individual NodeIds.

Introduction

The Industrial Internet of Things (IIoT) is at the forefront of a significant transformation in the manufacturing sector, driven by the convergence of advanced technologies, hybrid intelligent edge solutions, and AI. This evolution is not merely about adopting new technologies but about redefining how manufacturing processes communicate, interact, and operate in a connected world. This blog post explores these pivotal advancements, highlighting their role in streamlining operations and fostering a more agile, efficient, and interconnected manufacturing environment.

In this comprehensive tutorial, we will explore the process of OPC UA data modelling. The tutorial will cover modeling a machine, creating an OPC UA server to simulate machinery values, reading data from the server and transmitting it downstream (e.g., to the cloud), and detecting anomalies.

What is OPC UA?

To answer this question, I like to cite Stefan Hoppe the President and Executive Director of the OPC Foundation:

OPC Unified Architecture (OPC UA) is the information exchange standard for secure, reliable, manufacturer- and platform-independent industrial communications. It enables data exchange between products from different manufacturers and across operating systems. The OPC UA standard is based on specifications that were developed in close cooperation between manufacturers, users, research institutes and consortia, in order to enable consistent information exchange in heterogeneous systems.