Häufig gestellte Fragen
What does GPKE stand for in the energy industry and why does it matter for the ERP?
GPKE stands for "Geschäftsprozesse zur Kundenbelieferung mit Elektrizität" (business processes for supplying customers with electricity) and is a ruling by the German Federal Network Agency (Bundesnetzagentur) that bindingly regulates supplier switching, registrations and deregistrations as well as master data maintenance between market participants. For gas, GeLi Gas applies analogously, for metering the WiM (switching processes in metering) and for balancing in electricity the MaBiS. An ERP for utilities must handle these processes in an automated and deadline-compliant way via standardised EDIFACT messages such as UTILMD, MSCONS and INVOIC, since errors here directly lead to switching disruptions and balancing discrepancies.
Which ERP vendors are suitable for smaller municipal utilities?
Smaller and mid-sized municipal utilities frequently rely on industry solutions such as Wilken (ENER:GY), Schleupen (CS platform), Somentec or kVASy from SIV.AG, since these offer a complete energy-industry feature profile at licence and implementation costs geared to the mid-market and deliver industry updates for regulatory changes. These solutions are often operated from the vendor's data centre to relieve in-house IT and ensure the operational capability required for market communication and billing. SAP S/4HANA Utilities, by contrast, is mainly found at large municipal utilities and groups. Besides functional depth, the key selection criteria are the regulatory and update commitment and the availability of implementation partners.
How does the smart meter rollout affect the ERP?
With the rollout of intelligent metering systems accelerated by the GNDEW, data volumes and frequency increase considerably, as the ERP or the connected energy data management system must reliably receive, validate, substitute and provide quarter-hourly load profiles for billing, balancing and value-added services. A high-performance time-series database and automated plausibility checks are mandatory for this. Mandatory installations apply, among others, to consumers with an annual consumption of 6,000 kWh or more and to power generation plants such as PV from 7 kW of installed capacity, while the legislator wants to see at least 95 percent of mandatory cases equipped by the end of 2030. Since electricity suppliers have been required to offer dynamic tariffs since 2025 and the control of controllable consumption devices under Section 14a EnWG is added, the ERP also needs new billing-side logic for time-variable prices.
Which regulatory format changes does an energy ERP currently have to keep up with?
Market communication is subject to regular format releases by the Federal Network Agency, which utilities must roll out in their systems on fixed cut-off dates, so the ERP must provide the corresponding industry updates on schedule. Since 6 June 2025, the 24-hour supplier switch under Section 20a EnWG has also applied, requiring faster, pre-established processes between supplier, grid operator and metering point operator as well as consistent use of the MaLo-ID. AS4 has been mandatory as the transport channel since April 2024, while market communication is increasingly complementing and replacing file-based EDIFACT exchange with API-based web services, for example in the API process for MaLo-ID determination that has been mandatory since June 2025. A future-proof ERP should support these transitions without utilities having to rely on costly in-house developments each time.
What does the end of maintenance for SAP IS-U mean for municipal utilities?
SAP IS-U, as the predecessor of SAP S/4HANA Utilities, was the standard for the energy industry for years, but is being phased out of vendor maintenance, so support for market communication in IS-U will also end in the medium term. Regular maintenance for SAP IS-U is scheduled to end at the close of 2027, with paid extended maintenance available until the end of 2030, so affected utilities face a migration to SAP S/4HANA Utilities or a switch to an alternative industry solution. Such projects are demanding because data sets that have grown over years must be cleansed and the processes of the market roles supplier, grid operator and metering point operator must be transferred cleanly into the new architecture. Given long lead times and scarce consultant capacity, it is advisable to define migration planning and time windows early.
How long does implementing an ERP for utilities take and what does it cost?
Implementing an energy-industry ERP is generally a project running several months to several years, whose duration and cost depend heavily on company size, the number of market roles, data migration and the desired customising. Success-critical factors are a clean data migration from legacy systems, thorough testing of market communication, parallel operation of the old and new systems during the transition, and training of the clerical staff. Many municipal utilities choose hosting-based models or business process outsourcing of billing to relieve internal IT and make release changes more predictable. Reliable budgets only emerge from a concrete requirements and functional specification, since blanket price quotes rarely reflect the real effort.