SMETS requirement clause

5.29.1.1 — Limit APC [n] Level

18 technical records havebeen identified at this reference: 17 Section 20 items 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
17

Atomic items

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

19

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.29.1.1 · item LimitAPC[n]LevelCommandProcessed.apcLimitPeriodEnd

LimitAPC[n]LevelCommandProcessed - apcLimitPeriodEnd

Alert touchpoint only

The date-time for the end of the APC [n] Limit Period, which its SMETS meaning

Object
LimitAPC[n]LevelCommandProcessed
Attribute / method
apcLimitPeriodEnd
Interface disposition
E
Category
Alert
Section 20 meaning
The date-time for the end of the APC [n] Limit Period, which its SMETS meaning

Documented touchpoints

  • Alert touchpointECS1010x0121ESME0x8F86ECS101 Limit APC [n] Level Command processed
Evidence:source paragraph 2203, 2204Section 20 row 1977

SMETS5.29.1.1 · item LimitAPC[n]LevelCommandProcessed.apcLimitPeriodStart

LimitAPC[n]LevelCommandProcessed - apcLimitPeriodStart

Alert touchpoint only

The date-time for the start of the APC [n] Limit Period, which its SMETS meaning

Object
LimitAPC[n]LevelCommandProcessed
Attribute / method
apcLimitPeriodStart
Interface disposition
E
Category
Alert
Section 20 meaning
The date-time for the start of the APC [n] Limit Period, which its SMETS meaning

Documented touchpoints

  • Alert touchpointECS1010x0121ESME0x8F86ECS101 Limit APC [n] Level Command processed
Evidence:source paragraph 2203, 2204Section 20 row 1978

SMETS5.29.1.1 · item LimitAPC[n]LevelCommandProcessed.apcDirectionAndNumber

LimitAPC[n]LevelCommandProcessed - apcDirectionAndNumber

Alert touchpoint only

The most significant nibble of the octet shall be 0x1 (indicating output), or 0x2 (indicating input) and the least significant shall be 0xn, where n is the value in APC [n] and APC [n] is the APC affected, so a value between 1 and 5 inclusive.

Object
LimitAPC[n]LevelCommandProcessed
Attribute / method
apcDirectionAndNumber
Interface disposition
E
Category
Alert
Section 20 meaning
The most significant nibble of the octet shall be 0x1 (indicating output), or 0x2 (indicating input) and the least significant shall be 0xn, where n is the value in APC [n] and APC [n] is the APC affected, so a value between 1 and 5 inclusive.

Documented touchpoints

  • Alert touchpointECS1010x0121ESME0x8F86ECS101 Limit APC [n] Level Command processed
Evidence:source paragraph 2203, 2204Section 20 row 1979

SMETS5.29.1.1 · item LimitAPC[n]LevelCommandProcessed.resultingLevel

LimitAPC[n]LevelCommandProcessed - resultingLevel

Alert touchpoint only

The value 'p' where this Alert relates to output, or 'q' where it relates to input, where 'p' and 'q' are as per GBCS Section 7.3.6.1

Object
LimitAPC[n]LevelCommandProcessed
Attribute / method
resultingLevel
Interface disposition
E
Category
Alert
Section 20 meaning
The value 'p' where this Alert relates to output, or 'q' where it relates to input, where 'p' and 'q' are as per GBCS Section 7.3.6.1

Documented touchpoints

  • Alert touchpointECS1010x0121ESME0x8F86ECS101 Limit APC [n] Level Command processed
Evidence:source paragraph 2203, 2204Section 20 row 1980

SMETS5.29.1.1 · item LimitAPC[n]LevelEndedOrCancelled.apcDirectionAndNumber

LimitAPC[n]LevelEndedOrCancelled - apcDirectionAndNumber

Alert touchpoint only

The most significant nibble of the octet shall be 0x1 (indicating output) and the least significant shall be 0xn, where n is the value in APC [n] and APC [n] is the APC affected, so a value between 1 and 5 inclusive.

