Portfolio and building priorities
Cost drivers, operating signals, evidence, forecasts, and actions.
Operations viewOptional resident layerPersonal utility clarity,
Personal utility clarity,
without the noise.
Where authorized unit-level information is available, a focused resident experience can explain personal patterns and support practical action.
Building intelligence comes first; resident access is evaluated separately.
My utility viewSample data · Unit 1204 · June 2026
Your electricity is near its recent average.
−4%electricity
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.
Two audiences / clear boundaries
One intelligence layer. Two appropriately different views.
Management needs building-level priorities. Residents need a private, simple explanation of the information they are authorized to see.
Personal trends and guidance
Only authorized unit data with relevant, easy-to-understand context.
Private viewResident experienceSimple enough to use.
Simple enough to use.
Specific enough to matter.
The experience is built around questions a resident can understand and influence—not an operations dashboard reduced to a smaller screen.
01
Personal usage trends
Make authorized unit records readable across recent periods and personal baselines.
02
Meaningful changes
Surface notable personal changes without overwhelming residents with technical detail.
03
Rate-plan guidance
Explain lower-cost electricity periods where supported plans and interval data apply.
04
Bill understanding
Explain common usage and billing factors in clear, resident-friendly language.
05
Possible water signals
Show personal patterns only where authorized submeter data supports the view.
06
Practical guidance
Offer relevant conservation opportunities shaped by the available data.
Data readinessCapability follows
Capability follows
the available meter data.
Not every building supports every resident feature. The experience matches the utility, authorization, and level of data available.
Electricity
Often the strongest starting point
Unit-level billing or smart-meter access may support personal trends and time-based guidance.
- Personal usage history
- TOU or ULO guidance where applicable
- High-usage period review
- Recent-baseline comparison
Water
Available where units are submetered
Authorized unit-level water records may support personal trends and possible usage signals.
- Personal water trend
- Recent-period comparison
- Possible unusual-use indicator
- Conservation guidance
Gas & heating
Often shared at building level
When heating is central, resident information may focus on building trends and education.
- Seasonal explanation
- Weather-informed communication
- Building trend education
- Unit support where available
Privacy-conscious by design
Resident information stays in the right hands.
The resident layer uses only authorized data, avoids exposing another unit or occupant, and relies on aggregated comparisons when a benchmark adds value.
No unit-to-unit exposure
No identifiable information from another home.
Authorized access only
Capabilities follow approved data access.
Purpose-limited views
Only information useful to the resident experience.
Aggregated comparison
Grouped information where a benchmark is appropriate.
A staged rolloutProve building value.
Prove building value.
Then evaluate resident access.
The resident layer is introduced only where suitable data, authorization, privacy, and practical value are confirmed.
Building pilot
Validate the core analysis and management reporting for one property.
Data & permission review
Confirm unit-level availability, authority, and appropriate use.
Resident experience
Introduce only the capabilities the building can support responsibly.
Not required for the core platform. Building-level Utility AI can deliver value without a resident rollout.
Begin at the building level
Request pilot Evaluate resident value in the right order.
Request a core building pilot first. Unit-level data and resident capabilities can be reviewed later when relevant.