OPC UA.
OPC UA, OPC Unified Architecture is a platform-independent, service-oriented architecture for industrial data exchange. It is the standardized way to connect controls systems to enterprise IT, MES, historians, and analytics platforms. Unlike its predecessor OPC Classic, which depended on Microsoft DCOM, OPC UA runs over TCP and HTTP with built-in security and information-modelling.
What OPC UA means.
OPC UA is the protocol that connects the control layer of a plant to everything above it. The historian, the manufacturing execution system, the maintenance and analytics platforms, and the enterprise systems beyond them. Its predecessor, OPC Classic, did the same job but depended on Microsoft DCOM, which tied it to one operating system and made it hard to secure or to route across a network boundary. OPC UA, standardized as IEC 62541, replaces that with a platform-independent, service-oriented architecture that runs over TCP with certificate-based authentication and optional message encryption built in rather than bolted on. What makes it more than a transport is its information model. Instead of exposing a flat list of tag values, an OPC UA server presents an addressable namespace where each point carries its data type, engineering unit, description, history, and access rights, so a client can browse the structure of the plant rather than being handed a pre-agreed tag map. That is why it has become the standard north-bound interface that every major control platform implements, and the practical convergence layer at the OT, IT boundary. It sits above the field-device layer, not in place of it. HART, Profibus, Profinet, and EtherNet/IP continue to carry the signals from the instruments, and OPC UA carries the supervisory picture upward. The tag set it exposes is ultimately the same dataset the I/O list defines, propagated up through the controller and the historian.
What OPC UA actually does
It defines an information model. An object-oriented namespace where every controls data point lives at an addressable node with type information, units, descriptions, history, and access permissions. A client, HMI, historian, MES, cloud connector connects to a server, DCS, PLC, gateway and traverses the namespace, subscribing to data changes or method calls. Built-in security includes mutual TLS, certificate-based authentication, and signed, encrypted messaging.
Why OPC UA dominates the OT, IT boundary
Modern manufacturing and process plants run dozens of disparate controllers, multiple DCS vendors after acquisitions, third-party skid controllers, vibration-monitoring servers that need to expose data to higher-level systems. OPC UA is the protocol every major DCS, PLC, and historian vendor implements as the standard north-bound interface. MES, ERP, cloud platforms, and analytics tools consume OPC UA. It is the practical convergence layer between OT and IT.
Common questions
Is OPC UA replacing fieldbus protocols.
What's the difference between OPC UA and MQTT.
How does OPC UA handle security between OT and IT networks.
Run it on your drawings.
Upload a drawing set, get every document populated and classified, export to the format your team uses.