...

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 workspaces data (usage and reservations) for the last 30 days in the Basic Analytics. If you have uploaded a fl, you can see it here and analyse the workspaces based on the floor plan.
If you would like to have another timeframe then the last 30 days, or you would like to compare floor by floor / building by building, have a look at our Advanced Analytics. If you are interested, please contact sales@roomz.io for a trial.

Handle of the data

Data is always computed during the night, so data from today is available tomorrow. The working days come from 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 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)

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

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

All data in the Analytics are anonymous and will be stored for max. 2 years. After 2 years, we delete the analytics data.

What can be seen in the basic analytics

You can have two views, the floor view and the Workspace view:

Floor View

Select the building and the floor you would like to see, to see the hole floor select all under space Shows how many spaces 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 days Average space utilisation over the last 30 days Shows how much time you saved with ROOMZ (Auto and manual Releases)	Image Added
You will only have this view if you have uploaded a floorpan under my Organisation Change the displayed data (Usage / Reservation). Usage is only visible if on the selected floor is at least one sensor bound. Move your mouse over a space and the % of usage or Reservation will be displayed as base for this, we use the building opening hours. The legend of the colour overlay is displayed here. Blue is a low occupancy and red is a very high occupancy	Image Added
This graph will only be there if you have at least one desk with a sensor on the floor. The graph show the peak (red) and the average (blue) usage per day in %. If you reach 100% peak, this means that on this day all the desks were used 100% of the available time (opening hours)	Image Added

Workspace view - Room

Select the building and the floor and the room you would like to see 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 (Sensor required) Average space utilisation over the last 30 days (Sensor required) Shows how much time you saved with ROOMZ (Auto and manual Releases)	Image Added
Shows how user interact with the ROOMZ Display installed outside the meeting room. Show 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 is selected right. In our example with the standard polling interval of 1h all the meetings were displayed correctly, if we have selected 2h, may 1 meeting out of 42 was not displayed on the screen.	Image Added
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 booked but used → Used without instant book or an appointment Not booked and not used → Free 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 in the heatmap, that means missing information from the sensor and / or the booking system.	Image Added

Workspace view - Desk / Huddle

Select the building and the floor and the desk / huddle you would like to see Average space utilisation over the last 30 days (Sensor required) Not needed for desk / huddle spaces	Image Added
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 booked but used Not booked and not used Booked and not used If you do not have a sensor Green → Booked Blue → not booked If you have a gray area in the heatmap, that means missing information from the sensor and / or the booking system	Image Added