Skip to content

VDV463

Overview

VDV463 defines a standard interface between a Charging and Load Management System (CMS) and upstream operational platforms such as Integrated Transport Control Systems (ITCS) or Depot / Fleet Management Systems (DMS/FMS). The goal is to let planners and dispatchers coordinate vehicles, schedules, and chargers without writing bespoke integrations.

flowchart LR
    subgraph UpstreamSystems
        A[ITCS Control System]
        B[BMS]
    end

    C[Charging and Load Management System]

    C -->|ProvideChargingInformation|UpstreamSystems
    UpstreamSystems -->|ProvideChargingRequests| C

Purpose

  • Provide a common language for exchanging charging plans, vehicle availability, and energy constraints between the CMS and upstream systems.
  • Enable interoperable, vendor-neutral integrations across depots, fleets, and control centers.
  • Support near real-time visibility so upstream systems can adapt dispatching decisions based on the charging situation, and the CMS can react to operational requests.

Communication Model

  • Bidirectional message flows: upstream systems send requests (for example charging orders or schedule updates) while the CMS sends status, telemetry, and confirmations.
  • Event-driven exchange: the standard models interactions as asynchronous messages grouped into sequences that cover key business processes such as vehicle arrival, charging allocation, and departure clearance.
  • Typed payloads: messages reference shared enumerations and schema definitions so both parties interpret states, commands, and constraints consistently.

Key Implementation Elements

  • Message Model: defines the structure for every request, response, notification, and event between the CMS and upstream systems.
  • Communication Sequences: document the choreography for typical operational scenarios, clarifying triggers, expected acknowledgements, and error handling paths.
  • AsyncAPI Specification: captures the publish/subscribe channels, message contracts, and payload schemas to guide interface implementation or code generation.
  • Enumerations and Schemas: provide the canonical value sets and JSON schema definitions required to validate payloads and align system behavior.

Getting Started

  1. Read the setup & communication overview: start with the connection guide and communication sequences to understand the lifecycle of a vehicle as it interacts with the depot and charging infrastructure.
  2. Inspect the message definitions: review the message model, enumeration types, and schema definitions so you know which fields are mandatory, optional, or constrained.
  3. Review the interface contract: use the AsyncAPI specification to generate or validate client/server stubs for your CMS or upstream system.

Contents