SMETS requirement clause

5.7.4.7 — Billing Calendar

2 technical records havebeen identified at this reference: 2 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.

ESMESRV touchpoint
2

Atomic items

Section 20 objects, attributes or methods at this source reference.

3

Documented touchpoints

Typed relationships supported by source mapping rows.

3

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS5.7.4.7 · item BillingCalendar.startDateTimeAndLongerPeriodicity

BillingCalendar - startDateTimeAndLongerPeriodicity

SRV touchpoint

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

Evidence:source paragraph 1447, 1448Section 20 row 1963

SMETS5.7.4.7 · item TariffBlockCounterMatrix.dailyResetting

TariffBlockCounterMatrix - dailyResetting

SRV touchpoint

Specifies whether daily resetting of the ESME Tariff Block Counter Matrix is on or off.

Object
TariffBlockCounterMatrix
Attribute / method
dailyResetting
Interface disposition
E
Category
Configuration data
Section 20 meaning
Specifies whether daily resetting of the ESME Tariff Block Counter Matrix is on or off.

Documented touchpoints

Evidence:source paragraph 1447, 1448Section 20 row 1966

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.