Advanced Search

BSCP507: Supplier Volume Allocation Standing Data Changes

v 20.0
Download Forms
Download

Balancing and Settlement Code

BSC PROCEDURE

Supplier Volume Allocation Standing Data Changes

BSCP507

Version 20.0

Date: 02 November 2023

BSC Procedure 507 relating to Supplier Volume Allocation Standing Data Changes

1. Reference is made to the Balancing and Settlement Code (the Code) for the Electricity Industry in Great Britain and, in particular, to the definition of "BSC Procedure".

2. This is BSC Procedure 507, Version 20.0 relating to Supplier Volume Allocation Standing Data Changes.

3. This BSC Procedure is effective from 02 November 2023

4. This BSC Procedure has been approved by the Panel.

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.

AMENDMENT RECORD

Version

Date

Description of Changes

CRs Included

Mods Panel Ref

1.0

Code Effective Date

Re-badging version.

2.0

Code Effective Date

Approved for use by the Panel.

3.0

02/07/02

Changes relating to the reduction in Gate Closure time period embodied for P12.

AR1220

SVG/17/204

4.0

03/02/03

SVA Documentation Batch Release.

CPs 518, 668, 680, 786

SVG/22/275

5.0

24/06/03

Changes for the CVA Programme June 03 Release.

CP695

7.01

01/08/03

Updated for Modification P62.

P62

SVG/29/390

8.0

30/06/2004

Change proposal for the CVA Programme June 04 release

CP971

SVG/40/004

9.0

03/11/2004

Change Proposal for the CVA Programme Nov 04 release

CP1032

TDC/58/03

10.0

23/02/2005

SVA February 2005 Release and BETTA 6.3

P159, CP942, CP1091 and BETTA 6.3

SVG/47/004

11.0

23/02/2005

SVA February 2006 Release

CP1093, CP1130

SVG/51/003

SVG/53/002

12.0

22/02/2007

February 2007 Release

CP1156, CP1176

SVG/62/03

SVG67/17

ISG68/02

13.0

23/08/2007

P197 Release

P197

P/115/04

14.0

05/11/09

November 2009 Release

CP1278 v 2.0

ISG100/01

SVG100/02

15.0

05/11/15

November 2015 Release

P300

P228/06

16.0

28/02/19

February 2019 Release

P344

P284C/01

February 2019 Release

CP1510

ISG211/06

SVG214/02

17.0

01/04/20

April 2020 Standalone Release

P354, P388

SVG229/07

18.0

30/06/22

June 2022 Standard Release

P375

P309/06

19.0

23/02/2023

February 2023 Standard Release

P376

P314/06

20.0

13/07/2023

November 2023 Standard Release

P395

P340/05

1.1 Scope and Purpose of the Procedure

The purpose of this procedure is to ensure maintenance of an accurate, up-to-date set of Supplier Volume Allocation standing data. The standing data is used by the Supplier Volume Allocation Agent (SVAA) to ensure the correct working of its internal processing and, where appropriate, by the Central Registration Agent (CRA) for use in maintaining a list of BSC Agent details. The procedure covers the management and control of all changes made to the standing data in the Supplier Volume Allocation, System with the exceptions of:

SVA Metering System data registered in SMRS; and

Market Domain Data (MDD) which is handled exclusively in BSCP509 (Changes to Market Domain Data)2; and

Data Aggregator standing data changes which are required to be implemented for a Settlement Date only to enable a Supplier Volume Allocation Run to be completed. These changes are processed by the SVAA as contractual obligations and raised as problems with the BSC Service Desk.

Changes can be as the result of a request to add, change or delete individual standing data items.

1.2 Main Users of Procedure and their Responsibilities

The main users of this procedure are:

Suppliers, via their relevant authorised signatory or alternatively their nominated Non Half Hourly (NHH) Balancing Mechanism (BM) Unit representative, to raise / confirm Supplier / Supplier Agent and NHH BM Unit changes.

    • Virtual Lead Parties (VLP) and Asset Metering VLPs (AMVLP), via their relevant Authorised Signatory to raise / confirm VLP / AMVLP / Asset Metering Agent and Secondary BM Unit changes.

    • Suppliers, VLPs and AMVLPs, as Lead Parties of Baselined BM Units, via their relevant authorised signatory, to submit BM Unit Allocation Baselining Detail and BM Unit Allocation Event Day changes.

