SVAA Service Description

v 11.0
Download

Balancing and Settlement Code

BSC Service Description for Supplier Volume Allocation

Version 11.0

23 February 2023

SVAA Service Description

Version 11.0

1. This document is the BSC Service Description for the Supplier Volume Allocation Agent (SVAA) as appointed by the Balancing and Settlement Code Company (BSCCo).

2. The services of the SVAA are defined in accordance with the Balancing and Settlement Code (the Code) and Balancing and Settlement Code Procedures (BSCPs).

Version

Date

Description of Changes

Changes Included

Mods/ Panel/ Committee Refs

1.0

01/04/09

First Published

-

Panel 153/10

2.0

31/03/10

Updated to include P246 interim solution

P246

SVG109/05

3.0

03/11/11

November 11 Release

P253

Panel 174/05

4.0

23/02/12

February 2012 Release

CP1347

SVG125/03

5.0

05/11/15

November 2015 Release

P305

SVG177/03

6.0

28/02/19

February 2019 Release

P344

Panel 284C/01

7.0

11/12/19

11 December 2019 Standalone Release – CP1517

CP1517

SVG224/02

8.0

01/04/20

1 April 2020 Standalone Release – P354, P388

P354, P388

SVG229/07

9.0

01/04/21

1 April 2021 Standalone Release - P383

P383

SVG241/04

10.0

30/06/2022

June 2022 Standard Release

P375

SVG256/03

10.1

23/02/23

23 February 2023 Standard Release

P376

P312/04

10.2

23/02/23

23 February 2023 Standard Release

P419

P323/06

1. INTRODUCTION

1.1 Purpose

1.1.1 This document is the BSC Service Description for the Supplier Volume Allocation Agent (SVAA) as appointed by the Balancing and Settlement Code Company (BSCCo). The services of the SVAA are defined in accordance with the Balancing and Settlement Code (the Code) and Balancing and Settlement Code Procedures (BSCPs).

1.1.2 This Service Description defines the key roles of the SVAA in providing Supplier Volume Allocation (SVA), Daily Profile Production (DPP), Market Domain Data (MDD) and SVA Metering System Register services.

2. SUPPLIER VOLUME ALLOCATION

In order to carry out the Data Marshalling Process and operate the SVA System to calculate Suppliers’ Settlement charges, the SVAA shall operate and carry out the following.

2.1 Market Domain Data

2.1.1 Before each Volume Allocation Run (VAR) or DPP Run, the SVAA shall check whether the MDD has been updated and, if so, extract the updates into the SVA System in accordance with BSCP508.

2.1.2 Using the SVA System, the SVAA shall validate the MDD updates.

2.1.3 The SVAA shall inform the BSCCo or its nominated agent of any errors which occurred in validating the MDD, in accordance with BSCP508.

2.1.4 The SVAA shall maintain information related to each MDD update as specified in Appendix 1.

2.2 Non Half Hourly Data Aggregation (NHHDA) Data

2.2.1 Using the SVA System input, the SVAA shall validate every data file from an NHHDA received before the deadline in the SVAA Calendar, within the time period from receipt of the file specified in BSCP508.

2.2.2 Whenever possible, but provided that the SVAA meets its obligations under this Service Description and BSCP508, the SVAA shall validate and then use a data file received from a NHHDA after the deadline in the SVAA Calendar.

2.2.3 In relation to any data file received from a NHHDA, the SVAA shall inform that NHHDA, in accordance with BSCP508, of any validation errors and specify their nature.

2.2.4 Where the SVAA has received more than one data file which has passed validation from the same NHHDA designated for the same VAR, the SVAA shall use the file with the latest Run number in the file header.

2.25 The SVAA shall maintain information relating to files received from NHHDAs as specified in Appendix 1.

2.3 Half Hourly Data Aggregation (HHDA) Data

2.3.1 Using the SVAA System, the SVAA shall input and validate every data file from a HHDA received before the deadline in the SVAA Calendar, within the time period from receipt of the file specified in BSCP508.

2.3.2 Whenever possible, but provided that the SVAA meets its obligations under this Service Description and BSCP508, the SVAA shall validate and then use a data file received from a HHDA after the deadline in the SVAA Calendar.

2.3.3 In relation to any data file received from a HHDA, the SVAA shall inform that HHDA, in accordance with BSCP508, of any validation errors and specify their nature.

2.3.4 Where the SVAA has received more than one data file which has passed validation from the same HHDA designated for the same VAR, the SVAA shall use the file with the latest Run number in the file header.

2.3.5 The SVAA shall maintain information relating to files received from HHDAs as specified in Appendix 1.

2.3A Supplier, Virtual Lead Party, Asset Metering Virtual Lead and NETSO Data

2.3A.1 The SVAA shall input and validate every data file received from a Supplier, an Asset Metering Virtual Lead Party (AMVLP), Virtual Lead Party (VLP) or the NETSO as indicated in the SVA Metering System and Asset Metering System Register, within the time period specified in BSCP602.

2.3A.2 In relation to any data file received from an AMVLP, a VLP, a Supplier or the NETSO, the SVAA shall inform that Supplier, AMVLP, VLP or the NETSO, in accordance with BSCP602, of any validation errors and specify their nature.

2.3A.3 Where the SVAA has received more than one data file which has passed validation from the same Supplier, AMVLP, VLP or the NETSO for the same Settlement Period, the SVAA shall use the file with the latest Sequence Number in the file header.

2.3A.4 The SVAA shall maintain information relating to files received from Suppliers, AMVLPs, VLPs or the NETSO as specified in Appendix 1.

2.3B Activations Data

2.3B.1 The SVAA shall input and validate every data file received from the Settlement Administration Agent (SAA) identifying activations made in relation to Replacement Reserve (an SVA Metering System Balancing Service).

2.3C Declarations relating to SVA Non-Final Demand Facilities

2.3C.1 The SVAA shall input and validate every Declaration received from Suppliers identifying MSIDs linked to SVA Non-Final Demand Facilities for the purpose of notifying consumption volume for SVA Non-Final Demand Facilities to the NETSO.

2.3C.2 In relation to any Declaration received from a Supplier, the SVAA shall inform that Supplier, in accordance with BSCP602, of successful validations, and any validation errors and specify their nature.

2.3C.3 Where the SVAA has received more than one Declaration which has passed validation in respect of the same MSID, the SVAA shall update the details of the relevant Declaration using the latest file received.

2.3C.4 The SVAA shall maintain information relating to Declarations received from Suppliers as specified in Appendix 1.

2.3D Half Hourly AMSID Metered (HHDC) Data

2.3D.1 Using the SVAA System, the SVAA shall input and validate every data file from a HHDC received within the time period from receipt of the file specified in BSCP508.

2.3D.2 Whenever possible, but provided that the SVAA meets its obligations under this Service Description and BSCP508, the SVAA shall validate and then use a data file received from a HHDC after the deadline specified in BSCP508.

2.3D.3 In relation to any data file received from a HHDC, the SVAA shall inform that HHDC, in accordance with BSCP508, of any validation errors and specify their nature.

2.3D.4 Where the SVAA has received more than one data file which has passed validation from the same HHDC, the SVAA shall use the file with the latest Run number in the file header.

2.3D.5 The SVAA shall maintain information relating to files received from HHDCs as specified in Appendix 1.

2.4 GSP Group Take Data

2.4.1 Using the SVA System, the SVAA shall input and validate every data file received from the Central Data Collection Agent (CDCA), within the time period from receipt of the file specified in BSCP508.

2.4.2 Whenever possible, but provided that the SVAA meets its obligations under this Service Description and BSCP508, the SVAA shall validate and then use a data file received from the CDCA after the deadline in the SVAA Calendar.

2.4.3 In relation to any data file received from the CDCA, the SVAA shall inform the CDCA, in accordance with BSCP508, of any validation errors and specify their nature.

2.4.4 Where the SVAA has received more than one data file which has passed validation from the CDCA designated for the same VAR, the SVAA shall use the file with the latest Run number in the file header.

