BSC Digital Code logo
BSC Digital Code logo
  1. Home
  2. BSC & Codes
  3. BSC Digital Codes
Advanced Search
Previous version
Next version

CONTENTS

BSCP509: Changes to Market Domain Data

v 23.0
Effective From Date:
Status:LIVE
Download Forms
Download

BSC Procedure 509 relating to Changes to Market Domain Data

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

2. This is BSC Procedure 509 Version 23.0 relating to Changes to Market Domain Data.

3. This BSC Procedure is effective from 1 September 2021.

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

1. Introduction

1.1 Purpose and Scope of the Procedure

The purpose of this BSC Procedure (BSCP) is to ensure that all changes to Market Domain Data (MDD) within the Supplier Volume Allocation (SVA) arrangements are made in an auditable and controlled manner and where appropriate with due consultation with the affected parties. MDD refers to those items of data that are required to be passed from one party to another by the Supplier Volume Allocation Agent (SVAA).

This BSCP covers the raising of a change (an MDD Change Request ‘MDD CR’), authorisation and notification of MDD items to all relevant Market Participants (MPs) including the SVAA. The BSCP also covers the raising of a request to change an item of MDD whose values are linked to BSCCo developed software and the subsequent notification of such changes. However, in order to accommodate potential software changes, their authorisation must be carried out in accordance with BSCP40 “Change Management”. In addition, this BSCP outlines the process for effecting emergency changes to MDD.

A complete set of MDD entities together with their authorisation routes is contained in Appendix 4.1.

The BSCP does not cover the distribution and implementation of changes to MDD, or changes to SVA system standing data, which are covered by BSCPs 508, 'Supplier Volume Allocation Agent' and 507, 'Supplier Volume Allocation Standing Data Changes' respectively. Neither should it be used to implement changes to the structure of the MDD file. This file is included in the Baseline Management System (BMS), and is changed in accordance with BSCP40.

1.2 Main Users of the Procedure and their Responsibilities

The main users of this BSCP are:

    • Panel - approves changes to MDD

    • MPs – registered in accordance with BSCP38 for the purpose of interfacing with the BSCCo when managing changes to MDD1.

    • SVAA - receives notification of authorised changes to MDD from BSCCo and is involved in progressing changes to the SVAA calendar, preparing Impact Assessments (IAs), and agreeing release schedules.

1.3 Use of the Procedure

This BSCP must be used to progress all changes to those data items designated as MDD. The need to make changes to MDD may be identified by the Panel, one of its Panel Committees, relevant BSC Agents, or Parties, depending upon the nature of the change. Appendix 4.1 outlines who can raise an MDD CR and provides a list of MDD Entities. In order to progress an MDD CR, the originator is required to complete the MDD CR (using F509/01) with the aid of the scenarios set out in BSCP509 Appendix 2: MDD Change Request Entity Validation2 together with the valid section from the MDD Entity Form. Appendix 4.4 outlines the MDD Entity forms used by this BSCP.

There are two key milestones in this BSCP:

    • The SVAA is to be notified by BSCCo of a change to MDD no later than 7 Working Days (or as otherwise agreed between BSCCo and the SVAA) before the Go Live Date.

    • MPs have 2 Working Days from the receipt of the MDD to contact BSCCo if they believe that the change to MDD as notified is not as agreed or invalid. If BSCCo determines that the MDD publish is not as agreed it will assess the severity of the impact of any error. BSCCo will then determine whether any relevant error should be removed in the next publish of MDD or whether the emergency fix process should be used (see Section 3.5).

1.4 Balancing and Settlement Code Provision

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

1.5 Associated BSC Procedures

BSCP01

Overview of Trading Arrangements

BSCP15

BM Unit Registration

BSCP25

Registration of Transmission System Boundary Points, Grid Supply Points, GSP Groups and Distribution Systems Connection Points

BSCP38

Authorisations

BSCP40

Change Management

BSCP65

Registration of Parties and Exit Procedures

