Readings have stopped arriving
Find the site on the map, check its collection status and the date of the latest reading. After addressing the cause, check for new records.
Result: know which site and data source need checking.A platform for distributed utility networks
Readings, network status, and consumption history in one place. EnergyPortal helps you spot data gaps, understand changes, and prepare reports.
From a single building to a citywide or regional network.
EnergyPortal already works with tens of thousands of meters across major companies. With this much data, teams need both the full picture and a clear view of where readings have stopped arriving.
Statuses show which meters have reported and where readings are missing for a given period.
A problem site stands out in the network overview, without searching through spreadsheets.
After addressing the cause, the team checks for new records and the availability of data for the missing period.
Water, heat, electricity, and other resources come together in one system. Explore a heat meter as an example: review hourly, daily, and monthly records and find missing readings.
HT-204 Heat
Accumulated heat
| Period | Q, Gcal | V, m³ | T1, °C | T2, °C | ΔT, °C | Status |
|---|
Heat, water, electricity, gas and cooling are examples of resources that can be brought into the portal. Available readings and analysis depend on the meter type and connection.
EnergyPortal for every resource
Other meters and sensors, subject to compatibility checks.
Three workflows: locate a collection issue, investigate a change in readings and prepare a report.
Find the site on the map, check its collection status and the date of the latest reading. After addressing the cause, check for new records.
Result: know which site and data source need checking.Set a change threshold for a selected reading, as a percentage or an absolute value. A notification flags the deviation; use the history to investigate.
Result: a prompt to investigate, based on your rules.Select the period and report template. For recurring delivery, configure automatic sending by email or FTP.
Result: less manual compilation and repetitive sending.Assign staff to the organisations and buildings they work with. Residents receive access to their assigned premises and meters.
One network, with different roles and access scopes.Add EnergyPortal to your device’s home screen and open it like a regular app. Keep readings, site statuses, and notifications close at hand.
Launch the portal from your home screen icon, without searching for a browser tab.
Review readings, consumption history, and site statuses from your device.
Push notifications help you quickly spot events that need attention. Enable them on a device that supports this feature.
Share your meter models and available data transmission methods. We will assess the connection options and whether additional equipment is needed.
LoRaWAN meters and sensors send readings by radio through a gateway. The data then reaches EnergyPortal alongside other sources.
Takes a reading and sends a radio signal.
Receives messages from devices.
The network server processes data transmission.
Readings are available for monitoring and analysis.
Access and workflows depend on the role: the network team, utility provider, and resident each get what they need.
Monitor collection, find problem sites, analyze consumption, and prepare reports for the next steps.
Network overview → team prioritiesCollected readings and ready-made forms make regular data exchange with water, heat, and other utility organizations easier.
Verified data → report or integrationIn a personal account, customers can see their readings and consumption history in a clear format.
Transparent readings → greater trustConnections are planned around your devices, infrastructure, and goals, step by step.
Gather the list of sites, meter models and connection details. Agree on the required readings and reports.
Check compatibility and choose a collection method, including any additional equipment needed.
Configure transmission and check the first records: meter identity, date, units and data completeness.
Assign access and configure reports and notifications. Agree on responsible contacts and the support process after launch.