• The Balancing and Settlement Code Company (BSCCo) who authorises Supplier / Supplier Agent related changes.

• The SVAA who notifies the CRA of changes to the SVAA contact details.

• The SVAA who processes any changes to the Supplier / Supplier Agent / VLP / AMVLP / Asset Metering Agent standing data and notifies the relevant Supplier, VLP or AMVLP of such changes via a monthly report;

• The SVAA who processes any change to the NHH BM Unit Supplier Volume Allocation standing data. Prior to providing any NHH BM Unit data to the SVAA, Suppliers are required to ensure that their relevant authorised signatory or nominated NHH BM Unit representative has been registered as a relevant Authorised Person in accordance with BSCP38;

    • The SVAA who receives MSID Pair Allocation Notifications from VLPs, AMVLPs or the NETSO, and AMSID Pair Allocation Notifications from AMVLPs3, and who obtains the relevant:

    • MSID Standing Data which comprises details of the Grid Supply Point Group, HHDA, Supplier, Line Loss Factor Class and Consumption Component Class Id for each SVA Metering System;

    • AMSID Standing Data which comprises details of the Grid Supply Point Group, HHDC, AMHHDC, MOA, AMMOA, Line Loss Factor Class and Consumption Component Class Id for each Asset Metering System registered with the SVAA; and

    • The SVAA, who receives BM Unit Allocation Baselining Detail and BM Unit Allocation Event Day data from the Lead Parties of Baselined BM Units.

1.3 Use of the Procedure

The key milestones for changes to standing data are established as follows:

    • Following a Supplier’s initial entry into the market, Supplier and Supplier Agent related standing data must be provided no later than five Working Days (WD) after the first Supply Start Date (SSD) for the Supplier appointment in the GSP Group.

    • Following the initial registration of standing data, subsequent updates must be confirmed by the Supplier no later than ten WD following receipt of a monthly report of Standing Data changes from SVAA.

    • Following the initial registration of SVA Metering Systems in MSID Pairs, subsequent ad hoc notification of new or amended SVA Metering Systems or MSID Pairs by the VLP, [H/K] AMVLP or the NETSO.

    • Following the initial registration of Assets and related Asset Metering Systems, subsequent ad hoc notification of new or amended Assets and Asset Metering Systems by the AMVLP4,5 or Supplier.

The Supplier must ensure that Non Half Hourly Balancing Mechanism (BM) Unit changes are received by the SVAA no later than Gate Closure for the period to which the BM Unit applies. BM Unit changes provided after this timescale will not be processed by the SVAA.

The VLP, AMVLP and the NETSO must ensure that it notifies the SVAA of a new or amended MSID Pair no later than 5 WD before the Effective From Settlement Date that the MSID Pair allocation is to be valid.

An AMVLP must ensure that it notifies the SVAA of a new Asset and Asset Metering System(s) no later than 5 WD before the Effective From Settlement Date for the allocation of the related AMSID Pair in a Secondary BM Unit. A Supplier must ensure that it notifies the SVAA of a new Asset and Asset Metering System(s) no later than 5 WD before the Effective From Settlement Date for the related EMR AMSID Declaration.

The Lead Party of a Baselined BM Units may only send notification of Event Days which are not more than 30 calendar days in the past.

The SVAA must ensure that any changes to their contact details must be provided to the CRA within 1 WD of those changes becoming effective.

The remaining sections in this document are:

• Section 2 - This section is no longer in use.

• Section 3 - Interface and Timetable Information: this section defines in detail the requirements of each business process.

• Section 4 - Appendices: this section contains relevant supporting information. In addition, Appendix 4.1.1 Data Flows contains references to the BSC SVA Data Catalogue.

1.4 Balancing and Settlement Code Provision

This BSC Procedure has been produced in accordance with the provisions of the Balancing and Settlement Code (the Code). In the event of an inconsistency between the provisions of this BSC Procedure and the Code, the provisions of the Code shall prevail.

1.5 Associated BSC Procedures

BSCP11

Trading Disputes

BSCP38

Authorisations

BSCP503

Half Hourly Data Aggregation

BSCP508

Supplier Volume Allocation Agent

BSCP509

Changes to Market Domain Data

BSCP515

Licensed Distribution

BSCP533

PARMS Data Provision, Reporting and Publication of Peer Comparison Data

BSCP537

Qualification Process for SVA Parties, SVA Party Agents, VLPs, AMVLPs, Asset Metering Agents and CVA MOAs

