> 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/map-and-floor/floor/create-a-floor.md).

# Create a floor

## Create a floor

A floor is created like a regular asset via the "Create asset" menu.

However, several special features must be taken into account:

1. As the asset type, "Floor" must be selected
2. A floor plan must be assigned
3. The floor must be subordinated to a building

Both special features are explained in the following documentation.

{% hint style="info" %}
Correctly configured floors are always marked with the **Symbol \[U]** .
{% endhint %}

### Create a "floor" asset

<div data-full-width="true"><figure><img src="/files/9e9248a43d731438c7ee422d263d97208823bb63" alt=""><figcaption></figcaption></figure></div>

1. Open the menu item **Assets \[A]** on
2. Click on **\[B]**\
   ▷ The window **Add asset \[C]** opens
3. Under **Asset type** **\[C]:** Select the type "Floor"
4. Assign a GAI **\[D]**
5. Give the asset a name **\[E]**
6. (Optional): Add a description to the asset **\[F]**
7. (Optional): Enter one or more IDs for the asset **\[G]**&#x20;
8. (Optional): Assign one or more tags to the asset
9. Click on **Save \[I]**\
   ▷ The asset is created

### Assign a floor to a building

<div data-full-width="true"><figure><img src="/files/d2c771bc83ee938adee9d65f68812411899ca8f9" alt=""><figcaption></figcaption></figure></div>

1. Open the menu item **Assets \[A]** on
2. Navigate to an asset with the type "Floor"
3. In the item **Parent location \[J]** – Select an asset to which you want to assign the floor. \
   ◈ Most of the time, the parent asset is a building.
4. Click on **Save \[K]**

### Add floor plan

<div data-full-width="true"><figure><img src="/files/6c2e6da25e2d79e90dc8484371cc7af5cfe19539" alt=""><figcaption></figcaption></figure></div>

* Open the menu **Map \[L]**
* In the **Sidebar \[M]:** Expand the asset to which the floor is assigned, to which you want to add the floor plan. \
  ▷ You will see all assets assigned to this asset. These can include one or more floors.
* For the asset to which you want to add a floor plan: Click on the icon **\[N]**. \
  \&#xNAN;**⚠** Do NOT click on the name of the asset!\
  ▷ The details open
* Activate the **Placement mode \[P]**
* Activate the switch **Asset is a floor \[Q]**
* Upload under **Floor schema \[R]** upload a floor plan
* Select under **Floor description \[S]** the number of the floor.
* Click on **Save \[T]**\
  ▷ The floor has been created.\
  ▷ The floor is marked with a **Icon \[U]** marked.\
  ▷ In the menu **Assets \[A]** the floor now appears under the parent asset

{% hint style="success" %}
After you have carried out the steps in this chapter, the asset will be marked with the **Symbol \[U]** marked.

Only assets that are marked with the **Symbol \[U]** are correctly configured floors.
{% endhint %}

{% hint style="warning" %}
If the asset is not marked with the **Symbol \[U]** you cannot carry out the steps in the next chapter.
{% 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/map-and-floor/floor/create-a-floor.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.