Standards and Protocol Map¶

Standards describe boundaries between parties, assets, and systems. BetterFleet maps those boundaries into product concepts, then keeps the standard-specific details at the integration edge.

Use this page to answer three questions:

Which real-world boundary does the standard describe?
Which BetterFleet domain owns the decision that depends on it?
Which core ontology concept should the data project onto?

General Standards Map¶

Standard or family	Boundary	Main problem coordinate	Main physical coordinate	BetterFleet interpretation
OCPP 1.6J	charge point to central system	Smart Charging -> Protocol & Interoperability	charge point, connector, transaction, meter, time	Live charger operations, commands, status, meter evidence, and fault evidence.
OCPP 2.0.1 / 2.1	charging station to CSMS	Smart Charging -> Protocol & Interoperability	charging station, EVSE, connector, component, variable, certificate, transaction event, time	Richer charger topology, device model, transaction events, security, certificates, and smart-charging capability.
IEC 61851	EV conductive charging system	Smart Charging -> Charger Control	EVSE, EV, control pilot, charging mode, current limit	Electrical charging modes and basic control signalling. Useful when explaining what a charger can physically do before higher-level protocols act.
IEC 62196 / CCS / SAE J3400	plug, socket, vehicle inlet, and coupler family	Smart Charging -> Protocol & Interoperability	connector, cable, inlet, AC or DC path	Physical connector compatibility. Treat as hardware capability and deployment constraint, not as a session or commercial model.
ISO 15118	EV to EVSE high-level communication	Smart Charging -> Protocol & Interoperability; Resilience & Security -> Security & Access Control	EV, EVSE, connector, certificate, contract, charging session	Plug and Charge, EV-to-EVSE negotiation, smart charging, bidirectional charging, and certificate trust.
DIN SPEC 70121	EV to DC charger communication, mainly legacy CCS DC	Smart Charging -> Protocol & Interoperability	EV, DC EVSE, connector, charging session	Legacy DC charging communication that may appear in charger compatibility discussions. Prefer ISO 15118 for forward-looking models.
IEC 63110	charging and discharging infrastructure management	Smart Charging -> Protocol & Interoperability; Energy & Cost Management -> Site Energy & Infrastructure	charging infrastructure, CSMS, energy management, e-mobility actors	Future-facing management model for charging infrastructure and energy-transfer services. Track beside OCPP rather than treating it as today's production boundary.
OCPI	CPO to eMSP or roaming hub	Roaming & Shared Charging -> Network Access & Interoperability	location, EVSE, connector, token, tariff, session, CDR, time	Roaming data exchange for locations, tariffs, tokens, commands, sessions, and CDRs.
OICP	Hubject platform roles and intercharge flows	Roaming & Shared Charging -> Commercial Settlement & Shared Charging	CPO, EMP/eMSP, EVSE, token, authorization, CDR, price, time	Hub-centred roaming, authorization, EVSE data/status, pricing, CDR, and settlement flows.
OCMF	signed charging metering payload	Reporting & Insights -> Cost, Carbon & Compliance	meter, transaction, signed value, public key, time	Tamper-evident metering evidence for billing, audit, and regulated market transparency.
OSCP	flexibility provider to capacity provider, site owner, or DERMS	Energy & Cost Management -> Advanced Energy & Grid	group, grid connection, microgrid node, operating envelope, time	Capacity forecasts and flexibility constraints translated into protocol-neutral operating envelopes.
OpenADR	utility, aggregator, or market actor to flexible load/DER participant	Energy & Cost Management -> Advanced Energy & Grid	site, load, DER, demand response event, program, time	Demand response and flexibility event signalling. Candidate source for operating envelopes, curtailment requests, or flexibility programs.
IEC 61850	grid automation, substation, and DER information models	Energy & Cost Management -> Advanced Energy & Grid	grid asset, DER, protection/control equipment, telemetry	Grid and DER-side information models. Useful when integration goes below tariff/envelope level into utility or DERMS equipment semantics.
IEEE 2030.5	utility/DER aggregator to DER or customer energy resource	Energy & Cost Management -> Advanced Energy & Grid	DER, load, tariff, demand response, metering endpoint	US-leaning DER and demand-response integration candidate. Treat as grid-edge integration, not charger control.
VDV 452	planned route network and timetable data	Operations & Dispatch -> Depot & Integration	route, line, stop, journey, block, timetable	Planned work input. Maps primarily to `work`, schedules, blocks, duties, and depot planning.
VDV 462 / NeTEx	German profile and European model for planned public-transport data	Operations & Dispatch -> Depot & Integration	route, network, timetable, stop, line	Rich planned-data exchange. Maps to the same `work` concept as VDV 452, often with broader network modelling.
VDV 455	duty roster transfer	Operations & Dispatch -> Depot & Integration	duty roster, driver allocation, vehicle parking position, training requirement	Workforce and depot-operations context. Use when roster or depot positioning affects work assignment or readiness workflows.
VDV 453	real-time data interface for connection protection, dynamic passenger information, visualisation, and general messages	Operations & Dispatch -> Fleet & Vehicle Management; Incidents & Notifications -> Detection	vehicle movement, stop, connection, passenger information, operational message	Live operational state. Maps to `vehicle activity`, work execution, and incident/report evidence, not directly to charging plans.
VDV 454	real-time timetable information and schedule information services	Operations & Dispatch -> Dispatch & Scheduling; Reporting & Insights -> Operational Dashboards	current timetable state, service updates, actual or adjusted departures	Short-term operational schedule evidence. Useful for readiness confidence and reporting.
VDV 463	charging management to upstream systems such as DMS and ITCS	Operations & Dispatch -> Dispatch & Scheduling; Smart Charging -> Load Management	vehicle, depot, charging station, charging point, target SoC, departure time	Charge-planning bridge. Maps future work into energy requirements and charging information.
GTFS / GTFS Realtime	public-transport schedule and real-time feeds	Operations & Dispatch -> Depot & Integration	route, trip, stop, block, vehicle position, service alert	International schedule and real-time feed source. Project onto `work` and `vehicle activity` before planning.
TransXChange	UK bus timetable exchange	Operations & Dispatch -> Depot & Integration	route, journey, stop, operator, timetable	UK planned-work source for schedule creator and planning flows.
SIRI	public-transport real-time information services	Operations & Dispatch -> Fleet & Vehicle Management	vehicle monitoring, estimated timetable, stop monitoring, service alert	International real-time operations feed. Maps to `vehicle activity`, service disruption, and dashboard projections.

