Skip to content
AdminKit

OPC UA

What is OPC UA?

OPC UA, defined in the IEC 62541 series, is an industrial protocol for PLCs, SCADA and sensors with authentication and encryption built in as configurable options -- unlike older protocols such as Modbus or BACnet. AdminKit OT remote access, delivered by Netbase, reaches OPC UA devices outbound-only.

By AdminKit team, Netbase JSC · Updated

OPC UA (OPC Unified Architecture) is an industrial communication standard, defined in the multi-part IEC 62541 series published by the OPC Foundation and issued by IEC, whose Part 1 overview document frames how the rest of the series fits together, for exchanging data between PLCs, SCADA systems, sensors, and other industrial equipment across client/server and newer publish/subscribe models. Unlike older factory-floor protocols such as Modbus/TCP or BACnet, which assumed a physically isolated network and left authentication out entirely, OPC UA’s IEC 62541-2 security model defines authentication, message signing, and encryption as built-in, configurable options an implementer can turn on — though a server can still be deployed with security set to “none” for compatibility, so the standard supporting security doesn’t guarantee a given deployment uses it. OPC UA also defines its own structured, self-describing information model, letting a client discover a device’s variables and their types instead of relying on a fixed, externally documented register map the way Modbus does. Its binary TCP transport, the OPC UA Connection Protocol, has port 4840 registered for it (as opcua-tcp) in IANA’s service name and port number registry. It has become the preferred integration layer for newer industrial and building automation projects precisely because it gives operators a standards-based way to add the authentication older OT protocols never had, provided it’s actually configured rather than left at its most permissive default.

See the full AdminKit glossary for other related terms.

Frequently asked questions

Does OPC UA build in authentication and encryption, unlike Modbus or BACnet?

Yes -- OPC UA's IEC 62541-2 security model defines authentication, message signing, and encryption as built-in, configurable options, though a server can still be deployed with security set to "none".

Who publishes the OPC UA standard?

The OPC Foundation, as the multi-part IEC 62541 series.

How does OPC UA let a client discover a device's data, compared to Modbus?

Through its own structured, self-describing information model, rather than a fixed, externally documented register map the way Modbus does.

Does OPC UA support both client/server and publish/subscribe communication?

Yes, across both older client/server exchanges and newer publish/subscribe models.