Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
5 technical records havebeen identified at this reference: 5 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.
Section 20 objects, attributes or methods at this source reference.
Typed relationships supported by source mapping rows.
Unique retained services reached through exact control rows.
Explicit requirement-to-alert references.
SMETS5.7.5.38 · item AuxiliaryController[1].typeAndIdentifier
The value returned shall be determined by the type of Auxiliary Controller the Device has associated with Auxiliary Controller [1]: 1. The empty string if there is no associated Auxiliary Controller; 2. 0xFF if there is an associated APC; 3. 0x0000000000000000 if there is an associated ALCS; and 4. the HCALCS Entity Identifier, as stored in the Device Log entry for this HCALCS, if there is an associated HCALCS. Note that an HCALCS's Entity Identifier can never be 0x0000000000000000 or 0xFF or the empty string, because it is an EUI-64 identifier.
AuxiliaryController[1]typeAndIdentifierDocumented touchpoints
0x011DESMESRV 7.15SMETS5.7.5.38 · item AuxiliaryController[2].typeAndIdentifier
The value returned shall be determined by the type of Auxiliary Controller the Device has associated with Auxiliary Controller [2]: 1. The empty string if there is no associated Auxiliary Controller; 2. 0xFF if there is an associated APC; 3. 0x0000000000000000 if there is an associated ALCS; and 4. the HCALCS Entity Identifier, as stored in the Device Log entry for this HCALCS, if there is an associated HCALCS. Note that an HCALCS's Entity Identifier can never be 0x0000000000000000 or 0xFF or the empty string, because it is an EUI-64 identifier.
AuxiliaryController[2]typeAndIdentifierDocumented touchpoints
0x011DESMESRV 7.15SMETS5.7.5.38 · item AuxiliaryController[3].typeAndIdentifier
The value returned shall be determined by the type of Auxiliary Controller the Device has associated with Auxiliary Controller [3]: 1. The empty string if there is no associated Auxiliary Controller; 2. 0xFF if there is an associated APC; 3. 0x0000000000000000 if there is an associated ALCS; and 4. the HCALCS Entity Identifier, as stored in the Device Log entry for this HCALCS, if there is an associated HCALCS. Note that an HCALCS's Entity Identifier can never be 0x0000000000000000 or 0xFF or the empty string, because it is an EUI-64 identifier.
AuxiliaryController[3]typeAndIdentifierDocumented touchpoints
0x011DESMESRV 7.15SMETS5.7.5.38 · item AuxiliaryController[4].typeAndIdentifier
The value returned shall be determined by the type of Auxiliary Controller the Device has associated with Auxiliary Controller [4]: 1. The empty string if there is no associated Auxiliary Controller; 2. 0xFF if there is an associated APC; 3. 0x0000000000000000 if there is an associated ALCS; and 4. the HCALCS Entity Identifier, as stored in the Device Log entry for this HCALCS, if there is an associated HCALCS. Note that an HCALCS's Entity Identifier can never be 0x0000000000000000 or 0xFF or the empty string, because it is an EUI-64 identifier.
AuxiliaryController[4]typeAndIdentifierDocumented touchpoints
0x011DESMESRV 7.15SMETS5.7.5.38 · item AuxiliaryController[5].typeAndIdentifier
The value returned shall be determined by the type of Auxiliary Controller the Device has associated with Auxiliary Controller [5]: 1. The empty string if there is no associated Auxiliary Controller; 2. 0xFF if there is an associated APC; 3. 0x0000000000000000 if there is an associated ALCS; and 4. the HCALCS Entity Identifier, as stored in the Device Log entry for this HCALCS, if there is an associated HCALCS. Note that an HCALCS's Entity Identifier can never be 0x0000000000000000 or 0xFF or the empty string, because it is an EUI-64 identifier.
AuxiliaryController[5]typeAndIdentifierDocumented touchpoints
0x011DESMESRV 7.15How to read this page
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.