BSCP507

Supplier Volume Allocation Standing Data Changes

BSCP508

Supplier Volume Allocation

BSCP520

Unmetered Supplies Registered in SMRS

BSCP537

Qualification Processes for SVA Parties, SVA Party Agents and CVA MOAs

1.6 Acronyms and Definitions

1.6.1 Acronyms

The terms used in this BSCP are defined as follows:

AFYC

Average Fraction of Yearly Consumption

BM

Balancing Mechanism

BMS

Baseline Management System

BSCCo

Balancing and Settlement Code Company

BSCP

Balancing and Settlement Code Procedure

CD

Compact Disc

CDCA

Central Data Collection Agent

CPC

Change Proposal Circular

CRA

Central Registration Agent

EAC

Estimated Annual Consumption

FAA

Funds Administration Agent

GAD

Group Average Demand

GSP

Grid Supply Point

IA(s)

Impact Assessment(s)

ID

Identifier

LDSO

Licensed Distribution System Operator3

LLFC

Line Loss Factor Class

MDD

Market Domain Data

MDD CR

Market Domain Data Change Request

MP(s)

Market Participant(s)

MPID

Market Participant Identifier

MPR

Market Participant Register

MTC

Meter Timeswitch Class

PAB

Performance Assurance Board

PC

Profile Class

PEG

Profiling Expert Group

PrA

Profile Administrator

RECCo

Retail Energy Code Company

SAA

Settlement Administration Agent

SD

Settlement Day

SMETS

Smart Metering Equipment Specifications

SMRA

Supplier Meter Registration Agent

SSC

Standard Settlement Configuration

SVA

Supplier Volume Allocation

SVA MOA

Supplier Volume Allocation Meter Operator Agent

SVAA

Supplier Volume Allocation Agent

TPR

Time Pattern Regime

UMS

Unmetered Supplies

1.6.2 Definitions

MDD Circular - general information circulated by BSCCo relating to various MDD processes.

MDD Publish - refers to the distribution of all MDD flows by the SVAA to MPs. SVAA updates MDD with all the approved MDD CRs and sends the updated files to all MDD MPs in accordance with BSCP508.

Go Live Date - the last date after the Publication Date by which the new version of MDD should be implemented.

Originator - authorised source for proposing changes to MDD.

MP - an organisation who interfaces directly with BSCCo for the purpose of managing changes to MDD.

PEG4 - Appointed by the Panel for the purpose of reviewing the draft technical deliverables submitted by the PrA (Profile Administrator).

Publication Date - the date on which all data flows are sent by the SVAA to MPs.

All other terms are as defined in the Code.

2. Not Used

3. Interface and Timetable Information

3.1 Changes to Market Domain Data Provided by the Profile Administrator

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.1.1

As required within the terms of the contract.

Send GADs.

PrA

BSCCo.

GADs.

Email.

3.1.2

Within 5 WD of 3.1.1

Send GADs.

BSCCo.

PEG.

GADs; latest population data for each GSP and Profile Class.

Email.

3.1.3

Within 15 WD 3.1.2

Consider the GADs, associated information and any additional relevant data in accordance with the PEG Terms of Reference; make recommendations for submission to the Panel.

PEG.

BSCCo.

Recommendations on the suitability of Profile Class data.

Email.

3.1.4

In accordance with the deadlines associated with the meeting in 3.1.5.

Submit PEG recommendations to the Panel for approval.

BSCCo.

Panel.

PEG recommendations.

Internal Process.

3.1.5

At next Panel meeting

Consider the PEG recommendations and notify BSCCo of decisions made.

Panel.

BSCCo.

Panel decisions on PEG recommendations.

By Committee.

3.1.6

Within 1 WD

Notify relevant parties of Panel decisions regarding the PEG recommendations.

BSCCo.

PEG, PrA.

Panel decisions, details of any associated actions and timescales.

Email.

3.1.75

As required within the terms of the contract.

Send draft technical deliverables.

