OCPP connectivity planning
A commercial connected version that links a charger to a charge-point management system for remote operation, monitoring and integration workflows.
Choose OCPP for CPO, fleet, workplace or public-charging programs that require central management. APP and RFID may still be used at the driver layer, while DLB may still be required at the electrical site layer.
Request support →A defined scope technical and sourcing teams can use.
What this version adds
Backend connection, charger identity, remote commands, session and status messages, fault reporting and agreed security functions.
Best applications
Charge-point operators, fleets, workplace networks, public or semi-public charging and multi-site commercial programs.
How it differs
Compared with an end-user APP, OCPP connects the charger to an operator platform; compared with RFID, it can manage users and sessions centrally; it does not itself solve site power limits.
Confirm before ordering
OCPP version, CSMS provider, required message profiles, network method, SIM ownership, certificates, security profile, remote update policy and backend acceptance tests.
Four gates keep commercial speed aligned with engineering control.
- 01
Freeze the integration scope
Name the CSMS, OCPP version, required functions, security profile and responsible parties.
- 02
Prepare connectivity
Configure charger identity, endpoint, network, SIM or Ethernet, certificates and time settings.
- 03
Run backend acceptance
Exercise boot, authorization, sessions, meter values, remote commands, faults, offline queues and recovery.
- 04
Control released versions
Record approved firmware, backend version, test evidence and change-control responsibilities.