> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/connectivity-as-a-service/connect-devices-via-opc-ua.md).

# Connect Devices via OPC UA

## About OPC UA

OPC UA (Unified Architecture) is a modern standard that describes data transfer in industrial networks. It offers secure and reliable communication between devices while being hardware- and platform-independent, which enables data exchange between devices with different operating systems.

## Special Features

A special feature of OPC UA is that no formats are required to convert incoming data. Instead, incoming data is mapped directly to the individual assets.

## Procedure

1. An [↗ endpoint is created](/collection/mandatory-base/platform-core/connect-hub/connectivity-as-a-service/connect-devices-via-opc-ua/create-and-configure-an-endpoint.md) and configured.
2. On this endpoint, a [↗ subscription](/collection/mandatory-base/platform-core/connect-hub/connectivity-as-a-service/connect-devices-via-opc-ua/create-and-configure-an-endpoint.md) is created.
3. In this subscription, one or more [↗ asset types](/collection/mandatory-base/assets/asset-modeling-create-templates/create-a-new-template.md) are selected.
4. One or more assets of this type are assigned to the selected asset type.
5. The incoming values via OPC-UA are directly assigned to the respective asset attributes.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/connect-hub/connectivity-as-a-service/connect-devices-via-opc-ua.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.