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

# Structure assets

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

To keep an overview, it is therefore extremely important to structure assets in a sensible and traceable way. 

eliona offers 2 ways to structure and display assets:

* The Functional Sorting
* The 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 "building" is located within the asset "country". 

The asset "floor" is located within the asset "building". 

The asset "room" is located within the asset "floor". 

The asset "sensor" is located within the asset "room". 

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

## Geographical Sorting

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

## 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: in the basement there is the control unit, in all rooms there are several fans and temperature sensors each, and on the roof there are more fans. 

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 need 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 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/english-v14/documentation/assets/structure-assets.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.