Energy & Utilities · Facilities
Each building’s load for tomorrow, by the hour, before the plant starts
Next-day energy forecasts for a facilities portfolio, tested on 3,326,535 real metered building-hours against the same-day-last-week profile.
Executive summary
A next-day forecast cuts hourly error to 7.3% from 12.2% for the same day last week across 400 real metered buildings, and alerts on 4.6% of building-days instead of 10.2%.
Situation
BMS alerts compare today with last week, so they fire on ordinary days.
Approach
One portfolio model forecasting each building’s next day by the hour, tested on 3,326,535 building-hours.
Result
Closer in 100% of buildings; overspend alerts cut by more than half.
The problem
A facilities team running campuses, offices and residences sets each building’s expected load for tomorrow, for HVAC start times, demand charges and the overnight alert that something has been left running. Most building management systems compare today with the same day last week, which drifts with weather, term dates and holidays, so alerts fire on ordinary days and miss real ones.
I measured how much closer a next-day forecast gets to each building’s hourly load than the same-day-last-week profile, and how many false overspend alerts it removes.
- Team
- Head of facilities, energy manager, building services engineers
- Scale
- Hundreds of metered buildings across several sites
- Systems
- Interval meters, BMS such as Siemens Desigo or Johnson Controls Metasys, energy management platforms, weather feeds
- Measure
- Hourly forecast error; false overspend alerts per building-month; peak forecast error
What I built
A next-day forecast of every building’s hourly electricity, issued at midnight. It reads the building’s own last week and last four weeks, yesterday’s level and peak, the hour, the day of the week, the season, the outdoor temperature and the building’s use type. One model covers the portfolio, scaled to each building’s level, so a new building is forecast once it has a month of readings.
Results
I tested on the Building Data Genome 2 project: real hourly electricity meters from 1,578 non-residential and residential buildings across North America and Europe. 400 buildings with near-complete metering were chosen at random, the forecast was fitted on 2016 and tested on 3,326,535 building-hours in 2017.
| Next-day estimate | Hourly error | Daily peak error | Building-days over by 20% |
|---|---|---|---|
| Next-day forecast | 7.3% | 5.3% | 4.6% |
| Same day last week | 12.2% | 7.1% | 10.2% |
| Same weekday, four-week average | 11.7% | 8.2% |
Overspend alerts
With the same-day-last-week profile, 10% of building-days ran more than 20% over the expectation and would raise an alert. With the forecast, 4.6% did, so far fewer ordinary days raise an alert.
Data and method
- Data
- Building Data Genome 2 (CC BY 4.0): cleaned hourly electricity meter readings for 1,578 buildings at 19 sites, 2016 and 2017, with building use, floor area and site weather. Buildings are identified only by pseudonyms in the release and are not named here.
- Selection
- 874 buildings with readings for at least 97% of hours and few zero readings; 400 chosen at random
- Forecast
- Gradient-boosted regression of each hour’s load relative to the building’s last-week average, on its own lagged profiles, hour, weekday, day of year, outdoor temperature, use type and floor area; fitted on 2016, tested on 2017
- Comparisons
- Same day last week, yesterday, the last seven days, and the same weekday over four weeks
- Measures
- Hourly absolute error as a share of metered use; median error on each day’s peak; share of building-days over the expectation by more than 20%
Limitations
- The test uses the observed temperature for the next day. A live forecast uses the weather forecast, which adds a small error on hot and cold days.
- Mostly university campuses and public buildings in 2016 and 2017. The model is refitted on the portfolio’s own meters and calendars.
- An alert shows the day ran over the expectation; a site check confirms the cause.
- Electricity only. Gas, chilled water and steam meters follow the same method with their own weather response.
How I would take it live
- Connect a year of interval data and the BMS calendar for each building
- Fit the forecast and set alert thresholds with the energy manager
- Run alerts beside the existing BMS comparison for a month
- Adopt with false alerts and confirmed faults counted each month