Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
4.6.4.2 — Billing Calendar
4 technical records havebeen identified at this reference: 4 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.
GSMESRV touchpoint
Documented touchpoints
Typed relationships supported by source mapping rows.
Linked SRVs
Unique retained services reached through exact control rows.
Linked alerts
Explicit requirement-to-alert references.
SMETS4.6.4.2 · item Non-DisablementCalendar.activateNextDateTime
Non-DisablementCalendar - activateNextDateTime
If not high values(0xFF), the date-time at which the corresponding 'Next' parameters shall be used to overwrite the corresponding 'Current' attributes
- Object
Non-DisablementCalendar- Attribute / method
activateNextDateTime- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- If not high values(0xFF), the date-time at which the corresponding 'Next' parameters shall be used to overwrite the corresponding 'Current' attributes
Documented touchpoints
- ConfiguresGCS05
0x006FGSMESRV 2.1
SMETS4.6.4.2 · item BillingCalendar.startDateTimeAndLongerPeriodicity
BillingCalendar - startDateTimeAndLongerPeriodicity
The date-time of the first billing calendar snapshot and the periodicity of following ones after that (where periodicity can be daily, weekly, monthly, quarterly, six monthly or yearly if being set, or all periodicities if being read). A start date-time of 29th, 30th or 31st of month should not be used.
- Object
BillingCalendar- Attribute / method
startDateTimeAndLongerPeriodicity- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- The date-time of the first billing calendar snapshot and the periodicity of following ones after that (where periodicity can be daily, weekly, monthly, quarterly, six monthly or yearly if being set, or all periodicities if being read). A start date-time of 29th, 30th or 31st of month should not be used.
Documented touchpoints
- ConfiguresGCS25a
0x00D8GSMESRV 6.8
SMETS4.6.4.2 · item BillingCalendar.startDateTimeAndAnyPeriodicity
BillingCalendar - startDateTimeAndAnyPeriodicity
The date-time of the first billing calendar snapshot and the periodicity of following ones after that
- Object
BillingCalendar- Attribute / method
startDateTimeAndAnyPeriodicity- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The date-time of the first billing calendar snapshot and the periodicity of following ones after that
Documented touchpoints
- ReadsGCS21k
0x00DAGSMESRV 6.2.3
SMETS4.6.4.2 · item BillingCalendar.startDateTimeAndPeriodicity
BillingCalendar - startDateTimeAndPeriodicity
The date-time of the first billing calendar snapshot and the periodicity of following ones after that (where periodicity can be 1=daily; 2=weekly and 3=monthly). Monthly periodicity and a start date-time of 29th, 30th or 31st of month should not be used.
- Object
BillingCalendar- Attribute / method
startDateTimeAndPeriodicity- Interface disposition
- E
- Category
- Configuration data
- Section 20 meaning
- The date-time of the first billing calendar snapshot and the periodicity of following ones after that (where periodicity can be 1=daily; 2=weekly and 3=monthly). Monthly periodicity and a start date-time of 29th, 30th or 31st of month should not be used.
Documented touchpoints
- ConfiguresGCS25
0x007EGSMESRV 6.8
How to read this page
Evidence is kept at record level
A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.