THE CHALLENGEA Charger You Cannot See Is a Charger That Is Down
Charge point operators lose revenue and customers the moment a charger fails silently. A driver pulls up to a dead unit, the session never starts, and the operator finds out from a complaint instead of a dashboard. Most networks mix chargers from several vendors, each with its own cloud, so the operator has no single view of uptime, faults, or sessions. A vendor-neutral OCPP backend speaks to every compliant charger, detects faults the moment they happen, captures clean session data for billing, and gives the operator one dashboard for the whole network.
A component of the broader Telematics and GPS Tracking capability, often deployed with EV Fleet Tracking.
WHAT'S INCLUDED
The OCPP Backend and CPO Platform
OCPP Central System
The OCPP central system is where every charger connects, with support for OCPP 1.6J and 2.0.1 over secure WebSocket. It handles boot, heartbeat, status notifications, authorization, transactions, and remote commands, so any compliant charger from any vendor reports into one backend.
Uptime and Fault Analytics
Every connector status transition is tracked, surfacing availability, mean time to repair, and the specific fault codes a charger reports. A unit that drops heartbeats, faults a connector, or refuses sessions raises an alert immediately, so a dead charger never sits unnoticed.
Session Data and Metering
Meter values, energy delivered, duration, and cost are captured for every charging session, reconciled against the authorization and the connector. Clean session records feed billing, settlement with site hosts, and usage reporting with no manual stitching.
Remote Diagnostics and Control
Remote start and stop, reset, connector unlock, configuration changes, and firmware updates are exposed over OCPP. Your support team can clear a stuck session or push a config fix from the dashboard instead of dispatching a technician.
CPO Dashboard
The charge point operator dashboard shows a live map of every site and connector, uptime and revenue by location, a fault queue, and session history. Operations see the health of the network at a glance and drill into any charger for its full event log.
Roaming and Billing Integration
The backend connects to billing and roaming through OCPI so your drivers can charge across partner networks and your sessions settle correctly. Tariffs, CDRs, and token authorization flow between operators on open protocols.
UPTIME IS THE PRODUCT
Find the Fault Before the Driver Does
For a charge point operator, reliability is the whole business. Regulators and site hosts increasingly hold operators to uptime targets, and drivers simply stop coming back to a network that fails them. The monitoring layer catches problems the moment they appear and shortens the time to fix them.
Instant Fault Detection
A missed heartbeat, a faulted connector, or a repeated failed session triggers an alert with the OCPP fault code attached, so support knows what is wrong before they pick up the phone.
Remote First Response
Many faults clear with a remote reset or a config change pushed over OCPP. Resolving them from the dashboard avoids a truck roll and gets the connector back online in minutes.
Uptime Reporting
Availability is computed per connector, site, and network against the definitions your regulators and site hosts use, so your uptime numbers are defensible and your SLAs are easy to evidence.
HOW IT WORKS
Charger, Protocol, Cloud
Charger Connection
Chargers connect to the central system over OCPP on a secure WebSocket. Both 1.6J and 2.0.1 are handled, each charger is validated against the spec on onboarding, and a connection registry keeps track of which units are online.
Event Processing
Status notifications, meter values, and transactions stream into an event pipeline that updates connector state, builds sessions, and evaluates fault and uptime rules in real time. Commands flow back to chargers through the same channel.
Cloud Platform
A time-series store holds the full event and meter history. The dashboard, the analytics, and the OCPI roaming and billing interfaces all read the same records, so what operations see and what you bill always agree.
STANDARDS AND SECURITY
Open Protocols, Secure Sessions
OCPP Compliance
OCPP 1.6J and 2.0.1 are implemented to spec, including ISO 15118 plug-and-charge flows in 2.0.1 where chargers support them. Vendor-neutral by design, so you are never locked to one charger maker.
OCPI Roaming
OCPI is implemented for roaming and billing so locations, tariffs, sessions, and CDRs exchange cleanly with e-mobility service providers and hubs, letting your drivers charge across partner networks.
Connection Security
Charger connections run over TLS with WebSocket security, commands are authenticated, and session and driver data handling follows GDPR and local privacy rules. Firmware pushes are signed and staged with rollback.
FAQ
Common Questions
Which OCPP versions are supported?
OCPP 1.6J and 2.0.1 run over secure WebSocket, including the ISO 15118 plug-and-charge flows in 2.0.1 where the charger supports them. The backend is vendor-neutral, so any compliant charger reports into one central system.
Can chargers from different manufacturers be monitored?
Yes. Because the backend is built to the OCPP standard rather than to one vendor cloud, chargers from different makers connect to the same system. You get one dashboard for uptime, faults, and sessions across a mixed network.
How quickly is a charger fault detected?
In real time. A missed heartbeat, a faulted connector status, or a repeated failed session triggers an alert immediately with the OCPP fault code attached, so support knows a charger is down before a driver complains.
Can faults be fixed remotely?
Many can. Remote reset, connector unlock, configuration changes, and firmware updates are exposed over OCPP, so support can clear a stuck session or push a fix from the dashboard and avoid a technician visit.
How is session data used for billing?
Meter values, energy delivered, duration, and cost are captured for every session, reconciled against the authorization and connector. Those clean records feed billing directly and exchange with roaming partners as CDRs over OCPI.
Is roaming across networks supported?
Yes. OCPI support lets locations, tariffs, sessions, and CDRs exchange with e-mobility service providers and roaming hubs, so your drivers charge on partner networks and your sessions settle correctly.
Ready to Take Control of Your Charging Network?
Share your chargers, your OCPP version, and your uptime and billing needs to get a tailored approach covering the central system, the analytics, and the CPO dashboard.
Schedule a Free Consultation