BSCP602

SVA Metering System & Asset Metering System Register

1.6 Acronyms and Definitions

1.6.1 Acronyms

The terms used in this BSC Procedure are defined as follows:

AFYC

Average Fraction of Yearly Consumption

AMSID

Asset Metering System Identifier

AMVLP

Asset Metering Virtual Lead Party

BCA

BSC Change Administrator

BM

Balancing Mechanism

BSC

Balancing and Settlement Code

BSCCo

Balancing and Settlement Code Company

BSCP

Balancing and Settlement Code Procedure

CRA

Central Registration Agent

EMR

Electricity Market Reform

GSP

Grid Supply Point

LDSO

Licensed Distribution System Operator

MDD

Market Domain Data

MSID

Metering System Identifier

NETSO

National Electricity Transmission System Operator

PARMS

Performance Assurance Reporting and Monitoring System

PC

Profile Class

Ref

Reference

SMRA

Supplier Meter Registration Agent

SMRS

Supplier Meter Registration Service

SSC

Standard Settlement Configuration

SSD

Supply Start Date

SSR

Supplier Settlement and Reconciliation

SVA

Supplier Volume Allocation

SVAA

Supplier Volume Allocation Agent

VLP

Virtual Lead Party

WD

Working Day

1.6.2 Definitions

Full definitions of the above acronyms are, where appropriate, included in the Balancing and Settlement Code.

Effective Date - The date from which the SVA Settlement standing data change will become effective.

Self-Service Gateway - An online portal, accessible through the BSC Website, that allows authorised users to provide and maintain registration data, including (but not limited to) the data defined in this BSCP.

All other terms are as defined in the Balancing and Settlement Code.

2. This Section is no longer in use.

3. Interface and Timetable Information

3.1 Supplier / Supplier Agent, VLP / AMVLP / Asset Metering Agent and NETSO Standing Data Changes

The following process shall be used upon initial market entry of a Supplier, VLP, AMVLP or NETSO and in cases where a Supplier, VLP, AMVLP or NETSO wishes to notify the SVAA of any subsequent updates. Other changes to Supplier/Supplier Agent standing data are managed through Section 3.4 of this BSCP507, ‘Approval of Automatic Standing Data Updates’.

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.1.1

a) Following initial market entry, no later than 5 WD after the SSD for a Supplier appointment.

b) Subsequent to initial market entry, as required by the Supplier.

Authorised signatory to send the BSCP507/01A Form to SVAA.

Supplier.

SVAA.

Details of Supplier / Supplier Agent appointments including the effective date of the relationship starting and (if applicable) ending for the GSP Group(s).

Complete Form BSCP507/01A, Part A.

Fax / Email.

c) Following initial market entry

d) Subsequent to initial market entry, as required by the VLP or NETSO.

Register MSID Pairs with the SVAA in accordance with BSCP602.

For VLPs and AMVLPs only, allocate MSID Pairs to Secondary BM Units.

VLP, AMVLP,

NETSO

SVAA

P0278

e) Following initial market entry

f) Subsequent to initial market entry, as required by the AMVLP.

Register Assets, Asset Metering Agents and Asset Meters with the SVAA in accordance with BSCP602.

Allocate AMSID Pairs to Secondary BM Units.

Include AMSID Pairs in an EMR AMSID Declaration

AMVLP6, Supplier

SVAA

P0297 - Asset Registration

P0300 - Asset Metering Agent Appointments

P0303 - Asset Meter Registration

P0306 - AMSID Pair Allocation to a Secondary BM Unit

EMR AMSID Declaration

Electronic or other method, as agreed.

Self-service Gateway

Self-service Gateway

3.1.2

Within 1 WD of 3.1.1.

Log details of the Form.

SVAA.

Complete Form BSCP507/01A, Part B.

Internal Process.

3.1.3

Within 1 WD of 3.1.2

Verify authorised signatory details.

SVAA.

Form BSCP507/01A, Part B

Relevant authorised signatories list

Internal Process

3.1.4

If required, within 1 WD of 3.1.3

Resolve any problems with the authorised signatory details.

If the authorised signatory details cannot be accepted, reject form and notify reasons for rejection.

SVAA.

SVAA.

BSCCo.

Supplier,

NETSO, VLP, or AMVLP.

Form BSCP507/01A, Part A

Relevant authorised signatories list

Notification of rejection, including reasons for rejection

