DCC User Gateway Interface Design Specification. Annex - Service Request Definitions 4 Reading Service

Transcription

1 DCC User Gateway Interface Design Specification Formatted: Space Before: 0 pt, After: 0 pt Annex - Service Request Definitions 4 Reading Service Author: DCC Version: v0.8 Draft Date: 12 th September 2014 Page 1 of 239

2 Contents 4 Reading Service (4 RS) Read Instantaneous Import Registers (4.1) Read Instantaneous Import Registers (4.1.1) Read Instantaneous Import TOU Matrices (4.1.2) Read Instantaneous Import TOU With Blocks Matrices (4.1.3) Read Instantaneous Import Block Counters (4.1.4) Read Instantaneous Export Registers (4.2) Service Request Responses Read Instantaneous Prepay Values (4.3) Service Request Responses Retrieve Billing Data Log (4.4) Retrieve Debt And Credit Billing Data Log (4.4.1) Retrieve Change Of Mode / Tariff Triggered Billing Data Log (4.4.2) Retrieve Billing Calendar Triggered Billing Data Log (4.4.3) Retrieve Billing Data Log (Payment Based Debt Payments) (4.4.4) Retrieve Billing Data Log (Prepayment Credits) (4.4.5) Section Retrieve Daily Read Log (4.6) Retrieve Import Daily Read Log (4.6.1) Retrieve Export Daily Read Log (4.6.2) Section Read Profile Data (4.8) Read Active Import Profile Data (4.8.1) Read Reactive Import Profile Data (4.8.2) Read Export Profile Data (4.8.3) Section Read Network Data (4.10) Service Request Page 2 of 239

3 Responses Read Tariff (4.11) Read Tariff (Primary Element) (4.11.1) Read Tariff (Secondary Element) (4.11.2) Read Maximum Demand Registers (4.12) Read Maximum Demand Import Registers (4.12.1) Read Maximum Demand Export Registers (4.12.2) Read Prepayment Configuration (4.13) Service Request Responses Read Prepayment Daily Read Log (4.14) Service Request Responses Read Load Limit Counter (4.15) Service Request Responses Read Active Power Import (4.16) Service Request Responses Retrieve Daily Consumption Log (4.17) Service Request Responses Read Meter Balance for Credit Mode Smart Meter (4.18) Service Request Responses Page 3 of 239

4 4 Reading Service (4 RS) This section sets out the full content of the DCC Reading Service by providing the overarching service content that includes: service requestsrequest and response message types, data content items and User access roles. Service Name Reading Service Id 4 To allow enable a DCC Service User to retrieve an entry from: Service Objective the Billing Data Log the Daily Read Log Daily Consumption Log the Network Data Log the Profile Data Log the Average RMS Profile Data Log Prepayment configuration and register values Average RMS Over Voltage Counter Average RMS Under Voltage Counter Cumulative and Historical Value Store Maximum Demand Active Energy Import Value Maximum Demand (Configurable Time) Active Energy Import Value Maximum Demand Active Energy Export Value or, to read the import or export register values at a point in time, of a specific device associated to a specified device ID, such that the DCC Service User can obtain Electricity or Gas Smart Metering Equipment consumption and usage details and confirm that the operation has either completed or receive the reason for its failure. NB where a Service Request response returns a Log or data structure, parts of the data may be classified as sensitive data. Business Context Statement The DCC Service User requires the ability to be able to read and obtain Electricity or Gas meter register or log details at a specified device ID. The device may be an Electricity Smart Meter or Gas Smart Meter. / Gas Proxy Function. The following user roles have access to the list of service requests which make up the Reading Service: User Roles Electricity Import Supplier (EIS) Electricity Export Supplier (EES) Gas Import Supplier (GIS) Electricity Network Operator (ENO) Gas Network Operator (GNO) Other User (OU) Table 11 Overview of Reading Service The mapping between the Reading Services and the Devices they apply to is defined as follows: Page 4 of 239

5 DCC User Gateway Interface Design Specification Service Reference Service Reference Variant Name DevicesBusiness Target ID Read Instantaneous Import Registers Read Instantaneous Import TOU Matrices Read Instantaneous Import TOU With Blocks Matrices Read Instantaneous Import Block Counters Read Instantaneous Export Registers Read Instantaneous Prepay Values Retrieve Debt And Credit Billing Data Log Retrieve Change Of Mode / Tariff Triggered Billing Data Log Retrieve Billing Calendar Triggered Billing Data Log Retrieve Billing Data Log (Payment Based Debt Payments)Retrieve Billing Data Log (Gas) Retrieve Billing Data Log (Prepayment Credits) Retrieve Import Daily Read Log Retrieve Export Daily Read Log Read Active Import Profile Data Read Reactive Import Profile Data Read Export Profile Data Electricity Smart MeterEMSEESME, GPF, GSME Gas Smart MeterProxy Function Gas Smart Meter EMSEESME, GPF, GSMEElectricity Smart Meter Gas Smart MeterProxy Function Gas Smart Meter Electricity Smart MeterESME Gas Smart MeterProxy Function GPF, GSMEGas Proxy Function Gas Smart Meter ESMEElectricity Smart Meter EMSEESME, GPF, GSMEElectricity Smart Meter Gas Smart MeterProxy Function Gas Smart Meter Electricity Smart Meter ESME Gas Smart Meter EMSEESME, GPF, GSMEElectricity Smart Meter Gas Proxy Function Gas Smart Meter Gas Smart Meter EMSEESME, GPF, GSMEElectricity Smart Meter Gas Proxy Function Gas Smart Meter Gas Smart Meter GPF, GSMEGas Proxy Function Gas Smart Meter GPF, GSMEGas Proxy Function Gas Smart Meter EMSEESME, GPF, GSMEElectricity Smart Meter Gas Smart MeterProxy Function Gas Smart Meter Electricity Smart MeterESME EMSEESME, GPF, GSMEElectricity Smart Meter Gas Smart MeterProxy Function Gas Smart Meter ESMEElectricity Smart Meter ESMEElectricity Smart Meter Page 5 of 239 Formatted Table...

6 DCC User Gateway Interface Design Specification Service Reference Service Reference Variant Name DevicesBusiness Target ID Read Network Data Read Tariff (Primary Element) Read Tariff (Secondary Element) Read Maximum Demand Import Registers Read Maximum Demand Export Registers Read Prepayment Configuration Read Prepayment Daily Read Log Electricity Smart Meter Gas Smart MeterESME, GSME EMSEESME, GPF, GSMEElectricity Smart Meter Gas Smart MeterProxy Function Gas Smart Meter Electricity Smart MeterESME Electricity Smart MeterESME ESMEElectricity Smart Meter EMSEESME, GPF, GSMEElectricity Smart Meter Gas Smart MeterProxy Function Gas Smart Meter EMSEESME, GPF, GSMEElectricity Smart Meter Gas Smart MeterProxy Function Gas Smart Meter Formatted Table Read Load Limit Counter Read Active Power Import Retrieve Daily Consumption Log Read Meter Balance for Credit Mode Smart Meter Table 22 RS - Service Requests / Devices ESMEElectricity Smart Meter ESMEElectricity Smart Meter ESMEElectricity Smart Meter, GPFGas Smart MeterProxy Function EMSEESME, GPF, GSMEElectricity Smart Meter Gas Proxy Function Gas Smart Meter For each of the RS Service Requests supported by the DCC User Gateway, this section details: the reference to the appropriate section of the XML Schema (see XML Schema document 3 of this documentation set) the structure of each Service Request and Response with examples (if specific to the Service Request) if applicable, Service Request specific Validation and Response Codes This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set). 4.1 Read Instantaneous Import Registers (4.1) Service Request definition differs from that in the SEC2 Consultation to align with GBCS UCs, because thisthis Service Request maps to three Electricity and three Gas GBCS Use Cases and each Use Case requires its own Request ID. Page 6 of 239

7 Therefore the 4.1 Service Request has been broken into three four parts: (Registers) applicable to Electricity and Gas, (TOU Matrices) applicable to Electricity and Gas and, (TOU with Blocks Matrices) applicable to Electricity and (Block Counters) applicable to Gas Formatted: Font color: Text Read Instantaneous Import Registers (4.1.1) Service Request Name ReadInstantaneousImportRegisters Service Reference 4.1 Service Request Variant Name ReadInstantaneousImportRegisters Service Reference Variant Service Request Objective To allow enable a DCC Service User to obtain anread the instantaneous import energy register read on an electricity Electricity Smart or gas mmeteresme or Gas Proxy FunctionGPF / Smart MeterGSME. Business Context Statement The DCC Service User requires an immediate view of the current import register read values on an electricity Electricity Smart or gas mmeter or Gas Proxy Function / Smart Meter, e.g. to respond to a customer telephone enquiry Formatted Table User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Electricity Network Operator (ENO) Gas Network Operator (GNO) Security Classification Non-critical and sensitive (the request is non-sensitive and the device response register content is sensitive): GBCS XREF: SME.C.NC Page 7 of 239

8 1. The data items being read in this Service Request as defined by SMETS are the Active Import Register, Secondary Active Import Register and Reactive Import Register for the ESME and the Consumption Register for the GSME. All of these registers record cumulative Consumption on the device. 2. For reading the instantaneous import energy registers values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not avialableavailable for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users.Users. Service Request Narrative 1.3. This Service Request returns all the Import Energy Registers available at the meter MeterESME or / Gas Proxy FunctiGPF/GSMEon. It isn t possible to request a subset of them. Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS and GIS. 4. This Service Request if targeted to (Gas Devices (GPF/GSME)) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. This means that any subsequent sequenced command could not be sent by the DCC as the success of the preceedingpreceding Service Request Request can notcannot be established Because this Service Request returns data, URPs to the target Devioce (i.e. the Gas Network Operator, if the Device Type is Gas Smart Meter), have to include in the Service Request the Public Security Credentials they want the Device to sign the Response with. Formatted Table Formatted: Font: Not Italic, Font color: Auto Table 33 Read Instantaneous Import Registers Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its ReadInstantaneousImportRegisters XML element defines this Service Request and doesn t contain any data itemsonly contains the Key Agreement Public Security Credentials when the User Role is GNO and the Device Type Gas Smart Meter. Page 8 of 239

9 Formatted: Font: Italic, Font color: Blue Figure 1 Read Instantaneous Import Registers Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime KAPublicSecurityCr edentials KAPublicSecurityCr edentials The UTC date and time the DCC Service User requires the command to be executed on the device. Valid date-time in the futurethe Key Agreement Public Security Credentials (of the requesting partyuser) to be used where the request is from an Unknown Remote Party (i.e. Device Type = Gas Smart Meter and User Role = GNO) The Key Agreement Public Security Credentials (of the requesting user) to be used where the request is from an Unknown Remote Party (i.e. Device Type = Gas Smart Meter and User Role = GNO) xs:datexs:base64binary NoUser Role = GNO and Device Type = Gas Smart MeterGSME : Yes Otherwise: N/A xs:base64binary User Role = GNO and Device Type = GSME: Yes Otherwise: N/A N/ANon e Table 44 Read Instantaneous Import Registers Service Request Data Items UTC Date- TimeN/ A None N/A Non- Non- Formatted: No bullets or numbering N on- Formatted: Bulleted + Level: 1 + Aligned at: 0.63 cm + Indent at: 1.27 cm Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No NoDSP No Table Read Instantaneous Import Registers Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Instantaneous Import Registers Command Variant Values Validation Page 9 of 239

10 This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks and Annex section 17.2 for KA Public Security Credentials validation Sample Request A sample body of a Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 10 of 239

11 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.1</ServiceReference> <ServiceReferenceVariant>4.1.1</ServiceReferenceVariant> </Header> <Body> <ReadInstantaneousImportRegisters/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure 2 Sample Read Instantaneous Import Registers Service Request Format Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Responses The Service rresponse messages for a Read Instantaneous Import Registers Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below. Page 11 of 239

12 Response & Alert Common Interface Format Format - ReadInstantaneousImportRegistersRsp Formatted: Heading 6 Formatted: Font: Arial, Not Bold, Font color: Auto Formatted: Keep with next Figure 3 - Read Instantaneous Import Registers Parse Response Structure Specific Header Data Items Formatted: Caption, Justified Formatted: Heading 6 Page 12 of 239

13 Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode GBCSUseCaseNumber ECS17b GCS13a GBCSUseCaseName Read ESME Energy Registers (Import Energy) Read GSME Consumption Register Table 77 - Read Instantaneous Import Registers Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Consumption Register Gas Only Value The total energy imported xs:integerdecimal None m 3 Unit Unit of measure m 3 xs:string m 3 N/A Non- ActiveImport Register Value Electricity Only The active energy imported, as measured by the measuring element(s) xs: decimalinteger None Wh ActiveEnergyUnit Unit of measure - Wh xs:string Wh N/A ReactiveImport Register Value Electricity Only The reactive energy imported, as measured by the measuring element xs: decimalinteger None varh ReactiveEnergyUnit Unit of measure - VARh xs:string varh N/A SecondaryActiveI mportregister Value Electricity Only The active energy imported, as measured by the secondary measuring element xs: decimalinteger None Wh ActiveEnergyUnit Unit of measure - wh xs:string Wh N/A Table 88 - Read Instantaneous Import Registers Parse Response Body Data Items Figure 4 - Read Instantaneous Import Registers Parse Response Specific Data Items Sample Response Formatted: Keep with next Formatted: Caption Formatted: Heading 6 Page 13 of 239

14 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>27</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs17b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Energy Registers (Import Energy)</ra:GBCSUseCaseName> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readinstantaneousimportregistersrsp MessageSuccess="true"> <ra:electricity> <ra:activeimportregister> <ra:value>10.1</ra:value> <ra:activeenergyunit>wh</ra:activeenergyunit> </ra:activeimportregister> <ra:reactiveimportregister> <ra:value>20.2</ra:value> <ra:reactiveenergyunit>varh</ra:reactiveenergyunit> </ra:reactiveimportregister> <ra:secondaryactiveimportregister> <ra:value>30.3</ra:value> <ra:activeenergyunit>wh</ra:activeenergyunit> </ra:secondaryactiveimportregister> </ra:electricity> </ra:readinstantaneousimportregistersrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Instantaneous Import Registers Parse Response Sample The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Formatted: Keep with next Formatted: Caption Formatted: Font: Not Bold, Font color: Auto Read Instantaneous Import TOU Matrices (4.1.2) Service Request Name ReadInstantaneousImportRegisters Service Reference 4.1 Service Request Variant Name ReadInstantaneousImportTOUMatrices Service Reference Variant Service Request Objective To allow enable a DCC Service User to obtain an instantaneous import TOU (time of use) matrix read on an electricity Electricity Smart mmeter or gas Gas meterpproxy ffunctiion / Gas Smart Meter. Formatted Table Business Context Statement The DCC Service User requires an immediate view of the current import TOU matrix read values on an electricity Electricity Smart or gas mmeter or Gas Proxy Function / Smart Meter, e.g. to respond to a customer telephone enquiry Page 14 of 239

15 User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Security Classification Non-critical and sensitive (the request is non-sensitive and the device response matrix content is sensitive): GBCS XREF: SME.C.NC 1. The data items being read in this Service Request as defined by SMETS are the Tariff TOU Register Matrix, and Secondary Tariff TOU Register Matrix formatrix for the ESME and the Tariff TOU Register Matrix for the GSME. ESME Tariff TOU Register Matrix is defined in SMETS as a 1 x 48 matrix for storing Tariff Registers for Time-of-use Pricing Formatted: Indent: Left: 1.27 cm ESME Secondary Tariff TOU Register Matrix is defined in SMETS as a 1 x 4 matrix for storing Tariff Registers for Timeof-use Pricing relating to supply via the secondary measuring element of the Electricity Meter. GSME Tariff TOU Register Matrix is defined in SMETS as a 1 x 4 matrix for storing Tariff Registers for Time-of-use Pricing Service Request Narrative 1.2. This Service Request returns all the the Import TOU Matrices available at the meter Meter / Gas Proxy Function in full. It isn t possible to request a subset of them. Service Reference Grouping is applicable to this Service Request Variant for User Role EIS and GIS. 3. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. This means that any subsequent sequenced command could not be sent by the DCC as the success of the preceedingpreceding Service Request Request can notcannot be established. Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Formatted: Font: Not Italic, Font color: Text 1 Formatted: Font color: Text For reading the instantaneous import TOU matrices values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not available for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users Table Read Instantaneous Import TOU Matrices Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its ReadInstantaneousImportTOUMatrices XML element defines this Service Request and doesn t contain any data items. Page 15 of 239

16 Formatted: Font: Arial, 8 pt, Bold, Font color: Auto Figure Read Instantaneous Import TOU Matrices Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the device. Valid date-time in the future xs:date No N/A UTC Date- Time Table Read Instantaneous Import TOU Matrices Service Request Data Items Non- Formatted: Caption Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSPNo No Table Read Instantaneous Import TOU Matrices Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Instantaneous Import TOU Matrices Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 16 of 239

17 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.1</ServiceReference> <ServiceReferenceVariant>4.1.2</ServiceReferenceVariant> </Header> <Body> <ReadInstantaneousImportTOUMatrices/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Instantaneous Import TOU Matrices Service Request Format Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Rresponse messages for a Read Instantaneous Import TOU Matrices rrequest follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below. Page 17 of 239

18 Response & Alert Common Interface Format Format - - ReadInstantaneousImportTOUMatricesRsp Formatted: Heading 6 Formatted: Font: Arial, Not Bold, Font color: Auto Formatted: Keep with next Figure Read Instantaneous Import TOU Matrices Parse Response Structure Specific Header Data Items Formatted: Caption, Justified Formatted: Heading 6 Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode B6 GBCSUseCaseNumber ECS17d GCS13c GBCSUseCaseName Read ESME Energy Register (TOU) Read GSME Register (TOU) Table Read Instantaneous Import TOU Matrices Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table TOURegisterMatrixV alue Accumulated consumption for each TOU rate register. Gas Only xs: decimalinteger None M 3 Unit Unit of Measure Gas Only xs:string m3 N/A Non- TOUPrimaryRegiste rvalue Tariff Registers for Time-of-use Pricing Electricity Only xs: decimalinteger None Wh Formatted Table Page 18 of 239

19 Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table TOUSecondRegister Value Tariff Registers for Time-of-use Pricing for the secondary element Electricity Only Optional xs: decimalinteger None Wh Table Read Instantaneous Import TOU Matrices Parse Response Body Data Items Figure 9 - Read Instantaneous Import TOU Matrices Parse Response Specific Data Items Sample Response body <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>b6</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs13c</ra:gbcsusecasenumber> <ra:gbcsusecasename>read GSME Register (TOU)</ra:GBCSUseCaseName> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readinstantaneousimporttoumatricesrsp MessageSuccess="true"> <ra:gas> <ra:tarifftouregistermatrix> <ra:touregistermatrixvalue index="1">10.1</ra:touregistermatrixvalue> <ra:touregistermatrixvalue index="2">20.2</ra:touregistermatrixvalue> <ra:touregistermatrixvalue index="3">30.3</ra:touregistermatrixvalue> <ra:touregistermatrixvalue index="4">40.4</ra:touregistermatrixvalue> <ra:unit>m3</ra:unit> </ra:tarifftouregistermatrix> </ra:gas> </ra:readinstantaneousimporttoumatricesrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Instantaneous Import TOUou Matrices Parse Response Sample The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Read Instantaneous Import TOU With Blocks Matrices (4.1.3) Service Request Name Service Reference 4.1 Service Request Variant Name Service Reference Variant ReadInstantaneousImportRegisters ReadInstantaneousImportTOUWithBlocksMatrices Formatted: Keep with next Formatted: Caption Formatted: Heading 6 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: Arial, 8 pt, Not Bold Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: Arial, 8 pt, Not Bold Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: Arial, 8 pt, Not Bold Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: Arial, 8 pt, Not Bold Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: Not Bold Formatted: Font: (Default) Arial, 8 pt, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Font color: Text 1 Formatted: Caption Formatted: Font: Not Bold, Font color: Auto Page 19 of 239

20 Service Request Objective To allow enable a DCC Service User to obtain anread the instantaneous import TOU with Block s Register matrix read on an electricity Electricity Smart or gas mmeter or Gas Proxy Function. Business Context Statement The DCC Service User requires an immediate view of the current import TOU with Blocks matrix read values on an electricity Electricity Smart or gas mmeter or Gas Proxy Function, e.g. to respond to a customer telephone enquiry User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Security Classification Non-critical and sensitive (the request is non-sensitive and the device response matrix content is sensitive): GBCS XREF: SME.C.NC 1. The data items being read in this Service Request, as defined by SMETS, are the Tariff TOU Block Register Matrix andmatrix and Tariff Block Counter Matrix for the ESME. Service Request Narrative Tariff TOU Block Register Matrix, as defined in SMETS, is a 4 x 8 matrix for storing Tariff Registers for Timeof-use with Block Pricing. Tariff Block Counter Matrix, as defined in SMETS, is a 4 x 8 matrix for storing Block Counters for Block Pricing. This Service Request returns all the the Import TOU with Blocks Matrices available at the meter Meter/ Gas Proxy Function in full. It isn t possible to request a subset of them. 2. Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS and GIS. Table Read Instantaneous Import TOU With Blocks Matrices Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set). Formatted: None, Indent: Left: 1.27 cm, No bullets or numbering, No page break before, Don't keep with next Formatted: List Paragraph, None, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font: Not Bold Formatted: List Paragraph, None, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its ReadInstantaneousImportTOUWithBlocksMatrices XML element defines this Service Request and doesn t contain any data items. Formatted: Font: 8 pt, Bold Figure Read Instantaneous Import TOU With Blocks Matrices Service Request Structure Formatted: Font color: Custom Color(RGB(41,35,92)) Page 20 of 239

21 Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the device. Valid date-time in the future xs:date No N/A UTC Date- Time Table Read Instantaneous Import TOU With Block Matrices Service Request Data Items Non Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSPNo No Table Read Instantaneous Import TOU With Blocks Matrices Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Validation CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Instantaneous Import TOU With Blocks Matrices Command Variant Values This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 21 of 239

22 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.1</ServiceReference> <ServiceReferenceVariant>4.1.3</ServiceReferenceVariant> </Header> <Body> <ReadInstantaneousImportTOUWithBlocksMatrices/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Instantaneous Import TOU With Blocks Matrices Service Request Format Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Rresponse messages for a Read Instantaneous Import TOU With Blocks Matrices rrequest follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below. Page 22 of 239

23 Response & Alert Common Interface Format Format - ReadInstantaneousImportTOUWithBlocksMatricesRsp Formatted: Heading 6 Data in this response is organised as two sets of 8 values, one each for the block primary registers and the block counter registers, within a repeating group of up to 4 Tariff Blocks. Block 1 Block 2 Register Matrix 1 Register Matrix 2 : Register Matrix 8 Counter Matrix 1 Counter Matrix 2 : Counter Matrix 8 Register Matrix 1 etc Formatted: Font: 8 pt Formatted: Normal, Indent: Left: 2.54 cm Formatted: Normal Formatted: Normal, Indent: Left: 2.54 cm Formatted: Font: Arial, Not Bold, Font color: Auto Formatted: Keep with next Figure Read Instantaneous Import TOU With Blocks Matrices Parse Response Structure Specific Header Data Items Formatted: Caption Formatted: Heading 6 Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode GBCSUseCaseNumber GBCSUseCaseName 002A ECS17e Read ESME Energy Register (TOU with Blocks) Formatted: Keep with next Page 23 of 239

24 Table Read Instantaneous Import TOU With Blocks Matrices Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table RegisterMatrixTOUV aluetouregisterma trixvalue CounterMatrixTOUV aluetouprimaryre gistervalue Tariff Registers for Time-of-use with Block Pricing.Accumulated consumption for each TOU rate register. Gas Only Tariff Registers for Time-of-use with Block Pricing.Tariff Registers for Time-of-use Pricing Electricity Only xs:integer None WhM 3 xs:integer None WhWh TOUSecondRegister Value Tariff Registers for Time-of-use Pricing Electricity Only xs:integer None Wh Table Read Instantaneous Import TOU With Blocks Matrices Parse Response Body Data Items Figure 14 - Read Instantaneous Import TOU With Blocks Matrices Parse Response Specific Data Items Sample Response body Formatted: Keep with next Formatted: Caption Formatted: Heading 6 Page 24 of 239

25 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>2a</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs17e</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Energy Register (TOU with Blocks)</ra:GBCSUseCaseName> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readinstantaneousimporttouwithblocksmatricesrsp MessageSuccess="true"> <ra:tariffblocktouregistercollection> <ra:tariffblock index="1"> <ra:registermatrixtouvalue index="1">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="2">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="3">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="4">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="5">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="6">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="7">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="8">0</ra:registermatrixtouvalue> <ra:countermatrixtouvalue index="1">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="2">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="3">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="4">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="5">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="6">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="7">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="8">0</ra:countermatrixtouvalue> </ra:tariffblock> <ra:tariffblock index="2"> <ra:registermatrixtouvalue index="1">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="2">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="3">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="4">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="5">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="6">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="7">0</ra:registermatrixtouvalue> <ra:registermatrixtouvalue index="8">0</ra:registermatrixtouvalue> <ra:countermatrixtouvalue index="1">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="2">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="3">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="4">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="5">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="6">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="7">0</ra:countermatrixtouvalue> <ra:countermatrixtouvalue index="8">0</ra:countermatrixtouvalue> </ra:tariffblock> </ra:tariffblocktouregistercollection> </ra:readinstantaneousimporttouwithblocksmatricesrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Instantaneous Import TOU With Blocks Matrices Parse Response Sample Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Keep with next Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font color: Text 1 Formatted: Caption The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Page 25 of 239

26 7.1.2 Read Instantaneous Import Block Counters (4.1.4) Service Request Name ReadInstantaneousImportRegisters Service Reference 4.1 Service Request Variant Name ReadInstantaneousImportBlockCounters Service Reference Variant Service Request Objective Business Context Statement To allowenable a DCC Service User to obtainread the Gas Smart Meter an instantaneous import Block Counters matrix readheld on a Gas Proxy Function / Smart Meter. The DCC Service User requires an immediate view of the current import Block Counters matrix read values on a Gas Proxy Function / Smart Meter, e.g. to respond to a customer telephone enquiry Formatted: None, Indent: Left: cm, No page break before, Don't keep with next User Role Access Gas Import Supplier (GIS) Security Classification Non-critical and sensitive (the request is non-sensitive and the device response matrix content is sensitive): GBCS XREF: SME.C.NC Formatted: None, Indent: Left: 0 cm, Hanging: 0.63 cm, No page break before, Don't keep with next 1. The data item being read in this Service Request, as defined by SMETS, is the Tariff Block Counter Matrix for the GSME. Service Request Narrative Tariff Block Counter Matrix, as defneddefined in SMETS, is a 4 x 1 matrix for storing Block Counters for Block Pricing. 2. This Service Request returns all the the Block Counter Matrix valudesvalues available at the Meter in full. It isn t possible to request a subset of them. Service Reference Grouping is applicable to this Service Reference Variant for User Role GIS. 3. This Service Request can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. This means that any subsequent sequenced command could not be sent by the DCC as the success of the preceedingpreceding Service Request Request can notcannot be established. 4. For reading the instantaneous import block counter register values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not available for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. Formatted: Font color: Text 1 Formatted: Normal, None, Indent: Left: 1.27 cm, No bullets or numbering, No page break before, Don't keep with next Formatted: Font color: Text 1 Formatted: Font: Not Bold, Font color: Text 1 Formatted: None, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm, No page break before, Don't keep with next Formatted: Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font color: Text 1 Table Read Instantaneous Import Block Counters Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set). Page 26 of 239

27 Service Request Format The ServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests. Its ReadInstantaneousImportBlockCounters XML element defines this Service Request and doesn t contain any data items. Formatted: Font: 8 pt, Bold Figure Read Instantaneous Import Block Counters Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the device. Valid date-time in the future xs:date No N/A UTC Date- Time Table Read Instantaneous Import Block Counters Service Request Data Items Non- Formatted: Caption Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSPNo No Formatted: Space After: 0.6 line Table Read Instantaneous Import Block Counters Modes of Operation Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Validation CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Instantaneous Import Block Counters Command Variant Values This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request Page 27 of 239

