See the fourth lesson of our comprehensive eMobility training on OICP!

Having a chance to work with well-established startups from the e-mobility sector, Bartek gained invaluable knowledge on the industry requirements. On his path, he was given the opportunity to work on numerous EMSP applications and CPO platforms. Bartek is also our Head of Delivery.

Bartłomiej Łazarczyk

 is happy to introduce you to the Open Standards course led by our e-mobility expert - Bartlomiej. Throughout the following lessons, we will uncover the technicalities and functionalities of the OICP - a protocol developed by 

 - as well as business aspects for e-Mobility Service Providers and Charge Point Operators.

Such a knowledge-pack should serve everyone operating in the e-mobility industry as it unfolds the most crucial aspects of navigating through Open Standards utilization and many more!


Subscribe to our YouTube channel to make sure you don't miss out on the upcoming training entries.

Open InterCharge Protocol Training - Lesson 4

Now, let's focus more on a detailed view of services used in OICP. In this part of the training session, we will cover:

Most of those services have similar flow and logic for both CPO and EMP roles, but in this module we will cover them from CPO perspective. Then we will change perspective to EMP, go through them once again and see the differences. Let's get started.


eRoaming Authorization service. First operation in the eRoaming authorization service is eRoamingAuthorizeStart. This operation is used for authorizing the charging processing Hubject platform. Implementation is mandatory by every CPO partner. In general, this message is used when user authenticates himself at the charging point by i.e. RFID card. Request comes from CPO to Hubject platform and then eventually it goes to EMP. Every request must contain operator ID and type of identification data - as a result you may expect the generated session ID for the charging process.

Authentication process is not so simple, we may have three different scenarios. At first, Hubject will try to authorize the request in offline mode. In other words, it will check its database for the customer token present in request and validate if it can start a charging session. If that's true, it will automatically return a positive response to CPO without any involvement of EMP. Authentication data needed for that can be uploaded by EMP beforehand using eRoaming authentication data service dedicated only for EMPs.

In case when offline authorization is not possible, Hubject will try to communicate with EMP directly. EVcolID present in identification data will be used for identifying involved EMP. If Hubject finds EMP, then it will forward the request to them. Of course, with some conditions given EMP must implement authorization service for online EMP, the response must contain provider ID and also may contain a list of identification data that can be used for stopping a charging session i.e. it can be QR code or RFID card.

If for some reason Hubject cannot identify EMP based on identification data, it will try to authorize the request in another way. At first, it will fetch all the EMPs that are under a contract with CPO. In other words, it will patch all the EMPs that subscribe to CPO authorization service. Then it will forward the request to all of those EMPs and wait for a result. This process is called ‘broadcasting’. After every EMP response to the request, Hubject will check if only one response was positive. If that's true, the charging process can be started and provider ID is known, if not, then this operation cannot be authorized.

Here we have an example of what an eRoamingAuthorizeStart request looks like. CPO partner session ID and EMP partner session ID are optional but can be used for custom session mechanics. EVSE ID is also optional because it can be derived based on identification data. Nonetheless, it's recommended to provide it as well for better debugging. Identification is used for specifying authentication data to authorize the user. Identification types can be RFID, QR code, plug-and-charge and remote. Operator ID is mandatory and it identifies the CPO. Pricing product ID is the name of pricing product for tariff identification. The last one; session ID identifies the process and it also can be optional.

eRoamingAuthorizationStart message is used as a response for eRoamingAuthorizeStart request. This message is very similar to acknowledgement, but has some additional fields. The first one is authorization status which specifies whether the user was authorized to charge or not. The next one is AuthorizeStop identifications which is a list of identification data that can be used for stopping the charging process. The last one; provider ID specified involved EMP.

The next operation to perform in authorized service is eRoamingAuthorizedStop. Basically, authorized stop is almost the same as authorized start but of course it's used for stopping the charging process. Session ID must be provided, because based on that Hubject and derived EMP data use for authorizing the charging process. Also, it will allow Hubject to try to stop the charging process in offline mode.