2.4.5 The SVAA shall notify the BSCCo or its nominated agent without delay in the event that the SVAA receives a data file from the CDCA after the deadline in the SVAA Calendar.

2.4.6 The SVAA shall maintain information relating to files received from the CDCA as specified in Appendix 1.

2.5 Line Loss Factor Data

2.5.1 Using the SVA System, the SVAA shall input and validate every data file received from the BSCCo or its nominated agent, within the timescale agreed between the BSCCo or its nominated agent and SVAA.

2.5.2 In relation to any data file received from the BSCCo or its nominated agent, the SVAA shall inform the BSCCo or its nominated agent, in accordance with BSCP508, of any validation errors and specify their nature.

2.5.3 Following the deadline for the provision of Line Loss Factors in accordance with BSCP508, the SVAA shall inform the BSCCo or its nominated agent of any Line Loss Factor Classes for which data are missing.

2.5.4 The SVAA shall maintain information relating to files received from Licensed Distribution System Operators (LDSOs) as specified in Appendix 1.

2.6 Standing Data and Other Parameters Input by the SVAA

2.6.1 The SVAA shall maintain the standing data and manage the process for Supplier approval of automated standing data updates in accordance with BSCP507.

2.6.2 The SVAA shall advise the Central Registration Agent of changes to its contact details, in accordance with BSCP507.

2.6.3 The SVAA shall date and timestamp all Non Half Hourly Balancing Mechanism Unit data files received from a Supplier, via its nominated Non Half Hourly Balancing Mechanism Unit representative, on every day of the year, in accordance with BSCP507.

2.6.4 Before each VAR, the SVAA shall check whether the standing data has been updated and, if so, translate the updates into the SVA System before the VAR.

2.6.5 The SVAA shall enter into the SVA System any parameters required to make it function correctly.

2.6.6 The SVAA shall record details about standing data and other input parameters from time to time entered into the SVA System, together with any relevant validation messages, as specified in Appendix 1.

2.6.7 Where the data file has originated from a source designated as a valid Data Aggregator in MDD, but has failed validation due to a conflict with the standing data:

2.6.7.1 Loading of this file will produce an exception report containing a warning message that describes the discrepancy. The standing data for that Settlement Day will automatically be amended to agree with the data provided by the Data Aggregator.

2.6.8 The SVAA shall amend the standing data for a Settlement Day where the SVAA has been informed that a Data Aggregator’s file is not required for that GSP Group on that Settlement Day. This confirmation may be made by either that Data Aggregator, all the Suppliers that would be associated with the data file, the BSCCo or its nominated agent. In this instance the SVAA shall require written confirmation before altering the standing data at a Final Reconciliation VAR or a Post Final Run.

2.6.9 In respect of paragraph 2.6.8, the SVAA shall inform the BSCCo or its nominated agent within one Working Day of the VAR that the standing data has been altered.

2.7 Invoking Volume Allocation Runs (VARs)

2.7.1 The SVAA shall invoke the SVA System (using the version of the system agreed from time to time with the BSCCo or its nominated agent) in accordance with the SVAA Calendar for the specific GSP Groups, Settlement Days and run types, unless instructed otherwise by the BSCCo or its nominated agent.

2.7.2 Each year during January (and after publication of the Settlement Calendar) the BSCCo shall produce and publish1 a ‘Post Final Settlement Calendar’ scheduling all the ‘DF’ runs capable of being scheduled for that calendar year. The SVAA shall receive this during mid February each year and shall invoke VAR Runs as determined by the ‘SSR’ dates included in this calendar.

2.7.3 Before invoking a VAR, the SVAA shall actively seek to obtain any missing data file from the relevant originator, using a medium with a normal anticipated delivery time of less than ten minutes, at least four Working Hours (where a “Working Hour” is an hour within a Working Day) before the deadline for receipt of the relevant data specified in the SVAA Calendar or in BSCP508, as the case may be. For this purpose a missing data file means any file required for a VAR (as indicated by the standing data) which the SVAA knows to be unavailable in validated form. Where the SVAA believes that a data file is missing from a Data Aggregator, the SVAA shall enquire from the Data Aggregator as to whether the Data Aggregator is obligated to provide a data file and act in accordance with paragraph 2.6.8.

2.7.4 Where the data file is a Balancing Mechanism Unit file and has failed validation due to an invalid Balancing Mechanism Unit, the SVAA shall assign the energy value for the failed Balancing Mechanism Unit to the Base Balancing Mechanism Unit in accordance with BSCP508.

2.7.5 The SVAA shall maintain information relating to VARs in a log containing the information specified in Appendix 1.

2.7.6 Where the Managed Data Network or the NETA NETWORK (NETANET) has been non-operative such that the Services provided will obviously be affected, the SVAA shall contact the BSCCo or its nominated agent for advice about rescheduling the VAR(s).

2.7.1 In respect of missing data not received and validated by the relevant deadline for an Interim Information VAR, the SVAA shall take the following action:

2.7.7.1 missing Non Half Hourly Data Aggregator data - substitute data from the previous Settlement Day with sufficient number of Settlement Periods in respect of each Supplier / Non Half Hourly Data Aggregator combination;

2.7.7.2 missing Half Hourly Data Aggregator data - for Weekday, Saturday and Sunday day types, substitute data from the previous Settlement Day of the same day type, and for all other day types substitute data from the previous Sunday Settlement Day, with sufficient number of Settlement Periods in respect of each Supplier / Half Hourly Data Aggregator combination;

2.7.7.2A missing Half Hourly Data Collector data – no substituted data should be used for the relevant AMSID and the SVAA shall record a ‘null’ value. This shall not prevent the SVAA from performing the VAR, only the calculation for the associated Secondary BM Unit.

2.7.7.3 missing GSP Group Take data - seek and follow the instruction from the BSCCo or its nominated agent as to the appropriate data to substitute;

2.7.7.4 missing Line Loss Factor data - use a default value of ‘1.0’; or

2.7.7.5 seek and follow the instruction from the BSCCo or its nominated agent as to the appropriate data to substitute where the Data Aggregator data is missing and there is no previous Interim Information VAR with that Settlement Day day type, or where the SVAA is unsure of the appropriate data to substitute for any other reason.

2.7.8 In respect of missing data not received and validated by the relevant deadline for an Initial VAR or Reconciliation VAR, the SVAA shall take the following action:

2.7.8.1 missing Non Half Hourly Data Aggregator / Half Hourly Data Aggregator data - substitute data from the previous Settlement Run for that Settlement Day in respect of each Supplier / Data Aggregator combination;

2.7.8.2 missing GSP Group Take data – substitute data from the previous VAR for the same Settlement Day; or

2.7.8.3 missing Line Loss Factor data - use a default value of ‘1.0’.

2.7.8A Where a Half Hourly Data Collector has submitted Actual data for an AMSID for a Settlement Date, either as specified in BSCP508 or subsequently, and it has been processed in the first available VAR, there is no obligation on the Half Hourly Data Collector to submit data for that AMSID for any subsequent VAR. This shall not be considered ‘missing data’ for the purposes of paragraph 2.7.10.

2.7.8A.1 The SVAA shall reuse the data for each subsequent VAR, subject to paragraph 2.7.8A.2;

2.7.8A.2 If the HHDC submits revised data at any time before the Final Reconciliation VAR, the SVAA shall use such revised data for that AMSID in the first available VAR. Such data shall not be considered ‘substituted data’ for the purposes of paragraph 2.7.9.

2.7.8B Where a Half Hourly Data Collector has submitted Estimated data for an AMSID for a Settlement Date, either as specified in BSCP508 or subsequently, and it has been processed in the first available VAR, the Half Hourly Data Collector shall be required to submit Actual data for that AMSID for the next scheduled VAR.