28 A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: ncoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <CommandVariant>1</CommandVariant> <ServiceReference>4.1</ServiceReference> <ServiceReferenceVariant>4.1.4</ServiceReferenceVariant> </Header> <Body> <ReadInstantaneousImportBlockCounters/> </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> </ServiceRequest> Responses Figure Sample Read Instantaneous Import Block Counters Service Request Format Formatted: Font: (Default) Arial, 7.5 pt, Font color: Auto Formatted: Font: (Default) Arial, 7.5 pt, Font color: Auto Formatted: Font: (Default) Arial, 7.5 pt, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto The Service Rresponse messages for a Read Instantaneous Import Block Counters Rrequest follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadInstantaneousImportBlockCountersRsp The Tariff Block Counter Values are presented as a group of up to four values, repeating within the ImportBlockCounters group. Since GBCS only defines a value and no identifier, the parse response includes an index attribute against each value (defined as part of the IntegerWithIndex type) to differentiate them. Please see the sample in section below for an example. Formatted: Heading 6, No bullets or numbering Page 28 of 239

29 Formatted: Font: Arial, Not Bold, Font color: Auto Figure Read Instantaneous Import Block Counters Parse Response Structure Specific Header Data Items Data Item GBCSHexadecimalMessageCode GBCSUseCaseNumber Gas Response 00B8 GCS13b Formatted: Heading 6, No bullets or numbering Formatted Table GBCSUseCaseName Read GSME Block Counters Table Read Instantaneous Import Block Counters Parse Response Header Data Items Formatted: Caption, No bullets or numbering Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity TariffBlockCounterV alue Accumulated consumption within each block. Gas Only ra:decimalintegerwithin dex None m 3 Table Read Instantaneous Import Block Counters Parse Response Body Data Items Figure 19 - Read Instantaneous Import Block Counters Parse Response Specific Data Items Sample Response Formatted: Keep with next Formatted: Centered Formatted: Heading 6, No bullets or numbering Page 29 of 239

30 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>b8</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs13b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read GSME Block Counters</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readinstantaneousimportblockcountersrsp MessageSuccess="true"> <ra:importblockcounters> <ra:tariffblockcountervalue index="1">10.1</ra:tariffblockcountervalue> <ra:tariffblockcountervalue index="2">20.2</ra:tariffblockcountervalue> <ra:tariffblockcountervalue index="3">30.3</ra:tariffblockcountervalue> <ra:tariffblockcountervalue index="4">40.4</ra:tariffblockcountervalue> </ra:importblockcounters> </ra:readinstantaneousimportblockcountersrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Instantaneous Import Block Counters Parse Response Sample Formatted: Caption 7.2 Read Instantaneous Export Registers (4.2) Service Request Name ReadInstantaneousExportRegisters Service Reference 4.2 Service Request Variant Name ReadInstantaneousExportRegisters Service Reference Variant 4.2 Service Request Objective To allow enable a DCC Service User to read the instantaneous export register values on an electricity Electricity Smart metermeter. Business Context Statement The DCC Service User requires an immediate view of the current export register read values on an electricity Electricity Smart metermeter, e.g. to respond to a customer telephone enquiry. User Role Access Security Classification Service Request Narrative Electricity Export Supplier (EES) Electricity Network Operator (ENO) Non-critical and non-sensitive: GBCS XREF: SME.C.NC The data items being read in this Service Request, as defined by SMETS, are the Active Export Register andregister and Reactive Export Register for the ESME. Active Export Register, as defined by SMETS, is the register recording Page 30 of 239 Formatted: Font: Italic Formatted: None, Space After: 6 pt, No bullets or numbering, No page break before, Don't keep with next Formatted: Font: Italic Formatted: Font: Italic Formatted: Font: Italic Formatted: Font: Not Bold, Italic, Font color: Auto

31 the cumulative Active Energy Exported. Reactive Export Register, as defined by SMETS, is the register recording the cumulative Reactive Energy Exported. This Service Request returns all the Export Registers available at the metermeter. It isn t possible to request a subset of them. Table Read Instantaneous Export Registers Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its ReadInstantaneousExportRegisters XML element defines this Service Request and doesn t contain any data items. Formatted: Font: Italic, Font color: Blue Formatted: Centered Figure Read Instantaneous Export Registers Service Request Structure Formatted: Normal Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the device. Valid date-time in the future xs:date No N/A UTC Date- Time Table Read Instantaneous Export Registers Service Request Data Items Applicable Modes of Operation Non- Formatted: Caption, No bullets or numbering The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSPNo No Table Read Instantaneous Export Registers Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Page 31 of 239

32 Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Instantaneous Export Registers Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 32 of 239

33 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID>11-EE </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.2</ServiceReference> <ServiceReferenceVariant>4.2</ServiceReferenceVariant> </Header> <Body> <ReadInstantaneousExportRegisters/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Instantaneous Export Registers Service Request Format Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Rresponse messages for a Read Instantaneous Export Registers rrequest follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface. Page 33 of 239

34 See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - - ReadInstantaneousExportRegistersRsp Formatted: Keep with next Figure Read Instantaneous Export Registers Parse Response Structure Formatted: Caption, Justified Specific Header Data Items Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode 0026 GBCSUseCaseNumber GBCSUseCaseName ECS17a Read ESME Energy Registers (Export Energy) Page 34 of 239

35 Table Read Instantaneous Export Registers Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Units Sensitivity Formatted Table ActiveExportRegist er Value The register recording the active energy exported, as measured by the measuring element xs: decimalinteger Wh Nonsensitive ActiveEnergyUnit Unit of measure - Wh xs:string N/A Nonsensitive ReactiveExportReg ister Value The register recording the cumulative Reactive Energy Exported. xs: decimalinteger Varh Nonsensitive ReactiveEnergyUnit Unit of measure Varh xs:string N/A Nonsensitive Table Read Instantaneous Export Registers Parse Response Body Data Items Figure 24 - Read Instantaneous Export Registers Parse Response Specific Data Items Formatted: Keep with next Formatted: Caption Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>28</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs17a</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Energy Registers (Power)</ra:GBCSUseCaseName> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readinstantaneousexportregistersrsp MessageSuccess="true"> <ra:activeexportregister> <ra:value>100.1</ra:value> <ra:activeenergyunit>wh</ra:activeenergyunit> </ra:activeexportregister> <ra:reactiveexportregister> <ra:value>20.2</ra:value> <ra:reactiveenergyunit>varh</ra:reactiveenergyunit> </ra:reactiveexportregister> </ra:readinstantaneousexportregistersrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Instantaneous Export Registers Parse Response Sample The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Page 35 of 239 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: None, No bullets or numbering, No page break before Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font color: Text 1 Formatted: Caption Formatted: Normal, No bullets or numbering

36 8.2 Read Instantaneous Prepay Values (4.3) Service Request Name ReadInstantaneousPrepayValues Service Reference 4.3 Service Request Variant Name ReadInstantaneousPrepayValues Service Reference Variant 4.3 Service Request Objective To allow enable a DCC Service User to read instantaneous prepayment register values on aan Eelectricity Smart Meter or Gas Proxy FunctionSmart Meter. 3. The DCC Service User requires an immediate view of the current prepayment values on aan electricity Smart Meter / Gas Proxy Function, e.g. to respond to a customer telephone enquiry. The registers that will be queried through this request are: Formatted: Normal, Space Before: 0 pt, No bullets or numbering Formatted: Font color: Auto Business Context Statement Meter Balance Emergency Credit Balance Accumulated Debt Register Payment Debt Register Debt To Clear Time Debt Registers [1...2] User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Security Classification Non-critical, Request is non-sensitive, Response non-debt data is not non-sensitive and Response debt data is sensitive: GBCS XREF: SME.C.NC 1. The data items being read in this Service Request, as defined by SMETS are ; Meter Balance Emergency Credit Balance Accumulated Debt Register Payment Debt Register Debt To Clear Time Debt Registers [1...2] Service Request Narrative 2. This Service Request returns all the Prepayment Registers available at the meter / Gas Proxy Function. It isn t possible to request a subset of them. 3. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. This means that any subsequent sequenced command could not be sent by the DCC as the success of the preceedingpreceding Service Request Request can notcannot be established. When reading the read instantaneous prepayment register values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Page 36 of 239 Formatted: List Paragraph, None, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm

37 Only when the GPF is not avialableavailable for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users.Users. This Service Request returns all the Prepayment Registers available at the meter. / Gas Proxy Function. It isn t possible to request a subset of them. 4. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. Table Read Instantaneous Prepay Values Service Request Formatted: List Paragraph, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its ReadInstantaneousPrepayValues XML element defines this Service Request and doesn t contain any data items. Formatted: Centered Figure Read Instantaneous Prepay Values Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the device. Valid date-time in the future xs:date No N/A UTC Date- Time Table Read Instantaneous Import Prepay Values Service Request Data Items Non- Formatted: Caption, No bullets or numbering Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSPNo No Table Read Instantaneous Prepay Values Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Page 37 of 239

38 Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Validation CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Instantaneous Prepay Values Command Variant Values This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 38 of 239

39 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID>11-EE </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.3</ServiceReference> <ServiceReferenceVariant>4.3</ServiceReferenceVariant> </Header> <Body> <ReadInstantaneousPrepayValues/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Instantaneous Prepay Values Service Request Format Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Rresponse messages for a Read Instantaneous Prepay Values Rrequest follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface. Page 39 of 239

40 Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadInstantaneousPrepayValuesRsp Page 40 of 239

41 Formatted: Keep with next Page 41 of 239

42 Figure Read Instantaneous Prepay RegisterValues Parse Response Structure Formatted: Caption, Justified Specific Header Data Items Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode 002D 0075 GBCSUseCaseNumber ECS19 GCS14 GBCSUseCaseName Read ESME Prepayment Registers Read GSME Prepayment Register(s) Table Read Instantaneous Prepay Values Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table EmergencyCreditBal ance AccumulatedDebtRe gister PaymentDebtRegist er TimeDebtRegister1 TimeDebtRegister2 Amount of emergency credit remaining Debt accumulated on the meter for time based charges (standing charge and time based debt recovery) but only used whilst EmergencyCredit is in use, and where SuspendDebtEmergency.value = TRUE The remaining payment-based debt to be recovered Amount remaining to be recovered through time based debt recovery using DebtRecoveryRate[1..2] Amount remaining to be recovered through time based debt recovery using DebtRecoveryRate[1..2] xs:integer None Curren cy xs:integer None Curren cy xs:integer None Curren cy xs:integer None Curren cy xs:integer None Curren cy MeterBalance Credit available to the consumer xs:integer None Curren cy EMSE - Non- GSME Non- EMSE - GSME Non- Non- EMSE - GSME Non- EMSE - GSME EMSE GSME EMSE Table Read Instantaneous Prepay Values Parse Response Body Data Items GSME Non-Formatted: Keep with next Figure 29 - Read Instantaneous Prepay Values Parse Response Specific Data Items Formatted: Caption Sample Response body Page 42 of 239

43 Gas ECS20a ECS20b GCS15b ECS20c GCS15c GCS15d GCS15e DCC User Gateway Interface Design Specification <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>2d</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs19</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Prepayment Registers</ra:GBCSUseCaseName> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readinstantaneousprepayvaluesregistersrsp MessageSuccess="true"> <ra:emergencycreditbalance>10</ra:emergencycreditbalance> <ra:accumulateddebtregister>20</ra:accumulateddebtregister> <ra:paymentdebtregister>10</ra:paymentdebtregister> <ra:timedebtregister1>30</ra:timedebtregister1> <ra:timedebtregister2>40</ra:timedebtregister2> <ra:meterbalance>100</ra:meterbalance> </ra:readinstantaneousprepayvaluesregistersrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Instantaneous Prepayment ValuesRegisters Parse Response Sample The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. 9.2 Retrieve Billing Data Log (4.4) This Service Request maps to three Electricity and four GBCS Use Cases and each Use Case requires its own Request ID. Therefore the 4.4 Service Request has been broken into five parts: (Electricity Debt and Credit), (Electricity and Gas Change of Mode / Tariff Triggered), (Electricity and Gas Billing Calendar Triggered), (Gas Payment Debt) and (Gas Prepayment Credits). The following table maps the Service Requests to the SMETS data items defined on each device, the SMETS reference is given in brackets after the name. Billing data log ( ) Service Request GBCS Use Case 12 entries Tariff TOU Register Matrix ( ) y if in Prepayment Consumption Register ( ) Tariff Block Counter Matrix ( ) Page 43 of 239 y y Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: None, No bullets or numbering, No page break before Formatted: Font: Not Bold Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Font color: Text 1 Formatted: Font color: Text 1 Formatted: Caption, No bullets or numbering Formatted: Font: Arial, 9 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Font: Not Italic, Font color: Text 1 Formatted: Font: Arial, 9 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Font: Not Italic, Font color: Text 1 Formatted: Table Text - Centre Formatted Table Formatted: Table Text - Centre, Left Formatted: Table Text - Centre, Left, Indent: Left: 0 cm, Right: 0 cm Formatted: Table Text - Centre Formatted: Table Text - Centre, Left Formatted: Table Text - Centre, Left, Indent: Left: 0 cm, Right: 0 cm Formatted: Table Text - Centre Formatted: Table Text - Centre, Left Formatted: Table Text - Centre Formatted: Table Text - Centre, Left Formatted: Table Text - Centre, Left, Indent: Left: 0 cm, Right: 0 cm Formatted: Table Text - Centre, Left Formatted: Table Text - Centre, Left Formatted: Table Text - Centre, Left Formatted: Table Text - Centre, Left

44 Electricity - twin element Electricity - single element DCC User Gateway Interface Design Specification Mode 5 entries Value of prepayment credits Formatted y... 5 entries Debt adjustments ( ) 10 entries Payment-based debt payments Formatted y entries Meter balance ( ) y Billing data log ( ) Emergency credit balance ( ) Accumulated debt register ( ) Payment debt register ( ) Time debt registers [1..2] ( ) y y y y 12 entries Tariff TOU Register Matrix ( ) y y if in Prepayment Mode Tariff TOU Block Register Matrix ( ) y y Active import register ( ) y y 5 entries Value of prepayment credits y 5 entries Debt adjustments ( ) 10 entries Payment-based debt payments y 12 entries Meter balance ( ) y Billing data log ( ) Emergency credit balance ( ) Accumulated debt register ( ) Payment debt register ( ) Time debt registers [1..2] ( ) 12 entries Tariff TOU Register Matrix ( ) y y if in Prepayment Mode Secondary Tariff TOU Register Matrix ( ) y y Tariff TOU Block Register Matrix ( ) y y Active import register ( ) y y Secondary Active import register ( ) y y 5 entries Value of prepayment credits y 5 entries Debt adjustments ( ) 10 entries Payment-based debt payments y 12 entries Meter balance ( ) y Emergency credit balance ( ) Accumulated debt register ( ) Payment debt register ( ) Time debt registers [1..2] ( ) Table Service Requests to read Billing Data Log y y y y y y y y Page 44 of 239

45 The Billing Data Log, as defined in SMETS is a log capable of storing the following UTC date and time stamped entries: i. twelve entries comprising the Tariff TOU Register Matrix, the Secondary Tariff TOU Register Matrix, the Tariff TOU Block Register Matrix, the Active Import Register, the Secondary Active Import Register; and where in Prepayment mode: ii. iii. iv. five entries comprising the value of prepayment credits; five entries comprising the amount of any debt adjustment ten entries comprising the value of payment-based debt payments; and v. twelve entries comprising Meter Balance, Emergency Credit Balance, Accumulated Debt Register, Payment Debt Register and Time Debt Registers [1 2], each of i to v arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten. SR4.4.1 ESME only ii and iv SR4.4.2 ESME and GSME i SR ESME and GSME i SR4.4.4 GSME only iii and iv SR4.4.5 GSME only Prepayment Only entries ii Service Request definition differs from that in the SEC2 Consultation to align with GBCS UCs, because this Service Request maps to three Electricity and onefour GBCS Use Cases and each Use Case requires its own Request ID. Therefore the 4.4 Service Request has been broken into threefourive parts: (Electricity Debt and Credit), (Electricity and Gas Change of Mode / Tariff Triggered) and), (Electricity and Gas Billing Calendar Triggered) and, (Gas Billing Data LogPayment Debt) and (Gas Prepayment Credits) Retrieve Debt And Credit Billing Data Log (4.4.1) Service Request Name Service Reference 4.4 Service Request Variant Name Service Reference Variant Service Request Objective Business Context Statement RetrieveBillingDataLog RetrieveDebtAndCreditBillingDataLog To allow enable a DCC Service User to obtain read a data set stored in the Billing Data Log (Debt and Credit) of an Electricity Smart Meter on an ad-hoc basis for a specified date range. This Service Request Variant provides the mechanism tomechanism to read the Debt and Credit Billing Data Log on an ad-hoc basis. User Role Access Electricity Import Supplier (EIS) Page 45 of 239 Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto, Highlight Formatted: Highlight Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto, Highlight Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: 9 pt, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto

46 Gas Import Supplier (GIS) Security Classification Non-critical and sensitive (the request is non-sensitive and the device response Billing Data Log content is sensitive):: GBCS XREF: SME.C.NC 1. Returns Billing Log Data relating to an ESME operating in Prepayment Mode; specifically the value of prepayment credits and payment based debt payments as defined by SMETS. Service Request Narrative 1. The Service Request sender needs to be the Registered Import Supplier for the entire date-time period for which the Billing Data Log is requested. This could be the current or the old Registered Import Supplier. If the sender is not authorised to read data for the entire period requested, an error will be returned. Because this Service Request returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. Formatted: Font color: Text 1 Formatted: Indent: Left: cm 3.2. Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS and GIS. Table Retrieve Debt And Credit Billing Data Log Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its RetrieveDebtAndCreditBillingDataLog XML element defines this Service Request and contains the date-time period for which the log is to be read on the Device and, for Future Dated Requests, the Execution Date Time. Formatted: Font: Not Italic, Font color: Auto Page 46 of 239

47 Formatted: Font: (Default) Times New Roman, 0 pt, Not Bold, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Figure Retrieve Debt And Credit Billing Data Log Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity Formatted Table ExecutionDateTime BillingDataLogPerio dreadlogperiod The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future The Start and End Date-Times for which the data is required xs:datetime No None UTC Date- Time sr:readlogperiod (see Annex section 17 for details) Non- Formatted: Bulleted + Level: 1 + Yes None N/A Aligned at: 0 cm + Indent at: 0.63 cm Non- Page 47 of 239

48 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity Formatted Table PublicSecurityCrede ntial The Public Security Credential (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Old Registered Supplier) xs:base64binary Registered Supplier: N/A Old Registered Supplier 1 : Yes None N/A Non- Table Retrieve Debt And Credit Billing Data Log Service Request Data Items Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP No Table Retrieve Debt And Credit Billing Data Log Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Retrieve Debt And Credit Billing Data Log Command Variant Values Formatted: Font: 8 pt Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks and Annex section 17.2 for Execution Date Time and Read Log Period (BillingDataLogPeriod) validation. Formatted: Font: 9 pt Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 48 of 239

49 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.4</ServiceReference> <ServiceReferenceVariant>4.4.1</ServiceReferenceVariant> </Header> <Body> <RetrieveDebtAndCreditBillingDataLog> <BillingDataLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </BillingDataLogPeriodReadLogPeriod> </RetrieveDebtAndCreditBillingDataLog> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Retrieve Debt And Credit Billing Data Log Service Request Format Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Rresponse messages for a Retrieve Debt And Credit Billing Data Log rrequest follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Page 49 of 239

50 See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format Formatted Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Sample Response Formatted Format - RetrieveDebtAndCreditBillingDataLogRsp Formatted: Heading 6 Formatted: Font: Arial, Not Bold, Font color: Auto Figure Retrieve Debt And Credit Billing Data Log Parse Response Structure Specific Header Data Items Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode GBCSUseCaseNumber 002E ECS20a GBCSUseCaseName Read ESME Billing Data Log (debt and credit) Table Retrieve Debt And Credit Billing Data Log Parse Response Header Data Items Formatted: Caption, Left, Don't keep with next Specific Body Data Items Page 50 of 239 Formatted: Heading 6

51 Data Item Description / Valid Set Type Default Units Sensitivity PaymentBasedDebt Repayment Array of amount of debt recovered as part of the Credit Added ra:paymentbaseddebtr epaymenttype (see section ) None N/A Non- Formatted: Font: Arial, 8 pt, Not Bold, Font color: Text 1 Field Code Changed PrepaymentCredits Array of Prepayment Credits ra: PrepaymentCredits Type (see section PrepaymentCredits Specific Data Items ) None N/A Non- Table Retrieve Debt And Credit Billing Data Log Parse Response Body Data Items Formatted: Keep with next Formatted: Font: 8 pt Field Code Changed Figure 34 - Retrieve Debt And Credit Billing Data Log Parse Response Specific Data Items PaymentBasedDebtRepayment Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted: Heading 6, Left, Don't keep with next LogEntry 1 Amount of debt recovered as part of the credit added and time stamp of recovery ra:billingdatalogamount Timestamp (see section BillingDataLogAmountTi mestamp Specific Data ItemsBillingDataLogAmo unttimestamp Specific Data Items ) None N/A Non- Figure Retrieve Debt And Credit Billing Data Log Parse Response PaymentBasedDebtRepayment Specific Data Items Formatted: Superscript Field Code Changed Formatted: Font: Arial, 8 pt, Not Bold, Font color: Auto 1 Maximum 10 Formatted: Normal PrepaymentCredits Specific Data Items Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity LogEntry 1 Amount of Prepayment Credit Added and timestamp of application ra:billingdatalogamount Timestamp (see section Bi llingdatalogamounttim estamp Specific Data ItemsBillingDataLogAmo unttimestamp Specific Data Items) None N/A Non- Figure Retrieve Debt And Credit Billing Data Log Parse Response PrepaymentCredits Specific Data Items Formatted: Font: Not Bold, Font color: Auto Formatted: Font: 8 pt, Not Bold, Font color: Auto 1 Maximum 5 Formatted: Normal BillingDataLogAmountTimestamp Specific Data Items Formatted: Font: Arial Bold, 9 pt Data Item Description / Valid Set Type Default Units Sensitivity Page 51 of 239

52 Data Item Description / Valid Set Type Default Units Sensitivity Amount PaymentBasedDebtRepayment : Amount of debt recovered as part of the credit added Prepayment Credits: Amount of Prepayment Credit Added xs:integer None 1000th pence Non- Timestamp PaymentBasedDebtRepayment : Timestamp of recovery Prepayment Credits: Timestamp of application xs:datetime None UTC Date- Time Figure Retrieve Debt And Credit Billing Data Log Parse Response BillingDataLogAmountTimestamp Specific Data Items Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>2e</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs20a</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Billing Data Log (debt and credit)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrievedebtandcreditbillingdatalogrsp MessageSuccess="true"> <ra:paymentbaseddebtrepayment> <ra:logentry> <ra:amount>10000</ra:amount> <ra:timestamp> t19:23:08</ra:timestamp> </ra:logentry> </ra:paymentbaseddebtrepayment> <ra:prepaymentcredits> <ra:logentry> <ra:amount>1000</ra:amount> <ra:timestamp> t20:14:18</ra:timestamp> </ra:logentry> </ra:prepaymentcredits> </ra:retrievedebtandcreditbillingdatalogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Retrieve Debt And Credit Billing Data Log Parse Response Sample Non- Field Code Changed Formatted: Heading 6 Formatted: Font: 8 pt, Not Bold, Font color: Auto Formatted: Caption The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Retrieve Change Of Mode / Tariff Triggered Billing Data Log (4.4.2) Service Request Name RetrieveBillingDataLog Service Reference 4.4 Page 52 of 239

53 Service Request Variant Name RetrieveCoMOrTariffTriggeredBillingDataLog Service Reference Variant Service Request Objective Business Context Statement User Role Access Security Classification Service Request Narrative To allow enable a DCC Service User to obtain read a data set stored in the Billing Data Log (Change of Mode or Tariff Triggered) of an Electricity Smart Meter or Gas Proxy Function / Smart Meter on an adhoc basis for a specified date range. This Service Request Variant provides the mechanism tomechanism to read the Change of Mode / Tariff Triggered Billing Data Log on an ad-hoc basis. Electricity Import Supplier (EIS) Gas Import Supplier (GIS)Gas Import Supplier (GIS) Non-critical and sensitive (the request is non-sensitive and the device response Billing Data Log content is sensitive): GBCS XREF: SME.C.NC 1. The Service Request sender needs to be the Registered Import Supplier for the entire date-time period for which the Billing Data Log is requested. This could be the current or the old Registered Import Supplier. If the sender is not authorised to read data for the entire period requested, an error will be returned. 2. Because this Service Request returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS and GIS and GIS. 3. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. 4. This Service Request returns Billing Log Data relating to an ESME operating in either Credit or Prepayment Mode where Billing Data Log entries have been recorded as a result of a change in Device Configuration e.g. change of mode or tariff. Specific data items returned include the values of the Active Import register, Tariff TOU Register Matrix and Tariff TOU Block register Matrix, for a Single element ESME variant and in addition the values of then Secondary Active Import register and Secondary Tariff TOU register Matrix for a Twin element ESME variant as defined by SMETS. In addition, if the Device is operating in Prepayment Mode then values for Meter Balance, Emergency Credit Balance, Accumulated Debt register, payment Debt register and Time Debt registers [1..2] are also returned in addition to the first set of values. 5. If the device is a GSME in Prepayment Mode, then the values for Meter Balance, Emergency Credit Balance, Accumulated Debt register, payment Debt register and Time Debt registers [1..2] are Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: 9 pt Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: 9 pt Formatted: Font: Not Italic, Font color: Text 1 Formatted: List Paragraph, Space After: 6 pt, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Page 53 of 239

54 also returned For reading the Billing Data Log values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not available for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. Formatted: Font color: Text 1 Table Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its RetrieveCoMOrTariffTriggeredBillingDataLog XML element defines this Service Request and contains the date-time period for which the log is to be read on the device, for URPs the Key Agreement Public Security Credentials and, for Future Dated Requests, the Execution Date Time. Formatted: Justified Formatted: Font: Italic, Font color: Blue Page 54 of 239

55 Figure Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDate Time ReadLogPerio d KAPublicSecu ritycredentials The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future The Start and End Date-Times for which the data is required The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Old Registered Supplier) xs:datetime No None UTC Date- Time sr:readlogperiod (see Annex section 17 for details) sr:certificate (xs:base64binary) Non- Yes None N/A Non- Registered Supplier: N/A Old Registered Supplier 1 : Yes None N/A Non- Table Retrieve Debt And Credit Billing Data Log Service Request Data Items 1 Mandatory for User Roles EIS and GIS that were registered parties (KRPs) to the Device for the required time period, but they no longer are Formatted: Font: 9 pt Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP No Table Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks and Annex section 17.2 for Execution Date Time and, Read Log Period (BillingDataLogPeriod)and Key Agreement Public Security Credentials validation Sample Request Page 55 of 239

56 A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 56 of 239

57 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.4</ServiceReference> <ServiceReferenceVariant>4.4.2</ServiceReferenceVariant> </Header> <Body> <RetrieveCoMOrTariffTriggeredBillingDataLog> <BillingDataLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </BillingDataLogPeriodReadLogPeriod> </RetrieveCoMOrTariffTriggeredBillingDataLog> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Service Request Format Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Rresponse messages for a Retrieve Change Of Mode Or Tariff Triggered Billing Data Log rrequest follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Page 57 of 239

58 Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Sample Response Format - RetrieveChangeOfModeOrTariffTriggeredBillingDataLogRsp Formatted: Heading 6 Page 58 of 239

59 Formatted: Font: 9 pt, Not Bold Figure Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response Structure Formatted: Centered Page 59 of 239

60 Formatted: Normal, Left Figure Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response - LogEntryConsumptionAndTariffRegistersData Structure Formatted: Centered Page 60 of 239

61 Formatted: Normal, Left Figure Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response - LogEntryPrepaymentData Structure Specific Header Data Items Formatted: Centered Formatted: Heading 6, Left Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode 002F 00C3 GBCSUseCaseNumber ECS20b GCS15b GBCSUseCaseName Read ESME Billing Data Log (change of mode / tariff triggered exc export) Read GSME Billing Data Log (change of mode / tariff triggered) Table Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity LogEntryConsumpti onandtariffregister sdata 1 Array of Consumption and Tariff Registers Data Electricity Only ra: ConsumptionAndTariffR egisterstype (see section ConsumptionAndTariffR egisterstype Specific Data Items ) None N/A Formatted: Font: 8 pt, Not Bold, Font color: Auto Formatted: Font: Not Bold, Font color: Auto, Superscript Field Code Changed Formatted: Font: 8 pt Page 61 of 239

