What you will learn
- Interval consumption views by site, building, meter, and circuit
- Cost and carbon conversion with configurable tariffs and factors
- Baseline comparison against prior periods and weather-normalised figures
- Anomaly alerts for overnight use, spikes, and missing meter data
- Tenant and department cost allocation from submeter readings
What a energy monitoring dashboard is
Energy bills arrive too late and too aggregated to change behaviour. A single monthly total cannot say whether a chiller ran overnight, a production line idled at full power, or a tenant's usage spiked. Monitoring software collects interval readings from meters and submeters, aligns them with time and weather, and presents consumption, cost, and carbon views that a facilities manager can act on the same week.
The dashboard's core job is reconciliation: metered totals must match billed totals, and submetered parts must add up to the whole. Where they do not, the gap itself is information — an unmetered load, a faulty meter, or an estimation error. Good dashboards surface those gaps instead of smoothing them away, because an energy programme built on wrong baselines saves nothing verifiable.
Who uses it
Facilities managers, energy managers, sustainability teams, and portfolio owners use it. Tenants and department heads see their own consumption, and finance sees cost allocation based on measured use rather than floor area.
Core features
The features below are the ones buyers check first when evaluating a energy monitoring dashboard.
- Interval consumption views by site, building, meter, and circuit
- Cost and carbon conversion with configurable tariffs and factors
- Baseline comparison against prior periods and weather-normalised figures
- Anomaly alerts for overnight use, spikes, and missing meter data
- Tenant and department cost allocation from submeter readings
- Peak-demand tracking with the dates and causes of each peak
- Exportable reports for audits, certifications, and management review
- Meter health views showing offline, estimated, or faulty meters
How it is built
Build in this order, and do not skip the validation step at the end of each phase.
- Inventory meters and data sources. List every utility meter, submeter, and data feed, and establish how readings arrive — automated feeds, manual reads, or bill data — before designing screens.
- Build the metering data core. Store interval readings with meter identity and timestamps, and reconcile metered totals against bills from the start.
- Build consumption and cost views. Provide site, building, and circuit breakdowns with tariff-based costing and period comparison.
- Add alerts and allocation. Alert on anomalies and missing data, and allocate costs to tenants or departments from measured readings.
- Add baselines and reporting. Implement weather-normalised baselines and exportable audit and management reports.
- Validate one site end to end. Reconcile one site's dashboard totals against its actual bills for two months before rolling out to the portfolio.
Never present estimated readings as measured ones. Label estimated intervals clearly, or the first audit will discredit every saving the dashboard claims.
Technology considerations
Metering data is messy in specific ways: clocks drift, meters report in different units and intervals, and communication gaps create holes. The platform needs robust ingestion that normalises units and intervals, flags estimates, and preserves raw readings beside cleaned ones. Tariff handling also needs care, since rates change and historical costs must be recalculated consistently.
- Time-series storage for interval readings, separate from billing records
- Ingestion adapters for common meter protocols and utility data formats
- Raw-plus-cleaned storage so any figure can be traced to its source reading
- Configurable tariffs, carbon factors, and allocation rules with effective dates
- Role-based access separating portfolio, site, and tenant views
Challenges and how to handle them
Energy dashboards fail when baselines are never agreed. If last year's consumption is not established and weather-normalised, every claimed saving is arguable and the programme loses credibility. They also fail when meter gaps are hidden: a missing month silently becomes a zero, and consumption appears to fall.
- Baselines never agreed, so savings claims are disputed
- Estimated readings presented as measured data
- Meter communication gaps silently treated as zero consumption
- Tariffs applied without effective dates, corrupting historical costs
- Portfolio rollouts before a single site reconciles to its bills
What to check before launch
Before launch, reconcile one site's dashboard totals against its actual utility bills for two full months, including a month with estimated readings and a month with a meter communication gap. If metered totals do not match billed totals, find out whether the gap is an unmetered load, a faulty meter, or an estimation error, and surface that gap in the dashboard rather than smoothing it away. Test anomaly alerts against real events: overnight use, a genuine spike, and a missing meter, and confirm each alert is actionable rather than noise. Agree baselines with the site team, weather-normalised, before claiming any savings, because an energy programme built on an unagreed baseline will have every saving disputed. Only roll out to further sites once the pilot site reconciles.
What a good first version looks like
A good first version covers one or two sites completely: interval views, cost and carbon, anomaly alerts, and bill reconciliation. Portfolio benchmarking, forecasting, and tenant billing follow once the pilot sites reconcile.
Costs and timelines vary with scope, integrations, and the number of sites or users involved. Treat any figure you see online as a rough range only, and confirm with a written quote for your specific requirements before committing budget.
Frequently asked questions
How is this different from a utility bill portal?
A bill portal shows what you were charged. This dashboard shows what you used, when, and where — by circuit and by hour — which is what lets you reduce the next bill.
Do we need new meters?
Not always. Many sites start with utility interval data and existing submeters, adding meters only where a large load is currently invisible.
What is weather normalisation?
Adjusting consumption for how hot or cold a period was, so a mild winter does not masquerade as an efficiency saving, and a heatwave does not hide real progress.
Can tenants be billed from submeter data?
Where local rules and lease terms allow, yes, but billing use requires higher accuracy and audit standards than internal reporting. Confirm the legal position before billing from the dashboard.
How accurate must the data be?
Accurate enough to reconcile with bills and to support the decisions being made. Internal efficiency work tolerates small gaps if they are labelled; tenant billing does not.