> 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/documentation/assets/assets-strukturieren.md).

# Structure assets

Even in a rather small project, an extremely large number of assets accumulate very quickly.

To keep track, it is therefore extremely important to structure assets in a meaningful and traceable way.

eliona offers 2 ways to structure and display assets:

* Functional sorting
* Geographical sorting

## Nesting of assets

Assets can be nested within one another. Nesting is a hierarchical organization of assets. An asset is assigned a parent asset.

{% hint style="info" %}
**Example**

The asset "Land" contains the asset "Building".

The asset "Building" contains an asset "Floor".

The asset "Floor" contains the asset "Room".

The asset "Room" contains the asset "Sensor".

The nesting then looks as follows:\
Land > Building > Floor > Room > Sensor
{% endhint %}

## Geographical sorting

Geographical sorting displays assets sorted by location. This allows you, for example, to see all sensors located on a floor at a glance.

## Functional sorting

Functional sorting sorts assets according to their affiliation with a higher-level system.

{% hint style="info" %}
Example:

In a building there is a ventilation system. This ventilation system is distributed throughout the entire building: the control system is in the basement, in all rooms there are several fans and temperature sensors each, and there are more fans on the roof.

For eliona, each individual fan, temperature sensor, etc. is a separate asset.

With geographical sorting, it would be extremely difficult to keep track of each individual asset. The user would have to navigate to each individual floor and each individual room just to see a few assets.

In addition, the user would have to know exactly how many assets there are in total.

Functional sorting makes everything much easier: there is one asset for the entire ventilation system. All assets that functionally belong to the ventilation system are subordinate to this asset.
{% endhint %}


---

# 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/documentation/assets/assets-strukturieren.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.