Content

Overview

You can view your workspaces workspace data (usage and reservations) for the last 30 days in the Basic Analytics. If you have uploaded a flfloor plan to the plan editor, you can see are able to view it here and analyse the workspaces based on the floor plan.
If you would like to have another timeframe then the last 30 dayswant to be able to analyse a longer timeframe, or you would like to compare floor by floor / building by building, please have a look at our Advanced Analytics. If you are interested, please contact sales@roomz.io for a trial.demonstration

Handle of the workspaces data

Data The data is always computed processed during the night, so data information from today is will be available tomorrow. The working days come from and opening hours, defined in the building settings, if you change the opening day’s for a building the future (from today on) will include these days. (If you would like are the time frame in which the data is taken into account. As an example, if you want to include the weekend in the report, you have to change it in the building settings. From the date of change on the Analytics will calculate also the new days on, data in the past will be not calculated)must include “Saturday + Sunday” inside the settings. If you change these settings, the changes are taken into account in the future (from the day of the change). The data from the past will not be changed and stay with the previous opening hours, days.

For sensor data we only take process valid sensor data, if a workspace have has no valid data for one day or more we , we’ll handle this workspace like he would not wouldn’t exist (all calculations are done without this workspace). A sensor could have invalid date data if something some of the following issues were detectedoccurred:

• There is a physical shock on the device (for instance a knee bumping on the desk sensor)

• There is an electrical static discharge

• The USB is plugged/unplugged

If a sensor is not isn’t able to communicate with the server, he it will buffer the usage data up to 10 days or more (depends on the usage). As soon as the sensor it is able to communicate again, he it will send the data to the server and these the data are will be visible in the following day.

All analytics data in the Analytics are is anonymous and will be is stored for max. 2 years. After a maximum of 2 years, we delete the analytics dataafter which all data will be erased.

What can be seen in the basic analytics

You can have two views, the floor view and the Workspace view:different overviews over the last 30 days :

• Floor view

• Workspace view

Floor View

Select the building and the floor you would like to see, to see the hole floor select all under spaceanalyse, if you want the whole floor select “All” Shows how many spaces workspaces there are on this floor Shows how many meetings have taken place over the last 30 days Shows how many “Ghost-Meetings” happens over the last 30 daysAverage space utilisation over the last 30 dayshappened (Sensor required) Average workspace utilization (Sensor required) Shows how much time you have saved with ROOMZ (Auto with auto and manual Releasesreleases)
You will only have be able to see this view, if you have uploaded a floorpan Floorplan to the plan editor (under my OrganisationOrganization) Change the displayed data to display (Usage / Reservation). Usage The option “Usage” is only visible, if on the selected floor is at least one sensor bound . to a workspace Move your mouse cursor over a space and to display the % percentage of usage or Reservation will be displayed as base for this, we use the building opening hours. (%) or reservations of the space The basis are the opening hours of the building and the days The legend of the colour color overlay is displayed here. Blue is a means low occupancy and red is a very high occupancy
This graph will only be there shown, if you have at least one desk setup with a sensor on the floor.The graph show It shows the peak value (red) and the average (blue) usage per day in percent (%). If you reach 100% peak, this it means that on this that particular day all the desks desk were used 100% of the available time (opening hours)

Workspace view - Room

Select the building and the , floor and the room you would like want to seeshow Shows how many meetings have taken place over the last 30 days (Sensor required) Shows how many “Ghost-Meetings” happens over the last 30 days happened (Sensor required) Average space utilisation over the last 30 days utilization (Sensor required) Shows how much time you have saved with ROOMZ (Auto with auto and manual Releasesreleases)
Shows how the user interact interactions with the ROOMZ Display installed outside the meeting room. Show Shows the duration of the meetings over the past 30 days Shows the time between room booking and meeting start. Check here to see if the polling interval With this information, you are able to check if your Polling Interval is selected right . In our example with the standard polling interval of 1h all the meetings were displayed correctly, if . If we would have selected chosen 2h, may 1 meeting out of 42 was not meetings wouldn’t have been displayed on the screendisplay.
The heatmap shows you the status of the space over the past 30 days, you can have the following states: If you have a sensor Green , - booked and used → Normally used Not Yellow - not booked but used → Used without instant book or an appointment Not Blue - not booked and not used → Free Booked Red - booked and not used → Could be a ghost meeting, an early left or a break in the meeting If you do not have a sensor Green → Booked Blue → not booked If you have a gray area state in the heatmap, that it means missing information from the sensor and / or the booking system.

Workspace view - Desk / Huddle

Select the building and the , floor and the desk / or huddle you would like want to seeshow Average space utilisation over the last 30 days utilization (Sensor required) Not needed for desk / or huddle spaces

The heatmap shows you the status of the space over the past 30 days, you can have the following states: If you have a sensor Green , → booked and used Not Yellow → not booked but used Not Blue → not booked and not used Booked Red → booked and not used If you do not have a sensor Green → Bookedbooked Blue → not booked If you have a gray area state in the heatmap, that it means missing information from the sensor and / or the booking system.