Synopsis

This document describes the user requirements for the Central Registration Agent (CRA) service.

Version

Version 24.0

Effective date

02 April 2024

Prepared by

Design Authority

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.

28/01/10

15.0

Issued

23/02/12

16.0

Document rebadged and amended for February 2012 Release (P268 & P269)

ISG130/08

25/06/15

17.0

Modification P310; June 2015 Release

ISG169/05

23/02/17

18.0

CP1471

ISG185/03

P326 Self-Governance

ISG188/05, ISG191/01

29/06/17

19.0

P350 for the June 17 Release

ISG194/02

28/02/19

20.0

P344 – February 2019 Release

P284C/01

CP1510 – February 2019 Release

ISG211/06

SVG214/02

P359 – February 2019 Release

ISG212/03

29/03/19

21.0

P369 – March 2019 Standalone Release

P285/12

27/02/20

22.0

P394 February 2020 Release – Self-Governance

P297/07

01/09/21

23.0

P420 – 1 September 2021 Non-Standard Release

P316/05

CRA SD

Service Description for Central Registration Agent (NETA Programme)

TAA SD

Service Description for Technical Assurance Agent (NETA Programme)

CDCA SD

Service Description for Central Data Collection Agent (NETA Programme)

SAA SD

Service Description for Settlement Agent (NETA Programme)

CRA BPM

RETA Business Process Models [CRA] - (NETA Programme)

NETA SCH

NETA Service Agreement (NETA Programme)

CRAWS

CRA Workshop held on 01/02/2000

DID-2

Data Items Definition Design Clarification version 2 (NETA Programme) 17/02/2000

PPR

Program Progress Report (01/03/2000)

IDD

Interface Definition and Design (Parts 1 & 2)

Bank

A bank that receives debit and credit instructions from the Funds Administration Agent.

BMRA

Balancing Mechanism Reporting Agent.

BSC Party

Any user of Balancing and Settlement Code services.

BSCCo Ltd

The Balancing and Settlement Code Company.

CDCA

Central Data Collection Agent.

CRA

Central Registration Agent (including the Self-Service Gateway)

Credit Agency

A credit agency that provides credit cover data on Parties.

ECVAA

Energy Contract Volume Aggregation Agent.

ECVNA

Energy Contract Volume Notification Agent.

FAA

Funds Administration Agent.

IA

Interconnector Administrator.

IEA

Interconnector Error Administrator

Meter

A physical meter registered within the Balancing and Settlement Code arrangements.

MIDP

Market Index Data Provider

CVA MOA

Central Volume Allocation Meter Operation Agent.

MVRNA

Metered Volume Reallocation Notifications Agent

NETSO

National Electricity Transmission System Operator

Public

A member of the general public.

SAA

Settlement Administration Agent.

SVAA

Supplier Volume Aggregation Agent

TAA

Technical Assurance Agent.

Transfer Coordinator

A role undertaken by BSCCo Ltd to coordinate transfers of metering between CVA (CRA & CDCA) and SVA in order to address the risk that Metering Systems are ‘double counted’ or ‘omitted’ from Settlements’.

Requirement ID:

CRA-F001

Status:

Mandatory

Title:

Register BSC Party

BSC Reference:

CRA SD 4.1, CRA SD 4.2, CRA SD 4.3, CRABPM 3.1, CRAWS -20, CR_18_990909, P197

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Mostly at initial set-up

Functional Requirement:

The CRA shall allow an Operator or authorised Self-Service Gateway user to manually enter new BSC Party Registration Information into the CRA system.

The CRA system shall recognise a set of BSC Party types including (and not exclusively):

a) Transmission Owner,

b) NETSO,

c) Distribution Company,

d) Interconnector Administrator,

e) Trading Party

f) Interconnector Error Administrator (Note: These will be associated with pseudo-BM Units and will have Energy Accounts)

g) Virtual Lead Party

In addition, Trading Parties may have one or more of the following roles:

i) Generator

ii) Supplier

iii) Trader (Non Physical)

iv) Interconnector User

Each of the Party types and roles allow for a different set of registration requests to be processed by the system. (For instance a non-physical Trader should not in the main be allowed to register Interconnectors). Where an attempt is made and is not expected according to role, the CRA shall flag a warning. The following table illustrates these relationships.

These registration requests shall subsequently be received by the CRA in accordance with the other requirements in this specification. None of these later requests shall be processed until the initial BSC Party Registration has been completed.

The BSC Party shall submit registration information to the CRA system including details of:

• An Action Description to specify the type of registration operation,

• the Party (name, contact details),

• the Party’s Stage 2 Names (where they exist).

• authorised signatories and individual contact details,

• settlement report distribution requirements,

• Party Agents that the Party shall use,

A detailed description of the interface content may be found in CRA-I001.

Along with the details of the registration request from the BSC Party, the CRA shall receive supporting information from BSCCo Ltd (via the Self-Service Gateway, as applicable). BSC Parties shall not be able to complete registration with the CRA before they have completed Qualification Processes. CRA will receive authorisation from BSCCo Ltd to register a particular party.

The input data shall be validated in accordance with the following rules:

1) The Party Types associated with the BSC Party Registration are valid according to the valid set of Party type standing data,

2) Each Interconnector that is used by the BSC Party conforms to a valid Interconnector ID stored within the system.

3) Where a BSC Party states a change to the usage of an Interconnector that these details match those received from the Interconnector Administrator (both in usage type and effective to and from dates).

4) That where the BSC Party is the Interconnector Error Administrator for an Interconnector, the details match those received from the Interconnector Administrator registration details (both in responsibility and effective to and from dates).

5) That the Party Agents that the Party shall use are registered for the period of the registration request.

6) That there is at least one authorised signatory sent to the CRA.

Where the data has passed validation the information shall be stored within the CRA system database after being authorised by a Supervisor. Any authentication details (authorised signatories) referenced within the message shall be stored according to the requirements of CRA-F002. The CRA system shall then allocate and return to the Operator a meaningful and unique BSC Party ID and two energy account identifiers (derived from the BSC Party ID) in accordance with CRA-F004 and CRA-F005.

The CRA system shall also provide the BSC Party with sufficient information for the authentication of future communications, electronic or otherwise.

Where the BSC Party is of a type “Supplier” the CRA system shall trigger the registration of one BM Unit registration request for each GSP group in accordance with the requirements of CRA-F013.

Non Functional Requirement:

Interfaces:

Input interfaces:

CRA-I001

Output Interfaces:

CRA-I014

CRA-I015

CRA-I013

CRA-I012

Requirement ID:

CRA-F002

Status:

Mandatory

Title:

Maintain Authentication Data

BSC Reference:

CRA BPM 3.1, CRA SD 4.2.2, CRA SD 4.1.7, CRAWS-21, CP756 CP1193

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low, a few 10’s per month after initial set-up.

Functional Requirement:

The CRA shall allow an Operator to enter and maintain authentication data against which incoming BSC party registration requests may be authenticated. The CRA will also obtain and maintain authentication information from BSCCo Ltd nominated signatories.

The authentication details (authorised signatory, password and optionally an e-mail address) will be stored within the system against the BSC Party along with the authentication key for the BSC Party.

Where the password for an authorised signatory is changed, the old password must be entered correctly in order for the update to take place. Only if the current password is entered correctly will the new password be accepted. The new password will then be effective for all authentication processes from the date and time at which the update was accepted.

In the special case where a BSC Party has no current authorised signatories, the first entrant shall be accepted without confirmation checks. Validation that this signatory’s name and password is correct shall be a manual process according to CRA-F001.

The new authentication details shall be distributed to the BSCCO, FAA, ECVAA and SAA systems according to the distribute register data requirement (CRA-I013) by 5.00pm on the day of update or additionally as necessary.

Where the Self-Service Gateway is used and the relevant operation is supported by the Self-Service Gateway, Role-Based Access Control (RBAC) will be used to authenticate online requests.

Non Functional Requirement:

Interfaces:

Output Interfaces:

CRA-I013

Requirement ID:

CRA-F003

Status:

Mandatory

Title:

Authenticate Party

BSC Reference:

CRA BPM 3.1, CRA SD 4.1, CP756

Man/Auto:

Automatic/ Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall perform authentication validation between authentication data contained on incoming registration requests against that held within the system. The system authentication data will have been entered previously through process CRA-F002.

The authentication check shall consist of validating the password of the authorised signatory against that held within the system.

Where the request is received via e-mail, the authentication check will validate the password and the sender’s e-mail address against those held within the system for the authorised signatory. A request received via e-mail can only be authenticated if the signatory has a registered password.

The success / failure of all authentication checks will be maintained within the system along with the date and time of the request.

Where the Self-Service Gateway is used and the relevant operation is supported by the Self-Service Gateway, Role-Based Access Control (RBAC) will be used to authenticate online requests.

Non Functional Requirement:

Interfaces:

Requirement ID:

CRA-F004

Status:

Mandatory

Title:

Allocate BSC Party ID

BSC Reference:

CRA BPM 3.1, CRA SD 4.1.2, CRAWS-24

Man/Auto:

Automatic

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall, on receipt of a new BSC Party Registration request, create a unique and meaningful party identifier irrespective of role. Self-Service Gateway users may choose their own identifier.

The CRA system shall perform a check against the name of the BSC Party and currently stored BSC Parties.

To avoid errors of duplication, should a potential duplicate BSC Party name be found, the system will issue a warning which must be overridden prior to allocation of a new identifier.

Non Functional Requirement:

Interfaces:

Requirement ID:

CRA-F005

Status:

Mandatory

Title:

Allocate BSC Party Energy Account

BSC Reference:

CRA BPM 3.1, CRA SD 4.1.2, CRAWS-25

Man/Auto:

Automatic

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall, on request, allocate energy account identifiers for a BSC Party. Two energy accounts must be allocated to any individual BSC Party (one for production, one for consumption), with the exception of Virtual Lead Parties who will be allocated a single Virtual Balancing Account. A standard convention will be used for identification of the account based upon the BSC Party Identifier. The effective start date of the energy account shall be provided to the CRA system and stored against the accounts.

Non Functional Requirement:

Interfaces:

Requirement ID:

CRA-F006

Status:

Mandatory

Title:

View / Maintain BSC Party Registration Details

BSC Reference:

CRA BPM 3.1, CRA SD 4.1.1, CRAWS-20, CRAWS-26, CP508

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low, expected rate to be a few 10’s per month.

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator of the system to view and amend the details of a BSC Party. Self-Service Gateway users shall be allowed to view and amend details of their own BSC Party. The CRA shall allow a BSC Party to change any part of its registration information as specified in CRA-I001 and CRA-F001.

In addition, the system shall provide functionality for the de-registering of a BSC Party in accordance with the specific functionality detailed in the deregistration requirement below:

The system shall validate the authentication details (signatory and password) contained within the message against those held currently against the BSC Party in accordance with requirement CRA-F004.

The input data shall be validated in accordance with the following rules:

1) Any change to the Party Types associated with the BSC Party Registration are valid according to the valid set of Party type standing data,

2) Any Interconnector usage specified by the BSC Party references a valid Interconnector ID stored within the system.

3) Where a BSC Party states a change to the usage of an Interconnector that these details match those received from the Interconnector Administrator (both in usage type and effective to and from dates).