Request for eRoamingAuthorizeStop is very simple and looks similar to AuthorizeStart. Worth remembering is that EVSE ID is again optional, because it can be derived based on session ID. Nonetheless it's also recommended to provide that for better debugging.

eRoamingAuthorizationStop is a response for eRoamingAuthorizeStop request. This message is very similar to acknowledgement and also almost the same as eRoamingAuthorizationStart message, the only difference between those two is that eRoamingAuthorizationStop message does not include authorization stop identifications field.

eRoamingAuthorizeRemoteStart is another AuthorizeStart operation in authorization service, but this time the request comes from EMP to CPO. It allows EMP customers to directly start a charging process with i.e. mobile application. Implementation is mandatory by CPO, because it must be able to accept and process AuthorizeRemoteStart messages. Requests must contain provider ID and EVSE ID.

Logic for AuthorizeRemoteStart is a little bit different than for AuthorizeStart. At first, Hubject will check if there is a valid contract between CPO and EMP based on provided EVcolID, then it will check if EVSE ID is among the data uploaded by CPO. If that's not true, then the status code 603 on a known EVSE ID will be returned. Also, EVSE with a given ID should be Hubject compatible, otherwise status code 604 will be returned.

If EVSE ID is Hubject compatible or CPO has not uploaded any EVSE records yet, we cannot tell for sure that giving CPO is or isn't the owner of given EVSE. In that case, Hubject will generate a session ID and forward the request to CPO. CPO must return an acknowledgement with information whether he is the owner of EVSE and if the charging process can be started or not.

Based on this example, we can easily tell that the eRoamingAuthorizeRemoteStart request does not differ much from the eRoamingAuthorizeStart request. The only difference between those two is previously mentioned EVSE ID and provider ID.

eRoamingAcknowledgement message is a response for eRoamingAuthorizeRemoteStart request. It is also a response for most of the services we will cover later in this course. Structure is very simple; session ID related fields are the same as we have covered in eRoamingAuthorizeStart and eRoamingAuthorizeStop messages, the only difference is result field, which indicates whether operation was performed successfully or not.

Of course, there must be an eRoamingRemoteStop operation. It allows EMP customers to directly stop a charging session. Again, implementation is mandatory by the CPO partner, because it must be able to process this message in order to stop existing charging session.

As you can see in the example, the request is very simple. You need to provide EVSE ID, session ID and provider ID. As a response, you may expect an acknowledgement message.

After a charging session is completed, CPO must generate a ChargeDetailRecord associated with the session ID. CDR is a final summary of a charging session with details like meter values and consumed energy. CDR is immutable. You can think of it as a kind of invoice for a charging session. Because of that, Hubject created a separate operation in authorization service called eRoamingChargeDetailRecord. This operation is used for sending a CDR from CPO to the Hubject platform. Hubject will not only forward a CDR to online EMP but will also store the CDR in its database, in case EMP system cannot be addressed at the moment.

CDR data model is huge and has a lot of details regarding the charging session. We won't cover them all, but we'll point out the most interesting ones. Scientmeter values is a custom field needed in order to be compliant with german market regulations. Another field needed for that regulation is calibration law verification info. This field contains additional information regarding signed meter values. ChargingStart and ChargingEnd are pretty self-explanatory, but how are they different from SessionStart and SessionEnd? In general, session can be started before the charging process. For example, when a user authenticates himself at the charging point by RFID card. Also, session can end after a charging process is finished. Because of that, Hubject introduced separate fields for start date and end date of those two concepts. Consumed energy is a difference between MeterValueEnd and MeterValueStart, each of these fields is expressed in kilowatt hours.

MeterValueInBetween is a list of meter values present in a charging session. It is used for showing more detailed characteristics of charging.

Another service offered by Hubject is eRoamingReservation, this service is very simple. It contains only two operations; implementation is not mandatory by CPOpo but if a charging station offers reservation services then this functionality can be exposed to EMP by using operations defined in eRoamingReservation service.

