A fixed-schedule BMS conditions the entire office floor from 8am to 7pm every weekday, on the assumption that the floor will be fully occupied throughout those hours. In the post-pandemic hybrid-work era, that assumption is simply false — Indian corporate offices average 40-60% occupancy on any given day, with substantial day-to-day and zone-to-zone variability. The BMS is conditioning empty desks, empty meeting rooms, and empty zones at full capacity, burning energy for occupants who are working from home that day.
Occupancy-based automation replaces the fixed-schedule assumption with real observation. Computer vision occupancy detection counts actual people present in each zone in real time — not motion, not a schedule, but genuine occupancy density — and the BMS conditions accordingly. Combined with predictive pre-conditioning informed by meeting room bookings and historical attendance patterns, the building delivers precision comfort exactly where and when it's needed, while eliminating the energy waste of conditioning empty space that fixed schedules cannot avoid.
Occupancy Detection Method Comparison
| Detection Method | Accuracy | Zone Granularity | Response Time | Privacy Considerations | Energy Savings Potential |
|---|---|---|---|---|---|
| Fixed schedule (baseline) | N/A — no detection | None (assumed full) | N/A | None | 0% (reference) |
| PIR motion sensors | Binary (occ/unocc) | Zone-level | Instant (motion only) | Low risk | 10–15% |
| Computer vision counting | High — actual count | Sub-zone/desk-level | Real-time | Anonymised architecture required | 18–25% |
| Wi-Fi/BLE device detection | Medium — device proxy | Zone-level | Real-time | Device ID anonymisation needed | 12–18% |
| Desk sensor + badge correlation | High — direct + validated | Desk-level | Real-time | Badge data is personal data | 15–22% |
Technical Design: Occupancy-Based Automation Architecture
- Computer vision occupancy counting: Anonymised person-detection models (not face recognition) provide real-time zone occupancy count without identity capture — processed at the edge, only aggregate count data transmitted to BMS
- Zone-based HVAC modulation: VAV damper and AHU response to occupancy-derived cooling load, avoiding conditioning of unoccupied floors/zones while maintaining comfort in actively used areas
- Lighting integration: DALI/KNX lighting control responding to the same occupancy data feed as HVAC, delivering coordinated automation across both systems from a unified data source
- Hybrid work pattern adaptation: BMS control logic redesigned around genuinely variable, unpredictable daily occupancy rather than fixed 9-to-6 assumptions — reflecting India's 40-60% average post-pandemic office occupancy reality
- Privacy-preserving architecture: DPDP Act 2023-conscious design using anonymised body-count analytics — avoiding biometric/identity data classification through edge processing and aggregate-only data transmission
- Predictive occupancy modelling: Meeting room booking data and historical attendance patterns combined with real-time detection to pre-condition zones 15-20 minutes ahead of anticipated arrival, eliminating comfort recovery lag
- Access control cross-reference: Turnstile entry data as a secondary occupancy signal source, cross-referenced with computer vision counting for accuracy validation and redundancy
- Hot-desking granularity: Desk-level sensors or booking system integration providing finer-grained occupancy data for flexible seating environments where zone-level assumptions break down
Individual Comfort Profiles: Occupancy Meets Personalisation
Future occupancy-based automation will move beyond zone-level aggregate response toward individual comfort personalisation — combining anonymised occupancy detection with opt-in personal comfort preference profiles (accessed via a mobile app, not tied to identity in the BMS) to deliver micro-zone conditioning tuned to the specific mix of people present in a space at any moment. A meeting room's HVAC will automatically bias toward the average preference of the specific attendees who have checked in for that meeting, without the BMS ever needing to know who those individuals are — preference data remaining under the individual's control on their device, contributed anonymously and aggregated only at the point of use.