What is OPC UA? The industrial data transfer standard explained
Summary
OPC UA software connects automation systems securely. Learn what OPC UA is, how it works and why it is the industrial data transfer standard.
A Siemens PLC and an ABB system do not exchange data with each other without a shared protocol. Valmet process control uses a different protocol from a Beckhoff I/O system. An industrial plant can have dozens of equipment manufacturers, and historically every one of them has wanted to lock the customer into its own ecosystem. The OPC UA protocol was created to solve exactly this problem — and it has become the single most important standard in industrial digitalisation.
In this article I explain what OPC UA means, how it works in practice, and why every automation engineer, plant manager and IT lead should understand it. I also go through how modern OPC UA software such as DataPortia™ uses the protocol to collect and analyse industrial data.
What is OPC UA — a brief history and definition
Definition
OPC UA (Open Platform Communications Unified Architecture) is an open data transfer standard for industrial automation systems, developed by the OPC Foundation. It is a platform- and vendor-independent protocol that enables secure, reliable and semantically rich data transfer between machines, systems and cloud services.
The history of OPC starts in 1996, when the Windows-based OPC Classic (DA, HDA, A&E) was standardised. Classic OPC was, however, tied to Windows and to COM/DCOM technology — it worked, but it did not scale to the modern world.
OPC UA (IEC 62541), published in 2008, rebuilt the standard completely:
- Platform-independent: runs on Windows, on Linux, on embedded systems and in the cloud
- Built-in security: encryption, authentication and certificates as part of the standard
- Semantic information model: data is not just numbers — it carries meaning and structure
- Scalable: works as well inside a PLC as it does in a cloud integration
How does the OPC UA protocol work in practice?
OPC UA is built on a client-server architecture in which an OPC UA server (typically a PLC, SCADA or DCS) publishes information in an address space, and an OPC UA client requests or subscribes to that information.
Subscriptions
The client subscribes to the measurement points it needs — the temperature of a boiler, the speed of a pump or the position of a valve, for example. The server sends updates automatically only when a value changes or the configured time window elapses. In terms of network traffic this is a very efficient approach.
History read
The OPC UA Part 11 standard allows history to be read directly from the server's own archive. If the automation system has a data store of its own, missing data can be brought in afterwards without losing a single value.
Alarms and events (Alarms & Conditions)
OPC UA Part 9 covers the handling of alarms and conditions. Alarm data — source, severity, timestamps and acknowledgements among others — transfers in a standardised form. This makes it possible to manage alarms from several manufacturers' systems in one consistent way.
In practice, OPC UA software acts as a client: it connects to the PLC or the SCADA system, browses the node tree of the address space, selects the measurement points wanted and opens a subscription. After that the data flows automatically — once a second, once a minute or in real time.
Why OPC UA is the industrial data transfer standard — 5 reasons
The success of OPC UA is no accident. It is an answer to a genuine problem, and its design reflects the real needs of modern industry.
1. Vendor independence
OPC UA runs on the Siemens S7-1500, on the ABB AC500, in the Valmet Damatic system, in Beckhoff TwinCAT and in hundreds of other devices. One piece of OPC UA software connects the whole plant — no matter how many different manufacturers' devices you have.
2. Built-in security
OPC UA uses X.509 certificates, TLS encryption and user authentication. A connection is established only between certified parties. This is critical in industrial environments, where cyber security is a central requirement for OT (Operational Technology) networks.
3. Semantic information model
In OPC UA every node has a name, a type, a unit, a description and a hierarchical position in the address space. Data is not just a number — it is "boiler 2 outlet temperature (°C)". That makes the data considerably easier to understand and to analyse.
4. Reliable data transfer
OPC UA supports automatic reconnection, acknowledgements and duplicate filtering. If the connection drops, OPC UA software resumes automatically from where it left off — with no data loss, as long as the server stores history.
5. Industry 4.0 and IIoT compatibility
Every significant Industry 4.0 standard — RAMI 4.0, Asset Administration Shell, UMATI — is built on OPC UA. When you build OPC UA-based data acquisition now, you are ready for future integrations without rebuilding.
OPC UA software in practice: what does an industrial plant need?
Making use of the OPC UA protocol requires client-side software. The most direct route is ready-made OPC UA software that handles the connection, the node tree browsing, the subscriptions and the data storage — without you having to write a line of code.
| Feature | In-house OPC UA implementation | Ready-made OPC UA software |
|---|---|---|
| Deployment time | Weeks to months | Hours |
| Certificate management | Manual | Automatic |
| Subscriptions and buffering | Build it yourself | Built in |
| Database integration | Build it yourself | Automatic |
| Reporting and visualisation | Not included | Included |
| Redundancy (primary/secondary) | Build it yourself | Built in |
| Maintenance and updates | Your own responsibility | Handled by the supplier |
DataPortia is one example of ready-made OPC UA software: it connects to any OPC UA-compatible automation system, browses the node tree automatically, and starts storing data in a TimescaleDB time-series database — within minutes of installation.
- 2 000+
- measurement points per second — DataPortia handles the data from more than ten simultaneous OPC UA connections in a single database without performance problems.
Practical example: a process industry plant adopts OPC UA
Imagine a chemical plant with three process lines, several reactors and hundreds of measurement points. The plant runs Siemens and ABB automation systems alongside an older SCADA system that does not support integration with newer systems.
A chemical plant: OPC UA deployment
Case example
Starting point: data is collected manually into monthly Excel reports. Process deviations are not detected in real time. Energy consumption monitoring rests on calculated estimates.
Before OPC UA software
- The Siemens and ABB systems do not exchange data with each other
- Alarm data collected by hand — no delay log
- The energy efficiency report is compiled by hand once a month
- The cause of a process deviation emerges only days later
- Retrieving historical data takes hours
After OPC UA software
- All systems connected to a single DataPortia instance
- Alarms are stored automatically with their timestamps
- The energy report is generated automatically every day
- A process deviation shows up on the trend chart within seconds
- History read brings in 2 years of data at once
Deployment ran in three stages: first the OPC UA servers were enabled on the PLCs (on most modern PLCs this is a standard feature), then DataPortia was installed on the plant's server, and finally the measurement points were selected in the browser-based user interface. The whole project took two days.
OPC UA vs. other protocols: why choose OPC UA?
There are other industrial data transfer protocols on the market. Why choose OPC UA?
| Protocol | Strengths | Weaknesses | OPC UA support |
|---|---|---|---|
| OPC UA | Open, secure, semantic, vendor-independent | More complex to configure than simple protocols | Native |
| Modbus TCP | Simple, widely supported | No security, no semantics, register reads only | Gateway required |
| MQTT | Lightweight, suited to IoT environments | No semantics without additional specifications (Sparkplug B) | OPC UA over MQTT |
| Profinet / EtherNet/IP | Fast real-time control | Not designed for data acquisition or history storage | Gateway at PLC level |
| ODBC/SQL direct read | Easy if the SCADA supports it | Requires a database connection, no real-time support | Not applicable |
In summary: OPC UA is not the only industrial protocol, but it is the only one that combines openness, security, semantics and vendor independence into a single standard. That is why it is the international standard IEC 62541 and the basis of Industry 4.0.
Summary: OPC UA software is the foundation of data acquisition at an industrial plant
OPC UA is the infrastructure of industrial digitalisation — much as TCP/IP is the infrastructure of the internet. It is not a trend or marketing jargon but an international standard on which all modern industrial data transfer is built.
If your plant has automation systems that support OPC UA — and in 2026 equipment that is effectively the norm — you are one step away from systematic data acquisition. All you need is OPC UA software that makes the connection, stores the data and turns it into something useful.
DataPortia is Finnish OPC UA software designed for industry. It installs on a Windows or Linux server, brings every OPC UA device into one view and stores the data in a local TimescaleDB database. No cloud. No recurring licence fee per measurement point. Just reliable, fast data acquisition.