Energy management software

Energy management software collects meter, utility-bill and building data across sites, then turns it into consumption reports, alerts and savings work. Check how quickly it onboards new meters and tariffs, and whether you can take your data with you.

Platforms in this directory

What to look for

What good looks like

  • Fast onboarding of meters, submeters, tariffs and BMS sources across many sites
  • Alerting, baselines, reporting and workflow support for the operations team
  • Clear export paths, so the buyer keeps control of its energy data

Red flags

  • The marketing shows dashboards but says little about how data gets in.
  • There is no public detail on historian, meter or BMS integration.
  • Savings claims come without the workflows or deployments behind them.

How to choose energy management software

Decide what kind of system you need

“Energy management software” describes several different products. A useful shortlist starts with the decisions the system must support, the people who will act and the time available to respond. See energy management with EpiSensor for the complete measurement-to-action approach and multi-site energy monitoring for portfolio operations.

Swipe to see every column

System type Primary job Typical data and action boundary Best fit
Site energy monitoring or EMIS Find waste, compare loads and verify improvements Meter and equipment data, analysis, alerts and investigation Energy teams that need dependable operational evidence
Building energy management system or BEMS Supervise and control building services HVAC, plant schedules, alarms and approved control commands Buildings where facilities teams operate connected plant
Portfolio energy software Compare sites, track targets and coordinate action Normalised site data, benchmarks, tasks and management reporting Multi-site organisations with common governance
Reporting and business intelligence Combine energy with finance, production or carbon data Curated exports, models and dashboards Teams with established analytics capability
DERMS or virtual power plant platform Coordinate flexible generation, storage and demand Forecasts, constraints, dispatch instructions and verified response Assets participating in grid or flexibility programmes

A product may cover more than one category, but breadth is not proof of depth. Ask the supplier to demonstrate the exact workflow your operators will use.

Write the decision and data contract

Document the decision before listing features. For example: “The site energy lead reviews out-of-hours electrical demand every Monday and assigns an investigation when a circuit exceeds its agreed baseline.” This identifies the user, cadence, comparison and required action.

Define the data contract at the same time:

Swipe to see every column

Item What to specify
Site and asset identity Stable identifiers, hierarchy, location and ownership
Point identity Physical meter or calculated point, circuit served and source system
Quantity and unit Power, cumulative energy, interval energy, temperature or another stated quantity
Time Source timestamp, arrival timestamp, time zone and interval boundary
Freshness Expected reporting interval and the age at which data becomes stale
Quality Missing, estimated, substituted, reset, out-of-range and communications states
Corrections How late data, meter exchanges and revised values are versioned and audited

The distinction between source time and arrival time matters when a connection recovers and buffered readings arrive together. The telemetry timing guide explains that boundary. Use the energy monitoring commissioning checklist to turn the contract into site tests.

Compare deployment and integration

Cloud software can simplify portfolio access and shared updates. A local system can retain useful monitoring and automation when the WAN is unavailable. A hybrid architecture can use both: local acquisition and operation at each site, with governed delivery to a portfolio service.

Edge provides local dashboards, data exploration, calculated readings and automation. With the relevant exporter installed and commissioned, it can deliver selected information over a configured MQTTS or HTTPS path. Profile-specific file delivery and the authenticated read API cover other project needs. Gateway connects supported field equipment to that local system. Confirm the current endpoint, authentication method, schema and account setup with each platform provider; instructions for an older EpiSensor Gateway describe a different system.

Ask each supplier to show how it handles intermittent connectivity, duplicates, late readings, meter resets and changing site structures. A connector logo says little about the completeness or operating boundary of an integration.

Build a shortlist scorecard

Score evidence against your requirements. Weight the rows before demonstrations so an attractive dashboard does not displace a critical operational need.

Swipe to see every column

Requirement Evidence to request Acceptance test
Meter and asset onboarding Supported equipment, import process and naming controls Add a representative site without hidden manual remapping
Data quality Quality states, freshness rules and correction history Interrupt one feed and identify stale, recovered and corrected data
Analysis Baselines, comparisons and calculation definitions Reproduce an agreed result from exported source values
Alerts and workflow Routing, acknowledgement, escalation and task history Trigger a known condition and trace it to closure
Reporting Definitions, schedules, exports and recipient controls Produce the required report with units and period clearly stated
Integration Current interface specification and ownership boundary Exchange a representative payload in both normal and failure cases
Security and access Roles, audit records, authentication and support access Prove least-privilege access and review an administrative change
Control authority Approvals, limits, fallback and manual override Demonstrate a safe permitted action and a rejected unsafe request
Portability and exit Bulk export, identifiers, retention and deletion process Export usable data and configuration without supplier assistance

Record pass, partial, fail or not tested. Keep supplier statements separate from evidence observed during the demonstration.

Validate one meter before the whole estate

Choose a representative meter with a known register and compare source and destination values over the same period. Check units, sign convention, multipliers, interval boundaries and whether energy is cumulative or measured over an interval. Investigate every material difference before increasing the meter count.

Test an interruption and recovery. Confirm whether readings are buffered, how late data is labelled, whether duplicates are rejected and how the team learns that delivery failed. Repeat the test with a meter reset or replacement if the project will rely on long-running totals.

Run a structured demonstration

Give shortlisted suppliers the same script and sample data. Include a normal day, a missing interval, a delayed batch, a meter exchange and a value outside its expected range. Ask the supplier to:

  1. onboard the site and preserve your identifiers;
  2. diagnose the data-quality cases;
  3. build one decision-ready view without prepared assets;
  4. route an alert to the responsible person and show the audit trail;
  5. export the underlying readings and definitions; and
  6. explain which steps require supplier services or a paid module.

Run the final script in a limited pilot using your own measurements. A polished sales environment is not an acceptance test.

Separate monitoring from control authority

Monitoring compatibility does not automatically establish a safe control path. For any write or dispatch function, identify the authorised command, equipment and operating state; who approves it; permitted limits and ramp rates; timeout and fallback behaviour; manual override; and the evidence retained after execution.

Keep recommendations, operator approvals and automatic commands distinct. Involve the responsible controls, electrical and operational engineers before enabling writes to plant.

Plan security, ownership and exit

Agree who owns site configuration, platform accounts, device credentials, point mappings, calculated definitions and alert rules. Use named roles, least privilege, multi-factor authentication where available and auditable support access. Set a review process for dormant accounts and supplier access.

Specify retention, backups, regional hosting requirements and incident notification. Confirm that usable raw readings, identifiers, units, quality states and calculation definitions can be exported. Define how credentials are rotated and data is returned or deleted at contract end.

Turn the shortlist into a project brief

Use the energy monitoring project worksheet to record scope, measurements, decisions, owners and acceptance evidence. If the requirement is primarily analytics and management reporting, compare the separate reporting and BI tools.

The directory profiles below are a research starting point. Verify current product capabilities, commercial terms, regional support and interfaces directly with the supplier before selection.

Need an evidence-based software shortlist? Tell us about the estate, existing meters and decisions the system must support. We can help define the measurement and integration brief.

Browse by category

Buyer guides