SMETS requirement clause

5.6.3.1 — Activate Emergency Credit

2 technical records havebeen identified at this reference: 1 Section 20 item and 1 explicit clause reference. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

ESMEAlert touchpoint onlySRV touchpoint
1

Atomic items

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

3

Documented touchpoints

Typed relationships supported by source mapping rows.

1

Linked SRVs

Unique retained services reached through exact control rows.

2

Linked alerts

Explicit requirement-to-alert references.

SMETS5.6.3.1 · item EmergencyCredit.method: select

EmergencyCredit - select

SRV touchpoint

Activate emergency credit if emergency credit can be activated.

Object
EmergencyCredit
Attribute / method
method: select
Interface disposition
E
Category
Method
Section 20 meaning
Activate emergency credit if emergency credit can be activated.

Documented touchpoints

Evidence:source paragraph 1233, 1234Section 20 row 1050

SMETS5.6.3.1 · item clause.5.6.3.1

Activate Emergency Credit

Alert touchpoint only

This source clause is explicitly referenced by the GBCS device alert table.

Category
Alert reference

Documented touchpoints

  • Alert touchpointESME0x8168Supply Disabled then Armed - Activate Emergency Credit triggered
  • Alert touchpointESME0x81ABEmergency Credit Activated
Evidence:source paragraph 1233, 1234

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.