Utility software development for what the billing system cannot do.
Utility software development for energy suppliers and municipal utilities: tenant electricity, PV leasing and charging land in spreadsheets the core system does not know. We turn those into web applications and apps connected to SAP.
No invented references
In this sector we have no publicly nameable client reference. What you read here describes what we build.
In front of the core
A change inside SAP is paid for again at every upgrade. An application in front of it is not.
Built for the basement
At a meter you need three fields and a camera. Office software with twenty mandatory fields goes unused.
Utility software development: what we build.
-
Digitalization starts in front of the core system
Master data, billing and posting stay where they are. Our application captures, calculates the special case and hands the result over via OData or REST.
More on this
A change in the core has to be carried forward and tested at every upgrade. A front layer can be switched off once your system covers the case, and IT security approves it more readily. If the ERP extension is the better answer, we say so: ERP project management.
-
Solar billing software without a spreadsheet
Properties, meters, allocation keys, tenant changes and residual supply in a web application that hands the result to SAP.
More on this
We start by analysing your spreadsheet, which usually holds more domain knowledge than any specification. The route out of it: Excel and VBA modernization.
-
PV assets, contracting and charge points
Assets, contracts, terms, yields and maintenance dates in one overview, with deadlines that announce themselves.
More on this
Today those sit in a folder, a spreadsheet and the memory of individual people. Charge points, access rights and fault reports grow the same way, faster than anyone planned a system for.
-
Utilities customer portal and a field app
Consumption history, instalments and invoices for customers to check themselves. For the field, an app for meter exchanges, commissioning and faults, offline and syncing on its own.
More on this
Every self-service lookup is one call fewer. We build the app for iOS and Android from one codebase with Flutter, the portal as custom software.
How many such calls arrive daily?
Meter readings, fault status, instalment questions: describe your most frequent cases. We say which can be handled digitally.
Common questions from the energy industry.
Can you integrate with our SAP?
Yes, one of our most common cases. The application sits in front of the core system and hands over through its interfaces, with SAP via OData or REST. Your system stays in charge.
Do you build a billing system?
No. A complete energy billing system carries decades of regulatory history, so we do not rebuild it. We build the applications beside it: for models your system does not cover, for field capture, and for portals.
We bill tenant electricity in Excel today. Is that a case for you?
A classic one. Allocation keys, meter cascades, tenants moving mid-period and residual supply tip every spreadsheet over eventually. Because money and a billing obligation toward tenants ride on it, traceability counts for more than the time saved.
Does a smart meter app have to work offline?
Practically always. Meters sit in basements, plant rooms and dead spots. Entries and photos are stored locally first, and syncing runs as soon as there is a connection again.
What about data protection for consumption data?
Consumption data allows conclusions about people's habits. We build with data minimization: only the granularity the process needs, hosting in the EU, a data processing agreement. The controller role stays with you.
Do you also work for smaller municipal utilities, and how long does it take?
Yes, and that is often where it pays off most, because the special case hangs on one spreadsheet and one person. The timescale is decided by the domain questions, such as how the allocation key is formed. Those come first.
Further reading.
Which spreadsheet bills real money at your utility?
If a billing model depends on a spreadsheet one person understands, a conversation is worth it. We say whether an application, an integration or a process change is the answer.
New models, old core system.
Describe the model and the system that does not cover it. You get an assessment of whether a lean front layer is enough.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.