> 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/platform/map-and-floor/floor/placing-assets-on-a-floor.md). # Placing Assets on a Floor Follow these steps to place assets on a floor. ## Assign an Asset to a Floor Before assets can be placed on a floor, the assets must be subordinated to the floor. This is done in the settings of the asset that you want to assign to the floor. 1. Open the Assets menu item 2. Select the asset that you want to assign to a floor. 3. Click on Edit Information 4. In the Parent Location item – Select the floor that you want to assign the asset to. ## Place Assets on a Floor ### Place an Asset on a Floor

1. Make sure the asset has been added to the floor [-> Assign an Asset to a Floor](#place-an-asset-on-a-floor) 2. Open the **Map \[A]** 3. Click on the **symbol \[B]** of the floor where you want to place the asset. 4. Activate the **placement mode \[C]** 5. Click on the **icon \[D]** of the asset you want to place\ ▷ The "Place selection" opens.\ ▷ If you want to place a polygon: Continue with[ -> Place a Polygon](#place-a-polygon)\ ▷ If you want to place a point: Continue with [-> Place a Point](#place-a-point) #### Place a Point

1. Click on **Point \[F]** 2. Click on any location on the map to place a point there **\[M]** 3. Select the attribute **\[G]** 4. Select the color in which the point should be displayed **\[G]** 5. Click on **Save \[G]**\ ▷ The point is saved #### Place a Polygon

1. Click on **Polygon \[N]** 2. Click on any location on the map to place a polygon there **\[O]**\ ▷ At the corners of the polygon are white dots (nodes). Drag these dots to arrange the polygon.\ ▷ Click on the lines between the dots to create another node there.\ ▷ By adding multiple nodes, you can create round shapes **\[V]** 3. Select the attribute **\[P]** 4. Select the color **\[Q]** 5. Click on **Save \[G]**\ ▷ The polygon is saved #### Detailed Settings for Polygons

When displaying as a polygon, you can display additional values. The following options are available to you:

Element	Title	Details
[A]	"Alarms" switch	Activate this switch if an alarm should be displayed in the polygon.
[B]	"Set value-based color" switch	Activate this switch to change the color of the polygon depending on the value of the connected asset. -> Value Mapping
[B1]	Add new value	Click to add a new limit value
[B2]	Value	An entry for a limit value.
[B3]	Value specification	Here you can enter the desired limit value.
[B4]	Choose color	As long as the value is within the range defined in [B3], the polygon is displayed in the selected color.
[C]	"Show value" switch	Activate this switch so that the current value of the asset is displayed in the polygon.
[C1]	Selection	Choose whether the value is always displayed or only after a click.
[C2]	Font size	Set the font size of the value.
[D]	"Label" switch	Activate this switch so that the current value of the asset is displayed in the polygon.
[D1]	Label name	Enter the text to be displayed in the label here
[D2]	Font size	Set the font size of the label.
[E]	"Asset is a floor" switch	Asset is now seen as a floor
[E1]	Floor schema	Upload a floor plan here
[E2]	Floor number	Select the number of the floor here.
[F]	"Set polygon as room boundaries" switch	Here, the room boundaries for the trackers can be determined.
[G]	"Asset can be booked" switch	When the switch is activated, the asset can be booked in the Booking Widget. To enable this, the "Bookable" option must be activated in the asset template.

--- # 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/platform/map-and-floor/floor/placing-assets-on-a-floor.md?ask=&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.