OPC UA (Open Platform Communications Unified Architecture) is the OPC Foundation's platform-independent standard, published as IEC 62541, for exchanging industrial data securely together with a description of what the data means. It does not replace PROFINET or EtherNet/IP for hard real-time I/O; it sits above them, linking PLCs to SCADA, MES, historians and cloud platforms. The OPC Foundation released OPC UA in 2008 as a successor to the Windows-only OPC Classic.
What is OPC UA and why does it matter?
OPC UA is a service-oriented architecture that gives every automation vendor a common way to publish and read data. The OPC Foundation lists its design goals as functional equivalence with OPC Classic, platform independence, security, extensibility and comprehensive information modelling. In practice that means a Linux gateway, a PLC, a Windows SCADA package and a cloud service can all talk to one another without custom drivers.
Three properties explain why it became the default IT/OT bridge:
- Platform independence. The Foundation says OPC UA runs on anything from PCs and cloud servers to PLCs and microcontrollers, on Windows, macOS, Android or Linux.
- Information modelling. Data is exposed in an address space of objects, not as anonymous register numbers, so a client can browse to find a motor, its speed and its alarm state.
- Security built in. Session encryption, message signing, X.509 certificate authentication, user access rights and auditing are part of the specification.
How does OPC UA work? Client-server and PubSub
OPC UA offers two communication patterns, and choosing between them is the main design decision.
| Pattern | How it works | Best for |
|---|---|---|
| Client-server | A client connects to a server, browses its address space, then reads, writes, calls methods and subscribes to changes (report by exception) | SCADA, HMI, engineering tools, one-to-one data access with guaranteed delivery |
| Publish-subscribe (PubSub) | Publishers send messages to middleware without knowing who listens; subscribers pick the data they want | Many-to-many distribution, cloud and edge, broker-based IoT |
The OPC Foundation describes PubSub as optimised for many-to-many configurations, in contrast to client-server where each notification is for a single client. Wikipedia lists transport mappings that include UDP, Ethernet, MQTT, AMQP and WebSockets.

What are companion specifications?
Companion specifications are standardised information models for particular industries and devices, so that two vendors describe the same thing in the same way. The OPC Foundation says it offers an overview of 150-plus companion specifications. Several matter to PLC engineers:
- PROFINET. PI and the OPC Foundation published the OPC UA for PROFINET companion specification V1.0 in January 2020, focusing on asset management and diagnostics. PI notes that more than 30 million PROFINET field devices can already supply that information through Identification and Maintenance services.
- CIP / EtherNet/IP. ODVA and the OPC Foundation are working on a companion specification that maps CIP objects to OPC UA so that EtherNet/IP device data reaches OPC UA servers, edge systems and the cloud.
- IO-Link. The IO-Link community has created the OPC Unified Architecture for IO-Link companion specification with the OPC Foundation.
- IEC 61131-3. The Foundation notes a companion specification (OPC 30001) that maps OPC UA services to IEC 61131-3 function blocks so that PLC programs can act as OPC UA clients.
How do you use OPC UA with a PLC?
Many current PLCs can act as an OPC UA server, which is the simplest way to expose controller data. Exact steps differ by vendor, CPU, firmware and engineering-tool version, and some require a licence, so check the manual for your controller. The pattern is the same everywhere:
- Enable the server in the CPU properties.
- Choose security. Use signed and encrypted endpoints and certificate trust lists; avoid the "no security" option outside a lab.
- Decide what to expose. Publish only the tags or data blocks a client needs, ideally as a structured interface, not the whole program.
- Test with a free client. Browse the address space, read a value and confirm that subscriptions work before connecting production systems.
- Document endpoints. Record the endpoint URL (OPC UA endpoints begin with opc.tcp://), certificates and the account used by each client.
Siemens presents OPC UA as converging with PROFINET in its own communication portfolio. If you are learning TIA Portal, the OPC UA configuration screens are a useful next step after basic PLC-to-HMI work.
Where is OPC UA used in industrial IoT?
Typical uses are condition monitoring, energy reporting, quality traceability and remote visibility. A common architecture is PLC, then an edge gateway that is an OPC UA client, then an MQTT or OPC UA PubSub broker, then a historian or cloud analytics service. In every case the PLC keeps the real-time control, and OPC UA carries the data upward. The IO-Link community makes the same point from the sensor end: an IO-Link master with an IIoT interface can pass data to IT systems using MQTT, OPC UA or a REST API.
How do you keep OPC UA secure?
Connecting the plant floor to IT and cloud raises the stakes, so security is part of the design, not an add-on. HMS Networks reported in 2026 that nearly half of survey respondents cite cybersecurity as a top integration challenge, and 93% expect OT cybersecurity to change substantially over the next five years.
- Use OPC UA security policies with signing and encryption, and certificates for every application.
- Segment OT from IT with firewalls and a DMZ; do not expose a PLC server directly to the internet.
- Give each client its own account with the minimum access rights.
- Log and review connections; the specification supports auditing.
- Keep firmware and gateways patched.
For UK readers, the UK Government introduced the Cyber Security and Resilience Bill in November 2025 to update the NIS Regulations 2018. The EU's NIS2 Directive does not apply to UK law directly, although UK firms supplying the EU may still be affected. Check gov.uk for the Bill's latest status.
How do you test an OPC UA connection?
Test in layers, and do not assume the PLC is at fault. First confirm basic network reachability and that the firewall allows the server's port. Then check the endpoint URL and the security policy the server offers; a client that requests a policy the server does not support will be refused. Next, deal with certificates: most connection failures at commissioning are a server that does not yet trust the client certificate, or the reverse, and the fix is to move the certificate into the trusted list on the correct side. Finally, check the user account's rights and that the node you are reading is actually exposed in the address space. A free OPC UA client that lets you browse nodes is the quickest way to separate a PLC configuration problem from a problem in your SCADA or gateway.
Is OPC UA better than MQTT?
They solve different problems and are often used together. MQTT is a lightweight publish-subscribe transport; OPC UA adds an information model, a security framework and services such as browsing and method calls. The OPC UA specification itself defines an MQTT mapping for PubSub, so a plant can publish modelled OPC UA data over an MQTT broker. The IO-Link community makes a related point: its JSON integration is lighter than OPC UA and suits simple REST or MQTT use. Choose OPC UA when semantics, security and vendor interoperability matter most, and plain MQTT when you only need to move simple values cheaply.
How EDWartens can help
The EDWartens UK Professional Module is a five-day live online class in Siemens TIA Portal (PLC, HMI and WinCC SCADA), plus self-paced Basic Engineering with a module on industrial communication protocols. OPC UA server configuration and cloud connectivity are not a dedicated module of the course, so treat this article as a primer for self-study. You can build the underlying skills with the free industrial communication course, the WinCC SCADA course and the OT security simulator. Related reading: IoT and industrial automation and PLC vs SCADA.





