> For the complete documentation index, see [llms.txt](https://docs.mclimate.eu/mclimate-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mclimate.eu/mclimate-enterprise/configuration-and-management/building-management.md).

# Building Management

In order to efficiently manage a building it is considered a good practice to have a structure that is corresponding as close as possible to the actual physical entity. Floors, Spaces, etc. are a good tool to separate devices into zones, assign control levels to users, manage heating profiles, etc.

Additionally you can utilize floor plans where you can allocate devices, which improves trackability and is useful for maintenance technicians (for example in commercial buildings).

Let us take a deeper look at the Building structure in this chapter and discuss some examples to better understand how one could utilize it.

If you scroll down to the Devices section in the main screen you will find that the table has separate tabs for Floors, Spaces, etc. You can also navigate to any level of the structure via the sidebar on the left.

<figure><img src="/files/rygc1DPQYd82cF0lbmHS" alt=""><figcaption><p>Building layers</p></figcaption></figure>

{% hint style="info" %}
As mentioned before in order to have a structure level and to be able to add or remove components to it, you need to have it created when the Building itself is created. For example a Building that has no Spaces on Floors, will remain so, you will be able to only add/remove Floors and not spaces. Thus, we recommend you create an Entity on each level whether you intend to use it or not at the time.
{% endhint %}

We are going to look at two examples in more details in the following subsections:

* Floors - top level structure that contains every other level. This is where a Floor plan is added in order to have better device trackability
* Spaces and Rooms - lowest level entities, useful for separation of assets (especially for management or larger commercial buildings)


---

# 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.mclimate.eu/mclimate-enterprise/configuration-and-management/building-management.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.