Summer usage rise
Building utility intelligence
Turn utility data into decisions.
Explain cost changes, surface patterns worth checking, forecast what comes next, and give management one clear view of electricity, water, and gas.
One view. Three utility systems.
Above own average
Heating-season decline
Jul 2025–Jun 2026. Compare patterns, not quantities across utilities.
| Month | Electricity kWh | Water m³ | Gas m³ | Electricity index | Water index | Gas index |
|---|---|---|---|---|---|---|
| Jul 2025 | 43500 | 1020 | 4200 | 108.9 | 93.8 | 46.5 |
| Aug 2025 | 44800 | 1015 | 4150 | 112.1 | 93.3 | 46.0 |
| Sep 2025 | 40800 | 990 | 4900 | 102.1 | 91.0 | 54.3 |
| Oct 2025 | 37000 | 1005 | 7000 | 92.6 | 92.4 | 77.5 |
| Nov 2025 | 36500 | 995 | 10400 | 91.4 | 91.5 | 115.2 |
| Dec 2025 | 39400 | 1010 | 14200 | 98.6 | 92.8 | 157.3 |
| Jan 2026 | 40800 | 1080 | 17000 | 102.1 | 99.3 | 188.3 |
| Feb 2026 | 39200 | 1120 | 15600 | 98.1 | 102.9 | 172.8 |
| Mar 2026 | 38100 | 1160 | 12100 | 95.4 | 106.6 | 134.0 |
| Apr 2026 | 36600 | 1200 | 8100 | 91.6 | 110.3 | 89.7 |
| May 2026 | 39900 | 1220 | 5900 | 99.9 | 112.1 | 65.3 |
| Jun 2026 | 42800 | 1240 | 4800 | 107.1 | 114.0 | 53.2 |
Check the sustained water increase.
Monthly use is above its own average. Check billing periods and occupancy before drawing a conclusion.
Review the source recordElectricity use rises into summer.
A utility bill shows what happened.
Your team needs to know why.
Rates, weather, occupancy, equipment, and building events all change what a number means. Utility AI connects those factors before it presents a finding.
Rates & location
Connect each bill to supported provider, municipal, and time-based pricing context.
Weather & season
Separate heating and cooling pressure from changes that deserve a closer look.
Building reality
Account for occupancy, systems, amenities, renovations, and known operating events.
Different behaviour.
One operating picture.
Electricity, water, and gas need different analytical lenses. The platform keeps those distinctions clear while bringing the decisions together.
Sample data
When usage becomes cost.
Review supported rate plans, high-cost periods, peak behaviour, and large building loads.
Peak 126 kW at 17:00. Cost also depends on the rate plan.
| Hour beginning | Mean demand kW |
|---|---|
| 00:00 | 38 |
| 01:00 | 35 |
| 02:00 | 33 |
| 03:00 | 32 |
| 04:00 | 34 |
| 05:00 | 40 |
| 06:00 | 55 |
| 07:00 | 68 |
| 08:00 | 72 |
| 09:00 | 76 |
| 10:00 | 81 |
| 11:00 | 85 |
| 12:00 | 89 |
| 13:00 | 94 |
| 14:00 | 101 |
| 15:00 | 110 |
| 16:00 | 118 |
| 17:00 | 126 |
| 18:00 | 112 |
| 19:00 | 93 |
| 20:00 | 72 |
| 21:00 | 60 |
| 22:00 | 49 |
| 23:00 | 42 |
- Rate and tariff context
- Peak-period review
The pattern behind the increase.
Compare consumption with billing periods, occupancy, and persistent overnight use.
Dashed: 3 L/min reference. Verify overnight activity.
| Sample time | Flow L/min |
|---|---|
| 00:00 | 7.6 |
| 01:00 | 7.3 |
| 02:00 | 7.4 |
| 03:00 | 7.1 |
| 04:00 | 7.2 |
| 05:00 | 7.5 |
| 06:00 | 9.2 |
- Possible abnormal-use signals
- Occupancy context
Weather pressure or performance.
Review heating-season changes beside temperature, equipment, and operating events.
Dashed: weather estimate. Shaded: comparison band ±10%.
| Month | Observed gas m³ | Heating degree days (example) | Model estimate m³ |
|---|---|---|---|
| Jan 2026 | 17000 | 625 | 16700 |
| Feb 2026 | 15600 | 565 | 15500 |
| Mar 2026 | 12100 | 385 | 11900 |
| Apr 2026 | 8100 | 200 | 8200 |
| May 2026 | 5900 | 80 | 5800 |
| Jun 2026 | 4800 | 30 | 4800 |
- Weather-informed review
- Next-period forecast
Raw records in.
Defensible next steps out.
Utility AI does not treat every spike as a conclusion. It connects the available evidence, identifies what the evidence can support, and separates a useful signal from something that still needs verification.
Explore the platformStart with what you have.
Add depth when it matters.
A pilot can begin with bills and a basic property profile. Better source data improves the depth and confidence of the review.
Describe the building
Location, systems, occupancy, and the operating context already known.
Add the utility record
Start with bills. Add history or interval data when it improves the question.
Connect the context
Align pricing, weather, baselines, data quality, and relevant events.
Review the decision brief
See findings, evidence, confidence, limitations, and ranked next steps.
Not another dashboard to interpret.
Bring the important signals into one concise brief: cost and usage trends, pricing context, weather-informed observations, possible actions, limitations, and confidence.
Executive summaryPriority findings in management language.
Transparent evidenceSources, assumptions, and confidence stay visible.
Ranked next stepsClear items for operations or deeper review.
What deserves attention this month.
North Tower · Toronto · June 2026
Summer useReview schedules
Water trendVerify context
Heating contextCompare weather
Same 12-month averages as the building overview.
| Month | Electricity index | Water index | Gas index |
|---|---|---|---|
| Mar | 95.4 | 106.6 | 134.0 |
| Apr | 91.6 | 110.3 | 89.7 |
| May | 99.9 | 112.1 | 65.3 |
| Jun | 107.1 | 114.0 | 53.2 |
Your electricity is near its recent average.
Below your recent averageJune kWh compared with the previous six months.
Jun 403.2 kWh. Dashed: prior 6-month mean 420 kWh.
| Month | Electricity kWh |
|---|---|
| Dec | 430 |
| Jan | 450 |
| Feb | 420 |
| Mar | 410 |
| Apr | 400 |
| May | 410 |
| Jun | 403.2 |
ElectricityCheck your plan’s lower-cost hours.
WaterPersonal trends need unit-level data.
Seasonal noteCooling can affect summer electricity use.
Only authorized unit data is shown. Building comparisons are aggregated.
From building intelligence to personal clarity.
Where authorized unit-level information is available, residents can receive a private view of personal trends, seasonal context, and practical guidance.
Privacy-consciousAuthorized unit data and aggregated comparisons only.
Actionable contextSimple explanations instead of raw meter data.
One building is enough to begin.
No utility documents are needed in the first step. Share the property context and the question your team needs to answer.