Consumption per site and installation Normalising and comparing Reporting obligations, EED and ISO 50001

Custom energy management software development

Energy management software maps your consumption per site, installation or process, flags deviations and supports your reporting. The hard part is not the charts. It is correcting for conditions, handling meters that each speak their own format, and deciding who gets to see a deviation and who is allowed to act on it. Appfront builds that layer to your requirements.

What energy management software does and does not do

Energy management software collects readings from meters, installations and systems, puts them on a single timeline, corrects for the conditions under which they were recorded, and so makes three things possible: seeing where consumption goes, being alerted to deviations, and accounting afterwards for what happened.

An important distinction: this software does not control your installations. Setpoints, switching times and the control strategy stay with your building management system or process control. Energy management software determines when something needs to happen and records that it did. If you mainly want to look ahead, for example peak forecasting, a predictive analytics dashboard is a better fit. If your question is about production control where energy is just one signal, look at software for the manufacturing industry.

If the core of your question is the management system as a process, with procedures, internal audits and demonstrability to an auditor, then you need a custom quality management system. This software only covers the measurement side.

Readings on one clock

Meters, building management system and machines deliver data at their own intervals and in their own units. The system brings them together and distinguishes between zero consumption and no reading.

Measurement points with an owner

A measurement point is only useful if it can be traced to an installation, room or line, with someone responsible for it.

Reports that are reproducible

A report on last year should give the same result next year, even after meters have been added. That requires version control on both measurement data and calculation rules.

A measurement saves nothing until someone acts on it

Energy dashboards rarely fail because of technology, but because the organisation gets the insight and nothing happens. A production hall that is idle on Saturday still draws a substantial base load at night. On Monday that shows up as a clear bump in the weekly overview. If nobody has that overview as a task, it only gets noticed in the quarterly report, and it is no longer possible to trace which installation was running.

So the useful question isn't whether you can see it, but whether it reaches the right person. Three things have to hold. A signal is tied to a measurement point that can be traced back to a specific installation. It lands with someone who is authorised to have that installation switched off or inspected. And a trail remains: seen, action taken, and in the following week's measurement, effect or no effect. That feedback loop is the difference between a system that learns and a list of closed alerts.

The failure pattern we encounter most often is called alert fatigue. If a threshold is set at an absolute number of kilowatt-hours, it fires in every busy week and every cold spell. Within a month the first recipient turns the alerts off and the system goes quiet, even though technically it is still running. A threshold therefore has to compare against what was to be expected.

For commercial buildings above the capacity threshold, since the end of 2025 this is no longer a choice but an obligation under the Besluit bouwwerken leefomgeving (Dutch Building Decree). What exactly that requirement asks for and how you demonstrate compliance is covered under software for the BACS obligation.

The two problems where the real work lies

Normalising, otherwise you compare apples with oranges

A cold February explains higher gas consumption. An extra shift explains a higher peak. If you don't strip those conditions out of the figures, sooner or later you'll claim a saving that was really just the weather. For buildings you usually correct for outdoor temperature, using degree days as the denominator. For production you need a denominator that reflects how busy operations are: running hours, units produced or tonnes processed. That is usually the hardest part of the build, because that denominator lives in your ERP or MES, not in the metering chain.

The same applies when comparing sites. A ranking only makes sense if the metering boundaries are the same. If site A measures cooling on the main meter while site B has a sub-meter for it, you are measuring an administrative difference and calling it performance.

The data sources are messier than expected

Small-scale connections report via the smart meter, which according to Netbeheer Nederland has been mandatory under the Energiewet (Dutch Energy Act) since 1 January 2026 for households and small business connections. Large-scale consumption runs via a metering company, with its own delivery format and frequency. Sub-meters often speak Modbus or M-Bus, a building management system more likely BACnet, machines sometimes OPC UA and sometimes a barely documented manufacturer protocol. Inverters have their own API.

Missing measurements are the rule, not the exception: a gateway hangs, a meter is replaced, a network segment goes down. The most important design decision in the data layer is simple to write down and rarely executed well: a gap must never end up as zero in the total. Two other classics are double counting and the switch to winter time, which in quarter-hour values produces an hour that occurs twice.

Where these systems pay for themselves

These are the four situations we encounter most often, each placing different demands on the data layer.

Property owners

Offices, healthcare property or retail premises where consumption is compared per building and allocated to tenants. The question is rarely about more data, but about an allocation key that holds up.

Manufacturers

Where energy is a cost per product, not per month. Allocating it to a line or order requires an integration with the production administration, which off-the-shelf packages rarely offer out of the box.

Organisations with many sites

Branches, schools, pumping stations or care locations that are compared with one another. Without equal metering boundaries and a consistent denominator per location, you lose the argument with the site manager.

