[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ocpp] Re: Old OCPP 2.0 RC2 Time Zones description
Hi Robert,
This is the statement we added in OpenADR for time zone support, and it can be along the similar lines.
-- The time, date, or date and time MUST be specified using [ISO8601] utc-time (also called zulu time)
Hi Bill,
As promised, hereby the text for Time as defined in the old OCPP 2.0 RC2 document.
1.1 Time Zones & Daylight Saving Time
1.1.1 Time Zones
To improve interoperability between Central Systems and Charge Points all time values SHOULD be exchanged as UTC, with the time zone designator ‘Z’, as specified by ISO 8601.
For the purpose of displaying local time on a charge point’s display, the device model’s Clock component supports specifying a time offset between Central System time (UTC or otherwise) and local time at the Charge Point.
1.1.2 Daylight Saving Time
To support punctual automated bi-annual changeover between “standard time” and “daylight saving time” periods, the device model supports configuration values of the Clock component that allow transitions between “standard” and “daylight saving” time periods to be automated by specifying a “next” transition date-time and a corresponding “next” time offset.
Kind regards,
Robert de Leeuw
IHomer
Hoge Ham 855104 JC Dongen
John F. Kennedylaan 35555 XC Valkenswaard
T: +31 6 2857 2123
E: robert.de.leeuw@ihomer.nl
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]