An operator compares CSMS platforms — charge point management systems — on what a network feels at scale: many sites under one console, driver accounts, roaming connections, settlement-grade reporting, and an exit that does not strand the network. A single site can forgive a weak function; a network cannot. No platform is named here: the comparison is won on written answers — the functions in the contract, and the OCPP evidence your hardware states.
Key Takeaways
- Compare a CSMS at network scale: multi-site control, accounts, roaming readiness, settlement reporting, uptime method, exit.
- “OCPP compliant” is evidence only when it names a version, its functions and tested pairings — in writing.
- Stated OCPP 1.6J, “OCPP-ready” and silence are three different hardware claims; plan on each.
- The contract review — fees, pairing proof, exit terms — is the comparison; the demo is not.
What a Network Feels That a Single Site Does Not
| Function | Why a network feels it | The written evidence to demand |
|---|---|---|
| Multi-site management | Administered once, not site by site; a tariff change is a network act | Site and group structure, and per-site tariff control, stated in the contract — not only shown in a demo |
| Driver accounts and access | One account or credential should work across the whole network, with groups priced differently | Supported credential types, and how accounts and balances are handled if you leave |
| Roaming readiness | Other networks’ drivers arrive through the platform — it is the door they charge by | Roaming support named as a contract function, with the connection route and terms written down |
| Settlement and reporting | Hosts, partners and funders are paid from these records; gaps become disputes | Per-site, per-group session, energy and revenue reports — exportable, with a stated retention period |
| Uptime and fault operations | Funders read uptime from the platform’s records; faults are triaged remotely first | Which charger functions the platform implements — alerts, remote start, stop, reset — and how its uptime figure is calculated |
| Exit and portability | Networks outlive platform contracts; a bad exit strands chargers, accounts and history | Full data export, the re-pointing route and its cost, contract length and notice |
Uptime shows why the written method matters. The U.S. NEVI programme, under 23 CFR Part 680, expects corridor stations to average above 97% annual uptime — a figure that exists only as a platform calculation. Two platforms can report the same network differently; ask how the number is built before a contract depends on it.
The Hardware Side: An Evidence Ladder
The platform can only use what the charger states and implements — the layer our OCPP explainer for operators covers in depth. Read hardware claims as a ladder. At the top, a listing names a version: the EV-AC03201T AC station and the EV-RHDC30K-L compact DC charger both state OCPP 1.6J — confirm the platform runs that version and has tested the pairing, in writing. One step down, a listing says “OCPP-ready”, as the EV-ACS3210E’s does: the phrase leaves the version, any certification and the tested pairings open — questions to close before a network plan relies on that model. Below that, a listing stating neither is not platform-pairable on paper. And RFID or an app, as the EV-ACT3204E states, are local access features — not a CSMS connection.
Run the Comparison as a Contract Review
- Score written answers, not demonstrations. A demo shows a function exists; the contract decides whether it is yours, and at what fee line.
- Prove one pairing before the rollout. A charger-to-platform pairing is tested, not assumed — integration testing is a step of its own, done on one unit before fifty depend on it.
- Price the whole term. Per-charger and per-site fees, transaction lines and reporting charges live in the contract’s fee schedule — the only place platform prices honestly exist.
- Write the exit before you need it. Export rights, account handling and re-pointing costs are cheap at signing, not at departure.
EVDANCE builds hardware and operates no CSMS; its part is stated claims a platform must match, with a 3-year standard warranty behind the units. Pairing and network hardware questions run through our commercial charging page or contact us.
Frequently Asked Questions
What should “OCPP compliant” mean in a platform or hardware contract?
A named version, the functions implemented at that version, and tested pairings confirmed in writing. “Compliant” with no version named is not evidence — it cannot be tested or enforced.
Can one CSMS run chargers from several makers?
Yes — that is what an open protocol is for. Each model’s stated version must be supported, so confirm pairings per model, in writing, before a rollout depends on them.
Does EVDANCE provide the platform for its stations?
No. EVDANCE is the hardware manufacturer; the CSMS is a separate service you contract with its provider. EVDANCE’s part is a charger whose listing states the claim the platform must match.
Related Reading
- OCPP Explained: What Charge Point Operators Need From EV Charger Hardware
- How Do Commercial EV Charging Stations Work?
- RFID and User Management for Shared EV Chargers