2.7.8C Where a Half Hourly Data Aggregator has not submitted Half Hourly Metering System Metered Data (via a D0385) for a VAR, or a Half Hourly Data Collector has not submitted Actual Half Hourly Asset Metering System Metered Data (via a D0390) for an AMSID for a Settlement Date for the Initial Settlement (SF) VAR, this shall be considered ‘missing data’ for the purposes of paragraph 2.7.10, and the SVAA shall issue a P0310 ‘Missing Metering System Data’ to the Half Hourly Data Aggregator and relevant Supplier, or the HHDC and relevant AMVLP, as appropriate.

2.7.8D Where a Half Hourly Data Aggregator has submitted a D0385, or a Half Hourly Data Collector has submitted a D0390, which fails validation, the SVAA shall issue a P0311 ‘Invalid Metering System Data’ to the Half Hourly Data Aggregator and relevant Supplier, or the HHDC and relevant AMVLP, as appropriate.

2.7.9 The SVAA shall report details of any substituted data pursuant to paragraph 2.7.8 to the relevant Suppliers, LDSOs and the BSCCo or its nominated agent, in accordance with BSCP508.

2.7.10 The SVAA shall maintain a record of all contact with, and attempts to contact, originators of missing data as specified in Appendix 1.

2.7.11 The SVAA shall record the occurrence of, and investigate the reasons for, any VAR failure and report that information without delay to the BSCCo or its nominated agent.

2.7.12 The SVAA shall allow the Supplier Deemed Take by BM Unit to be either positive or negative (that is, negative consumption should not be treated as spill and should not be allocated to other Suppliers) as per BSCP508.

2.7.13 Where any VAR cannot be completed, the SVAA shall agree remedies with the BSCCo or its nominated agent, the Settlement Administration Agent and, if appropriate, the CDCA and the Funds Administration Agent to ensure that the output will be delivered to the Settlement Administration Agent in accordance with the Funds Administration Agent Calendar, or as soon as possible thereafter.

2.7.14 In the event that the SVAA is unable to complete an Initial VAR, the SVAA shall provide estimated data, by BM Unit, to the Settlement Administration Agent without fail for every occasion that an Initial VAR is required by the Funds Administration Agent Calendar. To estimate the data, the SVAA shall estimate in energy terms, by BM Unit, the total value of the Supplier Deemed Take in each half hour, between Suppliers in the same proportion as occurred in the last Initial VAR for a Settlement Day for which the same day type was input into the DPP run.

2.7.15 When a Demand Disconnection has occurred as part of a Demand Control Event, the SVAA will receive and process adjusted aggregated energy volumes for the affected settlement date(s) as part of a timetabled Reconciliation Run.

2.8 Provision of Output

2.8.1 The SVAA shall produce and distribute the reports (and optional reports) output from the SVA System in accordance with BSCP508, BSC Section D Part 5 and BSC Section V Table 7.

2.8.2 The SVAA shall maintain information relating to all output reports despatched with their date-stamps. This log shall include the information specified in Appendix 1, and cover the output from the SVA System Performance Monitoring Reports and all communications received or made with regard to errors in the Settlement Process or disputes arising from such errors.

2.8.3 The SVAA shall provide information on any file despatched on request to any authorised recipient of that file and to the BSCCo or its nominated agent.

2.8.4 The SVAA shall inform all authorised recipients and the BSCCo or its nominated agent of any missing or delayed reports as soon as it becomes aware that such a delay will be inevitable.

2.8.5 The SVAA shall re-send output reports, to a recipient requesting a re-send.

2.8A Non Half Hourly Aggregated Settlement Data

2.8A.1 The SVAA shall provide each Host LDSO2 with aggregated settlement data (Supplier data aggregated up to LDSO level) for all Non Half Hourly Metering Systems on other LDSO networks within the distribution licence area, with the exception of Non Half Hourly Metering Systems registered to Line Loss Factor Classes for which the Host LDSO has instructed SVAA (in accordance with paragraph 2.8A.3) not to provide data.

2.8A.2 The SVAA shall provide NHH aggregated settlement data to Host LDSOs in accordance with BSCP508.

2.8A.3 Any instruction to exclude one or more Line Loss Factor Classes from the NHH aggregated settlement data shall be provided to the SVAA by the Host LDSO using the functionality provided for that purpose by the Elexon Portal, or (in the event that that functionality is unavailable) via the BSC Service Desk.

2.8B Half Hourly Replacement Reserve Data

2.8B.1 The SVAA shall provide in relation to accepted Replacement Reserve Bids:

2.8B.1.1 Secondary Half Hourly Delivered Volumes to Suppliers;

2.8B.1.2 Secondary Half Hourly Consumption Volumes to VLPs; and

2.8B1.3 Secondary Half Hourly Demand Volumes and Secondary Half Hourly Delivered Volumes to the SAA.

2.8C Non-Final Demand Facility Demand Data

2.8C.1 The SVAA shall provide to the NETSO in relation to Imports from Non-Final Demand Facilities linked with a valid Declaration(s) held by SVAA:

2.8C.1.1 Corrected Period BMU Gross HH Demand;

2.8C.1.2 Period BMU Gross Non-Final Demand;

2.8C.1.3 Daily BMU Gross HH Non-Final Demand; and

2.8C.1.4 Corrected Daily BMU Gross HH Demand.

2.9 Additional VARs

2.9.1 On request by the BSCCo or its nominated agent, the SVAA shall invoke the SVA System for additional VARs, or run a module of the SVA System, using the specified input data.

2.9.2 Following any additional VAR of the SVA System, or module thereof, carried out in accordance with paragraph 2.9.1, the SVAA shall distribute the output reports as requested by the BSCCo or its nominated agent.

2.9.3 Where requested by the BSCCo or its nominated agent, the SVAA will produce and provide the VAR Equitability Report to the BSCCo or its nominated agent.

2.10 Performance Monitoring Reports

2.10.1 The SVAA shall provide complete and accurate monthly routine Performance Monitoring Reports to the BSCCo or its nominated agent within 5 Working Days before the end of the month.

2.10.2 The SVAA shall provide complete and accurate ad-hoc Performance Monitoring Reports to the BSCCo or its nominated agent within 5 Working Days from receipt of the request. This timeframe can be extended upon authorisation from the BSCCo or its nominated agent.

2.10.3 The SVAA shall provide the information specified in Appendix 1 to the BSCCo or its nominated agent on request.

3. Daily Profile Production (DPP)

For each Settlement Day, the SVA System produces the Settlement Period Profile Data and Time Regime Data required to run the Supplier Volume Allocation (SVA) part of the SVA System, the Daily Profile Totals to pass to the Non Half Hourly Data Collectors and the Profiling Reports to pass to the Suppliers and Non Half Hourly Data Collectors. In providing this service the SVAA shall carry out the following duties and actions.

3.1 Temperature and Sunset Data

3.1.1 The SVAA shall contract with an authorised Temperature Provider for the provision of the Noon Temperature Data at a location specified in the MDD for each GSP Group for which it provides the Services.

3.1.2 The SVAA shall contract with an authorised Time of Sunset Provider for the provision of Time of Sunset Data for the areas specified by the BSCCo or its nominated agent. The file format expected by the SVAA System requires that the Time of Sunset Data must be provided by GSP Group. However, the same time shall apply for all GSP Groups and the sunset time used in all cases is that of Birmingham.

3.1.3 The SVAA shall ensure that Noon Temperature Data and Time of Sunset Data is delivered to it in time to meet the requirements of, and the timescales set out in, BSCP508 for the delivery of profile data.

3.2 Regression Coefficients

3.2.1 The SVAA shall load data from the Regression Equations file (P0014) provided annually by the BSCCo or its nominated agent from the MDD system into the SVA System. This file contains regression coefficients.

3.2.2 The SVAA shall validate the regression coefficients and report to the BSCCo or its nominated agent any validation failures.

3.2.3 The SVAA shall inform the BSCCo or its nominated agent immediately when regression coefficients have not been received one month prior to the end date of any current profile data and actively seek to obtain this data from the BSCCo or its nominated agent.

