BSCP501: Supplier Meter Registration Service

v 19.0
Effective From Date:
Status:SUPERSEDED
Other versions
Download

Balancing and Settlement Code

BSC PROCEDURE

SUPPLIER METER REGISTRATION SERVICE

BSCP501

Version 19.0

Date: 30 June 2022

BSCP501 relating to Supplier Meter Registration Service

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 BSCP501, Version 19.0 relating to Supplier Meter Registration Service.

3. This BSC Procedure is effective from 30 June 2022.

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

D0.1

Code Effective Date

Re-Badged.

D0.2

Code Effective Date

Incorporated version D.01 review comments.

2.0

Code Effective Date

Approved for use by the Panel.

3.0

Code Effective Date

Incorporation of SMRS to CMRS Transfers (NCR114) and version alignment changes from AP501 embodied (NCR329).

NCR114,

NCR329

4.0

27/03/01

Further changes embodied for NCR329.

NCR329

5.0

10/10/02

Incorporates changes for P55 and CP753.

P55

CP753

P/40/013

ISG/16/167

SVG/22/277

6.0

03/02/03

SVA Documentation Batch Release.

CP698

SVG/22/275

7.0

17/02/03

Incorporates changes for P63.

P63

SVG/20/251

SVG/21/256

8.0

01/08/03

Updated for Modification P62

P62

SVG/29/390

9.0

04/11/03

SVA November 2003 Release

CP836

SVG/33/442

10.0

23/02/05

SVA February 2005 Release and BETTA 6.3

BETTA 6.3, P159, CP981, CP993, CP1091

SVG/47/004

11.0

06/11/08

November 2008 Release

CP1176 (part)

ISG68/02

SVG67/16

CP1237

ISG88/01

SVG88/02

PAB88/03

12.0

25/06/09

June 2009 Release

CP1272

SVG97/01

13.0

04/11/10

November 2010 Release

CP1267 v1.0

SVG104/01

14.0

25/06/15

June 2015 Release

CP1424

SVG168/05

15.0

29/06/17

June 2017 Release

CP1474

SVG191/03

16.0

27/06/19

June 2019 Release

CP1515

SVG218/02

17.0

25/06/20

June 2020 Release

CP1523

SVG208/04

18.0

01/09/21

September 2021 Release

P420

P316/05

19.0

30/06/22

June 2022 Release

CP1552

SVG251/06

1. Introduction

1.1 Scope and Purpose of the Procedure

This BSC Procedure defines those activities which enable the Supplier Meter Registration Service (SMRS) to fulfil its functions, relating to the following:-

Provide Suppliers with information relating to their MSIDs.

Notify Suppliers of loss of Settlement liability for MSIDs previously allocated to them. Provide New Suppliers with the Metering System Registration Data related to their MSIDs.

In the case of ‘fringe’ supplies, the SMRA within whose service area the SVA Metering System falls, is responsible for providing the Registration Service.

Provide Half Hourly Data Aggregators with MSID information.

Provide HHDAs with Half Hourly SVA Metering System Registration Data.

Provide Non Half Hourly Data Aggregators with MSID information.

Provide NHHDAs with Non Half Hourly SVA Metering System Registration Data.

Receive and process Supplier data.

To update the SMRS database with information when the Supplier is the data source.

Bulk Change of Non Half Hourly Supplier Agent

Where there is to be a change in a NHH Supplier Agent (bulk change of agent) such that the number of SVA Metering Systems affected exceeds a threshold set by the BSC Panel, a bulk change of agent application will be submitted for approval in accordance with BSCP513. Following such approval, this BSC Procedure will be used to process the bulk change of agent, without adversely impacting the normal daily operations of the SMRA.

Receive and process Licensed Distribution System Operator data.

To update the SMRS database with information when the Licensed Distribution System Operator is the data source.

Receive, validate and process SVA Meter Operator Agent data.

To validate information when the SVA Meter Operator Agent is the source and update the SMRS database with valid information. To send a response to the SVA Meter Operator Agent to notify the outcome of the validation.

Receive and process Market Domain Data.

To update the SMRS database with information from the Market Domain Data source.

Enable Transfers of Registrations between SMRS and CMRS.

To facilitate the Transfers of Registrations of Third Party Generator / Exemptable Generating Plant between SMRS and CMRS and vice versa.

Enable new connections where the same Metering Equipment at an Exemptable Generating Plant is comprised in both an SVA Metering System and a CVA Metering System, where Export Active Energy is traded in CVA and Import Active Energy is traded in SVA.

To ensure that relevant information is passed between appropriate participants and certain checks are carried out in the CVA and SVA registration systems to facilitate this type of registration.

Record BSCCo Required Data

To record the BSCCo Required Data for every Settlement Day that the MSID is connected.

1.2 Main Users of Procedure and their Responsibilities

This BSC Procedure should be used in the main by the SMRSs.

However the following organisations will also require input to or output from the SMRS; the SVAA (as MDDM), Suppliers, Data Aggregators, Licensed Distribution System Operators, SVA Meter Operator Agents, BSCCo, Central Registration Agent and the Transfer Co-ordinator.

Each Licensed Distribution System Operator is required to provide a single SMRS. As there is no restriction on the number of Licensed Distribution System Operators that may operate within a single GSP Group, there may also be a number of different SMRSs operating within that same GSP Group.

1.3 SMRS Access Restrictions, Controls and Constraints

The SMRA shall only permit access to people whose job responsibilities include the operation, support or audit of the SMRS.

For the avoidance of doubt, the access restrictions relating to the SMRA’s commercial role only relate to the Code requirements and Code Required Data.

The SMRA shall implement and maintain at least the following controls:

• Unique MSIDs in order that the Settlement system can work;

• Validation checks to ensure that all mandatory data fields are present on registration, and data is input accurately;

• Controls to ensure that the LDSO disconnects the correct SVA Metering System within SMRS;

• Controls to ensure that standing data is complete, accurate and up-to-date (i.e. consistent with the most recent valid input), and that there have not been unauthorised (i.e. invalid) changes;

• Controls to ensure that SVA Metering Systems are allocated to the correct GSP Group;

• Controls to ensure that the data held by the SMRS remains confidential;

• Controls to ensure that information is distributed to only the correct Party and Party Agents;

• Controls over input, processing and output (as well as over data and communications) in order to ensure that the rules for valid data processing defined during system design (including those specified by the Code) are adhered to, and the data held and processed by the SMRS is accurate, complete, valid and not out of date; and

