akenza.io
WebsiteAPI DocumentationWhat's newLogin
  • Overview
  • Getting Started
    • Connect a Device
  • Changelog
  • General
    • Applications
    • Organization context
    • Workspace Context
    • Users
      • User Roles
  • Device Management
    • Managing an organization
      • API keys
      • Users (Organization)
        • Add & removing users from your organization
    • Managing a workspace
      • General Settings
        • Device Lifecycle Reports
        • Workspace properties
        • Occupancy settings
        • Device Setup Assistant
      • Custom fields
      • Tags
      • Users (Workspace)
    • Devices
      • Device
      • Device Simulator
      • Bulk actions
      • Bulk import CSV templates
    • Rules
      • Input
      • Logic blocks
        • Comparison
        • Custom Logic
          • Logic Block Scripting
      • Timed Rules
      • Rule Actions
        • Downlink
    • Data Flows
      • Device Connectors
        • Device Security
          • Using Device Credentials
            • Creating Public/Private Key Pairs
            • Using JSON Web Tokens (JWTs)
              • Python
              • Java
        • HTTP
        • MQTT
        • CoAP
        • LoRaWAN
          • Connectivity Management
          • Swisscom LoRaWAN
          • The Things Network
          • Loriot
          • Actility’s ThingPark Wireless
          • EWZ
          • Cibicom
          • Helium
          • ChirpStack
        • NB-IoT
        • mioty
        • Disruptive Technologies
        • VergeSense
        • Spaceti
        • Haltian
      • Device Types
        • Custom Device Types
          • Uplink
          • Downlink
          • Scripting
        • Library
      • Output Connectors
        • Databases
          • akenza DB
          • InfluxDB
          • SQL Databases
        • Streaming
          • Webhook
          • Azure IoT Hub
          • AWS Kinesis
          • Google Cloud Pub/Sub
          • Apache Kafka
        • Notifications
          • E-Mail
          • SMS
          • Microsoft Teams
          • Slack
    • Custom Components
    • Integrations
    • Reference
      • REST API
        • Filtering
        • Querying Device Data
      • WebSocket API
      • Scripting
        • Stateful Operations
        • Utility Functions
      • Payload Templating
  • Reference
  • Dashboard Builder
    • Managing Dashboards
      • Embedding dashboards
    • Components
      • Map
      • Floorplan
  • Device Setup Assistant
    • Device Setup Assistant - Overview
  • Tutorials
    • BI Tools
      • Grafana Data Source Plugin
      • How to build a dashboard with Retool
      • How to analyze data with AWS QuickSight
    • Devices
      • How to integrate the XDK device from Legic via MQTT on akenza
      • How to connect the Disruptive Technologies-cloud on akenza
      • How to send Downlinks to the Kuando Busylight device
      • How to integrate an Arduino device via MQTT on akenza
      • Integrate a MClimate Vicki LoRaWAN Radiator Thermostat on akenza
      • How to integrate an ERS Elsys device with Loriot on akenza
      • How to integrate the IAM Decentlab device with TTN on akenza
      • How to integrate the Seeed SenseCAP T1000 tracker on akenza
      • How to integrate a Swisscom Multisense device on akenza
    • Notifications
      • How to send SMS notifications
      • How to send notifications to Slack
      • How to send notifications to Microsoft Teams
    • Enterprise solutions
      • How to send data to Azure IoT Hub
      • How to send data to the Google Cloud Pub/Sub
      • How to send data to InfluxDB
      • How to send data to AWS Kinesis
      • How to send data to Azure Event Hubs with Apache Kafka
    • IoT Starter Kits
      • How to integrate the IAQ Kit with Actility on akenza
      • How to integrate the CoWork Kit with Actility on akenza
      • How to integrate the Smart Building Kit with Actility on akenza
      • How to integrate the Pepperl+Fuchs Kit with Actility on akenza
  • Support Center
    • FAQ
    • Status Page
    • Service Desk
    • Request a feature
  • Deprecated
    • SIM-Cards
    • Everynet
    • Sigfox
    • How to connect the Yanzi Lifecycle cloud on akenza
Powered by GitBook
On this page
  • Creating a Space
  • Mapping assets
  • Floorplan and asset mapping services
  • Prepare akenza assets for mapping
  • Add floorplan component

Was this helpful?

  1. Dashboard Builder
  2. Components

Floorplan

PreviousMapNextDevice Setup Assistant - Overview

Last updated 7 months ago

Was this helpful?

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.

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.

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.

Getting the Space ID

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

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.

Click map assets in the menu list of your space (smplrspace)
A successfully mapped desk (smplrspace)
Custom fields example (use one per asset)
Settings tab
Developers tab with organization ID and token (smplrspace)
Space card with Copy space ID button (smplrspace)
Source tab