Standards Layer View¶

flowchart TB
  subgraph Physical["Physical charging and site layer"]
    Connectors["IEC 62196 / CCS / SAE J3400<br/>connector and inlet compatibility"]
    Conductive["IEC 61851<br/>charging modes and control pilot"]
    VehicleComm["ISO 15118 / DIN SPEC 70121<br/>EV to EVSE negotiation"]
    SiteEnergy["Meters, DER, grid connection,<br/>storage, generation, site load"]
  end

  subgraph ChargerPlatform["Charging platform layer"]
    OCPP["OCPP<br/>charger to CSMS"]
    IEC63110["IEC 63110<br/>charging infrastructure management"]
  end

  subgraph BetterFleet["BetterFleet domain layer"]
    Work["work"]
    Requirement["energy requirement"]
    EnergySystem["energy system"]
    Charging["charging"]
    VehicleActivity["vehicle activity"]
    Commercial["commercial record"]
    Incident["incident / failure signal"]
  end

  subgraph Transport["Transport and depot planning layer"]
    Planned["VDV 452 / 462 / NeTEx<br/>GTFS / TransXChange"]
    Realtime["VDV 453 / 454<br/>GTFS-RT / SIRI"]
    ChargePlanning["VDV 463<br/>charging requests and information"]
  end

  subgraph Grid["Grid and flexibility layer"]
    OSCP["OSCP<br/>capacity forecast"]
    OpenADR["OpenADR<br/>demand response event"]
    GridDER["IEC 61850 / IEEE 2030.5<br/>DER and grid-edge semantics"]
  end

  subgraph Roaming["Commercial and roaming layer"]
    OCPI["OCPI<br/>CPO/eMSP roaming"]
    OICP["OICP<br/>hub roaming"]
    OCMF["OCMF<br/>signed meter evidence"]
  end

  Connectors --> OCPP
  Conductive --> OCPP
  VehicleComm --> OCPP
  SiteEnergy --> EnergySystem
  OCPP --> Charging
  IEC63110 --> Charging
  Planned --> Work
  Realtime --> VehicleActivity
  ChargePlanning --> Requirement
  OSCP --> EnergySystem
  OpenADR --> EnergySystem
  GridDER --> EnergySystem
  Requirement --> Charging
  EnergySystem --> Charging
  Charging --> VehicleActivity
  Charging --> Commercial
  Charging --> Incident
  OCPI --> Commercial
  OICP --> Commercial
  OCMF --> Commercial