Changes, addition or amendment to authorisation data, shall be handled according to the requirements in CRA-F002.

Viewing of certain information, such as the authentication details for the Party, may be restricted to authorised personnel only.

BSC Party information may not be physically deleted from the system, it may only be logically deleted.

Registration changes relating to participant capacity or authorised person shall be confirmed by BSCCo Ltd in order to ensure that the new registration details are valid and are consistent with the current status of the BSC Party. This confirmation shall be submitted via a CRA-I001 flow from BSCCo Ltd containing the change. The registration changes requiring this confirmation are:

• Add new party role

• Change party role effective dates

• Change Stage 2 participant details

• Add, remove authorised signatory

• Add authorisation level

• Change effective dates on authorisation level

• Changes Interconnector Administration details

Other registration changes do not require confirmation by BSCCo Ltd.

Deregistration of BSC Party

In the special case where a BSC Party is de-registered, the CRA system shall check the validity of the termination request by ensuring that all sub-ordinate registrations for the Party (such as BM Units) have been de-registered prior to the request. Where this has not occurred, the CRA system shall inform the Operator of the fact and await confirmation of action.

The CRA shall require the explicit prior approval of the deregistration from BSCCo Ltd.

Non Functional Requirement:

If the Party sends a “CRA-I001 Receive BSC Party Registration Data” flow to CRA which requires authorisation by BSCCo Ltd as described above, then CRA will forward this directly to BSCCo Ltd. (Note: once the data has been forwarded to BSCCo Ltd, the flow processing has been completed. If BSCCo Ltd approve the change then BSCCo Ltd will submit a CRA-I001 to CRA containing the approved changes). The approval process will be carried out using the Self-Service Gateway, where applicable.

Interfaces:

Input interfaces:

CRA-I001

Output Interfaces triggered from this action:

CRA-I014

CRA-I015

CRA-I013

CRA-I028

Requirement ID:

CRA-F007

Status:

Mandatory

Title:

Register Interconnector Administrator

BSC Reference:

CRA SD 4.1.3, CRAWS-20, CRAWS-27, CRAWS-28

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA shall allow an Operator or Self-Service Gateway user to enter registration details for an Interconnector Administrator. The details shall consist of:

• An Action Description

• Interconnector Administrator Identification and Authentication Data

• Contact Details

• Interconnector Details

• Interconnector Error Administrator Details

A detailed description may be found in the requirements for CRA-I002.

The CRA system shall validate incoming data according to the following rules:

1) That each of the Interconnectors specified in the details are registered within the system,

2) That no other Interconnector Administrator is assigned to the Interconnector.

Where an Interconnector Administrator is already specified for the Interconnector, the system shall only allow the request to proceed if the effective from date of the new Interconnector Administrator matches the effective to date of the currently stored record.

Where data is registered in respect of an Interconnector Error Administrator, the CRA shall require the explicit authorisation of BSCCo Ltd. The approval process will be carried out using the Self-Service Gateway, where applicable.

The CRA system shall accept registration requests as per CRA-I002 where no Interconnector Error Administrator is specified on initial registration. This condition will be reported to the Operator for confirmation on entry and subsequently reported in accordance with the requirements of CRA-F023. Assignment of an Interconnector Error Administrator may then be conducted at a later time through CRA-F008.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I002

Output Interfaces triggered from this action:

CRA-I014

CRA-I015

CRA-I019

CRA-I020

Requirement ID:

CRA-F008

Status:

Mandatory

Title:

View / Maintain Interconnector Administrator Data

BSC Reference:

CRA SD 4.1.3, CRAWS-29

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to view / amend the details of an Interconnector Administrator registration.

The CRA system shall allow the Interconnector Administrator to change any details of the registration. The CRA will be sent any changes, including:

• An Action Description

• Interconnector Administrator Identification and Authentication Data

• Contact Details

• Interconnector Details

• Interconnector Error Administrator Details

A detailed description can be found in the requirements for CRA-I002.

Where the details state that the Interconnector Administrator is ceasing registration of the role, it is the responsibility of the Operator to ensure that this obligation has the agreement of BSCCo Ltd. This shall be conducted by review of supporting documentation from BSCCo Ltd and the fact that this check has been conducted shall be enterable against the transaction. The system shall then prompt the Operator to register the new Interconnector Administrator (through CRA-F007). If this cannot be entered, the fact that the Interconnector has no Administrator shall be flagged through CRA-F023 daily while this situation persists.

Where data is sent concerning a change of Interconnector Error Administrator, the data provided from the Interconnector Administrator shall require the explicit authorisation of BSCCo Ltd. The approval process will be carried out using the Self-Service Gateway, where applicable.

Non Functional Requirement:

Interfaces:

Requirement ID:

CRA-F009

Status:

Mandatory

Title:

Register BSC Party Agent

BSC Reference:

CRA SD 4.2, CRA SD 5, CRA BPM 3.5, CRAWS-30, P197

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low, Few 10’s per month

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to enter the registration details for a BSC Party Agent.

The range of valid BSC Party Agent types shall be defined as (not exclusively):

a) Energy Contract Volume Notification Agents,

b) Metered Volume Reallocation Notification Agents

c) Half Hourly Data Collector Agents

d) Half Hourly Data Aggregator Agents

e) Non Half Hourly Data Collector Agents

f) Non Half Hourly Data Aggregator Agents

g) Meter Administration Agent

h) Supplier Meter Administration Agent

i) CVA Meter Operator Agents

The CRA shall receive the following information from BSCCo Ltd:

• Authentication Details

• BSC Party Agent Details

• Individual Authorisation Details and signatories

• Certification /Accreditation Details³

Full details of the flow may be found in CRA-I003.

It is expected that the initial Registration from BSCCo Ltd may consist of only the BSC Party Agent Details and Qualification Details. The remainder of the registration details (such as Authorised Signatories) would be sent later by either the BSC Party Agent or BSCCo Ltd.

It shall be the responsibility of an operator of the CRA system to validate the following data against paper documentation:

1) That the BSC Party Agent has been registered with BSCCo Ltd,

2) That the BSC Party Agent has been Qualified.

Confirmation that each of these checks has been conducted shall be enterable into the CRA system alongside the entering Operator’s identification details.

The system shall store the authentication data contained in the flow according to the requirements of CRA-F002.

The CRA shall only accept a registration where the BSC Party Agent has a valid Qualification status (where applicable). Where the Qualification status is not valid, the details may be entered into the system though the BSC Party Agent will not be regarded as Registered. The Qualification status may subsequently be amended through the View / Maintain BSC Party Agent Registration requirement, at which point the Registration of the Agent will be completed.

On successful registration of the BSC Party Agent, a report detailing the BSC Party Agent, Registration, and Qualification Details shall be triggered. (CRA-I024)

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I003

Output interfaces:

CRA-I013

CRA-I014

CRA-I024

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to view and maintain BSC Party Agent details.

The BSC Party Agent Registration amendment will concern elements of the following data:

• Authentication Details

• BSC Party Agent Details

• Individual Authorisation Details and signatories

• Certification/Accreditation Details⁴

Full details of the flow may be found in CRA-I003.

The system shall validate that:

1) In the case where the amendment is to de-register an ECVNA or MVRNA, that the agent has no authorisations registered with ECVAA beyond the agent termination date. This communication is described by the requirements CRA-I036 and CRA-I037.

The system shall allow for the amendment of the Qualification and registration details as well as the details concerning the BSC Party Agent itself (such as address and contact data).

The CRA shall provide a mechanism for the management and storage of re-Qualification data where re-Qualification becomes necessary.

Where the registration update is to de-register a BSC Party Agent, the system shall inform all BSC Parties that have specified a use of the Agent. Affected Parties will continue to be flagged in the CRA system through CRA-F023.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I003

Output interfaces triggered from this activity:

CRA-I013

CRA-I014

CRA-I024

ECVAA Validation interfaces:

CRA-I036

CRA-I037

Requirement ID:

CRA-F011

Status:

Mandatory

Title:

Register BSC Service Agent

BSC Reference:

CRA SD 4.3, CRAWS-31, P82, P197

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to enter the registration details for the following BSC Service Agents, operating under the direct control of BSCCo Ltd. The list shall include:

1) Supplier Technical Assurance Agent

2) Supplier Teleswitch Support Agent

3) Supplier Volume Aggregation Agent

4) Settlement Administration Agent

5) Balancing Mechanism Reporting Agent

6) Energy Contract Volume Aggregation Agent

7) Funds Administration Agent

8) Supplier Volume Allocation Agent

9) Central Data Collection Agent

10) Central Registration Agent

The following information concerning the Service Agent is supplied by BSCCo Ltd:

• Name

• Type

• Contact Details

Full details of the interface may be found in CRA-I004.

The system shall validate that:

1) The name entered against the Service Agent is not already contained within the database.

2) The Agent Type is compliant with one of the agent types described above.

It shall be the responsibility of an Operator of the CRA system to validate the following data against paper documentation:

• That the BSC Service Agent has been registered with BSCCo Ltd

Non Functional Requirement:

Interfaces:

Input Interfaces:

CR-I004

Output Interfaces triggered by this activity:

CR-I013

CR-I014

CR-I021

Requirement ID:

CRA-F012

Status:

Optional

Title:

View / Maintain BSC Service Agent

BSC Reference:

CRA SD 4.3, CRAWS-31

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall allow a Self-Service user or an Operator to view and maintain BSC Service Agent details.

The following information is presented from BSCCo Ltd concerning the Service Agent:

• Name

• Type

• Contact Details

Any change to the BSC Service Agent details that results in a change of the registration state shall trigger the production of a registration report.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CR-I004

Output Interfaces triggered by this activity:

CR-I013

CR-I014

CR-I020

CR-I021

Requirement ID:

CRA-F013

Status:

Mandatory

Title:

BM Unit Registration

BSC Reference:

CRA SD 6.1, CRA BPM 3.2, NGC VAL 3.0, CRAWS-32, DID-2, CP753, CP775, P100, P215, P268, P269

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall allow a Self-Service user or an Operator to enter details of a BM Unit registration into the system. BM Units may be of 6 principal (though not exclusively limited to these) types:

i) Directly Connected BM Unit

ii) Supplier BM Unit (Base and Additional)

iii) Embedded site within GSP Group

iv) Interconnector Error Administrator BM Unit

v) Interconnector User BM Unit

vi) Secondary BM Unit

With the exception of Secondary BM units, only Trading Parties should in the main be allowed to register BM Units though other Parties shall be allowed to register them, as per CRA-N001. Only Virtual Lead Parties may register a Secondary BM Unit.

BM Units are related to GSP Groups, Interconnectors and Boundary Points dependent upon the type of the BM Unit. The CRA system shall maintain the relationship between a BM Unit and either a GSP Group or Interconnector, but not a Boundary Point. The following table illustrates which BM Unit types require an association to a GSP Group / Interconnector to be specified.

A BM Unit registration request shall contain the following information:

• An Action Description

• The BM Unit Registration Details (including type, production / consumption flag and whether an NETSO defined name is contained within the flow)

• Generation Capacity and Demand Capacity (not required for Secondary BM Units)

• Details of the GSP group associated with the BM Unit (if appropriate)