PrA.

BSCCo.

Draft technical deliverables and any supporting information (see Appendix 4.1 for valid MDD entities).

CD/Email.

3.1.8

Within 1 WD of 3.1.7.

Send draft technical deliverables for review.

BSCCo.

PEG.

Draft technical deliverables and any supporting information.

Email.

3.1.9

Within 15 WD of 3.1.8.

Provide comments on draft technical deliverables.

PEG.

BSCCo.

Comments.

Email.

3.1.10

Within 3 WD of 3.1.9.

Consolidate comments and return to PrA.

BSCCo.

PrA.

Consolidated comments.

Email.

3.1.11

By 10 WD before contract acceptance date.

Send updated draft technical deliverables.

PrA.

BSCCo.

Updated draft technical deliverables and any supporting information (see Appendix 4.1 for valid MDD entities).

CD/Email.

3.1.12

Within 1 WD of 3.1.11.

Raise and log MDD CR.

BSCCo.

F509/016 Part A in Appendix 4.2

Updated draft technical deliverables and any supporting information.

Internal process.

3.1.13

On same WD as 3.1.12.

Send MDD CR and updated draft technical deliverables to MPs for IA.

BSCCo.

MPs.

F509/01 Part A in Appendix 4.2

Updated draft technical deliverables and any supporting information.

Email/ Fax.

3.1.14

Within 5 WD of 3.1.13 and if MPs have comments.

Return IA and comments.

MPs.

BSCCo.

Comments and IA.

Email/ Fax.

3.1.15

Within 1 WD of 3.1.14.

Consolidate IA comments and submit MDD CR to Panel for approval.

BSCCo.

Panel.

Updated draft technical deliverables with supporting information, including consolidated comments and IA from MPs.

Internal process.

3.1.16

At next Panel meeting.

Consider MDD CR, IA and consolidated comments and approve or reject MDD CR.

Panel.

MDD CR IA, consolidated comments and proposed draft technical deliverables with supporting information.

By Committee.

3.1.17

Within 1 WD of 3.1.16.

Notify Panel decision.

Panel.

BSCCo.

Approval or rejection of MDD CR.

Proceed in accordance with BSCP508.

Email/ Fax.

3.1.18

Within 1 WD of 3.1.17

Notify Panel decision.

BSCCo.

MPs, SVAA.

MDD Circular.

Email/ Fax.

3.2 Changes to SVAA Calendar

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.2.1

Following authorisation of FAA Payment Calendar.

Authorise SVAA to create draft SVAA Calendar

BSCCo.

SVAA.

Email.

3.2.2

Within 5 WD of 3.2.1

Generate draft version of the SVAA Calendar and submit for review.

SVAA.

BSCCo.

Draft SVAA Calendar.

Internal process.

3.2.3

Within 10 WD of 3.2.2.

Resolve any issues with draft SVAA Calendar.

BSCCo.

SVAA and if appropriate, SAA / FAA / CDCA.

Manual.

3.2.4

Within 1 WD of 3.2.3

Send revised SVAA calendar

BSCCo

SVAA.

Revised SVAA Calendar

Email

3.2.5

Within 2 WD of 3.2.4.

Agree revised SVAA Calendar.

SVAA.

BSCCo.

Email.

3.2.6

Within 1 WD of 3.2.5.

Raise MDD CR.

BSCCo.

Proceed in accordance with 3.3.

Internal process.

3.3 General Changes to MDD7

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.3.1

As required.

Submit MDD CR and associated paperwork.8

Originator.

BSCCo.

F509/016 form and relevant parts of MDD Entity forms document.

Appendix 4 details the changes that can be raised and the originators that can raise them.

Email / Fax.

3.3.2

No later than the MDD CR submission9 deadline set out in the process for the following MDD version.

Review, raise and log MDD CR.

BSCCo.

MDD CR and any supporting information.

Internal process.

3.3.3

If required following 3.3.2

Provide review comments

