PowerUp: Scalable CPO Backend Architecture for Electric Mobility

PowerUp AG, headquartered in Zurich, is an innovative joint venture in the field of public e-mobility solutions. As a software-only CPO (Charge Point Operator), the company operates the public charging infrastructure of Swiss Post and Agrola, with a focus on DC and HPC charging. The goal is to drive the expansion of the charging infrastructure in Switzerland in an agile manner by combining and expanding the resources and branch networks within the joint venture.

At the start of the project, the parent companies were using different backend systems (CPMS) that had evolved over time. However, these separate IT environments were only partially suitable for joint, scalable operations. For the joint venture, it was clear: a standalone, future-proof, and vendor-neutral CPO backend architecture was needed to avoid vendor lock-in. 

PowerUp was looking for a suitable backend solution. Within a very short timeframe of just a few weeks, a robust architectural framework and decision-making basis had to be established. PowerUp wanted to clearly define its role as a CPO without its own eMSP, ensure maximum transparency regarding data and processes, and guarantee highly available loading operations. The management and governing bodies of the participating companies were pleased to be convinced by a concept that is not a copy of existing systems but rather offers a genuine foundation for innovation in the future.

To manage the complexity, doubleSlash focused on clearly defined core capabilities for CPO backend operations.  

Working within a defined timeframe, doubleSlash was able to quickly deliver the right solution through our AI software development process, leveraging its strong technical expertise in e-mobility combined with an artifact-driven, focused approach:

• Capabilities & Use Cases: During workshops, key capabilities were prioritized, use cases were defined, and processes, roles, and business objects were developed and consolidated.
• Architecture Modeling: The system context, container structure, and data flows of the future solution were modeled in detail.
• Architecture Decision Records (ADRs): Key decisions—such as those regarding the demarcation of existing IT landscapes or the design of a minimum viable product (MVP)—were transparently documented.

At the end of the first project phase, an architecture aligned with the business model and the derived requirements was established. It describes the future system landscape based on the defined capabilities, with the CPMS at its core, which is efficiently integrated with the identified and selected peripheral systems:

• Clear Direction: Instead of choosing between existing approaches, we now have a distinct vision for the joint venture.
• Solid Basis for Decision-Making: The structured classification of various CPMS options highlights opportunities and risks. The reference architecture significantly reduces the complexity of coordination.
• Transparent Roadmap Logic: The target architecture, migration principles, and dependencies are clearly laid out, allowing the path forward to be planned step-by-step with confidence.