Driver Identification Mode
The Smart OCPP Broker can be used in a lightweight mode where it only identifies drivers, without taking over scheduling or sending charging profiles to the stations.
How It Works
In this mode, the broker listens to OCPP StartTransaction messages from your charging stations. When a driver starts a charging session by scanning their RFID badge, the broker extracts the badge ID (idTag) from the transaction and links it to the corresponding driver in the Pleevi platform.
┌──────────────┐ StartTransaction ┌──────────────────┐ ┌──────────┐
│ Charging │ (with badge ID) │ Pleevi Smart │ OCPP │ Your │
│ Station │ ───────────────────► │ OCPP Broker │ ──────► │ CPMS │
└──────────────┘ └──────────────────┘ └──────────┘
│
│ Badge ID → Driver
▼
┌──────────────────┐
│ Pleevi Platform │
│ (Driver App) │
└──────────────────┘
All other OCPP messages are still proxied transparently to your CPMS. The broker does not send any commands back to the charging station in this mode, scheduling continues via your existing integration.
When to Use This Mode
This mode is useful when:
- You already have a working API or MQTT integration for sending measurements, transactions, and receiving schedules.
- You use a local controller like the Eniris Smart Grid One that handles charging schedules on-site, but you still want to identify drivers for the Pleevi driver application.
- You want to use the Pleevi driver application but need a way to link badge IDs to drivers without modifying your existing system.
- Your CPMS or local controller handles the actual charging profile application, and you only need Pleevi to identify who is charging.
What Gets Captured
| OCPP Message | Data Extracted | Purpose |
|---|---|---|
StartTransaction | idTag (badge ID), connector ID, timestamp | Links the driver to the charging session |
All other OCPP messages (MeterValues, StatusNotification, Heartbeat, etc.) are proxied through to your CPMS but are not processed by the Pleevi engine in this mode.
Scheduling Flow
Since the broker is only used for driver identification, the optimization flow remains unchanged:
- Measurements and transactions are sent to Pleevi via your existing API, MQTT, or Eniris Smart Grid One integration.
- Optimized schedules are delivered via the same channel (API polling, MQTT subscription, or directly to the Eniris controller).
- Your system applies the charging profiles to the stations.
The only addition is that the broker provides driver identity information to the Pleevi platform, enabling features like the driver app.
Setup
The setup is the same as the full Smart OCPP Broker, follow the Onboarding Guide. During onboarding, let us know that you want to use the broker in driver identification mode only, and we will configure it accordingly.
Need Help?
Contact your Pleevi representative or email support@pleevi.ai.