• Controls over the development and implementation of the SMRS (including the authorisation and co-ordination of transfers of data and programs) to ensure that:

- The system is tested prior to going live, with test plans and results documented;

- Systems documentation is provided in sufficient detail to support ongoing operational and future maintenance;

- Quality management is used;

- Migration of data onto the SMRS is conducted in a controlled manner, with data validity checks carried out;

- Users are adequately trained such that they are competent in the use of the system;

- Separate test and live environments are used; and

- A fully documented and repeatable system test model is used.

The SMRS shall be developed and operated in line with the following constraints:

• The SMRS shall allow entry of new Suppliers to the market and the exit of Suppliers from the market;

• The SMRA shall implement and maintain controls to ensure registration is made against the correct MSIDs (for the avoidance of doubt, MSIDs are allocated by the LDSO, who allocates the GSP Group for an SVA Metering System); and

• The SMRS shall enable the unambiguous identification of all SVA Metering Systems and their previous and current Suppliers together with dates of any changes.

1.4 Audit Trail and Auditor Access

The SMRA shall implement and maintain an audit trail which has at least the following characteristics:

• Data shall be traceable from the data held in SMRS to the source instruction and vice versa;

• Data shall be stored on magnetic or optical media in a consistent format;

• The SMRA shall record the effective date of changes in responsibilities;

• Movement of SVA Metering Systems between different SMRSs upon change of SVA Metering System’s LDSO shall be traceable;

• The SMRA shall be able to retrieve values of amended data in order to ensure that a full transaction history is available; and

• The data held on SMRS shall be maintained in order to ensure completeness, accuracy, and timeliness. The changes to data held require the following:

- That changes made shall be easily identifiable;

- The effective date for those changes made;

- The authoriser of the change and their authority; and

- For any manual changes, an explanation of why the change was made.

The SMRA shall ensure that the BSC Auditor has access at reasonable times and at reasonable notice to:

• Software, hardware or information held by the SMRA or its agents, where reasonably required by the BSC Auditor to fulfil its obligations under the Code;

• The relevant parts of the SMRA’s premises; and

• Relevant staff members of the SMRA, for a reasonable length of time in any one year.

1.5 Qualification

In providing the services specified in this BSCP, the SMRA shall use systems and processes so approved in accordance with BSCP537 that comply with the Code, BSC Procedures and PSL100.

1.6 Service Availability and Service Levels

On Working Days, the SMRA shall use reasonable endeavours to ensure that staff are available during Service Hours, defined as from 09:00 to 18:00.

The SMRA shall use reasonable endeavours to ensure that any planned outages are scheduled such that there is the minimum amount of disruption to the Service, and wherever practicable provide as much notice as possible to the relevant Data Aggregators and Suppliers.

In the event of an unplanned cessation of processing, the SMRA shall use reasonable endeavours to reinstate the service to meet its requirements under this BSCP as quickly as possible, and shall implement its disaster recovery procedures within 48 hours of the start of the cessation of processing.

Where agreed with the associated Supplier, the SMRA may provide additional services in support of a bulk change of agent outside of normal working hours, providing these additional services do not adversely impact its normal operational activities.

The SMRA shall provide BSCCo with information derived from its systems and processes so approved in accordance with BSCP537 in accordance with the SVA Data Catalogue, BSCP533 and its Appendices such that the SMRA can comply with the requirements of Appendix 4.7. All such communications shall be date-timestamped by the SMRA.

1.7 Use of the Procedure

This procedure should be referred to by the users to understand the responsibilities and role of the SMRA and the relationships between the SMRA, Licensed Distribution System Operator (LDSO), Suppliers, SVA MOAs, UMSO, SVAA and Data Aggregation agents.

Throughout this procedure, timetables reflect the number of Working Days (WD) within which an activity should be completed.

Although not shown in each interface timetable, there is an assumption that each communication successfully received at the SMRS gateway will be acknowledged by the Data Transfer Network. The acknowledgements sent will indicate the number of transactions received in each communication. In addition, SMRA will report to the originator, the number of files accepted and the number of files rejected (with reason codes) in accordance with the interface timetable.

The interface timetables in this BSCP show that any changes to registration data in SMRS shall be notified to the LDSO. Although not shown in each interface timetable, there is an assumption that where changes relate to an Unmetered Supply, the details of these changes shall also be notified to the UMSO by the LDSO.

In the case of non half hourly Supplier Agents, the SMRA will be informed via BSCP513 of any Supplier’s intention to initiate a change of agent where the number of Metering Systems affected exceeds the threshold set by the Panel. The SMRA will be required to confirm whether it can implement the proposed changes without adversely impacting other SMRS activities. Any bulk change of agent must therefore be initiated via BSCP513 before triggering the processes in this BSC Procedure.

The remaining sections in this document are:

Section 2 – Not used.

Section 3 - Interface and Timetable Information: this section defines each business process in detail. In addition, there, may be references to ‘D’ and ‘P’ dataflows in the ‘Information Required’ column.

Section 4 - Appendices: this section contains supporting information

The SVAA will be managing the Market Domain Data in addition to performing the Supplier Volume Allocation role, and therefore SVAA is the Market Domain Data Manager (MDDM).

1.8 Balancing and Settlement Code Provision

This BSC Procedure has been produced in accordance with the provisions of 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.

The requirements of SMRAs under the Code can be found in BSC Section J. An overview of these requirements is as follows:

The principal functions of an SMRA are to:

• Provide and operate a registration service in respect of those Boundary Points on the Distribution System(s) and Associated Distribution System(s) (if any) of such SMRA which are not registered in the Central Meter Registration Service;

• Provide data from such registration system to Parties, Party Agents and BSC Agents for the purposes of Settlement; and

• Provide BSCCo with data from such registration system for the purposes of monitoring in accordance with BSCP533.

1.9 Associated BSC Procedures

The following BSC Procedures interface with this BSC Procedure and should be read in conjunction with BSCP501.

BSCP68

Transfer of Registration of Metering Systems between CMRS and SMRS

BSCP503

Half Hourly Data Aggregation for Metering Systems Registered in SMRS

BSCP505

Non-Half Hourly Data Aggregation for Metering Systems Registered in SMRS

BSCP508

Supplier Volume Allocation Agent

BSCP513

Bulk Change of Non Half Hourly Supplier Agent

BSCP515

Licensed Distribution

BSCP533

PARMS Data Provision, Reporting and Publication of Peer Comparison Data

BSCP537

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

BSCP550

