> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/configure-ios/communication-protocol-ios/opc-ua-da.md).

# OPC UA/DA

## Introduction to OPC UA / OPC DA

OPC UA (Open Platform Communications Unified Architecture) and OPC DA (Data Access) are standardized industrial communication technologies used for interoperability between automation devices, control systems, and enterprise applications. They enable secure, reliable, and vendor‑neutral data exchange across industrial and manufacturing environments.

OPC DA is the classic, Windows‑based OPC specification, while OPC UA is its modern, platform‑independent successor designed for scalable, secure, and service‑oriented architectures.

## Protocol characteristics

* **Client/Server Architecture**\
  OPC clients (SCADA, HMIs, analytics platforms) request data from OPC servers that interface with PLCs, sensors, and other industrial devices.
* **Platform Independence (OPC UA)**\
  OPC UA supports Windows, Linux, embedded systems, and cloud environments, unlike OPC DA which relies on Windows COM/DCOM.
* **Rich Data Modeling**\
  Supports structured data, metadata, alarms, events, historical data, and complex object models—not just raw values.
* **Secure Communication**\
  Built‑in security features in OPC UA, including encryption, authentication, authorization, and certificate management.
* **Real-Time and Historical Acces**s\
  Provides both real‑time data access and historical data retrieval for analysis and reporting.

## How the protocol works

The OPC server exposes data points and information models representing devices and processes.\
OPC clients browse available data, subscribe to changes, or read/write values as needed. OPC UA communication can occur over TCP/IP, HTTPS, or WebSockets, while OPC DA typically uses DCOM on local or trusted networks.

## Example applications

* **Manufacturing and factory automation**\
  OPC UA enables communication between PLCs, robots, HMIs, and MES systems in smart factories.
* **SCADA and process control**\
  SCADA systems use OPC UA/DA to collect real‑time process data from distributed control systems.
* **Industrial IoT (IIoT)**\
  OPC UA serves as a bridge between shop‑floor equipment and cloud or edge analytics platforms.
* **Energy and utilities**\
  Power plants and substations use OPC UA to integrate control systems, monitoring tools, and asset management software.
* **Enterprise integration**\
  Business systems such as ERP and quality management platforms consume OPC data for production reporting and optimization.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/configure-ios/communication-protocol-ios/opc-ua-da.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