62 Data Item Description / Valid Set Type Default Units Sensitivity LogEntryPrepaymen Array of Prepayment Data ra: tdata 1 PrepaymentOperational DataType (see section ) None N/A LogEntryConsumpti onregister 1 Consumption Register value Gas Only xs: decimalinteger None kwh Table Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response Body Data Items Formatted: Keep with next Figure 44 - Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response Specific Data Items 1 Maximum ConsumptionAndTariffRegistersType Specific Data Items Formatted: Normal Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity ActiveImportRegiste rconsumption The register recording the cumulative Active Energy Imported. xs:integer None kwh TariffTOURegisterM atrixvalue 1 TariffTOUBlock1Reg istermatrixvalue 2 Tariff Registers for Time-of-use Pricing. Tariff Registers for Time of-use with Block Pricing. ra:integerwithindexdeci malwithindex ra: DecimalWithIndexIntege rwithindex None kwh None kwh Formatted: Font: Not Bold, Font color: Auto, Superscript TariffTOUBlock2Reg istermatrixvalue 2 Tariff Registers for Time of-use with Block Pricing. ra: DecimalWithIndexIntege rwithindex None kwh TariffTOUBlock3Reg istermatrixvalue 2 Tariff Registers for Time of-use with Block Pricing. ra: DecimalWithIndexIntege rwithindex None kwh TariffTOUBlock4Reg istermatrixvalue 2 Tariff Registers for Time of-use with Block Pricing. ra: DecimalWithIndexIntege rwithindex None kwh SecondaryActiveImp ortregisterconsump tion The register recording the cumulative Active Energy Imported via the secondary measuring element of the Electricity Meter. Only present if ESME variant = B twin element. xs:integerdecimal None kwh SecondaryTariffTOU RegisterMatrixValue 3 Secondary measument element Tariff Registers for Time-of-use Pricing. Only present if ESME variant = B twin element. ra: DecimalWithIndexIntege rwithindex None kwh Table Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response ConsumptionAndTariffRegistersType Specific Data Items Formatted: Keep with next Formatted: Font: Not Bold, Font color: Auto, Superscript Figure 45 - Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response ConsumptionAndTariffRegistersType Specific Data Items 1 Maximum 48 2 Maximum 8 3 Maximum 4 Formatted: Normal Page 62 of 239

63 Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>2f</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs20b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Billing Data Log (change of mode / tariff triggered exc export)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrievecomortarifftriggeredbillingdatalogrsp MessageSuccess="true"> <ra:electricity> <ra:logentryconsumptionandtariffregistersdata> <ra:activeimportregisterconsumption>0</ra:activeimportregisterconsumption> <ra:tarifftouregistermatrixvalue index="1">0</ra:tarifftouregistermatrixvalue> <ra:tarifftouregistermatrixvalue index="2">0</ra:tarifftouregistermatrixvalue> <ra:tarifftoublock1registermatrixvalue index="1">0</ra:tarifftoublock1registermatrixvalue> <ra:tarifftoublock1registermatrixvalue index="2">0</ra:tarifftoublock1registermatrixvalue> <ra:tarifftoublock2registermatrixvalue index="1">0</ra:tarifftoublock2registermatrixvalue> <ra:tarifftoublock2registermatrixvalue index="2">0</ra:tarifftoublock2registermatrixvalue> <ra:tarifftoublock3registermatrixvalue index="1">0</ra:tarifftoublock3registermatrixvalue> <ra:tarifftoublock3registermatrixvalue index="2">0</ra:tarifftoublock3registermatrixvalue> <ra:tarifftoublock4registermatrixvalue index="1">0</ra:tarifftoublock4registermatrixvalue> <ra:tarifftoublock4registermatrixvalue index="2">0</ra:tarifftoublock4registermatrixvalue> <ra:secondaryactiveimportregisterconsumption>0</ra:secondaryactiveimportregisterconsumption> <ra:secondarytarifftouregistermatrixvalue index="1">0</ra:secondarytarifftouregistermatrixvalue> <ra:secondarytarifftouregistermatrixvalue index="2">0</ra:secondarytarifftouregistermatrixvalue> </ra:logentryconsumptionandtariffregistersdata> <ra:logentryprepaymentdata> <ra:accumulateddebtregister>250000</ra:accumulateddebtregister> <ra:emergencycreditbalance>100000</ra:emergencycreditbalance> <ra:meterbalance>123000</ra:meterbalance> <ra:paymentdebtregister>500</ra:paymentdebtregister> <ra:timedebtregisters1>70</ra:timedebtregisters1> <ra:timedebtregisters2>80</ra:timedebtregisters2> <ra:timestamp> t00:01:02</ra:timestamp> </ra:logentryprepaymentdata> </ra:electricity> </ra:retrievecomortarifftriggeredbillingdatalogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Formatted: Heading 6 Formatted: Font: 8 pt, Not Bold, Font color: Auto Formatted: Font: 8 pt, Not Bold Formatted: Font: 8 pt, Not Bold Formatted: Font: 8 pt, Not Bold Formatted: Font: 8 pt, Not Bold Formatted: Font: 8 pt, Not Bold Figure Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response Sample Electricity Page 63 of 239

64 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>c3</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs15b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read GSME Billing Data Log (change of mode / tariff triggered exc export)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrievecomortarifftriggeredbillingdatalogrsp MessageSuccess="true"> <ra:gas> <ra:logentryconsumptionregister> <ra:consumptionregister>2</ra:consumptionregister> </ra:logentryconsumptionregister> <ra:logentryprepaymentdata> <ra:accumulateddebtregister>250000</ra:accumulateddebtregister> <ra:emergencycreditbalance>100000</ra:emergencycreditbalance> <ra:meterbalance>123000</ra:meterbalance> <ra:paymentdebtregister>500</ra:paymentdebtregister> <ra:timedebtregisters1>70</ra:timedebtregisters1> <ra:timedebtregisters2>80</ra:timedebtregisters2> <ra:timestamp> t00:01:02</ra:timestamp> </ra:logentryprepaymentdata> </ra:gas> </ra:retrievecomortarifftriggeredbillingdatalogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Retrieve Change Of Mode Or Tariff Triggered Billing Data Log Parse Response Sample - Gas Formatted: Font: Not Italic, Font color: Custom Color(RGB(41,35,92)) Formatted: Normal The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Retrieve Billing Calendar Triggered Billing Data Log (4.4.3) Service Request Name Service Reference 4.4 Service Request Variant Name Service Reference Variant Service Request Objective Business Context Statement RetrieveBillingDataLog RetrieveBillingCalendarTriggeredBillingDataLog To allow enable a DCC Service User to obtain read a data set stored in the Billing Data Log (Billing Calendar Triggered) of an Electricity Smart Meter or Gas Proxy Function / Smart Meter on an ad-hoc basis for a specified date range.. Scheduled (Billing Calendar triggered) Billing Data Log reads are configured via Service Request 6.8 (see Annex section 6.8) and Page 64 of 239 Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: 9 pt Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto

65 User Role Access Security Classification Service Request Narrative handled by the Electricity Smart Meter under SMETS2, with a Devicen Alert being sent to the supplier automatically each time data is written to the Billing Data Log. Service Request Variant provides the mechanism tomechanism to read the Billing Calendar Billing Data Log on an ad-hoc basis. Electricity Import Supplier (EIS) Gas Import Supplier (GIS)Gas Import Supplier (GIS) Non-critical and sensitive (the request is non-sensitive and the device response Billing Data Log content is sensitive): GBCS XREF: SME.C.NC 1. The Service Request sender needs to be the Registered Import Supplier for the entire date-time period for which the Billing Data Log is requested. This could be the current or the old Registered Import Supplier. If the sender is not authorised to read data for the entire period requested, an error will be returned. 2. Because this Service Request returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS and GIS and GIS. 3. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. 4. Returns Billing Log Data relating to an ESME operating in either Credit or Prepayment Mode where Billing Data Log entries have been recorded as a result of a billing calendar entry into the Billing Data Log. Specific data items returned include values of the Active Import register, Tariff TOU Register Matrix and Tariff TOU Block register Matrix for a Single element ESME variant and in addition the values of then Secondary Active Import register and Secondary Tariff TOU register Matrix for a Twin element ESME variant as defined by SMETS. 5. Returns Billing Log Data relating to a GSME operating in either Credit or Prepayment Mode where Billing Data Log entries have been recorded as a result of a billing calendar entry into the Billing Data Log. Specific data items returned include the values of the Consumption Register, Tariff TOU Register Matrix and Tariff Block Counter Matrix as defined by SMETS For reading the Billing Data Log values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not available for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: 9 pt Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Formatted: Font: 9 pt Formatted: Font: Not Italic, Font color: Text 1 Formatted Table Formatted: Font color: Text 1 Table Retrieve Billing Calendar Triggered Billing Data Log Service Request Page 65 of 239

66 This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its RetrieveBillingCalendarTriggeredBillingDataLog XML element defines this Service Request and contains the date-time period for which the log is to be read on the device, for URPs the Key Agreement Public Security Credentials and, for Future Dated Requests, the Execution Date Time. Formatted: Font: Arial, Not Bold, Italic, Font color: Blue Formatted: Font: Arial, Not Bold, Italic, Font color: Blue Figure Retrieve Billing Calendar Triggered Billing Data Log Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined in section The data items contained in the Service Request are defined as: Page 66 of 239

67 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDate Time The UTC date and time the DCC Service User requires the command to be executed on the Device ID xs:datetime No None UTC Date- Time Non- Valid date-time in the future ReadLogPerio d KAPublicSecu ritycredentials The Start and End Date-Times for which the data is required The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Old Registered Supplier) sr:readlogperiod (see Annex section 17 for details) sr:certificate (xs:base64binary) Yes None N/A Non- Registered Supplier: N/A Old Registered Supplier 1 : Yes None N/A Non- Table Retrieve Debt And Credit Billing Data Log Service Request Data Items 1 Mandatory for User Roles EIS that were registered parties (KRPs) to the Device for the required time period, but they no longer arein section Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP No Table Retrieve Billing Calendar Triggered Billing Data Log Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Validation CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Retrieve Billing Calendar Triggered Billing Data Log Command Variant Values This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks and Annex section 17.2 for Execution Date Time and, Read Log Period (BillingDataLogPeriod)and Key Agreement Public Security Credentials validation. Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 67 of 239

68 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.4</ServiceReference> <ServiceReferenceVariant>4.4.3</ServiceReferenceVariant> </Header> <Body> <RetrieveBillingCalendarTriggeredBillingDataLog> <BillingDataLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </BillingDataLogPeriodReadLogPeriod> </RetrieveBillingCalendarTriggeredBillingDataLog> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Retrieve Billing Calendar Triggered Billing Data Log Service Request Format Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Retrieve Billing Calendar Triggered Billing Data Log Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Page 68 of 239

69 Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Sample Response Format - RetrieveBillingCalendarTriggeredBillingDataLogRsp Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Figure Retrieve Billing Calendar Triggered Billing Data Log Parse Response Structure Page 69 of 239

70 Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Page 70 of 239

71 Figure Retrieve Billing Calendar Triggered Billing Data Log Parse Response - ESMEBillingDataLogEntry Structure Page 71 of 239

72 Formatted: Font: Arial, 9 pt, Not Bold, Font color: Auto Figure Retrieve Billing Calendar Triggered Billing Data Log Parse Response - GSMEBillingDataLogEntry Structure Specific Header Data Items Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode GBCSUseCaseNumber ECS20c GCS15c GBCSUseCaseName Read ESME Billing Data Log (billing calendar triggered exc export) Read GSME Billing Data Log (billing calendar triggered) Table Retrieve Billing Calendar Triggered Billing Data Log Parse Response Header Data Items Specific Body DataBody Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity ESMEBillingDataLo gentry 1 Electricity Smart Meter Billing Data Log Entry Electricity Only ra:esmebillingdatalog Entry (see Annex 15 section ) None N/A Page 72 of 239

73 Data Item Description / Valid Set Type Default Units Sensitivity GSMEBillingDataLo gentry 1 Gas Smart Meter Billing Data Log Entry Gas Only ra:esmebillingdatalog Entry (see Annex 15 section ) None N/A Table Retrieve Billing Calendar Triggered Billing Data Log Parse Response Body Data Items Formatted: Keep with next Figure 53 - Retrieve Billing Calendar Triggered Billing Data Log Parse Response Specific Data Items 1 Maximum Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>30</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs20c</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Billing Data Log (billing calendar triggered exc export)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrievebillingcalendartriggeredbillingdatalogrsp MessageSuccess="true"> <ra:electricity> <ra:esmebillingdatalogentry> <ra:timestamp> t18:12:51.0</ra:timestamp> <ra:activeimportregistervalueconsumption>2</ra:activeimportregistervalueconsumption> <ra:tarifftouregistermatrixvalue index="1">20</ra:tarifftouregistermatrixvalue> <ra:tarifftouregistermatrixvalue index="2">10</ra:tarifftouregistermatrixvalue> <ra:tarifftoublock1registermatrixvalue index="1">5</ra:tarifftoublock1registermatrixvalue> </ra:esmebillingdatalogentry> </ra:electricity> </ra:retrievebillingcalendartriggeredbillingdatalogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Formatted: Heading 6, Left, Don't keep with next Figure Retrieve Billing Calendar Triggered Billing Data Log Parse Response Sample Electricity Page 73 of 239

74 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>76</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs15c</ra:gbcsusecasenumber> <ra:gbcsusecasename>read GSME Billing Data Log (billing calendar triggered)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrievebillingcalendartriggeredbillingdatalogrsp MessageSuccess="true"> <ra:gas> <ra:gsmebillingdatalogentry> <ra:activeimportregistervalueconsumption>2</ra:activeimportregistervalueconsumption> <ra:blockregistermatrixvalue index="1">20</ra:blockregistermatrixvalue> <ra:tarifftouregistermatrixvalue index="2">10</ra:tarifftouregistermatrixvalue> <ra:timestamp> t18:12:51.0</ra:timestamp> </ra:gsmebillingdatalogentry> </ra:gas> </ra:retrievebillingcalendartriggeredbillingdatalogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Formatted Table Figure Retrieve Billing Calendar Triggered Billing Data Log Parse Response Sample - Gas The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Retrieve Billing Data Log (Payment Based Debt Payments)(Gas) (4.4.4) Service Request Name RetrieveBillingDataLog Formatted: Font: Arial Bold, 11 pt, Bold Formatted: Font: Arial Bold, 11 pt, Bold, Font color: Auto Service Reference 4.4 Service Request Variant Name RetrieveBillingDataLog(PaymentBasedDebtPayments)(Gas) Formatted: Font: (Default) Arial, 9 pt, Not Bold, Font color: Auto Service Reference Variant Service Request Objective To allowenable a DCC Service User to obtainread a data set stored in the Billing Data Log (Payment Based Debt Payments)(Debt and Credit, Change of Mode or Tariff Triggered and Billing Calendar Triggered) of a Gas Proxy Function / Gas Smart Meter on an ad-hoc basis for a specified date range. Formatted: Font: Arial, Not Bold, Font color: Auto Business Context Statement Scheduled (Billing Calendar triggered) Billing Data Log reads are configured via Service Request 6.8 (see Annex section 6.8) and handled by the Gas Smart Meter under SMETS2, with an Alert being sent to the supplier automatically each time data is written to the Billing Data Log. Service Request Variant provides the mechanism to read the Page 74 of 239

75 Billing Data Log (Debt and Credit, Change of Mode or Tariff Triggered and Billing Calendar Triggered) on an ad-hoc basis. User Role Access Gas Import Supplier (GIS) Security Classification Non-critical and non-sensitive (the request is non-sensitive and the device response Billing Data Log content is sensitive): GBCS XREF: SME.C.NC 1. The Service Request sender needs to be the Registered Import Supplier for the entire date-time period for which the Billing Data Log is requested. This could be the current or the old Registered Import Supplier. If the sender is not authorised to read data for the entire period requested, an error will be returned. Service Request Narrative 1. Returns Billing Log Data relating to a GSME operating in Prepayment Mode; specifically the value of prepayment based debt payments as defined by SMETS. 2. For reading the Billing Data Log values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not available for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. Because this Service Request returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. 3. Service Reference Grouping is applicable to this Service Reference Variant for User Role GISnot applicable to this Service Reference Variant, because none of the User Roles it applies to has access to any of the other variants. Formatted: Font color: Text 1 Formatted Table Formatted: Font color: Text 1 Formatted: Space After: 10 pt, Outline numbered + Level: 1 + Numbering Style: Bullet + Aligned at: 0 cm + Indent at: 0.63 cm Table Retrieve Billing Data Log (GasPayment Based Debt Payments) Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format - RetrieveBillingDataLogDebtPayments The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its RetrieveBillingDataLogGasDebtPayments XML element defines this Service Request and contains the date-time period for which the log is to be read on the device, for URPs the Key Agreement Public Security Credentials and, for Future Dated Requests, the Execution Date Time. Formatted: Heading 4, Outline numbered + Level: 4 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Tab after: 1.5 cm + Indent at: 1.5 cm Formatted: Heading 5 Page 75 of 239

76 Formatted: Font: Italic, Font color: Blue Figure Retrieve Billing Data Log (Payment Based Debt PaymentsGas) Service Request Structure Formatted: Caption, Indent: Left: 0 cm, Don't keep with next Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDate Time The UTC date and time the DCC Service User requires the command to be executed on the Device ID xs:datetime No None UTC Date- Time Non- Valid date-time in the future ReadLogPerio d The Start and End Date-Times for which the data is required sr:readlogperiod (see Annex section 17 for details) Yes None N/A Non- Page 76 of 239

77 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity KAPublicSecu ritycredentials The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Old Registered Supplier) sr:certificate (xs:base64binary) Registered Supplier: N/A Old Registered Supplier 1 : Yes None N/A Non- Table Retrieve Billing Data Log (Payment Based Debt PaymentsGas) Service Request Data Items 1 Mandatory for User Roles GIS that were registered parties (KRPs) to the Device for the required time period, but they no longer are Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Formatted: Heading 5 Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP No Formatted: Space After: 0.6 line Table Retrieve Billing Billing Data Log (Payment Based Debt PaymentsGas) Modes of Operation Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Formatted: Heading 5 CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Retrieve Billing Data Log (Payment Based Debt PaymentsGas) Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks and Annex section 17.2 for Execution Date Time,and Read Log Period and Key Agreement Public Security Credentials validation. Formatted: Heading Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 77 of 239

78 ncoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.4</ServiceReference> <ServiceReferenceVariant>4.4.4</ServiceReferenceVariant> </Header> <Body> <RetrieveBillingDataLogGasDebtPayments> <ReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </ReadLogPeriod> </RetrieveBillingDataLogGasDebtPayments> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Retrieve Billing Data Log (Payment Based Debt PaymentsGas) Service Request Format Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Retrieve Billing Data Log (Payment Based Debt PaymentsGas) Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Page 78 of 239

79 Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Sample Response Format - RetrieveBillingDataLogDebtPaymentsRsp Formatted: Heading 6 Formatted: Font: 9 pt, Not Bold Figure Retrieve Billing Data Log (Payment Based Debt Payments) Parse Response Structure Specific Header Data Items Data Item Gas Response Formatted Table GBCSHexadecimalMessageCode GBCSUseCaseNumber 00C4 GCS15d GBCSUseCaseName Read GSME Billing Data Log (payment-based debt payments) Table Retrieve Billing Data Log (Payment Based Debt Payments) Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity Page 79 of 239

80 Data Item Description / Valid Set Type Default Units Sensitivity PaymentBasedDebt Repayment Array of amount of debt recovered as part of the Credit Added ra:paymentbaseddebtr epaymenttype (see section ) None N/A Non- Table Retrieve Billing Data Log (Payment Based Debt Payments) Parse Response Body Data Items Formatted: None Figure 59 - Retrieve Billing Data Log (Payment Based Debt Payments) Parse Response Specific Data Items Sample Response body <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>c4</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs15d</ra:gbcsusecasenumber> <ra:gbcsusecasename> Read GSME Billing Data Log (payment-based debt payments)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrievebillingdatalogdebtpaymentsrsp MessageSuccess="true"> <ra:paymentbaseddebtrepayment> <ra:logentry> <ra:amount>10000</ra:amount> <ra:timestamp> t19:23:08</ra:timestamp> </ra:logentry> </ra:paymentbaseddebtrepayment> </ra:retrievebillingdatalogdebtpaymentsrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Retrieve Billing Data Log (Payment Based Debt Payments) Parse Response Sample Formatted: Heading 6, Left, Don't keep with next Formatted: Normal The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Retrieve Billing Data Log (Prepayment Credits) (4.4.5) Service Request Name RetrieveBillingDataLog Service Reference 4.4 Service Request Variant Name RetrieveBillingDataLog(PrepaymentCredits) Service Reference Variant Page 80 of 239

81 Service Request Objective To allowrnableenable a DCC Service User to obtainread a data set stored in the Billing Data Log (Prepayment Credits) of a Gas Proxy Function / Gas Smart Meter on an ad-hoc basis for a specified date range. Business Context Statement User Role Access Gas Import Supplier (GIS) Security Classification Non-critical and non-sensitive: GBCS XREF: SME.C.NC 1. The Service Request sender needs to be the Registered Import Supplier for the entire date-time period for which the Billing Data Log is requested. This could be the current or the old Registered Import Supplier. If the sender is not authorised to read data for the entire period requested, an error will be returned. Formatted: Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Service Request Narrative Returns Billing Log Data relating to a GSME operating in Prepayment Mode; specifically the value of prepayment credits as defined by SMETS. Formatted: Font color: Text 1 2. Service Reference Grouping is applicable to this Service Reference Variant for User Role GIS. Table Retrieve Billing Data Log (Prepayment Credits) Service Request Formatted: Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The ServiceRequestRequest XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests. Its RetrieveBillingDataLogPrepaymentCredits XML element defines this Service Request and contains the date-time period for which the log is to be read on the device and, for Future Dated Requests, the Execution Date Time. Page 81 of 239

82 Formatted: Font: Italic, Font color: Blue Figure Retrieve Billing Data Log (Prepayment Credits) Service Request Structure Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDate Time The UTC date and time the DCC Service User requires the command to be executed on the Device ID xs:datetime No None UTC Date- Time Non- Valid date-time in the future ReadLogPerio d The Start and End Date-Times for which the data is required sr:readlogperiod (see Annex section 17 for details) Yes None N/A Non- Table Retrieve Billing Data Log (Prepayment Credits) Service Request Data Items Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP No Formatted: Space After: 0.6 line Table Retrieve Billing Billing Data Log (Prepayment Credits) Modes of Operation Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Page 82 of 239

83 Table Retrieve Billing Data Log (Prepayment Credits) Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks and Annex section 17.2 for Execution Date Time and Read Log Period validation Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: ncoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <CommandVariant>1</CommandVariant> <ServiceReference>4.4</ServiceReference> <ServiceReferenceVariant>4.4.5</ServiceReferenceVariant> </Header> <Body> <RetrieveBillingDataLogPrepaymentCredits> <ReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </ReadLogPeriod> </RetrieveBillingDataLogPrepaymentCredits> </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> </ServiceRequest> Figure Sample Retrieve Billing Data Log (Prepayment Credits) Service Request Format Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Retrieve Billing Data Log (Prepayment Credits) Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Page 83 of 239

84 Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Sample Response Format - RetrieveBillingDataLogPrepaymentCreditsRsp Formatted: Font: 9 pt, Not Bold Figure Retrieve Billing Data Log (Prepayment Credits) Parse Response Structure Specific Header Data Items Data Item Gas Response Formatted Table GBCSHexadecimalMessageCode GBCSUseCaseNumber 00C5 GCS15e GBCSUseCaseName Read GSME Billing Data Log (prepayment credits) Table Retrieve Billing Data Log (Prepayment Credits) Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity Page 84 of 239

85 Data Item Description / Valid Set Type Default Units Sensitivity PrepaymentCredits Array of Prepayment Credits ra: PrepaymentCredits Type (see section Pr epaymentcredits Specific Data Items) None N/A Non- Table Retrieve Billing Data Log (Prepayment Credits) Parse Response Body Data Items Formatted: None Formatted: Font: 8 pt Figure 64 - Retrieve Billing Data Log (Prepayment Credits) Parse Response Specific Data Items Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>c5</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs15e</ra:gbcsusecasenumber> <ra:gbcsusecasename>read GSME Billing Data Log (prepayment credits)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrievebillingdatalogprepaymentcreditsrsp MessageSuccess="true"> <ra:prepaymentcredits> <ra:logentry> <ra:amount>1000</ra:amount> <ra:timestamp> t20:14:18</ra:timestamp> </ra:logentry> </ra:prepaymentcredits> </ra:retrievebillingdatalogprepaymentcreditsrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Formatted: Heading 6, Left, Don't keep with next Figure Retrieve Billing Data Log (Prepayment Credits) Parse Response Sample The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Section 4.5 This section has been intentionally left blank as there is no Service Reference 4.5. Formatted: Font: Italic, Font color: Text Retrieve Daily Read Log (4.6) Service Request definition differs from that in the SEC2 Consultation to align with GBCS UCs, because tthis Service Request maps to two Electricity and one Gas GBCS Use Cases and each Use Case requires its own Request ID. Therefore the 4.6 Service Request has been broken into two parts: (Import) and (Export) Formatted: Font: Not Italic, Font color: Text 1 Formatted: Font color: Text 1 Page 85 of 239

86 Retrieve Import Daily Read Log (4.6.1) Service Request Name RetrieveDailyReadLog Service Reference 4.6 Service Request Variant Name RetrieveImportDailyReadLog Service Reference Variant Service Request Objective To allow enable a DCC Service User to obtain read an Import Daily Read Log entry of an electricity or gas metersmart Meter or Gas Proxy Function / Smart Meter for a specified date-time period. Business Context Statement Allows a DCC Service User to request the retrieval of a stored Import Daily Read Log entry for a specific date (Enables a reading at a specific time (e.g. midnight) to be retrieved at a later time (for example on change of Supplier). User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Security Classification Non-critical and sensitive (the request is non-sensitive and the device response Daily Read Log content is sensitive): GBCS XREF: SME.C.NC Formatted Table Page 86 of 239

87 1. GSME Daily Read Log as defined in SMETS is, a log capable of storing thirty one UTC date and time stamped entries of the Tariff TOU Register Matrix, the Tariff Block Counter Matrix and the Consumption Register arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten. 2. ESME Daily Read Log as defined in SMETS is, a log capable of storing thirty one UTC date and time stamped entries of the Tariff TOU Register Matrix, the Tariff TOU Block Register Matrix, the Active Import Register and the Active Export Register arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten. In addition, Secondary Tariff TOU Register Matrix and Secondary Active Import Register may also be recorded for a twin element ESME. 3. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. 4. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. This could be the current or the old Registered Supplier. Because this Service Request returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. a. Access Control will allow the old Registered Import Supplier and the current Registered Import Supplier to read the Import Daily Read Log entry for a CoS Date identified from registration data. 5. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. This will never be the old Registered Supplier. Service Request Narrative 6. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. For reading the instantaneous import energy registersdaily read log values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not avialableavailable for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. 1. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Formatted: Space After: 10 pt o Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. This could be the current or the old Registered Supplier. Because this Service Request returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. Access Control will allow the old Registered Import Supplier and the current Registered Import Supplier to read the Import Daily Read Log entry for a CoS Date identified from registration data. Page 87 of 239 DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. This will never be the old Registered Supplier. Service Reference Grouping is not applicable to this Service Formatted: Space After: 10 pt, Outline numbered + Level: 1 + Numbering Style: Bullet + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Space After: 10 pt

88 Table Retrieve Import Daily Read Log Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its RetrieveImportDailyReadLog XML element defines this Service Request and contains the date-time period for which the log is to be read on the Device, for URPs the Key Agreement Public security Security Ccredentials and, for Future Dated Requests, the Execution Date Time. Formatted: Font: Formatted: Font: (Default) Times New Roman, 0 pt, Bold, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Figure Retrieve Import Daily Read Log Service Request Structure (Ad-hoc) Create Schedule: Its DSPRetrieveImportDailyReadLog XML element defines this Service Request and contains the date-time interval for which to read data on the device, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition. Page 88 of 239

89 Formatted: Font: Formatted: Caption Figure Retrieve Import Daily Read Log Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled RetrieveImportDailyReadLog (Ad-hoc) Formatted: Heading 6 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDate Time DailyReadLog Period KAPublicSecu ritycredentials The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future The Start and End Date-Times for which the data is required The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Old Registered Supplier) xs:datetime No None UTC Date- Time sr:readlogperiod (see Annex section 17 for details) sr:certificate (xs:base64binary) Page 89 of 239 Non- Yes None N/A Non- Formatted: Font: 8 pt Registered Supplier: N/A Old Registered Supplier 1 : Table Retrieve Import Daily Read Log Service Request Data Items (Ad-hoc) Yes None N/A Non- Formatted: Font: 8 pt, Not Italic Formatted: Font: 8 pt, Not Italic Formatted: Font: 8 pt, Not Italic Formatted: Font: Bold, Not Italic, Font color: Custom Color(RGB(41,35,92)), Check spelling and grammar

