Device architecture
OCPP functions must fit the charging station's existing firmware, hardware, and system architecture.
ChargeSphere.OCPP
OCPP software for manufacturers of charging stations and wallboxes
ChargeSphere.OCPP connects charging stations to backend systems and can be integrated into existing OEM architectures. Clemios supports the agreed integration and technical validation. Technical acceptance in the target architecture is performed by the OEM.
The integration challenge
Why OCPP integration involves more than protocol communication
Backend integration
Errors can occur at the boundaries between the protocol, configuration, device state, and backend behavior.
Testing and validation
Integration tests must detect deviations and regressions before the software is used within the defined scope.
Product scope
What the ChargeSphere.OCPP product scope includes
OCPP communication functions
The product scope includes the OCPP communication functions defined for the intended use. The exact functional scope is agreed and documented for each integration project.
Charging-station-side system boundary
The product scope covers the OCPP component on the charging-station side. The CSMS or backend is not part of this product scope.
Interfaces and configuration
Interfaces, configuration, and any required adaptations are defined and documented based on the requirements and system boundaries of the relevant OEM architecture.
What the product does not include
The product scope is limited to the OCPP software component. Hardware, complete device firmware, and the complete charging system are not part of the product.
Complementary technical services
Technical support for integration and validation
The complementary services applicable to a project are determined by the agreed project scope. Clemios supports agreed integration, testing, and validation activities for the defined ChargeSphere.OCPP operational scope.
Technical evaluation
During technical evaluation, the intended functional scope, interfaces, target architecture, and any required adaptations are defined and documented.
OEM integration
Integration is based on the OEM's target architecture, the agreed interfaces, and the documented system boundaries of the project.
Project-specific adaptation
Any required configurations and adaptations are defined based on the documented hardware and software constraints and recorded within the agreed project scope.
Testing and technical validation
Depending on the project scope, Clemios supports agreed integration and system tests as well as the technical assessment of results against documented requirements and test systems.
Project scope and responsibility boundary
The services are optional and do not form a fixed service package. The specific scope is agreed for each project based on the target architecture, requirements, and documented system boundaries.
Technical acceptance of the agreed operational scope is performed by the OEM.
Technical validation is not equivalent to formal OCPP certification, complete conformance, or universal interoperability. OEM acceptance does not constitute formal OCPP certification or a general production or series release by Clemios.