Object
LimitAPC[n]LevelEndedOrCancelled
Attribute / method
apcDirectionAndNumber
Interface disposition
E
Category
Alert
Section 20 meaning
The most significant nibble of the octet shall be 0x1 (indicating output) and the least significant shall be 0xn, where n is the value in APC [n] and APC [n] is the APC affected, so a value between 1 and 5 inclusive.

Documented touchpoints

  • Alert touchpointECS1020x0122ESME0x8F87ECS102 Limit APC [n] Level ended or cancelled
Evidence:source paragraph 2203, 2204Section 20 row 1981

SMETS5.29.1.1 · item LimitAPC[n]LevelEndedOrCancelled.resultingLevel

LimitAPC[n]LevelEndedOrCancelled - resultingLevel

Alert touchpoint only

The value 'p' where this Alert relates to output, or 'q' where it relates to input, where 'p' and 'q' are as per GBCS Section 7.3.6.1

Object
LimitAPC[n]LevelEndedOrCancelled
Attribute / method
resultingLevel
Interface disposition
E
Category
Alert
Section 20 meaning
The value 'p' where this Alert relates to output, or 'q' where it relates to input, where 'p' and 'q' are as per GBCS Section 7.3.6.1

Documented touchpoints

  • Alert touchpointECS1020x0122ESME0x8F87ECS102 Limit APC [n] Level ended or cancelled
Evidence:source paragraph 2203, 2204Section 20 row 1982

SMETS5.29.1.1 · item AuxiliaryProportionalController[1].limitPeriodStartDateTime

AuxiliaryProportionalController[1] - limitPeriodStartDateTime

SRV touchpoint

The value in this field shall be the start date-time of the APC [1] Limit Period if Auxiliary Controller [1] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 1 and shall never be present otherwise.

Object
AuxiliaryProportionalController[1]
Attribute / method
limitPeriodStartDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the start date-time of the APC [1] Limit Period if Auxiliary Controller [1] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 1 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1983

SMETS5.29.1.1 · item AuxiliaryProportionalController[2].limitPeriodStartDateTime

AuxiliaryProportionalController[2] - limitPeriodStartDateTime

SRV touchpoint

The value in this field shall be the start date-time of the APC [2] Limit Period if Auxiliary Controller [2] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 2 and shall never be present otherwise.

Object
AuxiliaryProportionalController[2]
Attribute / method
limitPeriodStartDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the start date-time of the APC [2] Limit Period if Auxiliary Controller [2] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 2 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1984

SMETS5.29.1.1 · item AuxiliaryProportionalController[3].limitPeriodStartDateTime

AuxiliaryProportionalController[3] - limitPeriodStartDateTime

SRV touchpoint

The value in this field shall be the start date-time of the APC [3] Limit Period if Auxiliary Controller [3] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 3 and shall never be present otherwise.

Object
AuxiliaryProportionalController[3]
Attribute / method
limitPeriodStartDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the start date-time of the APC [3] Limit Period if Auxiliary Controller [3] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 3 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1985

SMETS5.29.1.1 · item AuxiliaryProportionalController[4].limitPeriodStartDateTime

AuxiliaryProportionalController[4] - limitPeriodStartDateTime

SRV touchpoint

The value in this field shall be the start date-time of the APC [4] Limit Period if Auxiliary Controller [4] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 4 and shall never be present otherwise.

Object
AuxiliaryProportionalController[4]
Attribute / method
limitPeriodStartDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the start date-time of the APC [4] Limit Period if Auxiliary Controller [4] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 4 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1986

SMETS5.29.1.1 · item AuxiliaryProportionalController[5].limitPeriodStartDateTime

AuxiliaryProportionalController[5] - limitPeriodStartDateTime

SRV touchpoint

The value in this field shall be the start date-time of the APC [5] Limit Period if Auxiliary Controller [5] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 5 and shall never be present otherwise.

Object
AuxiliaryProportionalController[5]
Attribute / method
limitPeriodStartDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the start date-time of the APC [5] Limit Period if Auxiliary Controller [5] is an APC; otherwise it shall have no meaning. This field shall always be present where the 'controllerNumber' specified in the Command is 5 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1987

SMETS5.29.1.1 · item AuxiliaryProportionalController[1].limitPeriodEndDateTime