3.2.4 In the event of the SVAA being without valid regression coefficients for one or more profiles, the SVAA shall seek substitute data from the BSCCo or its nominated agent and use this data.

3.3 Data Input by the SVAA

3.3.1 The SVAA shall load Noon Temperature Data obtained from authorised providers.

3.3.2 The SVAA shall load Time of Sunset Data obtained from authorised providers for the areas specified by the BSCCo or its nominated agent. When loading the Time of Sunset Data, the same sunset time should be entered for all GSP Groups. The sunset time to be used is that of Birmingham.

3.3.3 The SVAA shall enter those items of data normally required to make the SVA System function correctly, including those changes submitted for manual entry by authorised agents as defined in BSCP508, and provide a daily report of all items of data manually entered to any relevant valid Supplier and the BSCCo or its nominated agent, together with any relevant validation messages.

3.3.4 The SVAA shall provide previously loaded data to Suppliers at their request.

3.3.5 The SVAA shall enter and disseminate Calendar/Clock Parameter Data and manually entered data details in accordance with BSCP508.

3.3.6 If the Temperature Provider does not provide Noon Temperature Data, the SVAA shall, if available, input alternative data provided by the Temperature Provider (listed below in order of preference) and inform the BSCCo or its nominated agent and Suppliers in accordance with BSCP508:

3.3.6.1 Data for 13:00 hours for the weather station at the GSP Group location on the same Settlement Day; or

3.3.6.2 Data for 11:00 hours for the weather station at the GSP Group location on the same Settlement Day; or

3.3.6.3 Data for 12:00 from an alternative weather station defined by the BSCCo or its nominated agent on the same Settlement Day.

3.3.7 If the Temperature Provider does not provide Noon Temperature Data or alternative data, the SVAA shall input the previous Settlement Day’s data and inform the BSCCo or its nominated agent and Suppliers in accordance with BSCP508.

3.4 Other Data Entry

3.4.1 In addition to the parameters normally input by the SVAA indicated above, the SVAA shall report without unreasonable delay to the BSCCo or its nominated agent every other occasion where the facility to enter data manually was used, such report to set out complete details of the entries made, the source of authorisation for the data and the time of receipt. This paragraph refers to the SVAA’s ability to enter time pattern regimes, Settlement configurations, clock intervals, the assignment of configurations to profile classes and the Average Fraction of Yearly Consumption.

3.5 Teleswitch Data

3.5.1 The SVAA shall record the receipt of the Teleswitch Contact Interval Data files from the Teleswitch Agent, noting those that arrive after the due time defined in the BSCP508, and requesting any overdue Teleswitch Contact Interval Data files.

3.5.2 The SVAA shall record valid Teleswitch Contact Interval Data combinations for which no switching data has been received by the due time each day.

3.5.3 If no data is received as recorded pursuant to paragraph 3.5.2, the SVAA shall:

3.5.3.1 where possible substitute the data from the most recent Settlement Day of the same day type; or

3.5.3.2 where the SVA System is unable to load the substitute data, use the previous Settlement Day’s data as the default.

3.5.4 The SVAA shall report to Suppliers, Non Half Hourly Data Collectors and the BSCCo or its nominated agent, on each occasion when the default settings are used.

3.5.5 The SVAA shall provide to all Suppliers the report detailing the Teleswitch Contact Intervals that were used during the DPP run, in accordance with BSCP508.

3.5.6 The SVAA shall load the initial Teleswitch data received from valid Suppliers or their nominated agents into the SVAA software ensuring that there is a complete set of data.

3.5.7 Using the manual entry facilities, the SVAA shall update the SVA System with any additional data provided by Suppliers or their nominated agents in time for each DPP run.

3.5.8 The SVAA shall maintain an audit trail of Teleswitch data and the input data used to define it.

3.5.9 The SVAA shall provide to all Suppliers the relevant Teleswitch data that was loaded for each run of DPP, in accordance with BSCP508.

3.6 Invoking the DPP Run

3.6.1 The SVAA shall use the version of the SVA System software specified to it by the BSCCo or its nominated agent.

3.6.2 The SVAA shall run DPP in accordance with the SVAA Calendar for the specific GSP Groups and Settlement Days for which the SVAA is contracted and record both the occasions and the input parameters, which it shall provide monthly and on demand to the BSCCo or its nominated agent.

3.6.3 The SVAA shall run the DPP in accordance with instructions received from the BSCCo or its nominated agent in addition to the requirements of the SVAA Calendar.

3.6.4 The SVAA shall, before running the DPP, actively seek to obtain any files SVAA knows to be missing by making contact with the originator.

3.6.5 The SVAA shall maintain a record of input files that arrive after the due date and time specified in the SVAA Calendar and the action taken by the SVAA to obtain them. This information shall be available to the BSCCo or its nominated agent on request.

3.6.6 The SVAA shall investigate, record and report immediately to the BSCCo or its nominated agent the occasions and reasons for any run failures.

3.6.7 The SVAA shall perform any validations or checks provided within the SVAA application software.

3.6.8 If data fails validation the SVAA shall use reasonable endeavours to resolve any problems with the data with the provider of the data and inform the BSCCo or its nominated agent.

3.6.9 If resolution pursuant to paragraph 3.6.8 is not possible, and to delay further is reasonably likely to prevent the SVAA from fulfilling its obligations under this Service Description in accordance with the SVAA Calendar, the SVAA shall substitute data for input into the SVA System in accordance with the BSCP508.

3.6.10 The SVAA shall report those instances where data is manifestly in error or suspected by the SVAA to be unreasonable to the BSCCo or its nominated agent immediately, unless instructed otherwise by the BSCCo or its nominated agent.

3.6.11 The SVAA shall support the resolution of any queries associated with DPP data as described in BSCP01 and will liaise as necessary with the Disputes Administrator.

3.6A Calculation of Secondary Half Hour Volumes

3.6A.1 The SVAA shall calculate Secondary Half Hour Delivered Volumes, Secondary Half Hour Demand Volumes and Secondary Half Hour Consumption Volumes in accordance with BSCP508.

3.7 Provision of Output

3.7.1 The SVAA shall produce and distribute the reports output from the SVA System in accordance with BSCP508.

3.7.2 The SVAA shall provide these output reports in accordance with the timescales specified in BSCP508 and maintain a record of all files despatched with the date stamps and the due time/date of despatch.

3.7.3 The SVAA shall provide this information to the BSCCo or its nominated agent on request.

3.7.4 The SVAA shall only re-send output reports to a recipient requesting a re-send.

3.7.5 The SVAA shall despatch reports by one of the available media defined in the BSCP508 and chosen by the recipient. The SVAA shall not despatch individual reports to recipients who have elected not to receive them.

3.7.6 The SVAA shall provide on request to any authorised recipient and the BSCCo or its nominated agent information on the files despatched.

4. Market Domain Data (MDD)

4.1 Receiving Updates to the MDD

4.1.1 The SVAA, in the role of MDD Manager (MDDM), shall receive updates to the MDD from the BSCCo or its nominated agent, via an MDD Change Request and in accordance with BSCP509, ‘Changes to Market Domain Data’.

4.1.2 In addition, the SVAA as MDDM shall, on an infrequent and ad hoc basis, receive updates from Suppliers informing the SVAA of the identity of Equipment Owners in relation to any Non Half Hourly Metering Systems for which the Supplier is registered in SMRS, as required by BSC Section S 2.7.11.

4.1.3 Where a Balancing Mechanism Unit file is received from the Central Registration Agent, the SVAA shall not publish this file until a request is received to publish this file from the BSCCo or its nominated agent, in accordance with paragraph 4.1.1 above.

4.1.4 The SVAA shall receive annually from the SAA a draft Settlement Calendar and shall review it in accordance with BSC Section U 2.4.2.

4.1.5 In support of paragraph 4.1.2 above, upon receipt of the Balancing Mechanism Unit file the SVAA shall notify the BSCCo or its nominated agent that the Balancing Mechanism Unit file has been received and, if requested, provide the file to the BSCCo or its nominated agent.