• Details of the Interconnector associated with the BM Unit (if appropriate)

• Mapping Details defining the relationships between SVA MSIDs and the BM Unit

• FPN Flag for the BM Unit

• Base TU Flag

A detailed description of the interface content may be found in CRA-I005.

The CRA shall accept updated details of the registration from BSCCo Ltd including:

• Exempt Export Flag (not applicable to Secondary BM Units)

A detailed description of the interface content may be found in CRA-I043.

The system shall validate the following details:

1) That the referenced lead Party is contained within the system and is a currently valid BSC Party and not a Party Agent

2) That the GSP Group referenced is contained within the system (where appropriate for type)

3) That the Interconnector referenced is contained within the system (where appropriate for type)

4) That the name provided for the BM unit is not duplicated within the system

5) That the sending BSC Party is of a type able to register a BM Unit as specified in the mapping between BSC Party types and Registration operations

6) That a valid (not null) WDCALF and NWDCALF value has been received (see CRA-F020) and entered, with the exception of Secondary BM Units for which these values do not apply

7) That if the BM Unit is a “Supplier BM Unit”, then a valid (not null) SECALF value has been received (see CRA-F020) and entered

8) That if the BM Unit is a “Supplier BM Unit”, then the Effective To Date for the BM Unit is open ended.

Where a duplicate name is found, the system shall warn the Operator of the fact and ask for confirmation before further processing. Where the last check is failed, the Operator shall be presented with a warning which must be explicitly overridden prior to acceptance of the data.

Production / Consumption Flag

Should the Production / Consumption flag be set within the flow, it is the responsibility of the Operator to ensure that an authorisation to support this has been received from BSCCo Ltd. The CRA system shall not allow the Production / Consumption Flag to be set for a non-Exempt Export BM Unit (unless it is an Interconnector User BM Unit or Secondary BM Unit, in which case the flag must be set).

In the case of an Exempt Export BM Unit, the Production / Consumption flag shall always be set to either “Production” or “Consumption” and shall never be cleared by the Operator while the BM Unit has Exempt Export status.

Exempt Export Flag⁵

On registration, the Exempt Export Flag shall be unset by default for all BM Units. The Exempt Export Flag will remain unset for all Secondary BM Units.

Base TU Flag

On registration, the Base TU Flag shall be set by default for all Base Supplier BM Units and Additional Supplier BM Units to indicate that the BM Unit is allocated to the GSP Group Base Trading Unit. The Base TU Flag shall be unset by default for all non-Exempt Export Embedded BM Units. The CRA system shall not allow the Base TU flag to be set for Directly Connected or Interconnector User BM Units.

A Secondary BM Unit cannot be in a Trading Unit; however, for the purposes of determining the relevant Transmission Loss Multiplier (TLMij), the Trading Unit Delivery Mode of the Base Trading Unit shall be used based on the GSP Group Id of that Secondary BM Unit).

After all validation has been completed, the system shall return a new unique, meaningful identifier for the BM Unit on completion of storing the registration data. Self-Service Gateway users may select a BM Unit identifier, subject to a uniqueness check. Where an NGC BM Unit name is supplied, this shall be stored against the BM Unit, though the name shall not be considered when generating the NETA BM Unit Identifier. In addition, the event shall trigger the creation of a Trading Unit for the BM Unit in accordance with the requirement of CRA-F015.

Where registration is accepted, the system shall calculate the WDBMCAEC, NWDBMCAEC, WDBMCAIC, NWDBMCAIC and Production / Consumption status (except for Secondary BM Units) and trigger the sending of a BM Unit, Interconnector and GSP Group Data (CRA-I015) report and a Registration Report (CRA-I014).

The CRA may from time to time issue the Credit Assessment Capability (CRA-I017) report to the SAA and ECVAA.

The calculation of the Production / Consumption status will only be conducted where the Production / Consumption flag is not set on reception from the BSC Party. Where the Base TU Flag is set and the Production / Consumption flag is null, the Production / Consumption status of a BM Unit shall be set to “Consumption” by default. Note that the Production / Consumption flag cannot be set to null for an Exempt Export BM Unit.

Where the requirement functionality has been triggered from CRA-F001 or CRA-F030 in order to create a “Supplier BM Unit”, a subset of the CRA-I015 output data flow shall be sent to the SVAA.

Where the input details state a relationship between a BM Unit and one or many SVA MSIDs, the system shall store the relationship and issue a report on the mapping to the SMRA through CRA-I023.

Where the registration is indicated as part of a transfer to or from SMRA, then

• If confirmation of the transfer has been received from the transfer coordinator:

- Enter the data ensuring the confirmed date is used as this may differ from that originally submitted.

- Send an extract of the entered data to the transfer coordinator.

• Where confirmation has not been received:

- Carry out validation but do not enter the data.

- Send a copy of the request to the transfer coordinator.

A BM Unit, other than a Secondary BM Unit, will be considered as having a Credit Qualifying Status of “True” for those effective Settlement Dates where it meets the following conditions:

• It is not an Interconnector BM Unit; and

• Its FPN Flag set as “True”; and

• Either:

1. It is an Exempt Export BM Unit; or

2. It has a Production/Consumption Flag set as “Production”; or

For all other effective Settlement Dates a BM Unit will be considered as having a Credit Qualifying Status of “False”.

A BM Unit will have its Demand-in-Production Flag set as “True” for those effective Settlement Dates where it meets the following conditions:

• It is not an Exempt Export BM Unit; and

• It has a Credit Qualifying Status of “False”; and

• It has a Production/Consumption Flag set as “Production”; and

• Its Relevant Capacity is not greater than zero (i.e. GC_i + DC_i <= 0).

For all other effective Settlement Dates a BM Unit’s Demand-in-Production Flag set as “False”.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I005

Output interfaces:

CRA-I014

CRA-I015

CRA-I017

CRA-I019

CRA-I020

CRA-I023

CRA-I028

Requirement ID:

CRA-F014

Status:

Mandatory

Title:

View / Maintain BM Unit Registration

BSC Reference:

CRA SD 6.1, CRA BPM 3.2, NGC VAL 3.0, CRAWS-34, CRAWS‑37, DID‑2, CP775, P100, P215, P268, P269

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low (A few per month)

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to view and amend the details of a BM Unit registration within the system.

The CRA shall accept updated details of the registration from the BSC Party or BSCCo (as set out in CRA-F041 & CRA-F043) including:

• The BM Unit Registration Details (including type, production / consumption flag and whether an NETSO defined name is contained within the flow)

• Positive QMij-(for conversion to Generation Capacity) and Negative QMij (for conversion to Demand Capacity) (not required for Secondary BM Units)

• Details of the GSP group associated with the BM Unit (if appropriate)

• Details of the Interconnector associated with the BM Unit (if appropriate)

• Whether the BM Unit is part of a group of related BM Units and, where appropriate, the other BM Units in the group.

• MPAN - BM Unit mapping Details

• BM Unit FPN Flag

• Base TU Flag

A detailed description of the interface content may be found in CRA-I005.

The CRA shall accept updated details of the registration from BSCCo Ltd including:

• Exempt Export Flag (not applicable to Secondary BM Units)

A detailed description of the interface content may be found in CRA-I043.

The Operator shall be able to:

1) Amend the details of the BM Unit - type (production / consumption), generation capacity, location and name,

2) Change the lead Party for the BM unit,

3) Amend the list of MPANs associated with the BM Unit.

The following sections detail the constraints under which each of the operations may be conducted.

Where the NGC BM Unit Name is changed, the system shall update the BM Unit with the new name, and the date of the change.

Where Generation Capacity is decreased or Demand Capacity is increased within a BSC Season, the CRA system shall issue a warning to the Operator and ask for explicit confirmation of the change. This would be allowed only if authorisation for the change has been received from BSCCo Ltd. Generation Capacity and Demand Capacity are not applicable for Secondary BM Units).

The WDCALF, NWDCALF and SECALF values (see CRA-F020) cannot be set to NULL for a current BM Unit, except for Secondary BM Units, to which these values do not apply.

If the BM Unit is a “Supplier BM Unit” that was originally created as a result of a trigger from CRA-F001 or CRA-F030 (i.e. it is a “Base BM Unit”), the CRA system will ensure that the Effective Date Range of the BM Unit is contiguous and open ended. If it is not, then the CRA system shall issue a warning to the Operator to ask for explicit confirmation of the change. This should generally be allowed only if:

1. the BM Unit is being de-registered as a result de-registration of the associated BSC Party or GSP Group, i.e. the Effective To Date is changed from open ended to a specified date,

2. the BM Unit is being re-registered following de-registration, i.e. the Effective From Date of the new record is after the Effective To Date of an existing record.

Where the Lead Party is being changed, that the referenced lead Party is contained within the system and is a currently valid BSC Party and not a Party Agent. The ownership of a Secondary BM Unit may not be transferred to another Lead Party.

Where the generation capacity or demand capacity of the BM Unit is changed the system shall calculate the WDBMCAEC, NWDBMCAEC, WDBMCAIC and NWDBMCAIC, and trigger the sending of a BM Unit, Interconnector and GSP Group Data (CRA-I015) report and a Registration Report (CRA-I014)

The CRA may from time to time issue the Credit Assessment Capability (CRA-I017) report to the SAA and ECVAA.

Generation Capacity and Demand Capacity data, and Production / Consumption information may be resubmitted to the CRA at any time by the relevant Parties. However, it will be necessary for the Parties to submit the information at least one working day in advance of when the change will take effect.

Should the Production / Consumption flag be set within the flow, it is the responsibility of the Operator to ensure that an authorisation to support this has been received from BSCCo Ltd. The CRA system shall allow the Production / Consumption Flag to be changed for any Exempt Export BM Unit. The CRA system shall not allow the Production / Consumption Flag to be set for a non-Exempt Export BM Unit (unless it is an Interconnector User BM Unit or Secondary BM Unit, in which case the flag must be set).

In the case of an Exempt Export BM Unit, the Production / Consumption flag shall always be set to either “Production” or “Consumption” and shall never be cleared by the Operator while the BM Units retains its Exempt Export status.

Subsequently, this information shall be issued through interface CRA-I017.

The CRA system shall allow an Operator to view and update the Exempt Export Flag for a BM Unit.

The CRA system shall only allow the Exempt Export Flag to be changed for Base Supplier BM Units, Additional Supplier BM Units, Embedded BM Units and Directly Connected BM Units. The CRA system shall not allow the Exempt Export Flag to be changed for any other type of BM Unit.

Where a request to change the Exempt Export Flag of a Base Supplier BM Unit or Additional Supplier BM Unit indicates that the BM Unit is to be non-Exempt Export (and therefore, re-allocated to the GSP Group Base Trading Unit), the CRA shall validate that the BM Unit does not belong to an explicit Trading Unit already. If it does, the request shall be rejected.

Where a valid request to change the Exempt Export Flag indicates that the BM Unit is to be Exempt Export, the CRA shall set the Exempt Export Flag.

Where a valid request to change the Exempt Export Flag indicates that the BM Unit is to be non-Exempt Export, the CRA shall:

1. clear the Production / Consumption Flag to indicate that Production / Consumption Status is derived dynamically

