BSCP602: SVA Metering System & Asset Metering System Register
Balancing and Settlement Code
BSC Procedure
SVA METERING SYSTEM & ASSET METERING SYSTEM REGISTER
BSCP602
Date:
|
Intellectual Property Rights, Copyright and Disclaimer The copyright and other intellectual property rights in this document are vested in Elexon or appear with the consent of the copyright owner. These materials are made available for you for the purposes of your participation in the electricity industry. If you have an interest in the electricity industry, you may view, download, copy, distribute, modify, transmit, publish, sell or create derivative works (in whatever format) from this document or in other cases use for personal academic or other non-commercial purposes. All copyright and other proprietary notices contained in the document must be retained on any copy you make. All other rights of the copyright owner not expressly dealt with above are reserved. No representation, warranty or guarantee is made that the information in this document is accurate or complete. While care is taken in the collection and provision of this information, Elexon Limited shall not be liable for any errors, omissions, misstatements or mistakes in any information or damages resulting from the use of this information or action taken in reliance on it. |
Version | Date | Description of Change | Changes Included | Mods/Panel/Committee Refs. |
1.0 | 28 Feb 2019 | February 2019 Release | P344 | Panel 284C/01 |
2.0 | 01 Apr 2020 | April 2020 Release | P354, P388 | Panel 276/04 |
3.0 | 01 April 2021 | April 2021 Release | P383 | Panel 312/08 |
4.0 | 30 June 2022 | June 2022 Release | P375, P433 | Panel 318/06, Panel 322/05 |
5.0 | 23 Feb 2023 | February 2023 Release | P376,P419 | P312/04, P323/06 |
6.0 | 29 June 2023 | June 2023 Release | CP1580 | P338/04 |
7.0 | 02 November 2023 | November 2023 Release | P395 |
1 Introduction
1.1 Purpose and Scope of the Procedure
1.1.1 MSID Pair and AMSID Pair allocation
Suppliers, Virtual Lead Parties (VLPs), Asset Metering Virtual Lead Parties (AMVLPs2) and the NETSO should follow when submitting MSID Pair allocation(s) and MSID Pair Delivered Volumes to the SVAA;
AMVLPs3and Suppliers should follow when registering an Asset thus creating AMSID number(s) and an AMSID Pair; and
AMVLPs should follow when submitting MSID Pair allocation(s) and AMSID Pair allocation(s) and MSID Pair Delivered Volumes or AMSID Pair Delivered Volumes to the SVAA.
to ensure maintenance of an accurate, up-to-date SVA Metering System and Asset Metering System Register;
to ensure the correct working of the SVAA internal processing for use in validating submissions of MSID Pair Allocations and AMSID Pair Allocations to the SVA Metering System Register;
to ensure MSID Pair Delivered Volumes and AMSID Pair Delivered Volumes are determined in good faith, in accordance with Good Industry Practice and notified in a timely manner; and
to ensure the correct working of the SVAA internal processing for use in validating MSID Pair Delivered Volumes and AMSID Pair Delivered Volumes.
1.1.2 Supporting the calculation of network charges
1.1.3 Baselined BM Units
Baselined MSID Pairs (or AMSID Pairs): The SVAA will use historic metered data to calculate the baseline consumption for the MSID Pair in accordance with the Baselining Methodology
Non-Baselined MSID Pairs (or AMSID Pairs): The Lead Party works out the FPN-equivalent, and submits a total figure (per BM Unit and Settlement Period) for all the non-Baselined MSID Pairs
Inactive MSID Pairs (or AMSID Pairs): excluded from the BM Unit (for Settlement purposes). Secondary BM Units only.
EMR MSID Declaration: where Generation and / or Battery Storage – but no Final Demand - is supplied via a SVA Import Metering System5, the Supplier for that Metering System should specify the SVA Boundary Point Import MSID.
EMR AMSID Declaration: where Generation and / or Battery Storage is co-located with Final Demand is supplied by one or more Import SVA Boundary Point Metering Systems which have the same Supplier, the Import Supplier should specify the relevant SVA Boundary Point MSID Pair(s) and AMSID Pair(s) that relate to the Licensed Generation and / or Battery Storage facilities. Each Generation and Battery Storage facility must be registered as an Asset in accordance with Sections 2.9 – 2.11 of this BSCP to obtain the AMSID Pair.
EMR CVA BM Unit Declaration: where Generation and / or Battery Storage is located behind one or more CVA Boundary Point Metering Systems included in a single CVA BM unit (Type T or E only), the registrant of that BM Unit should specify that CVA BM Unit.
1.2 Main Users of the Procedure
Suppliers
VLPs
AMVLPs
The NETSO
SVAA
SVA Non-Final Demand Facility Operators
1.3 Use of Procedure
1.4 Balancing and Settlement Code Provisions
1.5 Associated BSC Procedures
BSCP15 | BM Unit Registration |
BSCP503 | Half Hourly Data Aggregation for SVA Metering Systems Registered in SMRS |
BSCP507 | Supplier Volume Allocation Standing Data Changes |
BSCP508 | Supplier Volume Allocation Agent |
BSCP537 | Qualification Process for SVA Parties, SVA Party Agents VLPs, AMVLPs, AMVLP Agents and CVA MOAs |
BSCP603 | Meter Operations and Data Collection for Asset Metering Systems |
1.6 Acronyms and Definitions
Acronym | Expression |
AMHHDC | Asset Metering Half Hourly Data Collector |
AMMOA | Asset Metering Meter Operator Agent |
AMSID | Asset Metering System Identifier |
AMVLP | Asset Metering Virtual Lead Party |
BM | Balancing Mechanism |
BSC | Balancing and Settlement Code (the “Code”) |
BSCCo | Balancing and Settlement Code Company |
BSCP | Balancing and Settlement Code Procedure |
BSP | Balancing Service Provider |
BSUoS | Balancing Services Use of System |
CRA | Central Registration Agent |
ECOES | Electricity Central Online Enquiry Service |
EFSD | Effective From Settlement Date |
EMR | Electricity Market Reform |
ETSD | Effective To Settlement Date |
FCL | Final Consumption Levy |
HHDA | Half Hourly Data Aggregator |
HHDC | Half Hourly Data Collector |
kWh | Kilowatt-hour |
MOA | Meter Operator Agent |
MSID | Metering System Identifier |
Ref | Reference |
SVA | Supplier Volume Allocation |
SVAA | Supplier Volume Allocation Agent |
TNUoS | Transmission Network Use of System |
TUoS | Transmission Use of System |
VAR | Volume Allocation Run |
WD | Working Day |
2. Interface and Timetable Information
2.1 MSID Pair Allocation Notification
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.1.1 | At least 5 WD before the EFSD of the MSID Pair | Send the MSID Pair Allocation | Lead Party, NETSO | SVAA | P0278 – MSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
2.1.2 | As required upon receiving additional information | Send an amended MSID Pair Allocation7 | Lead Party, NETSO | SVAA | P0278 – MSID Pair Allocation Appendix 3.2 – Amendments to MSID Pair Allocations | Self-Service Gateway, as agreed. |
2.1.3 | Within 1 WD of 2.1.1 or where appropriate within 1 WD of 2.1.2 | If the MSID Pair Allocation was not submitted via the Self-Service Gateway, log MSID Pair in the SVA Metering System and Asset Metering System Register. | SVAA |
|
| Internal Process |
2.1.4 | Immediately following 2.1.1, 2.1.2 or 2.1.3 | Validate MSID Pair Allocation in accordance with Appendix 3.1 – Validation of MSID Pair Allocation and AMSID Pair Allocation files | SVAA |
| Appendix 3.1 – MSID Pair Allocation File Validation |
|
2.1.5 | Immediately following2.1.4
| If MSID Pair Allocation is invalid, the SVAA shall send notification of the rejection to the Lead Party or the NETSO | SVAA | Lead Party, NETSO | P0280 – Rejection of MSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
2.1.6 | After 2.1.5 | Return to 2.1.2 if Lead Party or the NETSO wishes to provide revised notification. | Lead Party NETSO |
|
|
|
2.1.7 | Immediately following 2.1.4 or where appropriate within 1 WD of 2.1.2 | If MSID Pair Allocation is valid, log the MSID Pair in the SVA Metering System & Asset Metering System Register . | SVAA |
|
|
|
2.1.8 | Immediately following 2.1.7 | Send confirmation of MSID Pair Allocation. | SVAA | Lead Party, NETSO | P0279 – Confirmation of MSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
2.1.9 | Immediately following 2.1.7 | Where an MSID Pair is allocated to a Lead Party and to the NETSO at the same time the SVAA shall notify the NETSO of the dual allocation immediately. Note that this is allowed, and so the Lead Party will not lose the MSID Pair. | SVAA | NETSO | Import MSID and related Secondary BM Unit Id. | Email or other method, as agreed. |
2.1.10 |
| If the MSID Pair was already allocated to a different Lead Party, the SVAA shall transfer the MSID Pair allocation from that Lead Party (the ‘Losing Lead Party’) to the new Lead Party (the ‘Gaining Lead Party’) in the SVA Metering System & Asset Metering System Register. | SVAA |
| Internal process |
|
2.1.11 | Within 1 WD of 2.1.10 | Upon allocation to the Gaining Lead Party the SVAA shall send a Loss of MSID Pair Allocation notification to the Losing Lead Party | SVAA | Losing Lead Party | P0281 – Loss of MSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
2.1.12 |
| If the Losing Lead Party disagrees with the Loss of MSID Pair Allocation they may initiate the Disputed MSID Pair Allocation Process (go to Section 2.3.1). | Losing Lead Party |
|
|
|
2.1A AMSID Pair Allocation to a Secondary BM Unit
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.1A.1 | At least 1 WD before the AMSID Pair will be used in the Secondary BM Unit | Submit an AMSID Pair Allocation | AMVLP | SVAA | P0306 – AMSID Pair Allocation to a Secondary BM Unit | Self-Service Gateway or other method, as agreed. |
2.1A.2 | As required | Submit an amended AMSID Pair Allocation9 | AMVLP | SVAA | P0306 - AMSID Pair Allocation to a Secondary BM Unit Appendix 3.2 – Amendments to a MSID Pair Allocation or an AMSID Pair Allocation | Self-Service Gateway, or other method, as agreed. |
2.1A.3 | Within 1 WD of 2.1A.1 or 2.1A.2 | If the AMSID Pair Allocation was not submitted via the Self-Service Gateway, log AMSID Pair Allocation in the SVA Metering System and Asset Meter Register. | SVAA |
|
| Internal Process |
2.1A.4 | Immediately following 2.1A.1, 2.1A2 or 2.1A.3 | Validate AMSID Pair Allocation. | SVAA |
| Appendix 3.1 – Validation of MSID Pair Allocation or AMSID Pair Allocation File Appendix 3.10 - Valid combinations of ‘MSID Pair Indicator’ and ‘AMSID Pair Differencing Indicator’ in a Secondary BM Unit. Appendix 3.12 Effect of Proposed AMSID Pair use in AMSID Pair Allocations. | Internal Process |
2.1A.5 | Immediately following 2.1A.4 | If the AMSID Pair Allocation fails validation, reject the AMSID Pair Allocation. | SVAA | AMVLP | P0308 – Rejection of AMSID Pair Allocation to a Secondary BM Unit | Self-Service Gateway |
2.1A.6 | Immediately following 2.1A.5, or as required | Return to 2.1A.2 if AMVLP wishes to provide a revised AMSID Pair Allocation. |
|
|
|
|
2.1A.7 | After 2.1A.4 | If the AMSID Pair Allocation is valid, and the AMSID Pair is not already allocated to another Secondary BM Unit, allocate the AMSID Pair to the Secondary BM Unit and notify the AMVLP | SVAA | AMVLP | P0307– Confirmation of AMSID Pair Allocation to a Secondary BM Unit | Self-Service Gateway |
2.1A.8 | After 2.1A.4 | If the AMSID Pair Allocation is valid, but the AMSID Pair is already allocated to another Secondary BM Unit for the same purpose:
| SVAA |
|
| Internal Process |
2.1A.9 | After 2.1A.8 | Notify ‘Gaining’ AMVLP of successful AMSID Pair Allocation
| SVAA | AMVLP | P0307– Confirmation of AMSID Pair Allocation to a Secondary BM Unit | Self-Service Gateway |
2.1A.10 | After 2.1A.8 | Notify ‘Losing’ AMVLP’ of the loss of the AMSID Pair from its Secondary BM Unit | SVAA | AMVLP | P0320 – Loss of AMSID Pair Allocation Notification | Self-Service Gateway |
2.1A.11 | After 2.1A.10 | AMVLPs agree the effective from date for the transfer of responsibility for the Asset Metering System to the Gaining AMVLP. | Losing AMVLP | Gaining AMVLP |
| Telephone, email or other method, as agreed. |
2.1A.12 | After 2.1A.11 and at least 5WD before Effective From Date | Notify SVAA of the new Registrant AMVLP for the Asset Metering System. | Gaining AMVLP | SVAA | P0297 Asset Registration with the “Action Indicator” set to ‘Change of Registrant’ | Self-Service Gateway, or other method, as agreed. |
2.1A.13 | After 2.1A.12 | If the P0297 is invalid, reject the file and notify the AMVLP | SVAA | Gaining AMVLP | P0298 – Rejection of Asset Registration | Internal process |
2.1A.14 | After 2.1A.13 | If the P0297 is valid, amend the AMVLP Id of the AMVLP responsible for the Asset in the Register. NB As this is not a new Asset Registration, SVAA shall keep the existing AMSID Pair relating to the Asset. | SVAA |
|
|
|
2.1A.15 | After 2.1A.14 | Notify the new AMVLP of the Successful change of Registrant AMVLP for the Asset.
| SVAA | Gaining AMVLP | P0299 Confirmation of Asset Registration. | Self-Service Gateway |
2.1A.16 | After 2.1A.15 | Where the new AMVLP decides to replace one or both Asset Metering Agent, go to 2.10.1 to Register the new Asset Metering Agent(s) |
|
|
|
|
2.1A.17 | After 2.1A.4 | If the AMSID Pair Allocation is valid, but the AMSID Pair is already allocated to another Secondary BM Unit for a different purpose:
|
|
|
| Internal Process |
2.1A.18 | After 2.1A.17 | Notify AMVLP of the successful allocation of the AMSID Pair to its BM Unit. | SVAA | AMVLP | P0307– Confirmation of AMSID Pair Allocation to a Secondary BM Unit | Self-Service Gateway |
Notify the AMVLP that already had the AMSID Pair Allocated to its BM Unit of this Allocation. | SVAA | AMVLP | P0309 - Notification of use of AMSID Pair by another AMVLP | Self-Service Gateway | ||
2.1A.19 | At any time after 2.1A.18 | If either AMVLP decides to stop using the AMSID Pair, notify the other AMVLP. | SVAA | AMVLP | P0309 - Notification of use of AMSID Pair by another AMVLP | Self-Service Gateway |
2.1A.20 | After 2.1A.19 | If the AMVLP that has decided to stop using the AMSID Pair was the ‘Registrant’ AMVLP, then the remaining AMVLP11 must either:
or
|
|
|
P0297 - Asset Registration - populated with Action Indicator ‘C’
P0306 - AMSID Pair Allocation to a Secondary BM Unit - populated with a non-null ‘AMSID Pair in Secondary BM Unit ETD’
P0297 - Asset Registration - populated with Action Indicator ‘D’ |
|
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.2A.1 | Within 1 WD of the provision of a Balancing Service | Submit the MSID Pair Delivered Volume for each MSID Pair used to delivered a Balancing Service
Submit the AMSID Pair Delivered Volume for each AMSID Pair used to deliver a Balancing Service via Asset Metering. Or Submit the MSID Pair Delivered Volume for each AMSID Pair used to deliver a Balancing Service via Asset Differencing or where no AMSID Pair used.
| VLP
AMVLP | SVAA
SVAA | P0282 – Delivered Volume Notification13 | Electronic or other method, as agreed. |
2.2A.2 | As required14 | Re-submit MSID Pair Delivered Volume or AMSID Pair Delivered Volume | VLP AMVLP | SVAA SVAA | P0282 –Delivered Volume Notification | Electronic or other method, as agreed. |
2.2A.3 | Within 1 WD of 2.2A.1 or where appropriate within 1 WD of 2.2A.2 | Log and validate MSID Pair Delivered Volume or AMSID Pair Delivered Volume. | SVAA |
| Appendix 3.4 Delivered Volume File Validation | Internal process. |
2.2A.4 | Within 1 WD of 2.2A.1 or where appropriate within 1 WD of 2.2A.2 | If the file cannot be processed send notification. | SVAA | VLP or AMVLP | Negative Acknowledgement | Electronic or other method, as agreed. |
|
| Return to 2.2A.2 if VLP wishes to provide revised MSID Pair Delivered Volume or AMVLP wishes to provide revised MSID Pair Delivered Volume or AMSID Pair Delivered Volume. |
|
|
|
|
2.2A.5 | Within 1 WD of 2.2A.1 or where appropriate within 1 WD of 2.2A.2 | If MSID Pair Delivered Volume fails validation send rejection. If AMSID Pair Delivered Volume fails validation send rejection. | SVAA | VLP or AMVLP
AMVLP | P0283 – Rejection of Delivered Volume10 | Electronic or other method, as agreed. |
|
| Return to 2.2A.2 if VLP wishes to provide revised MSID Pair Delivered Volume or AMSID Pair Delivered Volume. |
|
|
|
|
2.2A.6 | Within 1 WD of 2.2A.1 or where appropriate within 1 WD of 2.2A.2 | If MSID Pair Delivered Volume passes validation send confirmation. | SVAA | VLP or AMVLP
| P0284 – Confirmation of Delivered Volume10 | Electronic or other method, as agreed. |
If AMSID Pair Delivered Volume passes validation send confirmation | SVAA | AMVLP | ||||
2.2A.7 | As late as possible to meet the relevant VAR for the SD (to ensure most recent data from VLP or AMVLP) to meet the SVAA Calendar. | Perform checks in accordance with Appendix 3.6 | SVAA |
| Appendix 3.6 – MSID Pair / AMSID Pair Delivered Volume Allocation
|
Internal process |
2.2A.8 | Immediately following 2.2A.7 | If appropriate, send Delivered Volume Exception Report. | SVAA | VLP or AMVLP | P0285 –Delivered Volume Exception Report8 | Electronic or other method, as agreed. |
2.2B MSID Pair Delivered Volume Notification by the NETSO
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.2B.1 | Within 45 WD of the provision of a non BM Applicable Balancing Service to the NETSO | Submit the ABS MSID Pair Delivered Volume for each MSID Pair used to deliver the Balancing Service | NETSO | SVAA | P0292 – ABS MSID Pair Delivered Volume Notification | Electronic or other method, as agreed. |
2.2B.2 | As required15 | Re-submit ABS MSID Pair Delivered Volume | NETSO | SVAA | P0292 – ABS MSID Pair Delivered Volume Notification | Electronic or other method, as agreed. |
2.2B.3 | Within 1 WD of 2.2B.1 or where appropriate within 1 WD of 2.2B.2 | Log and validate ABS MSID Pair Delivered Volume | SVAA |
| Appendix 3.5 – ABS MSID Pair Delivered Volume File Validation | Electronic or other method, as agreed. |
2.2B.4 | Within 1 WD of 2.2B.1 or where appropriate within 1 WD of 2.2B.2 | If the file cannot be processed send notification. | SVAA | NETSO | Negative Acknowledgement | Electronic or other method, as agreed. |
|
| Return to 2.2B.1 if the NETSO wishes to provide revised ABS MSID Pair Delivered Volume |
|
|
|
|
2.2B.5 | Within 1 WD of 2.2B.1 or where appropriate within 1 WD of 2.2B.2 | If ABS MSID Pair Delivered Volume fails validation send rejection. | SVAA | NETSO | P0293 – Rejection of ABS MSID Pair Delivered Volume | Electronic or other method, as agreed. |
|
| Return to 2.2B.1 if the NETSO wishes to provide revised MSID Pair Delivered Volume |
|
|
|
|
2.2B.6 | Within 1 WD of 2.2B.1 or where appropriate within 1 WD of 2.2.2 | If ABS MSID Pair Delivered Volume passes validation send confirmation. | SVAA | NETSO | P0294 – Confirmation of ABS MSID Pair Delivered Volume | Electronic or other method, as agreed. |
2.2B.7 | As late as possible to meet the relevant VAR for the SD (to ensure most recent data from the NETSO) to meet the SVAA Calendar. | Perform calculations in accordance with Appendix 3.6 and, where it has not been possible to allocate an ABS MSID Pair Delivered Volume to the MSIDs in that MSID Pair, send an exception report to the NETSO | SVAA | NETSO | Appendix 3.6 – ABS MSID Pair Delivered Volume Allocation P0295 – ABS MSID Pair Delivered Volume Exception Report | Electronic or other method, as agreed. |
2.3 Disputed MSID Pair Allocation or Disputed AMSID Pair Allocation Resolution
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.3.1 | Within 5 WD of receipt of a Loss of MSID Pair / AMSID Pair Allocation notification in 2.1.8 | Initiate the Disputed MSID Pair Allocation or Disputed AMSID Pair Allocation Resolution Process in accordance with Section 3.3 of this document. | Losing Lead Party / AMVLP
Losing AMVLP | Gaining Lead Party / AMVLP
Gaining AMVLP | P0286 – Disputed MSID Pair Allocation or P0312 Disputed AMSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
2.3.2 | Within 5 WD of 2.3.1 | Respond to Disputed MSID Pair Allocation or Disputed AMSID Pair Allocation notification | Gaining Lead Party
Gaining AMVLP | Losing Lead Party
Losing AMVLP | P0286 – Disputed MSID Pair Allocation or P0312 Disputed AMSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
2.3.3 |
| Once the initial request has been made one of the following options shall be taken
or
|
|
|
| Internal Process |
2.3.4 | Same day as 2.3.3 | If both parties agree to the resolution of the Disputed MSID Pair Allocation or Disputed AMSID Pair Allocation go to 2.3.6 |
|
|
|
|
2.3.5 | Following 2.3.3 | If the Gaining Lead Party does not agree with the resolution in 2.3.3 and the Losing Lead Party wishes to re-raise the dispute, go to 2.3.1. See Appendix 3.3.6 for guidance. |
|
|
|
|
2.3.6 | Within 1 WD of 2.3.4 | Send a revised MSID Pair Allocation with agreed EFSD and ETSD or Send a revised AMSID Pair Allocation with agreed EFSD and ETSD | Gaining Lead Party
Gaining AMVLP | SVAA
SVAA | P0278 – MSID Pair Allocation or P0306 AMSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
2.3.7 | Within 1 WD of 2.3.4 | Send new MSID Pair Allocation with agreed EFSD and ETSD or Send new AMSID Pair Allocation with agreed EFSD and ETSD | Losing Lead Party
Losing AMVLP | SVAA
SVAA | P0278 – MSID Pair Allocation or P0306 AMSID Pair Allocation | Self-Service Gateway or other method, as agreed. |
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.4.1 | As soon as an SVA Non- Final Demand Facility Operator identifies that it would like to declare a facility | Complete and send a Non- Final Demand Declaration Document
Declaration Documents must be signed by an SVA Non- Final Demand Facility Operator’s director registered with Companies House. | SVA Facility Operator | Supplier(s) | Director-signed Non- Final Demand Declaration Document (Part B-D) – see Appendix 3.7.1.1 and Appendix 3.7.3.
| Agreed between SVA Non- Final Demand Facility Operator and Supplier |
2.4.2 | Within 5WD of 2.4.1 | Send SVA Non- Final Demand Facility Operator’s Declaration Document to the SVAA
| Supplier(s) | SVAA | Director-signed Non- Final Demand Declaration Document (Part A-D). | Self-service gateway, Email or other method agreed |
2.4.3 | Within 2WD of 2.4.2;
or
if the SVAA determines that a Declaration is one of a set18 then within 5WD of 2.4.2. | Check that each Non- Final Demand Declaration Document is complete and valid. The SVAA may liaise with the Supplier that submitted the declaration to seek additional information, corrections or a resubmission of the declaration.
The SVAA must register (or update) details of each SVA Non- Final Demand Facility declared to it, irrespective of whether successfully validated. | SVAA |
|
| Internal process |
2.4.4 | Within 1WD of 2.4.3 | Notify the Supplier of the outcome of 2.4.3. | SVAA | Supplier | The SVAA must inform the relevant Supplier(s) whether the Declaration for an SVA Non-Final Demand Facility identified in a Declaration Document was successfully validated or not.
Where the SVAA decides a Non-Final Demand Declaration is invalid or incomplete it must provide a short explanation to the Supplier(s). | Email or, where agreed, by other electronic means |
2.4.5 | Following receipt of 2.4.4 | Suppliers should send details of whether a Declaration(s) was successful or not for each declared SVA Non-Final Demand Facility sent per 2.4.2. | Supplier | SVA Storage Non-Final Demand Facility Operator |
| Agreed between SVA Non-Final Demand Facility Operator and Supplier |
2.4.6 | Within 1WD of 2.4.3 | Where an SVA Non-Final Demand Facility is successfully declared, determine whether for each of the facility’s MSIDs to instruct HHDA to begin reporting metered data to the SVAA19.
If instruction required, follow BSCP503 Section 3.7. | SVAA | HHDA | D0354 - Metering System Reporting Notification20 | Electronic, or other method, as agreed. |
2.5 SVA Non-Final Demand Facilities – voluntary withdrawal of an SVA Non-Final Demand declaration21
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.5.1 | As soon as an SVA Non Final Demand Facility Operator identifies that it must send notice that a declaration must end | Complete and send a Declaration Document to Supplier(s)
Declaration Documents must be signed by a Non Final Demand Facility Operator’s director registered with Companies House. | SVA Non Final Demand Facility Operator | Supplier(s) | Director-signed Declaration Document (Part B-D) – see Appendix 3.7.1.3 and Appendix 3.7.3.
| Agreed between SVA Non Final Demand Facility Operator and Supplier |
2.5.2 | Within 5WD of 2.5.1 | Send SVA Non Final Demand Facility Operator’s Declaration Document to the SVAA
| Supplier(s) | SVAA | Director-signed Declaration Document (Part A-D). | Self Service Gateway or Email. |
2.5.3 | Within 2WD of 2.5.2. | Check that each director-signed Declaration Document is complete and valid. The SVAA may liaise with the Supplier that submitted the Declaration Document to seek additional information, corrections or a resubmission of the declaration.
The SVAA must update the details of each SVA Non-Final Demand Facility identified to it to cease being a valid declared facility. | SVAA |
|
| Internal process |
2.5.4 | Within 1WD of 2.5.3 | Notify the Supplier(s) of the outcome of 2.5.3. | SVAA | Supplier(s) | Where the Declaration Document is successfully validated, the SVAA must inform the Supplier(s) that it has updated the registration details for the SVA Non-Final Demand Facility.
Otherwise, where a Declaration Document fails validation, the SVAA must provide a short explanation to the Supplier. | Electronic, or other method, as agreed. |
2.5.5 | Following receipt of 2.5.4 | Notify the SVA Non-Final Demand Facility Operator of the outcome of 2.5.3 and whether the SVAA has updated its records | Supplier(s) | SVA Storage Non-Final Facility Operator | Confirmation (or otherwise) that SVA Non-Final Demand Facility’s Declaration has been updated as having/expected to cease/d. | Agreed between SVA Non Final Demand Facility Operator and Supplier |
2.5.6 | Within 1WD of 2.5.3 | Where a Declaration for an SVA Non-Final Demand Facility has ended or is due to end, determine whether, for each of the facility’s MSIDs, to instruct HHDA to cease reporting metered data to the SVAA22.
If instruction required, follow BSCP503 Section 3.8. | SVAA | HHDA | D0354– Metering System Reporting Notification23 | Electronic, or other method, as agreed. |
2.6 SVA Non-Final Demand Facilities – enforced withdrawal of an SVA Non-Final Demand Facility’s declaration24
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.6.1 | Where the SVAA identifies a need to end a declaration or is instructed by the BSC Panel (via BSCCo) to end a declaration. | Update the details of each SVA Non-Final Demand Facility identified by or to it25 to cease being a valid declared facility. | SVAA |
|
| Internal SVAA process |
2.6.2 | Within 1WD of 2.6.1 | Notify the Supplier(s) of the action taken. | SVAA | Supplier(s) | The SVAA must provide a short explanation to the Supplier(s). | Electronic, or other method, as agreed. |
2.6.3 | Following receipt of 2.6.2 | Notify the SVA Non-Final Demand Facility Operator of the outcome of 2.6.2 | Supplier | SVA Non-Final Demand Facility Operator |
| Agreed between SVA Non-Final Demand Facility Operator and Supplier |
2.6.4 | Within 1WD of 2.6.1 | Where a Declaration for an SVA Non-FinalFacility has ended or is due to end, determine whether, for each of the facility’s MSIDs, to instruct HHDA to cease reporting metered data to the SVAA26.
If instruction required, follow BSCP503 3.8. | SVAA | HHDA | D0354 – Metering System Reporting Notification27 | Electronic, or other method, as agreed. |
2.7 SVA Non- Final Demand Facilities – withdrawal of an SVA Non- Final Demand Operator28
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.7.1 | As soon as an SVA Non- Final Demand Facility Operator identifies that it must or would like to cease to be an SVA Non- Final Demand Operator | Send a SVA Non- Final Demand Operator Withdrawal letter to the SVAA | SVA Non- Final Demand Facility Operator | SVAA | Director-signed Operator Withdrawal letter – see Appendix 3.7.1.5 and Appendix 3.7.4.
| Agreed between SVA Non-Final Demand Facility Operator and Supplier. |
2.7.2 | Within 2WD of 2.7.1 | Check that each SVA Non-Final Demand Operator Withdrawal letter is complete and valid.
| SVAA |
|
| Internal process |
2.7.3 | Where SVA Non-Final Demand Facility Operator Withdrawal Letter successfully validated per 2.7.2
Or
Where Panel instructs the SVAA
Or
Where BSCCo confirms that an SVA Non-Final Demand Facility Operator is no longer | Update the details of the SVA Non-Final Demand Facility Operator and end-date each related SVA Non-Final Demand Facility related to the SVA Non-Final Demand Facility Operator. | SVAA |
|
| Internal process |
2.7.4 | Within 1WD of 2.7.2 | Where the SVA Non-Final Demand Facility Operator Withdrawal is successfully validated, notify the SVA Non-Final Demand Facility Operator and all related Suppliers of the outcome of 2.7.2, and follows the steps in 2.6 to ensure all related SVA Non-Final Facilities are end-dated.
Where the SVA Non-Final Demand Facility Operator Withdrawal letter fails validation, notify the SVA Non-Final Demand Facility Operator of the outcome of 2.7.2 | SVAA | SVA Non-Final Facility Operator, Supplier(s) | Where the SVA Non-Final Demand Facility Operator Withdrawal Letter is successfully validated, the SVAA must inform the SVA Non-Final Demand Facility Operator and the Supplier(s) that it has updated the registration details for the SVA Non-Final Demand Facility Operator and SVA Non-Final Demand Facility(ies).
Otherwise, where a Withdrawal Letter fails validation, the SVAA must provide a short explanation to the SVA Non-Final Demand Facility Operator only. | Email or, where agreed, by other electronic means |
2.8 SVA Non-Final Demand Facilities – update following Change Of Supplier, Change of Agent or change of the Metering Systems registered for the Non-Final Demand Facility29
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.8.1 | As soon as an SVA Non-Final Demand Facility Operator identifies that it must update an existing declaration | Complete and send a Declaration Document to its Supplier(s) | SVA Non-Final Demand Facility Operator | Supplier(s) | Director-signed Declaration Document (Part B-D) – see Appendix 3.7.1.2 and Appendix 3.7.3.
| Agreed between SVA Non-Final Demand Facility Operator and Supplier |
2.8.2 | Within 5WD of 2.8.1 | Send SVA Non-Final Demand Facility Operator’s director-signed Declaration Document to the SVAA
| Supplier(s) | SVAA | Director-signed Declaration Document (Part A-D). | Self Service Gateway or Email |
2.8.3 | Within 2WD of 2.8.2;
or
if the SVAA determines that a Declaration is one of a set30 then within 5WD of 2.8.2. | Check that each director-signed Declaration Document is complete and valid. The SVAA may liaise with the Supplier that submitted the declaration to seek additional information, corrections or a resubmission of the declaration.
Where successfully validated, the SVAA must update the details of each SVA Non-Final Demand Facility. | SVAA |
|
| Internal process |
2.8.4 | Within 1WD of 2.8.3 | Notify the Supplier of the outcome of 2.8.3. | SVAA | Supplier | Where the Declaration Document is successfully validated, the SVAA must inform the Supplier(s) that it has updated the registration details for the SVA Non-Final Demand Facility.
Otherwise, where a Declaration Letter fails validation, the SVAA must provide a short explanation to the Supplier. | Electronic, or other method, as agreed. |
2.8.5 | Following receipt of 2.8.4 | Supplier(s) should notify the SVA Non-Final Demand Facility Operator of the outcome of 2.8.3 and so whether the SVAA has updated its records | Supplier | SVA Non-Final Demand Facility Operator | Confirmation (or otherwise) that SVA Non-Final Demand Facility’s Declaration has been updated as having/expected to cease/d. | Agreed between SVA Non-Final Facility Operator and Supplier |
2.8.6 | Within 1WD of 2.8.3 | Where a Declaration for an SVA Non-Final Demand Facility has ended or is due to end, determine whether, for each of the facility’s MSIDs, to instruct HHDA to cease reporting metered data to the SVAA31.
If instruction required, follow BSCP503 3.8. | SVAA | HHDA | D0354 - Metering System Reporting Notification32 | Electronic, or other method, as agreed. |
2.9 Asset Registration
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.9.1 | At least 10 WD before inclusion in Secondary BM unit or EMR AMSID Declaration | Submit details of the Asset. | AMVLP or Supplier | SVAA | P0297 - Asset Registration | Self-Service Gateway or other method, as agreed. |
2.9.2 | Within 1 WD of 2.9.1 | If Self-Service Gateway was not the method used in 2.9.1, log the Asset details in the Register. | SVAA |
|
| Internal Process |
2.9.3 | Within 1 WD of 2.9.1 | Validate the Asset details. | SVAA |
| Appendix 3.1.1 | Internal Process |
2.9.4 | Immediately following 2.9.3 | If Asset details are invalid, send rejection notification with rejection reason. | SVAA | AMVLP or Supplier | P0298 - Rejection of Asset Registration | Self-Service Gateway |
2.9.5 | After 2.9.4 | Return to 2.9.1 if AMVLP or Supplier wishes to submit valid Asset details. | AMVLP or Supplier |
|
|
|
2.9.6 | Immediately following 2.9.3 | If Asset details are valid, create and store unique AMSID(s) as an AMSID Pair. | SVAA |
|
| Internal Process |
2.9.7 | Immediately following 2.9.6 | Send an acceptance notification, including the AMSID Pair details. | SVAA | AMVLP or Supplier | P0299 - Confirmation of Asset Registration | Self-Service Gateway |
2.9.8 | After 2.9.7 | Go to Section 2.10. | AMVLP or Supplier |
|
|
|
2.10 Registration of Asset Metering Agents for Asset Metering System(s)
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.10.1 | After 2.9.8 or 2.1A.15 | Appoint Asset Metering Agents for the Asset Metering System(s) and related AMSID Pair. | AMVLP or Supplier |
|
| Internal process |
2.10.2 | After 2.10.1 and at least 5 WD before inclusion in Secondary BM unit or EMR AMSID Declaration | Register the Asset Metering Agent details in the SVA Metering System & Asset Metering System Register | AMVLP or Supplier | SVAA | P0300 – Registration of Asset Metering Agents | Self-Service Gateway or other method, as agreed. |
2.10.3 | Within 1 WD of 2.10.2
| If Self-Service Gateway was not used in 2.10.2, log the Asset Metering Agent details in the Register | SVAA |
|
| Internal process |
2.10.4 | Immediately following 2.10.2 or 2.10.3 | Validate Asset Metering Agent details | SVAA |
| Appendix 3.1.2 | Internal process |
2.10.5 | Within 1 WD of 2.10.4
| If Asset Metering Agent details are invalid, send rejection notification with rejection reason | SVAA | AMVLP or Supplier | P0301 - Rejection of Asset Metering Agent Registration | Self-Service Gateway |
2.10.6 | After 2.10.5 | Return to 2.10.1 if AMVLP or Supplier wishes to submit valid Asset Metering Agent details | AMVLP or Supplier |
|
|
|
2.10.7 | Within 1 WD of 2.10.4 | If Asset Metering Agent Details are valid, send acceptance notification | SVAA | AMVLP or Supplier | P0302 - Confirmation of Asset Metering Agent Registration | Self-Service Gateway |
2.10.8 | After 2.10.7 | Go to 2.11.1 | AMVLP or Supplier |
|
|
|
2.11 Registration of Asset Meter Details for an Asset and related Asset Metering Systems
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.11.1 | After 2.10.8 and at least 3 WD before allocation of the AMSID Pair to a Secondary BM Unit | Submit Asset Meter details. | AMVLP or Supplier | SVAA | P0303 - Asset Meter Registration | Self-Service Gateway or other method, as agreed. |
2.11.2 | Within 1 WD of 2.11.1 | If Self-Service Gateway was not the method used, in 2.11.1, log the Asset Meter details in the Register. | SVAA |
|
| Internal Process |
2.11.3 | Within 1 WD of 2.11.1 | Validate the Asset Meter details. | SVAA |
| Appendix 3.1.3 | Internal Process |
2.11.4 | Immediately following 2.11.3 | If Asset Meter details are invalid, send rejection notification with rejection reason.
If Asset Meter details are valid, but have already been registered, send rejection notification with rejection reason “This Asset has already been registered and AMSID Pair [xxxxxxxxxxxxx_yyyyyyyyyyyyy] has been generated. You may use this AMSID Pair without being the Registrant of the Asset”. | SVAA | AMVLP or Supplier | P0304 - Rejection of Asset Meter Registration
P0304 - Rejection of Asset Meter Registration | Self-Service Gateway |
2.11.5 | After 2.11.4 | Return to 2.11.1 if AMVLP wishes to submit revised Asset Meter details | AMVLP or Supplier |
|
|
|
2.11.6 | Immediately following 2.11.3 | If Asset Meter details are valid, send acceptance notification. | SVAA | AMVLP or Supplier | P0305 - Confirmation of Asset Meter Registration | Self-Service Gateway |
2.11.7 | After 2.11.6 | Asset Meter registration is complete. | AMVLP or Supplier |
|
|
|
2.11.8 | After 2.11.7 | AMVLPs proceed to Section 2.1A to allocate AMSID Pair(s) to a Secondary BM Unit.
Suppliers proceed to Section 2.15 to include AMSID Pair(s) in an EMR AMSID Declaration. | AMVLP
or
Supplier |
|
|
|
2.12 BM Unit Allocation Baselining Detail
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.12.1 | By 23:59 on the Settlement Day before it becomes effective. | Send the Baselined MSID Pairs or AMSID Pairs
Send Inactive MSID Pairs
| Lead Party | SVAA | P0326 –BM Unit Allocation Baselining Detail | Self-Service Gateway or other method, as agreed. |
2.12.2 | Within 1 WD of 2.12.1
| If the BM Unit Allocation Baselining Detail was not submitted via the Self-Service Gateway, log Baselined or Inactive MSID Pairs or AMSID Pairs in the SVA Metering System and Asset Metering System Register. | SVAA |
|
| Internal Process |
2.12.3 | Immediately following successful receipt of Baselined MSID/AMSID Pair(s) or Inactive MSID Pair or AMSID Pair(s) into SVAA | Validate Baselined MSID Pairs or AMSID Pairs in accordance with Appendix 3.13 – Validation of Baselined MSID Pair or AMSID Pair files
Validate Inactive MSID Pairs or AMSID Pairs in accordance with Appendix 3.13 – Validation of Inactive MSID Pair or AMSID Pair files | SVAA |
| Appendix 3.13 – Baselined MSID Pair or AMSID Pair File Validation
Appendix 3.13 – Inactive MSID Pair or AMSID Pair File Validation |
|
2.12.4 | Immediately following 2.12.3
| If Baselined or Inactive MSID Pair or AMSID Pair is invalid, the SVAA shall send notification of the rejection to the Lead Party | SVAA | Lead Party | P0327 – Rejection of BM Unit Allocation Baselining Detail | Self-Service Gateway or other method, as agreed. |
2.12.5 | Immediately following 2.12.4
| If Baselined or Inactive MSID Pairs or AMSID Pairs is valid, update the Baselined or Inactive MSID Pairs or AMSID Pairs in the SVA Metering System & Asset Metering System Register. | SVAA |
|
| Internal Process |
2.12.6 | Immediately following 2.12.5 | Send confirmation of Baselined or Inactive MSID Pairs or AMSID Pairs. | SVAA | Lead Party | P0334 – Confirmation of BM Unit Allocation Baselining Detail | Self-Service Gateway or other method, as agreed. |
2.13 BM Unit Submitted Expected Volumes
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.13.1 | By 23:59 on the Settlement Day before it becomes effective. | Submit the MSID Pair or AMSID Pair Default Submitted Expected Volumes (relating to non-Baselined MSID Pairs and non-Baselined AMSID Pairs in a Baselined BM Unit). | Lead Party | SVAA
| P0328 BM Unit Submitted Expected Volume Notification | Electronic or other method, as agreed. |
2.13.2 | No later than Gate closure for a Settlement Period | Submit the MSID Pair or AMSID Pair Submitted Expected Volumes (relating to non-Baselined MSID Pairs and non-Baselined AMSID Pairs in a Baselined BM Unit). | Lead Party | SVAA
| P0328 BM Unit Submitted Expected Volume Notification | Electronic or other method, as agreed. |
2.13.3 | Within 1 WD of 2.13.2 or where appropriate within 1 WD of 2.13.1 | Log and validate Submitted Expected Volumes | SVAA |
|
| Internal Process |
2.13.4 | Within 1 WD of 2.13.2 or where appropriate within 1 WD of 2.13.1 | If MSID Pair or AMSID Pair Delivered Volume fails validation send rejection.
| SVAA | Lead Party | P0329 – BM Unit Submitted Expected Volume Rejection
| Electronic or other method, as agreed. |
2.13.5 | Within 1 WD of 2.13.2 or where appropriate within 1 WD of 2.13.1 | If MSID Pair or AMSID Pair Submitted Expected Volume passes validation send confirmation.
| SVAA | Lead Party | P0330 –BM Unit Submitted Expected Volume Acceptance
| Electronic or other method, as agreed. |
2.13.6 | By Calendar Day prior to Settlement Day | Submitted Expected Volumes revalidation of EFD
(Non-zero Submitted Expected Volumes for BMU with no MSID/AMSID Pair with status ‘S’) | SVAA | Lead Party | P0331 BM Unit Submitted Expected Volume Warning | Electronic or other method, as agreed. |
2.13.7 | As per SVAA Calendar (for each Volume Allocation Run) | If a Submitted Expected Volume or Default Submitted Expected Volume for MSID Pair or AMSID Pair is not registered before Gate Closure for a particular Settlement Period, set Settlement Expected Volume to NULL | SVAA |
|
| Internal process |
2.14 BM Unit Allocation Event Day
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.14.1 | Up to 30 calendar days before an Event Day | Send notification of Event days for MSID Pairs or AMSID Pairs
Event Days can be submitted before the event and submissions can be updated subsequently if required (up until 30 calendar days after the event) | Lead Party | SVAA
| P0323 BM Unit Allocation Event Day | Self-Service Gateway |
2.14.2 | Within 1 WD of 2.14.1 | Log and validate Event Day(s) or change to Event Day(s) | SVAA |
|
| Internal Process |
2.14.3 | Within 1 WD of 2.14.1 | If Event Day notification fails validation send rejection. Where SVAA has received an instruction to cancel an Event Day this will be notified via the rejection. | SVAA | Lead Party | P0324 Rejection of BM Unit Allocation Event Day | Self-Service Gateway |
2.14.4 | Within 1 WD of 2.14.1 | If Event day notification passes validation send confirmation. | SVAA | Lead Party | P0325 Confirmation of BM Unit Allocation Event Day | Self-Service Gateway |
2.14.5 | As required | Cancel Event Day(s)
Where an event day has been created in error. | SVAA |
|
| Internal Process |
2.15 Submission of EMR Declarations
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.15.1 | As required, and at least 10 WD prior to the required Effective From date | Submit EMR MSID Declaration
Or
Submit EMR AMSID Declaration | Supplier | SVAA
| EMR MSID Declaration
EMR AMSID Declaration | Self-Service Gateway37 |
or
Submit EMR CVA BM Unit Declaration |
CVA Registrant |
CRA |
EMR CVA BM Unit Declaration | Self-Service Gateway35 | ||
2.15.2 | Immediately following 2.15.1 | Register submitted details. | SVAA or CRA |
|
| Internal Process |
2.15.3 | Within 4WD of 2.15.2 | Validate the EMR Declaration. | SVAA or CRA |
|
| Internal Process |
2.15.4 | Immediately following 2.15.3 | Notify Supplier or CVA Registrant of the outcome of the validation of the EMR Declaration | SVAA or CRA | Supplier or CVA Registrant |
| |
2.15.5 | Following 2.15.4, and at least 4 WD prior to the required Effective From date, if Declaration was invalid, | Provide updated details and go to 2.15.3. | Supplier or CVA Registrant |
|
| Self-Service Gateway35 |
2.15.6 | Following 2.15.4, if Declaration was valid | End |
|
|
|
|
2.16 Voluntary withdrawal of an EMR Declaration
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.16.1 | Where a Supplier or CVA Registrant becomes aware that the EMR Declaration will become invalid | End date EMR MSID Declaration
or
End date EMR AMSID Declaration | Supplier | SVAA
| Effective To Date for the Declaration38. | Self-Service Gateway35 |
or
End date EMR CVA BM Unit Declaration |
CVA Registrant |
CRA |
Effective To Date for the Declaration36 | Self-Service Gateway35 | ||
2.16.2 | Immediately following 2.16.1 | Validate the Declaration | SVAA or CRA |
|
| Internal Process |
2.16.3 | Immediately following 2.16.2 | If the Effective To Date is valid, store the Effective To Date and confirm acceptance to the Supplier or CVA Registrant | SVAA or CRA | Supplier or CVA Registrant | Confirmation acceptance | |
2.16.4 | Immediately following 2.16.3 | End process |
|
|
|
|
2.17 Enforced withdrawal of an EMR Declaration
REF | WHEN | ACTION | FROM | TO | INFORMATION REQUIRED | METHOD |
2.17.1 | Where the SVAA identifies39 - or is instructed by the BSC Panel (via BSCCo) - that an EMR Declaration is no longer valid. | The SVAA or CRA shall terminate the EMR Declaration by adding the Effective To Date specified by BSCCo.
Note that the Effective To Date could be retrospective and could be set to the Effective From Date to nullify an EMR Declaration. | SVAA
or
CRA |
| Effective To date | Internal SVAA process |
2.17.2 | Within 1WD of 2.6.1 | Notify the Supplier or CVA Registrant of the action taken. | SVAA
or
CRA | Supplier
Or CVA Registrant | The SVAA must provide a short explanation for the action taken | |
2.17.3 | Following 2.6.2 | End process |
|
|
|
|
3 Appendices
3.1 Validation of MSID Pair and AMSID Pair Allocation File
Physical integrity; and
That the data file contains all mandatory data items in the required formats in accordance with the SVA Data Catalogue
it is from a valid Lead Party (i.e. a qualified Supplier or VLP), an AMVLP or the NETSO
the BM Unit to be allocated is a valid BM Unit40
the Lead Party sending the notification is the Lead Party of the specified BM Unit to have a MSID Pair allocated
a MSID may not be allocated to more than one MSID Pair at any given time
each MSID within the MSID Pair is located within the same GSP group associated with the BM Unit39 to which they are to be allocated to; and
the EFSD of the MSID Pair Allocation is at least 5 working Days ahead of the date of receipt of the MSID Pair *
it is submitted by a valid AMVLP
the BM Unit specified is a valid Secondary BM Unit
an AMSID may not be allocated to more than one AMSID Pair at any given time
the AMSID Pair is in the same GSP Group as the Secondary BM Unit3939 to which it is to be allocated
the Associated MSID Pair(s) has already been associated to that Secondary BM Unit
the combination of MSID Pair Indicator and AMSID Pair Differencing Indicator is allowed (see Section 3.9)
deallocate it from the first AMVLP’s Secondary BM Unit identify whether the AMSID Pair is already included in another Secondary BM Unit; and, if it is
whether the AMSID Pair is being used for the same purpose (i.e. for Asset Differencing or Asset Metering) in the other Secondary BM Unit:
an allowed combination of MSID Pair Indicator and AMSID Pair Differencing Indicator would result in a loss of AMSID Pair (see Section 3.10)
each MSID is registered in the ECOES Database;
each MSID is a HH Metering System;
each MSID notified by a Lead Party is allocated to a Secondary BM Unit;
each MSID IS not disconnected; and
the GSP Group for each MSID has been recorded correctly.
each AMSID is an Asset Metering System;
each AMSID Pair relates to an Asset which has successfully completed the three stage Registration process.
3.2 Amendments to MSID Pair Allocation or an AMSID Pair Allocation
3.3 Disputed MSID Pair or AMSID Pair Allocation Resolution
A Losing Lead Party or Losing AMVLP may initiate the Disputed MSID Pair Allocation Resolution Process by sending the P0286 or P0312 to the Gaining Lead Party or Gaining AMVLP.
The Gaining Lead Party or Gaining AMVLP shall use reasonable endeavours to respond to the Losing Lead Party or Losing AMVLP within 5 Working Days of receipt of the P0286or P0312.
The Gaining Lead Party or AMVLP agrees that the MSID Pair or AMSID Pair is to be allocated to the Losing Lead Party or Losing AMVLP.
After appropriate investigation e.g. checking a valid contract is in place, the Gaining Lead Party or Gaining AMVLP disagrees with the Losing Lead Party or Losing AMVLP.
The Gaining Lead Party or Gaining AMVLP shall update the SVA Metering System & Asset Metering System Register with a revised MSID Pair Allocation or AMSID Pair Allocation populated appropriately.
The Losing Lead Party or Losing AMVLP shall send a new MSID Pair Allocation or AMSID Pair Allocation populated appropriately.
The Gaining Lead Party or Gaining AMVLP shall send the Losing Lead Party or Losing AMVLP the P0286 or P0312 indicating the Gaining Lead Party or Gaining AMVLP disagrees with the Losing Lead Party or Losing AMVLP
The Losing Lead Party or Losing AMVLP can restart process should they remain in the belief that the rejection is erroneous (please return to step 1)
They shall telephone the Customer to discuss the transfer and the reason for rejection,
They shall come to a conclusion with the Customer as to whether the transfer request is valid or invalid.
If valid, they shall amend the EFSD as requested and continue as per current process
If invalid, they will follow the current process in sending the rejection flow along with comments ‘validly rejected 3 times as agreed’.
If a further transfer request is received, the request will be escalated to a Gaining Lead Party team manager who will endeavour to reach a resolution with the Customer.
3.4 MSID Pair Delivered Volume or AMSID Pair Delivered Volume Notification
Sufficient information to demonstrate how the MSID Pair Delivered Volumes or ABS MSID Pair Delivered Volumes for any MSID Pair and the AMSID Pair Delivered Volumes for any AMSID Pair were derived.
It shall be possible for the VLP, AMVLP or the NETSO to re-run any individual determination of Delivered Volumes to recreate the results exactly as originally calculated, as a historical report. This shall include the facility to exclude later versions of business data which were received after the process was originally run.
Should any Delivered Volume process or other report process generate informational, warning or error logs as part of its processing, these logs should be available for inspection.
3.5 Validation of MSID Pair Delivered Volume or AMSID Pair Delivered Volume Files
Physical integrity
That the data file contains all mandatory data items in the required formats in accordance with the SVA Data Catalogue
it is from a valid Lead Party (i.e. a qualified Supplier, VLP or AMVLP) or the NETSO
the BM Unit specified is a valid BM Unit39
the sender of the notification is the Lead Party of the specified BM Unit for the relevant MSID Pair or AMSID Pair, or the NETSO
the MSID Pair Delivered Volume, AMSID Pair Delivered Volume or ABS MSID Pair Delivered Volume is for a valid MSID Pair or AMSID Pair stored in the SVA Metering System Register.
3.6 Allocation of MSID Pair Delivered Volumes, AMSID Pair Delivered Volumes and ABS MSID Pair Delivered Volumes
For each MSID Pair, start by allocating the MSID Pair Delivered Volume39 to the Export MSID for a positive value (or to the Import MSID for a negative value), subject to the constraint that the magnitude of the MSID Pair Delivered Volume that can be allocated is capped by the magnitude of the half hourly metered data.
Allocate any remaining MSID Pair Delivered Volume39 to the other MSID in the MSID Pair (i.e. the Import MSID for a positive value, or the Export MSID for a negative value).
In the special case of an MSID Pair that does not include an Export MSID this process, all of the MSID Pair Delivered Volume will be allocated to the Import MSID.
If a MSID Pair Delivered Volume cannot be allocated in full to the component MSIDs using this process, the SVAA System will report an exception.
The SVAA operator will then report this exception to BSCCo and the VLP or the NETSO, as an exception indicates that the MSID Delivered Volume is inconsistent with the Settlement MSID metered data (suggesting that the MSID Delivered Volume has been reported incorrectly).
If the review by the VLP or the NETSO identifies that the exception was caused by the MSID Pair Delivered Volume being incorrect, the Virtual Lead Party or the NETSO will submit a corrected MSID Delivered Volume to the SVAA.
For AMSID Pair Delivered Volumes, SVAA will assign those delivered volumes to the Associated MSID Pairs and will apply losses to those Delivered Volumes to take account of any losses between the Asset Metering System and the Boundary Point.
Where there is more than one AMVLP using AMSID Pairs and the same MSID Pair, MSID Pair Delivered Volumes will be assigned to each AMVLP based on their contribution to the MSID Pair Delivered Volume.
3.7 SVA Non-Final Demand Facilities
3.7.1 Submission and validation of SVA Non-Final Demand Facility Declarations
The Facility Operator can submit Declaration details using an on-line form via the BSC Website for the Supplier to complete via Self Service Gateway
The Supplier can submit Declaration details on behalf of Facility Operator using Self Service Gateway.
Facility Operators via their Suppliers can submit a Declaration Form (F602/01) paper form via e-mail
Part A - provide details about the Supplier and the Authorised Person submitting the entire Declaration Document to the SVAA on behalf of the SVA Non-Final Demand Facility Operator – the Supplier is responsible for filling out Part A but is responsible for submitting the entire Declaration Document, comprising Part A-D;
Part B – is a declaration letter containing a standard text with elements in square brackets which must be filled in or deleted as appropriate by the SVA Facility Operator depending on the circumstances. The final letter must be signed by one of the SVA Non-Final Demand Facility Operator’s registered directors;
Part C and Part D – provide templates for providing necessary details about a SVA Facility, the SVA Non-Final Demand Facility Operator and the related Metering Systems.
Where the SVA Non-Final Demand Facility Operator wishes to provide details for more than one SVA Facility in a Declaration Document, it may complete multiple copies of Part C, i.e. for each SVA Non-Final Demand Facility being declared. No matter how many Part Cs are provided, please list all MSID details in Part D.
use existing Declaration ID
use a new Declaration Set ID42
use a new Declaration Set EFD43 - i.e. the date on which the Declaration changes take effect. The Declaration Set EFD(s) should be the same as the date added to the letter in Part B.
use an appropriate Declaration Type – the SVA Non-Final Demand Facility Operator must use a Declaration Type that best reflects the purpose of updating the Declaration(s), i.e. ‘CoS’ (change of supplier), ‘CoA’ (change of agent) or ‘CoM’ (change of Metering System details).
Where more than one type of update is being made for a SVA Non-Final Demand Facility, each update should be submitted using a distinct Declaration set and Declaration Type. The exception to this is where a CoA takes effect as a consequence of a CoS, in which case simply use the CoS Declaration Type and include details of the CoS and CoA in the Declaration.
Where multiple Declarations are submitted at the same time for the same Non-Final Demand Facility these should be submitted in chronological order of when updates take effect.
ensure the Total MSID Count must equal the number of all MSIDs at the Facility, on the date the Declaration takes effect, which are registered by the Supplier(s), taking account of any new or removed MSIDs.
The SVA Non-Final Demand Facility Operator must ensure Declaration Documents are submitted for all Suppliers and all Metering Systems related to the SVA Non-Final Demand Facility.
Where the SVA Non-Final Demand Facility Operator updates an existing declaration by adding or removing a Metering System then the updated Metering System’s MSID EFD or ETD will reflect when the MSID was added or removed and all other unchanged MSIDs EFD/ETDs will be relisted as they were originally declared. Please note that the Declaration Set EFD for all rows related to the Non-Final Demand Facility should be the same, even if other items in a row, e.g. MSID EFD, are not changing.
The SVA Non-Final Demand Facility Operator need only submit Declaration Documents for the Supplier(s) that is responsible for the Agent(s) that is changing.
use existing Declaration ID
use a new Declaration Set ID44
use a new Declaration Set EFD45 - i.e. the date on which the Declaration changes take effect. The Declaration Set EFD(s) should be the same as the date on the cover letter.
Set each MSID
ensure the Total MSID Count equals the number of all MSIDs at the Facility registered by the Supplier(s)
3.7.2 No Longer Used
3.7.3 F602/01 SVA Non-Final Demand Facility Declaration Document form – Supplier
SVA Non-Final Demand Facility Declaration Document – F602/01 Part B, C and D are completed by the SVA Non-Final Demand Facility Operator prior to being sent to the Supplier to complete Part A. Once all parts are completed the Supplier should send to the SVAA by email or where agreed the equivalent information by other electronic means | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Part A - Completed by Supplier – Category F or Category A Authorised Person
Market Participant Id (MPID)………………... Authorised Person’s Name ................................................ Company .............................................. Party ID………………………………………….Password…………………………………………….
Date………………………(Authorised in accordance with BSCP38) | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Part B - Completed by SVA Non-Final Demand Facility Operator (please replace square bracketed text with correct/relevant information)(please see BSCP602 3.7.1 for guidance) [Insert company name] [Insert company address]
[Insert current date]
Director’s declaration of SVA Non-Final Demand Facility(ies) FAO the SVAA, I [insert full name], being a director of [insert your company name] (company number [insert company number]), hereby declare that, having made all due and careful enquiries, the information contained in this declaration is true, complete and accurate in all material respects and is not misleading by reference to the facts and circumstances at the date of this declaration. Capitalised terms used in this declaration have the meaning given to them in the Balancing and Settlement Code unless stated otherwise. I declare that as of [insert Non-Final Demand Declaration Set effective from date] the SVA Non-Final Demand [Facility/Facilities] identified in the attachments to this letter [comply with the meaning/will cease to comply with the meaning/ceased to comply with the meaning] of an SVA Non-Final Demand Facility. In particular that each SVA Non-Final Demand Facility to which this declaration relates:
I declare that any material changes to the operation, configuration or measurement of electricity to or from any SVA Non-Final Demand Facility identified in the annex to this letter will be notified to you as soon as reasonably practicable. This director’s declaration is governed by and construed in accordance with English Law. Yours sincerely,
[Insert Director’s Signature] [Insert full name] For and on behalf of: [Insert company name]
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Part C - Completed by SVA Non-Final Demand Facility Operator (Please note that the following table has been populated for illustrative purposes. Please delete and replace entries as appropriate. Please see BSCP602 3.7.1 for guidance.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||
Part D – Completed by SVA Non-Final Demand Facility Operator (Please note that the following table has been populated for illustrative purposes. Please delete and replace entries as appropriate, working with your Supplier/s where necessary, e.g. to identify HHDA MPIDs and EFD. Please add more rows as necessary. Please see BSCP602 3.7.1 for guidance.
|
3.7.4 Non-Final Demand Facility Operator Withdrawal Letter template – F602/02
SVA Non-Final Demand Facility Operator Withdrawal Letter – F602/02 Completed by SVA Non-Final Demand Facility Operator and sent to SVA Agent by email or where agreed, by other electronic means (please replace square bracketed text with correct/relevant information). (Please see BSCP602 3.7.1 for guidance.) |
[Insert company name] [Insert company address]
[Insert current date]
SVA Non-Final Demand Facility Operator withdrawal FAO the SVAA, I [insert full name], being a director of [insert your company name] (company number [insert company number]), hereby declare that, having made all due and careful enquiries, the information contained in this declaration is true, complete and accurate in all material respects and is not misleading by reference to the facts and circumstances at the date of this declaration. Capitalised terms used in this declaration have the meaning given to them in the Balancing and Settlement Code unless stated otherwise. I declare that as of [insert date] [insert your company name] will [cease/have ceased] to be an SVA Non-Final Demand Facility Operator and that all SVA Non-Final Demand Facilities currently declared by [insert your company name] will cease to be SVA Non-Final Demand Facilities on the same date. This director’s declaration is governed by and construed in accordance with English Law. Yours sincerely, [Insert Director’s Signature] [Insert full name] For and on behalf of: [Insert company name] |
The structure of data file conforms to the specification in the IDD and / or the SVA Data Catalogue; and
all mandatory data items have been included
it is from a valid AMVLP
The Asset Meters are not already in use in another Asset Metering System
All Associated MSID Pairs have been registered
The Asset Meter Type exists in the list of CoP11 compliant Asset Meters
The HHDC is Qualified
The AMHHDC (where appointed) is Qualified
The MOA or AMMOA appointed is Qualified
Outstation Type is in list of valid Types
3.9 Definitions of Asset Metering and Asset Differencing
3.10 Valid combinations of ‘MSID Pair Indicator’ and ‘AMSID Pair Asset Differencing Indicator’ in a Secondary BM Unit
| MSID Pair Indicator | |||
“T” (No AMSIDs in Secondary BM Unit) | “A” (AMSIDs in Secondary BM Unit used for Asset Metering) | “D” (AMSIDs in Secondary BM Unit used for Differencing) | ||
AMSID Pair Asset Differencing Indicator | “T” (Apply Differencing) |
Not allowed |
Not allowed | AMSID Pair Delivered Volume(s) subtracted from MSID Pair Delivered Volume |
“F” (Do not apply Differencing) |
Not allowed | AMSID Pair Delivered Volume(s) used instead of MSID Pair Delivered Volume |
Not allowed | |
3.11 Shared use of MSID Pairs
3.12 Effect of Proposed AMSID Pair use in AMSID Pair Allocations
Ref | Proposed use of MSID Pair | Existing use of MSID Pair by another AMVLP | Outcome | Proposed Solution |
1 | MSID Pair Indicator = “T” | Another AMVLP has the MSID Pair allocated to their Secondary BM Unit with indicator of ‘T’ | Reallocation process triggered. | This is the MSID Pair reallocation process for Secondary BM Units without AMSID Pairs. |
2 | MSID Pair Indicator = “T” | Another AMVLP has the MSID Pair allocated to their Secondary BM Unit with indicator of ‘A’ or ‘D’ | Allocation is not allowed
| The parties involved must agree how to resolve the inconsistency. For example, If an existing AMVLP is using Asset Metering, the new AMVLP could use Differencing. |
3 | MSID Pair Indicator = “A” | Another AMVLP is already using the AMSID Pair, with ‘Apply Differencing’ Indicator of False | Automatic reallocation process triggered
| SVAA re-allocates the AMSID Pair to the gaining AMVLP. This is similar to #1 above, except that MSID Pair and AMSID Pair allocations will need to be end-dated for the losing AMVLP. |
4 | MSID Pair Indicator = “A” | Another AMVLP is already using the AMSID Pair, with ‘Apply Differencing’ Indicator of True | No reallocation process required | Both AMVLPs can use the same AMSID Pair. |
5 | MSID Pair Indicator = “A” | Another AMVLP is already using one of the Boundary Point MSID Pairs, with Indicator of ‘T’ | SVAA validation prevents the allocation.
| The AMVLPs involved must agree how to resolve the inconsistency. For example, the existing AMVLP could switch to Differencing (removing the new AMVLP’s Asset from their Secondary BM Unit). |
6 | MSID Pair Indicator = “A” | Another AMVLP is already using one of the Boundary Point MSID Pairs, with Indicator of ‘A’ | No reallocation process required | Both AMVLPs can use Asset Metering for their respective Assets. Note that they couldn’t use Asset Metering with the same AMSID Pair – that is covered by #3 above. |
7 | MSID Pair Indicator = “A” | Another AMVLP is already using one of the Boundary Point MSID Pairs, with Indicator of ‘D’ | No reallocation process required… | …provided the new AMVLP’s AMSID Pair is also in the existing AMVLP’s Secondary BM Unit (scenario #4 above). If it is not, SVAA will prevent the new AMVLP’s allocation. The AMVLPs involved must agree how to resolve the discrepancy e.g. by the existing AMVLP adding the new AMSID Pair into their Secondary BM Unit. |
8 | MSID Pair Indicator = “D” | Another AMVLP is already using the AMSID Pair, with ‘Apply Differencing’ Indicator of True | SVAA validation prevents the allocation | Differencing is sufficiently complex that the new AMVLP will be blocked until the old AMVLP has end-dated their allocations. |
9 | MSID Pair Indicator = “D” | Another AMVLP is already using the AMSID Pair, with ‘Apply Differencing’ Indicator of False | No reallocation process required | Both AMVLPs can use the AMSID Pair
|
10 | MSID Pair Indicator = “D” | Another AMVLP is already using one of the Boundary Point MSID Pairs, with Indicator of ‘T’ | SVAA validation prevents the allocation | The AMVLPs involved must agree how to resolve the inconsistency. |
11 | MSID Pair Indicator = “D” | Another AMVLP is already using one of the Boundary Point MSID Pairs, with Indicator of ‘A’ | No reallocation process required… | …provided the new AMVLP includes the AMSID Pair(s) that the existing Secondary BM Unit is using in their Secondary BM Unit. |
12 | MSID Pair Indicator = “D” | Another AMVLP is already using one of the Boundary Point MSID Pairs, with Indicator of ‘D’ | SVAA validation prevents the allocation
| The AMVLPs involved must agree how to resolve the inconsistency. For example, the existing AMVLP could end-date their allocation, or switch to Asset Metering |
3.13 Validation of Baselined or Inactive MSID Pair and AMSID Pair Files
Physical integrity; and
That the data file contains all mandatory data items in the required formats in accordance with the SVA Data Catalogue
it is from a valid Lead Party (i.e. a qualified Supplier or VLP)
the BM Unit to be allocated is a Baselined BM Unit
the Lead Party sending the notification is the Lead Party of the Baselined BM Unit
the Baselining Methodology selected by the Lead Party is one of the approved; and
the EFSD of the Baselined MSID Pair is at least 1 Working Day ahead of the date of receipt of the Baselined MSID Pair
it is submitted by a valid AMVLP
the BM Unit specified is a valid Baselined BM Unit
the Lead Party sending the notification is the Lead Party of the Baselined BM Unit
the Baselining Methodology selected by the Lead Party is one of the approved
the EFSD of the Baselined AMSID Pair is at least 1 Working Day ahead of the date of receipt of the Baselined MSID Pair
it is from a valid Lead Party (only a VLP)
the BM Unit to be allocated is a Secondary BM Unit
the Lead Party sending the notification is the Lead Party of the Secondary BM Unit; and
the EFSD of the Inactive MSID Pair is at least 1 Working Day ahead of the date of receipt of the MSID Pair
it is submitted by a valid AMVLP
the BM Unit specified is a valid Secondary BM Unit
the Associated MSID Pair(s) has already been associated to that Secondary BM Unit; and
the EFSD of the Inactive MSID Pair is at least 1 Working Day ahead of the date of receipt of the MSID Pair {{
3.14 EMR Declarations
3.14.1 Submission and validation of EMR Declarations
3.14.2 Validation of EMR Declarations:
3.14.3 Validation of EMR MSID Declarations:
Final Demand flag is “F”
The Import MSID is appointed to the Supplier that submitted the EMR MSID Declaration
Each MSID is:
Energised
Correctly Specified as Import or Export
Half Hourly
Generation Licence is valid
Generation Licensee is registered
3.14.4 Validation of EMR AMSID Declarations
Final Demand flag is “T”
Each MSID Pair is a valid MSID Pair recorded in the SVA Metering Systems and Asset Metering Systems Register
Each MSID is:
Energised
Correctly Specified as Import or Export
Half Hourly
Each Import MSID is appointed to the Supplier that submitted the EMR MSID Declaration
Each AMSID Pair is a valid MSID Pair recorded in the SVA Metering Systems and Asset Metering Systems Register
Generation Licence is valid
Generation Licensee is registered
3.14.5 Validation of EMR CVA BM Unit Declarations:
Final Demand flag is “F”
Each CVA BM Unit is:
registered in CMRS
Type T or E (but not Type I)
Registrant is a valid Role for the BM Unit Type
Generation Licence is valid
Generation Licensee is registered
3.14.6 Change of details for an existing EMR Declaration
3.14.7 Enforced Withdrawal of an EMR Declaration
Supplier is no longer appointed to
The Import MSID in an EMR MSID Declaration; or
Every Import MSID in an EMR AMSID Declaration
there is Final Demand present at a site represented by an EMR MSID Declaration or a CVA BM Unit Declaration;
the Generation and / or Storage at a site is not operated under a Generation Licence.
3.14.8 Director’s Declaration of Generation
Completed by the Generation Licensee (please replace square bracketed text with correct/relevant information) [Insert company name] [Insert company address]
[Insert current date] |
Director’s Declaration of Generation Licence I [insert full name], being a director of [insert your company name] (company number [insert company number]), hereby declare that, having made all due and careful enquiries, the information contained in this declaration is true, complete and accurate in all material respects and is not misleading by reference to the facts and circumstances at the date of this declaration. Capitalised terms used in this declaration have the meaning given to them in the Balancing and Settlement Code unless stated otherwise. I declare that as of [insert effective from date] the [Generation and/or Battery Storage plant identified in the attachments to this letter] comply with the requirements of the EMR Declaration Type to which this declaration relates:
I declare that any material changes to the operation, configuration or measurement of electricity to or from any Generation and/or Battery Storage plant identified in the annex to this letter will be notified to you as soon as reasonably practicable. This director’s declaration is governed by and construed in accordance with English Law. Yours sincerely,
[Insert Director’s Signature] [Insert full name] |
Generation and/or Battery Storage plant at site |
3.14.9 F602/04 EMR MSID Declaration form
EMR MSID Declaration – F602/04 Completed by Supplier – Category A or Category F Authorised Person Market Participant Id (MPID)………………... Authorised Person’s Name ................................................ Company .............................................. Party ID………………………………………….Password……………………………………………. Date………………………(Authorised in accordance with BSCP38) | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||
EMR AMSID Declaration – F602/05 Completed by Supplier – Category A or Category F Authorised Person Market Participant Id (MPID)………………... Authorised Person’s Name ................................................ Company .............................................. Party ID………………………………………….Password……………………………………………. Date………………………(Authorised in accordance with BSCP38) | ||||||||||||||||||||||||||||||||||||
|
EMR CVA BM Unit Declaration – F602/06 Completed by CVA registrant – Category A or Category F Authorised Person Market Participant Id (MPID) ………………....................... Only required for Suppliers Authorised Person’s Name ................................................ Company .............................................. Party ID………………………………………….Password……………………………………………. Date………………………(Authorised in accordance with BSCP38) | ||||||||||||||||||||||
| ||||||||||||||||||||||
2 Final Consumption Levy charges are calculated by the Electricity Market Reform Settlement Company
3 A VLP that has not also Qualified as an Asset Metering VLP may not register an Asset
4 Balancing Services in this instance refers to the Balancing Mechanism and Replacement Reserve
5 For the avoidance of doubt, the same SVA MSID may be included in an EMR MSID Declaration and in a SVA Non-Final Demand Declaration where it meets the criteria for both.
6 Balancing Services in this instance refers to the Balancing Mechanism and Replacement Reserve
7 Where such amendments correct an identified error that impacts Settlement accuracy, the SVAA shall facilitate such amendments for Settlement Days prior to having undergone the R1 VAR Run
8 Provided that the AMSID Pair is in the same GSP Group as the Secondary BM Unit
9 Where such amendments correct an identified error that impacts Settlement accuracy, the SVAA shall facilitate such amendments for Settlement Days prior to having undergone the R1 VAR Run
10 Note that does not result in a ‘Loss of AMSID Pair Allocation’ for the first AMVLP, as both AMVLPs are allowed to use the AMSID Pair
11 If a Supplier is also using the AMSID Pair in an EMR AMSID Declaration in accordance with Section 2.15, they would be eligible to become the Registrant of the relevant Asset. If the Supplier became the Registrant of the Asset, the 2nd AMVLP would be allowed to continue to use the AMSID Pair.
12 Balancing Services in this instance refers to the Balancing Mechanism, Replacement Reserve
13 P375 will introduce new versions of the P0282, P0283, P0284 & P0285 that will include AMSID Pair Delivered Volumes or MSID Pair Delivered Volumes, as applicable.
14Upon receipt of revised Delivered Volume data
15 Upon receipt of revised ABS MSID Pair Delivered Volume data
16 Please see Appendix 3.7.1 for guidance.
17 Please note that where an SVA Facility Operator is declaring an SVA Non- Final DemandFacility for the first time, i.e. where the SVAA has no record of the person acting as an SVA Non- Final Demand Facility Operator, then the SVAA will create an ‘operator record’ as part of processing the declaration(s) for the SVA Non- Final Demand Facility. There is no dedicated ‘create operator record’ process.
18 That is, an SVA Non- Final Demand Facility may have more than one Metering System and each Metering System may be registered by a different Registrant. In such a scenario the SVAA should expect to receive a Declaration from each Supplier that is a Registrant of at least one of the Metering Systems at the SVA Non- Final Demand Facility. The SVAA determines whether they are expecting more than one declaration (i.e. a Declaration set) by reviewing the numbers of MSIDs declared in a Declaration and comparing it against the Total Number of MSIDs which is also identified in each Declaration.
19 The SVAA may not need to instruct the HHDA to report metered data for an MSID if that MSID is the subject of an existing Metering System Reporting Notification (D0354) for another BSC process.
20 The SVAA shall specify the Effective to Settlement Date (J1870) in the D0354 Metering System Reporting Notification.
21 Please see Appendix 3.7.1 for guidance.
22 The SVAA must not instruct the HHDA to cease reporting metered data for an MSID if that MSID is the subject of an existing Metering System Reporting Notification (D0354) for another BSC process.
23 The SVAA shall specify the Effective to Settlement Date (J1870) in the D0354 Metering System Reporting Notification.
24 Please see Appendix 3.7.1 for guidance.
25 The SVAA may identify that a Non-Final Demand Facility has become or will become invalid following a routine assurance check. Alternatively, following routine assurance checking by BSCCo, SVAA may be notified by BSCCo following a decision by BSC Panel that an SVA Non-Final Demand Facility is or should become invalid and have its Declaration withdrawn.
26 The SVAA must not instruct the HHDA to cease reporting metered data for an MSID if that MSID is the subject of an existing Metering System Reporting Notification (D0354) for another BSC process.
27 The SVAA shall specify the Effective to Settlement Date (J1870) in the D0354 Metering System Reporting Notification.
28 Nb there is not an equivalent ‘create operator’ process as this is inherent within 2.4, i.e. the SVAA will create an operator role if none exists. Please see Appendix 3.7.1 for guidance.
29 Please see Appendix 3.7.1 for guidance
30 That is, an SVA Non-Final Demand Facility may have more than one Metering System and each Metering System may be registered by a different Registrant. In such a scenario the SVAA should expect to receive a Declaration from each Supplier that is a Registrant of at least one of the Metering Systems at the SVA Non-Final Demand Facility. The SVAA determines whether they are expecting more than one declaration (i.e. a set) by reviewing the numbers of MSIDs declared in a Declaration and comparing it against the Total Number of MSIDs which is also identified in each Declaration.
31 The SVAA must not instruct the HHDA to cease reporting metered data for an MSID if that MSID is the subject of an existing Metering System Reporting Notification (D0354) for another BSC process.
32 The SVAA shall specify the Effective to Settlement Date (J1870) in the D0354 Metering System Reporting Notification.
33 If an Asset has no Generation capacity, no Export Asset Metering System will be required, so only an Import AMSID will be generated for that Asset’s AMSID Pair.
34 A Qualified AMMOA may be appointed for certain Asset Meters instead of a Qualified MOA in accordance with CoP11.
35 A Qualified AMHHDC may be required to be appointed in addition to a Qualified HHDC for certain Asset Meters in accordance with CoP11 and BSCP601
36The three types of EMR Declaration are specified in Section 1.16.
37See section 3.14.1
38 Where a Supplier or CVA Registrant is not able to withdraw an EMR Declaration using the Self Service Gateway, e.g. if there is a systems outage, they may submit a Declaration including the Effective To Date. All other details in the emailed EMR Declaration must match the details in the Self Service Gateway exactly.
39 If a Supplier was de-appointed from an MSID, the D0385 from the HHDA in respect of that MSID would include details of the new Supplier and the D0385 would be rejected.
40 This validation is not applicable where the NETSO has submitted the MSID Pair
41 Or ABS MSID Pair Delivered Volumes, as appropriate
42 The Declaration Set ID and Declaration Set EFD should be refreshed whenever updating, withdrawing or re-declaring a Non-Final Demand Facility. For example, if on 1 January an SVA Non-Final Demand Facility Operator declares a Facility for the first time then the Declaration Set ID and Declaration Set EFD should be the same in each Declaration Document submitted on 1 January for the Facility; once declared, should the SVA Non-Final Demand Facility Operator wish to update the declaration details on 28 February then the Declaration Document(s) submitted must consistently use a new Declaration Set ID and Declaration Set EFD.
43 See footnote 34.
44 See footnote 34.
45 See footnote 34.
46 The Supplier or CVA Registrant is not required to submit this form to the SVAA, but they should retain it as supporting evidence for the EMR Declaration, if subject to a BSC Audit or TAPAP check.