First operation is eRoamingAuthorizeRemoteReservationStart, it allows EMP customers to reserve a charging point of a CPO. Information if a charging point offers reservation services is a part of an EVSE data. In value added services field Hubject will first check if there is a valid contract between EMP and CPO, then it will check if EVSE is known and if CPO is the owner of EVSE and after that it will forward the request to CPR. As a result session ID is generated and also we must remember that provider ID and EVSE id must be a part of a request.

Request or AuthorizeRemoteReservationStart is very similar to AuthorizeRemoteStart, we have an identification field which holds authentication data to authorize the user. Also, we have previously mentioned provider ID and EVSE ID fields which are mandatory. Then we have a duration field which is expressed in minutes. Finally, we have session ID related fields.

If we have a possibility to start a reservation, we also need to have a possibility to stop the reservation. eRoamingAuthorizeRemoteReservation tab is used for that. It's very simple; it allows EMP customers to end existing reservations. After that, CPO must generate a proper CDR for this operation.

Request for RemoteReservationStop is very simple - you must provide session ID, provider ID and of course EVSE ID.

Checklist - Core CPO platform requirements

Actively supported two commercial open standards facilitating EV roaming.

Being an eMobility leader in various projects across multiple startups, Piotr was responsible for OCPI and OCPP integration as well as EMP and CPO platforms development. With extensive expertise in the open standards field and eMobility tech solutions, he is leading teams of experienced developers and contributing with invaluable knowledge and experience.

Piotr Majcher

Interoperability demands a flexible approach and cooperation between market participants. For opening the electric car charging market open standards have been established. Two are an initiative of independent associations (responsible for the development of Open Charge Point Interface and Open Clearing House Protocol). The two other open standards for EV roaming are privately held but similarly open and free to apply. Hub operators GIREVE and Hubject offer innovative customer-friendly service networks for cross-border charging. Both hubs actively support network growth. Becoming a marketplace for charge point operators, e-mobility service providers, car manufacturers, energy suppliers, and public institutions Hubject and GIREVE offer a broad range of profitable solutions and facilitated communication benefits.

Hubject’s network expands beyond Europe. At the moment hub operator connects 767 partners in 52 countries offering over 250 000 charging stations. Hubject is a joint venture of the BMW Group, Bosch, EnBW, Enel X, Mercedes-Benz, innogy, Siemens, and the Volkswagen Group. Initiated in 2012, forms now the largest pool of charging stations. Via intercharge, the dedicated e-mobility platform, provides standardized access to charging infrastructure. Besides, Hubject advises automotive manufacturers, charging providers, and other EV-related businesses launching e-mobility services or implementing Plug&Charge with ISO 15118.

GIREVE has been created as a startup by leading French players in electric mobility: Renault, CNR, la Caisse des Dépôts, EDF et Enedis. At the moment GIREVE operates on 31 European markets and offers 185 charging networks with 109 476 charging stations accessible via EV roaming. Following the open policy in November 2020 hub operator announced becoming a Full Contributor of EV Roaming Foundation (the one responsible for the development of the OCPI open standard). This provides enhanced opportunities for partners. For instance, for an operator being already OCPI compliant, there is no extra cost to connect to GIREVE. Offering two standards for interoperability enables innovation and progress for e-mobility.

OICP was designed in 2012 by Hubject - formed by leading automotive experts in Germany. Besides being the roaming platform, Hubject offers technical connection and contractual arrangements for e-roaming. The general structure of the OICP is divided into two parts - for the eMobility Service Providers and Charge Point Operators, nevertheless, the product offer is constantly being developed. Hubject proclaims the OCIP is “the most widely implemented communication standard between European eMSP and CPO systems”. The most recent version, 2.3, was released in October 2020. The newest update of the protocol follows market requirements - improves the POI quality in an upscaling market, calibration law compatibility, data process performance, and offers higher transparency on the different charging use cases. Additionally, Hubject offers helpful and relevant for CPOs set of remote testing functionalities, for complex examination of various use cases. With the recent protocol update, from July 1st, OCPI 2.1 will be withdrawn.

