OCPP Broker
The Pleevi OCPP Broker links charging sessions to drivers. It sits between your charging stations and your existing Charge Point Management System (CPMS) and forwards every OCPP message unchanged. Along the way it reads which badge (RFID card or token) started each session, so Pleevi can link the session to the right driver, for example for the driver application.
┌──────────────┐ OCPP ┌──────────────────┐ OCPP ┌──────────┐
│ Charging │ ──────► │ Pleevi OCPP │ ──────► │ Your │
│ Stations │ ◄────── │ Broker │ ◄────── │ CPMS │
└──────────────┘ └──────────────────┘ └──────────┘
│
│ Badge → Driver
▼
┌──────────────────┐
│ Pleevi Platform │
└──────────────────┘
- Your CPMS keeps receiving every message as before. Nothing changes on the CPMS side.
- The broker never sends commands to your charging stations.
- Measurements, transactions and charging schedules keep flowing through your existing integration: MQTT, the API, Eniris Smart Grid One, MINT or Pleevi Edge.
When to use it
- You want to use the Pleevi driver application, but your system cannot report which badge started a session.
- You use a local controller like the Eniris Smart Grid One, MINT PLCNext or Pleevi Edge for the charging schedules, and still want to identify drivers.
- Your CPMS or local controller applies the charging profiles, and you only need Pleevi to know who is charging.
Supported OCPP versions
- OCPP 1.6J
- OCPP 2.0.1
- OCPP 2.1
Get started
- Set up the broker for your site and point your chargers to it.
- Map the chargers to your assets, so Pleevi knows which connector is which asset.
- Add your drivers with their badges.
When a session is not linked to a driver, see Troubleshoot transaction linking. Using mutual TLS (security profile 3), a custom CA or a VPN? Email support@pleevi.ai and we set it up with you.
Need help?
Contact your Pleevi representative or email support@pleevi.ai.