As agreed.

3.1.5

Where there are any queries with the changes requested on the BSCP507/01A, Part A form, on same day as 3.1.2.

Liaise with the Supplier, NETSO, VLP or AMVLP to resolve any issues.

SVAA.

Supplier, NETSO, VLP or AMVLP.

Fax / Email

3.1.6

Within 1 WD of successful verification of both:

a) authorised signatory details; and

b) changes requested..

Implement changes requested in the SVAA System.

SVAA.

Complete Form BSCP507/01A, Part B.

Proceed in accordance with BSCP508.

Internal Process.

3.1.7

Within 1 WD of 3.1.6.

Send notification that change(s) incorporated in the SVAA System.

SVAA.

Supplier, NETSO, VLP or AMVLP.

Form BSCP507/01A.

Fax / Post / Email.

3.2 Non Half Hourly Balancing Mechanism Unit Standing Data Changes7

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.2.1

To be received by SVAA no later than Gate Closure for the Settlement Period to which BM Unit applies.

Send the NHH BM Unit Allocation / revised NHH BM Unit Allocation change proposal (following rejection of change proposal by SVAA).

Supplier.8

SVAA.

Form BSCP507/02.

P0185 NHH BM Unit Allocation.

Fax / email.

3.2.2

Following 3.2.1 and by Gate Closure for the Settlement Period to which BM Unit applies.

Log change proposal.

SVAA.

Confirmation to date and timestamp all change requests received up to and including Gate Closure on every day of the year.

Internal Process.

3.2.3

Within 1 WD of 3.2.2.

Load and validate change.

SVAA.

Check :

1. that Supplier is a valid Supplier in Market Domain Data.

2. That change is valid for the Supplier / GSP Group combination.

3. That new BM Unit allocation is not inconsistent with existing BM Unit allocation for same PC/SSC/GSP Group/Supplier combination.

4. That new BM Unit allocation for the PC/SSC/GSP Group combination is associated with AFYC data.

5. The date and timestamp indicated on the confirmation :

a) If date and timestamp after Gate Closure then BM Unit invalid for use for period indicated in change request. Proceed to 3.2.4

b) If date and timestamp prior to Gate Closure then BM Unit valid for use for period indicated in change request. Proceed to 3.2.5.

Internal Process.

3.2.4

Within 1 WD of 3.2.2.

If BM Unit Allocation invalid, send rejection of BM Unit Allocation.

Return to 3.2.1 if Supplier wishes to provide revised change proposal.

SVAA.

Supplier.

P0035 Invalid Data.

Fax / email.

3.2.5

Within 1 WD of 3.2.2.

If BM Unit Allocation valid send confirmation of acceptance of BM Unit Allocation.

SVAA.

Supplier.

Form BSCP507/02.

Proceed in accordance with BSCP508.

Fax / email.

If Supplier notices an error

3.2.6

Within 1 WD of identifying the error

Notify SVAA of error in BM Unit Allocation.

Supplier.

SVAA.

Details of suspected error.

Fax / email

3.2.7

On same day as 3.2.6

Notify BSCCo of detection of error by Supplier or SVAA.

SVAA

BSCCo

Details of suspected error.

Fax / email

3.2.8

Within 1 WD of 3.2.7

Decide whether the BM Unit Allocation should be modified for the Supplier.

BSCCo

Internal Process

3.2.9

On same day as 3.2.8

Inform SVAA of the decision.

BSCCo

SVAA

Details of change required.

Fax / email

3.2.10

Within 1 WD of 3.2.9

If instructed, modify the BM Unit Allocation for the Supplier.

SVAA

Internal Process

3.2.11

Once every week

Send BSCCo a summary of BM Unit Allocations covering the previous 5 days, listing those BM Unit Allocations entered correctly and those that required additional alteration.

SVAA

BSCCo

P0209 Summary of NHH BM Unit Allocation Standing Data Changes.

Email

3.3 SVAA Contact Detail Standing Data Changes

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.3.1

Within 1 WD of change(s) becoming effective.

Send SVAA contact detail change(s).

SVAA.

CRA.

P0194 Receive BSC Agent Details.

Manual Process / Self-Service Gateway.

3.3.2

Within 1 WD of 3.3.1.

Log and validate change proposal.

CRA.

Internal Process.

3.3.3

Within 1 WD of 3.3.2.

Send rejection of change(s).

CRA.

SVAA.

P0035 Invalid Data.

