OPC is the glue that lets industrial software talk to devices from any vendor. But there are two generations - the older OPC DA and the modern OPC UA - and the difference is significant for security, platform support, and where your data can go. This guide explains what changed and why it matters.
The short answer: OPC DA (Data Access) is the original OPC standard, built on Microsoft Windows COM/DCOM - Windows-only and awkward to secure across networks. OPC UA (Unified Architecture) is the modern successor: cross-platform, firewall-friendly, and secure by design, with richer data modeling. New systems use OPC UA.
OPC DA (often called "OPC Classic") was a breakthrough: a common way for HMI and SCADA software to read tags from any compliant device driver. But it was built on Microsoft COM/DCOM, which ties it to Windows and makes cross-network, cross-firewall communication difficult and insecure to configure. It works, and enormous installed bases still run on it, but it shows its age.
OPC UA was designed to fix DA's limitations. It is platform-independent (runs on Windows, Linux, embedded devices, and in the cloud), uses standard networking that traverses firewalls cleanly, and builds security in - authentication, encryption, and signing. It also adds a richer information model, so data carries structure and context, not just flat tag values. For any new SCADA integration, OPC UA is the standard to target.
| Dimension | OPC DA | OPC UA |
|---|---|---|
| Foundation | Windows COM/DCOM | Cross-platform, standard networking |
| Platforms | Windows only | Windows, Linux, embedded, cloud |
| Security | Weak; hard to secure over networks | Built-in auth, encryption, signing |
| Networking | Firewall-hostile (DCOM) | Firewall-friendly |
| Status | Legacy (large installed base) | Modern standard for new systems |
OPC DA is the legacy standard built on Windows COM/DCOM - Windows-only and hard to secure across networks. OPC UA is the modern successor: cross-platform, firewall-friendly, secure by design, with richer data modeling. New systems use OPC UA.
Not directly - they are different technologies. But OPC UA wrappers and gateways exist that expose legacy OPC DA sources over OPC UA, so you can modernize connectivity without ripping out old servers.
For anything new, OPC UA - it is cross-platform, secure, and cloud-ready. OPC DA remains common in legacy Windows installations, but its DCOM foundation makes it a poor choice for new or networked integrations.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix ingests OPC UA (and OPC DA via a gateway) - bring modern, secure device data into a cloud dashboard.