Shared SVA Meter Arrangements of Half Hourly Import and Export Active Energy

1.10 Associated Party Service Lines

The following Party Service Line interfaces with this BSC Procedure and should be read in conjunction with BSCP501.

PSL100

Generic Non Functional Requirements for Licensed Distribution System Operators and Party Agents

1.11 Acronyms and Definitions

In addition the following meanings and acronyms are used in this BSC Procedure.

BSCCo

Balancing and Settlement Code Company

CD

Calendar Days being all Working Days & Non-Working Days

CMRS

Central Meter Registration Service

DA

Data Aggregator (either Half Hourly or Non-Half Hourly)

Data

Those items denoted as used by the SMRS in the SVA Data Catalogue

DC

means Data Collector (either Half Hourly or Non-Half Hourly)

DUoS

Distribution Use of System

EFSD {REGI}

Effective From Settlement Date {Registration}

HHDA

Half Hourly Data Aggregator

Invalid data

Data which falls outside pre-defined parameters, or is incomplete or is corrupt

LDSO

Licensed Distribution System Operator

MDDM

Market Domain Data Manager

SVA MOA

SVA Meter Operator Agent

Metering System Registration Data

All BSCCo Required Data associated with Data Collector appointment; Data Aggregator appointment and Registration plus SVA Metering System Standing Data

Metering System Standing Data

All Code Required Data associated with SVA Metering Systems, Energisation Status, GSP Group, Line Loss Factor Class, Measurement Class, Profile Class, Standard Settlement Configuration and Measurement Quantity

MSID

Metering System Identifier

MPAS

Metering Point Administration Service, which is the MRA term for SMRS

NHHDA

Non-Half Hourly Data Aggregator

REC

Retail Energy Code

SMETS

Smart Metering Equipment Technical Specifications

SMRA

Supplier Meter Registration Agent

SMRS

Supplier Meter Registration Service

SSD

Supply Start Date (also known as Effective from Settlement Date {REGI})

Supplier-serviced Metering System

A Metering System where the Supplier obtains data from a SMETS compliant Meter, either directly or using a service provider

SVA

Supplier Volume Allocation

SVAA

Supplier Volume Allocation Agent

UMSO

Unmetered Supplies Operator

Valid data

Data which falls within pre-defined parameters, and is complete and is not corrupt

Validation

The process by which data is tested in order to establish whether it is ‘valid data’ or ‘invalid data’

WD

Working day

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

2. Not Used

3. Interface and Timetable Information

3.1 SVAA sends Market Domain Data

REF

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.1.1

At any time.

Request MDD

SMRA.

MDDM.

SMRS Id.

Electronic or other method as agreed.

3.1.2

Either on request from SMRA or when published by SVAA.

Send MDD.

SVAA.

SMRA.

D0269 Market Domain Data Complete Set.

D0270 Market Domain Data Incremental Set.

Electronic or other method, as agreed.

3.1.3

Within 1 WD of receipt of MDD.

Send acknowledgement that data has been received1.

SMRA.

MDDM.

P0024 Acknowledgement.

Electronic or other method, as agreed.

3.1.4

If data in incorrect format, corrupt or otherwise cannot be loaded.

Send notification and await receipt of corrected MDD.

SMRA.

MDDM.

P0035 Invalid Data.

Electronic or other method, as agreed.

3.1.5

Send corrected MDD.

SVAA.

SMRA.

Refer to 3.1.2 for dataflows.

Electronic or other method, as agreed.

3.1.6

Within 1 WD of receipt of MDD.

Send acknowledgement that data has been received1.

SMRA.

MDDM.

P0024 Acknowledgement.

Electronic or other method, as agreed.

3.1.7

If data in correct format (as soon as practicable, and in any case within 5 WD).

Update database2.

SMRA.

Internal Process.

3.2 Update of SMRS Database by Licensed Distribution System Operator

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.2.1

As soon as possible and in any event within 5 WD of (i) the effective date of the change; or (ii) receiving notification that a change is required if this occurs after the effective date of the change.

Provide changes to MS data, excluding Metering Point Address and Metering Point Postcode3, made by LDSO

LDSO

SMRA.

Changes to MS data. (e.g. MSID; LLF Class Id4, GSP Group Id; 1998 Trading Arrangement Indicator; Disconnection Date5 and address of premises).

Electronic or other method, as agreed.

3.2.2

On receipt of data.

Perform validation checks (i.e. Supplier Id etc are valid as published by SVAA (MDDM)).

SMRA.

Appendix 4.3 – Data Validation.

Internal Process.

3.2.3

Unsuccessful validation.

Notify originator of receipt of invalid data.

SMRA.

LDSO

Original message identifier and reason(s) for failure.

Electronic or other method, as agreed.

3.2.4

Upon successful validation and within 1WD of 3.2.2 above.

Update database.

SMRA.

Internal Process.

3.2.5

Confirm changes of data.

SMRA.

LDSO.

Current and / or future Supplier.

Current and / or future DA.

MSID; relevant changed data; current Supplier Id; Data Aggregator Id.

D0171 Notification of Distributor Changes to Metering Point Details.

D0209 Instruction(s)to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

3.2.6

Following 3.2.5.

Process instructions in accordance with section 3.11.

DA.

3.2A Not Used

3.2B Not Used

3.3 Update of SMRS Database by Supplier6

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.3.1

As soon as possible and in any event within 5 Working Days of (i) the effective date of the change; or (ii) receiving notification that a change is required if this occurs after the effective date of the change7 8.9

Notify changes of MSID specific changes by Supplier.

Current and / or future Supplier.

SMRA.

D0205 Update Registration Details10.

Electronic or other method, as agreed.

3.3.2

On receipt of data.

Perform validation checks (i.e. Supplier Id etc are valid as published by SVAA (MDDM)).

SMRA.

Appendix 4.3 – Data Validation.

Internal Process.

3.3.3

Unsuccessful validation.

Notify originator of receipt of invalid data.

SMRA.

Current and / or future Supplier.

D0172 Confirmation of Changes. D0203 Rejection of Changes to Metering Point Details.

Electronic or other method, as agreed.

3.3.4

Successful validation.

Update database.

SMRA.

Internal Process.

3.3.5

Within 1 WD11 of 3.3.4 above.

Confirm changes of data.

SMRA.

LDSO

Current Supplier.

Future Supplier.

Current and / or future DA, as appropriate.

MSID; relevant changed data; current Supplier Id; Data Aggregator Id.

D0172 Confirmation of Changes.