Manual Process.

3.3.4

Within 1 WD of 3.3.2.

Send confirmation of acceptance of change(s).

CRA.

SVAA.

P0195 Issue Registration Report.

Manual Process / Self-Service Gateway.

3.4 Approval of Automatic Supplier/Supplier Agent Standing Data Updates

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.4.1

Within 3 WD of any updates to relevant authorised signatories list

Issue relevant authorised signatories list.

BSCCo.

SVAA.

Relevant authorised signatories list

Email

3.4.2

By 3rd WD of each month

Issue report of all Standing Data changes made in the previous calendar month.

SVAA.

Supplier.

BSCCo.

P0219 Standing Data Changes for Supplier in a GSP group

P0220 Standing Data Changes for Supplier/ Data Aggregator in a GSP group

P0219 and P0220 Instructions for Suppliers

Form BSCP507/01B

Email

3.4.3

Within 10 WD of 3.4.2

Review P0219 and P0220 data.

Supplier.

As agreed.

3.4.4

Within 10 WD of 3.4.2

If the changes are not consistent with the Supplier’s view of the Appointment of the Data Aggregator, Supplier to correct the issue accordingly.

Supplier.

HHDA.

NHHDA.

The association marked Y in the Accept Action or Reject Action columns from the P0219 and/or P0220 flow(s)

As agreed.

3.4.5

Within 10 WD of 3.4.2

If the changes are consistent with the Supplier’s view of the Appointment of the Data Aggregator, accept or reject each change (providing alternative date ranges if necessary).

Supplier.

SVAA.

BSCCo.

P0219 Standing Data Changes for Supplier in a GSP group

P0220 Standing Data Changes for Supplier/ Data Aggregator in a GSP group

Form BSCP507/01B, Part A

For details on completing the forms see the Instruction Sheet which is provided with the P0219 and P0220 emails

Email/Fax

3.4.6

Within 1 WD of receipt of P0219 and P0220

Log P0219 and P0220 forms.

SVAA.

P0219 Standing Data Changes for Supplier in a GSP group

P0220 Standing Data Changes for Supplier/ Data Aggregator in a GSP group

Form BSCP507/01B

Email/Fax

3.4.7

Within 1 WD of 3.4.6

Verify authorised signatory details.

SVAA.

Form BSCP507/01B, Part B

Internal Process

3.4.8

Within 1 WD of 3.4.6

Resolve any problems with the authorised signatory details.

If the authorised signatory details cannot be accepted, reject form and inform Supplier of reasons for rejection.

SVAA.

SVAA.

BSCCo.

Supplier.

Form BSCP507/01B, Part A

Relevant authorised signatories list

Notification of rejection, including reasons for rejection

As agreed.

3.4.9

Within 1 WD of 3.4.6

Resolve any problems on P0219 and P0220 flows.

SVAA.

Supplier.

P0219 Standing Data Changes for Supplier in a GSP group

P0220 Standing Data Changes for Supplier/ Data Aggregator in a GSP group

As agreed.

3.4.10

Within 5 WD of 3.4.6

Implement changes in SVA System, based upon information provided by Suppliers in the P0219 and P0220 flows.

Confirm implementation.

SVAA.

Supplier.

P0219 Standing Data Changes for Supplier in a GSP group

P0220 Standing Data Changes for Supplier/ Data Aggregator in a GSP group

Form BSCP507/01B, Part C

Email/Fax

3.5 LDSO Standing Data Changes

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.5.1

Annually, by 40 Calendar Days before 1 April each year.

Send Standard Settlement Configuration and Time Pattern Regime combination to be used to report aggregated HH data for each relevant Line Loss Factor Class.

LDSO

SVAA

P0239 Mapping Data for HH Aggregated Metering Systems.

Electronic or other method as agreed.

3.5.2

Following 3.5.1.

Enter LDSOs mapping data and validate against the received data.

SVAA

P0239 Mapping Data for HH Aggregated Metering Systems.

Internal Process.

3.5.3

Following 3.5.2.

Notify relevant LDSO that its mapping data has been processed.

SVAA

LDSO

Electronic or other method as agreed.

3.6 MSID and AMSID Standing Data changes

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.6.1

At any time

Receive notification of a VLP or AMVLP and Secondary BM Units from the CRA

CRA

SVAA

P0181 Stage 2 BM Unit Registration9

Electronic or other method as agreed.

3.6.2