BSCCo

Originator

Comments on content of MDD CR (F509/01) form submitted

Email/Fax

3.3.4

If required following 3.3.3

Submit new/revised MDD CR if required (return to 3.3.1)

Originator

BSCCo

Email/Fax

3.3.5

Following 3.3.2 and if BM Unit change required.

If MDD CR relates to BM Unit(s), liaise with CRA and confirm they have received notification of forthcoming BM Unit(s) registration.

BSCCo.

CRA.

MDD CR.

Email / Fax.

3.3.6

Following 3.3.2

Send MDD CR for SVAA IA.

BSCCo.

SVAA.

MDD CR and any supporting information.

Email / Fax.

3.3.7

Within 3 WD of 3.3.6

Return SVAA IA.

SVAA.

BSCCo10.

Results of SVAA IA.

Email.

3.3.8

Following analysis of SVAA IA.

Report outcome of SVAA IA.

BSCCo.

Originator.

Results of SVAA IA.

Email / Fax.

3.3.9

If revision needed to MDD CR.

Submit new / revised MDD CR if required (return to 3.3.1).

Originator.

BSCCo

Email / Fax.

3.3.10

Within 2 WD of 3.3.9.

Send details of MDD CR, any supporting information and summary of SVAA IA for IA.

BSCCo.

MPs, SVAA.

MDD Circular, including details of change and summary of SVAA IA.

Email / Fax.

3.3.11

Within 5 WD of 3.3.10.

Return IA and comments.

MPs, SVAA.

BSCCo.

IA and comments on proposed MDD CR.

Email / Fax.

3.3.12

Within 2 WDs of 3.3.11

Consolidate comments of MPs, decide whether to recommend for approval.

BSCCo.

Originator, if necessary.

IA and comments on proposed MDD CR.

Email / Fax.

3.3.13

As required.

Submit MDD CR for approval.

BSCCo.

Panel.

Details of MDD CR and all relevant IAs and consolidated comments.

Internal process.

3.3.14

At next Panel meeting.

Consider MDD CR, IA and consolidated comments and approve or reject MDD CR.

Panel.

Internal process.

3.3.15

Within 1 WD of 3.3.14

Notify Panel decision.

Panel.

BSCCo.

Proceed in accordance with BSCP508 for publication of MDD.

Email / Fax.

3.3.16

Within 1 WD of 3.3.15

Notify Panel decision via MDD Circular.

BSCCo.

SVAA, MPs, Originator.

MDD Circular.

Email / Fax.

3.4 Agree Implementation, Publication and Release Schedule

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.4.1

Prior to anticipated publish of MDD.

Liaise with SVAA and agree timetable11 for publish of forthcoming MDD releases.

BSCCo.

SVAA.

Proposed timetable of publish and go live dates and SVG meeting dates.

Email.

3.4.2

Within 5 WD of 3.4.1.

Provide comments on timetable of forthcoming MDD releases.

SVAA.

BSCCo.

Comments on proposed forthcoming MDD releases.

Email.

3.4.3

Within 1 WD of 3.4.2.

Address comments from SVAA on forthcoming MDD releases and approve.

BSCCo.

Internal process.

3.4.4

Within 1 WD of 3.4.3.

Notify SVAA of approved MDD releases.

BSCCo.

SVAA.

Agreed timetable for forthcoming MDD releases.

Email.

3.4.5

Once MDD release schedule agreed.

Issue MDD Circular notifying MPs of future MDD release schedule. Publish MDD Circular on MDD page of the BSC website.

BSCCo.

MPs, SVAA.

MDD Circular.

Email./ Website publication.

3.5 Treating Emergency Fixes12

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.5.1

Problem requiring an emergency fix.

Identify MDD problem and notify of urgency for resolution.

MPs, SVAA, BSCCo.

BSCCo.

Details of problem and urgency for resolution.

Phone / Email.

3.5.2

As soon as possible after identifying.

Analyse problem, identify solution and liaise with SVAA.

