> 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/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-opc-ua-verbinden.md).

# Connect devices via OPC UA

## About OPC UA

OPC UA (Unified Architecture) is a modern standard that describes data transmission in industrial networks. It provides secure and reliable communication between devices and is also hardware- and platform-independent, enabling data exchange between devices with different operating systems.

## Special features

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

## Procedure

1. A[ ↗ endpoint is created](/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-opc-ua-verbinden/einen-endpunkt-erstellen-und-konfigurieren.md) and configured
2. On this endpoint, a [↗ subscription](/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-opc-ua-verbinden/einen-endpunkt-erstellen-und-konfigurieren.md#uebersicht) created.
3. In this subscription, one or more [↗ asset types](broken://pages/9a6e99aacbd1c7c71f737ac1647fc5a0c9991dfc) selected
4. One or more assets of this type are assigned to the selected asset type
5. The values received via OPC UA are mapped directly 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 by asking a question.

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

```
GET https://docs.buildings.ability.abb/collection/english-v14/connectivity-as-a-service/gerate-mit-abb-buildingpro-verbinden/gerate-per-opc-ua-verbinden.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.