90 1 Mandatory for User Roles EIS and GIS that were registered parties (KRPs) to the Device for the required time period, but they no longer are Formatted: Font: 8 pt, Not Italic, Not Superscript/ Subscript DSPRetrieveImportDailyReadLog (Create Schedule) Data Item Description / Valid Set Type Mandatory Default Units Sensitivity DSPDailyRea dlogperiod Offset The Start and End Date Offsets from the current date and the Start and End Times which together define the date-time period for which the data is required sr:readlogperiodoffset (see Annex section 17 for details) Yes None N/A Non- Table Retrieve Import Daily Read Log Service Request RetrieveDailyReadLog Data Items (Create Schedule) Formatted: Space After: 0 pt Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Retrieve Import Daily Read Log Modes of Operation Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Formatted: Space After: 0 pt CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Retrieve Import Daily Read Log Command Variant Values (Ad-hoc) Formatted: Font: 9 pt, Not Bold, Not Italic, Font color: Auto Formatted: Caption Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time, Key Agreement Public Security Credentials and Read Log Period (DailyReadLogPeriod) validation. Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSPDailyReadLogPeriodOffset) validation Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 90 of 239

91 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.6</ServiceReference> <ServiceReferenceVariant>4.6.1</ServiceReferenceVariant> </Header> <Body> <RetrieveImportDailyReadLog> <ReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </ReadLogPeriod> </RetrieveImportDailyReadLog> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Retrieve Import Daily Read Log Service Request Format (Ad-hoc) Formatted: Font: Arial, 7.5 pt, Not Italic, Font color: Auto Formatted: Font: Arial, 7.5 pt, Not Italic, Font color: Auto Formatted: Font: Arial, 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Retrieve Import Daily Read Log Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Page 91 of 239

92 See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - RetrieveImportDailyReadLogRsp Formatted: Heading 6 Page 92 of 239

93 Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Formatted: Keep with next Formatted: Font: Not Italic Figure Retrieve Import Daily Read Log Parse Response Structure Specific Header Data Items Formatted: Caption, Justified Formatted: Heading 6 Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode GBCSUseCaseNumber ECS21a GCS16a Page 93 of 239

94 Data Item Electricity Response Gas Response GBCSUseCaseName Read Electricity Daily Read Log (exc export) Read GSME Daily Read log(s) Table Retrieve Import Daily Read Log Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table ActiveImportRegiste rconsumption The register recording the cumulative Active Energy Imported. xs:integer None Wh Timestamp The UTC date-time at which the corresponding log entry was taken xs:datetime None N/AUT C Date- Time TariffBlockCounterM atrix TariffTOURegisterM atrix SecondaryActiveImp ortregisterconsump tion SecondaryTariffTOU RegisterMatrixValue TariffTOURegisterM atrixvalue TariffTOUBlock1Reg istermatrixvalue TariffTOUBlock2Reg istermatrixvalue TariffTOUBlock3Reg istermatrixvalue Block Counters for Block Pricing. Gas Only Tariff Registers for Time-of-use Pricing. Gas Only The register recording the cumulative Active Energy Imported via the secondary measuring element of the Electricity Meter. Electricity Only Optional Tariff Registers for Time-of-use Pricing. Electricity Only Optional Tariff Registers for Time-of-use Pricing. Electricity Only Block Counters for Block Pricing. Electricity Only Block Counters for Block Pricing. Electricity Only Block Counters for Block Pricing. Electricity Only xs:integer None Wh xs:integer None Wh xs:integer None Wh xs:integer None Wh xs:integer None Wh xs:integer None Wh xs:integer None Wh xs:integer None Wh TariffTOUBlock4Reg istermatrixvalue Block Counters for Block Pricing. Electricity Only xs:integer None Wh Table Retrieve Import Daily Read Log Parse Response Body Data Items Figure 70 - Retrieve Import Daily Read Log Parse Response Specific Data Items Sample Response Formatted: Keep with next Formatted: Caption Formatted: Heading 6 Page 94 of 239

95 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>33</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs21a</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Electricity Daily Read Log (exc Export)</ra:GBCSUseCaseName> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrieveimportdailyreadlogrsp MessageSuccess="true"> <ra:logentry> <ra:activeimportregisterconsumption>0</ra:activeimportregisterconsumption> <ra:timestamp> t00:00:00.0</ra:timestamp> <ra:electricity> <ra:secondaryactiveimportregisterconsumption>0</ra:secondaryactiveimportregisterconsumption> <ra:secondarytarifftouregistermatrixvalue index="1">0</ra:secondarytarifftouregistermatrixvalue> <ra:secondarytarifftouregistermatrixvalue index="2">0</ra:secondarytarifftouregistermatrixvalue> <ra:tarifftouregistermatrixvalue index="1">0</ra:tarifftouregistermatrixvalue> <ra:tarifftouregistermatrixvalue index="2">0</ra:tarifftouregistermatrixvalue> <ra:tarifftoublock1registermatrixvalue index="1">0</ra:tarifftoublock1registermatrixvalue> <ra:tarifftoublock1registermatrixvalue index="2">0</ra:tarifftoublock1registermatrixvalue> <ra:tarifftoublock2registermatrixvalue index="1">0</ra:tarifftoublock2registermatrixvalue> <ra:tarifftoublock2registermatrixvalue index="2">0</ra:tarifftoublock2registermatrixvalue> <ra:tarifftoublock3registermatrixvalue index="1">0</ra:tarifftoublock3registermatrixvalue> <ra:tarifftoublock3registermatrixvalue index="2">0</ra:tarifftoublock3registermatrixvalue> <ra:tarifftoublock4registermatrixvalue index="1">0</ra:tarifftoublock4registermatrixvalue> <ra:tarifftoublock4registermatrixvalue index="2">0</ra:tarifftoublock4registermatrixvalue> </ra:electricity> </ra:logentry> <ra:logentry> <ra:activeimportregisterconsumption>0</ra:activeimportregisterconsumption> <ra:timestamp> t00:00:00.0</ra:timestamp> <ra:electricity> <ra:secondaryactiveimportregisterconsumption>0</ra:secondaryactiveimportregisterconsumption> <ra:secondarytarifftouregistermatrixvalue index="1">0</ra:secondarytarifftouregistermatrixvalue> <ra:secondarytarifftouregistermatrixvalue index="2">0</ra:secondarytarifftouregistermatrixvalue> <ra:tarifftouregistermatrixvalue index="1">0</ra:tarifftouregistermatrixvalue> <ra:tarifftouregistermatrixvalue index="2">0</ra:tarifftouregistermatrixvalue> <ra:tarifftoublock1registermatrixvalue index="1">0</ra:tarifftoublock1registermatrixvalue> <ra:tarifftoublock1registermatrixvalue index="2">0</ra:tarifftoublock1registermatrixvalue> <ra:tarifftoublock2registermatrixvalue index="1">0</ra:tarifftoublock2registermatrixvalue> <ra:tarifftoublock2registermatrixvalue index="2">0</ra:tarifftoublock2registermatrixvalue> <ra:tarifftoublock3registermatrixvalue index="1">0</ra:tarifftoublock3registermatrixvalue> <ra:tarifftoublock3registermatrixvalue index="2">0</ra:tarifftoublock3registermatrixvalue> <ra:tarifftoublock4registermatrixvalue index="1">0</ra:tarifftoublock4registermatrixvalue> <ra:tarifftoublock4registermatrixvalue index="2">0</ra:tarifftoublock4registermatrixvalue> </ra:electricity> </ra:logentry> </ra:retrieveimportdailyreadlogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Retrieve Import Daily Read Log Parse Response Sample Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Keep with next Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Font color: Text 1 The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Page 95 of 239

96 Retrieve Export Daily Read Log (4.6.2) Service Request Name RetrieveDailyReadLog Service Reference 4.6 Service Request Variant Name RetrieveExportDailyReadLog Service Reference Variant Service Request Objective Business Context Statement To allow enable a DCC Service User to obtain read an Export Daily Read Log entry of an electricity meter for a specified date period. Allows a DCC Service User to request the retrieval of a stored Export Daily Read Log entry for a specific date (Enables a reading at a specific time (e.g. midnight) to be retrieved at a later time (for example on change of Supplier). User Role Access Electricity Export Supplier (EES) Security Classification Non-critical and sensitive (the request is non-sensitive and the device response Daily Read Log content is sensitive):: GBCS XREF: SME.C.NC Service Request Narrative 1. ESME Daily Read Log as defined in SMETS is, a log capable of storing thirty one UTC date and time stamped entries of the Tariff TOU Register Matrix, the Tariff TOU Block Register Matrix, the Active Import Register and the Active Export Register arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten. In addition, Secondary Tariff TOU Register Matrix and Secondary Active Import Register may also be recorded for a twin element ESME. 2. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. 3. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. a. Access Control will allow the old Registered Export Supplier and the current Registered Export Supplier to read the Export Daily Read Log entry for a CoS Date identified from registration data. 4. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. 1. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Formatted: Font: 9 pt, Not Bold, Not Italic, Not Highlight Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. Because this Service Request returns data, URPs (i.e. the Electricity Export Supplier), have to include in the Request Page 96 of 239

97 the Public Security Credentials they want the Device to sign the Response with. o Access Control will allow the old Registered Export Supplier and the current Registered Export Supplier to read the Export Daily Read Log entry for a CoS Date identified from registration data. Formatted: Font: Arial, 9 pt, Not Bold, Not Italic, Font color: Auto DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. The URP Public Security Credentials for the Device to sign the Response are included in the Create Schedule Service Request. See Annex section 5.1. Service Reference Grouping is not applicable to this Service Reference Variant, because none of the User Roles it applies to has access to Import and Export data 2.. Formatted: Normal, None, No bullets or numbering, No page break before, Don't keep with next Table Retrieve Export Daily Read Log Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its RetrieveExportDailyReadLog XML element defines this Service Request and contains the date-time period for which the log is to be read on the Device, the Public Credentials to be used to read it, for URP the security credentials and, for Future Dated Requests, the Execution Date Time. Formatted: Font: (Default) Arial, Not Bold, Font color: Blue Page 97 of 239

98 Formatted: Font: (Default) Arial, Not Bold, Not Italic, Font color: Auto Figure Retrieve Export Daily Read Log Service Request Structure (Ad-hoc) Create Schedule: Its DSPRetrieveExportDailyReadLog XML element defines this Service Request and contains the date-time interval for which to read data on the device, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition. Formatted: Font: (Default) Arial, Not Bold, Not Italic, Font color: Auto Page 98 of 239

99 Figure Retrieve Export Daily Read Log Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled RetrieveExportDailyReadLog (Ad-hoc) 3. The data items contained in the Service Request are defined in section Data Item Description / Valid Set Type Mandatory Default Units Sensitivity Formatted: Normal, Space After: 0 pt, No bullets or numbering ExecutionDate Time DailyReadLog Period PublicSecurity Credential The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future The Start and End Date-Times for which the data is required The Public Security Credential (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Electricity Export Supplier) xs:datetime No None UTC Date- Time sr:readlogperiod (see Annex section 17 for details) Non- Yes None N/A Non- Formatted: Font: 8 pt, Font color: Auto xs:base64binary Yes None N/A Non- Table 34 Retrieve Export Daily Read Log Service Request Data Items (Ad-hoc) DSPRetrieveExportDailyReadLog (Create Schedule) They are the same as those of Service Reference Variant See DSPRetrieveImportDailyReadLog (Create Schedule)DSPRetrieveImportDailyReadLog (Create Schedule)DSPRetrieveImportDailyReadLog (Create Schedule)DSPRetrieveImportDailyReadLog (Create Schedule)DSPRetrieveImportDailyReadLog (Create Schedule)DSPRetrieveImportDailyReadLog (Create Schedule)DSPRetrieveImportDailyReadLog (Create Schedule) Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Formatted: Heading 6 Formatted: Font: 9 pt, Not Italic, Font color: Auto Formatted: Font: 9 pt, Not Italic, Font color: Auto Formatted: Font: 9 pt, Not Italic, Font color: Auto Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Retrieve Export Daily Read Log Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Retrieve Export Daily Read Log Command Variant Values (Ad-hoc) Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Page 99 of 239

100 Ad-hoc: See also Annex section 17.2 for Execution Date Time and Read Log Period (DailyReadLogPeriod) validation. Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSPDailyReadLogPeriodOffset) validation Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 100 of 239

101 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.6</ServiceReference> <ServiceReferenceVariant>4.6.2</ServiceReferenceVariant> </Header> <Body> <RetrieveExportDailyReadLog> <ExportDailyReadLog> <DailyReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </DailyReadLogPeriod> </ExportDailyReadLog> <PublicSecurityCredential>ZGVmYXVsdA==</PublicSecurityCredential> </RetrieveExportDailyReadLog> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Retrieve Export Daily Read Log Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Retrieve Export Daily Read Log Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Page 101 of 239

102 Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - RetrieveExportDailyReadLogRsp Formatted: Heading 6 Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Figure Retrieve Export Daily Read Log Parse Response Structure Specific Header Data Items Formatted: Caption Formatted: Heading 6 Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode 0035 GBCSUseCaseNumber ECS21c GBCSUseCaseName Read Electricity Daily Read Log (export only) Table Retrieve Export Daily Read Log Parse Response Header Data Items Formatted: Caption Specific Body Data Items The body items in the table below appear as pairs within the LogEntry group which can repeat up to thirty-one times. Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table ActiveExportRegiste rvalue The billing log entry recorded at that date-time xs:integer None WhN/A Non- Timestamp The UTC date-time at which the corresponding log entry was taken xs:datetime None UTC Date- TimeN/ A Table Retrieve Export Daily Read Log Parse Response Body Data Items Non- Formatted: Keep with next Figure 76 - Retrieve Export Daily Read Log Parse Response Specific Data Items Formatted: Caption Page 102 of 239

103 Sample Response <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>35</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs21c</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Electricity Daily Read Log (export only)</ra:gbcsusecasename> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:retrieveexportdailyreadlogrsp MessageSuccess="true"> <ra:logentry> <ra:activeexportregistervalue>0</ra:activeexportregistervalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeexportregistervalue>10</ra:activeexportregistervalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeexportregistervalue>20</ra:activeexportregistervalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeexportregistervalue>30</ra:activeexportregistervalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeexportregistervalue>40</ra:activeexportregistervalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeexportregistervalue>50</ra:activeexportregistervalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> </ra:retrieveexportdailyreadlogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Retrieve Export Daily Read Log Parse Response Sample Formatted: Heading 6 Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Keep with next Formatted: Font color: Text 1 Formatted: Caption The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Section 4.7 This section has been intentionally left blank as there is no Service Reference Read Profile Data (4.8) Service Request definition differs from that in the SEC2 Consultation to align with GBCS UCs, because tthis Service Request maps to three Electricity and one Gas GBCS Use Cases and each Use Case requires its own Request ID. Therefore the 4.8 Service Request has been broken into three parts: (Active Import) applicable to Electricity and Gas, (Reactive Import) applicable to Electricity and (Export) applicable to Electricity. Formatted: Font: Arial, Not Bold, Not Italic, Font color: Text 1 Formatted: Font: Not Italic, Font color: Text 1 Formatted: Font: Arial, Not Bold, Not Italic, Font color: Text 1 Formatted: Font color: Text 1 Page 103 of 239

104 Read Active Import Profile Data (4.8.1) Service Request Name ReadProfileData Service Reference 4.8 Service Request Variant Name ReadActiveImportProfileData Service Reference Variant Service Request Objective To allow enable a DCC Service user to request the retrieval of interval data (half hourly active import consumption data) from a device Device with a specific device Device ID. A DCC Service User wishes to retrieve a set of half hourly active import consumption data for a device Device at a specific device Device ID. The Profile Data Log will store (where such time has elapsed) at least: Formatted: Font color: Auto Electricity: Business Context Statement Gas: 13 months of Active Energy Imported via the primary measuring element of the Electricity Meter; 13 months of Active Energy Imported via the secondary measuring element of the Electricity Meter (if present twin element EMSEESME variant only) 13 months of Active Import Consumption data (GPF) 3 months of Active Import Consumption data (GSME) This request will return such active import consumption data as is available. A DCC Service User will have the ability to request a start and end date for interval data. User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Electricity Network Operator (ENO) Gas Network Operator (GNO) Other User (OU) Security Classification Non-critical and sensitive (the request is non-sensitive and the response is sensitive): GBCS XREF: SME.C.NC Page 104 of 239

105 1. The Profile Data Log on the GSME, as defined in SMETS, is a log capable of storing a minimum of three months of UTC date and time stamped half hourly Consumption data arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten. The Gas Proxy Function will sturestore a minimuminimum of 13 months worthmonths worth of data from the GSME in its Profile Data Log. 2. When reading the read instantaneous prepayment active import profile register valuesdata from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not avialableavailable for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. 3. The span of the Read Log Period cannot exceed more than 31 days for a single request. Multiple requests can of course be made to retrieve the full set of data available on the Device. For example, to retrieve 13 months of data then the DCC Service User can make 13 requests, one for each month. 4. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Service Request Narrative 5. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. In the case of Import Supplier, this could be the current or the old Registered Supplier. Because this Service Request returns data, URPs (i.e. the old Registered Supplier and Other User ), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. 6. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. In the case of Import Supplier, this will never be the old Registered Supplier. The URP Public Security Credentials (applicable to Other User ) for the Device to sign the Response are included in the Create Schedule Service Request. See Annex section This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. 1. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. In the case of Import Supplier, this could be the current or the old Registered Supplier. Because this Service Request returns data, URPs (i.e. the old Registered Supplier and Other User ), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. In the case of Import Supplier, this will never be the old Registered Supplier. The URP Public Security Credentials (applicable to Other User ) for the Device to sign the Response are included in the Create Page Schedule 105 Service of 239 Request. See Annex section Service Reference Grouping is applicable to DCC this PUBLIC Service Reference Variant for User Role EIS, ENO and OU. (Electricity). Formatted: Font: (Default) Arial, Not Bold, Not Italic, Font color: Auto Formatted: Font color: Text 1 Formatted: Normal, Space After: 0 pt, No bullets or numbering Formatted: Font color: Auto Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto, Highlight Formatted: Normal, No bullets or numbering Formatted: Font color: Text 1

106 Table Read Active Import Profile Data Service Request This section should be read in conjunction with Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its ReadActiveImportProfileData XML element defines this Service Request and contains the date-time interval for which to read data on the device, for URP the Key Agreement Public security Security credentials Credentials and, for Future Dated, the Execution Date and Time. Page 106 of 239

107 Formatted: Font: Arial, Not Italic, Font color: Auto Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Page 107 of 239

108 Figure Read Active Import Profile Data Service Request Structure (Adhoc) Create Schedule: Its DSPReadActiveImportProfileData XML element defines this Service Request and contains the date-time interval for which to read data on the device, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition Formatted: Caption Formatted: Font: Not Italic Figure Read Active Import Profile Data Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadActiveImportProfileData (Ad-hoc) Formatted: Heading 6 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the Device ID xs:datetime No None UTC Date- Time Non- Valid date-time in the future ProfileDataLogPeriodRe adlogperiod The Start and End Date-Times for which the data is required sr:readlogperiod (see Annex section 17 for details) Yes None N/A Non- Page 108 of 239

109 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity KAPublicSecurityCreden tials The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Other User) xs:base64binary User Role 1 EIS, GIS, ENO, GNO: N/A User Role OU: Yes 1 Table Read Active Import ProfileImport Profile Data Service Request Data Items (Ad-hoc) None N/A Non- 1 Also Mandatory for User Roles: EIS and GIS that were registered parties (KRPs) to the Device for the required time period, but they no longer are GNO, if the Business Target ID Device Type is Gas Smart Meter DSPReadActiveImportProfileData (Create Schedule) Formatted: Font: 8 pt, Not Italic Formatted: List Paragraph, Bulleted + Level: 3 + Aligned at: 2.54 cm + Indent at: 3.17 cm Formatted: Font: 8 pt Formatted: Heading 6 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity DSPProfileDataLogPe riodoffset The Start and End Date Offsets from the current date and the Start and End Times which together define the datetime period for which the data is required sr:readlogperiod Offset (see Annex section 17 for details) Yes None N/A Non- Table Read Active Import Profile Data Service Request Data Items (Items (Create Schedule) Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Read Active Import Profile Data Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Active Import Profile Data Command Variant Values (Ad-hoc) Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time, KA Public Security Credentials and Read Log Period (ProfileDataLogPeriod) validation. Page 109 of 239

110 Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSPProfileDataLogPeriodOffset) validation. In addition the following check is performed on the Read Log Period: Validation Check Process Response Code Does the Read Log Period span more than 31 days? For an on-demand request compare the Start Date Time and End Date Time to calculate the span. If this is more than 31 days raise an error. For a DSP scheduled request compare the Start Date Offset and End Date Offset to calculate the span. If this is more than 31 days raise an error. Table Validation checks E Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 110 of 239

111 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.8</ServiceReference> <ServiceReferenceVariant>4.8.1</ServiceReferenceVariant> </Header> <Body> <ReadActiveImportProfileData> < <ProfileDataLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </ProfileDataLogPeriodReadLogPeriod> > </ReadActiveImportProfileData> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Active Import Profile Data Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Active Import Profile Data Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Page 111 of 239

112 Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the device. When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in the following section. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Service Response (from Device) DSP Scheduled Message DSP Scheduled Response Format The DSPScheduledMessage XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of the Service Response that includes the Device Command Response and the DSP Schedule ID. Figure DSP Scheduled Service Response (from Device) Structure DSP Scheduled Response Specific Data Items Definition If the Device sends a response to the DCC Data Systems, they will add the DSP Schedule ID to the GBCS response from the Device. Data Item Description / Valid Set Type Mandatory Default Units Sensitivity DSPScheduleID Schedule ID generated by the DCC Data Systems when the Schedule was created > 0 xs:positiveinteger Yes None N/A Non- Table DSP Scheduled Service Request Response Data Items DSP Scheduled Sample Response (KRP) The response from the Device isn t digitally signed by the DSP Broker, because of the inclusion of the DSP Schedule ID in the XML Page 112 of 239

113 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <ResponseIDRequestID>11-DB :99-00-AA-BB-CC-DD-EE-FF:50</ResponseIDRequestID> <ResponseID>99-00-AA-BB-CC-DD-EE-FF:11-DB :50</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <ResponseCode>I0</ResponseCode> <ResponseDateTime> T18:13:51.0</ResponseDateTime> </Header> <Body> <ResponseMessage> <ServiceReference>4.8</ServiceReference> <ServiceReferenceVariant>4.8.1</ServiceReferenceVariant> <DSPScheduledMessage> <GBCSPayload>ZGVmYXVsdA==</GBCSPayload> <DSPScheduleID>500</DSPScheduleID> </DSPScheduledMessage> </ResponseMessage> </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=dsp broker,ou=smart metering,o=dcc,l=london,st=england,c=uk</x509issuername> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> </AsynchronousServiceResponse> Figure Sample Service Response (from Device) Format (DSPScheduledMessage) (KRP) DSP Scheduled Sample Response (URP - Response includes sensitive data) The response from the Device isn t digitally signed by the DSP Broker, because of the inclusion of the DSP Schedule ID in the XML. Formatted: Font: 7.5 pt, Not Italic Formatted Table Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Bold, Font color: Auto Formatted: Heading 6 Page 113 of 239

114 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID>11-DB :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <ResponseID>99-00-AA-BB-CC-DD-EE-FF:11-DB :50</ResponseID> <ResponseID>11-DB :99-00-AA-BB-CC-DD-EE-FF:50</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <ResponseCode>I0</ResponseCode> <ResponseDateTime> T18:13:51.0</ResponseDateTime> </Header> <Body> <ResponseMessage> <ServiceReference>4.8</ServiceReference> <ServiceReferenceVariant>4.8.1</ServiceReferenceVariant> <DSPScheduledMessage> <GBCSPayload>ZGVmYXVsdA==</GBCSPayload> <DSPScheduleID>500</DSPScheduleID> </DSPScheduledMessage> </ResponseMessage> </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=dsp broker,ou=smart metering,o=dcc,l=london,st=england,c=uk</x509issuername> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> </AsynchronousServiceResponse> Figure Sample Service Response (from Device) Format (DSPScheduledMessage) (URP - Response includes sensitive data) DSP Scheduled Sample Response (URP - Response only includes non-sensitive data) Formatted: Font: 7.5 pt, Not Italic Formatted Table Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt Formatted: Heading 6 The response from the Device is digitally signed by the DSP Broker. Please note this sample has been included here for completeness, but it doesn t apply to this Service Reference Variant. Page 114 of 239

115 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID>11-DB :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <ResponseID>99-00-AA-BB-CC-DD-EE-FF:11-DB :50</ResponseID> <ResponseID>11-DB :99-00-AA-BB-CC-DD-EE-FF:50</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <ResponseCode>I0</ResponseCode> <ResponseDateTime> T18:13:51.0</ResponseDateTime> </Header> <Body> <ResponseMessage> <ServiceReference>4.8</ServiceReference> <ServiceReferenceVariant>4.8.1</ServiceReferenceVariant> <DSPScheduledMessage> <GBCSPayload>ZGVmYXVsdA==</GBCSPayload> <DSPScheduleID>500</DSPScheduleID> </DSPScheduledMessage> </ResponseMessage> </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=dsp broker,ou=smart metering,o=dcc,l=london,st=england,c=uk</x509issuername> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Figure Sample Service Response (from Device) Format (DSPScheduledMessage) (URP Response only includes non-sensitive data) Unsuccessful Response The Response Codes specific to this Service Request are: Formatted: Font: 7.5 pt, Not Italic Formatted Table Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt Formatted: Font: Bold, Not Italic, Font color: Custom Formatted: Font: Bold, Not Italic, Font color: Custom Response Code Response Code Name Response Code Type Description E Failed Validation Date Span invalid Error The Date span in the request is for more than 31 days. Table 90 Failed Read Active Import Profile Data Service Request Response Codes Formatted: Normal Response & Alert Common Interface Format Page 115 of 239

116 Format - ReadActiveImportProfileDataRsp Formatted: Heading 6, No bullets or numbering Formatted: Font: Not Italic Formatted: Normal, No bullets or numbering Formatted: Font: Not Italic Figure Read Active Import Profile Data Parse Response Structure Note: LogEntry Maximum A value of is considered as Unbounded by the XSD validation Specific Header Data Items Data Item Electricity Response Gas Response Formatted: Caption, No bullets or numbering Formatted: Heading 6, No bullets or numbering GBCSHexadecimalMessageCode GBCSUseCaseNumber ECS22b GCS17 GBCSUseCaseName Read Electricity Half Hour Profile Data (active import) Read GSME Profile Data Log Table Read Active Import Profile Data Parse Response Header Data Items Formatted: Caption, No bullets or numbering Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table PrimaryValue Timestamp The total active energy imported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases) The date-time stamp at the end of the period to which the value relates xs:integer None N/A xs:datetime None N/A Page 116 of 239

117 Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table SecondaryValue The total active energy imported in this 30 minute period on the secondary element Electricity Only Optional xs:integer None N/A Table Read Active Import Profile Data Parse Response Body Data Items Figure 86 - Read Active Import Profile Data Parse Response Specific Data Items Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>37</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs22b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Electricity Half Hour Profile Data (active import)</ra:gbcsusecasename> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readactiveimportprofiledatarsp MessageSuccess="true"> <ra:logentry> <ra:primaryvalue>0</ra:primaryvalue> <ra:timestamp> t00:00:00.0</ra:timestamp> <ra:electricity> <ra:secondaryvalue>0</ra:secondaryvalue> </ra:electricity> </ra:logentry> <ra:logentry> <ra:primaryvalue>0</ra:primaryvalue> <ra:timestamp> t00:30:00.0</ra:timestamp> <ra:electricity> <ra:secondaryvalue>0</ra:secondaryvalue> </ra:electricity> </ra:logentry> <ra:logentry> <ra:primaryvalue>0</ra:primaryvalue> <ra:timestamp> t01:00:00.0</ra:timestamp> <ra:electricity> <ra:secondaryvalue>0</ra:secondaryvalue> </ra:electricity> </ra:logentry> <ra:logentry> <ra:primaryvalue>0</ra:primaryvalue> <ra:timestamp> t01:30:00.0</ra:timestamp> <ra:electricity> <ra:secondaryvalue>0</ra:secondaryvalue> </ra:electricity> </ra:logentry> </ra:readactiveimportprofiledatarsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Active Import Profile Data Parse Response Sample Formatted: Keep with next Formatted: Caption Formatted: Heading 6, No bullets or numbering Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Keep with next Formatted: Font color: Text 1 Formatted: Caption The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Page 117 of 239

