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

# Structuring Assets

Even in a relatively small tenant, an extremely large number of assets can accumulate very quickly.

To maintain an overview, it's therefore extremely important to structure assets in a logical and comprehensible way.

BuildingPro Suites offers two ways to structure and display assets:

* Functional sorting
* Geographical sorting

***

## Nesting Assets

Assets can be nested within each other. Nesting is a hierarchical organization of assets, where an asset is assigned a parent asset.

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

Within a "Country" asset, there is the "Building" asset.

Within the "Building" asset, there is a "Floor" asset.

Within the "Floor" asset, there is the "Room" asset.

Within the "Room" asset, there is the "Sensor" asset.

The nesting then looks like this: Country > Building > Floor > Room > Sensor
{% endhint %}

***

## Geographical Sorting

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

***

## Functional Sorting

Functional sorting sorts assets according to their affiliation with a parent system.

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

A building contains a ventilation system. This ventilation system is distributed throughout the entire building: the control system is in the basement, each room has several fans and temperature sensors, and there are more fans on the roof.

For BuildingPro Suites, each individual fan, temperature sensor, etc., is its own asset.

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

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

Functional sorting makes everything much simpler: 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/mandatory-base/assets/structuring-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.