AuxiliaryProportionalController[1] - limitPeriodEndDateTime

SRV touchpoint

The value in this field shall be the end date-time of the APC [1] Limit Period if Auxiliary Controller [1] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 1 and shall never be present otherwise.

Object
AuxiliaryProportionalController[1]
Attribute / method
limitPeriodEndDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the end date-time of the APC [1] Limit Period if Auxiliary Controller [1] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 1 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1988

SMETS5.29.1.1 · item AuxiliaryProportionalController[2].limitPeriodEndDateTime

AuxiliaryProportionalController[2] - limitPeriodEndDateTime

SRV touchpoint

The value in this field shall be the end date-time of the APC [2] Limit Period if Auxiliary Controller [2] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 2 and shall never be present otherwise.

Object
AuxiliaryProportionalController[2]
Attribute / method
limitPeriodEndDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the end date-time of the APC [2] Limit Period if Auxiliary Controller [2] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 2 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1989

SMETS5.29.1.1 · item AuxiliaryProportionalController[3].limitPeriodEndDateTime

AuxiliaryProportionalController[3] - limitPeriodEndDateTime

SRV touchpoint

The value in this field shall be the end date-time of the APC [3] Limit Period if Auxiliary Controller [3] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 3 and shall never be present otherwise.

Object
AuxiliaryProportionalController[3]
Attribute / method
limitPeriodEndDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the end date-time of the APC [3] Limit Period if Auxiliary Controller [3] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 3 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1990

SMETS5.29.1.1 · item AuxiliaryProportionalController[4].limitPeriodEndDateTime

AuxiliaryProportionalController[4] - limitPeriodEndDateTime

SRV touchpoint

The value in this field shall be the end date-time of the APC [4] Limit Period if Auxiliary Controller [4] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 4 and shall never be present otherwise.

Object
AuxiliaryProportionalController[4]
Attribute / method
limitPeriodEndDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the end date-time of the APC [4] Limit Period if Auxiliary Controller [4] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 4 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1991

SMETS5.29.1.1 · item AuxiliaryProportionalController[5].limitPeriodEndDateTime

AuxiliaryProportionalController[5] - limitPeriodEndDateTime

SRV touchpoint

The value in this field shall be the end date-time of the APC [5] Limit Period if Auxiliary Controller [5] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 5 and shall never be present otherwise.

Object
AuxiliaryProportionalController[5]
Attribute / method
limitPeriodEndDateTime
Interface disposition
E
Category
Configuration data
Section 20 meaning
The value in this field shall be the end date-time of the APC [5] Limit Period if Auxiliary Controller [5] is an APC; otherwise it shall have no meaning. The Device shall, before updating this DLMS attribute, check that the limitPeriodEndDateTime is greater than the corresponding limitPeriodStartDateTime and is no more than 24 hours greater than the corresponding limitPeriodStartDateTime. If this check fails, the Device shall not update this DLMS attribute, and shall, in the Response, return corresponding Data-Access-Result / Action-Result values of other-reason for this and subsequent DLMS instructions in the Command. This field shall always be present where the 'controllerNumber' specified in the Command is 5 and shall never be present otherwise.

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1992

SMETS5.29.1.1 · item AuxiliaryProportionalController[n].method: controllerNumberAndCommandedState

AuxiliaryProportionalController[n] - controllerNumberAndCommandedState

SRV touchpoint

See GBCS Section 7.3.6.1

Object
AuxiliaryProportionalController[n]
Attribute / method
method: controllerNumberAndCommandedState
Interface disposition
E
Category
Method
Section 20 meaning
See GBCS Section 7.3.6.1

Documented touchpoints

Evidence:source paragraph 2203, 2204Section 20 row 1993

SMETS5.29.1.1 · item clause.5.29.1.1

Limit APC [n] Level

Alert touchpoint only

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

Category
Alert reference

Documented touchpoints

  • Alert touchpointESME0x8F86ECS101 Limit APC [n] Level Command processed
  • Alert touchpointESME0x8F87ECS102 Limit APC [n] Level ended or cancelled
Evidence:source paragraph 2203, 2204

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.