Connect fleet charge points to a CSMS (Charge Point Management System) using OCPP 2.0.1, ensuring the CSMS supports the full TransactionEvent message set introduced in OCPP 2.0.1
Subscribe to TransactionEvent messages from the CSMS to capture charging session start, update, and end events including energy delivered (kWh), state of charge at start and end, and session duration
Correlate each charging session to a vehicle by matching the EVSE identifier and any provided idToken (RFID, eMAID, or fleet card) against your vehicle roster
Extract the meter values from TransactionEvent sampledValue arrays, selecting the Measurand types relevant to your fleet reporting (for example, Energy.Active.Import.Register, SoC)
Forward aggregated charging session records to your fleet telematics store, joining with GPS and trip data to build per-vehicle energy consumption reports
Implement OCPP 2.0.1 smart charging profile management to set per-vehicle charge limits and schedules via the ChargingProfile mechanism, enabling fleet-level energy cost optimization
Known gotchas
OCPP 2.0.1 uses a different transaction model from OCPP 1.6 (StartTransaction/StopTransaction replaced by TransactionEvent); if your CSMS supports both versions simultaneously, ensure your consumer correctly identifies which message version it is parsing
MeterValues in OCPP 2.0.1 are embedded within TransactionEvent rather than sent as standalone MeterValues messages in some implementations; check your EVSE firmware behavior to know which pattern to expect
State of Charge (SoC) reporting via OCPP depends on the EV sharing this data over ISO 15118 or proprietary protocols to the EVSE; not all EV/EVSE combinations expose SoC in OCPP meter values
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp