Blog
Energy Overview: consumption monitoring for multi-site portfolios
On this page
Executive summary
Energy Overview (formerly the Consumption Monitoring Application) industrialises energy governance for multi-site portfolios, where fragmented data silos typically stall sustainability efforts. Acting as a centralised command centre, it standardises the workflow, from anomaly detection to a recorded saving. In this article, we look in depth at the technical architecture, the KPIs and the operational workflows that turn energy management from a reactive task into a scalable, strategic enterprise function.
The complexity wall: why traditional energy management fails at scale
In a small-scale environment, energy monitoring remains a straightforward operational exercise. However, as a portfolio grows beyond 50 sites, energy management turns from a technical challenge into an organisational crisis.
At this scale, the “complexity wall” emerges. Data resides in silos, fragmented across different utility providers, incompatible Building Management Systems (BMS) and manual spreadsheets. The result is a lack of visibility that hides large operational inefficiencies. Facility managers are overwhelmed by “alarm fatigue”, while executives set ambitious Net-Zero and ESG targets without a central mechanism to track, validate or accelerate progress.
To bridge this gap, organisations must move beyond passive monitoring. They need a multi-site consumption monitoring application designed to industrialise energy efficiency across the entire asset lifecycle.
The solution: a central hub for distributed portfolios
Most modern enterprises have defined rigorous sustainability goals. Yet there remains a deep disconnect between corporate strategy and site-level reality.
Energy Overview serves as the single source of truth. It turns raw data into a structured layer of information, providing the central space needed to track initiatives and guide decentralised teams towards common consumption reduction targets. It is no longer only about seeing data; it is about steering performance.
Inside the application
Energis.Cloud is built on four technical pillars that allow it to scale without compromising on granularity or performance.
1. The centralised data and universal metric catalogue
The foundation of the application is a catalogue of standard metrics, fed by the data sources of each site.
-
Data integration: 121 data-source connectors are ready (grid operators, metering companies, inverters, measurement devices, gateways, building systems and weather), and five routes need no connector at all: HTTP, MQTT, SFTP, email and a file uploaded through the portal. See data collection.
-
Ready-made KPIs, grouped by what you use them for. The app switches on these KPIs for every site, for each energy and at each level of the portfolio, from a meter up to all your sites:
- Consumption: consumption, net electricity consumption (with own production), main meter against its sub-meters, monthly and yearly totals.
- Benchmarking: consumption per m², the portfolio average per m², and what each site would use at that average, so the gap is in kWh.
- Waste and out-of-hours use: consumption during and outside opening hours, the drop after closing, and the baseload that never switches off.
- Weather normalisation: heating and cooling degree days, and weather-adjusted consumption, so a mild winter does not look like a saving.
- Cost and carbon: cost per energy from each site’s price, and CO₂ per energy from each site’s factor.
- Data quality: the share of expected readings that arrived, so every figure says how far it can be trusted.
The full list of 71 KPIs, with what each one tells you and how it is calculated, is in the energy KPI guide.
2. High-performance dashboards and use cases
-
Portfolio ranking: identify the “bottom 10%” performers across hundreds of sites to prioritise capital expenditure (CapEx) and maintenance interventions.
The portfolio overview of a demonstration account: sites on a map coloured by status, and a table ranking them by electricity per m², drop at night and gas per m², with the change against the previous year. -
Climate-normalised performance (HDD/CDD): use Heating and Cooling Degree Days to remove “weather noise”. A spike in consumption is then identified as an operational failure rather than just a cold snap, which allows a fair comparison between sites in different micro-climates.
Gas consumption of a site plotted against heating degree days, with the regression line and its r², and the monthly consumption next to the degree days over the same year. -
Load curve analysis: visualise the “pulse” of a building to detect unauthorised overnight consumption or early equipment start-ups.
-
Peak demand shaving: identify the exact timestamps of peak loads to redefine operational schedules and reduce power demand penalties.
The load curve of a site with its maximum (96.46 kW) and a memo on the timeline, next to the power duration curve that sorts every day of the period by its peak. -
Heatmap visualisation: displays energy intensity on a 24/7 grid. Managers can spot temporal patterns of waste at once, such as equipment starting too early or running too late.
Hourly electricity consumption over one month: each row is a day, each column an hour, and the colour shows the load, so opening hours, closed days and early starts stand out. -
Baseload and non-operational drift: isolate the “standing load” of each facility. By quantifying the energy consumed when the site is closed, the system identifies “silent waste” such as failed lighting sensors, redundant HVAC schedules or equipment left in standby mode.
Electricity use of a site during opening hours, staff-only hours and closed hours, with the drop after closing (69%) compared with the portfolio average. -
Operational alignment (occupancy vs. energy): overlay energy consumption with occupancy data or production logs. This detects “ghost consumption”, situations where energy intensity remains high despite low footfall or zero production output, so that schedules can be tuned precisely.
-
End-use breakdown and sub-metering granularity: combine a top-down and a bottom-up analysis. By integrating sub-metering data, the system breaks down site-level consumption into functional categories, such as HVAC, lighting or electric vehicle charging stations, and identifies which subsystem is driving portfolio-wide waste.
Thirty submeters of one building on a single chart, from HVAC and lighting to charging stations, with the data availability of each meter for the day in the table on the right. -
Similar period comparison: overlays consumption data from two different time periods (e.g. this week vs. last week). This is the main tool to verify the impact of energy-saving actions or to detect sudden drifts in performance.
A profile chart that lays five consecutive weeks over each other, so a change in the daily pattern after a saving action is visible at a glance. -
Regression analysis and target follow-up: plot consumption against an activity driver (e.g. production volume, occupancy or degree days) with its regression line, and follow each site in a “target vs. actual” view that highlights the sites missing their target.
-
Carbon footprint: translate kWh and m³ into CO₂ equivalents with the emission factors you set. This takes energy data from the boiler room to the boardroom, and the platform holds the data behind the figures you report for ESG.
CO₂ emissions from electricity and gas, split by country, as pie charts for the year and as monthly bars.
3. The Energy Engagement Portal: making performance visible to everyone
Technical solutions often fail because they are too complex for the people on the ground. The Energy Engagement Portal addresses this with a simplified, mobile-first UX.
- Simplified UX: a dedicated, mobile-responsive portal designed for site managers and occupants.
- Transparency: by making energy data visible and easy to read, we foster a culture of accountability.
- Automated periodical reports: tailored reports are sent on a schedule to the people attached to each site, so the right information reaches the right person at the right frequency.
4. Anomaly detection and action management
This is the engine of the “action-oriented journey”. You write each anomaly rule as a condition on any metric, and it runs on every site in the group.
- Rules that fit each site: a threshold can be a metric rather than a fixed number, such as a contracted power or a per-site limit from a lookup, so one rule detects the drifts that indicate equipment failure or human error on a small site and a large one.
- Integrated Action Manager: once an anomaly is detected, the workflow stays within the platform. The anomaly becomes an action with an owner and a date, and the Actions board shows the estimated yearly savings directly on each card, so you can prioritise by return on investment.
The workflow: the “action-oriented journey”
The value of the application comes from a disciplined operational workflow. This is how high-performance energy departments work in Energis.Cloud:
- The anomaly inbox: the energy manager starts the day in the anomaly inbox. Instead of hunting for problems, the manager filters the anomalies of the whole portfolio by severity, status or site.
- Diagnostic deep-dive: using the integrated dashboards, the manager analyses the load curve of the flagged site and determines whether the spike was a one-time event or a systemic failure.
- Mobilising action: through the Action Manager, the energy manager assigns a task to the local facility team.
- Portfolio-wide follow-up: the manager then switches to a portfolio-wide view to check that global performance is trending towards the quarterly objective. If one region is lagging, they reallocate resources based on the “bad performer” rankings.
- Transparent reporting: scheduled reports and Orbit, which writes up the performance, the anomalies and the savings in plain language, show the Board the return on the energy department’s interventions.
The result: one tool for the whole journey, from the finding to the recorded saving.
Conclusion: the “CRM” for the energy department
In the same way that a sales department cannot function without a CRM, or a finance department without an ERP, a modern energy department cannot scale without a dedicated consumption monitoring application.
Ambitious sustainability objectives require more than good intentions; they require a scalable system that industrialises efficiency.
Key functionalities at a glance
- Templates at every level: a metric, an anomaly rule or a report applies to every matching site.
- Data ingestion: 121 data-source connectors, plus HTTP, MQTT, SFTP, email and portal upload.
- Advanced analytics: load curve, peak detection and benchmarking.
- Closed-loop action management: integrated task tracking and resolution history.
- Engagement portal: mobile-optimised UX for non-technical stakeholders.
- Automated governance: periodical reporting and portfolio-wide KPI tracking.
Better together: focusing on electricity waste
The Waste Finder app focuses on electricity waste: it learns the normal use of each site and flags what goes beyond it, by day and by night, and anomaly rules, escalation by email and dashboards that rank the sites do the rest. See finding electricity waste on every site. Orbit can then read the data, the memos and the actions together, list the most likely causes and recommend the next step.
Frequently asked questions
Can the system track water and thermal energy in addition to electricity?
Yes. The metric catalogue covers the primary energy vectors, including electricity, natural gas, water and thermal energy.
Is there a limit to the number of assets the platform can track?
There is no fixed limit. Templates apply a metric, an anomaly rule or a report to every matching site, so the second thousand sites take no more work than the first.
How does the platform handle data from different hardware vendors?
Through 121 data-source connectors ready, from grid operators to building systems, and through five routes that need no connector: HTTP, MQTT, SFTP, email and portal upload. A source that is not on the list is a development with a lead time and a cost.
Is the platform suitable for non-technical staff or site managers?
Yes. The Energy Engagement Portal provides a simplified, mobile-first UX designed to make energy data easy to read and to foster accountability among site occupants and managers.
How long does the typical implementation take?
Implementation depends on the size of the portfolio and on how the data arrives. The rollout can be phased, one group of sites at a time.
New articles and product updates by email
Guides, customer stories and what is new in Energis.Cloud. You can unsubscribe at any time.
We use your email address only to send these updates. See our privacy policy.