BSCCo.

SVAA.

As appropriate.

Phone / Email.

3.5.3

Following agreement of action to be taken.

Obtain authorisation to implement emergency fix13.

BSCCo.

Panel

Analysis and generation of solutions and associated timescales.

Internal Process.

3.5.4

Following authorisation.

Resolve problem in accordance with agreed approach.

BSCCo.

MPs, SVAA.

As appropriate.

Phone / Email.

3.5.5

As soon as possible.

Instruct MDDM to re-publish MDD.

BSCCo.

MDDM.

Instruction to re-publish MDD. Proceed in accordance with BSCP508.

Email / Fax.

3.5.6

As soon as possible.

Raise MDD CR(s) and send details of changes.

BSCCo.

MPs, SVAA, and other BSC Agents.

MDD Circular detailing all changes to be made.

Email / Fax.

3.6 MDD Fast Track - MDD Housekeeping Changes, Registration of New Market Participants and Additional BM Units

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.6.1

As required

Submit MDD CR14 which has been selected as a housekeeping change and associated paperwork or a new Market Participant submits a CR to register in MDD15 or CR submitted for Additional BM Units

Originator.

BSCCo.

F509/016 form and relevant MDD Entity forms (including justification for being a Housekeeping CR).

Email / Fax.

3.6.2

No later than the Change Request submission deadline16 set out in the process for the following MDD version.

Determine that CR is Housekeeping or Originator is a new Market Participant or CR is for Additional BM Units. Review and log MDD CR.

BSCCo.

MDD CR and any supporting information.

Internal process.

3.6.3

If required following 3.6.2

Provide review comments

BSCCo

Originator

Comments on content of MDD CR (F509/01) form submitted

Email/Fax

3.6.4

If required following 3.6.3

Submit new/revised MDD CR if required (return to 3.3.1)

Originator

BSCCo

Email/Fax

3.6.5

Following 3.6.2 and if BM Unit change required.

If MDD CR relates to BM Unit(s), liaise with CRA to confirm they have received notification of forthcoming BM Unit(s) registration.

BSCCo.

CRA.

MDD CR.

Email / Fax.

3.6.6

Following 3.6.5

Send MDD CR for SVAA IA.

BSCCo.

SVAA.

MDD CR and any supporting information.

Email / Fax.

3.6.7

Within 3 WD of 3.6.6

Return SVAA IA.

SVAA.

BSCCo.

Results of SVAA IA.

Email.

3.6.8

Following analysis of SVAA IA.

Report outcome of SVAA IA.

BSCCo.

Originator.

Results of SVAA IA.

Email / Fax.

3.6.9

If revision needed to MDD CR.

Submit new / revised MDD CR if required (return to 3.6.1).

Originator.

BSCCo.

Email / Fax.

3.6.10

Within 2 WDs of 3.6.9

Consider MDD CR and comments from SVAA. Decide whether the change should be made. Notify Originator.

BSCCo.

Originator, if necessary.

IA and comments on proposed MDD CR.

Email / Fax.

3.6.11

At next available opportunity

Notify Panel of Housekeeping and / or new Market Participant change made and / or new Additional BM Units changes made.

BSCCo.

Panel.

Details of MDD CR and all relevant IAs and consolidated comments.

Internal process.

3.6.12

Within 1 WD of 3.6.11

Notify Housekeeping change and / or new Market Participant registration made and / or new Additional BM Unit changes made via MDD Circular. Publish MDD Circular on MDD page of the BSC website.

BSCCo.

SVAA, MPs, Originator.

MDD Circular.

Email / Fax / Website

4. Appendices

4.1 MDD Entities & Authorisation Route

No

Description

Authorisation Route

Originator

1

Market Participant

3.3

Market Participants, RECCo

2

GSP Licensed Distribution Systems Operator

3.3

LDSO

3

SVA Agent Appointment

3.3

BSCCo / BSC Party

4

SMRA Appointment

3.3