D0213 Advice from MPAS of Changed Metering Point Details.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

3.3.6

Following 3.3.5.

Process instructions in accordance with section 3.11.

DA.

3.3.7

DA validates instructions from SMRA. If SMRA instructions valid, update database.

If problem with file not caused by DA notify SMRA.

Generate a revised file and send or resend an exact copy of file or if problem caused by DA notify DA.

DA.

DA.

SMRA.

SMRA.

DA.

P0035 Invalid Data (for physical integrity problems) or D0023 Failed Instructions (for instruction level problems).

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Internal Process.

Electronic or other method, as agreed.

3.3.8

Within 1 WD of 3.3.4 above.

If NHHDC appointment details changed, confirm changes of data.

SMRA.

Old NHHDA12.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

3.3.9

Following 3.3.8.

Process instructions in accordance with section 3.11.

Old NHHDA.

3.4 Change of Supplier for Half Hourly SVA Metering System

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.4.1

Between SSD-28CD and SSD-1 WD or where SMRA allows a registration application on SSD, on the SSD13

Notification of Settlement liability for supply.

New Supplier.

SMRA.

D0055 Registration of Supplier to Specified Metering Point11.

Electronic or other method, as agreed.

3.4.2

On receipt of data.

Perform validation checks.

SMRA.

Appendix 4.3 – Data Validation.

Internal Process.

3.4.3

On unsuccessful validation and within 1 WD12 of 3.4.2.

Notify originator of receipt of invalid data.

SMRA.

New Supplier.

D0057 Rejection of Registration.

If MSID is root of error or missing, then this data item may be omitted.

Electronic or other method, as agreed.

3.4.4

On successful validation and within 1 WD14 of 3.4.2.

Notify change of Settlement liability for MSID and Supply Start Date

SMRA.

LDSO

New Supplier.

Old HHDA, new HHDA.

New Supplier Id; MSID and Supply Start Date.

D0171 Notification of Distributor Changes to Metering Point Details.

D0172 Confirmation of Changes.

D0217 Confirmation of the Registration of a Metering Point.

D0260 Notification from MPAS of Old Registration Details.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

3.4.5

Following 3.4.4.

Process instructions in accordance with section 3.11.

HHDA.

3.4.6

Within 1 WD15 of 3.4.2.

If validation checks successful, notify loss of Settlement liability to old Supplier.

SMRA16.

Old Supplier.

D0058 Notification of Termination of Supply Registration.

Electronic or other method, as agreed.

3.5 Change of Data Aggregator for SVA Metering System17 18

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.5.1

On change of DA.

Notify appointment of New DA for MSID.

Current and / or future Supplier.

SMRA.

D0205 Update Registration Details.

Electronic or other method, as agreed.

3.5.2

On receipt of data.

Perform validation checks. (i.e. Supplier Id etc are valid as published by SVAA (MDDM)).

SMRA.

Appendix 4.3 – Data Validation.

Internal Process.

3.5.3

On unsuccessful validation and within 1 WD12 of 3.5.2.

Notify originator of receipt of invalid data.

SMRA.

Current and / or future Supplier.

D0203 Rejection of Changes to Metering Point Details.

If MSID is root of error or missing, then this data item may be omitted.

Electronic or other method, as agreed.

3.5.4

On successful validation and within 1 WD19 of 3.5.2.

Notify change of appointment of DA.

SMRA.

LDSO.

Current and / or future DA, as appropriate.

Current Supplier.

Future Supplier.

MSID; Supply Start Date; New DA Id; Effective to Settlement Date; Old DA Id.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

D0172 Confirmation of Changes.

D0213 Advice from MPAS of Changed Metering Point Details.

Electronic or other method, as agreed.

3.5.5

Following 3.5.4.

Process instructions in accordance with section 3.11.

DA.

3.6 New Connection for SVA Metering System20

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.6.1

Within 2 WD of completion of the works associated with the new connection, or LDSO’s decision or agreement with the Supplier to enter a new MSID.

Notify new MSID data.

LDSO

SMRA.

MSID, GSP Group Id, LLF Class Id21, 1998 TA Indicator and Metering Point Address.

Electronic or other method, as agreed.

3.6.2

Between SSD-28CD and SSD-1 WD or where SMRA allows a registration application on SSD, on the SSD14

Notify Settlement liability for MSID and Supply Start Date22.

Supplier.

SMRA.

D0055 Registration of Supplier to Specified Metering Point11.

DA Id; DC Id, Profile Class, Standard Settlement Configuration, Measurement Class and Energisation Status23.

Electronic or other method, as agreed.

3.6.3

Within 1 WD of either 3.6.1 or 3.6.2.

Perform validation checks. If attempt made to change Energisation Status to “energised” or ” de-energised” whilst any mandatory field is blank, then invalidate Registration (i.e. unsuccessful).

SMRA.

Appendix 4.3 – Data Validation.

Internal Process.

3.6.4

On unsuccessful validation and within 1WD12 of either 3.6.1 or 3.6.2.

Notify originator of receipt of invalid data.

SMRA.

Supplier.

D0057 Rejection of Registration.

Electronic or other method, as agreed.

3.6.5

On successful validation and within 1WD24 of 3.6.2.

Notify Settlement liability for New MSID.

SMRA.

LDSO

Supplier.

DA.

Supplier Id; MSID; DA Id24, DC Id24 and Supply Start Date.

D0171 Notification of Distributor Changes.

D0172 Confirmation of Changes.

D0217 Confirmation of the Registration of a Metering Point.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

3.6.6

Following 3.6.5.

Process instructions in accordance with section 3.11.

DA.

3.7 Change of Supplier for Non-Half Hourly SVA Metering System

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.7.1

Between SSD-28CD and SSD-1WD or where SMRA allows a registration application on SSD, on the SSD14

Notification of Settlement liability for supply.

New Supplier.

SMRA.

D0055 Registration of Supplier to Specified Metering Point11.

Electronic or other method, as agreed.

3.7.2

On receipt of data.

Receive notification of New Supplier liability and perform validation checks.

SMRA.

Appendix 4.3 - Data Validation.

Internal Process.

3.7.3

On unsuccessful validation and within 1 WD12 of 3.7.2.

Notify originator of receipt of invalid data.

SMRA.

New Supplier.

D0057 Rejection of Registration.

Electronic or other method, as agreed.

3.7.4

On successful validation and within 1 WD25 of 3.7.2.

Notify change of Settlement liability for MSID and Supply Start Date.

SMRA.

LDSO.

New Supplier.