118 Read Reactive Import Profile Data (4.8.2) Service Request Name ReadProfileData Service Reference 4.8 Service Request Variant Name ReadReactiveImportProfileData Service Reference Variant Service Request Objective To allow enable a DCC Service user to request the retrieval of interval data (half hourly reactive import data) from a device Device with a specific device Device ID. Formatted Table Business Context Statement A DCC Service User wishes to retrieve a set of half hourly reactive import data for a device DeviceESME at a specific device Device ID. The Profile Data Log will store (where such time has elapsed) at least: 3 months reactive energy import This request will return such reactive import data as is available. A DCC Service User will have the ability to request a start and end date for interval data. User Role Access Electricity Import Supplier (EIS) Electricity Network Operator (ENO) Other User (OU) Security Classification Non-critical and sensitive (the request is non-sensitive and the response is sensitive):: GBCS XREF: SME.C.NC 1. The span of the Read Log Period cannot exceed more than 31 days for a single request. Multiple requests can of course be made to retrieve the full set of data available on the Device This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Formatted: Font color: Text 1 Service Request Narrative Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. In the case of Import Supplier, this could be the current or the old Registered Supplier. Because this Service Request returns data, URPs (i.e. the old Registered Supplier and Other User ), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. Formatted: Font: (Default) Arial, Not Bold, Not Italic, Font color: Auto DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. In the case of Import Supplier, this will never be the old Registered Supplier. The URP Public Security Credentials (applicable to Other User ) for the Device to sign the Response are included in the Create Schedule Service Request. See Annex Page 118 of 239

119 section Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS, ENO and OU. (Electricity). Table Read Reactive Import Profile Data Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set). Formatted: Indent: Left: 0.63 cm, Space After: 10 pt, No bullets or numbering Formatted: Font color: Auto Formatted: Indent: Left: 0 cm Service Request Format The SMSServiceRequestRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its ReadReactiveImportProfileData XML element defines this Service Request and contains the date-time interval for which to read data on the device, for URP the security credentials and, for Future Dated, the Execution Date and Time. Formatted: Font: Not Italic Page 119 of 239

120 Formatted: Caption Formatted: Font: Not Italic Figure Read Reactive Import Profile Data Service Request Structure (Ad-hoc) Create Schedule: Its DSPReadReactiveImportProfileData XML element defines this Service Request and contains the date-time interval for which to read data on the device, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition. Formatted: Font: Not Italic Page 120 of 239

121 Formatted: Font: (Default) Times New Roman, 0 pt, Not Italic, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear Formatted: Centered Figure Read Reactive Import Profile Data Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadReactiveImportProfileData (Ad-hoc) The data items contained in the Service Request are defined in section They are the same as those of Service Reference Variant See ReadActiveImportProfileData (Ad-hoc)ReadActiveImportProfileData (Ad-hoc). Formatted: Heading 6, Indent: Left: 0 cm DSPReadReactiveImportProfileData (Create Schedule) They are the same as those of Service Reference Variant See DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule) Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Read Reactive Import Profile Data Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Reactive Import Profile Data Command Variant Values (Ad-hoc) Validation Page 121 of 239

122 This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time and Read Log Period (ProfileDataLogPeriod) validation. Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSPProfileDataLogPeriodOffset) validation. In addition the following check is performed on the Read Log Period: Validation Check Process Response Code Does the Read Log Period span more than 31 days? For an on-demand request compare the Start Date Time and End Date Time to calculate the span. If this is more than 31 days raise an error. For a DSP scheduled request compare the Start Date Offset and End Date Offset to calculate the span. If this is more than 31 days raise an error. Table Validation checks E Formatted: Caption Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is) is as follows: Page 122 of 239

123 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.8</ServiceReference> <ServiceReferenceVariant>4.8.2</ServiceReferenceVariant> </Header> <Body> <ReadReactiveImportProfileData> < <ProfileDataLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </ProfileDataLogPeriodReadLogPeriod> > </ReadReactiveImportProfileData> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Reactive Import Profile Data Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Reactive Import Profile Data Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Page 123 of 239

124 See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the device. When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Unsuccessful Response The Response Codes specific to this Service Request are: Response Code Response Code Name Response Code Type Description E Failed Validation Date Span invalid Error The Date span in the request is for more than 31 days. Table 97 Failed Read Reactive Import Profile Data Service Request Response Codes Response & Alert Common Interface Format Format - ReadReactiveImportProfileDataRsp Formatted: Heading 6, No bullets or numbering Formatted: Font: Not Italic Formatted: Indent: Left: 1.27 cm, Keep with next Formatted: Font: Not Italic Figure Read Reactive Import Profile Data Parse Response Structure Formatted: Caption, Justified Note: LogEntry Maximum A value of 4464 is considered as Unbounded by the XSD validation Specific Header Data Items Formatted: Heading 6, No bullets or numbering Page 124 of 239

125 Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode 0038 GBCSUseCaseNumber ECS22c GBCSUseCaseName Read Electricity Half Hour Profile Data (reactive import) Table Read Reactive Import Profile Data Parse Response Header Data Items Formatted: Caption, No bullets or numbering Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table ReactiveEnergyImp ortedvalue The total reactive import energy imported in this 30 minute period (if a twin element meter, this is across the primary and secondary element; if on a polyphase meter, it is cumulative across the phases) xs:integer None Non- Timestamp The date-time stamp at the end of the period to which the value relates xs:datetime None N/A Non- Table Read Reactive Import Profile Data Parse Response Body Data Items Formatted: Keep with next Figure 92 - Read Reactive Import Profile Data Parse Response Specific Data Items Formatted: Caption Sample Response Formatted: Heading 6, No bullets or numbering Page 125 of 239

126 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>38</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs22c</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Electricity Half Hour Profile Data (reactive import)</ra:gbcsusecasename> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readreactiveimportprofiledatarsp MessageSuccess="true"> <ra:logentry> <ra:reactiveenergyimportedvalue>10</ra:reactiveenergyimportedvalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:reactiveenergyimportedvalue>20</ra:reactiveenergyimportedvalue> <ra:timestamp> t00:30:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:reactiveenergyimportedvalue>30</ra:reactiveenergyimportedvalue> <ra:timestamp> t01:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:reactiveenergyimportedvalue>40</ra:reactiveenergyimportedvalue> <ra:timestamp> t01:30:00.0</ra:timestamp> </ra:logentry> </ra:readreactiveimportprofiledatarsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Reactive Import Profile Data Parse Response Sample Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Keep with next Formatted: Font color: Text 1 Formatted: Caption The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Read Export Profile Data (4.8.3) Service Request Name ReadProfileData Service Reference 4.8 Service Request Variant Name ReadExportProfileData Service Reference Variant Service Request Objective To allow enable a DCC Service user to request the retrieval of interval data (half hourly export data) from a device Device with a specific device Device ID. Page 126 of 239

127 A DCC Service User wishes to retrieve a set of half hourly export data for a device Device at a specific device Device ID. The Profile Data Log will store (where such time has elapsed) at least: Business Context Statement 3 months active energy export 3 months reactive energy export This request will return such export data as is available. A DCC Service User will have the ability to request a start and end date for interval data. User Role Access Electricity Export Supplier (EES) Electricity Network Operator (ENO) Other User (OU) Security Classification Non-critical and sensitive (the request is non-sensitive and the response is sensitive):: GBCS XREF: SME.C.NC Page 127 of 239

128 Service Request Narrative 1. The span of the Read Log Period cannot exceed more than 31 days for a single request. Multiple requests can of course be made to retrieve the full set of data available on the Device. 2. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested.. In the case of Export Supplier or Electricity Network Operator, this could be the current or the old Registered Supplier. 1. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. See Annex section This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. Because this Service Request returns data,urps (i.e. the Electricity Export Supplier and Other User ), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. The URP Public Security Credentials (applicable to Electricity Export Supplier and Other User ) for the Device to sign the Response are included in the Create Schedule Service Request. See Annex section Service Reference Grouping is applicable to this Service Reference Variant for User Role ENO and OU. (Electricity). Formatted: None, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm, No page break before, Don't keep with next Formatted: Font: Not Bold, Font color: Text 1 Formatted: None, Bulleted + Level: 2 + Aligned at: 1.27 cm + Indent at: 1.9 cm, No page break before, Don't keep with next Formatted: Font: Not Italic, Not Highlight Formatted: Font: Not Italic, Not Highlight Formatted: None, Space After: 6 pt, Numbered + Level: 2 + Numbering Style: a, b, c, + Start at: 1 + Alignment: Left + Aligned at: 1.27 cm + Indent at: 1.9 cm, No page break before, Don't keep with next Formatted: Font: Not Bold, Font color: Text 1 Formatted: Bulleted + Level: 2 + Aligned at: 1.27 cm + Indent at: 1.9 cm Formatted Table Formatted: Normal, Space After: 0 pt, No bullets or numbering Formatted: Normal, No bullets or numbering Table Read Export Profile Data Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its ReadExportProfileData XML element defines this Service Request and contains the date-time interval for which to read data on the device, for URP the security credentials and, for Future Dated, the Execution Date and Time. Page 128 of 239

129 Formatted: Font: (Default) Arial, Not Bold, Not Italic, Font color: Auto Formatted: Font: (Default) Arial, Not Italic, Font color: Auto Figure Read Export Profile Data Service Request Structure (Ad-hoc) Create Schedule: Its DSPReadExportProfileData XML element defines this Service Request and contains the date-time interval for which to read data on the device, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition. Page 129 of 239

130 Formatted: Font: (Default) Arial, Not Bold, Not Italic, Font color: Auto Formatted: Font: (Default) Times New Roman, 0 pt, Not Bold, Not Italic, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Figure Read Export Profile Data Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadExportProfileData (Ad-hoc) Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime ProfileDataLogPeriod The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future The Start and End Date-Times for which the data is required xs:datetime No None UTC Date- Time sr:readlogperiod (see Annex section 17 for details) Non- Yes None N/A Non- PublicSecurityCredential The Public Security Credential (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Export Supplier or Other User) xs:base64binary User Role ENO: N/A User Role EES, OU: Yes None N/A Non- Page 130 of 239

131 The data items contained in the Service Request are defined in section Field Code Changed Table 47 Read Export Profile Data Service Request Data Items (Ad-hoc) DSPReadExportProfileData (Create Schedule) They are the same as those of Service Reference Variant See DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)DSPReadActiveImportProfileData (Create Schedule)See DSPReadActiveImportProfileData (Create Schedule) Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see the Main Document of this documentation set section 2.3 for Modes of Operation definitions): Formatted: Heading 6 Formatted: Font: 9 pt, Not Italic, Font color: Auto Formatted: Font: 9 pt, Not Italic, Font color: Auto Formatted: Font: 9 pt, Not Italic, Font color: Auto Formatted: Font: 9 pt, Not Italic, Font color: Auto Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Read Export Profile Data Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Export Profile Data Command Variant Values (Ad-hoc) Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time and Read Log Period (ProfileDataLogPeriod) validation. Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSPProfileDataLogPeriodOffset) validation. In addition the following check is performed on the Read Log Period: Validation Check Process Response Code Does the Read Log Period span more than 31 days? For an on-demand request compare the Start Date Time and End Date Time to calculate the span. If this is more than 31 days raise an error. For a DSP scheduled request compare the Start Date Offset and End Date Offset to calculate the span. If this is more than 31 days raise an error. Table Validation checks E Sample Request Page 131 of 239

132 A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns =" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.8</ServiceReference> <ServiceReferenceVariant>4.8.3</ServiceReferenceVariant> </Header> <Body> <ReadExportProfileData> <ProfileDataLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </ProfileDataLogPeriodReadLogPeriod> </ReadExportProfileData> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Formatted Table Figure Sample Read Export Profile Data Service Request Format (Adhoc) Responses The Service Response messages for a The repsonseresponse messages for a Read Export Profile Data Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Page 132 of 239

133 Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the device. When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Unsuccessful Response The Response Codes specific to this Service Request are: Response Code Response Code Name Response Code Type Description E Failed Validation Date Span invalid Error The Date span in the request is for more than 31 days. Table 104 Failed Read Export Profile Data Service Request Response Codes Response & Alert Common Interface Format Format - ReadExportProfileDataRsp Formatted: Heading 6, No bullets or numbering Page 133 of 239

134 Formatted: Font: Not Italic, Font color: Auto Formatted: Keep with next Formatted: Font: Not Italic Figure Read Export Profile Data Parse Response Structure Formatted: Caption, Justified Note: LogEntry Maximum A value of 4464 is considered as Unbounded by the XSD validation Specific Header Data Items Data Item Electricity Response Formatted: Heading 6, No bullets or numbering Formatted Table GBCSHexadecimalMessageCode 0036 GBCSUseCaseNumber ECS22a GBCSUseCaseName Read Electricity Half Hour Profile Data (export) Table Read Export Profile Data Parse Response Header Data Items Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted: Caption, No bullets or numbering Formatted Table ActiveEnergyExport edvalue The total active energy exported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases) xs:integer None Nonsensitive Page 134 of 239

135 Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table ReactiveEnergyExp ortedvalue The total reactive energy exported in this 30 minute period (if a twin element meter, this is for the primary element; if on a polyphase meter, it is cumulative across the phases) xs:integer None Nonsensitive Timestamp The date-time stamp at the end of the period to which the value relates xs:datetime None N/A Nonsensitive Table Read Export Profile Data Parse Response Body Data Items Formatted: Keep with next Figure 98 - Read Export Profile Data Parse Response Specific Data Items Formatted: Caption Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ns1=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>36</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs22a</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Electricity Half Hour Profile Data (export)</ra:gbcsusecasename> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readexportprofiledatarsp MessageSuccess="true"> <ra:logentry> <ra:activeenergyexportedvalue>10</ra:activeenergyexportedvalue> <ra:reactiveenergyexportedvalue>5</ra:reactiveenergyexportedvalue> <ra:timestamp> t00:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeenergyexportedvalue>20</ra:activeenergyexportedvalue> <ra:reactiveenergyexportedvalue>10</ra:reactiveenergyexportedvalue> <ra:timestamp> t00:30:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeenergyexportedvalue>30</ra:activeenergyexportedvalue> <ra:reactiveenergyexportedvalue>15</ra:reactiveenergyexportedvalue> <ra:timestamp> t01:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeenergyexportedvalue>40</ra:activeenergyexportedvalue> <ra:reactiveenergyexportedvalue>20</ra:reactiveenergyexportedvalue> <ra:timestamp> t01:30:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeenergyexportedvalue>50</ra:activeenergyexportedvalue> <ra:reactiveenergyexportedvalue>25</ra:reactiveenergyexportedvalue> <ra:timestamp> t02:00:00.0</ra:timestamp> </ra:logentry> <ra:logentry> <ra:activeenergyexportedvalue>60</ra:activeenergyexportedvalue> <ra:reactiveenergyexportedvalue>30</ra:reactiveenergyexportedvalue> <ra:timestamp> t02:30:00.0</ra:timestamp> </ra:logentry> </ra:readexportprofiledatarsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Export Profile Data Parse Response Sample Formatted: Heading 6, No bullets or numbering Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Text 1 Formatted: Keep with next Formatted Table Formatted: Font color: Text 1 Formatted: Caption Page 135 of 239

136 Formatted: Caption The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Section 4.9 This section has been intentionally left blank as there is no Service Reference Read Network Data (4.10) Service Request Name ReadINetworkData Service Reference 4.10 Service Request Variant Name ReadINetworkData Service Reference Variant 4.10 Service Request Objective Business Context Statement To allow a DCC Service User to retrieveretrieveto enable a DCC Service User to read stored power quality data from a device atdevice for a specified Device ID. The DCC Service User wishes to review the power quality data logs of a particular device (e.g. 6 minute gas sampling or Average RMS power) Formatted: Default, Space After: 0 Formatted: Font: 9 pt, Not Italic Formatted: Font: 9 pt, Not Italic User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Electricity Network Operator (ENO) Gas Network Operator (GNO) Security Classification Service Request Narrative Non-critical and non-sensitive for Electricity and response sensitive for Gas: GBCS XREF: SME.C.NC 1. For Gas, this Service Request reads the Network Data Log values from the GSME as defined in SMETS. A log capable of storing a period of up to 4 hours of consumption data recorded at 6 minute intervals on the Network Data Log can be read (total of 40 entries recorded in the Device). This data is recorded on the Network Data Log via Service Request 14.1 (Record Network Data (GAS)). See Annex section For Electricity, this Service Request reads the following data items as defined in SMETS - AverageRMSUnderVoltageCounter - AverageRMSOverVoltageCounter - AverageRMSVoltageProfileDataLog - A log capable of storing 4320 entries (including the UTC date and time at the end of the period to which the value relates) comprising the averaged RMS voltage for each Average RNS Voltage MeasuermentMeasurement Period arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten. Page 136 of 239 Formatted Table

137 3. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. 4. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. In the case of Import Supplier or Network Operator, this could be the current or the old Registered Supplier. 5. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. 6. For Electricity, the response content depends on whether the Meter is Single or Poly Phase. 7. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. 8. Because this Service Request (Gas) returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. 1. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. In the case of Import Supplier, this could be the current or the old Registered Supplier. Formatted: Normal, No bullets or numbering Formatted: Normal, Space After: 0 pt, No bullets or numbering DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. In the case of Import Supplier, this will never be the old Registered Supplier. For Electricity, the response content depends on whether the Meter is Single or Poly Phase. For Gas, a period of up to 4 hours of consumption data recorded at 6 minute intervals on the Network Data Log can be read. This data is recorded on the Network Data Log via Service Request 14.1 (Record Network Data (GAS)). See Annex section This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. Table Read Network Data Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Page 137 of 239

138 Ad-hoc: Its ReadNetworkData XML element defines this Service Request and contains the date-time interval for which the logs are to be retrieved, for URP the Key Agreement Public Security Credentials and, for Future Dated, the Execution Date Time. Page 138 of 239

139 Formatted: Font: Not Italic Figure Read Network Data Service Request Structure (Ad-hoc) Page 139 of 239

140 Create Schedule: Its DSPReadNetworkData XML element defines this Service Request and contains the date-time interval for which the log is to be read, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition. Formatted: Font: Not Italic Formatted: Font: (Default) Times New Roman, 0 pt, Not Italic, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Figure Read Network Data Service Request Structure (Create Schedule) Formatted: Font: Not Italic Formatted: Caption Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadNetworkData (Ad-hoc) Formatted: Heading 6 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the Device ID xs:datetime No None UTC Date- Time Non- Valid date-time in the future Page 140 of 239

141 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ReadLogPeriod The Start and End Date-Times for which the data is required. Note that for requests targeted at GSME, this date range must surround the 4 hour period. sr:readlogperiod (see Annex section 17 for details) Yes None N/A Non- KAPublicSecurityCreden tials The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Gas Network Operator) xs:base64binary User Role EIS, GIS, ENO: N/A User Role GNO: Table Read Network Data Service Request Data Items (Ad-hoc) Yes None N/A Non The data items contained in the Service Request are defined in section. Formatted: Normal Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future xs:datetime No None UTC Date- Time Non- NetworkDataLogPeriod The Start and End Date-Times for which the data is required sr:readlogperiod (see Annex section 17 for details) Table 51 Read Network Data Service Request Data Items (Ad-hoc) Yes None N/A Non DSPReadNetworkData (Create Schedule) Formatted: Heading 6 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity DSPNetworkDataLog PeriodOffsetReadLog PeriodOffset The Start and End Date Offsets from the current date and the Start and End Times which together define the datetime period for which the data is required sr:readlogperiod Offset (see Annex section 17 for details) Yes None N/A Non- Table Read Network Data Service Request Data Items (Create Schedule) Formatted: Space After: 0 pt Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Read Network Data Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Page 141 of 239

142 Validation CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Network Data Command Variant Values (Ad-hoc) This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time and Read Log Period (NetworkDataLogPeriod) validation. Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSPNetworkDataLogPeriodOffset) validation Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 142 of 239

143 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID>11-EE </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.10</ServiceReference> <ServiceReferenceVariant>4.10</ServiceReferenceVariant> </Header> <Body> <ReadNetworkData> <NetworkDataLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </NetworkDataLogPeriodReadLogPeriod> </ReadNetworkData> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Network Data Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Network Data Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface. Page 143 of 239

144 See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the device. Formatted: Normal, No bullets or numbering When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadNetworkDataRsp Formatted: Heading 4, Outline numbered + Level: 4 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Tab after: 1.5 cm + Indent at: 1.5 cm Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Figure Read Network Data Parse Response Structure Page 144 of 239

145 Formatted: Font: Not Italic Formatted: Normal, Left Figure Read Network Data Parse Response Electricity Single Phase ESME Structure Formatted: Centered Formatted: Font: Not Italic Formatted: Normal, Left Figure Read Network Data Parse Response Electricity Poly Phase ESME Structure Formatted: Centered Page 145 of 239

146 Formatted: Font: Not Italic Figure Read Network Data Parse Response Gas Network Data Log Structure Formatted: Normal, Left Specific Header Data Items Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode 0039 GBCSUseCaseNumber GBCSUseCaseName 00BC ECS23 ECS23b Read Voltage Operational Data Read Voltage Operational Data 3 Phase 0079 GCS18 Read Gas Network Data Log Table Read Network Data Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 5 Data Item Description / Valid Set Type Default Units Sensitivity SinglePhaseESME PolyPhaseESME NetworkDataLog Voltage operational data for the single phase of an Electricity Single Phase Meter or for each of the 3 phases in a Poly Phase Meter Voltage operational data for each of the 3 phases of an Electricity Poly Phase Meter Network Data Log Gas Only ra:voltageoperationalda ta (see section ) ra:voltagepolyphasees ME (see section ) ra:gasnetworkdatalog (see section ) None N/A Non- None N/A Non- None N/A Table Read Network Data Parse Response Body Data Items Figure Read Network Data Parse Response Specific Data Items Formatted: Keep with next VoltageOperationalData Specific Data Items Formatted: Heading 5 Data Item Description / Valid Set Type Default Units Sensitivity Page 146 of 239

147 Data Item Description / Valid Set Type Default Units Sensitivity AvgRMSOverVoltag ecountervalue AvgRMSOverVoltag ecounterunit AvgRMSUnderVolta gecountervalue AvgRMSUnderVolta gecounterunit AvgRMSVoltageProf iledatalog The Average RMS Over Voltage Counter since last reset The Average RMS Over Voltage Counter Unit Valid set: 255: No units The Average RMS Under Voltage Counter since last reset The Average RMS Under Voltage Counter Unit Valid set: 255: No units A log capable of storing 4320 entries (including the UTC date and time at the end of the period to which the value relates) comprising the averaged RMS voltage for each Average RMS Voltage Measurement Period arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten xs: decimalnonnegativeinte ger None N/A Non- xs:string None N/A Non- xs: decimalnonnegativeinte ger None N/A Non- xs:string None N/A Non- Ra:AvgRMSVoltageProfi ledatalog (see section ) None N/A Non- Table Read Network Data Parse Response- VoltageOperationalData Specific Data Items Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font: 8 pt, Not Italic, Font color: Text 1 Formatted: Keep with next Figure Read Network Data Parse Response- VoltageOperationalData Specific Data Items AvgRMSVoltageProfileDataLog Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity LogEntry.Value 1 The Average RMS Value measured xs:integer None Volts Non- LogEntry.Timestamp 1 MeasurementPeriod The date-time at the end of the corresponding measurement period The period in seconds over which the average RMS is averaged xs:datetime None UTC Date- Time xs:nonnegativeinteger None Secon ds Table Read Network Data Parse Response - AvgRMSVoltageProfileDataLog Specific Data Items Figure Read Network Data Parse Response - AvgRMSVoltageProfileDataLog Specific Data Items Non- Non- 1 Maximum 4320 Log Entries. Note that a value of 4320 is considered as Unbounded by the XSD validation Formatted: Font: Arial Bold, 9 pt, Bold, Not Italic, Font color: Custom Color(RGB(41,35,92)) Formatted Table Formatted: Font: Not Bold, Font color: Auto, Superscript Formatted: Font: 8 pt, Not Italic, Font color: Text 1 Formatted: Font: 8 pt, Not Italic, Font color: Text 1 Formatted: Font: 8 pt, Not Italic, Font color: Text 1 Formatted: Keep with next Field Code Changed Formatted: Normal VoltagePolyPhaseESME Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Page 147 of 239

148 Data Item Description / Valid Set Type Default Units Sensitivity PhaseVoltageOpera tionaldata 1 The Voltage Operational Data for each of the 3 phases ra:phasevoltageoperati onaldata (see section ) None N/A Non- Table Read Network Data Parse Response - VoltagePolyPhaseESME Specific Data Items Formatted: Keep with next Formatted: Font: Not Bold, Font color: Auto, Superscript Figure Read Network Data Parse Response - VoltagePolyPhaseESME Specific Data Items 1 Maximum 3 (one per phase) when the response is successful Formatted: Normal PhaseVoltageOperationalData Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity VoltageOperational Data The Voltage Operational Data for each of the 3 phases ra:voltageoperationalda ta (see section ) None N/A Non- Phase Each of the 3 phases in the Meter Valid set: Value between 1 and 3 Restriction of xs:positiveinteger (mininclusive = 1, maxinclusive = 3) Table Read Network Data Parse Response - PhaseVoltageOperationalData Specific Data Items None N/A Non- Formatted: Keep with next Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Figure Read Network Data Parse Response - PhaseVoltageOperationalData Specific Data Items GasNetworkDataLog Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table LogEntry.Value 1 Log of consumption data taken at 6- minute intervals over a 4-hour period: values xs:integer None kwh Formatted: Font: 8 pt, Not Italic, Font color: Text 1 LogEntry.Timestamp 1 The date-time at the end of the corresponding measurement period xs:datetime None UTC Date- Time Table Read Network Data Parse Response - GasNetworkDataLog Specific Data Items Formatted: Keep with next Formatted: Font: Not Bold, Font color: Auto, Highlight Figure Read Network Data Parse Response - GasNetworkDataLog Specific Data Items 1 Maximum 40 Formatted: Normal Sample Response Page 148 of 239

149 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>39</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs23</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Voltage Operational Data</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readnetworkdatarsp MessageSuccess="true"> <ra:electricity> <ra:singlephaseesme> <ra:avgrmsovervoltagecountervalue>10</ra:avgrmsovervoltagecountervalue> <ra:avgrmsundervoltagecountervalue>10</ra:avgrmsundervoltagecountervalue> <ra:avgrmsvoltageprofiledatalog> <ra:logentry> <ra:value>10</ra:value> <ra:timestamp> t00:01:00</ra:timestamp> </ra:logentry> <ra:measurementperiod>86400</ra:measurementperiod > </ra:avgrmsvoltageprofiledatalog> </ra:singlephaseesme> </ra:electricity> </ra:readnetworkdatarsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Network Data Parse Response Sample Single Phase ESME Formatted: Caption Formatted: Caption, No bullets or numbering Page 149 of 239

150 ncoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>bc</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs23b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Voltage Operational Data -3 Phase</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readnetworkdatarsp MessageSuccess="true"> <ra:electricity> <ra:polyphaseesme> <ra:phasevoltageoperationaldata> <ra:voltageoperationaldata> <ra:avgrmsovervoltagecountervalue>10</ra:avgrmsovervoltagecountervalue> <ra:avgrmsundervoltagecountervalue>10</ra:avgrmsundervoltagecountervalue> <ra:avgrmsvoltageprofiledatalog> <ra:logentry> <ra:value>10</ra:value> <ra:timestamp> t00:01:00</ra:timestamp> </ra:logentry> <ra:measurementperiod>86400</ra:measurementperiod > </ra:avgrmsvoltageprofiledatalog> </ra:voltageoperationaldata> <ra:phase>1</ra:phase> </ra:phasevoltageoperationaldata> <ra:phasevoltageoperationaldata> <ra:voltageoperationaldata> <ra:avgrmsovervoltagecountervalue>10</ra:avgrmsovervoltagecountervalue> <ra:avgrmsundervoltagecountervalue>10</ra:avgrmsundervoltagecountervalue> <ra:avgrmsvoltageprofiledatalog> <ra:logentry> <ra:value>7</ra:value> <ra:timestamp> t00:02:00</ra:timestamp> </ra:logentry> <ra:measurementperiod>86400</ra:measurementperiod > </ra:avgrmsvoltageprofiledatalog> </ra:voltageoperationaldata> <ra:phase>2</ra:phase> </ra:phasevoltageoperationaldata> <ra:phasevoltageoperationaldata> <ra:voltageoperationaldata> <ra:avgrmsovervoltagecountervalue>10</ra:avgrmsovervoltagecountervalue> <ra:avgrmsundervoltagecountervalue>10</ra:avgrmsundervoltagecountervalue> <ra:avgrmsvoltageprofiledatalog> <ra:logentry> <ra:value>5</ra:value> <ra:timestamp> t00:03:00</ra:timestamp> </ra:logentry> <ra:measurementperiod>86400</ra:measurementperiod > </ra:avgrmsvoltageprofiledatalog> </ra:voltageoperationaldata> <ra:phase>3</ra:phase> </ra:phasevoltageoperationaldata> </ra:polyphaseesme> </ra:electricity> </ra:readnetworkdatarsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Network Data Parse Response Sample Poly Phase ESME Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: Arial, 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Page 150 of 239