VDV Is A Family, Not One Boundary¶

VDV appears in several BetterFleet discussions, but each VDV standard describes a different boundary.

Standard	Purpose	BetterFleet domain meaning	Typical mapping
VDV 452	Planned route network and timetable exchange.	Supplies planned work and schedule structure.	`route`, `journey`, `block`, `duty`, and `timetable` map to `work`.
VDV 462 / NeTEx	Profile and European planned-data model for network/timetable exchange.	Supplies richer planned-work and network structure.	Maps to `work`, with stronger route, stop, line, and network semantics.
VDV 455	Duty roster exchange.	Supplies depot and workforce context that can affect assignment and readiness operations.	Maps to work support context, driver allocation, and parking-position context.
VDV 453	Real-time operations services such as connection protection and dynamic passenger information.	Supplies live operational context and user-impact evidence.	Maps to `vehicle activity`, service state, and incident/report projections.
VDV 454	Real-time timetable and schedule information.	Updates short-term dispatch confidence and timetable reality.	Maps adjusted schedule state to `work` execution and `vehicle activity`.
VDV 463	Charging management interface between upstream systems and charging/load management.	Converts operational intent into energy requirements and charging information.	Maps charging requests to `energy requirement` and charging process information to `charging`.

flowchart LR
  subgraph Planned["Planned work"]
    V452["VDV 452"]
    V462["VDV 462 / NeTEx"]
    V455["VDV 455"]
    GTFS["GTFS / TransXChange"]
  end

  subgraph LiveOps["Live operations"]
    V453["VDV 453"]
    V454["VDV 454"]
    SIRI["SIRI / GTFS-RT"]
  end

  subgraph ChargeOps["Charging operations"]
    V463["VDV 463"]
  end

  Work["work"]
  Activity["vehicle activity"]
  Requirement["energy requirement"]
  Charging["charging"]

  V452 --> Work
  V462 --> Work
  V455 --> Work
  GTFS --> Work
  V453 --> Activity
  V454 --> Activity
  SIRI --> Activity
  Work --> Requirement
  Activity --> Requirement
  V463 --> Requirement
  V463 --> Charging

Charging Standards Do Different Jobs¶

OCPP, ISO 15118, IEC 61851, and connector standards are often discussed together. They sit at different layers.

sequenceDiagram
  participant EV as Vehicle
  participant Cable as Connector / coupler
  participant EVSE as EVSE / charging station
  participant CSMS as CSMS boundary
  participant BF as BetterFleet domains

  EV->>Cable: physical fit and electrical path
  Note over Cable: IEC 62196 / CCS / SAE J3400
  EVSE->>EV: basic conductive charging signalling
  Note over EVSE,EV: IEC 61851
  EV->>EVSE: high-level negotiation / certificates
  Note over EV,EVSE: ISO 15118 or DIN SPEC 70121
  EVSE->>CSMS: status, transaction, meter, command exchange
  Note over EVSE,CSMS: OCPP
  CSMS->>BF: domain-safe session, status, meter, fault, and command events

Boundary Rules¶

Do not treat a protocol message as the domain model.
Map protocol data to the two coordinates before designing a feature: problem domain and physical anchor.
Keep standard version, vendor deviations, certificates, and transport details at the adapter or protocol boundary unless they are the product concern.
Use anti-corruption adapters when a standard uses a different identity model than BetterFleet.
Preserve lineage from raw standard payload to domain event, projection, report, and commercial record.
If a standard can command power or access, include Resilience & Security in the review even when the main domain is Smart Charging, Energy, or Roaming.