4.1.6 The SVAA shall check that the version numbers of the updates received from the BSCCo or its nominated agent are consecutive. In the event that the update versions are not consecutive, it shall contact the BSCCo or its nominated agent to inquire as to the existence of missing updates and, if in existence, to request their transmission.

4.1.7 Should the SVAA be unable to incorporate data because it is in the wrong format (for example, alphanumeric instead of numeric) it shall report the matter to the BSCCo or its nominated agent, and not incorporate any part of the update to the MDD.

4.1.8 The SVAA shall incorporate all authorised updates into the MDD, in sequence order of the version numbers, in accordance with BSCP509.

4.1.9 Should any recipient question the correctness of part of the MDD, then the SVAA shall report the matter to the BSCCo or its nominated agent and agree a remedy with the BSCCo or its nominated agent.

4.2 New Agencies

4.2.1 The SVAA shall assign an agreed unique reference code to new Supplier Meter Registration Agents, Suppliers, Meter Operator Agents, Data Collectors, Data Aggregators, Initial Allocation and Reconciliation Agent and the SVAA upon being informed of their existence by the BSCCo or its nominated agent. Such unique reference codes shall form part of the MDD and shall be agreed with the BSCCo or its nominated agent prior to their inclusion on an MDD Publish.

4.2.2 Where the CDCA has also assigned a unique reference code to any of the market participants referred to in paragraph 4.2.1, this shall also form part of the MDD.

4.3 Market Domain Data Matrix

4.3.1 The SVAA shall receive, and update changes to, the MDD matrix in accordance with BSCP509.

4.3.2 The SVAA shall use the MDD matrix to identify the recipients of all MDD files.

4.4 Provision of Output

4.4.1 The SVAA shall send the MDD files to each of the parties specified in BSCP509 and BSCP520 in accordance with the timescales specified in those documents.

4.4.2 The SVAA shall also send the MDD files to the BSCCo or its nominated agent.

4.4.3 The SVAA shall also provide, in accordance with BSCP509, a cut down version of MDD (the ‘Incremental Set’) unless the recipient of the file(s) has requested a full version of the file(s) or unless all of the data items with the MDD have changed, in which case a full version of the MDD file(s) will be provided (the ‘Complete Set’).

4.4.3.1 At the direction of the BSCCo or its nominated agent, the SVAA shall provide the latest Complete and Incremental MDD Sets to non-BSC parties.

4.4.4 The SVAA shall distribute the Technical Product Deliverables component of the MDD only to those parties that have signed the appropriate confidentiality undertaking, as notified to the SVAA by the BSCCo or its nominated agent.

4.4.5 The SVAA shall ensure every issued MDD file shall contain a unique consecutive version number.

4.4.6 The SVAA shall provide on request information about the despatch of files, as collected in Appendix 2, to any authorised recipient of the MDD updates and to the BSCCo or its nominated agent.

4.5 Checking Confirmation Messages

4.5.1 The SVAA shall re-send the MDD update files to any party which has not confirmed receipt of the original update files, by the same time on the next Working Day after the despatch. This shall NOT apply to those files sent to parties manually.

4.5.2 The SVAA shall report to the BSC Service Desk any parties which have not confirmed receipt of either the original update or the re-send of the update within four Working Hours of the receipt message for the resend. The due time of the receipt shall be as specified in BSCP508.

4.6 Maintaining the Market Domain Data Information

4.6.1 The SVAA shall record information about MDD as specified in Appendix 1.

4.6.2 The SVAA shall, on request of the BSCCo or its nominated agent, provide the information specified in Appendix 1.

4.7 Production of the SVAA Calendar

4.7.1 The SVAA shall produce the SVAA Calendar in accordance with BSCP509 and confirm that the dates in the calendar are acceptable. The SVAA Calendar does not (under current arrangements) include the Post Final Settlement Runs (Run Type DF) which are scheduled in the Post Final Settlement Calendar.

4.7.2 The SVAA shall send the SVAA Calendar to those recipients defined in BSCP509.

4.8 Production of the Data Aggregation and Settlements Timetable File

4.8.1 The SVAA shall produce the Data Aggregation and Settlements Timetable File within the constraints of BSCP01, with the contents as specified in Appendix 2.

4.8.2 The SVAA shall send the Data Aggregation and Settlements Timetable File to the Non Half Hourly Data Aggregators with every publication of the MDD, even though the data contained within the file may not have changed.

5. Other Services

5.1 Audit, Security & Control Requirements

5.1.1 The SVAA shall retain an audit trail for each DPP run, each VAR and each issue of MDD for forty (40) months following a Settlement Day, such that it is easily accessible to the BSC Auditor and in a form acceptable to the BSCCo or its nominated agent and the BSC Auditor.

5.1.2 The SVAA shall retain audit reports on standing data and changes to standing data and any supporting physical documentation for twenty eight (28) months following a Settlement Day, such that they are easily accessible for use by, and in a form acceptable to, the BSC Auditor and, thereafter, until 40 months after the relevant Settlement Day in a form that may be retrieved, if requested, within 10 Working Days.

5.1.3 The SVAA shall support the Extra-Settlement Determination process as agreed with the BSCCo or its nominated agent for a period of 40 months after the relevant Settlement Day.

5.1.4 The SVAA shall provide the BSCCo or its nominated agent and the BSC Auditor with access to all systems, data, information, records, procedures and plans related to, and staff involved in the provision of, the services carried out by the SVAA on behalf of the BSCCo or its nominated agent.

5.1.5 The SVAA shall provide a fully itemised list of all the hardware and software (system and application) used in the operation of the SVAA Operations Services within 2 weeks of a request to do so by the BSCCo or its nominated agent.

5.1.6 The SVAA shall provide facilities to, and manage access to, and operation rights of, users and operations and support staff, individually or in groups, to view and modify any data received by the SVAA in relation to the SVAA Operations Services.

5.1.7 The SVAA shall monitor attempts to breach the security of the SVAA Operations Services and report all such attempts within one Working Day of their occurrence to the BSCCo or its nominated agent and the BSC Auditor.

5.1.8 Subject to the prior agreement of the BSCCo or its nominated agent and the BSC Auditor, the SVAA shall arrange for all printed reports which are no longer required for the provision of services, or for audit or the purposes of the BSCCo or its nominated agent, to be securely destroyed (for example, by shredding) and for all the BSCCo’s or its nominated agent’s data which is no longer required to be obliterated from machine readable media prior to disposal.

5.1.9 The SVAA shall ensure the confidentiality and integrity of the information that it receives, processes and maintains.

5.2 Provision of Output Files

5.2.1 Extract files from the SVAA System shall be formulated into a predictable output as described in the BSC SVA Data Catalogue. These files shall then be output to the Data Marshalling Process.

5.2.2 The SVAA shall use the pre-determined volume parameters and the number of Settlement Day(s) provided by the BSCCo or its nominated agent for the purposes of determining the level of output which is acceptable in determining whether or not a re-send of output files will be undertaken.

5.2.3 When a request is received to re-send output files, the SVAA shall ensure that the re-send is submitted to the BSCCo or its nominated agent for consideration, where the request:

5.2.3.1 exceeds the pre-determined parameters provided to the SVAA; and

5.2.3.2 relates to more than three (3) Settlement Days, or an alternative number of Settlement Days as specified by the BSCCo or its nominated agent, in accordance with paragraph 5.2.2 above, of output files.

5.2.4 Where instructed by the BSCCo or its nominated agent to re-send the output files, the SVAA shall re-send the output files.

5.2.5 The SVAA shall maintain records of re-sends of output files and, when requested to do so by the BSCCo or its nominated agent, report this information to the BSCCo or its nominated agent.

5.2.6 Where instructed by the BSCCo or its nominated agent to provide a quotation for the cost of re-sending output files in accordance with paragraph 5.2.5 above, the SVAA shall provide such a quotation to the BSCCo or its nominated agent in accordance with the timescales and method defined in BSCP508.

5.3 Data Marshalling