Old NHHDA, new NHHDA.

New Supplier Id; MSID and Supply Start Date.

D0171 Notification of Distributor Changes.

D0172 Confirmation of Changes.

D0217 Confirmation of the Registration of a Metering Point.

D0260 Notification from MPAS of Old Registration Details.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

3.7.5

Following 3.7.4.

Process instructions in accordance with section 3.11.

NHHDA.

3.7.6

Within 1 WD26 of 3.7.2.

If basic validation checks successful, notify loss of Settlement liability to old Supplier.

SMRA27.

Old Supplier.

D0058 Notification of Termination of Supply Registration.

Electronic or other method, as agreed.

3.8 Request for SMRS Information

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.8.1

At any time.

Request Refresh of database.

DA.

SMRA.

MSID, if for selective refresh.

Manual, Fax.

3.8.2

Within 1 WD of 3.8.1 above for Full Refreshes. 28

Notify applicant of scheduled date for delivery of Full Refresh29.

SMRA.

DA.

Scheduled date.

Manual, Fax.

3.8.3

Within 15 WD of 3.8.1 above for Full Refreshes, within 1 WD30 for Selective Refreshes.

Send Refresh of database.

SMRA.

DA.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or CD ROM, or other method, as agreed.

3.8.4

Following 3.8.3.

Process instructions in accordance with section 3.11.

DA.

3.8.5

Within 28 CD of original message.

Request Resend of Instruction File.

DA.

SMRA.

Message sequence number and/or Date.

Manual.

3.8.6

Within 1 WD of receipt of request.

Accept or refuse request.

SMRA.

Internal Process.

3.8.7

Within 1 WD31 of 3.8.4 above.

Resend message using same file sequence number.32

SMRA.

DA.

Duplicate of original instruction (including date that file was originally sent).

Electronic or other method, as agreed.

3.8.8

Following 3.8.7.

Process instructions in accordance with section 3.11.

DA.

3.9 Removal of a SVA Metering System

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.9.1

Following the removal of SVA Metering System.

Notify disconnection of SVA Metering System.33

LDSO

SMRA.

Disconnection Date and MSID.

Manual, Electronic or other method, as agreed.

3.9.2

On receipt of notification.

Perform validation checks.

SMRA.

Appendix 4.3 – Data Validation.

Internal Process.

3.9.3

On unsuccessful validation.

Notify originator of receipt of invalid data.

SMRA.

LDSO

MSID, original message identifier and reason for failure.

(If MSID is root of error or missing, then this data item may be omitted).

Electronic or other method, as agreed.

3.9.4

On successful validation.

Notify removal of SVA Metering System34.

SMRA.

Current and / or future Supplier.

Current and / or future DA.

D0171 Notification of Distributor Changes to Metering Point Details.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or manual.

3.9.5

Following 3.9.4

Process instructions in accordance with section 3.11.

DA.

3.9.6

Following notification in 3.9.4

Notify removal of SVA Metering System where the SVA Metering System is associated with Exemptable Generating Plant and the Export Meter(s) is Registered in CMRS.

Current and / or future Supplier.

BSCCo

Fax/ Email

3.9.7

Following notification in 3.9.6

BSCCo to update internal records.

BSCCo

Update records for Metering Equipment at an Exemptable Generating Plant comprised in both an SVA Metering System and a CVA Metering System.

Internal Process

3.10 New Connection for Metering System which is associated with Exemptable Generating Plant and where the Export Meter(s) is Registered in CMRS35

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.10.1

Within 2 WD of completion of the works associated with the new connection, or LDSO’s decision or agreement with the Supplier to enter a new MSID.

Notify new MSID data.

LDSO

SMRA.

MSID, GSP Group Id, LDSO Id, LLF Class Id22, 1998 TA Indicator and Metering Point Address.

Electronic or other method, as agreed.

3.10.2

Between SSD-28CD and SSD-1 WD or where SMRA allows a registration application on SSD, on the SSD14

Notify Settlement liability for MSID and Supply Start Date.

Supplier.

SMRA.

D0055 Registration of Supplier to Specified Metering Point.

DA Id; DC Id, Profile Class, Standard Settlement Configuration, Measurement Class and Energisation Status24.

Electronic or other method, as agreed.

3.10.3

At the same time as 3.10.2

Notify BSCCo of the sites(s) which form part of the Exemptable Generating Plant.

Supplier.

BSCCo.

Supplier Id, LDSO Id, Site Name, Site Address, GSP Group, Site Occupier Name, Connection Voltage

Fax/ Email

3.10.4

Within 1 WD of 3.10.3

Request the EFSD {REGI} and associated details from LDSO.

BSCCo

LDSO

Supplier Id, Site Name, Site Address, Site Occupier Name, Connection Voltage, Energisation Status, Energisation Status Date, EFSD {REGI}.

Fax/ Email

3.10.5

Within 2 WD of 3.10.4.

Provide EFSD {REGI} and associated details.

LDSO

BSCCo

Supplier Id, Site Name, Site Address, Site Occupier Name, Connection Voltage, EFSD {REGI}, Energisation Status, Energisation Status Date, EFSD {REGI}.

Fax/ Email

3.10.6

Within 1 WD of 3.10.5

Check that the EFSD {REGI} registered for the Import(s) in SMRS for Exemptable Generating Plant is earlier or the same as that registered for any related Export(s) in CRA.

BSCCo

CRA

Check data provided in conjunction with BSCP20.

Fax/ Email

3.10.7

Immediately after 3.10.6 and if checks are unsatisfactory.

Resolve issues.

BSCCo

Supplier

Telephone/Fax / Email

3.10.8

Immediately after 3.10.6 or once issues resolved from 3.10.7.

Inform Supplier that registration can continue.

BSCCo

Supplier

Notification that registration of Import MSID(s) only can proceed.

Note: Supplier may need to request a change in their Settlement liability following resolution of 3.10.7 via D0205 Update Registration Details36.

Fax/ Email

3.10.9

Following 3.10.8.

Update internal records for Meter(s) at an Exemptable Generating Plant comprised in both an SVA Metering System and a CVA Metering System.

BSCCo

Site Address, GSP Group, Export CVA MSID, Import SVA MSID, CVA Registrant details, SVA Supplier details and REFD.

Internal Process.

3.10.10

Within 1 WD of either 3.10.1 or 3.10.2. or immediately after 3.10.9

Perform validation checks. If attempt made to change Energisation Status to “energised” or “de-energised” 25 whilst any mandatory field is blank, then invalidate Registration (i.e. unsuccessful).

