SAP S/4HANA Utilities as an Opportunity for Transformation
What Factors Influence the Schedule, Project Risks, and a Successful Launch
The SAP S/4HANA Utilities Implementation Project as an Opportunity for the Transformation of SAP Environments in the Energy Industry
End of Support: Mainstream support for SAP IS-U ends on December 31, 2027—optional, fee-based Extended Maintenance is currently scheduled to continue through the end of 2030.
More than just an upgrade: The transition to SAP S/4HANA Utilities affects billing, market communication, and customer service.
A realistic timeline: It begins with an assessment of in-house developments, interfaces, and data quality.
Standardization: Fewer deviations from the standard create room for business-relevant specifics.
Platform Approach: AEP.EnerS4 from Arvato Systems offers a modular cloud master system based on SAP S/4HANA Utilities.
SAP IS-U as the Backbone of Core Business Processes
For many municipal utilities, SAP IS-U is the backbone of their core business processes. With regular maintenance set to end on December 31, 2027, the question of how billing, customer service, and market communications should be structured in the future is becoming more pressing. However, the answer to this question should not be determined solely by the impending end of maintenance support. What matters most is a transition that fits the company’s specific needs—and is sustainable in the long term.
The end of support highlights the need for action. At the same time, it’s a good opportunity to review your own SAP landscape:
How much time is actually left for planning, implementation, testing, and the go-live?
Is there enough space, and is there sufficient capacity to meet individual needs?
Which processes are truly unique?
Where have deviations from the standard accumulated over the years?
Which of these variations still provide technical value today?
Is a standard approach sufficient, or is a customized project needed?
What ends on December 31, 2027?
SAP will discontinue mainstream maintenance for the affected SAP Business Suite 7 core applications at the end of 2027. As things stand, SAP will offer optional—and, of course, fee-based—Extended Maintenance for a transitional period through the end of 2030. Whether this option is even available for a specific SAP system landscape and makes economic sense must be evaluated based on the products in use, release versions, and contract terms. How data format adjustments should be handled during this period must also be clarified separately. Extended Maintenance can provide additional time, but it does not replace the decision regarding the future target architecture.
For energy providers, this means that the transition to SAP S/4HANA Utilities is not merely a technical upgrade. Billing, market communication, meter master data, customer service, interfaces, and collaboration with other departments must all be considered together. Data quality, legacy systems, and custom processes also influence how complex a project becomes.
Time pressure is real—but it’s not a good foundation for a robust project plan
Without the necessary groundwork, an implementation project of this scale will no longer be possible by the end of mainstream support. Companies that have yet to make the switch to SAP S/4HANA Utilities are therefore already planning for a go-live in 2028. But even this plan is often ambitious. In addition to the starting point and the project kickoff, the planned transformation approach is, of course, crucial for establishing a realistic timeline.
The key requirements for an ambitious yet reliable project plan include:
a shared understanding of the future SAP S/4HANA Utilities landscape,
a robust professional and technical vision,
A structured analysis phase—for example, using SAP Activate—transparency regarding in-house developments and interfaces, an early assessment of data quality, and sufficient capacity in IT and business units.
Added to this are the size and complexity of today's IT system landscape, as well as the question of which processes should be adopted, modified, or completely redesigned.
Reliable planning, therefore, does not begin with a blanket go-live date. It begins with an honest assessment of the current situation. This leads to a project plan that takes dependencies into account and highlights decisions before they jeopardize the schedule.
Standardization creates room for what really matters
A common concern is: Does a standardized approach leave enough flexibility for specific supplier processes, network-specific requirements, or existing customized workflows? The answer is yes—provided that specific requirements are reviewed early on and deliberately designed.
It is worth distinguishing between a necessary customization and a historical deviation. Not every customization continues to provide a competitive advantage in the industry. Where processes align more closely with the SAP standard, the effort required for maintenance and further development often decreases. This also creates better conditions for leveraging future innovations.
Standardization does not, therefore, mean that all municipal utilities need identical processes. Rather, the goal is to specifically address business-relevant nuances while keeping the core system as stable as possible.
A master system as a platform approach
With AEP.EnerS4, Arvato Systems offers a cloud-based billing platform based on an SAP S/4HANA Utilities master system. Key energy management functions are bundled into a modular, preconfigured master system template. Supplementary services and extensions make it possible to accommodate individual requirements outside the core platform.
The platform approach is based on collaborative development: Relevant technical and regulatory adjustments are developed centrally and can benefit users of the master system. This can reduce maintenance efforts and enable a faster rollout. At the same time, there is still flexibility to adapt the solution to the specific requirements of each utility provider. SAP describes AEP.EnerS4 as a cloud-based next-generation billing solution with a standardized, modular approach. SAP News
For energy providers, this can result in the following benefits in particular:
less effort required for individual training and professional development
Consolidated implementation of regulatory requirements
greater reusability of standardized processes
better conditions for automated testing and releases
Faster deployment of new features
more flexibility for business-specific requirements
Which market role should be transitioned first?
Supplier or integrated transmission system operator (TSO)/distribution system operator (DSO)? Parallel or sequential project implementation? Many energy utilities with different market roles are faced with the question of prioritization. Despite the lessons learned from numerous transformation projects, it is clear that there is no single blueprint for the correct sequence. The factors involved in this decision are too diverse to allow for a recommendation from an outside perspective.
The risk associated with a custom project persists even after go-live
A customized project may initially seem like a perfect fit. However, the more a solution deviates from the standard, the more responsibility utility companies often bear themselves for maintenance, testing, and future adjustments. In addition, consulting resources for such projects are limited. A platform-based approach can accelerate the initial implementation and involve users in joint further development over the long term.
Arvato Systems is preparing for the further development of AEP.EnerS4 even before the first customer projects begin and has experience from SAP S/4HANA Utilities projects. Capacity for future projects has also already been planned.
Set the Course Now
The end of support is a specific date. The transformation behind it is a strategic decision. By reviewing in-house developments, interfaces, and data quality early on, you can lay a better foundation for a realistic timeline. At the same time, the transition offers an opportunity to reduce complexity that has built up over time and to modernize the system landscape in a targeted manner.
Good to know: Until go-live, Arvato Systems provides comprehensive support for format changes and ongoing support for the legacy system in parallel with the transformation project.
The key question, therefore, is not only: How can we ensure the go-live happens on time? But also: What system and process landscape should our municipal utility rely on afterward? A standardized yet expandable platform can be the answer—provided it aligns with the company’s business requirements, operating model, and pace of change.
Written by