The protocol is publicly available at no cost and requires no registration. From May 2019, OICP became an open-source protocol, free of charge, distributed on Hubject’s website and on open code distribution systems. The aim is to include more stakeholders in the evolution of OICP. The protocol is published under the Creative Commons Attribution-ShareAlike 4.0 International License. This grants easy distribution and to be shared under the same consent. Additionally, Hubject offers Hubject-compatibility certification.

OICP is formed on SOAP (Simple Object Access Protocol) and uses an object-based approach. It’s a real-time protocol, that also offers asynchronous operations. Although a back-up database is provided, Hubject doesn’t actively support downloads to the charging station. The platform maintains a record of the transaction data.

The OICP protocol documentation establishes market roles as follows:

The EV user/owner wants to charge an EV at a charge point/charge station, and has an agreement with the eMSP.

The eMobility Service Provider wants to enable EV owners the access the charge points. In most cases, the eMSP has a valid contract and transfers information with the Charge Point Operator via Hubject’s platform. Hubject offers connection via eMSP aggregator, which enables communication with the platform. This means several eMSPs can integrate via an eMSP aggregator, hence, the sub-partners do not need to associate with Hubject.

The Charge Point Operator (CPO) manages a charge point. The operator has a signed contract and exchanges information via Hubject’s platform. Like eMSPs, several CPOs can integrate via a CPO aggregator. Appropriately the sub-partners do not need to register with Hubject, because the communication with Hubject is done via the CPO aggregator.

Hubject, being a roaming hub, facilitates communication between eMSPs and CPOs via the EV roaming platform Hubject Brokering System.

OICP supports the following functionalities:

Roaming via hub - The CPO and the eMSP system connect to based on web services Hubject B2B Service Platform. Both parties, the CPO and MSP, have an e-roaming contract through Hubject.

Ad hoc payment - ‘Intercharge direct’ is an ad hoc payment dedicated solution integrated in OICP and Hubject platform. This allows any contractless EV owner to charge up and pay at any charging station.

Authorization - Hubject links the IDs of eMSPs or CPOs and SSL certificate information. Then each does or does not authorize the charge session. Hubject’s database performs as back-up, but not actively support downloads from their database to the charging station.

Reservation - An EV owner can book a charge point e.g. via eMSP app. Hubject checks charge point compatibility with the EV.  If matches send the request to the CPO, which in return responds whether the booking was successful. A reservation can also be withdrawn.

Billing - Charge session data is recorded in Charge detail records (CDRs). Hubject passes on the CDR to the eMSP and stores the CDR in the system.

Charge point information - Uploaded charge point information can be distributed between CPOs and eMSPs via Hubject’s platform. The information areas are charge point ID, CPO, charge point name, charge point location (name, address, geocode, type), time zone, opening times, current availability, accessibility, tariffs, authorization modes, means of payment, charge mode, connector type, maximum power, hub connection, support contact number, reservation possible, real-time status information possible, predictive charge point usage, smart charging services, and the date of the last update. OICP maintains flexible pricing based on charge facility, charge point location, and time-of-use.

Real-time charge point information - This covers dynamic charge point availability status and tariff information.

Session information - Session ID, service specifics, charge point ID, authentication data, start and end time of charging, start and end time of connection, starting and stopping meter value, meter value in between, consumed energy, CPO ID, MSP ID.

Remote start/stop - From within the eMSP application, a charging session can be operated.


eMIP is designed and developed by a French start-up. Created in 2013 by leading French players in electric mobility: Renault, CNR, la Caisse des Dépôts, EDF et Enedis with the main objective to provide “open access to vehicle charging stations”. The core business of GIREVE is to offer a roaming platform for eMSPs and CPOs.