SMRA.

Appendix 4.3 – Data Validation.

Internal Process.

3.10.11

On unsuccessful validation and within 1 WD12 of either 3.10.1 or 3.10.2. or immediately after 3.10.9

Notify originator of receipt of invalid data.

SMRA.

Supplier.

D0057 Rejection of Registration.

Electronic or other method, as agreed.

3.10.12

Immediately after 3.10.11

Notify BSCCo of rejection of Registration.

Supplier

BSCCo

Fax / Email

3.10.13

On successful validation and within 1 WD37 of 3.10.2. or immediately after 3.10.9

Notify Settlement liability for New MSID.

SMRA.

LDSO

Supplier.

DA.

Supplier Id; MSID; DA Id24, DC Id24and Supply Start Date.

D0171 Notification of Distributor Changes.

D0172 Confirmation of Changes.

D0217 Confirmation of the Registration of a Metering Point.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

3.10.14

DA validates instructions from SMRA. If SMRA instructions valid, update database.

If problem with file not caused by DA notify SMRA.

Generate a revised file and send or resend an exact copy of file or if problem caused by DA notify DA.

DA.

DA.

SMRA.

SMRA.

DA.

P0035 Invalid Data (for physical integrity problems) or D0023 Failed Instructions (for instruction level problems.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Internal Process.

Electronic or other method, as agreed.

3.10.15

Within 5 WD of 3.10.13

Notify BSCCo of all MSID(s) which are part of Exemptable Generating Plant.

Supplier

BSCCo

List of MSID(s).

Fax/ Email

3.11 Instruction Processing

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

3.11.1

On receipt of file.

Perform validation checks.

DA.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Internal Process.

3.11.2

If validation successful.

Update database with instruction data.

DA.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Internal Process.

3.11.3

If validation unsuccessful.

Notify SMRA of problem.

DA.

SMRA.

P0035 Invalid Data (for transmission problems).

D0023 Failed Instructions (for instruction level validation problems).

Electronic or other method, as agreed.

3.11.4

Upon receipt of failure notification.

If transmission problem, resend exact copy of instruction file (with same file sequence number).

SMRA.

DA, Supplier.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

Electronic or other method, as agreed.

If file validation problem, generate and send refresh file (and advise DA of file sequence number).

DA, Supplier.

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

If problem caused by fault on SMRA’s system, resolve failure and generate and send revised file containing all instructions required to rectify the situation (and advise DA of file sequence number).

DA, Supplier

D0209 Instruction(s) to Non Half Hourly or Half Hourly Data Aggregator.

If problem believed to be caused by DA, notify DA and Supplier.

DA, Supplier

As appropriate.

If unable to resolve failure, notify Supplier.

Supplier

As appropriate.

If problem caused by fault on Managed Data Network, treat failure as request for Resend in accordance with section 3.8.

See section 3.8.

4. Appendices

4.1 This page has intentionally been left blank

4.2 Erroneous Registrations

4.2.1 General principle

The “Old Supplier” should not dismiss his Agents (i.e. Data Collector, Data Aggregator and SVA Meter Operator Agent) until the “Old Supplier” has received confirmation from SMRA that there is a “New Supplier” in place.

4.2.2 Scope

This section considers erroneous Registrations which are agreed by both Suppliers as being made in error. Where there is a dispute, the Suppliers may either use the REC disputes process, or seek redress through legal proceedings.

4.2.3 Identification of Registration Error

The identification of Registration errors falls into two distinct “time slots”:

identification by either Supplier:

(a) within the objection period;

(b) after the objection period.

4.2.4 Rectification of Registration Error

Time slot (a): Old Supplier raises objection through SMRA. If the New Supplier identifies the error, then the New Supplier should contact the Old Supplier and request that the Old Supplier lodges an objection with SMRA. (Table 4.2.5)

Time slot (b): Old Supplier re-registers as soon as practicable. If the New Supplier identifies the error, then the New Supplier should contact the Old Supplier and request the Old Supplier to re-register. (Table 4.2.6)

4.2.5 Registration Error detected within objection period

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

4.2.5.1

On detection of error within objection period.

Contact other Supplier and agree Registration is in error.

Supplier.

Other Supplier.

MSID.

Telephone or Fax.

4.2.5.2

On joint agreement that error exists and within objection period.

Register objection.

Old Supplier.

SMRA.

D0064 Notification of an Objection to Change of Supplier Made By the Old Supplier.

Electronic or other method, as agreed.

4.2.6 Registration Error detected after objection period

REF.

WHEN

ACTION

FROM

TO

INFORMATION REQUIRED

METHOD

4.2.6.1

On detection of error (if after objection period).

Contact other Supplier and agree Registration is in error.

Agree re-registration date (new SSD).

Supplier.

Other Supplier.

MSID.

Proposed new SSD.

Telephone or Fax.

4.2.6.2

As soon as practicable after end of lock-out period +1 WD.

Re-register MSID with agreed SSD.

Old Supplier.

SMRA.

D005511 Registration of Supplier to Specified Metering Point.

Electronic or other method, as agreed.

4.3 Data Validation

The SMRS must validate all BSCCo Required Data submitted before accepting or rejecting the data.

Upon rejection of data, the SMRA shall set out all the reasons for rejection to the sending market participant.

The SMRA shall ensure that all data for SVA Metering Systems conform with the rules outlined in the following table.

Property

Non Half Hourly

Half Hourly

Profile Class

Valid Profile Class (as specified in MDD) required

Profile Class not required

Standard Settlement Configuration

Valid Standard Settlement Configuration (as specified in MDD) required

Standard Settlement Configuration not required

Data Aggregator Appointment

Data Aggregator required to be specified as non half hourly in MDD

Data Aggregator required to be specified as half hourly in MDD

Data Collector Appointment

Data Collector required to be specified as non half hourly in MDD

Data Collector required to be specified as half hourly in MDD

LLF Class Id

Valid LLF Class Id (as specified in MDD) required.

Valid LLF Class Id (as specified in MDD) required.

MOA Appointments for Unmetered Supplies

Unmetered Supply Operator to be specified (from a list of Unmetered Supply Operators in MDD), in place of the SVA MOA, in the SVA MOA field to ensure a valid Unmetered Supplies Operator is appointed.

Appropriate ‘Measurement Class’ has been recorded for Non Half Hourly Unmetered Supplies

Meter Administrator to be specified (from a list of Meter Administrators in MDD), in place of the SVA MOA, in the SVA MOA field to ensure a valid Meter Administrator is appointed.

Appropriate ‘Measurement Class’ has been recorded for Half Hourly Unmetered Supplies

Please note that during the registration process for Non Half Hourly or Half Hourly Unmetered Supplies, the MOA field containing the UMSO/MA MPID is dependent on the Measurement Class field of the registration flow. Therefore if a change is made to the Measurement Class, it should be accompanied by a change in the SVA MOA field (e.g. if the Measurement Class changes from Non Half Hourly UMS to Half Hourly Unmetered Supply, this should mean a change of agent e.g. UMSO to MA).

For any particular event, the SMRA shall apply one or more of the following validation criteria as appropriate:

• Data will only be accepted from the market participant that is the source of the data as defined in Section 3 of this document;

• Upon receipt of a change to the data within SMRS, SMRA shall validate that any of the following codes involved in the change are valid (in accordance with the Market Domain Data) on the effective date of the change:

- Data Aggregator Id

- Data Collector Id

- Energisation Status

- GSP Group Id

- Line Loss Class Id

- Measurement Class Id

- Meter Operator Id

- Profile Class Id

- Supplier Id

- Standard Settlement Configuration Id

• Upon receipt, from a Supplier, of changes to Metering System Registration Data the SMRA shall validate that the Supplier is liable for the SVA Metering System on the effective date of the change;

    • Upon receipt of changes to Meter Information Data or Meter Asset Provider from a SVA Meter Operator Agent, the SMRA shall validate that the SVA Meter Operator Agent is appointed for the SVA Metering System on the effective date of the change.

• The SMRA shall validate that the Line Loss Factor Class provided by the LDSO for an MSID is a valid Line Loss Factor Class for that LDSO as provided by the SVAA as MDDM;

• Upon receipt from a LDSO, of changes to Metering System Registration Data, the SMRA shall validate that the LDSO is the SVA Metering System’s LDSO as determined from the SVA Metering System Identifier;

• Upon receipt of creation details for a new SVA Metering System from the LDSO, the SMRA shall validate that SVA Metering System identifier contains the correct Distributor Id and does not already exist.

• Upon receipt of a Registration from a Supplier, SMRA will validate that the SVA Metering System identifier exists.

• Upon a change of Profile Class and / or Standard Settlement Configuration, the SMRA shall validate that the resulting combination of Profile Class and Standard Settlement Configuration are valid in the SVA Metering System’s GSP Group on the effective date of the change, as specified by the Average Fraction of Yearly Consumption Set data provided by the SVAA as part of Market Domain Data.

• An existing SVA Metering System, may only be registered for supply if, in respect of the SVA Metering System being registered:

- the LDSO has provided all the relevant data for which it is the source; and

- all the data for which the Supplier is the source have been provided.

- where the 1998 Trading Arrangement Indicator has been set to ‘Y’.

• A new SVA Metering System where the Energisation Status has not yet been provided, may be registered for future supply if, in respect of the SVA Metering System being registered:

- the LDSO has provided the MSID, GSP Group Id; and

- the Supplier has provided the MSID, Supply Start Date;

- and the 1998 Trading Arrangement Indicator has not been set to ‘N’.

then, prior to the Energisation Status being set to “energised” or “de-energised”, the SMRA shall validate that:

- the LDSO has provided all the relevant data for which it is the source; and

- the Supplier has provided all the relevant data for which it is the source.

• A SVA Metering System that has been disconnected i.e. has a Disconnection Date, may not be registered for dates after the disconnection date.

Where the SMRA has rules used in validating notifications to the SMRS which are additional to those specified in this BSCP, the SMRA shall declare them to the relevant Supplier and DA and shall only change these additional rules in accordance with the procedures specified in the REC.

4.4 Contact Notice Facility

The SMRA shall provide a Contact Notice Facility in accordance with this Appendix 4.4.

The SMRA shall make the Contact Notice Facility available in the following circumstances:

• The Old or New Supplier, in relation to the current or pending registration for a particular MSID, reasonably believes that the New Supplier has been erroneously registered for that MSID;

• The Old Supplier in relation to the current registration wishes to assign to the New Supplier a debt owing to it by a Customer at Domestic Premises in accordance with the Old Supplier’s Supply Licence;

• The Old or New Supplier in relation to the current or pending registration reasonably believes that the New Supplier applied to register an MSID which is a Related MSID without applying to register all the relevant Related MSIDs at the same time; and/or

• The Old Supplier makes a change to one of the data items for which it is stated to be responsible in the SVA Data Catalogue, in relation to a MSID, and its instruction to the relevant SMRA is rejected and the reason for such rejection is stated to be the New Supplier’s registration.

Where the SMRA receives more than 50 requests for the Contact Notice Facility on any Working Day and the SMRA cannot receive requests via the Managed Data Network (other than as a result of a failure of the Managed Data Network), the SMRA shall use reasonable endeavours to provide as many Contact Notices as possible but shall only be required to provide 50 Contact Notices using the following allocation:

• A maximum of five per Supplier allocated in the order that the requests are received;

• Where the above rule has been complied with, any extra Contact Notices which have been requested shall be provided in the order in which they have been requested; and

• Any extra Contact Notices in excess of 50 requested in any Working Day or received after 15:00 hours on a Working Day, which the SMRA has not provided, shall be deemed to have been the first requested at the start of the next Working Day.

4.5 Refreshes

Where BSCCo or the Performance Assurance Board (PAB) instructs a NHHDA to request a Full Refresh, the SMRA shall send, in instruction format, a Full Refresh containing all relevant data covering those Settlement dates for which a Final Reconciliation Run has not yet taken place at the time the Full Refresh is generated.

For Selective Refreshes, or additional Full Refreshes initiated by mutual agreement between the SMRA and the Data Aggregator, a shorter Settlement period may apply.

Where an SMRA receives more than 50 requests for a Selective Refresh on any Working Day, the SMRA shall use reasonable endeavours to provide as many Selective Refreshes as possible but shall only be required to provide 50 Selective Refreshes using the following allocation:

• A maximum of five per Supplier or Data Aggregator allocated in the order that the requests are received;

• Where the above rule has been complied with, any extra Selective Refreshes which have been requested shall be provided in the order in which they have been requested; and

• Any extra Selective Refreshes in excess of 50 requested in any Working Day or received after 15:00 hours on a Working Day, which the SMRA has not provided, shall be deemed to have been the first requested at the start of the next Working Day.

Where an SMRA receives more than 3 requests for a Full Refresh within a 5 Working Day period, the SMRA shall use its reasonable endeavours to provide as many Full Refreshes as possible, but shall only be required to provide Full Refreshes in response to the first 3 requests received during that 5 Working Day period within 15 Working Days of the request. Any further requests received during that 5 Working Day period shall be deemed to have been received on the fifth Working Day after the receipt of the first request.

4.6 Resends

Where the SMRA receives more than 50 requests for a Resend on any Working Day, the SMRA shall use reasonable endeavours to provide as many Resends as possible but shall only be required to provide 50 Resends using the following allocation:

• A maximum of five per Supplier or Data Aggregator allocated in the order that the requests are received;

• Where the above rule has been complied with, any extra Resends which have been requested shall be provided in the order in which they have been requested; and

• Any extra Resends in excess of 50 requested in any Working Day or received after 15:00 hours on a Working Day, which the SMRA has not provided, shall be deemed to have been the first requested at the start of the next Working Day.

4.7 Service Level Performance Standards

Serial

Sender

Process

Sub-Process

Recipient

Performance Measure

Service Levels

Reporting Method

SP07

SMRA

1.6 Service Availability and Service Levels

SMRA & SVAA MSID Count – SMRA File

N/A

SMRA/SVAA MSID Count Comparison between SMRA and SVAA files

SMRA MSID Count

Provision of data under 1.6

1 For the avoidance of doubt, the SMRA can fulfil this obligation by an automatic acknowledgement of receipt sent by the SMRA’s Managed Data Network gateway

2 The SMRA shall maintain a history of change.

3 If updating Metering Point Address and/or Metering Point Postcode refer to the timescale as defined in the REC.

4 LLF Class Id will contain the actual LLF Class Id and not a default LLF Class Id. However, it is recognised that the default LLF Class Id may be the same in which case no change will occur.

5 If this is a Transfer of Registration to CMRS, the Disconnection Date shall be one day before the Effective From Date in BSCP68, Section 3.1.

6 Where a bulk change of agent is being initiated, BSCP513 must have been completed prior to triggering this process. Updates to the SMRS Database resulting from a bulk change of agent will be conducted without adversely impacting the SMRA’s normal daily operations.

7 The SMRA System must not preclude changes made by a Supplier before the Final Reconciliation Volume Allocation Run.

8 If the effective date of the change is before the current effective date contained in the SMRS, the Supplier will determine whether or not to correct the error as required by the BSC.

9 The timeframe provided is intended to apply to noted sections of BSCP520, and changes to 3.3.1 should be reflected there.

10 When registering a Supplier-serviced Metering System, the Supplier must ensure that the Meter Operator Id (J0178) is for their appointed SVA MOA, and that the value for Meter Operator Type (J0675) is valid in SMRS for the Measurement Class.

11 For notifications received before 18:00 on a Working Day, SMRA will reply by 06:00 on the next Working Day.

12 All continuous preceding NHHDAs that were appointed for the current Supplier Registration, in the previous 15 months of the current Supplier Registration, prior to the change.

13 Providing that the registration is received by 1800 on SSD.

14 For notifications received before 18:00 on a Working Day, SMRA will reply and notify by 06:00 on the next Working Day.

15 For notifications received before 18:00 on a Working Day, SMRA will notify by 06:00 on the next Working Day.

16 The SMRA shall provide a Contact Notice Facility in accordance with Appendix 4.4 and shall not provide automatic disclosure of the New Supplier’s identity.

17 This table applies to Non-Half Hourly Data Aggregation with effect from 1 April 2000.

18 Where an approved bulk change of agent affects the Non Half Hourly Data Aggregator, this process will be completed without adversely impacting normal daily operations.

19 For notifications received before 18:00 on a Working Day, SMRA will notify by 06:00 on the next Working Day.

20 Where the new connection is a Metering System which is associated with Exemptable Generating Plant and where the Export Meter(s) is Registered in CMRS, refer to section 3.10 ‘New Connection for Metering System which is associated with Exemptable Generating Plant and where the Export Meter(s) is Registered in CMRS’.

21 LLF Class Id will contain the actual LLF Class Id or where this is not known a default LLF Class Id.

22 If a Registration Transfer from CMRS, the Supply Start Date will be the “Effective From Date” defined in BSCP68, Section 3.2.

23 Agent Ids (DA/DC) and other marked items are not mandatory for a Supplier to register liability whilst the Energisation Status has not yet been provided.

24 For notifications received before 18:00 on a Working Day, SMRA will notify by 06:00 on the next Working Day.

25 For notifications received before 18:00 on a Working Day, SMRA will reply and notify by 06:00 on the next Working Day.

26 For notifications received before 18:00 on a Working Day, SMRA will notify by 06:00 on the next Working Day.

27 The SMRA shall provide a Contact Notice Facility and shall not provide automatic disclosure of the New Supplier’s identity.

28 A Full Refresh includes SMRS data for all the GSP Groups relevant to the DA’s activities.

29 If request for Refresh is refused, (e.g. for an MSID not registered on the SMRS), then the SMRA shall notify the applicant within 1 WD of request. The notification shall state the reason for the refusal.

30 For notifications received before 15:00 on a Working Day, the SMRA will reply by 06:00 on the next Working Day subject to a maximum of 50 per day. Where the SMRA receives more than 50 notifications on any Working Day, the SMRA shall process these notifications in accordance with Appendix 4.5

31 For notifications received before 15:00 on a Working Day, the SMRA will reply by 06:00 on the next Working Day subject to a maximum of 50 per day. Where the SMRA receives more than 50 notifications on any Working Day, the SMRA shall process these notifications in accordance with Appendix 4.6

32 If request for Resend is refused, (e.g. for message more than 28 Days old), then the SMRA shall notify the applicant within 1 WD of request. The notification shall state the reason for the refusal.

33 Note that a physical Disconnection will not occur where this process is used in conjunction with BSCP68 for a Registration transfer to CMRS.

34 Once recorded, the SMRA shall not remove any MSID from the SMRA System until two years after the Disconnection Date of that MSID (as notified to the SMRA by the LDSO).

35 Where the new connection is not associated with an Exemptable Generating Plant with the Export Meter(s) registered in CMRS, refer to section 3.6 ‘New Connection for SVA Metering System’.

36 Note that EFSD {REGI} is determined in 3.10.1 and cannot be changed via D0205

37 For notifications received before 18:00 on a Working Day, SMRA will notify by 06:00 on the next Working Day.