151 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>79</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs18</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Gas Network Data Log</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readnetworkdatarsp MessageSuccess="true"> <ra:gas> <ra:networkdatalog> <ra:logentry> <ra:value>10</ra:value> <ra:timestamp> t00:01:00</ra:timestamp> </ra:logentry> </ra:networkdatalog> </ra:gas> </ra:readnetworkdatarsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Network Data Parse Response Sample GasThe output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Formatted: Caption 18.2 Read Tariff (4.11) Service Request definition differs from that in the SEC2 Consultation to align with GBCS UCs, because this Service Request maps to two Electricity and one Gas GBCS Use Cases and each Use Case requires its own Request ID. Therefore the 4.11 Service Request has been broken into two parts: (Primary Element) applicable to Electricity and Gas and (Secondary Element) applicable to Electricity Twin Element Smart Meter Read Tariff (Primary Element) (4.11.1) Formatted: Font: Not Italic, Font color: Text 1 Formatted: Normal Formatted: Font: Not Italic, Font color: Text 1 Formatted: Font color: Text 1 Service Request Name ReadTariff Service Reference 4.11 Service Request Variant Name ReadTariff(PrimaryElement) Service Reference Variant Service Request Objective Business Context Statement To enable a DCC Service User to read the current tariff settings (including price, time of use matrix and time of use blocks) that are in use on a meter, in addition to the payment mode. The DCC Service User requires a view of the tariff deployed to a device to resolve a customer query. Page 151 of 239

152 User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Other User (OU) Security Classification Service Request Narrative Non-critical and non-sensitive: GBCS XREF: SME.C.NC 1. This Service Request returns all the current tariff settings available at the Primary Element of the metermeter. It isn t possible to request a subset of them. 2. For reading the instantaneous import energy registerstariff values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not avialableavailable for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS and OU (Electricity). Formatted: List Paragraph, None, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: List Paragraph, Indent: Left: 0.63 cm Table Read Tariff (Primary Element) Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its ReadTariffPrimaryElement XML element defines this Service Request and doesn t contain any data items. Formatted: Heading 4, Outline numbered + Level: 4 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Tab after: 1.5 cm + Indent at: 1.5 cm Formatted: Heading 5, No bullets or numbering Formatted: Font color: Blue Formatted: Centered Figure Read Tariff (Primary Element) Service Request Structure Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No No No Table Read Tariff (Primary Element) Modes of Operation Formatted: Heading 5, No bullets or numbering Formatted: Space After: 0 pt Formatted Table Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values Page 152 of 239 Formatted: Heading 5, No bullets or numbering

153 The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Tariff (Primary Element) Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Formatted: Heading 5, No bullets or numbering Formatted: Heading 5, No bullets or numbering <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID>11-EE </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.11</ServiceReference> <ServiceReferenceVariant>4.11.1</ServiceReferenceVariant> </Header> <Body> <ReadTariffPrimaryElement/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Tariff (Primary Element) Service Request Format Page 153 of 239 Formatted: Font: Arial, 7.5 pt, Not Italic, Font color: Auto Formatted: Font: Arial, 7.5 pt, Not Italic, Font color: Auto Formatted: Font: Arial, 7.5 pt, Not Italic, Font color: Auto Formatted: Font: Arial, 7.5 pt, Font color: Auto Formatted: Font: 7.5 pt

154 Responses The Service Response messages for a The repsonseresponse messages for a Read Tariff (Primary Element) Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Formatted: Heading 4, Outline numbered + Level: 4 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Tab after: 1.5 cm + Indent at: 1.5 cm Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface. See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadTariffPrimaryElementRsp Formatted: Heading 6 Formatted: Font: Arial, 9 pt, Not Bold, Not Italic, Font color: Auto Figure Read Tariff Primary Element Parse Response Structure Formatted: Centered Page 154 of 239

155 Formatted: Font: Not Italic Formatted: Normal, Left Figure Read Tariff Primary Element Parse Response Electricity Structure Formatted: Centered Formatted: Font: Not Italic Formatted: Normal, Left Figure Read Tariff Primary Element Parse Response Electricity TariffBlockPriceMatrixPrimaryElementStructure Page 155 of 239

156 Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Electricity TariffTOUPriceMatrixStructure Formatted: Normal Formatted: Font: Not Italic Formatted: Normal, Left Figure Read Tariff Primary Element Parse Response Electricity TariffSwitchingTableStructure Formatted: Font: Not Bold, Not Italic, Font color: Auto Figure Read Tariff Primary Element Parse Response Electricity Day Profiles Structure Page 156 of 239

157 Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Electricity Week Profiles Structure Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Electricity Season Profiles Structure Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Electricity TariffSwitchingTableSpecialDays Structure Page 157 of 239

158 Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Electricity TariffThresholdMatrix Structure Formatted: Centered Formatted: Font: Not Italic Formatted: Normal, Left Figure Read Tariff Primary Element Parse Response Gas Structure Formatted: Centered Page 158 of 239

159 Formatted: Font: Not Italic Formatted: Normal, Left Figure Read Tariff Primary Element Parse Response Gas TariffSwitchingTable Structure Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Gas DayProfiles Structure Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Gas WeekProfiles Structure Page 159 of 239

160 Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Gas Seasons Structure Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Primary Element Parse Response Gas TariffSwitchingTableSpcialDays Structure Formatted: Normal Formatted: Font: Not Italic Figure Read Tariff Primary Element Parse Response Gas TariffThresholdMatrix Structure Formatted: Font: Not Italic Formatted: Normal Page 160 of 239

161 Figure Read Tariff Primary Element Parse Response Gas TariffTOUPriceMatrix Structure Specific Header Data Items Formatted: Centered Formatted: Heading 6, Left Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode 003A 009F GBCSUseCaseNumber ECS24 GCS21f GBCSUseCaseName Read ESME Tariff Data Read GSME Tariff Data Table Read Tariff Primary Element Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity PrimaryActiveTariffP rice Number representing the price in currency units per Wh consumed Electricity Only xs:nonnegativeinteger None 1000 th pence per Wh Non- Formatted: Font: 8 pt, Not Italic Formatted: Normal, Space After: 0 Formatted: Font: Not Italic, Superscript BlockDailyReset If set to Enabled the Electricity Smart Meter will reset the counters in the Tariff Block Counter Matrix once per Day and in accordance with the timetable set-out in the Billing Calendar Restriction of xs:string (Enumeration) None N/A Non- Valid set: Enabled Not Enabled Electricity Only Formatted: List Paragraph, Space After: 3 pt, Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font: 8 pt, Not Italic CurrencyUnitsLabel The Currency Units currently used by a Smart Meter for display purposes, which shall be GB Pounds Valid set: Restriction of xs:string (Enumeration) GBP N/A Non- Formatted: Font: 8 pt, Font color: Auto CurrencyUnitsName GBP. GB Pounds Electricity and Gas The Currency Units currently used by a Smart Meter for display purposes, which shall be GB Pounds Valid set: Restriction of xs:string (Enumeration) 1000th pence N/A Non- Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font: Millipence th pence Electricity Only Formatted: Font: Not Italic, Superscript StandingCharge A charge to be levied in Currency Units per unit time when operating in Credit Mode and Prepayment Mode Valid set: xs:nonnegativeinteger None 1000 th pence per day Non- Formatted: Font: Not Italic Formatted: Font: Not Bold, Font color: Auto, Highlight >= 0 Electricity and Gas Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Page 161 of 239

162 Data Item Description / Valid Set Type Default Units Sensitivity Electricity Electricity Smart Meter: A 4 x 8 TariffBlockPriceMatri matrix containing prices for Block x 1 Pricing Electricity Only ra:electricitytariffblockp ricematrixprimaryeleme nt 2 (see Annex section for sr:electricitytariffblockp ricematrixprimaryeleme nt) None N/A Non- Formatted: Font: Not Bold, Superscript Formatted: Font: Not Bold, Font color: Auto, Superscript Electricity Electricity Smart Meter: A 1 x 48 TariffTOUPriceMatri matrix containing prices for Time-ofuse x 3 Pricing Electricity Only ra:electricitytarifftoupri cematrix 2 (see Annex section for sr:electricitytarifftoupri cematrix) None N/A Non- Electricity TariffSwitchingTable A calendar defining UTC times, days and dates for switching the Primary Element tariff Electricity Only ra: TariffSwitchingTablePri maryelement 2 (see Annex section for sr: TariffSwitchingTablePri maryelement) None N/A Non- Formatted: Font: Not Bold, Font color: Auto, Superscript Electricity TariffSwitchingTable SpecialDays A calendar defining special dates for switching the Primary Element tariff Electricity Only ra: TariffSwitchingTableSpe cialdaysprimaryelement 2 (see Annex section for sr: TariffSwitchingTableSpe cialdaysprimaryelement ) None N/A Non- Formatted: Font: Not Bold, Font color: Auto, Superscript Electricity TariffThesholdMatrix A 3 (thresholds) x 8 (rows) matrix capable of holding thresholds for controlling Block Tariffs. Electricity Only ra:electricitytariffthresh oldmatrix 2 (see Annex section for sr: ElectricityTariffThreshold Matrix) None N/A Non- Formatted: Font: Not Bold, Font color: Auto, Superscript Gas TariffBlockPriceMatri xscaler Price Trailing Digit: 0x0617 Gas Only xs:nonnegativeinteger None N/A Non- Formatted: Font: 8 pt, Not Italic Gas TariffSwitchingTable A calendar defining UTC times, days and dates for switching the tariff ra: GasTariffSwitchingTable 2 None N/A Non- Gas Only (see Annex section for sr: GasTariffSwitchingTable ) Gas TariffSwitchingTable SpecialDays A calendar defining special dates for switching the Primary Element tariff Gas Only ra: GasTariffSwitchingTable SpecialDays 2 (see Annex section 1.1.1) for sr: GasTariffSwitchingTable SpecialDays) None N/A Non- GasTariffThesholdM atrix A 3 x 1 matrix capable of holding thresholds for controlling Block Tariffs Gas Only ra:gastariffthresholdm atrix 2 (see Annex section for sr:gastariffthresholdma trix) None N/A Non- Page 162 of 239

163 Data Item Description / Valid Set Type Default Units Sensitivity GasTariffTOUPrice Matrix 4 Gas Smart Meter: A 1 x 4 matrix containing Prices for Time-of-use Pricing Gas Only ra:gastarifftoupricema trix 2 (see Annex section for sr:gastarifftoupricema trix) None N/A Non- Formatted: Font: Not Bold, Font color: Auto, Superscript TariffType The Tariff type in operation, being Time-of-use or Time-of-use with Block. Restriction of xs:string (Enumeration) None N/A Non- Formatted: Keep with next Valid Set: TOU TOU With Block Table Read Tariff Primary Element Parse Response Body Data Items Figure Read Tariff Primary Element Parse Response Specific Data Items 1 Maximum 8 Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font: 8 pt, Not Italic Formatted: Font: 8 pt Formatted: Normal 2 ra: data type is identical to the corresponding sr: data type, except that in ra: all the components are optional 3 Maximum 48 4 Maximum Sample Response Formatted: Heading 6 Page 163 of 239

164 encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>3a</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs24</ra:gbcsusecasenumber> <ra:gbcsusecasename> Read ESME Tariff Data</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readtariffprimaryelementrsp MessageSuccess="true"> <ra:electricity> <ra:primaryactivetariffprice>100</ra:primaryactivetariffprice> <ra:blockdailyreset>enabled</ra:blockdailyreset> <ra:currencyunitslabel>gbp</ra:currencyunitslabel> <ra:currencyunitsname>millipence</ra:currencyunitsname> <ra:standingcharge>5000</ra:standingcharge> <ra:tariffblockpricematrix index= "1"> <ra:blockprices> <ra:price index="1">2000</ra:price> <ra:price index="2">2500</ra:price> <ra:price index="3">3000</ra:price> <ra:price index="4">4000</ra:price> </ra:blockprices> <ra:associatedtouwithblocktariffaction>101</ra:associatedtouwithblocktariffaction> </ra:tariffblockpricematrix> <ra:tariffblockpricematrix index= "2"> <ra:blockprices> <ra:price index="1">5000</ra:price> <ra:price index="2">5500</ra:price> <ra:price index="3">6000</ra:price> <ra:price index="4">7000</ra:price> </ra:blockprices> <ra:associatedtouwithblocktariffaction>102</ra:associatedtouwithblocktariffaction> </ra:tariffblockpricematrix> <ra:tarifftoupricematrix index= "1"> <ra:tarifftouprice>2000</ra:tarifftouprice> <ra:associatedtoutariffaction>08</ra:associatedtoutariffaction> </ra:tarifftoupricematrix> <ra:tarifftoupricematrix index= "2"> <ra:tarifftouprice>2500</ra:tarifftouprice> <ra:associatedtoutariffaction>03</ra:associatedtoutariffaction> </ra:tarifftoupricematrix> See Figure 114Figure 114Figure 114Figure 114Figure 138 for details of ElectricityTariff Switching Tables <ra:tariffthresholdmatrix> <ra:electricitytariffthresholds index= "1"> <ra:blockthreshold index= "1">10</ra:BlockThreshold> <ra:blockthreshold index= "2">20</ra:BlockThreshold> <ra:blockthreshold index= "3">30</ra:BlockThreshold> <ra:associatedtouwithblocktariffaction>103</ra:associatedtouwithblocktariffaction> </ra:electricitytariffthresholds> </ra:tariffthresholdmatrix> </ra:electricity> </ra:readtariffprimaryelementrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Tariff Primary Element Parse Response Sample - Electricity Page 164 of 239 Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Italic, Font color: Auto

165 <ra:tariffswitchingtable> <ra:dayprofiles> <ra:dayprofile index= "1"> <ra:day>01</ra:day> <ra:profileschedule index= "1"> <ra:starttime>00:00:00</ra:starttime> <ra:toutariffaction>01</ra:toutariffaction> </ra:profileschedule> </ra:dayprofile> <ra:dayprofile index= "2"> <ra:day>02</ra:day> <ra:profileschedule index= "2"> <ra:starttime>00:00:00</ra:starttime> <ra:toutariffaction>03</ra:toutariffaction> </ra:profileschedule> </ra:dayprofile> </ra:dayprofiles> <ra:weekprofiles> <ra:weekprofile index= "1"> <ra:weekname>01</ra:weekname> <ra:referencedelecday index= "1">1</ra:ReferencedElecDay> <ra:referencedelecday index= "2">1</ra:ReferencedElecDay> <ra:referencedelecday index= "3">1</ra:ReferencedElecDay> <ra:referencedelecday index= "4">1</ra:ReferencedElecDay> <ra:referencedelecday index= "5">1</ra:ReferencedElecDay> <ra:referencedelecday index= "6">2</ra:ReferencedElecDay> <ra:referencedelecday index= "7">2</ra:ReferencedElecDay> </ra:weekprofile> </ra:weekprofiles> <ra:seasons> <ra:season index= "1"> <ra:seasonname>spring</ra:seasonname> <ra:seasonstartdate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>3</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>1</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:seasonstartdate> <ra:referencedweekname index= "1">01</ra:ReferencedWeekName> </ra:season> </ra:seasons> </ra:tariffswitchingtable> <ra:tariffswitchingtablespecialdays> <ra:specialday index= "1"> <ra:date> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>12</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>25</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:date> <ra:referencedday>02</ra:referencedday> </ra:specialday> </ra:tariffswitchingtablespecialdays> Formatted: Font: 8 pt, Not Italic, Font color: Auto Formatted Table Figure Read Tariff Primary Element Parse Response Sample Electricity Tariff Switching Tables Page 165 of 239

166 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>9f</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs21f</ra:gbcsusecasenumber> <ra:gbcsusecasename> Read GSME Tariff Data</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readtariffprimaryelementrsp MessageSuccess="true"> <ra:gas> <ra:currencyunitslabel>gbp</ra:currencyunitslabel> <ra:standingcharge>5000</ra:standingcharge> <ra:tariffblockpricematrixscaler>100</ra:tariffblockpricematrixscaler> See Figure 116Figure 116Figure 116Figure 116Figure 140 for details of Gas Tariff Switching Tables <ra:tariffthresholdmatrix> <ra:blockthreshold index= "1">10</ra:BlockThreshold> <ra:blockthreshold index= "2">20</ra:BlockThreshold> <ra:blockthreshold index= "3">30</ra:BlockThreshold> <ra:associatedtouwithblocktariffaction>101</ra:associatedtouwithblocktariffaction> </ra:tariffthresholdmatrix> <ra:tarifftoupricematrix index= "1"> <ra:tarifftouprice>2700</ra:tarifftouprice> <ra:associatedtoutariffaction>03</ra:associatedtoutariffaction> </ra:tarifftoupricematrix> <ra:tarifftoupricematrix index= "2"> <ra:tarifftouprice>4500</ra:tarifftouprice> <ra:associatedtoutariffaction>04</ra:associatedtoutariffaction> </ra:tarifftoupricematrix> <ra:tarifftype>tou</ra:tarifftype> </ra:gas> </ra:readtariffprimaryelementrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Tariff Primary Element Parse Response Sample - Gas Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Bold, Not Italic, Font color: Auto Page 166 of 239

167 <ra:tariffswitchingtable> <ra:dayprofiles> <ra:dayprofile index= "1"> <ra:day>01</ra:day> <ra:profileschedule> <ra:starttime>00:00:00</ra:starttime> <ra:toutariffaction>01</ra:toutariffaction> </ra:profileschedule> </ra:dayprofile> <ra:dayprofile index= "2"> <ra:day>02</ra:day> <ra:profileschedule> <ra:starttime>00:00:00</ra:starttime> <ra:toutariffaction>03</ra:toutariffaction> </ra:profileschedule> </ra:dayprofile> </ra:dayprofiles> <ra:weekprofiles> <ra:weekprofile index= "1"> <ra:weekname>01</ra:weekname> <ra:referencedday index= "1">1</ra:ReferencedDay> <ra:referencedday index= "2">1</ra:ReferencedDay> <ra:referencedday index= "3">1</ra:ReferencedDay> <ra:referencedday index= "4">1</ra:ReferencedDay> <ra:referencedday index= "5">1</ra:ReferencedDay> <ra:referencedday index= "6">2</ra:ReferencedDay> <ra:referencedday index= "7">2</ra:ReferencedDay> </ra:weekprofile> </ra:weekprofiles> <ra:seasons> <ra:season index= "1"> <ra:seasonname>spring</ra:seasonname> <ra:seasonstartdate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>3</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>1</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:seasonstartdate> <ra:referencedweekname index= "1">01</ra:ReferencedWeekName> </ra:season> </ra:seasons> </ra:tariffswitchingtable> <ra:tariffswitchingtablespecialdays> <ra:specialday index= "1"> <ra:date> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>12</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>25</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:date> <ra:referencedday>02</ra:referencedday> </ra:specialday> </ra:tariffswitchingtablespecialdays> Figure Read Tariff Primary Element Parse Response Sample Gas Tariff Switching Tables Page 167 of 239 Formatted: Normal, No bullets or numbering

168 The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Read Tariff (Secondary Element) (4.11.2) Service Request Name ReadTariff Service Reference 4.11 Service Request Variant Name ReadTariff(SecondaryElement) Service Reference Variant Service Request Objective Business Context Statement To enable a DCC Service User to read the current tariff settings (including price, time of use matrix and time of use blocks) that are in use on a Twin Element Electricity Smart Meter. The DCC Service User requires a view of the tariff deployed to a device to resolve a customer query. User Role Access Electricity Import Supplier (EIS) Other User (OU) Security Classification Service Request Narrative Non-critical and non-sensitive: GBCS XREF: SME.C.NC 1. This Service Request returns all the current tariff settings available at the Secondary Element of the Meter. It isn t possible to request a subset of them. 2. Service Reference Grouping is applicable to this Service Reference Variant for User Role EIS and OU (Electricity). Formatted: Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Table Read Tariff (Secondary Element) Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The ServiceRequest Body XMLThe Request Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests. Its ReadTariffSecondaryElement XML element defines this Service Request and doesn t contain any data items. Formatted: Font: Font color: Blue Figure Read Tariff (Secondary Element) Service Request Structure Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Page 168 of 239

169 Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No No No Table Read Tariff (Secondary Element) Modes of Operation Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Tariff (Secondary Element) Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: ncoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <Header> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <CommandVariant>1</CommandVariant> <ServiceReference>4.11</ServiceReference> <ServiceReferenceVariant>4.11.2</ServiceReferenceVariant> </Header> <Body> <ReadTariffSecondaryElement/> </Body> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> </ServiceRequest> Figure Sample Read Tariff (Secondary Element) Service Request Format Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Page 169 of 239

170 Responses The Service Response messages for a The repsonseresponse messages for a Read Tariff (Secondary Element) Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface. See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface FormatFormat Format - ReadTariffSecondaryElementRsp Formatted: Heading 5, Space After: 0 pt, No bullets or numbering Formatted: Heading 6 Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Figure Read Tariff Secondary Element Parse Response Structure Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Figure Read Tariff Secondary Element Parse Response TariffSwitchingTable Structure Formatted: Caption Page 170 of 239

171 Formatted: Font: Not Italic Figure Read Tariff Secondary Element Parse Response DayProfiles Structure Formatted: Font: Not Italic Figure Read Tariff Secondary Element Parse Response WeekProfiles Structure Formatted: Font: Not Italic Formatted: Normal Figure Read Tariff Secondary Element Parse Response Seasons Structure Page 171 of 239

172 Formatted: Font: Not Bold, Not Italic, Font color: Auto Figure Read Tariff Secondary Element Parse Response TariffSwitchingTableSpecialDays Structure Specific Header Data Items Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode GBCSUseCaseNumber 00BD ECS24b GBCSUseCaseName Read ESME Tariff Data - second element Table Read Tariff Secondary Element Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity SecondaryActiveTari ffprice Number representing the price in currency units per Wh consumed xs:nonnegativeinteger None 1000 th pence per Wh Non- TariffTOUPriceMatri x 1 Twin Element Electricity Smart Meter: A 1 x 4 matrix containing prices for Time-of-use Pricing Tariffs relating to Supply via the secondary measuring element of the Electricity Meter ra:secondarytarifftoup ricetariff 2 (see Annex section for sr:secondarytarifftoup ricetariff) None N/A Non- Formatted: Font: Not Bold, Font color: Auto, Superscript TariffSwitchingTable TariffSwitchingTable SpecialDays A calendar defining UTC times, days and dates for switching the Secondary Element tariff A calendar defining special dates for switching the Secondary Element tariff ra: TariffSwitchingTableSec ondaryelement 2 (see Annex section for sr: TariffSwitchingTableSec ondaryelement ra: TariffSwitchingTableSpe cialdayssecondaryelem ent 1 (see Annex section for sr: TariffSwitchingTableSpe cialdayssecondaryelem ent) None N/A Non- None N/A Non- Table Read Tariff Secondary Element Parse Response Body Data Items Formatted: Keep with next Figure Read Tariff Secondary Element Parse Response Specific Data Items 1 Maximum 4 Page 172 of 239

173 2 ra: data type is identical to the corresponding sr: data type, except that in ra: all the components are optional Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>bd</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs24b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Tariff Data - second element</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readtariffsecondaryelementrsp MessageSuccess="true"> <ra:secondaryactivetariffprice>100</ra:secondaryactivetariffprice> <ra:tarifftoupricematrix index= "1"> <ra:tarifftouprice>2700</ra:tarifftouprice> <ra:associatedtoutariffaction>03</ra:associatedtoutariffaction> </ra:tarifftoupricematrix> <ra:tarifftoupricematrix index= "2"> <ra:tarifftouprice>4500</ra:tarifftouprice> <ra:associatedtoutariffaction>04</ra:associatedtoutariffaction> </ra:tarifftoupricematrix> See Figure 126Figure 126Figure 126Figure 126Figure 151 for details of Tariff Switching Tables </ra:readtariffsecondaryelementrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Tariff Secondary Element Parse Response Sample Page 173 of 239

174 <ra:tariffswitchingtable> <ra:dayprofiles> <ra:dayprofile index= "1"> <ra:day>01</ra:day> <ra:profileschedule index= "1"> <ra:starttime>00:00:00</ra:starttime> <ra:toutariffaction>01</ra:toutariffaction> </ra:profileschedule> </ra:dayprofile> <ra:dayprofile index= "2"> <ra:day>02</ra:day> <ra:profileschedule index= "2"> <ra:starttime>00:00:00</ra:starttime> <ra:toutariffaction>03</ra:toutariffaction> </ra:profileschedule> </ra:dayprofile> </ra:dayprofiles> <ra:weekprofiles> <ra:weekprofile index= "1"> <ra:weekname>01</ra:weekname> <ra:referencedelecday index= "1">1</ra:ReferencedElecDay> <ra:referencedelecday index= "2">1</ra:ReferencedElecDay> <ra:referencedelecday index= "3">1</ra:ReferencedElecDay> <ra:referencedelecday index= "4">1</ra:ReferencedElecDay> <ra:referencedelecday index= "5">1</ra:ReferencedElecDay> <ra:referencedelecday index= "6">2</ra:ReferencedElecDay> <ra:referencedelecday index= "7">2</ra:ReferencedElecDay> </ra:weekprofile> </ra:weekprofiles> <ra:seasons> <ra:season index= "1"> <ra:seasonname>spring</ra:seasonname> <ra:seasonstartdate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>3</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>1</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:seasonstartdate> <ra:referencedweekname index= "1">01</ra:ReferencedWeekName> </ra:season> </ra:seasons> </ra:tariffswitchingtable> <ra:tariffswitchingtablespecialdays> <ra:specialday index= "1"> <ra:date> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>12</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>25</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:date> <ra:referencedday>02</ra:referencedday> </ra:specialday> </ra:tariffswitchingtablespecialdays> Figure Read Tariff Secondary Element Parse Response Sample Tariff Switching Tables Page 174 of 239

175 Formatted: Indent: Left: 0 cm 18.3 Read Maximum Demand Registers (4.12) Service Request definition differs from that in the SEC2 Consultation to align with GBCS UCs, because thisthis Service Request maps to two GBCS Use Cases and each Use Case requires its own Request ID. Therefore the 4.12 Service Request has been broken into two parts: (Import) and (Export) Read Maximum Demand Import Registers (4.12.1) Service Request Name ReadIMaximumDemandRegisters Service Reference 4.12 Service Request Variant Name ReadIMaximumDemandImportRegisters Service Reference Variant Service Request Objective Business Context Statement To enable a DCC Service user to retrieve read the maximum demand import register values recorded on an ESME meter. The DCC Service user has conducted a network analysis survey for network planning purposes and wishes to retrieve maximum demand import register values. User Role Access Electricity Import Supplier (EIS) Electricity Network Operator (ENO) Security Classification Non-critical and non-sensitive: GBCS XREF: SME.C.NC 1. This Service Request returns all the Maximum Demand Import Registers available at the meter. It isn t possible to request a read for only a subset of them. Service Request Narrative 2. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule) Service Reference Grouping is applicable to this Service Reference Variant for User Role ENO. Table Read Maximum Demand Import Registers Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Page 175 of 239

176 Ad-hoc: Its ReadMaximumDemandImportRegisters XML element defines this Service Request and contains the Execution Date and Time. Formatted: Font: 8 pt, Bold, Not Italic Figure Read Maximum Demand Import Registers Service Request Structure (Ad-hoc) Create Schedule: Its DSPReadMaximumDemandImportRegisters XML element defines this Service Request and doesn t contain any data items. Formatted: Font: Not Italic Formatted: Centered Figure Read Maximum Demand Import Registers Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadIMaximumDemandmportRegisters (Ad-hoc) Formatted: Heading 6, Indent: Left: 0 cm Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future xs:datetime Yes None UTC Date- Time Table Read Maximum Demand Import Registers Service Request Data Items (Ad-hoc) Non DSPReadMaximumDemandImportRegisters (Create Schedule) N/A Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Page 176 of 239

177 Transform On Demand DCC Only Future Dated DSP Scheduled No YesNoNo No DSP Yes Table Read Maximum Demand Import Registers Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes YesNoNo YesNoNo No No No No No Table Read Maximum Demand Import Registers Command Variant Values (Ad-hoc) Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time validation Sample Request Sample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as followsa sample Service Request document is as follows: Page 177 of 239