The eMobility Interoperation Protocol enables roaming via clearinghouse data. The protocol provides access to charging point databases, and smart charging features. Although the GIREVE’s main market is France, in 2017 expansion covered the connection of European operators in Austria, Germany, Netherlands, Switzerland, Sweden, UK, Italy, Romania, Norway, Czech Republic, Lettonia, Hungary, Denmark, Belgium, Spain, Slovakia, Irland, and Luxembourg. In 2018 GIREVE’s platform was made compatible with the open protocol OCPI. Currently, the roaming platform operates in 28 countries.

The most recent version, eMIP 1.0.7, was released at the end of July 2019. eMIP is open for free although requires registration. GIREVE also proposes certification services. Moreover, to join GIREVE, the before-mentioned certification is required to connect to the platform. The eMIP protocol is open and, when a partner is approved by GIREVE, allows complete benefits. This includes connecting with a different hub platform or conducting peer-to-peer connections. Note, the protocol documentation explicitly declares GIREVE as the hub platform, the eMIP in practice does not apply to peer-to-peer connections. To ensure a high level of architectural openness and up-to-date offering, GIREVE consults with stakeholders potential future functionalities. GIREVE entirely takes responsibility for the eMIP protocol, in contrast to the previously mentioned approaches (commercial and non-commercial), there is no formal eMIP-member association.

eMIP is based on SOAP (Simple Object Access Protocol). Although eMIP is designed as a real-time protocol, it also supports asynchronous operations. The peculiarity of eMIP’s architecture makes it fairly adaptable and flexible. Any new sorts of data messages, or identification methods, can quickly be added via definition tables.

eMobility Interoperation Protocol documentation defines market roles as follows:

The EV user/owner wants to charge a vehicle at a charge point and an authorization medium.

The eMobility Services Providers warrant EV owners different services amongst which EV charging service, rental, car-sharing, navigation services, etc. The eMSP has a B2C agreement with the EV owner/user and a subscription to GIREVE’s platform.

The Charge Point Operator (CPO) accesses charging infrastructure and other services to EV users/owners and has a subscription to GIREVE’s platform.

The data aggregator applies to a system controlling charging infrastructure data in a given area and which can be inquired via GIREVE’s platform.

GIREVE, as a hub, manages the eMobility Services Platform which offers and ensures technical and functional means to standard services between the eMSPs, CPOs, and data aggregators.

eMobility Interopeational Protocol supports the following functionalities:

Roaming via hub - eMSPs, CPOs, and data aggregators join, based on web services, GIREVE’s roaming platform. The protocol documentation indicates GIREVE as the hub platform.

Authorization - eMIP offers several authorization processes.

Synchronous Authorization - check-in via the charge point (e.g. with an RFID card) or via the eMSP (e.g. an app).

Asynchronous Authorisation: Authentication Data Exchange. The eMSPs upload a list of approved subscribers to GIREVE’s platform. The list can be downloaded by CPOs. When charging at the charge point, e.g. via a RFID card, the CPO verifies the ID with the list provided.

Asynchronous Authentication Data Exchange & Synchronous Authorisation covers an event when CPOs do not download the list but request GIREVE to review the EV user ID. The decision on which authorization process to implement lies at the CPO's discretion.

Reservation - An EV driver can reserve a charge point via the eMSP app. (If the option is implemented and supported)

Billing - CDRs between CPOs and eMSPs are exchanged via GIREVE’s platform. This forms the foundation for invoicing. Via Asynchronous Exchange, the eMSP can download a CDR supplied by the CPO at any time, or via Synchronous Exchange - the eMSP gets quickly a CDR uploaded by the CPO.

Static charge point information - CPOs upload charge point information to GIREVE’s platform. GIREVE verifies the CPOs contract before updating their repository. The aforementioned data can be regained by CPOs, MSPs, and data aggregators. The information hold charge point ID, CPO, charge point manufacturer, charge point name, charge point location (address, geocode, type), time zone, opening times, current availability status, scheduled availability status, accessibility, tariffs, authorization modes, payment methods, charge mode, connector type, maximum power, guaranteed power, voltage, amperage, support contact, remote start/stop possible, reservation possible, and the time of the last update.

