OCPI Roles and Typical Implementations

The Open Charge Point Interface (OCPI) is a protocol designed to facilitate communication between various actors in the electric vehicle charging ecosystem. It defines specific roles and commands, ensuring seamless integration and operation across different platforms. Below is a description of these roles and the typical commands associated with each, followed by a table outlining their typical implementations.

Step-by-Step Plan to Determine the Necessary Roles in OCPI Roaming

1

Step 1: Define Your Project’s Goals and Objectives

Analyze Your Needs: Identify the specific tasks your project needs to accomplish within the context of EV charging roaming. This could include managing charging stations, providing customer services, integrating with other networks, or managing roaming.
Determine Key Functions: Identify the core functions required, such as user authentication, transaction processing, charging session management, etc.

2

Step 2: Review the Available OCPI Roles

Study OCPI Documentation: Familiarize yourself with the official OCPI documentation to understand the available roles and their functions.
List of Roles:

CPO (Charge Point Operator): Manages and operates charging stations.
eMSP (eMobility Service Provider): Offers charging services to customers using CPO infrastructure.
Hub (Hub Service Provider): Facilitates roaming and integration between different CPOs and eMSPs.
NSP (Navigation Service Provider): Provides information about charging stations for navigation.
NAP (National Access Point): Manages and distributes charging station data on a national level.
SCSP (Smart Charging Service Provider): Manages smart charging solutions, optimizing energy use and costs.

3

Step 3: Match Roles with Your Project’s Functions

Align Roles with Functions: Match the functional requirements of your project with the corresponding OCPI roles.

If managing charging stations is a priority, you will need the CPO role.
If providing charging services to end-users is essential, the eMSP role is required.
To facilitate roaming between different networks, consider the Hub role.
For providing station data to navigation services, the NSP role may be necessary.
If managing a national charging station database is part of your project, you'll need the NAP role.
For implementing smart charging, the SCSP role is required.

4

Step 4: Determine the Required Modules and Commands

Step 4: Determine the Required Modules and Commands

Analyze Necessary Modules: Identify the modules you need to support within the selected roles. For example, if you are acting as a CPO, you may need modules for managing locations, charging sessions, tariffs, etc.
Identify Commands: Determine the commands necessary for interacting with other OCPI participants, such as authentication, tariff management, charging session data exchange, etc.

5

Step 5: Evaluate the Need for Interaction with Other Roles

Consider Interaction with Other Roles: Think about which other ecosystem participants you will need to interact with to ensure your solution works effectively. For example, as a CPO, you will need to interact with eMSPs to offer services to customers.

6

Step 6: Consider Scalability

Plan for the Future: If you plan to expand your infrastructure or add new functionalities in the future, consider the possibility of implementing additional roles or modules.

7

Step 7: Consult with Experts and Conduct Testing

Consult with Experts: Reach out to OCPI experts to ensure that you have selected the correct roles and modules for your project.
Testing: Conduct pilot testing of the selected roles and modules to ensure they work correctly and interact as expected.

8

Step 8: Implement and Deploy the Selected Roles

Implementation: Start integrating the selected roles and modules into your system.
Monitoring and Optimization: Continuously monitor the performance and make necessary adjustments to optimize the process.

Conclusion
Understanding the roles and commands in OCPI is essential for integrating and optimizing electric vehicle charging infrastructure. This table provides a quick reference to how different roles typically interact with the various modules within the OCPI protocol.