5.3.1 The SVAA shall route all electronic output files, via the Data Marshalling Process.

5.3.2 The SVAA shall use the flow control parameters notified to the SVAA in writing by the BSCCo or its nominated agent. The BSCCo or its nominated agent retains the right to change the flow control parameters at any time and the SVAA will use these flow control parameters as soon as practicable but no later than one Working Day after receipt.

5.3.3 The performance of the flow controller element of the Data Marshalling Process shall be reported to the BSCCo or its nominated agent on a periodic basis by the SVAA.

5.3.4 The SVAA shall propose revisions to the flow control parameters and submit these to the BSCCo or its nominated agent for agreement, in a format agreed with the BSCCo or its nominated agent.

5.3.5 The SVAA shall ensure that the Data Marshalling Process outputs files in the following order of priority:

5.3.5.1 Daily Profile Coefficient File;

5.3.5.2 the remaining reports specified in BSCP508.

5.3.6 The BSCCo or its nominated agent retains the right to change the order of priority at any time. Any such changes will be notified to the SVAA, in writing by the BSCCo or its nominated agent. The SVAA will amend the order of priority as soon as practicable but no later than one Working Day after receipt.

5.4 Managed Data Network

5.4.1 The SVAA shall manage the Data Marshalling Process so that the files are passed, as soon as possible, to the gateway using the flow control parameters provided by the BSCCo or its nominated agent from time to time.

5.4.2 “Successful dispatch” means the receipt of such files at the gateway where the flow controller element of the Data Marshalling Process:

5.4.2.1 holds files; and

5.4.2.2 is constrained only by the flow control parameters specified above; and

5.4.2.3 is operating in accordance with its agreed functional specification.

5.4.3 The receipt of a complete and correct set of files in the Data Marshalling Process shall be deemed to have achieved “successful despatch”.

5.5 Dispute Handling

5.5.1 The SVAA shall provide the Dispute Support Service in order that Market Participants may pursue and verify disputes.

5.5.2 When instructed by the BSCCo or its nominated agent, the SVAA shall re-run the DPP and prioritise the despatch of the files as specified in paragraph 5.3.5 above.

5.5.3 For up to twenty eight (28) months after any Settlement Day the SVAA shall, on request of the BSCCo or its nominated agent, perform a VAR for such Settlement Day.

5.5.4 The SVAA shall (on request) provide the information required by the Market Participant requesting support. This may consist of the data used and the outputs produced on one or more Settlement Days.

5.5.5 The SVAA shall ensure that, unless otherwise agreed, Suppliers only receive data relating to their own purchases.

5.5.6 The SVAA shall comply with BSCP11.

5.5.7 The SVAA shall be able to supply input and output data and software from archive within two Working Days for any Settlement Day up to 28 months after the Settlement Day, in printed and electronic form, to support the reasonable requirements of the BSCCo or its nominated agent.

5.5.8 The SVAA shall support the Extra-Settlement Determination process as agreed with the BSCCo or its nominated agent.

5.5.9 The SVAA shall provide a copy of MDD for any Settlement Day on request by any authorised party, for audit and dispute purposes for a period of 14 months prior to when the request was made.

5.5.10 Where the SVAA is aware of errors within the Settlement system that may give rise to a dispute it shall notify the BSCCo or its nominated agent promptly.

5.5.11 The SVAA shall initiate a dispute where there has been a material error in the Settlement process. The BSCCo or its nominated agent shall inform the SVAA, from time to time, of the definition of “material” for the purposes of this paragraph.

5.6 Provision of Performance Monitoring Data

5.6.1 The SVAA shall provide the appropriate data to the BSCCo or its nominated agent as specified in BSCP533.

5.6.2 The SVAA shall provide the appropriate data to the BSCCo or its nominated agent in the timescales specified in BSCP533.

5.7 Re-calculation of Average Fraction of Yearly Consumption, GSP Group Profile Class Average EAC and GSP Group Profile Class Default EAC Values

5.7.1 Annually in February, or at an alternative time specified by the BSCCo or its nominated agent, the SVAA shall use the SVA System to re-calculate for all GSP Groups, on a Settlement Day basis for a twelve (12) month period, the:

5.7.1.1 Average Fraction of Yearly Consumption;

5.7.1.2 GSP Group Profile Class Average EAC; and

5.7.1.3 GSP Group Profile Class Default EAC,

values spanning the twelve (12) month period, in accordance with BCP508.

5.7.2 The BSCCo or its nominated agent will specify the start and end periods relating to the twelve (12) month period to be re-calculated.

5.7.3 The SVAA shall log any exceptions generated during the re-calculation and shall report these exceptions to the BSCCo or its nominated agent.

5.7.4 The SVAA shall provide the revised Average Fraction of Yearly Consumption, GSP Group Profile Class Average EAC and GSP Group Profile Class Default EAC values to the BSCCo or its nominated agent for approval, in accordance with BSCP509.

5.7.5 Upon notification of the approval of the revised Average Fraction of Yearly Consumption, GSP Group Profile Class Average EAC and GSP Group Profile Class Default EAC values, the SVAA shall distribute these revised values in accordance with BSCP508.

5.8 Miscellaneous

5.8.1 The SVAA shall immediately report to the BSCCo or its nominated agent any known or suspected failures of the hardware or software, any such report to be confirmed in writing.

5.8.2 The SVAA shall report to the BSCCo or its nominated agent any significant known or suspected errors in the Settlement process, any such report to be confirmed in writing.

5.8.3 The SVAA shall seek and follow the advice of the BSCCo or its nominated agent where the SVAA is uncertain about the correct course of action in exceptional circumstances or in cases of ambiguity in the documentation, provided that seeking advice shall not delay passing reports to the Settlement Administration Agent beyond the timescales in the Funds Administration Agent Calendar.

5.8.4 The SVAA shall synchronise the SVA System’s time to ensure agreement within one second of Co-ordinated Universal Time.

5.8.5 Where requested by the BSCCo or its nominated agent, the SVAA will produce and provide the Measurement Requirement and Profile Class in a GSP Group Report to the BSCCo or its nominated agent.

5.8.6 The SVAA shall attach file creation timestamps to incoming files to ensure that the files are loaded in the correct order.

5.8.7 The SVAA shall attach file processed timestamps (the time at which the file was processed) to incoming files for audit purposes.

6. Service Availability

6.1.1 The SVAA shall ensure the Services described in this Service Description shall be carried out for each Settlement Day according to the SVAA Calendar, and be available throughout the Working Day.

6.1.2 In addition to paragraph 6.1.1, the SVAA shall provide a logging service for date and timestamping all Non Half Hourly Balancing Mechanism Unit files received on every day of the year.

6.1.3 The SVAA shall ensure the SVA System is capable of being operational for 24 hours per day, less the time reasonably required for planned daily back-up.

6.1.4 The SVAA shall, as required by the BSCCo or its nominated agent, provide the Service for additional VARs other than those required to meet the SVAA Calendar, on a timescale to be agreed with the BSCCo or its nominated agent.

6.1.5 Where required by the BSCCo or its nominated agent, and given five Working Days’ notice, the SVAA shall provide the Service 24 hours per day, less the time reasonably required for planned daily back-up.

In relation to MDD, the SVAA shall ensure that:

6.1.5.1 the MDDM Normal Working Hours are defined as 08:30 to 17:00 on Working Days; and

6.1.5.2 it meets its obligations under this Service Description, regardless of any potential constraints which might be imposed by the definition of MDDM Normal Working Hours.

7. SVA Metering SYSTEM and Asset Metering system REGISTER

7.1.1 The SVAA shall be responsible for the creation and maintenance of the SVA Metering System and Asset Metering System Register. The SVA Metering System and Asset Metering System Register is a register of SVA Metering System Numbers, Asset Metering System Numbers and the Secondary and / or Additional BM Unit to which they have been allocated for the purposes of providing BM or Replacement Reserve Services.

