> 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/wayfinding/ein-neues-wayfinding-gebaude-mit-stockwerken-erstellen.md).

# Create a new Wayfinding building with floors

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/c7QSzbRfcWp0X4bBjN4Z/Wayfinding%20Geb%C3%A4ude%20(4).png" alt=""><figcaption></figcaption></figure>

## Create a new building with floors

To create a new building with floors for the wayfinding system, follow these steps:

## Create a wayfinding building

1. Open the menu item **Engineering \[A]**

   ▷ The "Engineering" workspace opens.
2. Click on **Wayfinding \[B]**

   ▷ The "Wayfinding" workspace opens.
3. Click on **\[+ Building]** **\[C]**

   ▷ The window **"Create wayfinding for the building" \[D]** opens
4. Give your building a name **\[E]**
5. Select an asset on which the building is based **\[F]**

### Add a floor:

1. Click the tab **Floors \[G]**

   ▷ The window switches to the **floor view \[H]**.
2. Select an asset that represents the floor **\[I]**
3. Give the floor a name **\[J]**
4. Click on **"Add floor" \[K]**

   ▷ Another row appears **\[L]**
5. If necessary, remove the floor by clicking on **Remove** **\[M]**

   ▷ The corresponding row is removed.
6. Click on "**Save**" **\[N]**

   ▷ Congratulations! You have successfully created a wayfinding building


---

# 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/wayfinding/ein-neues-wayfinding-gebaude-mit-stockwerken-erstellen.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.