Häufig gestellte Fragen
Is a conventional ERP sufficient for municipal utilities?
In most cases, an industry-neutral standard ERP is not sufficient for a municipal utility, because energy-market processes such as GPKE, MaBiS, GeLi Gas and WiM, including EDIFACT market communication (UTILMD, MSCONS, INVOIC), must be deeply integrated. Added to this is the multi-division logic spanning electricity, gas, water, wastewater and district heating, which conventional merchandise management or finance systems do not cover. The norm is therefore industry-specific energy-sector and billing systems, which are sometimes combined with an ERP core or operated as an integrated platform. The exact setup depends heavily on the number of divisions, the customer base and the historically grown IT landscape of the individual utility.
What does implementing a municipal utility ERP cost?
Costs vary considerably with size, number of divisions and customising depth, and cannot be quantified as a flat rate. For mid-sized municipal utilities, complete projects typically fall in the range of several hundred thousand to a few million euros, while large utilities can invest considerably higher double-digit million amounts over multi-year programmes. With on-premise licence models, annual maintenance and update fees come on top, which are customarily around 18 to 22 percent of the licence sum; cloud/SaaS models instead charge ongoing subscription fees. The main cost drivers are data migration from legacy systems, interfaces for market communication, plus training and process adaptation, which is why a reliable calculation always requires an individual needs analysis.
Which vendors are relevant in the municipal utility segment?
Among larger utilities, SAP with IS-U and its successor S/4HANA Utilities is considered the widespread market leader. In the municipal mid-market, industry specialists dominate, including Wilken (ENER:GY), the SIV Group with kVASy, Schleupen and Somentec, as well as cloud-native solutions such as powercloud. These specialised vendors offer a complete energy-sector functional profile with regulatory updates at comparatively mid-market-oriented terms. Which solution fits depends on company size, division mix, cross-divisional structures and the existing system landscape, which is why a structured requirements and vendor comparison is recommended before selection.
What does the 24-hour supplier switch mean for the ERP?
Under ruling BK6-22-024 of the Bundesnetzagentur, the technical supplier switch for electricity must be possible within 24 hours and on any working day; binding implementation took effect on 6 June 2025. For municipal utilities, this means that registration and deregistration processes and the associated market communication must run highly automated and almost in real time, largely ruling out manual post-processing. Retroactive registrations and deregistrations have as a rule not been permitted since that cut-off date, as the switching processes were converted to an exclusively forward-looking model. A municipal utility ERP must therefore map the accelerated switching processes on schedule and in automated form within its market communication workflows.
Which obligations does NIS-2 bring for municipal utilities with regard to ERP?
The German NIS2 implementation act (NIS2UmsuCG) has been in force since 6 December 2025 and considerably expands the circle of supervised companies; many smaller and mid-sized municipal utilities also fall under the supervision of the BSI as energy suppliers. Affected companies had to register and must report significant security incidents in stages: an initial report or early warning within 24 hours, a more detailed report within 72 hours and a final report after one month. Also required are risk management measures such as backup concepts, supply chain security and multi-factor authentication, which places direct demands on ERP operations, access management and interfaces. Violations carry substantial fines, which is why cybersecurity is becoming a fixed selection and operating criterion for municipal utility software.
How must the ERP support the smart meter rollout?
The statutory rollout of intelligent metering systems under the amended Metering Point Operation Act (Messstellenbetriebsgesetz) and the GNDEW sets binding quotas: at least 20 percent of mandatory installation cases by the end of 2025, around 50 percent by the end of 2028 and roughly 95 percent by the end of 2030. For municipal utilities, this means a growing stream of metering and load profile data that must flow reliably into billing and energy data management via the interface to the metering point operator. The ERP should therefore be able to process RLM and SLP data, active and reactive energy, and load profiles automatically and link them with the market processes. Scalable data storage and a clean MSB connection are thus central selection criteria for the coming rollout years.