7.1.1A The SVA Metering System and Asset Metering System Register shall also contain SVA Metering System Numbers provided by the NETSO for the purposes of providing Non BM ABSVD. Such SVA Metering System Numbers will not be associated with a BM Unit.

7.1.2 MSID Pair Allocation data will be provided to the SVAA by Suppliers, AMVLPs, VLPs and the NETSO as defined in the SVA Data Catalogue. If the file received cannot be processed the SVAA shall send a notification informing the sender.

7.1.2A AMSID Pair Allocation data will be provided to the SVAA by AMVLPs, as defined in the SVA Data Catalogue, and will identify all associated MSID Pairs and whether the AMSID Pair(s) Delivered Volumes should be used instead of MSID Pair(s) Delivered Volumes or should be used for Asset Differencing.

7.1.3 The SVAA will validate the MSID Pair Allocation data it receives prior to recording that data on the SVA Metering System and Asset Metering System Register. The SVAA shall use data held in the Electricity Enquiry Service (EES) database to facilitate such validation, either using an Automated Programmable Interface (API) of by manual inspection.

7.1.4 Where a MSID Pair submitted by a Supplier, an AMVLP or a VLP, or an AMSID Pair submitted by an AMVLP, is already allocated to a BM Unit that offers Balancing Services, the SVAA shall, subject to validation, confirm the most recent allocation and notify the previous SVA Metering System and Asset Metering System Register registrant of such loss.

7.1.5 The SVAA shall provide functionality to allow a Supplier, AMVLP, VLP or the NETSO to retrospectively correct a MSID Pair Allocation error or, in the case of an AMVLP, an AMSID Pair Allocation error, and that where correction of the identified error ensures that the future accuracy of Settlement.

7.1.5A The SVAA shall provide functionality to allow a Supplier, an AMVLP or a VLP to Baseline MSID Pairs - and to allow an AMVLP to Baseline AMSID Pairs – in BM Units (Additional BM Units for Suppliers and Secondary BM Units for AMVLPs and VLPs).

7.1.5B The SVAA shall provide functionality to allow a Supplier, an AMVLP or a VLP to submit:

i) Baselining Details and Event Days for Baselined BM Units; and

ii) Submitted Expected Volumes for Baselined BM Units with AMSID Pairs or MSID Pairs allocated with Baseline Indicator "Submitted".

7.1.6 When the SVAA validates and confirms a MSID Pair Allocation it shall procure and record MSID Standing Data by either manual enquiry of SMRS data or another source as agreed by the BSC Panel.

7.1.7 The SVAA will further validate MSID Pair Notifications against MSID Standing Data procured from the relevant SMRS. MSID Pair data will be validated to ensure that the data is compliant with MSID Pair specifications.

7.1.7A The SVAA shall not be required to perform the actions set out in paragraphs 7.1.6 and 7.1.7 for AMSID Pair Allocations, as AMSIDs will not be recorded in SMRS.

7.1.8 The SVAA shall provide functionality to facilitate the resolution of Disputed MSID Pair Allocations and Disputed AMSID Pair Allocations.

7.1.9 For each SVA Metering System Number in the SVA Metering System and Asset Metering System Register, the SVAA shall request that the appointed HHDA submits Metering System Half Hourly Metered Data for the period that the related MSID Pair is effective. Where the appointed HHDA rejects such request, the SVAA shall use reasonable endeavours to resolve the issue, including revising the SVA Metering System and Asset Metering System Register and informing BSCCo as necessary.

When a MSID Pair becomes baselined, the SVAA shall also request for each MSID in a Baselined MSID Pair that the HHDA provide historic Metering System Half Hourly Metered Data for the 60 days prior to the Baselining Effective From Date.

7.1.9A For each Asset Metering System Number in the SVA Metering System and Asset Metering System Register, the SVAA shall not be required to request that the appointed HHDC submits Asset Metering System Half Hourly Metered Data for the period that the related AMSID Pair is effective. Instead, each HHDC shall submit Asset Metering System Half Hourly Metered Data to the SVAA for each Asset Metering System Number for which it has been appointed by an AMVLP in accordance with the dates specified in the relevant contract.

7.1.10 SVAA shall ensure that the allocation data contained with the SVA Metering System and Asset Metering System Register is available for each Settlement Run for each Settlement day.

7A. REGISTRATION OF Asset Metering systemS

7A.1 SVAA shall validate Asset Metering Systems registration data submitted to the SVA Metering System and Asset Metering System Register by an AMVLP in three stages, in accordance with BSCP602:

7A.1.1 Stage 1 Asset Registration;

7A.1.2 Stage 2 Asset Metering Party Agent Registration; and

7A.1.3 Stage 3 Asset Meter Registration.

7A.2 If the Asset Metering Systems registration data for a registration stage submitted under 7A.1 fails validation, the SVAA shall issue a Rejection Notification to the AMVLP and shall not process any registration data for a subsequent registration stage submitted by the AMVLP in respect of that Asset Metering System until such time that the AVLP has corrected all errors in the previously rejected Registration Stage data.

7A.3 If the Asset Metering Systems registration data for a registration stage submitted under 7A.1 passes validation, the SVAA shall issue a Confirmation Notification to the AMVLP and shall process the registration data for the subsequent registration stage when received from the AMVLP.

7A.4 If the Asset Metering Systems Stage 1 Registration data passes validation, the SVAA shall generate an AMSID Pair and include details of such AMSID Pair in the Confirmation Notification to the AMVLP.

7A.4 The SVAA shall not process any AMSID Pair Allocations received pursuant to paragraph 7.1.3 until such time that all three Asset Metering System Registration Stages have passed validation.

7A.5 The SVAA shall ensure that any Asset Registration Stage data that has passed validation shall be stored in the SVA Metering System and Asset Metering System Register.

7B. AMSID PAIRS

7B.1 An AMSID Pair shall comprise an Import AMSID and, where so required, an Export AMSID.

7B.2 Each Asset Metering System Number, which is also referred to as ‘Asset Metering System Number’, shall be an unique 13-digit number, which shall comprise:

    • Digits 1-2 – shall always be “77”;

    • Digits 3-12 – shall be an unique 10-digit number; and

    • Digit 13 – shall be generated from digits 1-12 using a checksum algorithm.

8. Appendices

8.1 Appendix 1 - Details of Information Maintained

The following minimum information shall be retained by the SVAA. This information may be held in various forms, such as database records, problem management logs, exceptions reports or manual records, and will be extracted and made available to the BSCCo or its nominated agent on request. The SVAA shall ensure that it also maintains records of any additional information required to fulfil its obligations under this Service Description or any other contractual obligation.

Type of Information

Minimum Requirements

Market Domain Data Details

(for each Market Domain Data load into SVAA)

MDD Version number

Date and Time loaded into ISRA

Details of any validation errors including:

Nature of Error

When BSCCo or its nominated agent informed

Whether BSCCo informed within BSCP timescale

Details of Action Taken

NHHDA Details

(for each file received from a NHHDA)

Run Number of File

MPID of NHHDA

Settlement Date

Run Type

Date and Time of Receipt

Deadline

Number of files received from that Originator for that Volume Allocation Run

Date and time validated

Whether validated within BSCP timescale

Details of any Validation errors including:

Nature of Error

When notification of validation error sent

Whether sent within BSCP timescale

Medium by which sent

Address where sent (network, fax no, physical, etc)

Volume Allocation Runs file used in

HHDA Details

(for each file received from a HHDA)

Same as for NHHDA

HHDC Details

(for each file received from a HHDC)

Run Number of File

MPID of HHDC

Settlement Date

Date and Time of Receipt

Deadline

Number of files received from that Originator for each AMSID

Date and time validated

Whether validated within BSCP timescale

Details of any Validation errors including:

Nature of Error

When notification of validation error sent

Whether sent within BSCP timescale

Medium by which sent

Address where sent (network, fax no, physical, etc)

Volume Allocation Runs file used in

Supplier, AMVLP or VLP Details (for each file received from a Supplier, AMVLP or VLP)