Real-time charge point information - GIREVE’s platform receives from CPOs the current availability status of the charge point. The CPOs agreement is verified before updating GIREVE’s repository. This includes scheduled status changes (e.g. for reservation).

Charge point search - The “charge point finder” function eMSPs can retrieve a list of charge points located in a given area and fulfill a set of charging criteria, (e.g. connector type).

Session information - Recorded and sent in the CDR - Charge Detail Record, covers the session ID, CPO ID, eMSP ID, EV user ID, charge point ID, contract ID, start and end time of charging session, metering report.

Real-time session information - With offered message service, CPOs can report events to eMSPs, and eMSPs can request actions while a charging session is in progress.

Remote start/stop - A charging session can be started or terminated by the eMSP.

Platform monitoring - GIREVE’s platform introduces a monitoring ability to check whether eMSPs, CPOs, and data aggregators have a valid connection to the platform. Specially designed “Heartbeat” tests the connection. The system sends “Heartbeat” requests to the associated companies.

EV roaming charging software of the e-mobility community

Privately held protocols offer great support and match users’ expectations. Joining at least one hub will be beneficial since emobility operators and providers can easily improve services and provide a top-notch experience. GIREVE and Hubject on a road to EV roaming extend charging infrastructure with additional user-friendly features. A cross-border network is on hand, and the support of emobility experts and industry leaders ensures the coherence and sustainability of the network. Keep in mind that even though both hubs are developing their individual protocols (OICP and eMIP), they also contribute to OCPI and OCHP growth.

OICP and eMIP refine the EV charging experience

The fact that both hubs were created at the initiative of automotive leaders makes the established EV charging e-roaming solution a guarantee of stability and accelerated growth of the whole network. Besides coverage of crucial functionalities, both protocols offer and develop additional services. The proof is in the numbers. Hubject operates on more than 50 markets on 4 continents and GIREVE offers a pan-European connection in nearly 30 countries. In light of the reality that the e-mobility market is growing rapidly and 2020 was a record year for electric car sales, it is expected that the scope of both hubs will continue to expand.

An extensive scientific analysis of the four most commonly developed protocols in terms of the search for the ideal protocol can be found 

Actively supported two commercial open standards facilitating EV roaming. Discover cross-border e-mobility standards for accessible charging network.

EV roaming with open standards - OICP and eMIP

Download our comprehensive PDF and learn about the pricing structures in e-mobility

Although it would seem rather straightforward, the pricing system within the EV charging environment extends further than just to the payments made by electric vehicles right after they charge their car.

Being such an interconnected network of mutual dependencies between numerous involved parties, e-mobility charging services require various levels of settlements.


It must be noted that it takes a few units to build up and manage a charging network. From 

, which manufacture the hardware side of required components (connectors, chargers, cables, etc), through 

, which are responsible for the backend management, all the way to 

, which determine the final user (here: EV driver) experience, there is a whole network of reliabilities.

Put simply and briefly, CPO’s are to establish billing connections with both EVSE and eMSP’s, in order to put the entire charging formation in place, while ensuring all parties receive transparent information and clear instructions.

To facilitate it, there are multiple types of pricings and contracts, some of which allow for complex, dynamic price models. Such undertaking is required so that eMSP’s can shape their end-users pricing often based on certain conditions, leaving the rates flexible.


Interoperability - the core of proper functioning

It should go without saying, that managing a pool of charging stations - oftentimes distributed across entire countries/regions - is not an easy task to handle and can only be achieved via advanced levels of interoperability and clear, unified procedures.

Open Standards are the chief example of how this can be achieved and maintained. Through the utilization of API’s like OICP the flow of information can be sustained in a transparent manner. This allows for a seamless communication and can facilitate the management of a vast majority of proceedings remotely, which comes in handy while developing a state-wide network, especially when there are numerous parties involved.


Knowing the behind-the-scenes nuances and arrangements, we prepared a comprehensive paper portraying the pricing structure within the e-mobility industry. Those who are willing to learn more about tariffs within charging services, should definitely find it useful.