2. for Base Supplier BM Units and Additional Supplier BM Units, set the Base TU Flag to indicate that the BM Unit is allocated to the GSP Group Base Trading Unit

3. for all other BM Units, unset the Base TU Flag and allocate the BM Unit to its own (default) Trading Unit

4. unset the Exempt Export Flag.

The new Exempt Export Flag shall subsequently be distributed as per the requirements of CRA-I014 and CRA-I020.

The CRA system shall allow for the transfer of responsibility of a BM Unit, with the exception of Secondary BM Units, from one lead Party to another. However, if the BM Unit is of a Supplier BM Unit, a warning shall be issued to the Operator.

The process of responsibility transference shall be a multi-step process conducted in the following manner:

Where a Party informs the CRA of responsibility for a BM Unit currently allocated to another Party, the CRA shall inform the Operator of this fact. The Operator must acknowledge this warning, upon which, the details of the registration change shall be stored within the system in a pending state. Should the effective start date by sooner than a predefined, system defined time limit [28 days]. The Operator shall also be warned of the fact.

On completion of the update an acknowledgement of the registration request will be sent to both the new and old Parties.

Where subsequently, a confirmation of the transference is sent from the old Party, the CRA system shall validate that the effective to date from the new Party is consistent with that received from the new Party. Where this occurs, the system shall update both the pending registration and the new registration.

Where the confirmation of responsibility is received after the effective start date of the new registration, the system shall present the Operator with a warning. This must be explicitly overridden by a Supervisor prior to the update being conducted. Where the Supervisor decides that the update cannot take place, the new registration request may also be put in a pending state for later resolution.

The change of BM Unit responsibility shall not require a change in BM Unit name.

Where the input details state a change to the relationship between a BM Unit and one or many Stage 2 MPAN’s, the system shall store the amended relationship and issue a report on the mapping to the SMRA through CRA-I023.

Where a request to change the Base TU Flag is received the CRA shall validate that the BM Unit is Exempt Export and, if not, the request shall be rejected.

The CRA system shall not allow the Base TU Flag to be changed for Directly Connected or Interconnector User BM Units.

Where a request to change the Base TU Flag indicates that the BM Unit is to be allocated to the GSP Group Base Trading Unit, the CRA shall validate that the BM Unit does not belong to an explicit Trading Unit already. If it does, the request shall be rejected.

Where a valid request to change the Base TU Flag indicates that the BM Unit is to be added to the GSP Group Base Trading Unit, the CRA shall re-allocate the BM Unit from its own (default) Trading Unit to the GSP Group Base Trading Unit.

Where a valid request to change the Base TU Flag indicates that the BM Unit is to be removed from the GSP Group Base Trading Unit, the CRA shall re-allocate the BM Unit to its own (default) Trading Unit.

Allocations and de-allocations to/from a GSP Group Base Trading Unit shall be made via the Base TU Flag only.

The Production / Consumption Status of the Base Trading Unit and its components shall be re‑computed for each change to a Base TU Flag. Where the Base TU Flag is set and the Production / Consumption flag is null, the Production / Consumption status of a BM Unit shall be set to “Consumption” by default. Note that the Production / Consumption flag cannot be set to null for an Exempt Export BM Unit.

A BM Unit will be considered as having a Credit Qualifying Status of “True” for those effective Settlement Dates where it meets the following conditions:

• It is not an Interconnector BM Unit; and

• Its FPN Flag set as “True”; and

• Either:

1. It is an Exempt Export BM Unit; or

2. It has a Production/Consumption Flag set as “Production”; or

For all other effective Settlement Dates a BM Unit will be considered as having a Credit Qualifying Status of “False”.

A BM Unit will have its Demand-in-Production Flag set as “True” for those effective Settlement Dates where it meets the following conditions:

• It is not an Exempt Export BM Unit; and

• It has a Credit Qualifying Status of “False”; and

• It has a Production/Consumption Flag set as “Production”; and

• Its Relevant Capacity is not greater than zero (i.e. GC_i + DC_i <= 0).

For all other effective Settlement Dates a BM Unit’s Demand-in-Production Flag set as “False”.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I005

CRA-I009

CRA-I043

Output interfaces:

CRA-I014

CRA-I015

CRA-I017

CRA-I019

CRA-I020

CRA-I023

CRA-I028

Requirement ID:

CRA-F015

Status:

Mandatory

Title:

Trading Unit Registration

BSC Reference:

CRA SD 6.2, CRA BPM 3.2, CRAWS-35, P100

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to enter details of a Trading Unit registration into the system (excluding Base Trading Units). The information for the definition of the Trading Unit shall be composed of:

• An Action Description

• Trading Unit Details (name, registration dates)

• Component BM Units

The definition of a Trading Unit requires the explicit authorisation of BSCCo Ltd. It shall be the responsibility of the Operator to ensure that supporting documentation from BSCCo Ltd has been received and are consistent with the Trading Unit registration request.

Trading Units should only be created by BSC Traders though other Parties shall not be restricted in their creation as per CRA-N001.

The system shall validate the following details:

1) That each of the BM Units acceptance of commercial responsibility is registered and recorded within the CRA system.

2) That at least one BM Unit is listed as a component of the Trading Unit (by default, on creation of a BM Unit, a Trading Unit is defined for the BM Unit).

3) That Base Supplier BM Units and Additional Supplier BM Units are Exempt Export.

4) That Secondary BM Units may not be allocated to a Trading Unit

After all validation has been completed, the system shall return a new unique identifier for the Trading Unit on completion of storing the registration data.

Where a BM Unit is associated with a Trading Unit explicitly, any previous association with a Trading Unit will be removed. This includes removal from a GSP Group Base Trading Unit, which the CRA shall perform according to requirement CRA-F014.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I006

Output Interfaces:

CRA-014

CRA-I015

CRA-I019

CRA-I020

Requirement ID:

CRA-F016

Status:

Mandatory

Title:

View / Maintain Trading Unit Registration Details

BSC Reference:

CRA SD 6.2, CRA BPM 3.2, CRAWS-35, CRAWS-39

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to enter details of Trading Unit registration changes into the system. The information for the amendment of the Trading Unit shall be composed of:

• An Action Description

• Trading Unit Details (name, registration dates)

• Component BM Units

Any change to a Trading Unit registration requires the explicit authorisation of BSCCo Ltd

The system shall validate that each of the BM Units’ acceptance of commercial responsibility is registered and recorded within the CRA system.

Where a BM Unit is removed from a Trading Unit, it shall be reassigned to its own (default) Trading Unit after completion of the operation. Where a BM Unit is added to a Trading Unit, it shall be removed from its (default) Trading Unit.

Where a change to the scope of the component BM Units (either through addition or subtraction) fails validation, the Trading Unit registration request will be held as pending subject to resolution.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I006

Output Interfaces:

CRA-I014

CRA-I015

CRA-I019

CRA-I020

Requirement ID:

CRA-F017

Status:

Mandatory

Title:

Register CRA Boundary Points and System Connection Points Details

BSC Reference:

CRA SD 6.4, CRA BPM 3.3, CR_990813_07, CRAWS-36, CRAWS-39, CP615, CP1301

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

1. The CRA or Self-Service Gateway user shall register data relating to all Boundary Points and System Connection Points. These are registered by either the NETSO or a Distribution System Operator using flow CRA-I007 at least 20 WD before the Effective From date. The BSCP form on which this flow is based contains additional information which is not captured in the database, but which is used by other recipients of the form.

a. A Boundary Point is a point at which any Plant or Apparatus not forming part of the Total System is connected to the Total System (Total System means the Transmission System and each Distribution System)

Boundary Points Registered By NETSO are:

• Gensets directly connected to the Transmission Network

• Station Transformers directly connected to the Transmission Network

• Demand sites directly connected to the Transmission Network

• Interconnectors with other Transmission Systems

Boundary Points Registered by the Distribution Business are:

• Embedded sites, under the direct control of the NETSO, that form an individual BM Unit. (These are sites over 50 MW or those being despatched by the NETSO).

• Other Embedded sites.

• Interconnectors with other Transmission Systems (where these connect to a distribution system)

b. A System Connection Point is a point at which two or more Systems are connected, including a connection between Distribution Systems in different GSP Groups (but excluding a connection between Distribution Systems in the same GSP Group).

System Connection Points Registered By NETSO are:

• Grid Supply Points (including Offshore Transmission Connection Points)

• An Offshore Transmission Connection Point is a point where a Distribution System connects to an Offshore Transmission System and will be registered by the NETSO as a Grid Supply Point.

System Connection Points Registered By Distribution Business are:

• Interconnectors Between Distribution Networks

2. In each case CRA shall maintain the following information:

• Boundary Point, or System Connection Point Identifier;

• Boundary Point or System Connection Point Type

• Effective From Date

• Effective To Date

3. Where a request is received to create a Boundary Point or System Connection Point then CRA shall inform BSCCo Ltd by forwarding a copy of the information provided. BSCCo Ltd will be notified of any changes input using the Self-Service Gateway.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I007

Output Interfaces:

CRA-I007

CRA-I014

CRA-I019

CRA-I028

Issues:

Requirement ID:

CRA-F034

Status:

Mandatory

Title:

Register Metering System Details

BSC Reference:

CRA SD 6.4, CRA BPM 3.3, CR_990813_07, CRAWS-36, CRAWS-39, CP569, CP753, P55, CP1301

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA shall receive the following information concerning the registration of Boundary Points and Metering Systems.

• An Action Description

• Authentication Details

• Metering System Details (including the CVA Meter Operator Agent for the Metering System)

Metering Systems should only be registered by certain types of BSC Parties. The following table illustrates which type of BSC Party should register a Metering System(See CRA-N001)

The NETSO shall register Metering System details for Offshore Transmission Connection Points only. All other Metering Systems for Grid Supply Points shall be registered by the Distribution Company.

It shall be the responsibility of the Operator to ensure that the type of the meter specified on the incoming flow is correct against any supporting paper based documentation.

Where metering system details are registered, the CRA shall validate that the CVA Meter Operator Agent specified against the metering system is registered with the CRA.

Where a Metering System is attempted to be registered but already exists within the system, the Operator shall be informed of the event and may, instead, enter the new details as an amendment to the current details through the View / Maintain Metering Systems functionality.

For each new Metering System registration, the CRA shall ensure that the registrant has confirmed that either:

• the Registrant is the Equipment Owner, or

• the Registrant has obtained the Equipment Owner’s consent for the appointment.

Where the registration is indicated as part of a transfer to or from SMRA, then

• If confirmation of the transfer has been received from the transfer coordinator:

- Enter the data ensuring the confirmed date is used as this may differ from that originally submitted.

- Send an extract of the entered data to the transfer coordinator.

• Where confirmation has not been received:

- Carry out validation but do not enter the data. If necessary allocate a Metering System Identifier and inform the registrant.

- Send a copy of the request, including any allocated metering system id, to the transfer coordinator.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I031

Output Interfaces:

CRA-I014

CRA-I019

CRA-I022

CRA-I028

Issues:

Functional Requirement:

The CRA shall receive changes to the registration of Boundary Points and System Connection Points. Changes may also be made using the Self-Service Gateway.

Where a request is received to decommission a Boundary Point or System Connection Point then CRA shall inform BSCCo Ltd by forwarding a copy of the information provided. BSCCo Ltd will be notified of any changes input using the Self-Service Gateway.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I007

