Skip to main content
Captia Technology

What is OPC-UA

Definition

What is OPC-UA?

Vendor-neutral industrial communication standard (IEC 62541) for exchanging data between OT equipment and IT systems. Captia Connect uses it as the preferred protocol for normalised ingestion.

OPC-UA (OPC Unified Architecture) is a vendor-neutral international industrial communication standard (IEC 62541) for exchanging data between plant equipment (PLCs, sensors, machines) and information systems such as the ERP or analytics platforms, with built-in security, semantics and a shared data model.

How OPC-UA works

OPC-UA defines both a transport protocol and an information model. An OPC-UA server (typically the PLC, the machine or a gateway) exposes variables that clients read, write or subscribe to. Each variable carries type, units, hierarchy and metadata, so consumers understand what they are reading without manual mapping tables. Security (authentication, encryption, message signing) is part of the standard, unlike older protocols such as Modbus.

Why it matters for industrial SMEs

For an SME running machines from several vendors, OPC-UA is the cleanest way to unify data capture without proprietary drivers per device. Most modern PLCs ship with an OPC-UA server, and legacy equipment can be exposed through a gateway. That feeds dashboards, OEE calculation or quality systems through one read mechanism, and allows controlled write-back of recipes and setpoints.

OPC-UA is a core piece of OT/IT convergence. It coexists with Modbus on legacy equipment and complements MQTT and the Unified Namespace, often processed close to the machine via edge computing. It supersedes classic OPC DA, tied to COM/DCOM on Windows, and underpins sector models such as EUROMAP 77 in plastics injection moulding.

Related terms

Related solutions

How we apply this concept in practice:

Frequently asked questions

What is the difference between OPC-UA and classic OPC?
Classic OPC (OPC-DA) depended on Windows technologies (COM/DCOM). OPC-UA is cross-platform, runs over TCP or WebSockets, adds built-in security and a semantic information model, so it can run on PLCs, Linux gateways or the cloud.
Does OPC-UA replace MQTT?
No: they solve different problems. OPC-UA structures data reads and writes at the source; MQTT transports data publish/subscribe to many consumers. In many architectures both coexist: OPC-UA at the machine, MQTT as the bus towards IT.
Can legacy machines use OPC-UA?
Yes, through an industrial gateway that reads the equipment’s original protocol (Modbus, PLC signals, proprietary buses) and republishes it as an OPC-UA server. The machine itself is untouched; an external translation layer is added.
Is it safe to expose plant data over OPC-UA?
The standard includes client authentication, encryption and message signing. Real security depends on configuration: managed certificates, network segmentation and restricted write permissions are essential practices in any deployment.

Keep reading

This term belongs to the scope of Captia Connect. You can find every other definition in the full glossary.