Download our free paper and broaden your horizons with some great knowledge!

E-mobility tariffs. How is the pricing structured within the industry?

Anchor points on becoming Charge Point Operator. Click to learn more.

After founding Solidstudio, Pawel was an originator in terms of pursuing expertise in eMobility. With the build-up of a solid knowledge-base on industry’s needs & wants, he now keeps a close eye on products’ development. He’s also hugely responsible for the business’ side and designs the business models for our products.

Paweł Małkowiak

The e-mobility market is booming but still enigmatic in terms of processes between market participants or taken roles and available standards. In general, we can distinguish two sides of the charging ecosystem - being on the user-side eMobility Service Providers and Charge Point Operators providing devices and software to manage the infrastructure. In this piece, we address the part of the market responsible for deploying and managing charging points (also called charging stations).

Charge Point Operator or Charging Station Operator is responsible for providing, managing, and setting the charging infrastructure for the e-mobility industry. A CPO business operates a network of charging points - the hardware devices and future-oriented software. The value lies in connecting smart charging equipment with eMobility Service Providers. A CPO assures the network works seamlessly. This includes diagnostics, maintenance, price setting, and Point of interest (POI) data management.

On the operators' side is to provide available, steady, and 24/7 functioning EV chargers. Managing systems need to real-time report any malfunction that occurs with the device. And if possible, automatically fix it.

The matter of real-time also applies to software platforms. Necessary information delivery for adequate decision-making will help to shape operations, business, and technical statistics analysis. Even when the service does not assume the large scale, automation is the core in reducing the Total Cost of Ownership (TCO). Automated processes should hassle-freely handle transactional and technical concerns without engaging employees.

Charging Stations require sufficient energy supply and distribution. Smart management during peak hours, involving renewables and storing battery power, reduces capital and operating costs. Identifying areas for cost optimization and investigating user’s expectations will help balance business processes. This market will continue to grow, for now, with a focus on segmentation, preferences, and habits, the hidden (greener) Holy Grail is possibly up to grasp.

How does the Charge Point Operator platform work?

First, we need to explain that an Operator’s role range may vary. In some cases, CPO owns the infrastructure, provides connectivity, and can supply only one side of the ecosystem. Some of the CPOs act like 

 . Since it’s a mutual interest, they offer other eMSPs access to the charging infrastructure.

To explain the charging ecosystem’s general flow, let’s place CPO as a separate service - hardware and software provider. In this scenario, CPO exposes access to the charging network and relies on eMSPs.

CPO exposes charging network with tailored API. In this scenario, each new linking with a partner follows the provided documentation and matches eMSPs API. This approach is time-consuming and limiting in terms of fast integration and scaling. Via custom API, we link two models and two teams working separately. The matter lies in the charging options provided, and the service eMSP wants to offer. The integration via custom API takes months. Assuming that each operator offers only integration via its API, connecting with each requires substantial resources and time.

However, there are two faster ways to connect and open the charging network.

 follow the general principle in the e-mobility world, providing an open and accessible network to EV drivers. Charge Point Operator can expose charging network to any eMSP in a standardized way, enabling faster integration and scaling. With Open Charge Point Interface (OCPI), managed by 

 , the linking between partners can be done within several days. Open Standards, besides, provide transparent information to consumers about charging locations and prices. Moreover, they are developed and updated by a strong community 

following technical innovations and market requirements

 . Also, as a part of the ultimate goal, Open Standards are free to use. By simplifying, standardizing, and harmonizing charging networks, standards are an integral part of rapid e-mobility growth.

With one contract owned Charging Stations become exposed to thousands of new users and eMobility Service Providers. Thanks to the Open Intercharge Protocol (OICP), integration with a hub like GIREVE or Hubject opens the broadest spectrum of possibilities. E-roaming networks are the desired state of EV charging cross-border arrangement.

