OPC DA vs OPC UA: Key Differences and When to Use Each

The OPC DA (Data Access) is an older Windows-only protocol for real-time data exchange in SCADA systems, while OPC UA (Unified Architecture) is a modern, platform-independent standard with enhanced security and flexibility. OPC UA supports complex data types and secure communication, making it the preferred choice for new industrial automation projects.

Quick Comparison

Here is a quick side-by-side comparison of OPC DA and OPC UA based on key factors.

Factor	OPC DA	OPC UA
Protocol Type	COM/DCOM based	Service-oriented architecture (SOA) over TCP/IP
Platform Support	Windows only	Cross-platform (Windows, Linux, macOS)
Security	Limited (relies on DCOM security)	Built-in encryption, authentication, and authorization
Data Types	Simple data types only	Supports complex and custom data types
Communication	Real-time data access only	Real-time, historical, alarms, and events
Scalability	Limited	Highly scalable and extensible

Key Differences

OPC DA is based on Microsoft's COM/DCOM technology, which restricts it to Windows environments and makes network configuration complex due to DCOM settings. It mainly supports simple real-time data access and lacks modern security features, making it less suitable for today's industrial networks.

In contrast, OPC UA is designed as a platform-independent standard using a service-oriented architecture over TCP/IP. It supports secure communication with built-in encryption and user authentication, which is essential for protecting industrial data. OPC UA also handles complex data types, historical data, alarms, and events, providing a richer and more flexible data model.

Because of these differences, OPC UA is more scalable and future-proof, supporting cross-platform deployments and easier integration with modern IT systems, while OPC DA remains limited to legacy Windows-based SCADA systems.

Code Comparison

Example: Reading a tag value using OPC DA in C#.

csharp

using Opc.Da;

// Connect to OPC DA server
Server server = new Server(new OpcCom.Factory(), null);
server.Connect("opcda://localhost/YourOpcServer");

// Define item to read
Item item = new Item { ItemName = "Tag1" };

// Read item value
ItemValueResult result = server.Read(new Item[] { item })[0];

Console.WriteLine($"Value: {result.Value}");

server.Disconnect();

Output

Value: 123.45

OPC UA Equivalent

Example: Reading a node value using OPC UA in C# with the OPC Foundation SDK.

csharp

using Opc.Ua;
using Opc.Ua.Client;
using Opc.Ua.Configuration;

// Create application configuration
var config = new ApplicationConfiguration()
{
    ApplicationName = "OpcUaClient",
    ApplicationType = ApplicationType.Client,
    SecurityConfiguration = new SecurityConfiguration { ApplicationCertificate = new CertificateIdentifier() },
    TransportConfigurations = new TransportConfigurationCollection(),
    TransportQuotas = new TransportQuotas { OperationTimeout = 15000 },
    ClientConfiguration = new ClientConfiguration { DefaultSessionTimeout = 60000 }
};

await config.Validate(ApplicationType.Client);

// Create session
var endpointURL = "opc.tcp://localhost:4840";
var selectedEndpoint = CoreClientUtils.SelectEndpoint(endpointURL, false);
var endpointConfiguration = EndpointConfiguration.Create(config);
var endpoint = new ConfiguredEndpoint(null, selectedEndpoint, endpointConfiguration);

using var session = await Session.Create(config, endpoint, false, "OpcUaClient", 60000, null, null);

// Read node value
var nodeId = new NodeId("ns=2;s=Tag1");
var value = session.ReadValue(nodeId);

Console.WriteLine($"Value: {value.Value}");

Output

Value: 123.45

When to Use Which

Choose OPC DA if you are working with legacy Windows-only SCADA systems that require simple real-time data access and cannot upgrade infrastructure. It fits well in environments where DCOM is already configured and security needs are minimal.

Choose OPC UA for new projects or upgrades needing cross-platform support, strong security, and flexible data handling including historical data and events. OPC UA is ideal for modern industrial IoT, cloud integration, and scalable automation systems.

Key Takeaways

OPC DA is Windows-only and uses COM/DCOM with limited security and simple data types.

OPC UA is cross-platform, secure, and supports complex data and multiple communication types.

Use OPC DA for legacy systems; use OPC UA for modern, scalable, and secure industrial applications.

OPC UA’s service-oriented architecture makes it future-proof and easier to integrate.

Code examples show OPC DA uses COM calls, while OPC UA uses a client-server model over TCP/IP.