Output Interfaces:

CRA-I014

CRA-I019

CRA-I028

Requirement ID:

CRA-F019

Status:

Mandatory

Title:

View / Maintain Interconnector Registration

BSC Reference:

CRA SD 6.3, CRA BPM 3.6, CRAWS-38, CRAWS-39

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Infrequent

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to register Interconnector Registration details. The details of an Interconnector shall be composed of:

• Action Description

• Authentication Details

• Interconnector Details (including GSP group where appropriate)

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I008

Output Interfaces:

CRA-I014

CRA-I015

CRA-I020

Requirement ID:

CRA-F020

Status:

Mandatory

Title:

Maintain Credit Assessment Load Factor

BSC Reference:

CRA SD 7.1, CRA SD 7.2, CRA BPM 2, CR012, CP775, P310

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to view and update the Working Day Credit Assessment Load Factor (WDCALF_i), Non-Working Day Credit Assessment Load Factor (NWDCALF_i) and Supplier Export Credit Assessment Load Factor (SECALF_i) values for a BM Unit other than a Secondary BM Unit. The Working Day Credit Assessment Load Factor (WDCALF_i), Non-Working Day Credit Assessment Load Factor (NWDCALF_i) and SECALF_i are each single values per BM Unit that may be changed from time to time. SECALF_i values are only relevant for Supplier BM Units; for all other BM Units a zero value of SECALF_i shall be entered.

The interface contains the following information:

• Action Description

• Authentication Details

• WDCALF_i and date from which it is effective.

• NWDCALF_i and date from which it is effective.

• SECALF_i and date from which it is effective.

The WDCALF_i, NWDCALF_i and SECALF_i values cannot be set to NULL for a current BM Unit, other than a Secondary BM Unit.

At the effective commencement date of the new BM Unit, other than a Secondary BM Unit, WDCALF_i, NWDCALF_i or SECALF_i, the CRA shall recalculate the Working Day BM Unit Credit Assessment Export Capability (WDBMCAEC_i) , the Non-Working Day BM Unit Credit Assessment Export Capability (NWDBMCAEC_i), the Working Day BM Unit Credit Assessment Import Capability (WDBMCAIC_i) and the Non-Working Day BM Unit Credit Assessment Import Capability (NWDBMCAIC_i) in accordance with the following formula for all registered BM Units:

WDBMCAIC_i = WDCALF_i*DC_i

NWDBMCAIC_i = NWDCALF_i*DC_i

If Supplier BM Unit,

If DC_i=0 and GC_i>0, then

WDBMCAEC_i = SECALF_i*GC_i

NWDBMCAEC_i = SECALF_i*GC_i

Else

WDBMCAEC_i = WDCALF_i*GC_i

NWDBMCAEC_i = NWDCALF_i*GC_i

The new WDBMCAEC_i, NWDBMCAEC_i, WDBMCAIC_i and NWDBMCAIC_i for all BM Units, other than Secondary BM Units, shall subsequently be distributed as per the requirements of CRA-F013 and CRA-F014.

The CRA may from time to time issue the Credit Assessment Capability Report (CRA-I017) to the SAA and ECVAA Services.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I011

Output Interfaces:

CRA-I014

CRA-I015

CRA-I017

Requirement ID:

CRA-F021

Status:

Title:

Requirement not currently used

BSC Reference:

Man/Auto:

Frequency:

Volumes:

Functional Requirement:

Non Functional Requirement:

Interfaces:

Man/Auto:

Automatic

Frequency:

Monthly or Ad-hoc

Volumes:

Low

Functional Requirement:

The CRA shall recalculate and store the Working Day BM Unit Credit Assessment Export Capability (WDBMCAEC_i), the Non-Working Day BM Unit Credit Assessment Export Capability (NWDBMCAEC_i), the Working Day BM Unit Credit Assessment Import Capability (WDBMCAIC_i) and the Non-Working Day BM Unit Credit Assessment Import Capability (NWDBMCAIC_i) in accordance with the following formula for all registered BM Units, other than Secondary BM Units, once per month or for individual BM Units, other than Secondary BM Units, when triggered as a result of the:

• redefinition of a Trading Unit;

• registration of a new BM Unit;

• change in the Generation or Demand Capacity for a BM Unit

• change in the WDCALF_i, NWDCALF_i or SECALF_i for a BM Unit

The CRA shall calculate the Credit Assessment Capability values as:

WDBMCAIC_i = WDCALF_i*DC_i

NWDBMCAIC_i = NWDCALF_i*DC_i

If Supplier BM Unit,

If DC_i=0 and GC_i>0, then

WDBMCAEC_i = WDSECALF_i*GC_i

NWDBMCAEC_i = SECALF_i*GC_i

Else

WDBMCAEC_i = CALF_i*GC_i

NWDBMCAEC_i = NWDCALF_i*GC_i

The system shall not overwrite the previous values of the WDBMCAEC_i, NWDBMCAEC_i, WDBMCAIC_i or NWDBMCAIC_i, but log the new data with the date from which it is effective.

The CRA shall also recalculate the Production / Consumption Status for the affected BM Units if the BM Unit is defined to have a non-fixed Production / Consumption Status, as follows:

If DC_i >= GC_i, then

the Relevant Capacity is DC_i.

Else

the Relevant Capacity is GC_i.

The Trading Unit Production / Consumption Status is determined by summing the Relevant Capacities for all BM Units in the Trading Unit.

If the sum of the Relevant Capacities is <= 0, then

the Trading Unit Status is Consumption

else

the Trading Unit Status is Production.

Each BM Unit shall be assigned the same (Production / Consumption) Status as the relevant Trading Unit, except in the case where the Flag has been notified by the Party. In this case, the BM Unit Production/Consumption Status is as notified by the Party (Production / Consumption Flag set).

The CRA will distribute the new WDBMCAEC_i, NWDBMCAEC_i, WDBMCAIC_i and NWDBMCAIC_i for all BM Units, other than Secondary BM Units, as per the requirements of CRA-F013 and CRA-F014.

Non Functional Requirement:

Interfaces:

Output Interfaces:

CRA-I014

CRA-I015

CRA-I017

Requirement ID:

CRA-F023

Status:

Mandatory

Title:

Validate Registrations

BSC Reference:

CRA SD 8, CRA BPM 3.4, CRAWS-40, P100

Man/Auto:

Automatic

Frequency:

Daily

Volumes:

Low

Functional Requirement:

The CRA system shall on a daily basis, perform a validation check to ensure the consistency of all data that has been changed over the course of the day. This check shall highlight conditions in two states - Error and Warning and shall validate that:

1) All BM Units, other than Secondary BM Units, are associated with a Trading Unit, (Error)

2) All Interconnectors have a defined Interconnector Error Administrator. In addition that the BSC Party statement of Error Administrator registration matches that received through the Interconnector Administrator registration data. (Warning / Error)

3) That all BM Units have a defined lead Party (Error)

4) That no BM unit responsibility registration requests are pending (Warning)

5) That all BSC Party and Service Agents are outside of a system wide time prior to the end of their certification period [28 days] (Warning)

6) That there are no unconfirmed change of BM Unit responsibility requests within a system wide period of the date of change. [28 days] (Warning)

7) All Base Supplier BM Units and Additional Supplier BM Units that are not Exempt Export, are allocated to the Base Trading Unit of the appropriate GSP Group (Warning).

In addition, the CRA system shall list all registration changes that are pending or failed along with the date at which they entered such states.

The system shall present each validation warning / failure to the Operator through an online screen on demand for subsequent rectification through View / Maintain functionality described in previous appropriate requirements.

The CRA system shall allow an Operator to search through the highlighted information by failure type, BSC Party and effective to / from dates to limit the amount of information presented at any one time.

Non Functional Requirement:

Interfaces:

Requirement ID:

CRA-F024

Status:

Mandatory

Title:

Report Registration Details

BSC Reference:

CRA SD 10, CRA BPM 3.7, CRAWS-41

Man/Auto:

Automatic

Frequency:

Daily

Volumes:

Low

Functional Requirement:

The CRA shall produce a report, daily, on all registration details that have changed over the course of the day to the relevant BSC Parties.

The system shall maintain a log of all information distributed on each occurrence.

Non Functional Requirement:

Interfaces:

Output Interfaces:

CRA-I014

Requirement ID:

CRA-F025

Status:

Mandatory

Title:

Distribute Register Data

BSC Reference:

CRA SD 10, CRA SD 11, CRA BPM 3.8, CRAWS-42, CR_991027_06a, CP753, CP551, CP642, P197

Man/Auto:

Automatic

Frequency:

See Text

Volumes:

Low

Functional Requirement:

The CRA shall, daily (or more frequently if multiple changes occur), distribute changes to centrally held register data within the system on a pre-defined schedule. The following data shall be distributed daily as a result of a change to the base data as highlighted in prior requirements:

CRA-I013 - Issue Authentication Report

CRA-I014 - Issue Registration Report

CRA-I015 - Issue BM Unit & Energy Account Registration Data (See Note 1)

CRA-I017 - Issue Credit Assessment Capability

CRA-I020 - Issue Operations Registration Report (Incremental Report)

CRA-I022 - Issue Metering System Details

CRA-I024 - Issue Certification & Accreditation Status Report⁶

CRA-I028 - Issue NGC Standing Data Report

The following data shall be distributed monthly irrespective of whether the data has changed over the previous month.

CRA-I013 - Issue Authentication Report

CRA-I017 - Issue Credit Assessment Capability

The following data shall be sent to the BSCCo weekly irrespective of whether the data has changed over the previous week:

CRA-I020 - Issue Operations Registration Report (Full Refresh Report)

Each report shall also be able to be distributed on request through an Operator entering the distribution details.

Note 1: The BM Unit and Energy Account Registration report (CRA-I015, subflow 2) generated for SVAA will only be sent if the report itself differs from the previously generated report.

Non Functional Requirement:

Interfaces:

Output Interfaces:

CRA-I013

CRA-I014

CRA-I015

CRA-I017

CRA-I020

CRA-I022

CRA-I024

CRA-I028

Requirement ID:

CRA-F026

Status:

Mandatory

Title:

Maintain Reference Data

BSC Reference:

CRA SD 8, CR_990813_07, CRAWS-43

Man/Auto:

Manual

Frequency:

Daily

Volumes:

Low

Functional Requirement:

The CRA system shall provide facilities for the maintenance of reference data used within the system. The following data shall be maintained (though additional requirements may be found during detailed design):

a) BSC Party Types,

b) BSC Party Agent Types,

c) BSC Service Agent Types,

d) Settlement Report Distribution Methods,

e) Point Types,

f) BM Unit Types.

Non Functional Requirement:

Interfaces:

The information is expected to be presented to the CRA system in low volume on paper.

Requirement ID:

CRA-F027

Status:

Mandatory

Title:

SLA Reporting

BSC Reference:

CRA SD Appendix B, CRAWS-45, P197, P310

Man/Auto:

Manual

Frequency:

Monthly

Volumes:

Low

Functional Requirement:

The CRA shall produce reports monthly detailing the level of service provided by the Service to the BSCCo Ltd. The reports shall detail the response times in delivering various aspects of the system as detailed below. The Service level for each of the activities is contained within the brackets in each case.