178 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID>11-EE </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.12</ServiceReference> <ServiceReferenceVariant>4.12.1</ServiceReferenceVariant> </Header> <Body> <ReadMaximumDemandImportRegisters> <ExecutionDateTime> T02:05:00.0</ExecutionDateTime> </ReadMaximumDemandImportRegisters> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Maximum Demand Import Registers Service Request (Body) Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Rresponse messages for a Read Maximum Demand Import Registers Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Rrequest are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Response & Alert Common Interface When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below. Page 178 of 239

179 Response & Alert Common Interface Format Format - ReadMaximumDemandImportRegistersRsp Formatted: Heading 6 Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Figure Read Maximum Demand Import Registers Parse Response Structure Page 179 of 239

180 Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Figure Read Maximum Demand Import Registers Parse Response Read Maximum Demand Configurable Time Period Structure Specific Header Data Items Data Item Electricity Response Formatted: Heading 6 Formatted Table GBCSHexadecimalMessageCode GBCSUseCaseNumber 002C ECS18b GBCSUseCaseName Read Maximum Demand Registers (import) Table Read Maximum Demand Import Registers Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity Page 180 of 239

181 Data Item Description / Valid Set Type Default Units Sensitivity MaxDemandConfigu rabletimeactiveene rgyimport A store capable of holding the largest average value of Active Energy Import recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour) within the time period specified in Maximum Demand Configurable Time Period (including the UTC date and time at the end of the 30 minute period to which the data relates) since the value was last reset, together with the UTC date and time when the value was last reset, arranged such that the recording of a larger value shall cause the previous entry to be overwritten ra:maxdemandconfigur abletimeactiveenergyi mport (see section MaxDemandConfigurabl etimeactiveenergyimpo rt Specific Data ItemsMaxDemandConfig urabletimeactiveenergy Import Specific Data Items) None N/A Non- Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Field Code Changed Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto MaxDemandActiveE nergyimport A store capable of holding the largest average value of Active Energy Import recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour and including the UTC date and time at the end of the 30 minute period to which the data relates) since the value was last, together with the UTC date and time when the value was last reset, arranged such that the recording of a larger value shall cause the previous entry to be overwritten. ra:maxdemandregister DataType (see section MaxDemandRegisterDat atype Specific Data Items) None N/A Non- Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: 8 pt, Not Italic Field Code Changed MaxDemandConfigu rabletimeperiod 1 A single time period of up to 24 hours comprising a number of halfhour periods (commencing at the start of minutes 00 and 30 in each hour) during which recording to the Maximum Demand (Configurable Time) Active Energy Import Value is active ra:maxdemandconfigur abletimeperiodschedule (see section MaxDemandTimePeriod Schedule Specific Data Items) None N/A Non- Table Read Maximum Demand Import Registers Parse Response Body Data Items Figure Read Maximum Demand Import Registers Parse Response Specific Data Items Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: None Formatted: Font: Not Bold, Superscript Field Code Changed Formatted: Font: 8 pt, Not Italic Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto 1 Maximum MaxDemandConfigurableTimeActiveEnergyImport Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted: Font: Arial Bold, 9 pt, Bold, Not Italic, Font color: Custom Color(RGB(41,35,92)) LastResetDateTime UTC date time at which the Maximum Demand (Configurable Time) Active Energy Import Value was last reset xs:datetime None UTC Date- Time Non- Page 181 of 239

182 Data Item Description / Valid Set Type Default Units Sensitivity MaxDemandRegiste rdata The largest average value of Active Energy Import recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour) within the time period specified in Maximum Demand Configurable Time Period (including the UTC date and time at the end of the 30 minute period to which the data relates) ra:maxdemandregister DataType None N/A Non- Formatted: Keep with next Table Read Maximum Demand Import Registers Parse Response - MaxDemandConfigurableTimeActiveEnergyImport Specific Data Items Figure Read Maximum Demand Import Registers Parse Response - MaxDemandConfigurableTimeActiveEnergyImport Specific Data Items MaxDemandRegisterDataType Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity Field Code Changed Formatted: Heading 6, Left, Don't keep with next Value The largest average value of Active Energy Import or Export recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour) within the time period specified in Maximum Demand Configurable Time Period xs:datetimedecimal None W Non- CaptureTime The UTC date and time at the end of the 30 minute period to which the Value relates xs:datetime None UTC Date- Time Non- Formatted: Keep with next Table Read Maximum Demand Import Registers Parse Response - MaxDemandRegisterDataType Specific Data Items Figure Read Maximum Demand Import Registers Parse Response - MaxDemandRegisterDataType Specific Data Items MaxDemandTimePeriodSchedule Specific Data Items Formatted: Caption Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity MaximumDemandS cript Identifier of the Script to be run to record the Maximum Demand (Configurable Time) Active Energy Import Value Valid set: Values between 01 and 02 Restriction of xs:nonnegativeinteger (total digits = 2 min inclusive = 01 max inclusive = 02) None N/A Non- Formatted: Font: 8 pt, Not Italic, Font color: Text 1 Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font: 8 pt, Font color: Auto Page 182 of 239

183 Data Item Description / Valid Set Type Default Units Sensitivity DaysOfWeekApplica bility 1 MaximumDemandS chedule MaximumDemandS pecialdays Enable ValidityWindow ScriptLogicalName The days of the week to which the schedule applies defined as an array of 7 Day IDs Valid set: Monday Tuesday Wednesday Thursday Friday Saturday Sunday The switch time and date range (with wildcards) when the script is to be run The Special Day IDs (from indicated by their position on the string) to which the schedule applies. N/A to Maximum Demand so set to a constant value of Indicates if the schedule is to be enabled. Set to constant value true N/A to Maximum Demand so set to a constant value of FFFF The name of the script to be run by the scheduler. Set to a constant valuvalue e of 00000A8064FF ra:dayofweekid restriction of xs:string (Enumeration) ra:electricityschedule 2 (see Annex Section 17 for sr:electricityschedule) Restriction of xs:string (Constant) Restriction of xs:boolean (Constant) Restriction of xs:hexbinary (Constant) Restriction of xs:string (Constant) None N/A Non- None N/A Non N/A Non- true N/A Non- FFFF N/A Non A 8064FF Table Read Maximum Demand Import Registers Parse Response - MaxDemandTimePeriodSchedule Specific Data Items 1 Maximum 7 Figure Read Maximum Demand Import Registers Parse Response - MaxDemandTimePeriodSchedule Specific Data Items N/A Non- Formatted: Font: Not Bold, Font color: Auto, Superscript Formatted: Table bullet 2, Indent: Left: 0.17 cm, Bulleted + Level: 1 + Aligned at: 0.63 cm + Indent at: 1.27 cm Formatted: Font: 8 pt, Font color: Black Formatted: Superscript Formatted: Keep with next Formatted: Caption Formatted: Not Superscript/ Subscript 2 ra: data type is identical to the corresponding sr: data type, except that in ra: all the components are optional Sample Response body Formatted: Heading 6 Page 183 of 239

184 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>2c</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs18b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Maximum Demand Registers (import)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readmaximumdemandimportregistersrsp MessageSuccess="true"> <ra:maxdemandconfigurabletimeactiveenergyimport> <ra:lastresetdatetime> t12:13:24</ra:lastresetdatetime> <ra:maxdemandregisterdata> <ra:value>100</ra:value> <ra:capturetime> t11:30:00</ra:capturetime> </ra:maxdemandregisterdata> </ra:maxdemandconfigurabletimeactiveenergyimport> <ra:maxdemandactiveenergyimport> <ra:value>50</ra:value> <ra:capturetime> t09:00:00</ra:capturetime> </ra:maxdemandactiveenergyimport> <ra:maxdemandconfigurabletimeperiod> <ra:maximumdemandscript>01</ra:maximumdemandscript> <ra:daysofweekapplicability> <ra:dayofweekid>monday</ra:dayofweekid> </ra:daysofweekapplicability> <ra:maximumdemandschedule> <ra:switchtime>00:00:00</ra:switchtime> <ra:startdate> <sr:year> <sr:specifiedyear>2014</sr:specifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>08</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>01</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:startdate> <ra:enddate> <sr:year> <sr:specifiedyear>2014</sr:specifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>09</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>30</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:enddate> </ra:maximumdemandschedule> <ra:maximumdemandspecialdays> </ra:maximumdemandspecialdays> <ra:enable>true</ra:enable> <ra:validitywindow>ffff</ra:validitywindow> <ra:scriptlogicalname>00000a8064ff</ra:scriptlogicalname> </ra:maxdemandconfigurabletimeperiod> </ra:readmaximumdemandimportregistersrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Maximum Demand Import Registers Parse Response Sample Formatted: Font: 7.5 pt, Not Italic Formatted: Normal, Don't keep with next, Don't adjust space between Latin and Asian text, Don't adjust space between Asian text and numbers Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Bold Page 184 of 239

185 Formatted: Normal The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Read Maximum Demand Export Registers (4.12.2) Service Request Name ReadIMaximumDemandRegisters Service Reference 4.12 Service Request Variant Name ReadIMaximumDemandExportRegisters Service Reference Variant Service Request Objective Business Context Statement To enable a DCC Service user to retrieve read the maximum demand export register values recorded on an ESME meter. The DCC Service user has conducted a network analysis survey for network planning purposes and wishes to retrieve maximum demand values. User Role Access Electricity Export Supplier (EES) Electricity Network Operator (ENO) Security Classification Non-critical and non-sensitive: GBCS XREF: SME.C.NC 1. This Service Request returns all the Maximum Demand Export Registers available at the meter. It isn t possible to request a subset of them. Service Request Narrative 2. This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule) Service Reference Grouping is applicable to this Service Reference Variant for User Role ENO. Table Read Maximum Demand Export Registers Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its ReadMaximumDemandExportRegisters XML element defines this Service Request and contains the Execution Date and Time. Page 185 of 239

186 Formatted: Font: (Default) Arial, 8 pt, Bold, Not Italic, Font color: Auto Figure Read Maximum Demand Export Registers Service Request Structure (Ad-hoc) Create Schedule: Its DSPReadMaximumDemandExportRegisters XML element defines this Service Request and doesn t contain any data items. Formatted: Font: Not Italic Formatted: Centered Figure Read Maximum Demand Export Registers Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadIMaximumDemandExortRegisters (Ad-hoc) Formatted: Heading 6, Indent: Left: 0 cm Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future xs:datetime Yes None UTC Date- Time Table Read Maximum Demand Export Registers Service Request Data Items (Ad-hoc) Non DSPReadMaximumDemandExportRegisters (Create Schedule) N/A Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled Page 186 of 239

187 Transform On Demand DCC Only Future Dated DSP Scheduled No NoYesNo No DSP Yes Table Read Maximum Demand Export Registers Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes YesNoYes YesNoYes No No No No No Table Read Maximum Demand Export Registers Command Variant Values (Ad-hoc) Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time validation Sample Request Sample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as followsa sample Service Request body document is as follows: Page 187 of 239

188 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID>11-EE </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.12</ServiceReference> <ServiceReferenceVariant>4.12.2</ServiceReferenceVariant> </Header> <Body> <ReadMaximumDemandExportRegisters> <ExecutionDateTime> T02:05:00.0</ExecutionDateTime> </ReadMaximumDemandExportRegisters> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Maximum Demand Export Registers Service Request (Body) Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Maximum Demand Export Registers Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. Page 188 of 239

189 When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadMaximumDemandExportRegistersRsp Formatted: Heading 6 Formatted: Font: Arial, Not Bold, Not Italic, Font color: Auto Figure Read Maximum Demand Export Registers Parse Response Structure Specific Header Data Items Data Item Electricity Response Formatted: Heading 6 Formatted Table GBCSHexadecimalMessageCode GBCSUseCaseNumber 002B ECS18a GBCSUseCaseName Read Maximum Demand Registers (export) Table Read Maximum Demand Export Registers Parse Response Header Data Items Specific Body Data Items Formatted: Caption, Left, Don't keep with next Formatted: Heading 6 Data Item Description / Valid Set Type Default Units Sensitivity Page 189 of 239

190 Data Item Description / Valid Set Type Default Units Sensitivity MaxDemandActiveE nergyexport A store capable of holding the largest average value of Active Energy Export recorded in any 30 minute period (commencing at the start of minutes 00 and 30 in each hour and including the UTC date and time at the end of the 30 minute period to which the data relates) since the value was last, together with the UTC date and time when the value was last reset, arranged such that the recording of a larger value shall cause the previous entry to be overwritten. ra:maxdemandregister DataType (see section MaxDemandRegisterDat atype Specific Data Items) None N/A Non- Formatted: None Formatted: Font: 8 pt, Not Italic Table Read Maximum Demand Export Registers Parse Response Body Data Items Figure Read Maximum Demand Export Registers Parse Response Specific Data Items Sample Response encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>2b</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs18a</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Maximum Demand Registers (export)</ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readmaximumdemandexportregistersrsp MessageSuccess="true"> <ra:maxdemandactiveenergyexport> <ra:value>50</ra:value> <ra:capturetime> t09:00:00</ra:capturetime> </ra:maxdemandactiveenergyexport> </ra:readmaximumdemandexportregistersrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Maximum Demand Export Registers Parse Response Sample Formatted: Heading 6, Left, Don't keep with next Formatted: Font: 8 pt, Not Italic Formatted: Font: 8 pt, Not Bold, Font color: Auto Formatted: Normal The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Read Prepayment Configuration (4.13) Service Request Name ReadPrepaymentConfiguration Page 190 of 239

191 Service Reference 4.13 Service Request Variant Name ReadPrepaymentConfiguration Service Reference Variant 4.13 Service Request Objective To enable a DCC Service user to determine the prepayment specific configuration datas that hasve been set on a smart meter. NB This Service request provides response for the configuration settings of the prepayment, rather than register values which may be retrieved using Service Request 4.3 (see section ) Business Context Statement The DCC Service Uuser wishes to establish the basis on which the meter (operating in prepayment) mode is operating in response to a customer query. User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Security Classification Non-critical and non-sensitive: GBCS XREF: SME.C.NC This Service Request returns all the Prepayment Configuration data available at the meter as set up by Service Request 2.1 Update Prepay Configuration (see Annex section 2). It isn t possible to request the reading of a subset of the data. Service Request Narrative For reading the instantaneous import energy registersprepayment configuration values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not avialableavailable for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. (see Annex section 2). It isn t possible to request a subset of the data. Table Read Prepayment Configuration Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Its ReadPrepaymentConfiguration XML element defines this Service Request and only contains the Execution Date Time for Future Dated requests. Page 191 of 239

192 Formatted: Font: Arial, Not Bold, Font color: Blue Figure Read Prepayment Configuration Service Request Structure Formatted: Caption, No bullets or numbering Formatted: Font: Not Italic, Check spelling and grammar Formatted: Caption Specific Data Items Definition The data items contained in the Service Request are defined as: Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDate Time The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future xs:datetime No None UTC Date- Time Table Read Prepayment Configuration Service Request Data Items Non- Formatted: None, Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP No Table Read Prepayment Configuration Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Page 192 of 239

193 CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Prepayment Configuration Command Variant Values Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks and Annex section 17.2 for Execution Date Time validation Sample Request A sample Service Request body document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 193 of 239

194 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID>11-EE :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID>11-EE </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.13</ServiceReference> <ServiceReferenceVariant>4.13</ServiceReferenceVariant> </Header> <Body> <ReadPrepaymentConfiguration/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Prepayment Configuration Service Request Format Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Prepayment Configuration Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface. Page 194 of 239

195 Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadPrepaymentConfigurationRsp Formatted: Font: 9 pt, Not Bold, Not Italic Figure Read Prepayment Configuration Parse Response Structure Page 195 of 239

196 Formatted: Font: 9 pt, Not Bold, Not Italic Figure Read Prepayment Configuration Parse Response Electricity Non-Disablement Calendar Formatted: Font: Not Italic Formatted: Normal Figure Read Prepayment Configuration Parse Response Electricity SpecialDaysApplicability Formatted: Font: Not Italic Formatted: Normal Figure Read Prepayment Configuration Parse Response Electricity DaysOfWeekApplicability Page 196 of 239

197 Formatted: Font: Not Bold, Not Italic, Font color: Auto Figure Read Prepayment Configuration Parse Response Gas Non-Disablement Calendar Formatted: Caption Formatted: Font: Not Italic Figure Read Prepayment Configuration Parse Response Gas DayProfiles Formatted: Caption Formatted: Font: Not Italic Figure Read Prepayment Configuration Parse Response Gas WeekProfiles Page 197 of 239

198 Formatted: Normal Formatted: Font: Not Bold, Not Italic, Font color: Auto Figure Read Prepayment Configuration Parse Response Gas SeasonProfiles Formatted: Normal Formatted: Font: Not Bold, Not Italic, Font color: Auto Figure Read Prepayment Configuration Parse Response Gas SpecialDays Specific Header Data Items Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode 003B 00B5 GBCSUseCaseNumber ECS26a GCS21b GBCSUseCaseName Read ESME Configuration Data Prepayment Read GSME Configuration Data Prepayment Table Read Prepayment Configuration Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Page 198 of 239

199 Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table DebtRecoveryPerPa yment The percentage of a payment to be recovered against debt when the Meter is operating Payment-based Debt Recovery in Prepayment Mode. Valid set: >= 0 and <= (100.00%) Restriction of xs:nonnegativeinteger (min Inclusive = 0, max Inclusive = 10000) None % Non- DebtRecoveryRateC ap DebtRecoveryRate1 The maximum amount in Currency Units per unit time (week) that can be recovered through Paymentbased Debt Recovery when the Meter is operating in Prepayment Mode. Debt recovery rate in Currency Units per unit time for the first time-based debt recovery register when the Meter is using Time-based Debt Recovery in Prepayment Mode. xs:integer None 1000 th pence / week xs:integer None 1000 th Pence per Day Non- Non- Formatted Table Formatted: Font: Not Italic, Not Highlight Formatted: Font: Not Italic, Not Highlight Formatted: Font: Not Bold, Font color: Auto, Superscript DebtRecoveryRate2 Debt recovery rate in Currency Units per unit time for the first time-based debt recovery register when the Meter is using Time-based Debt Recovery in Prepayment Mode. xs:integer None 1000 th Pence per Day Non- DisablementThresho ld The threshold in Currency Units for controlling when to Disable the Supply. xs:integer None 1000 th pence Non- EmergencyCreditLi mit The amount of Emergency Credit in Currency Units to be made available to a Consumer when Emergency Credit is activated by the Consumer. xs:integer None 1000 th pence Non- Formatted Table EmergencyCreditThr eshold The threshold in Currency Units below which Emergency Credit may be activated by the Consumer, if so configured, when the Meter is operating in Prepayment Mode. xs:integer None 1000 th pence Non- LowCreditThreshold The threshold in Currency Units below which a low credit Alert is signalled. xs:integer None 1000 th pence Non- CreditMaxCreditThre shold Maximum amount of credit permitted per top up. xs:integer None 1000 th pence Non- MaxCreditMaxMeter Balance Maximum amount of credit permitted on meter. xs:integer None 1000 th pence Non- SuspendDebtDisabl ed SuspendDebtEmerg ency A setting controlling whether debt should be collected when the Meter is operating in Prepayment Mode and Supply is Disabled. True: Collect Debt False: Don t Collect Debt A setting controlling whether debt should be collected when the Meter is operating in Prepayment Mode and Emergency Credit has been activated. True: Collect Debt False: Don t Collect Debt xs:boolean None N/A Non- xs:boolean None N/A Non- Formatted: Outline numbered + Level: 1 + Numbering Style: Bullet + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Outline numbered + Level: 1 + Numbering Style: Bullet + Aligned at: 0 cm + Indent at: 0.63 cm Page 199 of 239

200 Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table Electricity NonDisablementCal endar Electricity CurrencyUnitName Gas NonDisablementCal endar Structure defining the Non Disablement schedules Electricity Only The Currency Units currently used by a Smart Meter for display purposes, which shall be GB Pounds Valid set: 1000th pence th pence Electricity Only Calendar defining the time periods when Non-Disablement applies or doesn t apply Gas Only ra: ElectricityNonDisableme ntcalendar 1 (see Annex section 2.1 for sr: ElectricityNonDisableme ntcalendar) Restriction of xs:string (Enumeration) ra: GasNonDisablementCal endar 1 (see Annex section 2.1 for sr: GasNonDisablementCal endar) None N/A Non- 1000th pence N/A Non- None N/A Non- Table Read Prepayment Configuration Parse Response Body Data Items Formatted: Keep with next Formatted: Font: Not Bold, Font color: Auto, Superscript Figure Read Prepayment Configuration Parse Response Specific Data Items 1 ra: data type is identical to the corresponding sr: data type, except that in ra: all the components are optional Sample Response Page 200 of 239

201 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>3b</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs26a</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Configuration Data Prepayment</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readprepaymentconfigurationrsp MessageSuccess="true"> <ra:debtrecoveryperpayment>25</ra:debtrecoveryperpayment> <ra:debtrecoveryratecap>50</ra:debtrecoveryratecap> <ra:debtrecoveryrate1>50</ra:debtrecoveryrate1> <ra:debtrecoveryrate2>30</ra:debtrecoveryrate2> <ra:disablementthreshold>10000</ra:disablementthreshold> <ra:emergencycreditlimit>50</ra:emergencycreditlimit> <ra:emergencycreditthreshold>50</ra:emergencycreditthreshold> <ra:lowcreditthreshold>50</ra:lowcreditthreshold> <ra:creditmaxcreditthreshold>50</ra:creditmaxcreditthreshold> <ra:maxcreditmaxmeterbalance>5000</ra:maxcreditmaxmeterbalance> <ra:suspenddebtdisabled>true</ra:suspenddebtdisabled> <ra:suspenddebtemergency>true</ra:suspenddebtemergency> <ra:electricity> See Figure 150Figure 150Figure 150Figure 150Figure 181 for details of Electricity Non-Disablement Calendar rencyunitname>millipence</ra:currencyunitname> </ra:electricity> </ra:readprepaymentconfigurationrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Prepayment Configuration Parse Response Sample Electricity Formatted: Font: 7.5 pt, Not Bold, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: Not Bold, Not Italic Formatted: Font: 7.5 pt, Not Bold, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Page 201 of 239

202 <ra:nondisablementcalendar> <ra:electricitynondisablementschedule index="1"> <ra:nondisablementscript>32</ra:nondisablementscript> <ra:daysofweekapplicability> <ra:dayofweekapplicability index="7"> <ra:dayofweekid>sunday</ra:dayofweekid> </ra:dayofweekapplicability> </ra:daysofweekapplicability> <ra:electricityschedule> <ra:switchtime>00:00:00</ra:switchtime> <ra:startdate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:nonspecifiedmonth>ff</sr:nonspecifiedmonth> </sr:month> <sr:dayofmonth> <sr:nonspecifieddayofmonth>ff</sr:nonspecifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:specifieddayofweek>7</sr:specifieddayofweek> </sr:dayofweek> </ra:startdate> <ra:enddate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:nonspecifiedmonth>ff</sr:nonspecifiedmonth> </sr:month> <sr:dayofmonth> <sr:nonspecifieddayofmonth>ff</sr:nonspecifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:specifieddayofweek>7</sr:specifieddayofweek> </sr:dayofweek> </ra:enddate> </ra:electricityschedule> </ra:electricitynondisablementschedule> <ra:electricitynondisablementschedule index="2"> <ra:nondisablementscript>33</ra:nondisablementscript> <ra:daysofweekapplicability> <ra:dayofweekapplicability index="7"> <ra:dayofweekid>sunday</ra:dayofweekid> </ra:dayofweekapplicability> </ra:daysofweekapplicability> <ra:electricityschedule> <ra:switchtime>23:59:59</ra:switchtime> <ra:startdate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:nonspecifiedmonth>ff</sr:nonspecifiedmonth> </sr:month> <sr:dayofmonth> <sr:nonspecifieddayofmonth>ff</sr:nonspecifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:specifieddayofweek>7</sr:specifieddayofweek> </sr:dayofweek> </ra:startdate> <ra:enddate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:nonspecifiedmonth>ff</sr:nonspecifiedmonth> </sr:month> <sr:dayofmonth> <sr:nonspecifieddayofmonth>ff</sr:nonspecifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:specifieddayofweek>7</sr:specifieddayofweek> </sr:dayofweek> </ra:enddate> </ra:electricityschedule> </ra:electricitynondisablementschedule> </ra:nondisablementcalendar> Formatted Table Figure Read Prepayment Configuration Parse Response Sample Electricity Non-Disablement Calendar Page 202 of 239

203 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>b5</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs21b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read GSME Configuration Data Prepayment</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readprepaymentconfigurationrsp MessageSuccess="true"> <ra:debtrecoveryperpayment>25</ra:debtrecoveryperpayment> <ra:debtrecoveryratecap>50</ra:debtrecoveryratecap> <ra:debtrecoveryrate1>50</ra:debtrecoveryrate1> <ra:debtrecoveryrate2>20</ra:debtrecoveryrate2> <ra:disablementthreshold>10000</ra:disablementthreshold> <ra:emergencycreditlimit>50</ra:emergencycreditlimit> <ra:emergencycreditthreshold>50</ra:emergencycreditthreshold> <ra:lowcreditthreshold>50</ra:lowcreditthreshold> <ra:creditmaxcreditthreshold>50</ra:creditmaxcreditthreshold> <ra:maxcreditmaxmeterbalance>5000</ra:maxcreditmaxmeterbalance> <ra:suspenddebtdisabled>true</ra:suspenddebtdisabled> <ra:suspenddebtemergency>true</ra:suspenddebtemergency> <ra:gas> See Figure 152Figure 152Figure 152Figure 152Figure 183 for details of Electricity Non-Disablement Calendar </ra:gas> </ra:readprepaymentconfigurationrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Prepayment Configuration Parse Response Sample Gas Page 203 of 239

204 <ra:nondisablementcalendar> <ra:dayprofiles> <ra:gasnondisablementdayprofile index="1"> <ra:timestartaction index="1"> <ra:starttime>00:00:00</ra:starttime> <ra:nondisablementaction>32</ra:nondisablementaction> </ra:timestartaction> <ra:timestartaction index="2"> <ra:starttime>07:00:00</ra:starttime> <ra:nondisablementaction>33</ra:nondisablementaction> </ra:timestartaction> <ra:timestartaction index="3"> <ra:starttime>22:00:00</ra:starttime> <ra:nondisablementaction>32</ra:nondisablementaction> </ra:timestartaction> <ra:dayidentifier>01</ra:dayidentifier> </ra:gasnondisablementdayprofile> <ra:gasnondisablementdayprofile index="2"> <ra:timestartaction index="1"> <ra:starttime>00:00:00</ra:starttime> <ra:nondisablementaction>32</ra:nondisablementaction> </ra:timestartaction> <ra:timestartaction index="2"> <ra:starttime>23:59:59</ra:starttime> <ra:nondisablementaction>33</ra:nondisablementaction> </ra:timestartaction> <ra:dayidentifier>02</ra:dayidentifier> </ra:gasnondisablementdayprofile> </ra:dayprofiles> <ra:weekprofiles> <ra:weekprofile index="1"> <ra:weekname>01</ra:weekname> <ra:referencedday index="1">01</ra:referencedday> <ra:referencedday index="2">01</ra:referencedday> <ra:referencedday index="3">01</ra:referencedday> <ra:referencedday index="4">01</ra:referencedday> <ra:referencedday index="5">01</ra:referencedday> <ra:referencedday index="6">02</ra:referencedday> <ra:referencedday index="7">02</ra:referencedday> </ra:weekprofile> </ra:weekprofiles> <ra:seasonprofiles> <ra:season index="1"> <ra:seasonname>summer</ra:seasonname> <ra:seasonstartdate> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>04</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>01</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:seasonstartdate> <ra:referencedweekname index="1">01</ra:referencedweekname> </ra:season> </ra:seasonprofiles> <ra:specialdays> <ra:gasspecialdays index="1"> <ra:date> <sr:year> <sr:nonspecifiedyear>ffff</sr:nonspecifiedyear> </sr:year> <sr:month> <sr:specifiedmonth>12</sr:specifiedmonth> </sr:month> <sr:dayofmonth> <sr:specifieddayofmonth>25</sr:specifieddayofmonth> </sr:dayofmonth> <sr:dayofweek> <sr:nonspecifieddayofweek>f</sr:nonspecifieddayofweek> </sr:dayofweek> </ra:date> <ra:referencedday>02</ra:referencedday> </ra:gasspecialdays> </ra:specialdays> </ra:nondisablementcalendar> Figure Read Prepayment Configuration Parse Response Sample Gas Non-Disablement Calendar Formatted Table Formatted: Caption, No bullets or numbering Page 204 of 239

