Using Edge with energy-management software

Edge can be the site's own monitoring and automation system. If your team already uses another energy platform, connect the measurements it needs without losing the local tools.

Decide which work happens locally

Edge includes dashboards, data exploration, calculated readings and local automation. You do not need another platform just to see consumption, compare circuits or configure local rules.

An external energy-management system may still be useful for an established portfolio, accounting or reporting workflow. Start with the decisions people need to make and the tools they already use, then identify the data that must pass between them.

See energy management with EpiSensor for the broader site approach and customer projects.

Map the measurements before the export

List the mains and submeters, their locations, identifiers and units. Establish whether each exported energy value is a cumulative total or consumption over an interval. A receiving system must not treat those as interchangeable.

Agree reporting intervals, timestamps, time zones and how to handle missing readings, meter resets and replacements. Retain the relationship between each platform point and its physical meter so operators can investigate an unexpected value.

Review the hardware range for new measurements and the Gateway for the site connection. Existing supported equipment can also contribute data; a new software connection does not automatically require replacing every meter.

Confirm the current integration

Edge supports pre-built and partner-built flows. Choose the receiving service, authentication, transport and format together. Protocol support alone does not mean its data model or account configuration is ready.

Our directory profiles describe previously documented EpiSensor integrations with EnergyCAP SmartAnalytics, MRI eSight and Spacewell Energy, formerly Dexma. Each profile distinguishes legacy Gateway instructions from the checks needed for a new Edge deployment. Do not copy old endpoint or menu instructions without confirming them.

Validate one meter before the whole estate

Send a representative sample and compare source and destination values over the same period. Check units, interval boundaries and the handling of cumulative readings. Investigate any difference before increasing the meter count.

Test an interruption and recovery using the configured flow. Agree how the team will notice delivery failures and who owns the source settings, credentials and receiving mapping.

Keep operational and reporting views connected

Use the local Edge view to understand the equipment and investigate anomalies; use the external platform where it adds value to the team's wider workflow. Keep point names and calculation definitions consistent enough to relate one view to the other.

For further analysis, see the reporting and BI guide. To scope a new connection, tell us which EMS and measurements you need.