Skip to main content

Smart OCPP Broker

The Pleevi Smart OCPP Broker is a transparent proxy that sits between your charging stations and your existing Charge Point Management System (CPMS). It intercepts OCPP messages to extract measurements and transaction data, and, if enabled, sends optimized charging schedules directly to the charging stations.

How It Works​

┌──────────────┐         ┌──────────────────┐         ┌──────────┐
│   Charging   │  OCPP   │   Pleevi Smart   │  OCPP   │   Your   │
│   Stations   │ ──────► │   OCPP Broker    │ ──────► │   CPMS   │
│              │ ◄────── │                  │ ◄────── │          │
└──────────────┘         └──────────────────┘         └──────────┘
                                  │
                                  │ Measurements &
                                  │ Transactions
                                  ▼
                         ┌──────────────────┐
                         │  Pleevi Engine   │
                         │  (Optimization)  │
                         └──────────────────┘
  1. You reconfigure the WebSocket URL on your charging stations to point to the Pleevi broker instead of your CPMS.
  2. The broker proxies all OCPP messages transparently to your existing CPMS, your CPMS continues to work exactly as before.
  3. Pleevi extracts measurement data and transaction events from the OCPP traffic to feed the optimization engine.
  4. If smart charging is enabled, Pleevi sends optimized charging profiles directly to the charging stations via OCPP SetChargingProfile messages.
info

Your existing CPMS will continue to receive all OCPP messages as before, no changes are needed on the CPMS side.

Two Modes of Operation​

Full Smart Charging​

In this mode, the broker handles the complete optimization loop:

  • Captures measurements and transactions from OCPP traffic.
  • Feeds data to the Pleevi optimization engine.
  • Sends optimized charging schedules back to the charging stations via OCPP.

This is the simplest integration path, no code changes are needed on your side. Just reconfigure the WebSocket URL and provide the onboarding information.

Driver Identification Only​

In this mode, the broker is used solely to identify drivers by listening to OCPP StartTransaction events and extracting the badge ID (RFID token). This links the driver to the charging session in the Pleevi platform (e.g., for the driver application).

Scheduling and optimization still flow through your existing integration (API or MQTT). See Driver Identification Mode for details.

Supported OCPP Versions​

  • OCPP 1.6J
  • OCPP 2.0.1
  • OCPP 2.1

Getting Started​

To connect your charging infrastructure to the Smart OCPP Broker, we need some information from you. See the Onboarding Guide for the full checklist, or download the onboarding form (PDF).

Need Help?​

Contact your Pleevi representative or email support@pleevi.ai.