Protocol coverage
See which of OCPP's nineteen functional blocks Flowion runs today, on which versions, and what you reach them through.
On this page
OCPP 2.1 groups its use cases into nineteen functional blocks, A to S. This page shows where Flowion stands on each, so you can check a requirement in a minute.
A block counts as supported when it works end to end and you can use it through the API or the console, not merely when the message types exist. Every block also depends on the charger: a feature a charger does not implement still will not run on it. The supported devices list shows what each model speaks.
Supported today
The everyday work of running a charging network: getting chargers online, deciding who charges, recording sessions, and controlling chargers remotely.
| Row | Block | What you get | Versions |
|---|---|---|---|
| B | Provisioning | Automatic registration with setup per make and model, boot history, settings kept in step on every charger, configuration keys and the 2.x device model, restarts, triggered messages | all |
| C | Authorization | Live decisions from your access rules and the people you allow, cards held by people, offline behaviour kept in line with your rules, mid-session revocation on 2.x | all |
| E | Transactions | Full session lifecycle as an event log, energy, stop reasons, per-session limits on 2.1 | all |
| F | Remote control | Remote start and stop, start with a current cap, release a cable, triggered messages | all |
| G | Availability | In and out of service per connector, EVSE or whole charger | all |
| H | Reservation | Reserve a connector for a person, cancel it, and reservation status from 2.x chargers, through the API | all |
| J | Metering | Session readings, standalone readings, the charger's main meter | all |
| O | Display message | Messages on the charger's screen, set per charger, site or project and re-sent if the charger loses them | 2.0.1, 2.1 |
| P | Data transfer | Send vendor-specific data to a charger | all |
Partly supported
Each of these works today for what is listed; the rest of the block is on the way.
| Row | Block | Works today | Not yet |
|---|---|---|---|
| A | Security | Basic auth over TLS (Profile 2), key rotation, certificates signed by Flowion's own certificate authority for 2.x chargers, security events received | Client-certificate connections (Profile 3), pushing a new key to the charger |
| D | Local authorization list | On 1.6, the list is built from who may charge and pushed for you | 2.x |
| I | Tariff and cost | Tariffs defined, versioned and assigned per project, site, charger or EVSE; cost per session; tariffs sent to 2.1 chargers | Payment terminals |
| K | Smart charging | Load balancing across circuits with live energy monitors, priorities and price-aware planning; charger current limits; per-session limits on 2.1 | Composite schedules, ISO 15118 charging needs |
| L | Firmware | Firmware updates from Flowion's firmware catalogue, on 1.6 | 2.x |
| N | Diagnostics | Diagnostics files from 1.6 chargers, status history, active faults, every inbound message | 2.x log retrieval, monitoring |
Not yet supported
M Certificate management (installing certificates on a charger, ISO 15118 contract certificates)
Q Bidirectional power transfer
R DER control
S Battery swapping
These are OCPP 2.1's newest blocks and the least common in hardware today.
Beyond the blocks
Much of what Flowion does has no OCPP use case at all:
Organizations and projects, with members and permission policies.
Sites and circuits, with load management that keeps each site within its limits.
Energy monitors reporting a circuit's live load.
Day-ahead electricity prices, served through the API.
Webhooks and live updates, instead of polling.
Virtual chargers, to build and test against before any hardware.
Chargers connected through their maker's cloud, alongside chargers that connect directly.
Versions
All three versions connect, register, authorize, report status, run sessions and send meter values. Flowion meets each charger on the newest version it offers. See Which OCPP version am I dealing with? for the features that belong to one version.