Panel Secretary

5

Default Period Profile Class Coefficient

3.1

BSCCo

6

GSP Group Average EAC

3.1

BSCCo

7

Period Regression Equation

3.1

BSCCo

8

Profile Regression Equation Set

3.1

BSCCo

9

Profile Set

3.1

BSCCo

10

Regression Coefficient

3.1

BSCCo

11

Average Fraction of Yearly Consumption Set17

3.3

BSC Party

12

Average Fraction of Yearly Consumption (AFYC)

3.3

BSC Party

13

GSP Group Profile Class Average EAC

3.3

BSC Party

14

Clock Time Change18

3.3

BSCCo

15

Settlement Calendar

3.2

SVAA

16

Year18

3.3

BSCCo

17

Line Loss Factor Class (LLFC)

3.3

LDSO

18

GSP Group

3.3

BSCCo

19

GSP Group Correction Scaling Factor

3.3

BSCCo

20

GSP Group Profile Class Default EAC

3.3

BSCCo

21

Market Role

3.3

BSC Party

22

Settlement Day (SD) 18

3.3

BSCCo

23

Settlement Period18

3.3

BSCCo

24

Smoothing Parameter

3.3

BSC Party

25

Threshold Parameter

3.3

BSC Party

26

Yearly Season Details18

3.3

BSCCo

27

Clock Interval

3.3

Supplier

28

Clock Time Pattern Regime

3.3

Supplier

29

Measurement Requirement

3.3

Supplier

30

Profile

3.3

BSC Party

31

Profile Class

3.3

BSC Party

32

Standard Settlement Configuration (SSC)

3.3

Supplier / BSCCo

33

Teleswitch TPR

3.3

Supplier

34

Teleswitch Register Rule

3.3

Supplier

35

Teleswitch Contact Rule

3.3

Supplier

36

Teleswitch Contact

3.3

Supplier

37

Teleswitch Group

3.3

Supplier

38

Time Pattern Regimes (TPR)

3.3

Supplier

39

Valid Measurement Requirement Profile Class

3.3

Supplier

40

Valid Settlement Configuration Profile Class

3.3

Supplier

41

Consumption Component Class

3.3

BSC Party

42

Day of the Week

3.3

BSCCo

43

Day Type

3.3

BSCCo

44

Energisation Status

3.3

BSC Party

45

Market Participant Role

3.3

Market Participant / BSCCo/ RECCo

46

Measurement Class

3.3

BSC Party

47

Measurement Quantity

3.3

BSC Party

48

Data item now redundant

N/A

N/A

49

Regression Coefficient Type

3.3

BSC Party

50

Season

3.3

BSC Party

51

Settlement Type

3.3

BSC Party

52

Meter Timeswitch Class (MTC)

3.3

BSC Party

53

Meter Timeswitch Class for Distributor19

3.3

BSC Party

54

Valid MTC SSC Combination

3.3

BSC Party

55

Valid MTC LLFC Combination

3.3

BSC Party

56

Valid MTC LLFC SSC Combination

3.3

BSC Party

57

MTC Meter Type

3.3

BSC Party

58

MTC Payment Type

3.3

BSC Party

59

HH Default EAC

3.3

BSCCo

60

GSP Group Profile Class Tolerances

3.3

BSCCo

61

BM Unit for Supplier in GSP Group

3.3/3.6

Supplier / BSCCo

62

Unmetered Supplies Operational Information20

3.3

BSCCo

63

Valid MTC LLFC SSC PC Combination19

3.3

BSC Party

64

SMETS Version

3.3

BSCCo

4.2 MDD Forms

MDD Change Request Form - F509/01

MDD CR Number

(For BSCCo use)

Part A - Completed by Originator and submitted to BSCCo

Market Participant Id (MPID)………………...Market Participant Role Code………………………..

MDD Entity Forms Attached……………………

Details of proposed change.............................................................................................................

…………………………………………………………………………………………………….