Other General requirements are described within the Common requirement GEN-N005

1) Process New BSC Party registrations - Validate data, authenticate registration application and update registration system with new registration data on the Working Day received (100%).

2) Process Change to BSC Party Standing Data - Validate changes to data and update registration system with new data on the Working Day received (100%)

3) Provide BSC Party Registration report - Registration reports produced and despatched to recipient on the Working Day received (100%)

4) BSC Party Authentication Details - Reports produced and despatched to recipient on the Working Day received (100%)

5) Qualify new BSC Party Agent - Complete Qualification Report returned on the Working Day received (100%)

6) Credit Assessment Import/Export Capability re-set on a monthly basis or within [1 Working Day] of change to WDCALF, NWDCALF or SECALF or DC or GC (100%)

Non Functional Requirement:

Interfaces:

BSCCo Ltd

Requirement ID:

CRA-F028

Status:

Title:

Requirement not currently used

BSC Reference:

Man/Auto:

Frequency:

Volumes:

Functional Requirement:

Non Functional Requirement:

Interfaces:

Requirement ID:

CRA-F029

Status:

Mandatory

Title:

Register Interconnector

BSC Reference:

CRA SD 6.3, CRA BPM 3.6, CRAWS-38

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Infrequent

Functional Requirement:

The CRA system shall allow a Self-Service Gateway user or an Operator to register Interconnector Registration details. The details of an Interconnector shall be composed of:

• Action Description

• Authentication Details

• Interconnector Details (including GSP group where appropriate)

Interconnectors should only be registered by a limited sub-set of BSC Parties (the Transmission Owner / Distribution Company) though other BSC Party types may register them in accordance with CRA-N001.

Interconnectors may only be registered after endorsement from BSCCo Ltd. It shall thus be the responsibility of the Operator to ensure that supporting documentation has been received and checked prior to registration.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I008

Output Interfaces triggered from this activity:

CRA-I014

CRA-I015

CRA-I020

Requirement ID:

CRA-F030

Status:

Mandatory

Title:

Register GSP Group and GSP Details

BSC Reference:

CRAWS-44, P100

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Infrequent

Functional Requirement:

The CRA system shall allow an Operator to register GSP Groups. The CRA system shall allow a Self-Service Gateway user or an Operator to register GSP and Distribution Systems Connection Point (DSCP) Registration details. The details of a GSP Group shall be composed of:

• Action Description,

• Authentication Details,

• GSP Group Details,

• GSP Details,

GSP Groups should only be registered by a limited sub-set of BSC Parties (The Distribution Companies) though other Party types may register in accordance with CRA-N001.

GSP Groups may only be registered after endorsement from BSCCo Ltd. It shall thus be the responsibility of the Operator to ensure that supporting documentation has been received and checked prior to registration. The CRA system shall allow the Operator to enter details that these checks have been conducted.

On successful registration of a GSP Group, the CRA shall register a Base Trading Unit for that GSP Group (with CRA as the registrant). Each BSC Party of type “Supplier” shall be returned a BM Unit of type “Base Supplier BM Unit” in accordance with the requirements of CRA-F013. Each Base Supplier BM Unit created in this way shall, by default, be allocated to the GSP Group Base Trading Unit, in accordance with the requirements of CRA-F013.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I027

Output Interfaces:

CRA-I014

CRA-I028

Requirement ID:

CRA-F031

Status:

Mandatory

Title:

View Maintain GSP Group and GSP Registrations

BSC Reference:

CRAWS-44

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Infrequent

Functional Requirement:

The CRA system shall allow an Operator to register changes to the GSP Group Registration details. The details of a GSP Group shall be composed of:

• Action Description,

• Authentication Details,

• GSP Group Details,

• GSP Details,

• GSP Registrant.

Changes to GSP Groups may only be registered after endorsement from BSCCo Ltd. It shall thus be the responsibility of the Operator to ensure that supporting documentation has been received and checked prior to registration. The CRA system shall allow the Operator to enter details that these checks have been conducted.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I027

Output Interfaces:

CRA-I014

CRA-I019

CRA-I028

Requirement ID:

CRA-F032

Status:

Mandatory

Title:

Maintain Transmission Loss Factors

BSC Reference:

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Infrequent

Functional Requirement:

The CRA system shall allow an Operator to update the Transmission Loss Factors for a BM Unit when instructed from BSCCo Ltd.

BSCCo Ltd shall provide the following information:

• The Proportion of Losses (alpha)

• The Transmission Loss Factors for individual BM Units for each Settlement Day.

The CRA system shall validate that each BM Unit detailed is registered for the range of effect of the Transmission Loss Factor Update. Where a discrepancy is found, the system shall issue a warning to the Operator.

The Transmission Loss Factors shall be issued via the CRA-I015.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I029

Output Interfaces:

CRA-I015

Requirement ID:

CRA-F033

Status:

Mandatory

Title:

Receive Registration Exception Reports

BSC Reference:

Man/Auto:

Automatic

Frequency:

As Necessary

Volumes:

Infrequent

Functional Requirement:

The CRA system shall receive Exception reports from the SAA, BMRA and ECVAA systems where Registration data sent to these systems has been rejected.

The CRA system shall receive exception data including:

• Sending Agent

• Exception Type

• Exception Description

The CRA system shall receive the exceptions automatically and allow an Operator to view the nature and description of the Exception. It is subsequently the responsibility of the Operator or a Supervisor to communicate with the sending Agent and resolve the discrepancy.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I030

Output Interfaces:

CRA-I015

Functional Requirement:

The CRA shall receive the following information about changes to the registration of the Metering Systems.

• An Action Description

• Authentication Details

• Metering System Details (including the CVA Meter Operator Agent for the metering system).

The CRA system shall allow the amendment of individual Metering System details;

The following validation shall be conducted:

1) That the effective from date of the change shall be no sooner than a pre-defined system wide duration [28 days] from the date of the registration request.

2) That the CVA Meter Operator Agent specified against a metering system is registered with the CRA.

Failure of the validation rule shall be flagged to the Operator who must subsequently acknowledge that the request is valid after consultation with interested Parties.

Non Functional Requirement:

Interfaces:

Input Interfaces:

CRA-I031

Output Interfaces:

CRA-I014

CRA-I019

CRA-I022

CRA-I028

Requirement ID:

CRA-F036

Status:

Mandatory

Title:

Maintain Flexible Reporting Requirements

BSC Reference:

CR 53, P8

Mechanism:

Manual

Frequency:

As Necessary

Volumes:

Low

Functional Requirement:

The CRA shall allow a Self-Service Gateway user or an Operator to update the set of flexible reporting requests currently in force. Each request is for a BSC Party role to receive a copy of a specific report destined for another BSC Party role, for BSCCo Ltd. to receive a copy of a specific report destined for another BSC Party role or for a specific version of a report to be generated for a BSC Party.

Batches of flexible reporting requests shall be received according to interface CRA-I034.

While a copy request is in force the system shall automatically distribute a copy of the report to the requesting BSC Party (or BSCCo Ltd.). The version copied will be that generated for the original organisation.

While a version request is in force, the system shall automatically generate the requested version of the report for the requesting organisation.

Non Functional Requirement:

Interfaces:

Input Interfaces

CRA-I034

Requirement ID:

CRA-F037

Status:

M

Title:

Transfer from SMRS

BSC Reference:

CP753

Man/Auto:

Manual

Frequency:

As necessary

Volumes:

Low

Functional Requirement:

A. When a new transfer notification is initiated, CRA will receive three flows.

• Meter Registration for the new metering system(s) (CRA-I031)

• BM Unit Registration for the new BM Unit(s) (CRA-I005)

• Transfer from SMRS details (CRA I038)

1. Process the Meter Registration according to CRA-F034, including allocation of a Metering System Identifier, but do not enter the data.

2. Send a copy of the received details (including allocated Metering System identifier) to the Transfer Coordinator.

3. Process the BM Unit registration according to CRA-F013, but do not enter the data. Send a copy of the received details to the Transfer Coordinator.

4. Check that the registrant named on the transfer initiation is a BSC Party

5. Confirm that BM Unit details have been submitted for the BM Unit(s) indicated on the transfer initiation

6. Confirm that the stated effective from date is possible

7. Confirm that the CVA MOA in the metering systems registration is valid

8. Send a report to the transfer coordinator (CRA-I039)

B. The Transfer coordinator will subsequently submit a CRA-I038 to confirm the transfer. This flow will contain the confirmed effective from date.

1. apply the changes (as received and validated above) using the confirmed effective from date.

2. send a Transfer Summary Report (CRA-I023) to the transfer coordinator and to the new CVA registrant(s)

C. If the Transfer coordinator submits a CRA-I038 rejecting the transfer, the process is abandoned (at this stage no changes have been made).

D. If the transfer coordinator submits a CRA-I038 to confirm progress, the CRA shall respond with information regarding the progress of the transfer including completed and outstanding operations

Non Functional Requirement:

Interfaces:

The CRA shall receive notification of transfer using flow CRA-I038

The CRA shall issue transfer reports using flow CRA-I039

Issues:

Requirement ID:

CRA-F038

Status:

M

Title:

Transfer to SMRS

BSC Reference:

CP753

Man/Auto:

Manual

Frequency:

Volumes:

Functional Requirement:

A. When a new transfer notification is initiated, CRA will receive:

• Transfer to SMRS details (CRA I040)

1. Check that the Metering System is registered in CRA

2. Check that the BM Unit(s) are registered in CRA

3. Confirm that the effective to date is possible

4. Confirm that the BM Unit is ready for deregistration

5. Check whether the BM Unit is part of a Trading Unit registered using CRA-F015

6. Send a report to the transfer coordinator (CRA-I041)

B. The Transfer coordinator will subsequently submit a CRA-I040 to confirm the transfer. This flow will contain the confirmed effective from date.

1. record the effective to date

2. on receipt of deregistration requests for the Metering systems and/or BM Units, apply the changes using the confirmed effective to date

3. send a Transfer Summary Report (CRA-I023) to the transfer coordinator and to the affected PDSO

C. If the Transfer coordinator submits a CRA-I040 rejecting the transfer, the process is abandoned (at this stage no changes have been made).

D. If the transfer coordinator submits a CRA-I040 to confirm progress, the CRA shall respond with information regarding the progress of the transfer including completed and outstanding operations.

Non Functional Requirement:

If deregistrations of all Metering Systems and BM Units have not been received by 20 working days before the confirmed effective to date, then contact the registrant.

Interfaces:

The CRA shall receive notification of transfer using flow CRA-I040

The CRA shall issue transfer reports using flow CRA-I041

Issues:

Requirement ID:

CRA-F039

Status:

Mandatory

Title:

Register / View / Maintain Market Index Data Provider

BSC Reference:

P78

Man/Auto:

Manual

Frequency:

As Necessary

Volumes:

Mostly at initial set-up

Functional Requirement:

1. The CRA shall allow an Operator to manually enter new Market Index Data Provider (MIDP) Registration Information into the CRA system.

The BSSCo Ltd shall submit registration information to the CRA system including details of:

• An Action Description to specify the type of registration operation,

• the MIDP (name, contact details),