MPID of Supplier AMVLP or VLP

Settlement Date

Secondary BM Unit Id

MSID Pair EFD

MSID Pair ETD

Import MSID

Import MSID Customer Consent EFD

Import MSID Customer Consent ETD

Export MSID

Export MSID Customer Consent EFD

Export MSID Customer Consent ETD

AMSID Pair EFD*

AMSID Pair ETD*

Import AMSID *

Export AMSID*

Date and Time of Receipt

Date and time validated

Whether validated within BSCP timescale

Details of any Validation errors including:

Nature of Error

When notification of validation error sent

Whether sent within BSCP timescale

Volume Allocation Runs file used in

* AMVLPs only

NETSO Details (for each file received from the NETSO)

Settlement Date

MSID Pair EFD

MSID Pair ETD

Import MSID

Import MSID Customer Consent EFD

Import MSID Customer Consent ETD

Export MSID

Export MSID Customer Consent EFD

Export MSID Customer Consent ETD

Date and Time of Receipt

Date and time validated

Whether validated within BSCP timescale

Details of any Validation errors including:

Nature of Error

When notification of validation error sent

Whether sent within BSCP timescale

Volume Allocation Runs file used in

Type of Information

Minimum Requirements

Activations Data (for each file received from SAA)

Settlement Date

BM Unit Id (Primary and Secondary)

Settlement Period

Balancing Mechanism activations

Replacement Reserve activations for each Quarter Hour

GSP Group Take Details

(for each file received from the CDCA)

Run Number of File

Settlement Date

Run Type

Date and Time of Receipt

Deadline

If received after deadline:

When the BSCCo or its nominated agent informed

Whether within BSCP timescale

Details of action taken

Details of any validation errors, including:

Nature of error

When notification of validation error sent

Whether sent within BSCP timescale

Medium by which sent

Address where sent (network, fax no, physical, etc)

Name of Information

Minimum Requirements

LLF Details

(for each file received from BSCCo or its nominated agent)

Date and time file created

Date and time of receipt

Details of any validation errors, including:

Nature of Error

When the BSCCo or its nominated agent informed

Whether informed within BSCP timescale

Details of Action Taken

Type of Information

Minimum Requirements

Manual Standing Data Change Details

(for every time the standing data is updated by manual input)

Input parameter description

Input parameter value

Effective-from Settlement Date

Effective-to Settlement Date

Identity of operator authorising change

If change was made to accept a file from Data Aggregator:

Details of file from Data Aggregator

Details informing BSCCo or its nominated agent of changes to standing data.

If conflict with Non Half Hourly Balancing and Settlement Code Data Aggregator standing data – details of notifications to the BSCCo or its nominated agent

If conflict with Non Half Hourly Balancing Mechanism Unit standing data:

Details of condition

Details of action taken

Volume Allocation Run Details (for every VAR)

Settlement Date

Settlement Code

Time and date

Input files used

Input parameters used

Details of any warning or error condition, including:

Details of condition

Details of action taken

Missing Input Data Details

(for every VAR) =

Settlement Date

Settlement Code

Type of data missing

Originator of missing data:

When Contacted

By which medium

Whether within BSCP timescale

Details of Correspondence

Details of substituted data

Type of Information

Minimum Requirements

Output Report Details

(for every VAR)

Type of report

To whom sent

Settlement Date

Settlement Code

Time and date sent

Sent within BSCP timescales

Medium by which sent

Address

If late or missing:

Time and date the SVAA first realised the report would not meet the deadline

Time and date recipient contacted

Contact’s name / area

Medium by which contacted

Output Report Details

(for every VAR)

Details of report requested, including:

File type

Settlement Date

Run type

MPID of original recipient

MPID of requestor

When requested

Whether authorisation correct

If authorisation not correct:

Date and time of contacting authorised Party

Medium by which contacted

Whether within BSCP timescale

Details of response

Whether update accepted as authorised

Date and time file re-sent

Whether re-sent within four Working Hours

Type of Information

Minimum Requirements

Receiving Updates

(for every Market Domain Data update received)

Version Number of Update

Date and Time received

Medium by which received

Intended MDD Publication Date

Date and Time of Validation

Whether validated within timescales agreed with the BSCCo or its nominated agent

Details of any validation errors including:

Nature of Error

Date and Time of Contacting BSCCo

Whether contacted within BSCP timescales

If not contacted within BSCP timescales, the number of days late

Problems with MDD

(for every problem reported from the BSC Service Desk

Date and Time of receipt of query from BSC Service Desk

Nature of query

Date & Time of Contacting BSCCo or its nominated agent

Whether BSCCo contacted within BSCP timescale

Date and time of contacting BSCCo

Within BSCP timescale (Y/N)

Sending Files

(for every Market Domain Data Publish)

Type of Report

MDD Version Number

Sent to whom

Time and date sent

If not sent within timescales specified in the MDD Change Management Circular, number of days late.

Medium by which sent

Address

If acknowledgement not received within four Working Hours of despatch:

Date and time of re-send

Whether within timescale

If not, number of days late

If acknowledgement of re-send not received within four Working Hours:

Whether acknowledgment of original send has been received

If not, then date and time of informing BSC Service Desk

Whether within timescale

If not, number of days late

Daily Profile Production Data

Temperature Data (P0033)

Sunset Data (P0011)

Teleswitch Contact Interval Data (D0277)

Name of Information

Minimum Requirements

SVA Metering System and Asset Metering System Register Details

Date and time of receipt of MSID Pair Allocation or AMSID Pair Allocation

Details of any validation errors, including:

Nature of Error

When the Lead Party was informed

Whether informed within BSCP timescale

Details of any successful validation, including:

When the Lead Party or the NETSO was informed

Whether informed within BSCP timescale

Details of any Disputed MSID Pair Allocations, including:

Nature of dispute

When the Current Lead Party was informed

When the Current Lead Party replied

Whether Parties are within BSCP timescale

Name of Information

Minimum Requirements

Non-Final Demand Facility Declaration

Source of Declaration, including:

Supplier Contact E-mail Address

Supplier MPID

Declaration information, including:

Declaration Type

Declaration Set ID

Declaration ID

Declaration effective dates

Facility Operator (FO) details, including:

FO Participant ID

FO Company Number

FO Company Name

FO Company Address

FO Company Director

FO Company Director E-mail Address

FO Contact Name

FO Contact Phone

FO Contact e-mail

Facility Category

Facility details, including:

Facility ID

Facility Name

Facility Address/Location

Facility Description

Facility Maximum Import Capacity

Facility Maximum Export Capacity

Facility Effective From Date

Facility Effective To Date

Total MSIDs Count

Metering System (MS) details, including:

MSID

MS Import/Export Indicator

MS GSP Group

MS SF Effective From Date

MS SF Effective To Date

MS Supplier Effective From Date

MS HHDA MPID

MS HHDA Effective From Date

8.2 Appendix 2 - SVAA Calendar and Data Aggregation and Settlements Timetable File

8.2.1 Distributed in the MDD Complete / MDD Incremental Set files, the SVAA Calendar will contain for each VAR, inter alia:

    • Settlement Code;

    • Settlement Date;

    • Payment Date; and

    • SVA Notification Deadline Date (for receipt of files from CDCA, NHHDA, HHDA and LDSO).

The files will contain those data items listed below, for each Settlement Day, inter alia:

    • Clock Changes;

    • Day of the Week Id; and

    • Season Id.

8.2.2 Distributed in the Data Aggregation and Settlements Timetable File, the file will contain for each VAR, inter alia:

    • First Payment Date;

    • Last Payment Date;

    • Settlement Code;

    • Settlement Date;

    • Payment Date;

    • SVA Notification Deadline Date; and

    • Planned Data Aggregation Run Date.

1 The SVAA may be required to review a draft version of the Post Final Settlement Calendar before approval and publication by BSCCo.

2 A ‘Host LDSO’ is an LDSO operating a distribution network that is directly connected to the Transmission System in their own distribution licence area.