> 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/preface/glossar.md).

# Glossary

## GAI

Abbreviation for **G**lobal **A**sset **I**dentifier.

The GAI is a unique identifier that must be assigned to every asset. The GAI can be used to uniquely identify each individual asset.

## Assets

Assets are a special type of entity in ABB BuildingPro.

Most of the assets you will encounter will probably be sensors. But rooms, floors, buildings, and even entire countries and continents can also be assets.

## Entities

Everything you can interact with in ABB BuildingPro is an entity: assets, users, projects, tags, etc.

Entities are an abstract representation of a real or conceptual object that stores information or data and is used in the context of the application. Entities can have various attributes and properties. Entities are used to organize and process information.

## Building users

Building users are people who do not work directly with ABB BuildingPro, but use the building passively - e.g. employees in an office building.


---

# 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/preface/glossar.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.