A detailed description of the interface content may be found in CRA-I042.

Where the data has passed validation the information shall be stored within the CRA system database after being authorised by a Supervisor. The CRA system shall then allocate and return to the Operator a meaningful and unique MIDP ID.

The CRA system shall also provide the MIDP with sufficient information for the authentication of future communications, electronic or otherwise.

2. The CRA system shall, on receipt of a new Market Index Data Provider Registration request, create a unique and meaningful party identifier.

The CRA system shall perform a check against the name of the MIDP and currently stored MIDP.

To avoid errors of duplication, should a potential duplicate MIDP name be found, the system will issue a warning which must be overridden prior to allocation of a new identifier

3. The CRA system shall allow an Operator to view and maintain Market Index Data Provider details.

Full details of the flow may be found in CRA-I042.

Non Functional Requirement:

Interfaces:

Input interfaces:

CRA-I042

Output Interfaces:

CRA-I014

Requirement ID:

CRA-F040

Status:

Mandatory

Title:

Provide BSCCo with Withdrawals Checklist

BSC Reference:

CP974, P152

Man/Auto:

Manual

Frequency:

On request

Volumes:

Low

Functional Requirement:

The CRA shall collate registration and trading details relating to a BSC Party / BSC Party Agent in response to a request for the Withdrawals Checklist received from BSCCo Ltd (via Interface Requirement CRA-I044).

1. The registration details shall be matched to the request by means of the participant id and / or participant name registered in CRA.

2. Details of BSC Party / BSC Party Agent registrations shall be provided. Where a registration has ceased to be effective, the latest Effective To date shall be provided.

3. The CRA shall obtain the trading details relating to a BSC Party by requesting information from the ECVAA (Interface Requirement CRA-I045) and the SAA (Interface Requirement CRA-I046).

4. The last day of trading for the BSC Party shall be the date of the last non-zero metered volumes held by the SAA, or the date of the last non-zero notifications held by the ECVAA, whichever is the later. Where the BSC Party has no metered volumes recorded for any settlement day then the date of the last non-zero notifications shall be used. Where the date of the last non-zero notification is "evergreen", the last day of trading for the BSC Party shall also be "evergreen".

5. The payment date of the Final Reconciliation Run for the Party's last day of trading shall be determined from the Settlement Calendar. Note that the payment date may not be known if the last day of trading is recent (within the last 14 months).

Non Functional Requirement:

Interfaces:

CRA-I044: Receive Withdrawals Checklist Request

CRA-I045: Receive Withdrawing Party Authorisation and Notification Details

CRA-I046: Receive Withdrawing Party Settlement Details

CRA-I047: Issue Withdrawals Checklist

Requirement ID:

CRA-F041

Status:

Mandatory

Title:

GC and DC Breach Monitoring

BSC Reference:

P359

Man/Auto:

Automatic

Frequency:

Weekly

Volumes:

Low

Functional Requirement:

The CRA shall monitor BM Unit Metered Volumes to identify where a BM Unit has exceeded its Generation Capacity (GC) by more than the GC Limit (a GC breach) and/or has exceeded its Demand Capacity (DC) by more than the DC Limit (a DC breach).

1. On a periodic basis (schedule to be agreed with and changed, from time to time, by BSCCo) in the current BSC Season, the CRA shall, for each BM Unit other than a Secondary BM Unit or a BM Unit undergoing a GC or DC Estimation Challenge in accordance with BSC K3.4.7J:

1. derive the GC Limits and DC Limits for each eligible BM Unit in the current BSC Season, where GC/DC Limits are set by the Panel in accordance with the Demand Capacity and Generation Capacity Limit Review and Determination document and published on the BSC website;

2. retrieve the BM Unit Metered Volumes (QM_ij) for each Settlement Day and Settlement Period in the current BSC Season (except those Metered Volumes for BMUs that occurred on Settlement Days prior to the latest effective DC in accordance with BSC K3.4.2A, i.e. a downward declaration), and ensure Metered Volumes for any Emergency Instruction (EI) that occurred during the BSC Season are subtracted from the relevant BM Unit(s) QM_ij;

3. determine for all eligible BM Units and every Settlement Period in the current BSC Season that has been the subject of at least the II Settlement Run if a ‘GC Breach’ and/or ‘DC Breach’ has occurred, where a GC Breach for a BM Unit is where any of its positive values of QMij (excluding any EI volumes) exceed the GC by more than the GC Limits, and a DC Breach for a BM Unit is if any negative value of QMij exceeds the DC by more than the DC Limits.

Non Functional Requirement:

Interfaces:

Requirement ID:

CRA-F042

Status:

Mandatory

Title:

Identify CRA-estimated GC and DC amounts

BSC Reference:

P359

Man/Auto:

Automatic

Frequency:

As required

Volumes:

Low

Functional Requirement:

This is a description of the BM Unit Volume Estimation Methodology published on the BSC Website.⁷

1. Where a GC Breach or a DC Breach has been identified for a BM Unit, the CRA shall, for that BM Unit, estimate a replacement GC or DCQMij value (CRA-estimated GC and DC amounts) as follows, and in all cases before 1400 on the day the breach is identified:

a. Depending on whether responding to a GC breach and / or a DC breach, identify all positive QMij and/or negative QMij values for that BM Unit from the most recent Settlement Run for each Settlement Day and Settlement Period from the current BSC Season and the corresponding BSC Season in the previous BSC Year;

b. subtract from QMij any related Period Accepted Offer Volume(s) and/or Period Accepted Bid Volume(s) relating to Emergency Instructions that occurred on the same Settlement Day(s) and Settlement Period(s) as QMij identified in (a) above;

c. find the maximum positive QMij, which will be the CRA-estimated GC Amount; and

d. find the minimum negative QMij, which will be the CRA-estimated DC Amount.

2. Upon determining the CRA-estimated GC Amount and/or the CRA-estimated DC Amount, as applicable, the CRA will ensure the GC and/or DC for the BM Unit is updated, per CRA-F014, to reflect the CRA-estimated GC Amount and/or the CRA-estimated DC Amount. The new GC and / or DC should take effect at 00:00 on the next working day.

3. Not later than 15:00 on the day that the GC Breach or DC Breach is identified, the CRA shall notify the Lead Party of the BM Unit that the BM Unit is in GC Breach or DC Breach and will provide supporting information:

1. whether the BM Unit is in GC Breach or in DC Breach;

2. the Settlement Day and Settlement Period to which the Breach applies;

3. the relevant CRA-estimated GC or DC Amount:

4. the date on which the CRA-Estimated GC or DC Amounts will take effect⁸;

5. any other information deemed by BSCCo to be relevant; and

6. a statement to the effect that this notification will also be published on the BSC Website.

Note that, if a BM Unit is found to be in a GC Breach and DC Breach in the same Breach Monitoring run, separate notices will be issued for the GC Breach and the DC Breach.

4. The notice sent pursuant to 2.should also be sent to BSCCo, the CM Settlement Services Provider and the CFD Settlement Services Provider.

5. The means of communication will be agreed between the CRA and BSCCo, the CM Settlement Services Provider and the CfD Settlement Services Provider, and may change from time to time.

Non Functional Requirement:

Interfaces:

CRA-I049 ‘Notification of a GC Breach or a DC Breach”

Requirement ID:

CRA-F043

Status:

Mandatory

Title:

Manage GC or DC Estimation Challenges

BSC Reference:

P359

Man/Auto:

Automatic

Frequency:

As required

Volumes:

Low

Functional Requirement:

1. Where a Lead Party has been notified of a BM Unit which is in GC Breach or DC Breach, and believes that the CRA-Estimated GC or DC Amounts were calculated incorrectly (i.e. because either the CRA has not followed the BM Unit Volume Estimation Methodology correctly or the Settlement Data used is incorrect, the Lead Party may challenge the estimate(s).

2. A challenge will only be valid if submitted within 2 full Working Days of the Lead Party being notified (starting from the beginning of the Working Day following the deemed receipt of the notification); the CRA will not allow a challenge to be raised after this deadline.

3. The CRA must enable a Lead Party to submit a GC or DC Estimation Challenge online in respect of a BM Unit which is in GC Breach or DC Breach. The CRA must allow the Lead Party to provide it with the following details (the challenge details):

1. The relevant BM Unit;

2. The Settlement Date and Settlement Period relating to the GC Breach or DC Breach;

3. Evidence that the relevant positive or negative QMij was erroneous;

4. An alternative value of positive or negative QMij.

4. Where the CRA receives details of a challenge from the Lead Party, pursuant to 2 above, it shall immediately set the Appeal Status for the BM Unit to “Appealed”

5. The CRA must allow BSCCo to change the Appeal Status of any breach.

6. Where the CRA receives a GC or DC Estimation Challenge, pursuant to 2 above, it must immediately send the challenge details to BSCCo.

7. The means of communication will be agreed, and changed from time to time, between CRA and BSCCo

8. The CRA shall receive a decision from BSCCo on a GC Breach or DC Breach Challenge within 2 full Working Days of receipt of Appeal notification, which shall include.

1. The relevant BM Unit;

2. The Settlement Date and Settlement Period relating to the GC Breach or DC Breach; and

3. Whether the decision is “Upheld” or “Rejected”;

4. For an “Upheld” decision:

1. The new value of positive QM_ij or negative QM_ij to be assigned to the BM Unit; and

2. The Effective From Date for the new value of GC or DC.

9. Following 6 above, the CRA shall set the Appeal Status for the BM Unit to “Upheld” or “Rejected”, as appropriate, and subject to the rule set out in CRA-F044.

Non Functional Requirement:

Interfaces:

CRA-I050 “ GC Breach or a DC Breach Appeal”

CRA-I051 ‘GC or DC Breach Appeal Decision’

Requirement ID:

CRA-F044

Status:

Mandatory

Title:

Manage Conflicting GC/DC Submissions

BSC Reference:

P359

Man/Auto:

Manual

Frequency:

As required

Volumes:

Low

Functional Requirement:

The CRA may receive up to three distinct types of request to update GC and/or DC values which could have the same Effective From Date. Where the Effective From Dates are the same, the CRA shall prioritise the requests according to the order shown below, where 1 is the highest priority and 3 the lowest:

1. A value submitted by BSCCo following the conclusion of an appeal;

2. A value estimated by CRA following the identification of a breach;

3. A value submitted by the Lead Party (not as a consequence of an appeal, but in accordance with K3.4.2 and K3.4.2A).

N.b. where two or more of these requests are received with different Effective From Dates, the CRA shall process each request individually.

Non Functional Requirement:

Interfaces:

CRA-I050 “ GC Breach or a DC Breach Appeal”

CRA-I051 ‘GC or DC Breach Appeal Decision’

Requirement ID:

CRA-F045

Status:

Mandatory

Title:

Publish GC and DC Breach data

BSC Reference:

P359

Man/Auto:

Automatic

Frequency:

As required

Volumes:

Low

Functional Requirement:

The CRA shall publish data relating to a BM Unit in GC Breach or DC Breach on the BSC Website for not less than 24 calendar months after the date of the Breach notification:

• Breach Identification Date/Time stamp

• GC or DC breach

• BM Unit ID

• Breach SD

• Breach SP

• Actual BM Unit Metered Volume that triggered breach

• Prevailing GC or DC

• CRA calculated estimate of BM Unit Metered Volume

• EFD for GC or DC based on CRA estimate

• Appeal status – default value at the time of breach identification will be ‘No appeal’. Allowable values are: ‘No appeal’, ‘Appealed’, ‘Upheld’, ‘Rejected’

• Estimated BM Unit Metered Volume following the conclusion of an appeal (default value is NULL)

• Effective From Date of the amended volume due to an appeal. When an appeal has been successfully completed the effected from date of the new GC and/or DC resulting from the appeal.

The CRA shall ensure that only the Lead Party for the relevant BM Unit will be entitled to see the above details.

Non Functional Requirement:

Interfaces:

CRA-I001

Receive BSC Party Registration Data

I

BSC Party, BSCCo Ltd

Manual / Online

CRA-I001

Receive BSC Party Registration Data

O

BSCCo Ltd

Manual / Online

CRA-I002

Receive Interconnector Admin. Registration Data

I

BSC Party

Manual / Online

CRA-I003

Receive BSC Party Agent Data

I

BSC Party

BSCCo Ltd

Manual / Online

CRA-I004

Receive BSC Service Agent Data

I

BSCCo Ltd

Manual / Online

CRA-I005

Receive BM Unit Registration

I

BSC Party

Manual / Online

CRA-I006

Receive Trading Unit Registration

I

BSC Party

Manual / Online

CRA-I007

Receive Boundary Point and System Connection Point Data

I

BSC Party, NETSO

Manual / Online

CRA-I007

Receive Boundary Point and System Connection Point Data

O

BSCCo Ltd

Manual / Online

CRA-I008

Receive Interconnector Registration Details

I

NETSO

Manual / Online

CRA-I009

Receive BM Unit Manual Credit Qualifying Flag (Redundant)

I

BSCCo Ltd

Manual / Online

CRA-I010

No longer used

CRA-I011

Receive Credit Assessment Load Factors

I

BSCCo Ltd.

Manual / Online

CRA-I012

Issue CRA Encryption Key

O

BSC Party, MIDP & other Agents

Automatic

CRA-I013

Issue Authentication Details Report

O

FAA

ECVAA

BMRA

SAA

NETSO

BSCCo Ltd

Automatic

CRA-I014

Issue Registration Report

O

BSC Party, NETSO & BSC Party Agents

Automatic/Manual

CRA-I015

Issue BM Unit Registration Data

O

SAA,

SVAA

BMRA,

ECVAA,

FAA

Shared Database / Automatic

CRA-I016

No longer used

CRA-I017

Issue Credit Assessment Export Capability

O

SAA

ECVAA

Shared Database

CRA-I018

No longer used

CRA-I019

Issue CRA Registered Meter Data

O

CDCA

Shared Database

CRA-I020

Issue Operations Registration Report

O

NETSO

BSCCo Ltd

Automatic

CRA-I021

Issue Registered Service List

O

BSC Parties & public

Automatic

CRA-I022

Issue Metering System Details

O

Technical Assurance Agent

Manual

CRA-I023

Issue Registration Transfer Report

O

Transfer Coordinator,

BSC Parties,

PDSO

Manual

CRA-I024

Issue Certification & accreditation Status Report

O

BSC Parties

BSC Party Agents

BSC Service Agents

Automatic/Manual

CRA-I025

Receive Acknowledgement

I

All automatic outbound systems

Automatic

CRA-I026

Send Acknowledgement

O

All automatic inbound systems

Automatic

CRA-I027

Receive GSP Group Registration Details

I

BSC Party (Distributor)

Automatic

CRA-I028

Issue NGC Standing Data Report

O

NETSO

Automatic

CRA-I029

Receive Transmission Loss Factors

I

BSCCo Ltd

Manual / Online

CRA-I030

Receive Exception Report

I

SAA

ECVAA

BMRA

Automatic

CRA-I031

Receive Metering System Data

I

BSC Party

Manual

CRA-I033

Requirement not currently used

CRA-I034

Flexible Reporting Request

I

All automatic outbound systems

Manual / Online

CRA-I035

CRA BSC Section D Charging Data

O

BSCCo Ltd

Manual / Online

CRA-I036

Send Notification Agent Termination Request

O

ECVAA

Manual / Online

CRA-I037

Receive Notification Agent Termination Feedback

I

ECVAA

Manual / Online

CRA‑I038

Transfer from SMRS information

I

Transfer Coordinator, BSC Party

Manual

CRA‑I039

Transfer from SMRS report

O

Transfer Coordinator

Manual

CRA‑I040

Transfer to SMRS information

I

Transfer Coordinator, BSC Party

Manual

CRA‑I041

Transfer to SMRS report

O

Transfer Coordinator

Manual

CRA-I042

Receive Market Index Data Provider Registration Data

I

BSCCo Ltd

Manual / Online

CRA-I043

Receive Exempt Export Registration Data

I

BSCCo Ltd

Manual / Online

CRA-I044

Receive Withdrawals Checklist Request

I

BSCCo Ltd

Manual / Online

CRA-I045

Receive Withdrawing Party Authorisation and Notification Details

I

ECVAA

Manual / Online

CRA-I046

Receive Withdrawing Party Settlement Details

I

SAA

Shared Database

CRA-I047

Issue Withdrawals Checklist

O

BSCCo Ltd

Manual / Online

Requirement ID:

CRA-N001

Status:

M

Title:

Input Interface Requirements

BSC Reference:

CRAWS-40, CN122

Man/Auto:

Manual & Automatic

Frequency:

As required

Volumes:

Low

Non Functional Requirement:

1. The CRA system shall provide manual input mechanisms for the insertion of data into the system from external parties where stated.

2. The CRA service shall provide a mechanism for the decoding of electronically transferred data so that an operator may enter the details contained in the messages.

3. The CRA service shall provide functionality for a user to select an electronic data notification from a list of outstanding input messages and display the contents in a human readable form. Data items shall be listed alongside a label describing individual fields in the input data flow.

4. Where appropriate, the CRA system shall allow an Operator to ‘cut and paste’ the information in these messages into the relevant input screens.

5. The CRA service shall carry out validation of all data input so as to ensure that the data is, as far as is practicable, complete and consistent.

6. Where data is to be input manually, the service shall use reasonable endeavours to ensure that the quality of the data is not compromised in any way. The exact mechanism to ensure this is conducted will be developed in detail within the System and Detailed Design Specification.

7. Where relevant, registration actions or changes to registered data shall require the approval of BSCCo Ltd. The approval process will be facilitated by the Self-Service Gateway. Where the Self-Service Gateway is not used for data entry by the BSC Party, BSC Party Agent or applicant, paper based supporting documentation is required,. an Operator shall be expected to check that this authorisation has been received when processing the Registration request and supporting documentation. The Self-Service Gateway will provide facilities to:

• allow for cross-referencing between paper and electronic registration information.

• log that all relevant checks have been completed.

8. Should the data, once entered on the input form pass input validation but require confirmation from either a second Party or BSCCo Ltd, the Operator/Self-Service Gateway user shall then be presented with the ability to save the valid parts of the registration (subject to database constraints) in a “Pending” state rather than having to abort the entire update. While in this state, the data will be “invisible” to other parts of the BSC Central Systems. For instance it will not be issued to other Services (CDCA, SAA). At a later time, the Operator/Self-Service Gateway user shall be able to retrieve the partial update and complete when the original failure has been corrected.

9. Certain registration items (such as BM Units) are expected to be registered from a limited sub-set of Party types. The CRA system shall ensure that a check against Party type is conducted on entry or amendment of registration details.

10.. All registration entries / amendments will be tagged with the date and time of the operation as well as the identifier (username) of the Operator/Self-Service Gateway user who entered the details.

11.. Each registration operation may require a specific level of authorisation within the requesting Party. The CRA stores these levels of authorisation and shall validate that the requesting person has the authorisation to conduct the requested operation. Where this check fails the CRA shall reject the entire request. The Role-Based Access Control (RBAC) provided by the Self-Service Gateway will be used to authenticate online requests.

12. The CRA system shall (with exceptions such as on change of ownership of BM Units and Interconnector Error Administration responsibility) only accept registration amendments from the Party that sent in the original registration request.

13. The CRA Service shall undertake Interface Tests for all Parties wishing to register within the CRA. The interface tests will cover the following services (as appropriate to the applicant):

• BMRA;

• CDCA;

• CRA;

• FAA and

• SAA.

14. Where Validation errors occur within the system as either a result of individual data entry or through the daily validation check (CRA-F023) the system shall allow the failures to be viewed and searched for by an Operator in accordance with the following:

• The system shall present each validation warning / failure to the Operator through an online screen on demand for subsequent rectification through View / Maintain functionality described in previous appropriate requirements in Section 5.

• The CRA system shall allow an Operator to search through the highlighted information by failure type, BSC Party and effective to / from dates to limit the amount of information presented at any one time.

Man/Auto:

Manual & Automatic

Frequency:

As required

Volumes:

Low

Non Functional Requirement:

The CRA system shall receive electronic data in either encrypted or non-encrypted format. Each Party may exchange data with the CRA system using one or more encryption public keys. BSC Party information shall always be received using a notified encryption key, whereas Service Agents shall not be required to use encryption.

The CRA system shall communicate back to Parties using the encryption public key supplied from the party where supplied and the use mandated.

Requirement ID:

CRA-S002

Status:

Mandatory

Title:

Data Migration Requirements

BSC Reference:

CR990813_07, CRAWS-56

Man/Auto:

Manual & Automatic

Frequency:

As required

Volumes:

Non Functional Requirement:

Detailed Data Migration requirements will be established during the detailed design phase.

Issues:

Data Migration requirements need to be discussed with the Customer in detail and will be documented separately outside of the scope of the URS.

Man/Auto:

Manual & Automatic

Frequency:

As required

Volumes:

Non Functional Requirement:

The CRA shall provide a suitably secure repository for any documents or paper based information provided by BSC Parties in connection with their Registration or generated by the CRA in connection with the operation of their registration service.

This requirement is in addition to all general archiving requirements as stated in GEN-S004.

Issues:

System Administrator

Database management

Specific aspects of system configuration

User account and security management

Supervisor

Management of Operators

Management of standing data updates

Management of planned operational and service level requirements

Creation of management information reports

Support for communication with external parties

Operator

Performance of procedures to monitor receipt and processing of information from external parties.

Second level support for ad hoc queries raised by external parties

Help Desk Operator

First level support for ad hoc queries raised by external parties.

Auditor

There shall be a specific user security configuration which allows an external auditor to review data within the system, but prevents the initiation of batch processes or logical edits to business data.

Market Index Data Provider

Market Index Data Providers are registered by BSCCo Ltd, and their details are passed on by CRA to SAA and BMRA.

Role

Summary of Activities related to CRA

BSCCo Ltd.

Receives summary settlement reports from CRA at periodic intervals (daily, weekly, monthly) as well as CRA performance reports.

Balancing Mechanism Operator (NETSO)

Reports are produced to NETSO on Standing data held within the system.

BSC Party

BSC Parties register information (such as their own registration) as well as registration details of BM Units, Trading Units, etc. They also receive confirmation that these registrations have been either successful applied or failed for some reason.