Following 3.6.1

Store data in the SVA Metering System and Asset Metering System Register

SVAA

P0181 Stage 2 BM Unit Registration99

P0297 Asset Registration

P0300 Asset Metering Agent Appointments

P0303 Asset Meter Registration

Internal Process

3.6.3

At any time

SVAA to receive and validate MSID Pair details from the VLP, AMVLP or the NETSO in accordance with BSCP602

VLP,

AMVLP, NETSO

SVAA

P0278 MSID Pair Allocation

  • Import Metering System (mandatory)

  • Export Metering System (optional)

Self Service Gateway or other method as agreed.

SVAA to receive and validate AMSID Pair details from an AMVLP5 or Supplier in accordance with BSCP602.

AMVLP5, Supplier

SVAA

P0306 AMSID Pair Allocation to a Secondary BM Unit

Self Service Gateway or other method as agreed.

3.6.4

Within 1 WD of 3.6.3

Procure and record MSID and AMSID Standing Data

SVAA

Internal Process

3.6.5

At any time

Receive notification of HHDA Metering System Reporting Rejection

HHDA

SVAA

D0356 - Metering System Reporting Rejection

3.6.6

Within 1 WD of 3.6.5

Re-procure and record MSID Standing Data

SVAA

3.6.7

Within 1 WD of 3.6.5

Where re-procurement of MSID Standing Data results in change of HHDA send reporting notification to new HHDA

SVAA

HHDA

D0354 – Metering System Reporting Notification9

Electronic or other method as agreed.

3.6.8

As late as possible (to ensure most recent data from HHDA) to meet SVAA’s Calendar.

SVAA identify missing MSID Metered Volumes expected from the HHDA

SVAA

Internal Process

3.6.8A

4 hours before the end of business hours on the SF SVA Notification Date in the SVA Settlement Calendar

and, where estimated data was submitted at SF, and no actual data has been submitted subsequently

4 hours before the end of business hours on the relevant Reconciliation VAR SVA Notification Date in the SVA Settlement Calendar

SVAA to identify missing AMSID Metered Volumes expected from the HHDC

SVAA

Internal Process

SVAA notifies HHDC & AMVLP or Supplier

SVAA

HHDC

AMVLP or Supplier

P0310 – Missing Metering System Data

Electronic or other method as agreed.

3.6.9

Within 1 WD of 3.6.8

Re-procure and record MSID Standing Data

SVAA

Internal Process

3.6.10

Within 1 WD of 3.6.8

Where re-procurement of MSID Standing Data results in change of HHDA send reporting notification to new HHDA

SVAA

HHDA

D0354 – Metering System Reporting Notification9

Electronic or other method as agreed.

3.6.11

Upon receipt of a D0385 Metering System Half Hourly Metered Volumes

Validate that the Supplier held within the D0385 matches the Supplier recorded in the SVA Metering System and Asset Metering System Register

SVAA

D0385 Metering System Half Hourly Metered Volumes

Internal Process

3.6.11A

Upon receipt of a D0268 Asset Metering System Half Hourly Metered Data

Validate that the HHDC issuing the D0268 matches the HHDC recorded in the SVA Metering System and Asset Metering System Register for each AMSID

SVAA

D0268 Asset Metering System Half Hourly Metered Data

3.6.12

Within 1 WD of 3.6.11

SVAA identify an inconsistency between Supplier held on D0385 and the SVA Metering System Register

SVAA

Internal Process

3.6.12A

Within 1 WD of 3.6.11A

SVAA identify an inconsistency between HHDC issuing a D0390 and the SVA Metering System and Asset Metering System Register

SVAA

Internal Process

3.6.13

Within 1 WD of 3.6.11

Re-procure and record MSID Standing Data

Internal Process

3.6.13A

Within 1 WD of 3.6.11A

Re-procure and record AMSID Standing Data

Internal Process

3.6.14

Within 1 WD of 3.6.8

Where re-procurement of MSID Standing Data results in change of HHDA send reporting notification to new HHDA

SVAA

HHDA

D0354 – Metering System Reporting Notification9

Electronic or other method as agreed.

3.7 Baselined BM Unit Standing Data changes

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.7.1

At any time

Receive notification of a Baselined BM Unit and validate it in accordance with BSCP60210.

Lead Party

SVAA

P0335 - BM Unit Baselining Status

Electronic or other method, as agreed.

3.7.2

Immediately following 3.7.1

