> For the complete documentation index, see [llms.txt](https://docs.akenza.io/akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/akenza.io/dashboard-builder/components/floorplan.md). # Floorplan ### Creating a Space Akenza uses building models from smplrspace.com to display sensor values in 2D and 3D building models. Therefore, create an organization with smplrspace.com and create your space there. You'll later import this space into the akenza floorplan dashboard component. ### Mapping assets Once your space has been created and furnished you'll map assets to the model. This is a prerequisite for displaying sensor data in the model.

Click **map assets** in the menu list of your space (smplrspace)

In the **"map assets"** view. Create the following groups as needed: * Desk -> Furniture * Room -> Polygon * Sensor -> Point **Desk**, **Room** and **Sensor** are keywords for the later mapping, so do not change the spelling. #### Adding assets Assets in the **Desk** group will be mapped to objects of type **Furniture.** Click **"Add asset"** to create a new mapping. Then name it (e.g. "A101") and select a furniture object to complete the mapping. **Room** and **Sensor** assets can be added in the same way.

#### Export mapping to .csv Once you are done mapping your assets click **"Export to CSV"**. We're working on a feature to automate the upload process of this .csv file to akenza. In the mean time please get in touch with the akenza team and share this .csv file. We'll gladly store it in the right place on akenza for you. ### Floorplan and asset mapping services If your floorplan digitization is complex or you'd like to map a large number of devices, smplrspace offers services to complete these task for you for a fee. ### Prepare akenza assets for mapping Akenza assets will need a **"Custom Field"** matching the naming of assets mapped to the smplrspace model. Custom field: * **SpaceId** -> mapped to **Room** * **EquipmentId** -> mapped to **Desk** * **SensorDesignId** -> mapped to **Sensor** **SpaceId**, **EquipmentId** and **SensorDesignId** are keywords. For a successful mapping do not change the spelling.

Custom fields example (use one per asset)

### Add floorplan component #### Settings Once you created your building model over at smplrspace.com you will need to enter your **Smplrspace** **Organization ID**, **Space ID** and **Token** to load your model into the floorplan component on akenza.

#### Getting the Organization ID and Token The Organization ID can be found in the **"Developers"** tab. At the same location you'll be able to create a **Token** to copy into the floorplan component settings.

Developers tab with organization ID and token (smplrspace)

#### Getting the Space ID The **Space ID** can be copied from the Space card inside the smplrspace application.

Space card with Copy space ID button (smplrspace)

Once the model is loaded click **"Sync metadata"** to sync devices. A prerequisite for this is the previous .csv mapping file upload to akenza as described above. On successful sync the number of mapped devices will be displayed. #### **Source** In the source tab select the layer and datapoint you'd like to plot. Here you can also further refine how the sensor data is displayed in the model. * Define layer name: Begin by assigning a name to the layer you wish to display. * Select a layer type to display: Choose the specific layer you want to view from the available list of layers. * Filter Devices by Tag (Optional): To narrow down the devices displayed, apply filters based on device tags, if necessary. * Select Data Point to Display: Choose which data point you want to display on the selected layer. * Set Aggregation Type: Finally, configure the aggregation type (e.g., average, sum, etc.) for the selected data point to refine how the information is presented.

--- # 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.akenza.io/akenza.io/dashboard-builder/components/floorplan.md?ask=&goal= ``` `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.