Reason for Change……………………………………………………………………………………….

Originator’s Name ................................................ Company ..............................................

Party ID………………………………………….Password…………………………………………….

Date………………………(Authorised in accordance with BSCP38 except Non-BSC Parties)

Fast Track (3.6) (Please delete one)…..Y / N

 Please tick this box to indicate that approval has been obtained from the relevant Party for data items linked to an MDD Change which is/are not the responsibility of the Originator

Part B - Completed by BSCCo and submitted to SVA Agent

I confirm that appropriate authorisation has now approved the above MDD Change Request.

Please implement the change, ensuring publication no later than (calendar date): .................................

with a Go Live Date of .............................................................................................

BSCCo Name ......................................... Date- ........................................................

Part C - Completed by SVA Agent and returned to the BSCCo

I confirm that above MDD Change Request has been implemented.

SVAA Name ...................................... Date ........................................................................

4.3 MDD Registration Criteria

4.3.1 New Suppliers / Licensed Distribution System Operators (LDSOs)

In order for a new Supplier’s or new LDSO’s Market Participant and Market Participant Role Data to be registered in MDD they must have completed the following steps:

    • Acceded (Registered as a BSC Party); and

    • Qualified (Proven that they can interface with Central Systems).

4.3.2 Existing LDSOs registering in a GSP Group

In order for GSP Group associations (i.e. GSP Group Distributor and SMRA Appointment data) for an LDSO to be registered in MDD they must have completed the following steps:

    • Acceded (Registered as a BSC Party); and

    • Qualified (Proven that they can interface with Central Systems).

    • Have gained PAB approval that their SMRS has completed Qualification (in accordance with BSCP537).

GSP Group registration is progressed through BSCP25.

4.3.3 New BSC Party Agents

In order for a new BSC Party Agent21 to be registered in MDD they must have:

    • Completed Qualification i.e. gained approval from PAB (in accordance with BSCP537) that they have completed the Qualification process.

4.4 MDD Entity Change Request Forms

The MDD Entity Forms are attached to this BSCP as a separate document (BSCP509 Appendix 1: MDD Entity Change Request Forms).

4.4.1 MDD Entity Change Request Forms for CFD

If BSCCo is registering one or more Additional BM Units under instruction from any CFD Settlement Services Provider, spreadsheets or other suitable formats may be used to detail the registration details other than entity 61 form. Suppliers registering Additional BM Units for CFD Assets shall use the entity 61 form. Additional BM Units for CFD Assets must be of BM Unit Type ‘S’ and follow the naming convention for the BM Unit ID and BM Unit Name on the BSC Website.

AMENDMENT RECORD – BSCP509

Version

Date

Description of Changes

Changes Included

Mods/ Panel/ Committee Refs

D0.1

Code Effective Date

Full document before Re-Badging

D.0.2

Code Effective Date

Re-Badging

D0.3

Code Effective Date

Incorporated Version D.02 comments

D0.4

Code Effective Date

Incorporated Version D.03 comments

D.05

Code Effective Date

Comments embodied following CMC1273

2.0

Code Effective Date

Approved for use by the Panel

3.0

Code Effective Date

Version alignment changes from AP509 embodied.

NCR329

4.0

03/02/03

SVA Documentation Batch Release.

CP608, CP721, CP727

SVG22/275

5.0

29/05/03

P81 ‘Removal of the Requirement for Half Hourly Metering on Third Party Generators at Domestic Premises’.

P81

SVG27/366

6.0

24/06/03

Approved Modification P106 for CVA Programme June 03 Release

P106

7.0

01/08/03

Updated for Modification P62

P62

SVG29/390

8.0

27/11/03

Approved Change Proposal 923

CP923

9.0

03/11/04

Change Proposal for the CVA Programme Nov 04 Release

CP1032

TDC58/03

10.0

23/02/05

SVA and CVA February 05 Release

CP1041, CP1049, CP1091

11.0

BETTA Effective Date

BETTA 6.3

