OPC Blog

What is OPC UA? OPC UA (Open Platform Communications Unified Architecture) is a modern, platform-independent machine-to-machine communication protocol designed for industrial automation. It enables secure, reliable, and standardised data exchange between devices, machines, control systems, and enterprise applications from the factory floor all the way to the cloud. Developed by the OPC Foundation and standardised as IEC 62541, OPC UA has become the de-facto communication standard for Industry 4.0, IIoT (Industrial Internet of Things), and digital transformation programmes across manufacturing, energy, oil and gas, pharmaceuticals, and critical infrastructure. Unlike legacy industrial protocols, OPC UA is: Platform-independent: runs on Windows, Linux, embedded devices, and cloud infrastructure Security-first: built-in encryption, authentication, and data integrity from the ground up Semantically rich: uses an object-oriented information model that describes not just data values but their meaning and relationships Scalable: from 8-bit microcontrollers to enterprise servers and cloud platforms Interoperable: a single standard that replaces dozens of proprietary protocols In plain language: OPC UA is the common language that allows a Siemens PLC, a Rockwell SCADA system, a cloud analytics platform, and an AI model to all understand each other - securely and without custom integrations for every pairing. Discover our OPC UA Products The history of OPC UA OPC Classic (1996–2006) was the original OPC standard. It solved a real problem allowing industrial devices from different manufacturers to share data - but it had a fundamental flaw: it was built on Microsoft's COM/DCOM technology, which meant it was Windows-only, hard to secure, and difficult to use across firewalls or wide-area networks. As Industry 4.0 began to take shape in the mid-2000s, manufacturers needed something better. The OPC Foundation responded by designing OPC UA from scratch with a clear mandate: keep everything that worked about OPC Classic, discard the Windows dependency, and make security non-negotiable from the first line of code. The core OPC UA specification (Part 1) was published in 2008. The protocol has been continuously updated since then, with major additions including: PubSub (2018): a publish-subscribe communication model for IIoT-scale deployments OPC UA FX (Field eXchange, 2023): for controller-to-controller communication at the field level OPC UA over cloud protocols: MQTT, AMQP, Kafka, and REST integrations formalised by the OPC Foundation Cloud Initiative (2024–2026) Today, OPC UA is implemented by thousands of device vendors and software providers worldwide, including Siemens, Rockwell Automation, Emerson, ABB, Beckhoff, and many others. How OPC UA works: architecture explained The protocol uses a service-oriented architecture (SOA) built on two complementary communication models. Client-server model A client application connects to an OPC UA server, requests data, reads or writes values, subscribes to changes, and receives notifications. This is the right model for: SCADA systems reading PLC data in real time MES platforms querying production KPIs Historians archiving process data Applications that need guaranteed, point-to-point delivery Publish-subscribe (PubSub) model Introduced in OPC UA Part 14, PubSub decouples data producers from consumers. Publishers send data to a message broker (MQTT, AMQP, or UDP multicast) without knowing who is listening. Subscribers receive the data they need without connecting directly to the source. This model scales to thousands of endpoints and is ideal for: IIoT sensor networks Cloud data pipelines Edge-to-cloud architectures Large-scale monitoring systems where many consumers need the same data Transport and encoding Transport Use case OPC UA TCP (Binary) High-performance, low-latency connections on local networks HTTPS Internet-facing applications, firewall-friendly WebSockets Browser-based clients and web applications MQTT / AMQP Cloud and IIoT brokered messaging The address space and information model One of OPC UA's most powerful - and often underappreciated - features is its information model. Every piece of data exposed by an OPC UA server lives in a structured address space: a hierarchical, object-oriented model that describes not just values but their types, relationships, methods, and events. This means that when an OPC UA client connects to a server, it can discover what data is available, what it means, and how it relates to other data - automatically and without prior configuration. This is what enables true interoperability between systems from different vendors. The security model Security is not an add-on in OPC UA; it was designed in from the very beginning. This is a fundamental difference from OPC Classic, where DCOM-based communication exposed serious vulnerabilities that are difficult or impossible to remediate without a full protocol migration. Its security architecture operates at three layers: Transport security Every connection uses TLS-equivalent encryption (128-bit or 256-bit AES) to protect data in transit. Messages are also signed, preventing tampering. Three security modes are available: None (for isolated test environments only), Sign, and Sign & Encrypt. Authentication OPC UA supports multiple identity verification methods: Anonymous (suitable only for public read-only data) Username/password with encrypted transmission X.509 certificates the recommended method for production environments, where each client and server holds a cryptographic certificate that must be mutually trusted before a session is established Token-based authentication for integration with enterprise identity systems Authorisation Once authenticated,th protocol enforces role-based access control (RBAC). Different users or applications can be granted different permissions - read-only access to some nodes, read/write to others, no access to sensitive process data. OPC Classic vs. OPC UA: key differences OPC Classic, introduced in the mid-1990s by OPC Foundation, was one of the first standards aimed at facilitating communications in industrial automation. The OPC specifications provided a common interface for data exchange between different systems and devices, enabling interoperability in a heterogeneous environment. What’s OPC? Aspect OPC Classic OPC UA Platform Independence Tied to Windows, based on Microsoft’s COM/DCOM technology Platform-independent, runs on various operating systems including Windows, Linux, and embedded systems Architecture Uses multiple specifications for different functionalities (DA, AE, HDA) Service-oriented architecture (SOA), integrates all functionalities into a single, extensible framework Security Limited security features DCOM presents several security vulnerabilities Comprehensive security features including authentication, encryption, and integrity checks Scalability Not well-suited for large-scale systems Scalable architecture supporting a wide range of devices and applications Information Modeling Basic data structures Advanced information modeling capabilities allowing for complex data structures and relationships Interoperability Compatibility issues with non-Windows platforms and modern IT infrastructures Enhanced interoperability with support for various communication protocols and modern IT systems OPC Classic vs OPC UA Still Using OPC Classic? See how you can secure your communications What industries use OPC UA? OPC UA is used across virtually every sector of industrial automation. The following represent the highest-adoption industries: Manufacturing (discrete and process): The protocol is used to connect PLCs, robots, vision systems, and quality control equipment to MES and ERP platforms. The umati initiative has accelerated its adoption in machine tool manufacturing particularly strongly in Germany and across the EU. Oil and gas: combined with the WITSML companion specification, it enables real-time wellsite data integration. Major operators in North America and the Middle East use OPC UA as the data integration backbone between field systems, historians, and cloud analytics. Energy and utilities: Grid operators and power generation companies use this communication protocol to connect SCADA systems, energy management systems, and smart grid devices. Compliance with NERC CIP in North America and EU grid codes drives OPC UA adoption as a secure alternative to legacy protocols. Pharmaceuticals: FDA 21 CFR Part 11 and EU Annex 11 requirements for electronic records and audit trails align naturally with its security and logging capabilities. Pharma manufacturers in the US and EU use it to integrate batch management systems with process automation. Building automation: The OPC UA for Building Automation companion specification enables HVAC, lighting, access control, and energy management systems to share data on a common platform - a growing requirement for smart building and ESG reporting mandates in Europe and the Middle East. Water and wastewater: Utilities use this protocol to integrate remote telemetry units (RTUs) with central SCADA systems. The protocol's firewall-friendliness makes it practical for geographically distributed infrastructure. How to migrate from OPC Classic to OPC UA Migrating from OPC Classic to OPC UA becomes increasingly essential to leverage modern features like platform independence, enhanced security, and scalability. This transition ensures that systems remain future-proof, interoperable, and capable of meeting contemporary industrial requirements. However, the migration process can seem daunting due to the significant differences between the two standards. To facilitate a smooth and efficient transition from OPC Classic, we provide OPC UA Wrapper, a plug-and-play software product designed for seamless integration. The Wrapper bridges the gap between OPC Classic and OPC UA, facilitating the coexistence of both protocols and allowing organizations to advance industrial communication without disrupting critical processes. Migration Challenges and how the Wrapper addresses them The migration process is not without its challenges. As organizations embark on this migration journey, hurdles such as data mapping, security integration, and protocol interoperability may arise. OPC UA Wrapper is engineered to tackle migration challenges by providing a comprehensive solution and mitigating the complexities associated with such migrations. Challenge Description OPC UA Wrapper Solution Data Mapping intricacies Mapping the addresses spaces of OPC Classic and OPC UA protocols Facilitates data mapping by intelligently bridging the address spaces of OPC Classic servers and OPC UA servers Security Integration Complexities Integrating robust security features during migration can be complex and critical Provides built-in encryption and authentication mechanisms, managing security settings and certificates Protocol Interoperability Concerns Ensuring interoperability between different vendors and vendors and versions due to variations in implementations Uses standardized profiles in OPC UA to facilitate seamless communication between diverse devices and systems Efficient handling of alarms and events Migrating alarms and events to ensure efficient handling and acknowledgement Allows efficient reading and acknowledgment of alarms and events, ensuring smooth transition without disruption, Efficient Handling of Real-time and Historical Data Migrating real-time and historical data efficiently Enables efficient reading and writing of real-time OPC item data and secure handling of historical data operations · Features The OPC UA Wrapper offers comprehensive functionalities to ensure a robust and versatile integration process: COM Server to UA Server: allows Unified Architecture (UA) clients to access classic OPC servers as if they were UA servers UA Server to COM Server: enables classic OPC clients to access UA servers as if they were OPC COM servers Intuitive User Interface: simplifies the migration process with a user-friendly interface for easy configuration and integration management Run as Windows Service: operates in the background as a Windows service OPC UA Security: provides security features such as secure communication channels, session tracking, encryption, and message signing, with configurable security modes and user identity tokens Log Capabilities: records messages with different logging levels for tracking execution and diagnosing problems, aiding in troubleshooting Read and Write OPC Item Values: allows easy reading and writing of OPC item values for enhanced control and monitoring Historical Data Read Capability: supports reading historical data for analysis and insights from past industrial processes, enhancing industrial communication capabilities Reading and acknowledging alarms and events: real-time monitoring and alerting by facilitating the mapping of alarms and events between OPC Classic Server and the OPC UA information model, enabling efficient management and timely acknowledgment The software supports multiple OPC specifications, including OPC Data Access (DA), OPC Historical Data Access (HDA), and OPC Alarms & Events (AE), providing a comprehensive solution for various industrial requirements. Watch Demo Videos OPC UA and the cloud, Azure, AWS, and IIoT OPC UA was designed with cloud connectivity in mind particularly through its PubSub model and support for standard messaging protocols like MQTT and AMQP. OPC UA to Azure IoT Hub: The OPC UA IoT Broker pattern allows OPC UA servers on the plant floor to publish data directly to Azure IoT Hub, where it becomes available to Azure Stream Analytics, Azure Digital Twins, Power BI, and AI/ML services. OPC UA and MQTT Sparkplug B: The MQTT Sparkplug B specification defines how OPC UA data should be structured when published over MQTT enabling consistent, self-describing payloads that any Sparkplug-aware broker or cloud platform can consume. This combination is increasingly the standard architecture for brownfield IIoT deployments. OPC UA and digital twins: Microsoft Azure Digital Twins, AWS IoT TwinMaker, and other digital twin platforms can consume OPC UA data directly. The OPC UA information model maps naturally to digital twin concepts - nodes become assets, attributes become properties, and methods become capabilities. AI and machine learning integration: OPC UA data, once streamed to a cloud data lake or time-series database, becomes the training and inference data for predictive maintenance models, anomaly detection systems, and process optimisation algorithms. The semantic richness of the OPC UA information model - where data carries meaning, not just values - makes it significantly more valuable for AI applications than raw, unlabelled process data. Frequently asked questions about OPC UA

Simplify OPC Unified Architecture in Heterogeneous Environments

What is OPC UA? A Complete Guide for Industrial Automation

Partnership & Recognition

Get in Touch

Explore More