1Your hotel's demand
Peak demand is the most power (kW) the hotel draws at one time, shown on your electricity bill or utility portal. The monthly profile is optional but makes the eligibility check more accurate.
| Month | Peak demand (kW) | Energy used (kWh) |
|---|
Leave a month blank if you don't have it; averages use the months you enter.
Monthly peak demand
Against the Class A thresholds set in Step 4.
2Equipment you can shift
For each system, the power it draws on a hot afternoon (kW) and the share you could turn down or move to another time for one peak hour without hurting guests.
| Equipment | Load on a hot afternoon (kW) | % you can shift | kW cut | How |
|---|
3How well you'll respond
Nobody knows the peak hours in advance. Alert services flag likely peak days, so hotels act on 10 to 15 alerts a summer to be sure of catching the 5 that count.
4Assumptions
Reasonable starting values for recent years. These are assumptions: check them with your utility or energy advisor, because GA costs change every year and the ICI rules are reviewed by the province.
Results
Saving vs peaks caught
Annual GA saving under Class A for each number of peak hours you manage to cut, before the pre-cooling cost. The darker bar is your expected result.
Where the kW come from
Each system's share of the kilowatts cut during a peak hour.
Contribution by equipment
Annual saving each system brings at your expected catch rate.
Class A or Class B?
A year of GA under each option, using the assumptions in Step 4.
5Peak day playbook
Print this for engineering, laundry and the front desk. Tick items off on an alert day; ticks are saved in this browser. Steps for equipment you set to 0 kW are left out.
Doing this by hand every alert day is the hard part. An AI agent can watch the IESO demand forecast, decide when to pre-cool and send the playbook to each department automatically.
See how an AI swarm does this automaticallyHow it's calculated
Class A GA charge. The real charge is your peak demand factor (your demand in the peak hours ÷ Ontario's demand in those hours, averaged over the 5 hours of the May to April base period) × the total Global Adjustment for each month of the following year. This tool simplifies that to demand in the peak hours (kW) × GA cost per kW-year. The default of $450 per kW-year is a rough figure in line with recent years. It is an assumption, check with your utility: it moves with the province's total GA cost and total peak demand.
kW cut = sum over equipment of load × % you can shift, capped at your demand in the peak hours. Expected peaks caught = share caught × number of peak hours. Because the charge uses the average over the peak hours, cutting C kW in k of N hours lowers your average by C × k ÷ N. Annual saving = C × k ÷ N × GA cost per kW-year.
Pre-cooling cost = alert days × hours per alert × kW cut × rebound % × energy price. Net saving = saving minus that cost. Payback = setup cost ÷ net saving.
Eligibility. The check uses your average monthly peak (from the profile when it is switched on). Above the Class A threshold (1 MW by default) a customer can opt in; above 5 MW Class A is automatic. Between 500 kW and 1 MW, opt-in has historically been limited to certain sectors such as manufacturing and greenhouses, so a hotel in that band should check with its utility. Opting in is usually done once a year, before the base period starts.
Class B comparison = annual kWh × the Class B GA rate. Annual kWh comes from the profile, or is estimated as average peak × 8,760 hours × 55% load factor when there is no profile.
Limits. This is an estimate for planning, not a bill calculation. It ignores transmission charges that also use peak demand (which add to the saving), weather-driven changes in your load, and the risk that a missed peak lands on a day you did not get an alert. Your inputs are stored only in this browser.