01Protocols
OCPI
Open Charge Point Interface 2.2.1
What it is, and how we use it
OCPI connects two charging platforms rather than a charger and a platform. zevOS implements version 2.2.1 in both the CPO and the eMSP role, which is what most networks of any size eventually need.
As a CPO you publish selected locations — you choose which, per partner — with live status and tariffs, authorise partner tokens in real time, and issue CDRs for settlement. As an eMSP you pull partner locations into your own app and start sessions remotely on chargers you do not own.
Inbound and outbound CDRs are stored and reconciled against partner statements, so roaming revenue does not become the line nobody can explain.
Other standards
The rest of the picture
OCPP
The link between every charger and the platform. Both versions run side by side behind one operational surface.
RoadmapISO 15118
Certificate-based vehicle identification, enabling plug-and-charge. On the roadmap, with OCPP 2.0.1 as the prerequisite.
RoadmapOpenADR
Utility-initiated curtailment signals applied through the charging-profile mechanism. On the roadmap.
Bring your integration questions
If your evaluation includes a protocol conformance review, we would rather have that conversation early than late.