A typical Indian office’s HVAC operates 8-10 hours per workday (typically 8 AM-7 PM) with peak occupancy mid-day. Yet many buildings run cooling 24/7 at design conditions, including weekends + nights. The simplest, lowest-cost energy reduction lever is occupancy-based cooling scheduling — reducing or shutting cooling outside occupied hours.
This guide covers the four scheduling strategies, their implementation in BMS/BAS, and the energy savings achievable.
Why scheduling matters more than equipment efficiency
Equipment efficiency improvements (5-star chiller, premium motors) typically yield 10-15% energy reduction. Smart scheduling typically yields 25-35%. Sequencing the two: start with scheduling discipline, then optimize equipment.
Four scheduling strategies
Strategy 1: Time-of-day scheduling (basic)
Cooling on at 6:30 AM (90 min before occupancy); off at 7:30 PM (30 min after); off weekends/holidays.
Energy reduction: 30-40% vs 24/7 operation.
Implementation: BMS clock + day-of-week logic. Most building BMS already supports this.
Indian gotcha: Non-standard occupancy (overnight IT shifts; weekend retail) means the schedule must be customized per building.
Strategy 2: Setpoint setback (intermediate)
Setpoint relaxed during unoccupied hours: 24 °C → 28 °C cooling; 21 °C → 17 °C heating. Equipment runs to maintain the setback temperature, not full design.
Energy reduction: 35-50% vs 24/7 design setpoint.
Implementation: BMS scheduled setpoint reset.
Compromise: Building takes 30-60 min to ramp from setback to occupancy setpoint. Either start ramp early (at expense of energy savings) or accept some morning discomfort.
Strategy 3: Occupancy-detected scheduling (advanced)
PIR / time-of-flight occupancy sensors trigger zone cooling on demand. If conference room is empty for 30 min, zone setpoint setback engages. If meeting starts unexpectedly, sensor detects occupancy + cooling ramps.
Energy reduction: 40-60% in highly variable spaces (conference, meeting rooms).
Implementation: Zone-level PIR/ToF sensors connected to BMS.
Capex: ~₹15-25k per zone for sensor + integration.
Strategy 4: Predictive scheduling (most advanced)
ML model predicts occupancy + sets schedule in advance. Uses calendar data, weather forecast, historical patterns.
Energy reduction: 50-65% in complex buildings (mixed-use, hospitality).
Implementation: AI-augmented BMS (Trane Tracer SC+, JCI Metasys Edge, Honeywell WEBs predictive); typical capex ₹2-5 lakh per building.
BMS programming logic
For a typical Indian office, the scheduling program looks like:
Mon-Fri:
06:30 - cooling start; ramp to occupancy setpoint by 08:00
17:30 - 19:00 - setback initiation (28 °C cooling)
19:00 - cooling off; setback continues (only fans, dehumidification)
Sat:
09:00 - cooling start (if 50%+ occupancy on Saturdays)
14:00 - cooling off
Sun + Holidays:
Cooling off entirely
Setback only via natural infiltration
Per-zone overrides (if occupancy sensor active):
Empty 30 min → zone setpoint drops to 27 °C
Empty 60 min → zone equipment off
Occupancy detected → zone returns to 24 °C, equipment cycles on
Implementation in commercial BMS: standard scheduling tools handle Strategy 1 + 2 natively. Strategy 3 requires sensor wiring + BMS programming. Strategy 4 requires firmware upgrade or integration with predictive analytics platform.
Energy savings — worked example
5,000 m² Bangalore office:
Without scheduling (24/7 design):
- Annual energy: 1,500 MWh = ₹15 crore/yr at typical office tariff
- EUI: 300 kWh/m²/yr
With Strategy 1 (basic time-of-day):
- Annual energy: 1,000 MWh = ₹10 crore/yr (33% saved)
- EUI: 200 kWh/m²/yr
With Strategy 2 (setback):
- Annual energy: 850 MWh = ₹8.5 crore/yr (43% saved)
- EUI: 170 kWh/m²/yr
With Strategy 3 (occupancy-detected):
- Annual energy: 750 MWh = ₹7.5 crore/yr (50% saved)
- EUI: 150 kWh/m²/yr
With Strategy 4 (predictive):
- Annual energy: 650 MWh = ₹6.5 crore/yr (57% saved)
- EUI: 130 kWh/m²/yr
For typical 5,000 m² office, savings going from no-scheduling to Strategy 3 = ₹5+ crore/yr. Capex for Strategy 3 ≈ ₹25-40 lakh. Payback < 1 year.
Common scheduling mistakes
1. Defaulting BMS to “always on” — many BMS ship with default 24/7 schedule; never customized for actual occupancy.
2. Setback temperature too aggressive — 30 °C setback in monsoon Mumbai means morning ramp takes 90 min; occupants arrive to hot office.
3. No occupancy sensor for variable spaces — conference rooms running cooling continuously despite 90% empty. Easy savings missed.
4. No holiday/exception calendar — Republic Day cooling running with empty building.
5. No periodic schedule audit — schedule set in 2020 still running in 2026 despite occupancy shifts.
Quick checklist
- [ ] BMS schedule reviewed quarterly + customized for actual occupancy
- [ ] Setback engaged 30-60 min before close + lifted 60-90 min before opening
- [ ] Setback temperature 28 °C (cooling) / 17 °C (heating) acceptable
- [ ] Occupancy sensors in conference/meeting rooms
- [ ] Holiday calendar imported into BMS
- [ ] Annual occupancy survey to validate schedule fit
- [ ] BMS schedule logged in commissioning documentation
References: ASHRAE 90.1-2022 §6.4.3 (HVAC Controls); ECBC 2017 §5.4 (Controls); ISHRAE Handbook Volume 7 (BMS); ASHRAE Handbook HVAC Apps 2023 Ch 47.
[Disclosure block, Legal notice — auto-included by article template]