Open robogeek opened 7 months ago
Thank you for your input!
While we agree that a session might include multiple charging periods, because the intent of the session reporting specification is to provide reporting and compliance information that is easily consumable by a regulator or program administrator, we have chosen to simplify by requiring aggregated single-session metrics for the session reporting table. EVSPs and other charging data providers are responsible for aggregating the sub-session information they collect into session-level reporting metrics, including summing individual charging period durations into an overall charging duration metric.
A standard for collecting sub-session energy and power use metrics (interval data) is a planned extension to this specification.
Reading the Session data collection, isn't there a possibility of multiple periods of charging per session?
The specification says a charging session begins when the cord is plugged in, and ends when the plug is removed. It is possible to turn the charging station on and off multiple times between those two points in time. This is alluded to in the discussion of the
charging_duration
field.This suggests there should be a field containing an array of
charge_start
charge_end
duration
Maybe some other fields like
energy_kwh
,peak_kw
,fee_charged
, andenergy_fee
could be in this array.Then, existing fields would be an aggregation of the values in the detailed array.