Difference between Occupancy and Utilization explained
occupancy (eg 50% occupied in 8h time) vs utilization (2 out of 4 chairs)
e.g. a room can be occupied 50% of a day (4 out of 8h) but when only 2 chairs are used out of 4,
it is utilized 50% against 50% occupation.
-> The real performance is then only 25% (half a day used for half the capacity).
Other example: An 8h meeting for 2 people in a meeting room with capacity=10
Occupancy = 100%
Utilisation = 20%
How to interpret room occupancy in Cobundu : Utilization & Occupancy Matrix
Check Room capacity page for more information on how to configure Room Capacity.
Direct Utilization & Occupancy
| Sensor method | Installation method | other hardware needed | max installation height | Functioning method | max Detection area | Icon decay | Config | info available | advised for utilization? |
|---|---|---|---|---|---|---|---|---|---|
| Pointgrab | wired | none | 2.15m (7ft) to 4.5m (14.8ft) | https://confluence.mcs.be/display/SUM/Headcount+%28Pointgrab%29+Sensor+way+of+measuring | 8m x 6m (26 x 20 ft) | 2min | CPMS + Studio | Live Floorplan+Dashboards | yes for utilization in meeting rooms or in open spaces |
| Vergesense wired | wired | device manager | 3,66m (12 ft) | Every 1min, a snapshot is taken + data is updated every 1 min; intervall is so low that person in the room will be captured | 1 per room or ~ 6 desks (smaller detection area than Pointgrab) | 2min | Vergesense + Studio | Live Floorplan+Dashboards | yes for utilization in meeting rooms or in open spaces |
| Vergesense wireless | wireless | gateway+wireless repeater | 3,66m (12 ft) | Every 15min, a snapshot is taken (no average of 15min!) and data is send to Cobundu Cloud every 15min. | 1 per room or ~ 6 desks (smaller detection area than Pointgrab) | 15min | Vergesense + Studio | Live Floorplan+Dashboards | yes for utilization in meeting rooms or in open spaces |
Indirect Utilization & Occupancy
| Sensor method | Installation method | other hardware needed | max installation height | Functioning method | max Detection area | Icon decay | Config | info available | advised for utilization? |
|---|---|---|---|---|---|---|---|---|---|
| PIR (Tabs)* | wireless (tape) | hub+sensors per seat/chair | 2.15m (7ft) to 4m (13.12ft) | https://confluence.mcs.be/display/SUM/Tabs+%28Tracknet%29+PIR+Sensor+way+of+measuring | 4m x 10m (13,12 x 32,81 ft) | 15min | Studio | Live Floorplan+Dashboards | - possible for utilization in open spaces - not advised for utilization in meeting rooms (difficult/technical set-up; not possible to detect over-utilisation + risk of false positive/negatives is bigger, eg people standing up in the room or people walking around the chairs while on the phone) |
| Footfall (Pointgrab) | wired | none | 2.15m (7ft) to 4.5m (14.8ft) | in/out-traffic | 8m x 1m (26 x 3 ft) | 2min | CPMS + Studio | Live Floorplan | other options are more reliable (footfall method very sensitive) |
| Actuator LOGIClink (LOGICdata) | wired | drive/motor | NA | https://confluence.mcs.be/display/SUM/LOGIClink+%28LOGICDATA%29+installation+guide | NA | 15min | config tool | Live Floorplan+Dashboards | - possible for utilization in open spaces - not advised for utilization in meeting rooms (difficult/technical set-up; not possible to detect over-utilisation + risk of false positive/negatives is bigger, eg people standing up in the room or people walking around the chairs while on the phone) |
| Airthings | wireless | hub | NA | estimate based on size of the room + CO2 => combination of parameters | 50m2 (538,2 sq ft) | 15min | Airthings + Studio | not yet integrated | other options are more reliable |
Setting up Indirect utilization (with PIR): Each SEAT needs to be a real WORKPLACE
- Make sure each meeting room seat corresponds to a workplace
- IWMS "Workplaces" objects to be created in/under the correct ROOM object, which in turn should be in the correct room category -> make sure room categories are correctly mapped in Studio
- Make sure the capacity for meeting rooms is set correctly in Studio (ref Room Capacity)
- Reminder: Workplace objects can only be linked to SVG floorplans in Studio
*How is utilization calculated in case both a room and workplaces are linked to a PIR sensor?
- Occupancy
- Presence on room level is true in case presence is true for 1 or more seats OR if presence is true for the sensor linked to the room itself
- So if someone walks around in the room, where seat PIRs are not triggered, but room PIR is triggered -> presence = true
- Utilization
- If presence detected on seat level AND room level, headcount will only be calculated based upon sum of triggered seats. It ignores the room PIR.
- So if 2 people sit on a chair/seat triggered by workplace PIR, headcount will be 2
- If presence detected ONLY on room level and not on seats, headcount is set to minimum 1
- So if someone walks around in the room, but seats PIRs not triggered, headcount is 1
Example
Quarter 1 | Quarter 2 | Quarter 3 | ||
Occupancy | Room PIR | 0 | 1 | 1 |
Seat 1 PIR | 1 | 1 | 0 | |
Seat 2 PIR | 1 | 1 | 0 | |
Seat 3 PIR | 0 | 0 | 0 | |
Room occupancy live floorplan | TRUE | TRUE | TRUE | |
Room utilization live floorplan | 2 | 2 | 1 | |
Room utilization count timeslots | 2 | 2 | 1 |
Utilization & Occupancy on Live Floorplan
Occupancy on live floorplan shows: location occupied or not (independent of how many people are in that location)
Utilization on live floorplan shows: how many people are detected in that location