SMETS requirement clause

5.7.5.38 — Auxiliary Controller [n] Type

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.

ESMESRV touchpoint
5

Atomic items

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

5

Documented touchpoints

Typed relationships supported by source mapping rows.

1

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

SMETS5.7.5.38 · item AuxiliaryController[1].typeAndIdentifier

AuxiliaryController[1] - typeAndIdentifier

SRV touchpoint

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.

Object
AuxiliaryController[1]
Attribute / method
typeAndIdentifier
Interface disposition
E
Category
Operational data
Section 20 meaning
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.

Documented touchpoints

Evidence:source paragraph 1640, 1641Section 20 row 1830

SMETS5.7.5.38 · item AuxiliaryController[2].typeAndIdentifier

AuxiliaryController[2] - typeAndIdentifier

SRV touchpoint

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.

Object
AuxiliaryController[2]
Attribute / method
typeAndIdentifier
Interface disposition
E
Category
Operational data
Section 20 meaning
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.

Documented touchpoints

Evidence:source paragraph 1640, 1641Section 20 row 1831

SMETS5.7.5.38 · item AuxiliaryController[3].typeAndIdentifier

AuxiliaryController[3] - typeAndIdentifier

SRV touchpoint

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.

Object
AuxiliaryController[3]
Attribute / method
typeAndIdentifier
Interface disposition
E
Category
Operational data
Section 20 meaning
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.

Documented touchpoints

Evidence:source paragraph 1640, 1641Section 20 row 1832

SMETS5.7.5.38 · item AuxiliaryController[4].typeAndIdentifier

AuxiliaryController[4] - typeAndIdentifier

SRV touchpoint

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.

Object
AuxiliaryController[4]
Attribute / method
typeAndIdentifier
Interface disposition
E
Category
Operational data
Section 20 meaning
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.

Documented touchpoints

Evidence:source paragraph 1640, 1641Section 20 row 1833

SMETS5.7.5.38 · item AuxiliaryController[5].typeAndIdentifier

AuxiliaryController[5] - typeAndIdentifier

SRV touchpoint

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.

Object
AuxiliaryController[5]
Attribute / method
typeAndIdentifier
Interface disposition
E
Category
Operational data
Section 20 meaning
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.

Documented touchpoints

Evidence:source paragraph 1640, 1641Section 20 row 1834

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.