OCPP software component for OEMs
ChargeSphere.OCPP
Clemios provides ChargeSphere.OCPP, an OCPP software component for manufacturers of charging stations and wallboxes. ChargeSphere.OCPP connects charging stations with backend systems and can be integrated into existing OEM architectures.
Available for OEM integration · Formal OCPP certification is still outstanding
Connection between charging station and backend
ChargeSphere.OCPP connects charging stations with backend systems and can be integrated into existing OEM architectures.
Charging station
The OEM charging-station software and hardware form the target architecture.
ChargeSphere.OCPP
The OCPP software component is integrated within the agreed OEM operational scope.
Backend system
Communication with the target system belongs to the documented integration scope.
Product scope for OEM integration projects
The released functional scope of ChargeSphere.OCPP is commercially available.
OCPP software product
ChargeSphere.OCPP is an OCPP software product for manufacturers of charging stations and wallboxes.
Defined operational scope
The functions, interfaces, project-specific modifications, and known limitations are defined and documented during technical evaluation.
Product-related support
Clemios supports agreed integration, testing, and validation activities for the defined ChargeSphere.OCPP operational scope.
Technical validation is not equivalent to formal OCPP certification, complete conformance, or universal interoperability.
Functional blocks by OCPP version
ChargeSphere.OCPP implements all standard-defined Functional Blocks of OCPP 2.0.1 and OCPP 2.1. OCPP 2.1 continues the 15 functional blocks from OCPP 2.0.1 and adds four new functional blocks. Existing functional areas may be extended or adapted in OCPP 2.1.
OCPP 2.0.1
A defined OCPP 2.0.1 functional scope for OEM integration projects is released for ChargeSphere.OCPP.
OCPP 2.1
A defined OCPP 2.1 functional scope for OEM integration projects is released for ChargeSphere.OCPP.
New in OCPP 2.1:
- Tariff and Cost
- Bidirectional Charging
- DER Control
- Battery Swapping
Show all 19 functional blocks
| Block | Functional area | OCPP 2.0.1 | OCPP 2.1 |
|---|---|---|---|
| A | Security | Implemented | Implemented |
| B | Provisioning | Implemented | Implemented |
| C | Authorization | Implemented | Implemented |
| D | Local Authorization List Management | Implemented | Implemented |
| E | Transactions | Implemented | Implemented |
| F | Remote Control | Implemented | Implemented |
| G | Availability | Implemented | Implemented |
| H | Reservation | Implemented | Implemented |
| I | Tariff and Cost | Not part of OCPP 2.0.1 | Implemented, new in OCPP 2.1 |
| J | Meter Values | Implemented | Implemented |
| K | Smart Charging | Implemented | Implemented, expanded in OCPP 2.1 |
| L | Firmware Management | Implemented | Implemented |
| M | ISO 15118 Certificate Management | Implemented | Implemented |
| N | Diagnostics | Implemented | Implemented |
| O | Display Message | Implemented | Implemented |
| P | Data Transfer | Implemented | Implemented |
| Q | Bidirectional Charging | Not part of OCPP 2.0.1 | Implemented, new in OCPP 2.1 |
| R | DER Control | Not part of OCPP 2.0.1 | Implemented, new in OCPP 2.1 |
| S | Battery Swapping | Not part of OCPP 2.0.1 | Implemented, new in OCPP 2.1 |
Shared functional blocks may be extended or adapted in OCPP 2.1 compared with OCPP 2.0.1. The specific operational scope, interfaces, project-specific modifications, and known limitations are defined and documented for each OEM integration project.
Technical evaluation and integration
The OCPP version or version scopes, functions, interfaces, and project-specific modifications are defined and documented during technical evaluation.
Operational scope
The agreed ChargeSphere.OCPP operational scope forms the basis for further technical planning.
Interfaces
Required interfaces and dependencies are described for the target architecture.
Modifications
Project-specific modifications are defined within the agreed operational scope.
Testing and validation
Clemios supports agreed integration, testing, and validation activities for the defined ChargeSphere.OCPP operational scope.
Technical validation is not equivalent to formal OCPP certification, complete conformance, or universal interoperability.
Certification and technical acceptance
Product scope, technical evaluation, and acceptance are clearly separated for each OEM integration project.
Current certification status
ChargeSphere.OCPP is currently not formally OCPP-certified.
Technical acceptance
Technical acceptance of the agreed operational scope is performed by the OEM.
OEM acceptance is not formal OCPP certification and not general production or series release by Clemios.