BETTA 6.3

SVG48/004

12.0

29/06/06

June 2006 Release

CP1150

SVG/64/02

13.0

22/02/07

Draft February 07 Release

CP1158, CP1172, CP1176

SVG66/04 ISG66/06

14.0

23/08/07

P197 Release

P197

P/115/04

15.0

01/11/07

November 07 Release

CP1190, CP1210

SVG77/04

ISG79/02

SVG79/02

16.0

26/06/08

June 08 Release

CP1216

SVG82/03

17.0

25/06/09

June 09 Release

CP1270

SVG97/01

CP1271

SVG97/01

18.0

05/11/09

November 09 Release

CP1269

SVG97/01

19.0

04/11/10

November 10 Release

CP1327

SVG112/03

20.0

07/11/13

November 2013 Release

CP1390

SVG148/04

21.0

27/02/14

27 February 2014 Release

CP1396

SVG153/03

22.0

01/08/14

Electricity Market Reform

ORD005

Directed by the Secretary of State

23.0

01/09/21

1 September 2021 Non-Standard Release

P420

P316/05

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.

1 The previous version of BSCP509 required MPs to register in accordance with form F509/02 which was contained within this BSCP.

2 BSCP509 Appendix 2: MDD Change Request Entity Validation, details an array of scenarios in which an MDD CR may be required along with the information that should be included with such MDD CRs.

3 LDSOs will include Independent LDSOs.

4 The PEG consists of volunteer industry experts requested by Elexon and appointed on an ad-hoc basis.

5 Steps 3.1.7- 3.1.10 may be repeated on request of the PrA as long as this does not prejudice the timescale in 3.1.11.

6 F509/01 form must be completed with the aid of the scenarios set out in BSCP509 Appendix 2: MDD Change Request Entity Validation

7 Approved MDD changes for new Suppliers, new LDSOs, existing LDSOs and new Party Agents should be made in accordance with the criteria in Appendix 4.3. MDD changes related to MDD Housekeeping, Registration of New Market Participants or registration of Additional BM Units should follow 3.6.

8 Participants raising CRs relating to Additional BM Unit registration, BM Unit deregistration or Cessation of Supplier should ensure the procedures within BSCP15 are followed. Participants raising CRs in relation to the registration or deregistration of a Supplier ID should ensure the procedures within BSCP65 are followed. BSCCo will raise CRs relating to Unmetered Supplies Operational Information in accordance with BSCP520. GPS Group Registration is progressed through BSCP25.

9 Refer to the MDD release schedule published on the BSC Website for general changes.

10 If any proposed change(s) will result in a change to the MDD software, proceed in accordance with BSCP40.

11 BSCCo will issue a release schedule for general changes to MDD and for new Market Participants,Party Agents and Additional BM Units. The Change Request submission dates will differ for each type of change, however they will both be included in the same MDD Publish.

12 An emergency fix will only be required if, following an MDD publish and subsequent go-live, an error in the MDD data is reported, either by BSCCo, the SVAA or a Market Participant. An emergency fix can be defined as an additional publish of MDD which would include an incremented version number.

13 Authorisation to be sought from Panel.

14 A Housekeeping CR is one which is of a minor nature and it is self-evident that the change would improve the data within MDD.

15 This may include Market Participant, Market Participant Role, SMRA Appointment and / or BM Unit for Supplier in GSP Group data.

16 Refer to the MDD release schedule published on the BSC Website for new Market Participants and Party Agents.

17 A change to end the use of an AFYC Set will not be permitted if it results in SVA Metering Systems having invalid combinations of Profile Class, SSC and GSP Group.

18 The annual updates of these entities will be progressed simultaneously.

19 Changes relating to this entity shall be agreed with the relevant LDSO prior to making a formal submission.

20 This information is not included in the MDD database, but can be found on the BSC Website.

21 Excluding SVA MOAs who will be qualified in accordance with the Retail Energy Code Qualification and Maintenance Schedule