01Protocols
OCPP
Open Charge Point Protocol 1.6J and 2.0.1
What it is, and how we use it
zevOS implements OCPP 1.6J and OCPP 2.0.1 as separate protocol handlers that normalise into a single internal event vocabulary. Everything downstream — billing, analytics, availability, the console — consumes the normalised form.
The practical consequence is that your operations team never needs to know which version a charger speaks in order to reset it, reconfigure it or read its uptime. Adding a protocol version is a gateway change, not a platform-wide project.
The gateway validates every incoming frame against the schema, responds immediately, and emits a domain event. It performs no database writes, no billing and no authorisation policy — because a gateway that blocks is a charger that disconnects.
Other standards
The rest of the picture
OCPI
The link between platforms. Publish your network to roaming partners, and let your drivers charge on theirs.
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.