Version 1: Release Note 28 November 2014


ESME requirements for using Special Days objects



Download 4.8 Mb.
Page89/258
Date03.04.2021
Size4.8 Mb.
1   ...   85   86   87   88   89   90   91   92   ...   258

ESME requirements for using Special Days objects


When applying Blue Book special days related requirements to a Calendar / Scheduler object listed in Table 7.3.10, an ESME shall use the corresponding Specials Days Object in Table 7.3.10.



Calendar / Scheduler object

Special Days Object to be used

SMETS Reference

Class ID

OBIS

OBIS

TariffSwitchingTable(SpecialDays)

20

0-0:13.0.0.255

0-0:11.0.0.255

TariffSwitchingTable(SecondaryElement)(SpecialDays)

20

0-0:13.0.1.255

0-0:11.0.1.255

Non-DisablementCalendar(SpecialDays)

10

0-0:12.0.1.255

0-0:11.0.2.255

AuxiliaryLoadControlSwitchesCalendar(SpecialDays)

10

0-0:12.0.2.255

0-0:11.0.3.255

Table 7.3.10: Special Days Object
    1. Device requirements – ZSE


This Section 7.4 details the ZigBee clusters, attributes and commands that shall be supported by Devices in their interactions with other Devices on the same HAN, including whether the support is as a ZSE client or a server. Note, this section does not detail the ZCL / ZSE commands that Devices will need to process as part of processing Remote Party Commands, or Commands sent by a PPMID to a GSME. Such requirements are detailed in Sections 18 and 19.

For clarity and as required by ZSE, all Devices shall support the Key Establishment Cluster as both Client and Server.

A GSME shall implement a ZSE Metering Device and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘GSME: Metering Device’.

A GPF shall implement a ZSE Metering Device and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘GPF: Metering Device (Gas Mirror Endpoint)’.

A GPF shall implement a ZSE Energy Services Interface and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘GPF: Energy Services Interface (Gas ESI Endpoint)’

A CHF shall implement a ZSE Remote Communications Device and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘CHF: Remote Communications Device (Remote Communications Endpoint)’.

An ESME which is not a Twin Element ESME shall implement a ZSE Energy Services Interface and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘ESME: Energy Services Interface (Electricity ESI Endpoint)’

An ESME which is a Twin Element ESME shall implement three ZSE Energy Services Interfaces:



  1. the first which shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘ESME: Energy Services Interface (Twin ESME aggregate ESI Endpoint)’;

  1. the second which, in relation to the primary measuring element, shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘ESME: Energy Services Interface (Twin ESME primary/secondary ESI Endpoint)’; and

  2. the third which, in relation to the secondary measuring element, shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘ESME: Energy Services Interface (Twin ESME primary/secondary ESI Endpoint)’.

A PPMID shall implement a ZSE In-Home Display and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘PPMID: In-Home Display’

An HCALCS shall implement a ZSE Load Control Device and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘HCALCS: Load Control Device’.

An HHT shall implement a ZSE Remote Communications Device and shall implement all the clusters, commands, attribute sets and attributes in Table 7.4 where column A is ‘HHT: Remote Communications Device’.

An IHD shall support the mandatory attributes of the Basic cluster and the other clusters, attributes and commands necessary to meet the SMETS requirements.

Where a row in Table 7.4 is required for a Device, that Device shall support the cluster, attribute or command specified in that row as client or server, as specified in column C (labelled ‘Client / Server’).

Support for clusters, commands, attribute sets and attributes shall be as defined in columns B (‘Cluster’), D (‘Command’), E (‘Attribute Set’) and F (‘Attribute’).

Note that the other columns in Table 7.4 are informative and for requirements traceability only.



Table 7.4: Device Requirements

  1. Directory: government -> uploads -> system -> uploads -> attachment data -> file
    file -> Remove this if sending to pagerunnerr Page Title Light Rail Security Recommended Best Practice
    file -> 8 Section 1 : Sport
    file -> Notice of exercise of additional powers of seizure under Sections 50 or 51 of the Criminal Justice and Police Act 2001
    file -> Home office circular 004/2014 Powers to search for and seize invalid travel documents in Schedule 8 to the Anti-social Behaviour, Crime and Policing Act 2014
    file -> Consultation on the Royal Parks and Other Open Spaces (Amendment) (No. 2) Regulations 2012
    file -> Crown copyright 2012
    file -> This is the Report to Government by the Film Policy Review Panel The brief
    file -> Impact Assessment (IA)
    file -> Dcms/Wolfson Museums and Galleries Improvement Fund a public-Private Partnership (2002-2010)


    Share with your friends:
1   ...   85   86   87   88   89   90   91   92   ...   258




The database is protected by copyright ©essaydocs.org 2020
send message

    Main page