Difficulty: novice
Content
Learning Objectives
After reading this article, you’ll be able to:
Interpret the Utilization Live View
What is “View by” on a live data floor plan?
Utilization view
To obtain utilization data, a sensor like VergeSense or Pointgrab needs to be configured, or push utilization data to Workplace using our Generic Endpoint, see External Data Sources.
Depending on the type of sensor installed and the mode it’s configured on, Utilization View will show a value or just give an indication of occupancy:
1. If no headcount or traffic sensor is configured:
Utilization view will show the same data as View By Space Occupancy and indicate if the location is occupied or not (legend “available” vs “occupied”)
2. When a headcount sensor is configured: Headcount number is visualized in the Utilization view, otherwise showing same data as View By Space Occupancy (legend “available” vs “occupied”)
3. When a traffic sensor is configured: the number visualized in the Utilization view is the calculated difference between the traffic IN and OUT values. This number indicates how many people are still inside the location.
Don’t see any value? Check out the FAQ below.
4. When Indirect Utilization with Motion sensors is configured*: the calculated utilization number is visualized in the Utilization view, otherwise showing same data as View By Space Occupancy (legend “available” vs “occupied”)
*See Use Browan motion sensors for indirect utilization for more information on how to set-up and how Utilization is calculated for this case.
See Utilization & Occupancy Matrix for a comparison of Direct and Indirect Utilization tracking methods
Utilization View, “Show Room Capacity Thresholds” is NOT enabled | Utilization translation |
---|---|
Green (Available) | no presence detected |
Red (Occupied) | presence detected |
Red (with icon) | presence detected by motion sensor |
Red (with utilization number) | presence detected by headcount sensor (Direct Utilization method) or a calculated utilization (Indirect Utilization method through traffic sensor or a combination of motion sensors) |
When “Show Room Capacity Thresholds” is enabled
Utilization View, “Show Room Capacity Thresholds” is enabled | Utilization translation |
---|---|
Green (Quiet) |
|
Yellow (Crowded) | # people detected is above "Quiet (max)" set in Studio, but below "Crowded (max)" set in Studio |
Red (Overcrowded) | # people detected is above "Crowded (max)" set in Studio |
Number, no color | Utilization is tracked for this location, but there are no capacity values configured |
Icon, no color |
|
The icons and colors mentioned are configurable in Live floorplan settings
FAQ
Although (footfall) data is available for a location, I’m not seeing any data in the Utilization view?
If footfall data does not come in regularly (for example only confirming “movement”, not the absence of movement) Workplace platform tackles this through a decay feature, which allows to visualize occupancy/headcount on the live floor plans for longer than what the data really tells us.
For an example on how Decay works, see https://spacewell.atlassian.net/wiki/spaces/KB/pages/491737/Motion+sensor#How-is-Motion-sensor-data-reflected-in-Workplace-Live-Views%3F
For a potential solution for data gaps in the dashboards (copy data in time slots), see https://spacewell.atlassian.net/wiki/spaces/KB/pages/5242896/External+Data+Sources#FAQ
Also, if there is a headcount device configured for the same location as the footfall device: A headcount device has higher priority than a footfall device, so utilization is not calculated based on footfall. Remove the headcount device to get the data from the footfall device.
Is it possible to track utilization based on footfall data on multiple entries to a location ?
When different footfall sensors are installed at different entrances for the same location (multiple data streams arriving at 1 location in the Workplace platform), then footfall data (and derived utilization data) will be based on the sum and/or subtraction of the data from all footfall sensors.
Although it’s technically possible to link multiple headcount sensors to 1 location in Workplace, the headcount data saved to the location from one sensor will overwrite the headcount data from the other sensor. If multiple headcount sensors are required to cover a location, it’s best to look into the Stitching mechanism of the specific sensor to obtain 1 “data point” from the sensor platform to then link to 1 location in Workplace.
Search