Charge Point Operator


Technologies:

Java, Spring Boot, Hibernate, MariaDB, MongoDB, Docker, Kubernetes

Date:

09.2018 - 10.2020

Unlocking Charge Point Operator’s business processes with Open Standards

Backend platform development and maintenance modeling the Charge Point Operator’s business processes. A 2-year journey including OCPI and OICP by Hubject integration. Multi-level product development to become more user-friendly and boost market penetration. Java, Spring Boot, and Kubernetes at its finest to achieve business flexibility.

Challenges

Our e-mobility partner was looking for highly-skilled developers, that could nourish the existing team and support further large-scale development on the market. They were looking for an associate who would effectively help them maintain and develop the backend platform responsible for Charge Point Operator's business process modeling.

Our partner’s integration was based on custom-made APIs exposed specifically to the partners they were integrating with. APIs were limited in scope and exposed mainly static data. This quickly became the main challenge, because linking with a new partner was time-consuming, taking several months to connect. In the long run, this would quickly become inefficient or unmaintainable.

Solutions

As a team partner, to gain a full picture of the processes taking a place in the e-mobility market we conducted two workshops. One took place at the partner’s headquarters, the other one was conducted at our office. Based on the given insightful findings, we started planning the workflow. The beginning of this partnership was launched with two developers involved in the project expansion.

We searched for the most efficient solution to achieve full e-roaming flow, giving end-users the most convenient experience. At that moment we decided to implement Open Standards. To confirm our predictions on how to apply Open Standards and how to deal with potential obstacles, we began with a simple use-case.

Having proved that the standard matches our partner needs we started to add successive modules to enrich the API and expose new functionalities. The final stage of this long, carefully evaluated process was full e-roaming functionality, which boosted the integration process by up to 95%. The time required for integration with a new partner at the moment takes a few days, compared to the time needed for integration without these Open Standards took up to 4 months.

Apart from applying open standards (OCPI and OICP) we were also responsible for establishing a charge point management platform itself, a system integrating with the British electricity market, development and maintenance of custom APIs, as well as an API for a functioning portal.

As this ambitious partnership was growing, we nourished the team, at key moments of progress, with 7 extra developers. Two of them were assigned to build a dedicated 2-months lasting project. Eventually, this 2-year partnership was crowned with a knowledge-sharing space for future development, valuable experience, and excellent performance.

Outcomes

  • Open, secure, widely applied, accessible charging network
  • 95% faster integration with new partners
  • 2 Open Standards implemented (OICP & OCPI)
  • 1 place to monitor, maintain and secure the system