Industrial IoT (IIoT) requires clear data structuring. With the growing number of connected devices and edge nodes, the OPC UA (Open Platform Communications Unified Architecture) standard is becoming a key tool for creating a shared information space between OT equipment and IT infrastructure.
Challenges of industrial interface fragmentation
The use of heterogeneous protocols and legacy equipment creates a complex web of point-to-point connections. This leads to three main challenges:
- loss of data context (lack of metadata and units of measurement);
- architectural fragility when replacing controllers or changing register maps;
- low security level of legacy interfaces that lack built-in encryption.
As a result, engineers are forced to spend time manually aligning reference books and maintaining converters instead of performing analysis.
Benefits of the OPC UA standard
OPC UA addresses fragmentation through an object-oriented information model (Address Space). Instead of flat address tables, devices describe themselves through a structure of nodes containing data type, units of measurement, timestamp, and quality status. The standard is cross-platform and runs on Linux, Windows, RTOS, and edge gateways, unifying new IIoT devices and legacy controllers.
Integration architecture and security
The data flow typically travels from equipment through edge gateways to the OPC UA server, and then to SCADA, MES, ERP systems, and analytics platforms. To secure information within the framework of ISA/IEC 62443 standards, it is recommended to:
- place OPC UA servers in a demilitarized zone (DMZ) to prevent direct access to equipment;
- use secure security profiles with encryption and signing (e.g., Basic256Sha256);
- manage the lifecycle of digital device certificates and restrict access permissions.
Preparing data for Edge AI
Implementing artificial intelligence at the edge (Edge AI) and predictive maintenance requires clean data. OPC UA provides a normalized information layer, capturing data provenance, timestamps, and quality codes. This enables the effective application of risk management methodologies such as NIST AI RMF 1.0.
In large-scale projects, modern low-code platforms (such as UnityBase) are used to build an enterprise metadata layer and manage business processes, integrating with enterprise applications and databases without directly interfering with the low-level OT layer.
The effect on the market
Adopting the OPC UA standard enables businesses to transition from fragmented, fragile point-to-point connections to a unified, secure data architecture. This significantly reduces maintenance costs, prevents data loss, and establishes a reliable foundation for deploying advanced analytics, Edge AI, and predictive maintenance across the enterprise.
How to respond
- Map legacy device registers to the OPC UA object-oriented Address Space to preserve data context and metadata.
- Deploy edge gateways to route data flows from legacy controllers to OPC UA servers.
- Isolate OPC UA servers within a demilitarized zone (DMZ) and enforce secure profiles like Basic256Sha256 for encryption and signing.
- Integrate low-code platforms like UnityBase to manage the enterprise metadata layer and business processes without interfering with low-level OT systems.
Prepared by a Software Ukraine member. Original publication.