Pre-cool before occupancy spike, reduce demand charge
72-hour staging schedule positions setpoints 90–120 minutes before morning occupancy, avoiding the steepest demand ramp of the day.
Learn moreHeatvelo calculates a 72-hour thermal demand forecast from your occupancy logs, weather data, and building envelope specs — and delivers a staging schedule your facilities team can read, question, and act on. No new hardware. Measurable demand charge reduction within the first billing cycle.
attributable to overcycling on peak-tariff intervals — the portion a staging schedule directly addresses
occupancy + weather + envelope data combined into a forward demand curve, updated nightly at 11 PM local time
typical on-peak vs off-peak price differential for Midwest commercial TOU accounts — what overcycling at the wrong hour actually costs
Most commercial buildings already generate the occupancy logs, BMS historian data, and weather forecasts needed to eliminate peak demand waste. The data exists — it's just never been combined into a forward-looking demand curve. Heatvelo is that combination: a thermal model calibrated to your specific building's envelope, oriented to your specific utility tariff structure, and delivered as a staging schedule your facilities team can read the morning before it runs.
No new hardware. We connect to your existing BMS historian via BACnet/IP or Modbus TCP and pull weather data from National Weather Service APIs. Occupancy comes from access control logs, WiFi device counts, CO2 sensors, or retail POS transaction counts — whatever your building already tracks.
The forecasting engine models your building's thermal mass, window-to-wall ratio, and orientation against the predicted occupancy curve and 72-hour weather forecast. Output includes 10th/90th percentile uncertainty bands. MAPE below 8% on the 24-hour horizon in validated pilots.
Each staging window specifies a start time, end time, setpoint offset in Celsius, and a confidence score. Delivered as a structured JSON feed via REST API or pushed directly via BACnet/IP or Modbus TCP to your existing BAS controllers — no BMS replacement required.
Each building type has a different occupancy signature and a different demand charge driver. A single fixed schedule can't serve all three — a forecast that knows your building can.
72-hour staging schedule positions setpoints 90–120 minutes before morning occupancy, avoiding the steepest demand ramp of the day.
Learn moreFoot-traffic data as occupancy proxy — right-sizing HVAC pre-conditioning per store per day, not worst-case fixed schedules.
Learn moreZone-segmented thermal model with independent staging schedules per floor cluster eliminates cross-zone HVAC interference.
Learn moreThree overlapping curves — occupancy pattern, outdoor dry-bulb temperature, and predicted HVAC demand — plotted across the full 72-hour window. Shaded peak-tariff zones mark the intervals with the highest demand charge exposure. Pre-cooling windows are labeled for direct staging schedule action the morning before they run.
Delivered as a structured JSON feed via REST API or pushed directly to your BAS via BACnet/IP or Modbus TCP. No new hardware. No BMS replacement.
"We'd been running fixed setback schedules for six years and assumed demand charges were just a cost of doing business. The pilot showed us exactly which 15-minute windows were driving our monthly peak — and what the pre-cooling timing needed to be to avoid them."
Regional Office Portfolio Operator, Pacific Northwest
"The staging schedule is readable. You can look at it the morning before and understand why the system is pre-cooling at 6:15 AM instead of 7. That matters a lot when your operations team needs to override it for a building event — they can do it confidently, not blindly."
Commercial Real Estate Operator, Midwest