UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

Service Reference Variant

3.2 · Restrict Access For Change Of Tenancy

Service details

Identifiers, rules, and applicability

Service reference
3.2
Service Reference Variant
3.2
DUIS section
3.8.13
Command variants
1, 2, 3
DUIS possible responses
AcknowledgementService Response from Device - GBCSPayloadResponse to a Command for Local Delivery Request - LocalCommand FormatCountersigned SMETS1 Response
Critical
No
Sensitive response
No
Protection against replay
No
On demand
Yes
Future dated
DSP
DSP scheduled
No
DCC only
No
SMETS1 applicability
Yes
SAPC requirement
Optional
DUIS applicability
3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3

Cross-specification evidence

SMETS/CHTS to GBCS Mapping

This section shows the SMETS and CHTS attributes that can be read or written by the identified GBCS Use Case. Command requirements are shown separately from the mapped attributes.

ECS121 command0 attributes0x0022ESME

Command mapped to ECS12

No mapped data attributes.

GCS091 command0 attributes0x0072GPF

Command mapped to GCS09

No mapped data attributes.

Specific Errors

Response codes and descriptions

No specific validation is defined for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS120x0022
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISESME
Use Case / Message Code
GCS090x0072
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
GISGPF

DUIS Service Definition

Data items and DCC processing

Request data items

Table 123: RestrictAccessForChangeOfTenancy (sr:RestrictAccessForChangeOfTenancy) data items
Data ItemDescription / ValuesTypeMandatoryDefaultUnits
ExecutionDateTimeA User shall only add this Data Item to the Service Request where they require the Service Request to be executed at a future date and time. The UTC date and time the User requires the command to be executed on the Device ID Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time
RestrictionDateTimeThe UTC date and time the User requires the restriction to be applied from (so no personal data held in the device for a period prior to this date and time will be available over the HAN / via a User Interface) Valid date-timexs:dateTime (Wildcards not permitted)YesNoneUTC Date-Time

Additional System Processing - DUIS

Upon successful execution of a RestrictAccessForChangeOfTenancy Service Request, the DCC shall, for the specified DeviceID (for a Gas Proxy Function, Schedules on the associated Gas Smart Meter will also be deleted) identified within the Service Request, perform the following actions.

  1. Delete all active DCC Schedules created by Other Users that are held within the DCC Systems and send a DCC Alert to the Schedule owner to inform them of their deletion.
  2. Delete all Future Dated (DSP) requests created by Other Users with future dated execution dates that have not been sent to the Device and send a DCC Alert to the orginal sender of the request

Message Patterns & Examples

Pattern explorer

Open Message Patterns →

SMETS1 Supporting Requirements

Device-model variations and equivalent steps

Review the Section 18 requirements and their applicability across the documented manufacturer, Device Type, model, and firmware profiles.

Open S1SR Requirements →