...

...

...

...

Data of one floor of the Roomz solution

Example:

Building → ex.: Prime Tower

Floor → ex.: 42

Workspace → ex.: All (All desks and rooms)

What data is shown here?

We have 15 Workspaces like meeting rooms, desks or huddles, furthermore we see the count of meetings of the last 30 days (124 Meetings).

Then we can see the number of Ghost meetings, which are meetings where the room was booked but no one entered the room and the meeting didn't happen (at least in this room).

The 22% of Workspace usage shows us the medium percentage of all workspaces, in this case we can say there are probably enough rooms and desks for all employees to work.

4201 m is the enormous time in minutes, the room solution was able to safe, so the sensor auto released so many meetings which would block at meeting room much longer as needed.

Image RemovedImage RemovedImage Removed

Daily desk's usage (number of desks of this floor)

hint: Use the cursor to see dates and numbers of the graph

Peak

This shows us the highest amount of used desk on that specific day.

Average

Here you can see the average desk usage of the day, mostly the better number to take into calculation if you should take action.

Data

The sensors and the booking system are the main data source.

The data shown is always about the last 30 days.

Furthermore, the smart analytics software is reading the opening hours of the chosen building.

For example:

Prime Tower is open between 08.00 - 18.00 o`clock, Mo. - Fr.

The Graph and chart now shows every important data of the last days (max. 30 days) between the opening hours of to choose building room/desk.

Analyzing the booking system and sensors data is very important to improve your office solution and efficiency, it can help you find weak spots/strong spots, it is necessary in a modern office environment to see how employees use the office. With this it's possible to improve, having a clean, easy and an awesome office experience.

Image Removed

How to read data of the rooms

How to check the last 30 days of a room in the Roomz-portal:

Building → ex.: Prime Tower

Floor → ex.: 42

Workspace → ex.: Analytics-Room

User actions

This chart shows you what kind of actions the users are using while interacting with the buttons of the display.

In our example picture, the most used function is to book a 15-minute slot at a meeting room.

Meeting duration

here you can have a look how long meetings are in this specific room.

In our example, we see that the most meetings are finished within 00.16 - 00.30 minutes.

Time between room booking and meeting start

this chart shows you how to put your polling interval to safe battery life of your displays because as often as the display is asking their server for an agenda as more battery is used.

In our example, we can clearly see that nearly all meetings are booked two days before. So polling interval > 1h is completely fine.

Hint: if instant bookings are made, you don't need a low polling interval, because in this case the display will always communicate with the server to get the newest agenda (set-up polling interval).

...

...

Content

Overview

You can view your workspace data (usage and reservations) for the last 30 days in the Basic Analytics. If you have uploaded a floor plan to the plan editor, you are able to view it here and analyse the workspaces based on the floor plan.
If you want 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 demonstration

Handle of the workspaces data

The data is always processed during the night, so information from today will be available tomorrow. The working days and opening hours, defined in the building settings, 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 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 process valid data, if a workspace has no valid data for one day or more, we’ll handle this workspace like he wouldn’t exist (all calculations are done without this workspace). A sensor could have invalid data if some of the following issues occurred:

• 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 isn’t able to communicate with the server, it will buffer the usage data up to 10 days or more (depends on the usage). As soon as it is able to communicate again, it will send the data to the server and the data will be visible the following day.

All analytics data is anonymous and is stored for a maximum of 2 years, after which all data will be erased.

What can be seen in the basic analytics

You can have two different overviews over the last 30 days :

• Floor view

• Workspace view

Floor View

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

Workspace view - Room

Select the building, floor and room you want to show Shows how many meetings have taken place Shows how many “Ghost-Meetings” happened (Sensor required) Average space utilization (Sensor required) Shows how much time you have saved with ROOMZ (with auto and manual releases)	Image Added
Shows the user interactions with the ROOMZ Display installed outside the meeting room Shows the duration of the meetings Shows the time between room booking and meeting start. 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 we would have chosen 2h, 1 out of 42 meetings wouldn’t have been displayed on the display.	Image Added
The heatmap shows you the status of the space, you can have the following states: If you have a sensor Green - booked and used → Normally used Yellow - not booked but used → Used without instant book or an appointment Blue - not booked and not used → Free 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 state in the heatmap, it means missing information from the sensor and / or the booking system.	Image Added

Workspace view - Desk / Huddle / Parking

Select the building, floor and the desk or huddle you want to show Average space utilization (Sensor required) Not needed for desk or huddle spaces	Image Added
The heatmap shows the status of the space, you can have the following states: If you have a sensor Green → booked and used Yellow → not booked but used Blue → not booked and not used Red → booked and not used If you do not have a sensor Green → booked Blue → not booked If you have a gray state in the heatmap, it means missing information from the sensor and / or the booking system.	Image Added