Store valid Baselined BM Unit data in the SVA Metering System and Asset Metering System Register.

SVAA

Internal

3.7.3

At any time after 3.7.2

Receive notification of BM Unit Baselining Allocation Detail and validate it in accordance with BSCP602.

Lead Party

SVAA

Electronic or other method, as agreed.

3.7.4

Immediately following 3.7.3

Store valid BM Unit Baselining Allocation Detail data in the SVA Metering System and Asset Metering System Register.

SVAA

Internal

3.7.5

At any time after 3.7.2

Receive notification of BM Unit Baselining Event Day data and validate it in accordance with BSCP602.

Lead Party

SVAA

P0323 - BM Unit Baselining Event Day

Electronic or other method, as agreed.

3.7.6

Immediately following 3.7.5

Store valid BM Unit Baselining Event Day data in the SVA Metering System and Asset Metering System Register.

SVAA

Internal

4. Appendices

4.1 Supplier Volume Allocation Standing Data

The VLP, AMVLP and the NETSO will notify the SVAA of new or amended MSID Pair data and the AMVLP5 and Supplier will notify the SVAA of new or amended AMSID Pair data.

4.1.1 Data Flows

The following table contains a list of the data flows which may be changed over time using this BSC Procedure.

The ‘DC Flow Ref’ column provides the data flow references in the BSC SVA Data Catalogue. References that begin with a ‘P’ have an equivalent BSC SVA Data Catalogue data flow.

Data Flow

DC Flow Ref

From

To

Supplier in a GSP Group

P0030

Supplier

SVAA

Data Aggregator in a GSP Group

P0031

Supplier

SVAA

Data Collector in a GSP Group

P0032

Supplier, VLP, AMVLP

SVAA

Acknowledgement

P0024

SVAA

Supplier

Missing Data

P0310

SVAA

VLP,

AMVLP,

HHDA,

HHDC

Supplier

Invalid Data

P0035

SVAA

Supplier

NHH BM Unit Allocation

P0185

Supplier

SVAA

Receive BSC Agent Details

P0194

SVAA

CRA

Issue Registration Report

P0195

CRA

SVAA

Standing Data Changes for Supplier in a GSP group

P0219

SVAA

Supplier, BSCCo

Standing Data Changes for Supplier in a GSP group

P0219

Supplier

SVAA, BSCCo

Standing Data Changes for Supplier/ Data Aggregator in a GSP group

P0220

Supplier

SVAA, BSCCo

Standing Data Changes for Supplier/ Data Aggregator in a GSP group

P0220

SVAA

Supplier, BSCCo

4.1.2 Business Events triggering SVA Settlement Standing Data Changes

The following business events will trigger changes to Supplier Volume Allocation standing data:

4.1.3 Supplier starts or stops trading in a GSP Group

This is triggered, for example, by the Change of Supplier event. This triggers a change at the GSP Group for a given Supplier.

4.1.3A AMVLP or VLP starts or stops trading in a GSP Group

This is triggered, for example, by the Change of AMVLP event.

4.1.3.1 Data Aggregator starts or stops operating in a GSP Group

This may be triggered, for example, by the Change of Supplier event or by a Supplier appointing a new Data Aggregator or changing an existing Data Aggregator. This triggers a change for a Data Aggregator / Supplier relationship at a given GSP Group.

4.1.3.2 Data Collector starts or stops operating in a GSP Group

This may be triggered, for example, by the Change of Supplier event or a Change of AMVLP event or by a Supplier or AMVLP appointing a new Data Collector or changing an existing Data Collector. This triggers a change for a Data Collector / Supplier or a Data Collector / AMVLP relationship at a given GSP Group.

4.1.3.3 NHH BM Unit data in a GSP Group

This is triggered by a change to the Profile Class / Standard Settlement Configuration / GSP Group combinations allocated to a BM Unit by the Supplier.

4.1.3.4 SVAA Agent Contact details

The SVAA will notify the CRA of any change to its contact details including e.g. change of address, telephone, e-mail address.

complex image of process

Supplier Volume Allocation Agent System

Supplier / Supplier Agent Standing Data Change Form BSCP507/01B

Email or Fax

SVAA Use Only

Ref No

AUTHORISATION OF CHANGES REQUIRED PART A - SUPPLIER

FOR P0219 and P0220 FORMS

Supplier ID:

AUTHORISED SIGNATORY NAME: _______________________________