205 The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Formatted: Caption 21.2 Read Prepayment Daily Read Log (4.14) Service Request Name ReadPrepaymentDailyReadLog Service Reference 4.14 Service Request Variant Name ReadPrepaymentDailyReadLog Service Reference Variant 4.14 Service Request Objective To allow enable a DCC Service User to obtain a Daily Read Log entry of from an ESME, GPF/GSMEelectricity or gas meter or Gas Proxy Function / Smart Meter for a specified date-time period. Business Context Statement. Allows Enables a DCC Service User to request the retrieval of a stored Daily Read Log entry for a specific date period (Enables a reading at a specific time (e.g. midnight) to be retrieved at a later time (for example on change of Supplier). User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Security Classification Non-critical, Request is non-sensitive and Response is sensitive for Gas Smart Meters but non-sensitive for Electric Smart Meters:: GBCS XREF: SME.C.NC Page 205 of 239

206 1. The Prepayment Daily Read Log, as defined by SMETS, is a log capable of storing thirty one UTC date and time stamped entries of; - Meter Balance - Emergency Credit Balance, - Accumulated Debt Register, - Payment Debt Register and - Time Debt Registers [1 2] arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Service Request Narrative Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. This could be the current or the old Registered Supplier. Because this Service Request returns data, URPs (i.e. the old Registered Supplier), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. o Access Control will allow the old Registered Import Supplier and the current Registered Import Supplier to read the Prepayment Daily Read Log entry for a CoS Date identified from registration data. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. This will never be the old Registered Supplier. 3. This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. 4. For reading the instantaneous import energy registersprepayment daily read log values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not avialableavailable for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. Formatted: Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font color: Text 1 Formatted: Space After: 10 pt, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Table Read Prepayment Daily Read Log Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Page 206 of 239

207 Ad-hoc: Its ReadPrepaymentDailyReadLog XML element defines this Service Request and contains the date interval for which the log is to be retrieved, for URP the Key Agreement Public security Security credentials Credentials and, for Future Dated, the Execution Date Time. Formatted: Font: Not Italic Formatted: Font: Not Italic Figure Read Prepayment Daily Read Log Service Request Structure (Ad-hoc) Create Schedule: Its DSPReadPrepaymentDailyReadLog XML element defines this Service Request and contains the date-time interval for which the log is to be retrieved, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition. Page 207 of 239

208 Formatted: Font: Not Italic Formatted: Font: Not Italic Figure Read Prepayment Daily Read Log Service Request Structure (Create Schedule) Formatted: Caption Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadPrepaymentDailyReadLog (Ad-hoc) Formatted: Heading 6 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime PrepaymentDailyReadL ogperiod The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future The Start and End Date-Times for which the data is required xs:datetime No None UTC Date- Time sr:readlogperiod (see Annex section 17 for details) Non- Yes None N/A Non- KAPublicSecurityCreden tials The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Old Registered Supplier) sr:certificate (xs:base64binary) Registered Supplier: N/A Old Registered Supplier 1 : Yes None N/A Non- Page 208 of 239

209 Table Read Prepayment Daily Read Log Service Request Data Items (Ad-hoc)_ 1 Mandatory for User Roles EIS and GIS that were registered parties (KRPs) to the Device for the required time period, but they no longer are DSPReadPrepaymentDailyReadLog (Create Schedule) Data Item Description / Valid Set Type Mandatory Default Units Sensitivity DSPPrepaymentDaily ReadLogPeriod Offset The Start and End Date Offsets from the current date and the Start and End Times which together define the datetime period for which the data is required sr:readlogperiod Offset (see Annex section 17 for details) Yes None N/A Non- Table Read Prepayment Daily Read Log Service Request Data Items (Create Schedule) Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Read Prepayment Daily Read Log Modes of Operation Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Formatted: Space After: 0 pt Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0 pt Validation Yes Yes Yes No No No No No Table Read Prepayment Daily Read Log Command Variant Values (Ad-hoc) This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time and,, Key Agreement Public Security Credentials and Read Log Period (PrepaymentDailyReadLogPeriod) and Public Security Credentials validation. Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSP PrepaymentDailyReadLogPeriodOffset) validation Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 209 of 239

210 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.14</ServiceReference> <ServiceReferenceVariant>4.14</ServiceReferenceVariant> </Header> <Body> <ReadPrepaymentDailyReadLog> <PrepaymentDailyReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </PrepaymentDailyReadLogPeriod> </ReadPrepaymentDailyReadLog> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Prepayment Daily Read Log Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Prepayment Daily Read Log Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device). Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Page 210 of 239

211 See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadPrepaymentDailyReadLogRsp Formatted: Font: 9 pt, Not Bold, Not Italic Figure Read Prepayment Daily Read Log Parse Response Structure Formatted: Justified Specific Header Data Items Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode GBCSUseCaseNumber ECS21b GCS16b GBCSUseCaseName Read Electricity (Prepayment) Daily Read Log Read GSME Daily Read log(s) (prepayment) Table Read Prepayment Daily Read Log Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Page 211 of 239

212 Data Item Description / Valid Set Type Default Units Sensitivity LogEntry 1 Each of the 31 entries of the Prepayment Daily Read Log. This log is capable of storing thirty one UTC date and time stamped entries of Meter Balance, Emergency Credit Balance, Accumulated Debt Register, Payment Debt Register and Time Debt Registers [1..2] arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten ra:prepaymentoperation aldatatype (see section ) None N/A Table Read Prepayment Daily Read Log Parse Response Body Data Items Formatted: Font: Not Bold, Font color: Auto, Superscript Formatted: Keep with next Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: (Default) Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: Not Bold, Font color: Auto Figure Read Prepayment Daily Read Log Parse Response Specific Data Items 1 Maximum PrepaymentOperationalDataType Specific Data Items Data Item Description / Valid Set Type Default Units Sensitivity AccumulatedDebtRe gister The debt resulting from the collection of Standing Charge and/or time-based debt when Emergency Credit is in Use as configured by Suspend Debt Emergency, when operating in Prepayment Mode xs:integer None 1000th pence Formatted: Font: 8 pt, Not Italic Formatted: Add space between paragraphs of the same style, Line spacing: single, Tab stops: 0.48 cm, Left cm, Centered EmergencyCreditBal ance The amount of Emergency Credit available to the Consumer after it has been activated by the Consumer. xs:integer None 1000th pence Formatted: Font: 8 pt, Not Italic MeterBalance When operating in Prepayment Mode, the Meter Balance represents the Smart Meter s determination of the amount of credit available to the Consumer (excluding any Emergency Credit Balance) xs:integer None 1000th pence Formatted: Font: 8 pt, Not Italic Formatted: Font: 8 pt, Not Italic PaymentDebtRegist er Debt to be recovered as a percentage of payment when using Payment-based Debt Recovery in Prepayment Mode xs:integer None 1000th pence Formatted: Font: 8 pt, Not Italic TimeDebtRegisters1 One of two registers recording independent debts to be recovered over time when operating Timebased Debt Recovery in Prepayment Mode xs:integer None 1000th pence Formatted: Font: 8 pt, Not Italic TimeDebtRegisters1 One of two registers recording independent debts to be recovered over time when operating Timebased Debt Recovery in Prepayment Mode xs:integer None 1000th pence Timestamp The UTC date-time at which the corresponding log entry was taken xs:datetime None UTC Date- Time Formatted: Keep with next Table Read Prepayment Daily Read Log Parse Response - PrepaymentOperatonalDataTypeSpecific Data Items Figure Read Prepayment Daily Read Log Parse Response - PrepaymentOperatonalDataTypeSpecific Data Items Formatted: Caption Page 212 of 239

213 Sample Response body <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>34</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs21b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read Electricity (Prepayment) Daily Read Log</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readprepaymentdailyreadlogrsp MessageSuccess="true"> <ra:electricity> <ra:logentry> <ra:accumulateddebtregister>250000</ra:accumulateddebtregister> <ra:emergencycreditbalance>100000</ra:emergencycreditbalance> <ra:meterbalance>123000</ra:meterbalance> <ra:paymentdebtregister>500</ra:paymentdebtregister> <ra:timedebtregisters1>70</ra:timedebtregisters1> <ra:timedebtregisters2>80</ra:timedebtregisters2> <ra:timestamp> t00:01:02</ra:timestamp> </ra:logentry> </ra:electricity> </ra:readprepaymentdailyreadlogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Prepayment Daily Read Log Parse Response Sample Electricity Formatted: Font: 8 pt, Not Italic Formatted: Normal, None, No bullets or numbering, No page break before, Don't keep with next, Don't adjust space between Latin and Asian text, Don't adjust space between Asian text and numbers Formatted: Font: 8 pt, Not Italic Formatted: Font: 8 pt, Bold, Font color: Auto Page 213 of 239

214 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>96</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>gcs16b</ra:gbcsusecasenumber> <ra:gbcsusecasename>read GSME Daily Read log(s) (prepayment) </ra:gbcsusecasename> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readprepaymentdailyreadlogrsp MessageSuccess="true"> <ra:gas> <ra:logentry> <ra:accumulateddebtregister>250000</ra:accumulateddebtregister> <ra:emergencycreditbalance>100000</ra:emergencycreditbalance> <ra:meterbalance>123000</ra:meterbalance> <ra:paymentdebtregister>500</ra:paymentdebtregister> <ra:timedebtregisters1>70</ra:timedebtregisters1> <ra:timedebtregisters2>80</ra:timedebtregisters2> <ra:timestamp> t00:01:02</ra:timestamp> </ra:logentry> </ra:gas> </ra:readprepaymentdailyreadlogrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Prepayment Daily Read Log Parse Response Sample Gas The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Formatted: Normal, No bullets or numbering 22.2 Read Load Limit Counter (4.15) Service Request Name ReadLoadLimitCounter Service Reference 4.15 Service Request Variant Name ReadLoadLimitCounter Service Reference Variant 4.15 Service Request Objective Business Context Statement To allow enable a DCC Service User to read the Load Limit Counter on a specified electricity Electricity Smart metermeter. A When a customer has a load limited tariff and the DCC Service User needs to read how many times the load limiter has activated. User Role Access Electricity Import Supplier (EIS) Electricity Network Operator (ENO) Page 214 of 239

215 Security Classification Non-critical and non-sensitive: GBCS XREF: SME.C.NC 1. This Service Request reads the following data item values as defined in SMETS - Load Limit Counter - Load Limit Supply State - Load Limit Power Threshold Service Request Narrative - Load Limit Period - Load Limit Restoration Period 1.2. This Service Request returns the Load Limit Counter Data available at the meter. It isn t possible to request a subset of it This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). Table Read Load Limit Counter Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its ReadLoadLimitCounter XML element defines this Service Request and contains the Execution Date Time. Formatted: Font: Arial, 9 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: Not Italic Formatted: Caption, Indent: Left: 0 cm, Don't keep with next Figure Read Load Limit Counter Service Request Structure (Adhoc) Create Schedule: Its DSPReadLoadLimitCounter XML element defines this Service Request and doesn t contain any data items. Page 215 of 239

216 Formatted: Font: Not Italic Formatted: Centered Figure Read Load Limit Counter Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled ReadLoadLimitCounter (Ad-hoc) Formatted: Heading 6 Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future xs:datetime Yes None UTC Date- Time Table Read Load Limit Counter Service Request Data Items (Ad-hoc) Non- Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm DSPReadLoadLimitCounter (Create Schedule) N/A. Formatted: Heading Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No No No DSP Yes Table Read Load Limit Counter Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0 pt Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Validation CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes No No No No No No No Table Read Load Limit Counter Command Variant Values (Adhoc) This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time validation. Page 216 of 239

217 Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 217 of 239

218 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.15</ServiceReference> <ServiceReferenceVariant>4.15</ServiceReferenceVariant> </Header> <Body> <ReadLoadLimitCounter> <ExecutionDateTime> T02:00:00.0</ExecutionDateTime> </ReadLoadLimitCounter> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Load Limit Counter Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Load Limit Counter Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Response & Alert Common Interface When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Page 218 of 239

219 Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadLoadLimitCounterRsp Formatted: Font: 9 pt, Not Bold, Not Italic, Font color: Auto Formatted: Font: Not Bold, Not Italic, Font color: Auto Figure Read Load Limit Counter Parse Response Structure Specific Header Data Items Page 219 of 239

220 Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode 0042 GBCSUseCaseNumber ECS27 GBCSUseCaseName Read ESME Load Limit Data Table Read Load Limit Counter Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity Formatted Table LoadLimitCounterVa lue The count of load limit events since last reset xs: decimalnonnegativeinte ger None N/A Non- LoadLimitCounterUn it The Load Limit Counter Unit Valid set: xs:string None N/A Non- LoadLimitPowerThre shold 255: No units The Active Power threshold above which the measurement of a Load Limit Period is commenced xs:integer None kw Non- Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font: Not Italic, Not Highlight LoadLimitPeriod The length of time which the Active Power Import needs to continuously exceed the Load Limit Power Threshold before a load limiting event is deemed to have occurred xs:nonnegativeinteger None Secon ds Non- Formatted Table LoadLimitRestoratio nperiod The length of time after the Supply has been Armed following a Load Limiting Event before the Supply is Enabled by the Electricity Smart Meter xs:nonnegativeinteger None Secon ds Non- LoadLimitSupplyStat e A setting to control the state of the Supply in the case of a load limiting occurring, being: Disable Unchanged Restriction of xs:string (Enumeration) None N/A Non- Table Read Load Limit Counter Parse Response Body Data Items Formatted: Keep with next Formatted: Bulleted + Level: 1 + Aligned at: 0.63 cm + Indent at: 1.27 cm Figure Read Load Limit Counter Parse Response Specific Data Items Sample Response body Page 220 of 239

221 <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>42</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs27</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Load Limit Data</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readloadlimitcounterrsp MessageSuccess="true"> <ra:loadlimitcounter>7</ra:loadlimitcounter> <ra:loadlimitpowerthreshold>10</ra:loadlimitpowerthreshold> <ra:loadlimitperiod>300</ra:loadlimitperiod> <ra:loadlimitrestorationperiod>600</ra:loadlimitrestorationperiod> <ra:loadlimitsupplystate>unchanged</ra:loadlimitsupplystate> </ra:readloadlimitcounterrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Load Limit Counter Parse Response Sample The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document Read Active Power Import (4.16) Service Request Name Service Reference 4.16 Service Request Variant Name Service Reference Variant 4.16 Service Request Objective ReadActivePowerImport ReadActivePowerImport To allow enable a DCC Service User to read the Active Power Import value(s) on a specified electricity Electricity Smart metermeter. Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Font: 8 pt, Not Bold, Not Italic Formatted: Caption, No bullets or numbering Formatted: Caption Business Context Statement To allow enable a DCC Service User to read the Active Power Import value(s) on a specified electricity Electricity Smart metermeter. User Role Access Electricity Import Supplier (EIS) Electricity Network Operator (ENO) Security Classification Service Request Narrative Non-critical and non-sensitive: GBCS XREF: SME.C.NC 1. This Service Request will return all the Active Power Import Registers. The Active Power Import registers returned depend on whether the Electricity Smart Meter is Single or Twin Element. 2. This Service Request can be run Ad-hoc or be DSP Scheduled Page 221 of 239

222 (via Create Schedule). Table Read Active Power Import Service Request This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set) Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its ReadActivePowerImport XML element defines this Service Request and doesn t contain any data items. Formatted: Font: Not Italic Formatted: Centered Formatted: Font color: Blue Figure Read Active Power Import Service Request Structure (Ad-hoc) Create Schedule: Its DSPReadActivePowerImport XML element defines this Service Request and doesn t contain any data items. Formatted: Font: Not Italic Figure Read Active Power Import Service Request Structure (Create Schedule) Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled Formatted Table No Yes No No Yes Table Read Active Power Import Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Page 222 of 239

223 CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Read Active Power Import Command Variant Values (Adhoc) Validation This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 223 of 239

224 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.16</ServiceReference> <ServiceReferenceVariant>4.16</ServiceReferenceVariant> </Header> <Body> <ReadActivePowerImport/> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Read Active Power Import Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Not Italic Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Read Active Power Import Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Response & Alert Common Interface Page 224 of 239

225 When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - ReadActivePowerImportRsp Formatted: Font: 9 pt, Not Bold, Not Italic Formatted: Font: Not Italic Figure Read Active Power Import Parse Response Structure Specific Header Data Items Data Item Electricity Response Formatted Table GBCSHexadecimalMessageCode 0028 GBCSUseCaseNumber GBCSUseCaseName ECS17c Read ESME Energy Registers (Power) Page 225 of 239

226 Table Read Active Power Import Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity ActivePowerImportV alue The total active Power from all elements on the Meter xs: decimalnonnegativeinte ger None W Non- PrimaryActivePowerI mportvalue The total active Power from the first element on the Meter xs:nonnegativeinteger None W Non- Table Read Active Power Import Parse Response Body Data Items Formatted: Keep with next Figure Read Active Power Import Parse Response Specific Data Items Sample Response <?xml version="1.0" encoding="utf-8"?> <ra:gbcsresponse xmlns:ds=" xmlns:sr=" xmlns:ra=" xmlns:xsi=" xsi:schemalocation=" schemaversion="1.0"> <ra:header> <ra:businessoriginatorid> </ra:businessoriginatorid> <ra:businesstargetid> </ra:businesstargetid> <ra:originatorcounter>50</ra:originatorcounter> <ra:gbcshexadecimalmessagecode>28</ra:gbcshexadecimalmessagecode> <ra:gbcsusecasenumber>ecs17c</ra:gbcsusecasenumber> <ra:gbcsusecasename>read ESME Energy Registers (Power)</ra:GBCSUseCaseName> <ra:timestamp> t09:10:37</ra:timestamp> </ra:header> <ra:body> <ra:responsemessage> <ra:smetsdata> <ra:readactivepowerimportrsp MessageSuccess="true"> <ra:activepowerimportvalue>100000</ra:activepowerimportvalue > <ra:primaryactivepowerimportvalue>100000</ra:primaryactivepowerimportvalue > </ra:readactivepowerimportrsp> </ra:smetsdata> </ra:responsemessage> </ra:body> </ra:gbcsresponse> Figure Read Active Power Import Parse Response Sample The output of the Parse component of Parse and Correlate for this Service Response will be defined in this section in a subsequent version of this document. Formatted: Caption, No bullets or numbering Formatted: Caption 24.2 Retrieve Daily Consumption Log (4.17) Service Request Name RetrieveDailyConsumptionLog Service Reference 4.17 Service Request Variant Name RetrieveDailyConsumptionLog Service Reference Variant 4.17 Service Request Objective Retrieve To enable a DCC Service User to read the specified Daily Consumption Log entry(s) on the specified meter. Page 226 of 239

227 Business Context Statement. The DCC Service user needs to measure, over a period of up to two years, the consumption profile changes on a particular meter. User Role Access Electricity Import Supplier (EIS) Gas Import Supplier (GIS) Electricity Network Operator (ENO) Gas Network Operator (GNO) Other User (OU) Security Classification Non-critical, Request is non-sensitive and Response is sensitive: GBCS XREF: SME.C.NC 1. The Daily Consumption Log as defined by SMETS is a log capable of storing 731 date stamped entries of Consumption arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten This Service Request can be run Ad-hoc or be DSP Scheduled (via Create Schedule). In all cases, if the sender is not authorised to read data for the entire period requested, an error will be returned. Service Request Narrative Ad-hoc: Available to User Roles with access to the Device during the entire date-time range requested. In the case of Import Supplier, this could be the current or the old Registered Supplier. Because this Service Request returns data, URPs (i.e. the old Registered Supplier and Other User ), have to include in the Request the Public Security Credentials they want the Device to sign the Response with. DSP Scheduled: Available to User Roles with access to the Device at the time the Schedule is created. In the case of Import Supplier, this will never be the old Registered Supplier. The URP Public Security Credentials (applicable to Other User ) for the Device to sign the Response are included in the Create Schedule Service Request. See Annex section This Service Request (Gas) can t be part of a Sequence, because the Command Response status is encrypted and the DSP is not able to check its contents. 4. For reading Daily Consumption Log values from the GSME, the DCC Service User should wherever possible request this to be read from the GPF as the primary use case. Only when the GPF is not available for query should this Service Request be targeted to the GSME. This will save battery life on the GSME for all Users. Table Retrieve Daily Consumption Log Service Request Formatted: Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font color: Text 1 Formatted: Space After: 10 pt, Numbered + Level: 1 + Numbering Style: 1, 2, 3, + Start at: 1 + Alignment: Left + Aligned at: 0 cm + Indent at: 0.63 cm This section should be read in conjunction with the Main Document of this documentation set section 9 (which describes the general formatting for all Service Requests and Service Responses) and with the XSD (XML Schema document 3 of this documentation set). Page 227 of 239

228 Service Request Format The SMSServiceRequest Body XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of all the Service Requests that send Commands to Devices. Ad-hoc: Its RetrieveDailyConsumptionLog XML element defines this Service Request (Adhoc) and contains the date-time interval for which the log is to be retrieved, for URP the Key Agreement Public security Security credentials Credentials and, for Future Dated, the Execution Date Time. Formatted: Font: 8 pt, Bold, Not Italic Formatted: Font: 8 pt, Bold, Not Italic Figure Retrieve Daily Consumption Log Service Request Structure (Ad-hoc) Create Schedule: Its DSPRetrieveDailyConsumptionLog XML element defines this Service Request and contains the date-time interval for which the log is to be retrieved, defined relative to the current date at the point the Scheduledeach Service Request is generated from the schedule. See Annex section 17 ReadLogPeriodOffset definition. Page 228 of 239

229 Formatted: Font: Not Italic Formatted: Font: (Default) Times New Roman, 0 pt, Bold, Not Italic, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Figure Retrieve Daily Consumption Log Service Request Structure (Create Schedule) Specific Data Items Definition The Data Items applicable depend on whether the Request is Ad-hoc or DSP Scheduled RetrieveDailyConsumptionLog (Ad-hoc) Formatted: Heading 6, Space After: 0 pt, No bullets or numbering Data Item Description / Valid Set Type Mandatory Default Units Sensitivity ExecutionDateTime DailyConsumptionLogPe riod KAPublicSecurityCreden tials The UTC date and time the DCC Service User requires the command to be executed on the Device ID Valid date-time in the future The Start and End Date-Times for which the data is required The Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Other User) xs:datetime No None UTC Date- Time sr:readlogperiod (see Annex section 17 for details) sr:certificate (xs:base64binary) Non- Formatted: Bulleted + Level: 1 + Yes None N/A Aligned at: 0 cm + Indent at: 0.63 cm Non- User Role 1 EIS, GIS, ENO, GNO: N/A User Role OU: Yes None N/A Non- Table Retrieve Daily Consumption Log Service Request Data Items (Ad-hoc) Page 229 of 239

230 1 Also Mandatory for User Roles EIS and GIS that were registered parties (KRPs) to the Device for the required time period, but they no longer are DSPRetrieveDailyConsumptionLog (Create Schedule) Formatted: Heading 6, Space After: 0 pt Data Item Description / Valid Set Type Mandatory Default Units Sensitivity DSPDailyConsumptio nlogperiodoffsetrea dlogperiodoffset The Start and End Date Offsets from the current date and the Start and End Times which together define the datetime period for which the data is required sr:readlogperiod Offset (see Annex section 17 for details) Yes None N/A Non- Table Retrieve Daily Consumption Log Service Request Data Items (Create Schedule) Formatted: Space After: 0 pt Applicable Modes of Operation The Modes of Operation applicable to this Service Request are (see Main Document of this documentation set section 2.3 for Modes of Operation definitions): Transform On Demand DCC Only Future Dated DSP Scheduled No Yes No DSP Yes Table Retrieve Daily Consumption Log Modes of Operation Formatted: Space Before: 0.5 line, After: 0.6 line Formatted: Space After: 0 pt Applicable Command Variant Values The Command Variant values applicable to this Service Request are (see Main Document of this documentation set section 3 for Command Variant definitions): Validation CV = 1 CV = 2 CV = 3 CV = 4 CV = 5 CV = 6 CV = 7 CV = 8 Yes Yes Yes No No No No No Table Retrieve Daily Consumption Log Command Variant Values (Ad-hoc) This Service Request has no specific validation. See Main Document of this documentation set section 7 for generic access control checks. Ad-hoc: See also Annex section 17.2 for Execution Date Time and, Read Log Period (DailyConsumptionLogPeriod)and Key Agreement Public Security Credentials validation. Create Schedule: See also Annex section 17.2 for Read Log Period Offset (DSPDailyConsumptionLogPeriodOffset) validation Sample Request A sample Service Request document is as followssample requests are given in Annex Introduction Appendix 2. The specific information for this Service Request (Body) is as follows: Page 230 of 239

231 <?xml version="1.0" encoding="utf-8"?> <ServiceRequest xmlns:ds=" xmlns=" xmlns:xsi=" schemaversion="1.0"> <SMSServiceHeader> <RequestID> :99-00-AA-BB-CC-DD-EE-FF:50</RequestID> <BusinessOriginatorID> </BusinessOriginatorID> <BusinessTargetID>99-00-AA-BB-CC-DD-EE-FF</BusinessTargetID> <OriginatorCounter>50</OriginatorCounter> <CommandVariant>1</CommandVariant> <ServiceReference>4.17</ServiceReference> <ServiceReferenceVariant>4.17</ServiceReferenceVariant> </Header> <Body> <RetrieveDailyConsumptionLog> <DailyConsumptionLogPeriodReadLogPeriod> <StartDateTime> T00:00:00.0</StartDateTime> <EndDateTime> T23:59:59.0</EndDateTime> </DailyConsumptionLogPeriodReadLogPeriod> </RetrieveDailyConsumptionLog> </SMSServiceBody> <Signature xmlns=" <SignedInfo> <CanonicalizationMethod Algorithm=" <SignatureMethod Algorithm=" <Reference URI=""> <Transforms> <Transform Algorithm=" </Transforms> <DigestMethod Algorithm=" <DigestValue>ZGVmYXVsdA==</DigestValue> </Reference> </SignedInfo> <SignatureValue>ZGVmYXVsdA==</SignatureValue> <KeyInfo> <X509Data> <X509IssuerSerial> <X509IssuerName>CN=user 1,OU=smart metering,o=company 1,L=glasgow,ST=scotland,C=uk</X509IssuerName> <X509SerialNumber> </X509SerialNumber> </X509IssuerSerial> </X509Data> </KeyInfo> </Signature> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </ServiceRequest> Figure Sample Retrieve Daily Consumption Log Service Request Format (Ad-hoc) Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Not Italic, Font color: Auto Formatted: Font: 7.5 pt, Font color: Auto Responses The Service Response messages for a The repsonseresponse messages for a Retrieve Daily Consumption Log Request request follow the generic format for all Device response messages, the generic responses applicable to this Service Request are; Acknowledgement Service Response (from Device) - GBCSPayload. Service Response Specific Payload Command for Local Delivery Page 231 of 239

232 Response & Alert Common Interface See Main Document of this documentation set section 4 for Response IDs returned to DCC Service Users that are Known Remote Parties (KRP) or Unknown Remote Parties (URP) to the Device. When this Service Request is run as DSP Scheduled, the Service Response (from Device) is a variation of the generic one and it is defined in section Sample responses are given in Annex Introduction Appendix 1, response specific information details are given below Response & Alert Common Interface Format Format - RetrieveDailyConsumptionLogRsp Formatted: Font: 9 pt, Not Bold, Not Italic, Font color: Auto Figure Retrieve Daily Consumption Log Parse Response Structure Specific Header Data Items Data Item Electricity Response Gas Response GBCSHexadecimalMessageCode A0 GBCSUseCaseNumber ECS66 GCS61 GBCSUseCaseName Read ESME Daily Consumption Log Read gas Daily Consumption Log Table Retrieve Daily Consumption Log Parse Response Header Data Items Formatted: Caption Specific Body Data Items Data Item Description / Valid Set Type Default Units Sensitivity LogEntry 1 Each of the 731 date stamped entries of Consumption arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten ra:dailyconsumptionlog EntryType (see section ) None N/A Table Retrieve Daily Consumption Log Parse Response Body Data Items Figure Retrieve Daily Consumption Log Parse Response Specific Data Items 1 Electricity: Maximum 731 Log Entries. Note that a value of 731 is considered as Unbounded by the XSD validation Formatted: Font: Arial, 8 pt, Not Bold, Not Italic, Font color: Auto Formatted: Keep with next Formatted: Font: (Default) Arial, 9 pt, Not Bold, Not Italic Page 232 of 239