August 11, 2026 · Comparison

OPC UA vs OPC Classic (DA): Why the Upgrade Matters

If you have been in industrial automation for more than a decade, you have fought with OPC DA. The classic COM/DCOM-based protocol that connected SCADA to PLCs worked — eventually — once you convinced DCOM security, firewall exceptions, and the `Everyone`/`Anonymous Logon` permission maze to cooperate on a Windows machine. OPC UA was designed to make all of that go away. It is not a minor revision of OPC DA; it is a ground-up replacement with a different transport, a different security model, and a richer data model.

This guide compares the two so you understand what you gain by migrating. For the UA information model specifically, see OPC UA Information Model; for how UA compares to a lighter alternative, OPC UA vs MQTT.

What Changed

OPC DA (Data Access) is one of the classic OPC specifications, built on Microsoft COM/DCOM. It exposes tags as a flat or lightly structured list and relies on DCOM for remote connections. It is Windows-only and notorious for configuration pain.

OPC UA (Unified Architecture) is a platform-independent, service-oriented protocol. It defines its own binary and HTTP transports, a full address-space information model (objects, variables, methods), and security built into the protocol. It runs on Linux, macOS, embedded controllers, and Windows alike.

One-line summary: OPC DA is a Windows COM API for reading tags. OPC UA is a cross-platform, secure, self-describing protocol with its own transport.

Feature Comparison

Transport

Own binary / HTTP

COM/DCOM

Platform

Cross-platform

Windows only

Security

Built-in (certs, signing, encryption)

DCOM (hard to configure)

Data model

Rich address space (objects, types)

Flat tag list

Self-description

Browse + type system

Browse names only

History / Alarms

Integrated (HDA, A&E)

Separate specs

Firewall friendliness

Single port, optional TLS

Many DCOM ports

Why the Upgrade Matters

No more DCOM. The single biggest operational reason. UA clients and servers talk over one port without the DCOM permission ritual.
Cross-platform. UA servers run on Linux controllers and embedded devices, not just Windows HMIs. Your SCADA is no longer anchored to a Windows server.
Real security. X.509 certificates, mutual auth, signing, encryption — selectable per endpoint. See UA security setup.
Richer data. UA's address space models objects, types, and methods — not just tags. Companion specifications (OPC UA for Machinery, for Robotics, etc.) standardize domain models. See information model.

Coexistence and Migration

Most plants run both for years. Legacy PLCs expose OPC DA through an OPC server (Kepware, Matrikon); a UA wrapper or aggregation server exposes those DA tags as UA nodes so modern UA clients can reach them. New equipment speaks UA natively. The migration path is gradual: expose DA as UA, retire the DA servers as the underlying equipment is replaced, and eventually the DCOM era ends.

Browsing UA From macOS

OPC DA was Windows-only by definition. UA's cross-platform design means a native macOS client can browse and subscribe. MacTools OPC UA Explorer connects to any UA server, browses the address space, subscribes to variable changes, and reads/writes node attributes — native macOS, no Windows, no DCOM.

Browse OPC UA on macOS

MacTools OPC UA Explorer — connect to any UA server, browse the address space, subscribe to variables, read and write nodes. Native macOS app, no DCOM, no Windows.

Get MacTools OPC UA Explorer

Frequently Asked Questions

What is the difference between OPC UA and OPC DA?

OPC DA (Data Access) is the classic COM/DCOM-based OPC specification for reading and writing real-time data, tied to Windows. OPC UA (Unified Architecture) is its replacement: a platform-independent, service-oriented protocol with built-in security, a rich address-space information model, and no dependency on COM/DCOM. UA is not a wrapper around DA; it is a separate, modern protocol stack.

Does OPC UA use DCOM?

No. OPC UA replaces DCOM entirely. Classic OPC (DA, HDA, A&E) relied on Microsoft COM/DCOM for remote connections, which was a notorious source of firewall, authentication, and configuration pain on Windows. OPC UA uses its own binary or HTTP-based transport, so it runs cross-platform without DCOM and without Windows.

Can OPC UA talk to OPC DA servers?

Not directly — they are different protocols. Integration is done with an OPC UA wrapper or companion server that exposes OPC DA tags as OPC UA nodes, or a gateway that bridges the two. Many vendors ship a UA server that aggregates legacy DA servers, letting UA clients reach DA data through a UA facade.

Is OPC UA more secure than OPC DA?

Yes. OPC DA inherited DCOM's weak, hard-to-configure security. OPC UA has security built into the protocol: X.509 certificates, mutual authentication, message signing, and encryption, with selectable security policies per endpoint. A properly configured UA deployment is far more defensible than a classic DCOM-based one.

Related: Continuous Monitoring

Voltrus SCADA browses and subscribes to OPC UA (plus Modbus, S7, EtherNet/IP, DNP3) — dashboards, alarms, historian. From $249 lifetime.