enen
Ongoing project

Acceptance criteria OCPP – HEMS side of the OCPP “Light” Connector

Below, the acceptance criteria for the needed functionality is listed per protocol.

Acceptance criteria OCPP – HEMS side of the OCPP “Light” Connector

  1. Supports sending the following OCPP message:
    1. SetChargingProfile
    2. ClearChargingProfile
  2. Supports receiving and handling the following messages:
    1. BootNotification
    2. Metervalue
  3. Able to address individual charge points by ID
  4. Gracefully handles status updates and failure reports

Acceptance criteria regular OCPP controller

  1. Supports OCPP 1.6j, 2.0.1, and/or 2.1 depending on configuration
  2. Accepts and interprets HEMS-issued TxProfile or SetChargingProfile messages
  3. Applies local profiles without violating active CPO profiles
  4. Aggregates metering values from connected EVSE unit
  5. Performs local power allocation based on available headroom
  6. Ensures total site consumption remains within CPOimposed envelope
  7. Emulates one or more virtual charge points to the upstream HEMS
  8. Supports seamless fallback to CPO-only control if local control fails