SMETS requirement clause

5.26.2.1 — Boost Function Control [n]

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.

15

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.26.2.1 · item BoostFunctionControl[1].value

BoostFunctionControl[1] - value

SRV touchpoint

TRUE meaning the Boost Function is to control Auxiliary Controller [1], where those terms have their SMETS meanings. FALSE otherwise.

Object
BoostFunctionControl[1]
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
TRUE meaning the Boost Function is to control Auxiliary Controller [1], where those terms have their SMETS meanings. FALSE otherwise.

Documented touchpoints

Evidence:source paragraph 2185, 2186Section 20 row 13

SMETS5.26.2.1 · item BoostFunctionControl[2].value

BoostFunctionControl[2] - value

SRV touchpoint

TRUE meaning the Boost Function is to control Auxiliary Controller [2], where those terms have their SMETS meanings. FALSE otherwise.

Object
BoostFunctionControl[2]
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
TRUE meaning the Boost Function is to control Auxiliary Controller [2], where those terms have their SMETS meanings. FALSE otherwise.

Documented touchpoints

Evidence:source paragraph 2185, 2186Section 20 row 14

SMETS5.26.2.1 · item BoostFunctionControl[3].value

BoostFunctionControl[3] - value

SRV touchpoint

TRUE meaning the Boost Function is to control Auxiliary Controller [3], where those terms have their SMETS meanings. FALSE otherwise.

Object
BoostFunctionControl[3]
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
TRUE meaning the Boost Function is to control Auxiliary Controller [3], where those terms have their SMETS meanings. FALSE otherwise.

Documented touchpoints

Evidence:source paragraph 2185, 2186Section 20 row 15

SMETS5.26.2.1 · item BoostFunctionControl[4].value

BoostFunctionControl[4] - value

SRV touchpoint

TRUE meaning the Boost Function is to control Auxiliary Controller [4], where those terms have their SMETS meanings. FALSE otherwise.

Object
BoostFunctionControl[4]
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
TRUE meaning the Boost Function is to control Auxiliary Controller [4], where those terms have their SMETS meanings. FALSE otherwise.

Documented touchpoints

Evidence:source paragraph 2185, 2186Section 20 row 16

SMETS5.26.2.1 · item BoostFunctionControl[5].value

BoostFunctionControl[5] - value

SRV touchpoint

TRUE meaning the Boost Function is to control Auxiliary Controller [5], where those terms have their SMETS meanings. FALSE otherwise.

Object
BoostFunctionControl[5]
Attribute / method
value
Interface disposition
E
Category
Configuration data
Section 20 meaning
TRUE meaning the Boost Function is to control Auxiliary Controller [5], where those terms have their SMETS meanings. FALSE otherwise.

Documented touchpoints

Evidence:source paragraph 2185, 2186Section 20 row 17

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.