Being integrated with a hub does not limit the other possibilities. Charge Point Operator’s platform can be exposed at the same time to the hub, and eMobility Service Provider via the most commonly applied (and supported) OCPI standard.

What are the Charge Point Operator platform’s features?

At the most basic level, every Charge Point Operator platform should provide via admin panel pricing, reporting and billing solution, remote charging stations management, and smart energy management.

The comprehensive backend system allows CPO to 

 for the charging session. Rates can be modeled and verified at the admin panel. The charging session’s price can be specified on the total charged kilowatt-hours, the duration, or a blend of other circumstances (additional parking fee, time & day of the week). The B2B contract between CPO and eMSP includes all tariffs and is invoiced at the end of the billing period. The price that is exposed to the final user (EV owner) depends on the individual eMSP price management system.

, CPOs should easily handle all station-related administration and control tasks. The admin panel should provide a view of the billing history, modify charging prices, remote management of chargers, and with advanced automation resolve common issues.

 allows to reduce the risks of the station and network overload, ensure EVs are charged securely and economically optimized. The highest charging switch can be limited from the admin panel. For example, developing a feature for dynamic load management (DLM) allows setting maximum capacity for several charging points and diffuses the load within the single one.

How can Charge Point Operators optimize their business?

Focus on operational advantage, staying up-to-date with the most recent protocols’ releases, smart energy administration, monitoring, and analyzing will provide excellent scalability and interoperability. The reliable charging infrastructure management system, easy to maintain and open for eMSPs boosts network scaling and ROI. In turn, an e-roaming platform exposes charge points in the fastest and most efficient way. Fortunately, one approach does not eliminate the possibility of benefiting from the other. However, responsibility for the maintenance of charging points remains on the CPO's side. Automation and the ability to make quick, ideally remote fixes, responsiveness will have a significant role in the prosperity of one's performance.

Direct and indirect recipients of CPO services depend on the availability of the entire operational infrastructure. This includes real-time hardware monitoring to identify and fix malfunctions before the beneficiary - or even the CPO - is aware of them. Automated maintenance reduces costs of in-field technical repairs.

It’s good to make sure the CPO platform offers smart energy management control. The entire energy flow across the EV charging system secures energy that is delivered at the right time to the right stock at the lowest cost.

The ability to scale is critical to keep up with the booming growth of the EV market. It’s not just about placing devices in an accessible locality but also about providing back-end infrastructure ready to connect with new partners and render the service.

For long-term operations, interoperability will be essential. On the CPO side lies the responsibility for delivering the 

 , allowing easy integration of any charger. Compatibility with protocols and standards like OCPP, OCPI, OICP secures smooth backend operations’ communications.

When considering investing in Charging Infrastructure, the above issues are worth verifying whether the available solutions on the market meet our expectations. Depending on the scale of the planned activity, our needs will differ.

How to efficiently manage interoperability?

Charge Point Operators are the foundation of the eMobility growth. Analyzing and improving EV charging operations leads to better decision-making. In consequence, it maximizes business profits and eliminates unnecessary costs ensuring the best EV charging experience. Regarding investments, this varies based on which market we plan to operate in. Both governmental plans and local units support the development of charging networks. Thus it is worth spending time and finding out what are the possibilities and criteria for obtaining subsidies. The shape of the budget may be subject to modification, and new approaches may arise.

With the advantage of having e-mobility experts, at Solidstudio we took on board the daring challenge of developing a CPO platform on our own. Knowing the industry's nuances, we made sure that the product we developed would suit a whole plethora of needs that various clients may search for. Thus, our CPO platform can be installed either in any client’s infrastructure or as supported by Solidstudio.

Our platform comes with various necessary functionalities that concur to an effortless charging stations management. The core features consist of:

There are more functionalities planned, they will be gradually announced.

 is fully customizable, ready to be designed as per client’s requests. Supplementary features (which are not within the license, such as the new standards implementation) can be available to purchase as an add-on or upgrade.

Open InterCharge Protocole Training. Lesson 4

03 MARCH 2022 • 12 MIN READ