PARTY ID: _____________________________________________________

PASSWORD: ___________________________________________________

SIGNATURE: _________________________________________(only if sent via FAX)

DATE: ___________________________________________________________

VERIFICATION OF DETAILS PART B – SVAA

DATE RECEIVED _____________________

NAME AND PASSWORD/SIGNATURE VALID (Y/N) ____________________

CHANGE APPLIED PART C – SVAA

NAME

DATE

DATE CONFIRMATION SENT TO SUPPLIER

Supplier Volume Allocation Non Half Hourly Balancing Mechanism Unit Allocation Standing Data Change Form BSCP507/02

Supplier Volume Allocation Non Half Hourly Balancing Mechanism Unit Allocation Standing Data Change Form BSCP507/02

SVAA Use Only

Ref No

DETAILS OF CHANGES REQUIRED PART A - SUPPLIER

Supplier Id

GSP Group Id

A maximum of 30 entries per form. If more than 30 entries, then another form must be completed

Change Type

(Ad /

Am / De11)

BM Unit Id

(maximum of 11 characters)

Profile Class ID (maximum of 1 character)

SSC ID (maximum of 4 characters)

Effective From Settlement Date (NHH BM Unit Allocation)

Effective To Settlement Date (NHH BM Unit Allocation)

Change Type

(Ad /

Am / De11)

BM Unit Id

(maximum of 11 characters)

Profile Class ID (maximum of 1 character)

SSC ID (maximum of 4 characters)

Effective From Settlement Date (NHH BM Unit Allocation)

Effective To Settlement Date (NHH BM Unit Allocation)

NHH BM Unit Nominated Representative:

Signature:

Company:

Date and Time Submitted:

Date and Time Received: PART B – SVAA

Received by Gate Closure: Yes / No (select appropriate)

SVAA Representative: ___________________________________________________________

Signature: ___________________________________________________________

Validation Completed

Date and Time Entered into SVAA System: ___________________________________________________________

Validation Successful: Yes / No (select appropriate)

Supplier notified of Outcome of Validation: Yes / No (select appropriate)

Date Supplier Notified: ____________________________________________________________

SVAA Representative: ____________________________________________________________

Signature: _______________________________ PART C – ELEXON (Optional)

Correction to NHH BM Unit Authorised: Yes / No (select appropriate)

Description of Change Required: ___________________________________________________________

ELEXON Representative: ____________________________________________________________

Signature: ____________________________________________________________

Date: ____________________________________________________________

Date Notified to SVAA to Implement Correction: ____________________________________________________________

Date Authorisation Received from ELEXON: ______________________________________________ PART D – SVAA

Date and Time Entered into SVAA System: ____________________________________________________________

SVAA Representative: ____________________________________________________________

Signature: ___________________________________________________________

1 Version 6.0 was not issued due to an administrative error.

2 MDD also maintains information regarding the GSP Groups in which Licensed Distribution System Operators (LDSOs) and Supplier Meter Registration Agents (SMRAs) are operating.

3

4Note that SVAA will generate an AMSID Pair on the successful registration of an Asset and related Asset Metering System(s).

5VLPs that wish to register an Asset and its Asset Metering Systems and to allocate the related AMSID Pair to a Secondary BM Unit must complete the Asset Metering VLP Qualification process to become AMVLPs.

6 VLPs that wish to register an Asset and its Asset Metering Systems and to allocate the related AMSID Pair to a Secondary BM Unit must additionally complete the Asset Metering VLP Qualification process.

7 Suppliers should note the following:

  1. If an NHH BM Unit Allocation is only required to be effective for a particular Settlement Day, Form BSCP507/02 should be submitted with dates in both the Effective From and Effective To fields;

  2. Non Half Hourly consumption will be allocated to the Base BM Unit by default, without any need to submit additional allocations;

  3. Specifying an Effective To date will terminate an allocation to an additional BM Unit once the date has been reached.

8 The originator of the NHH BM Unit data must be authorised in accordance with BSCP38.

9 The SVA shall specify the Effective from Settlement Date (J1869) the Effective to Settlement Date (J1870) in the D0354 Metering System Reporting Notification

10 Note that the Lead Party may alternatively register the Baselined BM Unit with CRA in accordance with BSCP15, in which case the SVAA will be able to access the data through the shared Elexon Kinnect database.

11 Select one of the following change types: Ad – Addition, Am – Amendment, De - Deletion