Edge AI · Operations & OCPP

CPMS and OCPP Broker run where the charge points are.

Critical OCPP functions, site status, remote commands and session protection become locally available. The central backend stays important, but it is no longer the only place where operations can happen.

OCPP on site

Digital Twin, routing and queue at the edge.

The OCPP Broker maintains a state cache per charger, normalizes protocol quirks and routes messages to local or central backends. That protects running sessions during unstable connectivity.

Charger OCPP 1.6 / 2.0.1 Edge OCPP Broker Digital Twin & Message Queue Local CPMS Cloud CPMS / Fleet / Billing

Site operations

Live status, local commands, charger timeline and event log stay usable on site.

Migration & fallback

Backend routing per charger, group or site. Old and new CPMS can run in parallel.

Synchronization

Local events are sequenced and later transferred to cloud, fleet and reporting.