Custom energy management software development
Energy management software maps your consumption by location, installation or process, flags deviations and supports your reporting. The difficult part is not the charts. It lies in correcting for conditions, in meters that each speak their own format, and in deciding who sees a deviation and who is allowed to act on it. Appfront builds that layer to measure.
What energy management software does and does not do
Energy management software collects readings from meters, installations and systems, places them on a single timeline, corrects for the conditions in which they arose, and thereby 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 schedules and control strategy remain with your building management system or process control. Energy management software determines when something needs to happen and records that it has happened. If your main interest is looking ahead, for example peak forecasting, a predictive analytics dashboard is a better fit. If your question concerns production control in which energy is one signal among many, 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 demonstrable compliance for an auditor, then a custom quality management system is what you need. This software only covers the measurement side.
Measurements on one clock
Meters, the building management system and machines deliver data at their own intervals and in their own units. The system brings them together, distinguishing 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 outcome next year, even after meters have been replaced or added. That requires version control of both the measurement data and the calculation rules.
A reading saves nothing until someone acts on it
Energy dashboards rarely fail on technology. They fail because the organisation gets the insight but nothing happens. A production hall that is idle on Saturday still draws a considerable base load overnight. On Monday that shows up as a clear spike in the weekly overview. If nobody has that overview as a task, it only surfaces in the quarterly report, and by then it is impossible to tell which installation was running.
The useful question, then, is not whether you can see the signal, but whether it reaches the right person. Three things need to hold for that. A signal must be tied to a measurement point that can be traced to a specific installation. It must land with someone authorised to have that installation switched off or inspected. And a trace must remain: seen, action taken, and in the following week's measurements, whether there was any 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 alarm fatigue. If a threshold is set at an absolute number of kilowatt-hours, it goes off in every busy week and every cold spell. Within a month the first recipient switches the notifications off, and the system falls silent while it is technically still running. A threshold should therefore compare against what was expected.
For non-residential buildings above the power threshold, this has been a legal requirement under the Building Activities Decree (Besluit bouwwerken leefomgeving) since the end of 2025, rather than an option. What that requirement specifically asks for and how you demonstrate compliance is covered in software for the BACS requirement.
The two problems where the real work lies
Normalising, or you are comparing apples with pears
A cold February explains higher gas consumption. An extra shift explains a higher peak. If you don't strip those circumstances out of the figures, sooner or later you will claim a saving that was really just the weather. For buildings you typically correct for outdoor temperature, using degree days as the denominator. For production you need a denominator that reflects operational activity: running hours, units produced or tonnes processed. This is usually the hardest part of the build, because that denominator sits in your ERP or MES rather than in the metering chain.
The same applies when comparing sites. A ranking only means something if the metering boundaries are the same. If site A includes 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-consumer connections deliver data via the smart meter, which according to Netbeheer Nederland has been mandatory under the Energy Act since 1 January 2026 for households and small business connections. Large-consumer connections run through a metering company, with its own delivery format and frequency. Sub-meters often speak Modbus or M-Bus, a building management system earlier used BACnet, machines sometimes use OPC UA and sometimes a barely documented manufacturer protocol. Inverters have their own API.
Missing readings are the rule, not the exception: a gateway hangs, a meter gets replaced, a network segment goes down. The most important design decision in the data layer is simple to state and rarely done 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-hourly values produces an hour that occurs twice.
Where these systems earn their keep
We encounter these four situations most often, each with a different requirement of the data layer.
Property owners
Offices, care property or retail premises where consumption is compared per building and charged on to tenants. The question is rarely more data, but an allocation key that holds up.
Manufacturing companies
Where energy is a cost per product rather than per month. Attributing it to a line or order requires an integration with production administration, which packaged software rarely offers out of the box.
Organisations with many sites
Branches, schools, pumping stations or care locations compared with one another. Without equal metering boundaries and an unambiguous denominator per location, you lose the argument with the site manager.
Own generation and grid load
Solar panels, a battery or a heat pump make measurement more complicated: feed-in, self-consumption and grid load run together. Steering on peak demand requires visibility behind the meter.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →What your data rules require
Many sites are subject to the energy-saving obligation, which includes a reporting duty: once every four years you report which measures have been carried out, based on the Recognised Measures Lists of measures that pay back within five years or less. That report is submitted via RVO and assessed by the environmental service on behalf of the competent authority. The next submission deadline RVO has announced is 1 December 2027.
High-consuming 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 exactly what a well-designed system produces as a by-product.
Large enterprises without SME status fall under the EED energy audit, also once every four years with 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 lead to a penalty payment order. If you operate a certified energy management system, you do not need to submit a separate audit report: RVO cites ISO 50001, or ISO 14001 combined with ISO 14051.
The criteria shift from company size to actual energy consumption. Check with RVO which variant applies to you before you set up your system, as that determines the breakdown you will need later. Software does not deliver compliance, only evidence.
- Breakdown by processes, buildings, installations and transport
- Electricity load profile from quarter-hourly or hourly values
- Measures carried out, recorded with date, measuring point and effect
- A documented baseline with traceable indicators
- Reports that reach the same outcome a year later
When you are better off not building custom software
Mature energy monitoring platforms exist, often from your metering equipment supplier or your energy provider. For sites with standard meters and a common reporting format, these are almost always the better choice: quicker to deploy, lighter to manage, and the vendor maintains the integrations. If that describes you, buy a package. We would rather say so upfront than halfway through an implementation.
Custom development pays off in three situations. First: energy data only makes sense when interpreted alongside your own production or occupancy data from your ERP, MES or booking system. Second: the reporting format you need is not available in a package, for example an allocation key for tenants or a grouping by cost centres that only you know. Third: the platform is tied to one supplier's metering equipment and you want to be able to switch without losing your historical series.
Factor in one burden you don't carry with a package: the integrations become yours. If a meter operator changes its data delivery format, that maintenance falls to you. That is why the middle path is often the most sensible: keep standard monitoring where it suffices and build only the layer on top that adds your own data.
Frequently Asked Questions
No. Measuring provides insight, not savings. Savings only arise when a deviation reaches someone who knows which installation is involved and is authorised to act on it. What happens after a signal is received, and what is recorded afterwards, matters as much as the measurement data itself.
Often you should. For buildings with standard meters and a common reporting format, such a platform is quicker to deploy and lighter to manage. Custom development becomes worthwhile only if you want to combine energy data with your own production or occupancy data, or need a reporting format the package does not support.
That depends on agreements made in advance, not good intentions afterwards. Record who owns the measurement data, in what format it can be exported, and whether the derived series come along too: corrections, normalisations and the calculation rules behind them. Raw meter readings without that context are only worth half as much.
No. Certification concerns your organisation, your procedures and the way you implement improvements; software can at most supply the supporting evidence. What a system can do is reduce the administrative burden: a documented baseline, traceable indicators and reports you can rerun later with the same outcome.
That depends on your consumption and size. For many sites the energy-saving obligation applies, with an information duty reported once every four years; high-consuming sites in certain sectors also have an investigation duty. Large enterprises without SME status fall under the EED energy audit. RVO sets out which variant applies to you.
Agree on this upfront. Settle who owns the code and the data, where the source code lives, and which 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 questions that look ahead: 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 on one screen.
Custom quality management system
For the management system as a process: procedures, internal audits, corrective actions and demonstrable compliance for an auditor.
For managers of multiple buildings with different building management systems, there is our building automation monitoring dashboard.
Discuss your metering situation with us
Tell us which meters and systems you have, which reporting you need to deliver and where things are currently getting stuck. We will first check whether an existing platform is sufficient, and only then what custom work is needed.