On-site generation and grid load

Solar panels, a battery or a heat pump make metering more complicated: feed-in, self-consumption and grid load all intermingle. Steering on peak demand requires visibility behind the meter.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

What the rules require of your data

Many sites are subject to the energy-saving obligation, which includes a duty to provide information: every four years you report which measures have been implemented, based on the Recognised Measures Lists of measures that pay for themselves within five years or less. That report goes through RVO and is assessed by the regional environmental agency on behalf of the competent authority. The next deadline RVO mentions is 1 December 2027.

High-consumption sites in certain sectors also have an investigation obligation. That report requires, among other things, a schematic overview of the site, a description of installations and processes, an analysis of energy use including monitoring, a basic check on energy management and an implementation plan. That is almost literally what a well-set-up system produces as a by-product.

Large companies that are not SMEs fall under the EED energy audit, likewise every four years via RVO. That report requires, among other things, consumption in gigajoules, a load profile for electricity and a breakdown by processes, buildings, installations and transport; submitting late can result in a penalty payment order. Organisations that apply a certified energy management system do not need to submit a separate audit report: RVO names ISO 50001, or ISO 14001 combined with ISO 14051.

The criteria are shifting from company size to actual energy use. Check with RVO which variant applies to you before you set anything up: it determines the breakdown you will need later. Software does not deliver compliance, only evidence.

  • Breakdown by processes, buildings, installations and transport
  • Load profile for electricity from quarter-hourly or hourly readings
  • Measures implemented, recorded with date, measuring point and effect
  • A documented baseline with traceable indicators
  • Reports that give the same result a year later

When you are better off not building this

Mature energy monitoring platforms exist, often from the supplier of your metering equipment or from your energy supplier. For buildings with standard meters and a common reporting format, they are almost always the better choice: faster to get running, lighter to maintain, and the supplier looks after the integrations. If that sounds like you, buy a package. We would rather tell you that upfront than halfway through an implementation.

Custom software pays for itself in three situations. The first: energy data can only be interpreted together with your own production or occupancy data from your ERP, MES or booking system. The second: the reporting format you need does not exist in the package, for example an allocation key for tenants or a breakdown by cost centre that only you use. The third: the platform is tied to the metering equipment of a single supplier and you want to be able to switch without losing your historical series.

Factor in one burden you do not have with a package: the integrations become yours. If a metering company changes its delivery format, maintaining that becomes your job. That is why the middle route is often the wisest: keep standard monitoring where it is enough and build only the layer on top that adds your own data.

Frequently asked questions

No. Measuring provides insight, not savings. Savings only happen when a deviation reaches someone who knows which installation is involved and has the authority to act on it. Who receives a signal and what is recorded afterwards is just as decisive as the measurement data itself.

Often you should. For buildings with standard meters and a common reporting format, such a platform is faster to get running and lighter to maintain. Custom software only becomes interesting when you want to combine energy data with your own production or occupancy data, or need a report format the package does not support.

That depends on agreements made up front, not on good intentions afterwards. Specify who owns the measurement data, which format it can be exported in and whether the derived series come with it: corrections, normalisations and the calculation rules behind them. Raw meter readings without that context are worth only half as much.

No. Certification is about your organisation, your procedures and the way you implement improvements; software can at best provide the evidence. What a system can do is reduce the administrative burden: a documented baseline, traceable indicators and reports you can run again later with the same outcome.

That depends on your consumption and size. For many sites the energy-saving obligation applies, with a reporting duty every four years; high-consumption sites in certain sectors also have an obligation to carry out an energy audit. Large enterprises that are not SMEs fall under the EED energy audit. RVO (the Netherlands Enterprise Agency) describes which variant applies to you.

You should make arrangements about this up front. Agree who owns the code and the data, where the source code is hosted and what documentation comes with delivery: integrations, calculation rules and the setup of the environment. A system that another team can read and run is the only firm guarantee.

Related services

Predictive analytics dashboard

For forward-looking questions: consumption forecasts, peak prediction and model-based anomaly detection instead of fixed thresholds.

Software for the manufacturing industry

When production control is the core and energy is one of the signals: orders, machine status and consumption in the same view.

Custom quality management system

For the management system as a process: procedures, internal audits, corrective actions and demonstrability to an auditor.

For managers of multiple buildings with different building management systems, there is our building automation monitoring dashboard.

If you need to report the energy-saving information obligation for many locations, there is our portal tool for the energy-saving information obligation.

Discuss your metering situation with us

Tell us which meters and systems you have, which reporting you need to deliver and where you are currently getting stuck. We first look at whether an existing platform is enough, and only then at what needs to be built custom alongside it.

Edit content