Synopsis	This document contains the definition and design of all interfaces between the BSC Service Systems and other Systems. It includes the specification of file formats and structure of electronic files. Part two only contains details for interfaces which involve BSC Agents and other service providers.
Version	Version 51.0
Effective date	07 November 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.

0.1 Purpose

0.1.1 Summary

This document is Part 2 of the Interface Definition and Design

The scope of the document is, for each BSC Service System provided, the definition and design of all interfaces between the BSC Service System and other Systems.

The scope of Part 2 is limited to the definition and design of all interfaces with the BSC Service System which do not involve BSC Parties and their Agents.

Note that, subsequent to the introduction of P62, any of the following terms can represent a Licensed Distribution System Operator (LDSO) or any Party which distributes electricity.

Distribution Business
Distribution System Operator
Public Distribution System Operator (and abbreviation PDSO)
Distribution Company
Public Electricity Suppliers (PES), as operators of a distribution network
Distributor, as operator of a distribution network.

0.2 Scope

0.2.1 The Scope of this Document

The scope of the BSC Service systems are defined in Part 1 of the Interface Definition and Design.

Interfaces between BSC Service Systems services are termed here Internal. They are referenced in the URS documentation as being of equal status to external interfaces but are only indicated in the Interface Definition and Design, as the precise nature of the interface is an implementation decision.

0.3 Summary

Part 2 of the Interface Definition and Design covers interfaces with other BSC Systems, and is organised as follows:

Section 2 describes common interface conventions, in particular defining the approach to interfacing via file transfer.
Section 2.1 gives a summary of the interfaces, organised by BSC agent and by corresponding party.
Sections 4 to 8 and 10 to 11 define the interfaces to each of the corresponding parties.
Section 9 defines interfaces between the BSC agents.

0.4 Amendment History

Date	Version	Details of Change	Committee Approval Ref
04/11/2010	26.0	Document rebadged and amended for November 2010 Release (P243, P244, CP1333)
03/11/2011	27.0	November 2011 Release (CP1345, P253)
28/06/2012	28.0	June 2012 Release (CP1364)
26/06/2014	29.0	26 June 2014 Release (CP1397)	ISG150/02
01/08/2014	30.0	ORD005 – Electricity Market Reform Directed by the Secretary of State	Directed by the Secretary of State
06/11/2014	31.0	6 November 2014 Release (CP1412)	ISG159/01
16/12/2014	32.0	16 December 2014 Release (P291, P295)	ISG162/01
25/06/2015	33.0	June 2015 Release (CP1435)	ISG168/02
		June 2015 Release (P310 Self-Governance)	ISG169/05
05/11/2015	34.0	November 2015 Release (P323)	P245/06
		November 2015 Release (P305)	ISG172/04
23/02/17	35.0	February 2016 Release (P326 Self-Governance Alternative)	ISG188/05
29/06/17	36.0	29 June 17 Release (P321 Self-Governance, P350)	ISG194/02
02/11/2017	37.0	P342 Alternative. 2 November 2017 Release	ISG198/04
01/11/2018	38.0	CP1503; 1 November 2018 Release	P277/04
28/02/2019	39.0	February 2019 Release – P344	P284C/01
		February 2019 Release – P359	ISG212/03
		February 2019 Release – P297	P222/06
		February 2019 Release – P373	P284/04
29/03/2019	40.0	March 2019 Standalone Release – P369	P285/12
27/06/2019	41.0	June 2019 Release – P367 Self-Governance	ISG216/01
11/12/2019	42.0	11 December 2019 Standalone Release – CP1517	ISG220/01 ISG222/03
27/02/2020	43.0	February 2020 Release – P394 Self -Governance	P297/07
01/04/2020	44.0	April 2020 Standalone Release – P354	ISG227/0
05/11/2020	45.0	November 2020 Release – P396	ISG233/04
18/03/2021	46.0	18 March 2021 Standalone Release – P408 Self-Governance	ISG234/02
04/11/2021	47.0	4 November 2021 Standard Release	P310/04
07/12/2022	48.0	7 December 2022 Special Release - P448	P332A/01
23/02/2023	49.0	23 February 2023 Standard Release	P314/06, ISG259/09
02/11/2023	50.0	02 November 2023 Standard Release	P340/05
07/11/2024	51.0	07 Novemeber 2024 Standard release	P415

0.5 References

[SD]	Draft Service Descriptions for Central Data Collection, Energy Contract Volume Aggregation, Central Registration, Balancing Mechanism Reporting, Settlement Administration,
[BPM]	RETA Business Process Models:
	Top Level Processes
	Central Registration
	Aggregate and Check Contract Volume
	Balancing Mechanism Reporting
	Central Data Collection and Aggregation
	Calculate Settlement Debits and Credits
	Indicative Reporting Requirement
	Entity Relationship Model
[COMMS]	Communications Requirements Document
[NGCSPEC]	NGC Control Technology Specification: NETA BMRA & SAA Interface Specification

0.6 Abbreviations

A list of abbreviations is given in Part 1 of this document.

1 Common Interface Conventions

1.1 Interface Mechanisms

This section outlines the different interface mechanisms used.

1.1.1 Manual

Some interfaces employ a manual mechanism. This means that the information is delivered by mail, by a telephone call, by email, or by fax from one person to another. (Perhaps in an electronic file attached to an email or written to a floppy disc)

All incoming manual flows are required to have been initiated by an Authorised Signatory. The flow will contain the Authorised Signatory Name and Password plus:

for flows submitted by post or fax, the signatory’s signature is required;
for those flows which are submitted by email, the sending email address must be that registered for the signatory.

Where applicable, the sender will have read the information from a computer screen or printed it out before sending it. Similarly, where applicable, the recipient enters the information into a computer system, probably via a data entry screen-based interface.

More details of the manual mechanism are given where appropriate for a particular flow.

1.1.2 Electronic Data File Transfer

The majority of non-manual interfaces use electronic file transfer. A data file is created on the source system, and is then copied to a predetermined directory on the destination system. The mechanism for the network copy is described in [COMMS].

Common File Format

A common format will be used as far as is possible for data files transferred to and from BSC Central Services. This is specified in Section 2.2 of Part 1 of the Interface Definition and Design.

NGC File Format

Data received from the National Electricity Transmission System Operator (NETSO) (described in this document as flows BMRA-I002 and BMRA-I003) will be formatted according to the NETSO’s specification for the flows, given in [NGCSPEC]. For the avoidance of doubt, this format is amplified as follows:

The first line of the file will contain an asterisk and the file name.
The second through fifth lines of the file will start with an asterisk and will be ignored.
The last line of the file will begin with the characters ‘<EOF>’.
Lines not beginning with an asterisk or ‘<EOF>’ will contain data records. A data record consists of fields separated by commas as illustrated in Section 14 of [NGCSPEC].
A checksum is not included in these files.

The files use the ASCII character set.

In addition, receipt of these files will not be acknowledged by the BSC Central Systems in any way. Files contain sequence numbers - each file type has its own sequence, and duplicate or missing file detection is the same as described in section 2.2 of Part 1, except that instead of sending an out of sequence message, a warning is logged so that the operator can instigate manual processed to resolve the problem.

[NGCSPEC] defines one file which has a different format: the System Warning file, file name SYS_WARN_<CREATION DATE>.bmr. This is a free format text file with no special formats for the first five lines or the last line.

The other exception is the SO-SO Price interface (BMRA-I025). This data is provided as an XML file, in a format defined by the XML Schema for Merit Order List documents (published in the ENTSO-E Reserve Resource Planning EDI library).

All other interfaces with the System Operators will use the common conventions specified in Section 2.2 of Part 1 of the Interface Definition and Design.

NOTE: following implementation of the new Electricity Balancing System (currently scheduled for 2013), we plan to begin migrating all interfaces with the NETSO from CSV to XML. Our intention (subject to confirmation when assessing the relevant Modification Proposals or Change Proposals) is that all new or amended files provided by the NETSO, whether in relation to BMRA-I002, BMRA-I003 or any other relevant interface requirement, will make use of an XML format. The details of this format will be agreed with the NETSO closer to the time, and will then be defined in [NGCSPEC].

Pool Transfer File Format

The interfaces with Stage 2 (described in section 8 of this document as flows CDCA-I043, SAA-I007 and CRA-I015) will use Pool Transfer File Format (PTFF) as defined in the SVA Data Catalogue.

The files use the ASCII character set.

The PTFF header and footer records are described in the SVA Data Catalogue. The specific information needed to populate the header record for each flow is given in section 8.

Response messages are sent in response to these flows. These response messages are P0183001 PTFF files as specified in the SVA Data Catalogue.

Interfaces to EMR

The BM Unit Chargeable Demand Report (SAA-I042) is sent to the EMR Settlement Services Provider in XML format, as described in section 11.

1.1.3 Internal Interfaces

Interfaces between BSC Agent services are only indicated in the Interface Definition and Design, as the precise nature of the interface is an implementation decision. As part of the current architecture these internal interfaces are of three kinds:

via shared database – between CRA, and CDCA
via automated interface between SAA and CRA
electronic data file transfer – between these and ECVAA and BMRA.

1.1.4 Repeating Structure

The structure of records and their nesting rules are specified using tables. The tables are defined in a spreadsheet attached to the end of the document. The meaning of data in those tables is explained in section 2.2.4 of Part I.

The Tabs of the Spreadsheet

There is one tab corresponding to the each of the sections of this document: Multiple, NETSO, BSCCo Ltd, FAA, Stage 2, Internal. The NGC tab shows the structure of the files sent from the NETSO to BMRA and SAA (this information is mastered in [NGCSPEC]). The Items tab is the master definition of each item; the item definitions in the CRA, ECVAA, CDCA and SAA tabs are copied from there. Note that the NGC tab uses different data types: standard Oracle types are used, except for datetime which is defined as “YYYYMMDDHHMM”.

1.1.5 File names

The names of the files received from the NETSO are given in [NGCSPEC]. The names of the files received from and sent to SVAA follow the following convention:

character 1: Sender role code (Pool format)

characters 2-5: Sender participant Id (Pool format)

characters 6-14: Unique identifier.

The names of all other files follow the convention given in section 2.2.5 of Part 1.

1.1.6 Unstructured File Format

With the exception of files from the NETSO and files to and from SVAA, the unstructured file format defined in section 2.2.6 of Part I is available.

1.1.7 Acknowledgement Messages and Sequence Numbers

Section 2.2.7, Acknowledgement Messages, of Part I applies to all files except those from the NETSO.

With the exception of files from the NETSO and files to and from Stage 2, section 2.2.8, Use Of Sequence Numbers, of Part 1, applies. Sequence numbers within NGC files are described in 2.1.2.2, NGC File Format.

1.1.8 Time

All times contained in files will be in GMT; however note that the Settlement Calendar uses local time, and hence Settlement Periods are numbered starting at midnight local time.

1.1.9 Valid Sets

This section defines the domains referred to in the repeating structure tables.

Activity

See Part 1, section 2.2.11.1

BMRA Exception Type

One of the values:

‘B’ (Balancing Mechanism Data Incomplete)

‘T’ (Termination or general input file validation error)

BM Unit Type

See Part 1, section 2.2.11.2

Charge Type

One of the values:

‘A’ (Administration Charge)

‘C’ (Daily Party RR Cashflow)

‘D’ (Daily Party RR Instruction Deviation Cashflow)

‘E’ (Energy Imbalance Cashflows)

‘I’ (Information Imbalance Charges)

‘N’ (Non-delivery Charge)

‘R’ (Residual Cashflow Reallocations)

‘B’ (BM Payments)

‘S’ (System Operator Charges)

‘F’ (Daily Virtual Lead Party Compensation Cashflow)

‘G’ (Daily Supplier Compensation Cashflow)

Organisation Type

See Part 1, section 2.2.11.9

Run Type

See Part 1, section 2.2.11.13

2 External Interface Summary

This section provides convenient summary lists of the interfaces by system / party. Note that this section defines the default rules for distribution of reports: copies of other reports may be requested through BSCCo Ltd. using the Flexible Reporting procedure.

2.1 Interfaces by BSC Agent

The interfaces to each Agent are listed in the following tables. Interfaces which are defined in Part 1 are not included in these tables.

2.1.1 BMRA Interfaces

Agent-id	Name	Dir’n	User	Type
BMRA-I002	Balancing Mechanism Data	from	NETSO	Electronic data file transfer, NGC File Format
BMRA-I003	System Related Data	from	NETSO	Electronic data file transfer, NGC File Format
BMRA-I007	SAA/ECVAA Balancing Mechanism Data	to	SAA (I003) ECVAA (I048)	Electronic data file transfer
BMRA-I011	Performance Reports	to	BSCCo Ltd	Manual
BMRA-I012	System Parameters	from	BSCCo Ltd	Manual
BMRA-I013	BMRA BSC Section D Charging Data	to	BSCCo Ltd	Manual
BMRA-I014	Price Adjustment Data	from	NETSO	Automatic
BMRA-I016	Receive Market Index Data Provider Thresholds	from	BSCCo Ltd	Manual
BMRA-I017	Report Market Index Data Provider Thresholds	To	BSCCo Ltd	Manual
BMRA-I018	Publish Credit Default Notices	from	ECVAA (I036)	Electronic data file transfer
BMRA-I020	BM Unit Fuel Type List	from	NETSO	Manual
BMRA-I021	Temperature Reference Data	from	NETSO	Manual
BMRA-I022	Daily Energy Volume Reference Data	from	NETSO	Manual
BMRA-I023	Wind Generation Registered Capacities	from	NETSO	Manual
BMRA-I024¹	Large Combustion Plant Directive Spreadsheet	from	BSCCo Ltd	Manual
BMRA-I025	SO-SO Prices	from	NETSO	Automatic
BMRA-i026	SO-SO Standing Data	from	NETSO	Manual
BMRA-I027	Settlement Report	from	SAA (I014)	Electronic data file transfer
BMRA-I028	Receive REMIT Data	From	NETSO	Electronic data file transfer
BMRA-I029	Receive Transparency Data	From	NETSO	Electronic data file transfer
BMRA-I032	Demand Control Instructions to SVAA	To	SVAA	Electronic data file transfer
BMRA-I033	STOR Availability Window	From	BSCCo	Manual
BMRA-I034	Trading Unit Data	From	SAA (I049)	Electronic data file transfer

2.1.2 CDCA Interfaces

Agent-id	Name	Dir’n	User	Type
CDCA-I016	Metering System Details Request	from	TAA	Manual
CDCA-I020	Site Visit Inspection Report	from	CDCA Site Visit Agent	Manual
CDCA-I022	Distribution Line Loss Factors	From	BSCCo Ltd	Electronic data file transfer
CDCA-I023	Missing Line Loss Factors	To	BSCCo Ltd	Manual
CDCA-I027	Aggregated Interconnector Meter Flow Volumes	to	SAA (I004)	Electronic data file transfer
CDCA-I028	Aggregated BM Unit Metered Volumes	to	SAA (I004)	Electronic data file transfer
CDCA-I032	Data Collection and Aggregation Performance Report	to	BSCCo Ltd	Manual
CDCA-I035	Site Visit Report on Aggregation Rule compliance	from	CDCA Site Visit Agent	Manual
CDCA-I036	GSP Group Take to SAA	to	SAA (I004)	Electronic data file transfer
CDCA-I039	Exchange of information with TAA	to	TAA	Manual
CDCA-I040²	BM Unit ‘Credit Cover’ Meter Volume Data Report	To	ECVAA (I015)	Electronic data file transfer
CDCA-I043	GSP Group Take to SVAA	to	SVAA	Electronic data file transfer, Pool Transfer File Format
CDCA-I049	Total Demand per GSP	to	NETSO	Electronic data file transfer
CDCA-I051	Report Meter Technical Details	to	NETSO	Manual
CDCA-I055	Transfer from SMRS information	from	Transfer Coordinator	Manual
CDCA-I056	Transfer from SMRS report	to	Transfer Coordinator	Manual
CDCA-I057	Transfer to SMRS information	from	Transfer Coordinator	Manual
CDCA-I058	Transfer to SMRS report	to	Transfer Coordinator	Manual
CDCA-I061	Receive System Parameters	From	BSCCo Ltd	Manual
CDCA-I062	Receive Sample Settlement Periods	from	BSCCo Ltd	Manual
CDCA-I063	Metered Volume Data for Sample Settlement Periods	to	BSCCo Ltd	Manual
CDCA-I064	MOA Proving Tests Report	To	BSCCo Ltd	Manual
CDCA-I065	MOA Fault Resolution Report	To	BSCCo Ltd	Manual
CDCA-I066	Demand Control Instructions to CDCA	From	SAA	Via shared database
CDCA-I067	Disconnected CVA BM Units	From	NETSO, Distribution Business	Manual
CDCA-I068	Aggregated BM Unit Disconnection Volumes	To	SAA	Electronic data file transfer

2.1.3 CRA Interfaces

Agent-id	Name	Dir’n	User	Type
CRA-I001	BSC Party Registration Data	From	BSCCo Ltd	Manual
CRA-I004	BSC Service Agent Details	from	BSCCo Ltd	Manual
CRA-I004	BSC Service Agent Details	from	BSC Service Agents	Manual
CRA-I004	BSC Service Agent Details	from	FAA	Manual
CRA-I004	BSC Service Agent Details	from	SVAA	Manual

CRA-I007	Boundary Point and System Connection Point Registration Data	from	NETSO	Manual
CRA-I007	Boundary Point and System Connection Point Registration Data	To	BSCCo Ltd	Manual
CRA-I011	CALF	from	BSCCo Ltd	Manual
CRA-I013	Issue Authentication Report	to	BMRA (I001)	Electronic data file transfer
CRA-I013	Issue Authentication Report	to	ECVAA (I001)	Electronic data file transfer
CRA-I013	Issue Authentication Report	to	SAA (I001)	Automated Interface
CRA-I013	Issue Authentication Report	to	FAA	Electronic data file transfer
CRA-I013	Issue Authentication Report	to	NETSO	Electronic data file transfer
CRA-I013	Issue Authentication Report	to	BSCCo Ltd	Electronic data file transfer
CRA-I014	Registration Report	to	BSCCo Ltd	Manual
CRA-I015	BM Unit and Energy Account Registration Data	to	BMRA (I001)	Electronic data file transfer
CRA-I015	BM Unit and Energy Account Registration Data	to	ECVAA (I001)	Electronic data file transfer
CRA-I015	BM Unit and Energy Account Registration Data	to	SAA (I001)	Automated Interface
CRA-I015	BM Unit and Energy Account Registration Data	to	SVAA	Electronic data file transfer
CRA-I015	BM Unit and Energy Account Registration Data	to	FAA	Electronic data file transfer
CRA-I017	Credit Assessment Export Capability	to	ECVAA (I001)	Electronic data file transfer
CRA-I017	Credit Assessment Export Capability	to	SAA (I002)	Automated Interface
CRA-I019	Registration Data	to	CDCA (I002)	Via shared database
CRA-I020	Operations Registration Report	to	BSCCo Ltd	Electronic data file transfer
CRA-I020	Operations Registration Report	to	NETSO	Electronic data file transfer
CRA-I022	Metering System Details	to	TAA (I015)	Manual
CRA-I023	Issue Registration Transfer Report	to	Transfer Coordinator	Manual
CRA-I028	NGC Standing Data Report	to	BSCCo Ltd	Electronic data file transfer
CRA-I028	NGC Standing Data Report	to	NETSO	Electronic data file transfer
CRA-I029	Transmission Loss Factors	from	BSCCo Ltd	Manual
CRA-I032	CRA Performance Reports	to	BSCCo Ltd	Manual
CRA-I034	Flexible Reporting Request	from	BSCCo Ltd	Manual
CRA-I034	Flexible Reporting Request	from	BSC Service Agent	Manual
CRA-I034	Flexible Reporting Request	from	NETSO	Manual
CRA-I035	CRA BSC Section D Charging Data	to	BSCCo Ltd	Electronic data file transfer
CRA-I036	Notification Agent Termination Request	To	ECVAA (I030)	Manual
CRA-I037	Notification Agent Termination Feedback	From	ECVAA (I031)	Manual
CRA-I038	Transfer from SMRS information	from	Transfer Coordinator	Manual
CRA-I039	Transfer from SMRS report	to	Transfer Coordinator	Manual
CRA-I040	Transfer to SMRS information	from	Transfer Coordinator	Manual
CRA-I041	Transfer to SMRS report	to	Transfer Coordinator	Manual
CRA-I042	Receive Market Index Data Provider Registration Data	From	BSCCo Ltd	Manual
CRA-I043	Receive Exempt Export Registration Data	From	BSCCo Ltd	Manual
CRA-I044	Withdrawals Checklist Request	from	BSCCo Ltd	Manual
CRA-I045	Withdrawing Party Authorisation and Notification Details	from	ECVAA (I047)	Manual
CRA-I046	Withdrawing Party Settlement Details	from	SAA (I037)	Manual
CRA-I047	Withdrawals Checklist	to	BSCCo Ltd	Manual
CRA-I050	GC or DC Breach Estimation Challenge Decision	from	BSCCo Ltd	Manual
CRA-I052	BM Unit Period Metered Volume	From	SAA (I056)	Electronic data file transfer

2.1.4 ECVAA Interfaces

Agent-id	Name	Dir’n	User	Type
ECVAA-I006	Credit Limit Data	from	FAA	Electronic data file transfer
ECVAA-I011	Account bilateral Contract Volume Report	to	SAA (I008)	Electronic data file transfer
ECVAA-I012	MVR Notification Report	to	SAA (I008)	Electronic data file transfer
ECVAA-I015³	Receive BM Unit Credit Cover Meter Volume Data	From	CDCA (I040)	Electronic data file transfer
ECVAA-I016	ECVAA Data Exception Report	to	CRA (I030)	Electronic data file transfer
ECVAA-I016	ECVAA Data Exception Report	to	FAA	Electronic data file transfer
ECVAA-I017	ECVAA Performance Report	to	BSCCo Ltd	Manual
ECVAA-I021	Credit Limit Warning	to	BSCCo Ltd	Manual
ECVAA-I023	ECVAA BSC Section D Charging Data	to	BSCCo Ltd	Electronic data file transfer
ECVAA-I025	Credit Cover Minimum Eligible Amount Report	to	BSCCo Ltd	Manual
ECVAA-I025	Credit Cover Minimum Eligible Amount Report	to	FAA	Manual
ECVAA-I026	Minimum Eligible Amount Request	to	BSCCo Ltd	Manual
ECVAA-I027	Notification of BSC Parties in Section H Default	from	BSCCo Ltd	Manual
ECVAA-I030	Notification Agent Termination Request	from	CRA (I036)	Manual
ECVAA-I031	Notification Agent Termination Feedback	To	CRA (I037)	Manual
ECVAA-I032	Credit Assessment Price	from	BSCCo Ltd	Manual
ECVAA-I033	Credit/Debit Reports	from	SAA (I013)	Electronic data file transfer
ECVAA-I036	Publish Credit Default Notices	to	BMRA (I018)	Electronic data file transfer
ECVAA-I040	Issue Notification System Status Report	to	BSCCo Ltd	Manual
ECVAA-I041	Party Credit Default Authorisation Details	from	BSCCo Ltd	Manual
ECVAA-I047	Withdrawing Party Authorisation and Notification Details	to	CRA (I045)	Manual
ECVAA-I048	Physical Notification Data	from	BMRA (I007)	Electronic data file transfer
ECVAA-I049	Request to remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default	from	BSCCo Ltd	Manual
ECVAA-I050	Remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default Feedback	to	BSCCo Ltd	Manual
ECVAA-I053	Daily Wholesale Market Activity Report	to	SVAA	API

2.1.5 SAA Interfaces

Agent-id	Name	Dir’n	User	Type
SAA-I003	Balancing Mechanism Data	from	BMRA	Electronic data file transfer
SAA-I007	BM Unit Allocated Demand Volume	from	SVAA	Electronic data file transfer, Pool Transfer File Format
SAA-I010	BSCCo Ltd Costs (Redundant)	from	BSCCo Ltd	Electronic data file transfer
SAA-I011	Payment Calendar Data	from	FAA	Manual
SAA-I013	Credit/Debit Reports	to	FAA	Electronic data file transfer
SAA-I013	Credit/Debit Reports	to	ECVAA (I033)	Electronic data file transfer
SAA-I014	Settlement Report	to	NETSO	Electronic data file transfer
SAA-I014	Settlement Report	to	BSCCo Ltd	Electronic data file transfer
SAA-I014	Settlement Report	to	BMRA (I027)	Electronic data file transfer
SAA-I014	Settlement Report	to	EMR Settlement Services Provider	Electronic data file transfer
SAA-I016	Settlement Calendar	to	CDCA (I016)	Via shared database
SAA-I019	BSC Party Performance Reports (Redundant)	to	BSCCo Ltd	Electronic data file transfer
SAA-I020	SAA Performance Reports	to	BSCCo Ltd	Manual
SAA-I023	System Parameters	from	BSCCo Ltd	Manual

SAA-I025	SAA BSC Section D Charging Data	to	BSCCo Ltd	Electronic data file transfer
SAA-I026	Price Adjustment Data	from	NETSO	Automatic
SAA-I027	Report pre-settlement run validation failure	to	BSCCo Ltd	Manual
SAA-I028	Receive settlement run decision	from	BSCCo Ltd	Manual
SAA-I029	Receive settlement run instructions	from	BSCCo Ltd	Manual
SAA-I031	Receive Market Index Data Provider Thresholds	From	BSCCo Ltd	Manual
SAA-I032	Report Market Index Data Provider Thresholds	to	BSCCo Ltd	Manual
SAA-I033	Receive Request for Data Change	from	NETSO	Manual
SAA-I034	Report Recommended Data Change	to	BSCCo Ltd	Manual
SAA-I035	Receive Instruction for Data Change	from	BSCCo Ltd	Manual
SAA-I036	Report Confirmation of Data Change	to	BSCCo Ltd	Manual
SAA-I037	Withdrawing Party Settlement Details	to	CRA (I046)	Manual
SAA-I038	Excluded Emergency Acceptance Pricing Information	from	BSCCo Ltd	Manual
SAA-I039	Send Excluded Emergency Acceptance Dry Run Results	to	BSCCo Ltd	Manual
SAA-I040	Receive Authorisation To Proceed With Full Settlement Run	from	BSCCo Ltd	Manual
SAA-I041	BM Unit SVA Gross Demand Data File	from	SVAA	Electronic data file transfer, Pool Transfer File Format
SAA-I042	BM Unit Chargeable Demand Report	to	EMR Settlement Services Provider	Electronic data file transfer, XML
SAA-I043	Demand Control Instructions to CDCA	to	CDCA	Manual
SAA-I044	Period BM Unit Demand Disconnection Volumes	from	CDCA	Electronic data file transfer
SAA-I045	BM Unit Allocated Disconnection Demand Volume	from	SVAA	Electronic data file transfer, Pool Transfer File Format
SAA-I046	STOR Availability Window	From	BSCCo	Manual
SAA-I049	Trading Unit Data	To	BMRA (I034)	Electronic data file transfer
SAA-I050	Secondary BM Unit Demand Volumes	From	SVAA	Electronic data file transfer
SAA-I051	Secondary BM Unit Supplier Delivered Volumes	From	SVAA	Electronic data file transfer
SAA-I052	Daily Activations Report	To	SVAA	Electronic data file transfer
SAA-I054	Supplier BM Unit Non BM ABSVD	from	SVAA	Electronic data file transfer
SAA-I055	BM Unit Settlement Expected Volume	From	SVAA	Electronic data file transfer
SAA-I056	BM Unit Period Metered Volume	To	CRA (I052)	Electronic data file transfer
SAA-I057	Supplier BM Unit Non-Chargeable Demand	From	SVAA	Electronic data file transfer
SAA-I059	Supplier BM Unit Period Total Gross Non-Final Demand	From	SVAA	Electronic data file transfer
SAA-I060	BM Unit Period Deviation Volume	From	SVAA	Electronic data file transfer

2.2 Interfaces by Corresponding Party

The interfaces to each corresponding party are listed in the following tables. Interfaces which are defined in Part 1 are included in these tables, in italic font.

2.2.1 BSCCo Ltd Interfaces

Dir’n	User	Agent-id	Name	Type
To	NETSO	BMRA-I010	Data Exception Reports	Electronic data file transfer
To	BSCCo Ltd	BMRA-I011	Performance Reports	Manual
from	BSCCo Ltd	BMRA-I012	System Parameters	Manual
To	BSCCo Ltd	BMRA-I013	BMRA BSC Section D Charging Data	Manual
to	BSCCo Ltd	CDCA-I014	Estimated Data Report (Part 1)	Electronic data file transfer
from	BSCCo Ltd	BMRA-I016	Receive Market Index Data Provider Thresholds	Manual
To	BSCCo Ltd	BMRA-I017	Report Market Index Data Provider Thresholds	Manual
from	BSCCo Ltd	BMRA-I024	Large Combustion Plant Directive Spreadsheet⁴	Manual
to	BSCCo Ltd	CDCA-I018	MAR Reconciliation Report (Part 1)	Manual
to	BSCCo Ltd	CDCA-I019	MAR Remedial Action Report (Part 1)	Manual
from	BSCCo Ltd	CDCA-I022	Distribution Line Loss Factors	Electronic data file transfer
To	BSCCo Ltd	CDCA-I023	Missing Line Loss Factors	Manual
To	BSCCo Ltd	CDCA-I032	Data Collection and Aggregation Performance Report	Manual
from	BSCCo Ltd	CDCA-I043	Receive Exempt Export Registration Data	Manual
To	BSCCo Ltd	CDCA-I047	Correspondence Receipt Acknowledgement (Part 1)	Manual
from	BSCCo Ltd	CDCA-I061	Receive System Parameters	Manual
From	BSCCo Ltd	CDCA-I062	Receive Sample Settlement Periods⁵	Manual
To	BSCCo Ltd	CDCA-I063	Metered Volume Data for Sample Settlement Periods	Manual
from	BSCCo Ltd	CRA-I001	BSC Party Registration Data (Part 1)	Manual
to	BSCCo Ltd	CDCA-I064	MOA Proving Tests Report	Manual
to	BSCCo Ltd	CDCA-I065	MOA Fault Resolution Report	Manual
to	BSCCo Ltd	CRA-I001	BSC Party Registration Data (Part 1)	Manual
from	BSCCo Ltd	CRA-I003	BSC Party Agent Registration Data (Part 1)	Manual
from	BSCCo Ltd	CRA-I004	BSC Service Agent Details	Manual
To	BSCCo Ltd	CRA-I007	Boundary Point and System Connection Point Registration Data (Part 1)	Manual
from	BSCCo Ltd	CRA-I011	CALF	Manual
to	BSCCo Ltd	CRA-I013	Issue Authentication Report	Electronic data file transfer
to	BSCCo Ltd	CRA-I014	Registration Report	Manual
to	BSCCo Ltd	CRA-I020	Operations Registration Report	Electronic data file transfer
to	BSCCo Ltd	CRA-I028	NGC Standing Data Report	Electronic data file transfer
from	BSCCo Ltd	CRA-I029	Transmission Loss Factors	Manual
to	BSCCo Ltd	CRA-I032	CRA Performance Reports	Manual
from	BSCCo Ltd	CRA-I034	Flexible Reporting Request	Manual
to	BSCCo Ltd	CRA-I035	CRA BSC Section D Charging Data	Electronic data file transfer
from	BSCCo Ltd	CRA-I042	Market Index Data Provider Registration Data	Manual
from	BSCCo Ltd	CRA-I044	Withdrawals Checklist Request	Manual
to	BSCCo Ltd	CRA-I047	Withdrawals Checklist	Manual
from	BSCCo Ltd	CRA-I050	GC or DC Breach Estimation Challenge Decision	Manual
to	BSCCo Ltd	ECVAA-I017	ECVAA Performance Report	Manual
to	BSCCo Ltd	ECVAA-I021	Credit Limit Warning	Manual
to	BSCCo Ltd	ECVAA-I023	ECVAA BSC Section D Charging Data	Electronic data file transfer
to	BSCCo Ltd	ECVAA-I025	Credit Cover Minimum Eligible Amount Report	Manual
to	BSCCo Ltd	ECVAA-I026	Minimum Eligible Amount Request	Manual
from	BSCCo Ltd	ECVAA-I027	Notification of BSC Parties in Section H Default	Manual
from	BSCCo Ltd	ECVAA-I032	Credit Assessment Price	Manual
to	BSCCo Ltd	ECVAA-I040	Issue Notification System Status Report	Manual
from	BSCCo Ltd	ECVAA-I041	Party Credit Default Authorisation Details	Manual
from	BSCCo Ltd	ECVAA-I049	Request to remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default	Manual
to	BSCCo Ltd	ECVAA-I050	Remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default Feedback	Manual
from	BSCCo Ltd	SAA-I010	BSCCo Ltd Costs (Redundant)	Electronic data file transfer
from	BSCCo Ltd	SAA-I012	Dispute Notification (Part 1)	Manual
to	BSCCo Ltd	SAA-I014	Settlement Report	Electronic data file transfer
To	BSCCo Ltd	SAA-I016	Settlement Calendar (Part 1)	Manual
to	BSCCo Ltd	SAA-I018	Dispute Report (Part 1)	Manual
to	BSCCo Ltd	SAA-I019	BSC Party Performance Reports (Redundant)	Electronic data file transfer
to	BSCCo Ltd	SAA-I020	SAA Performance Reports	Manual
from	BSCCo Ltd	SAA-I023	System Parameters	Manual
To	BSCCo Ltd	SAA-I025	SAA BSC Section D Charging Data	Electronic data file transfer
To	BSCCo Ltd	SAA-I02	Report pre-settlement run validation failure	Manual
From	BSCCo Ltd	SAA-I028	Receive settlement run decision	Manual
From	BSCCo Ltd	SAA-I029	Receive settlement run instructions	Manual
from	BSCCo Ltd	SAA-I031	Receive Market Index Data Provider Thresholds	Manual
to	BSCCo Ltd	SAA-I032	Report Market Index Data Provider Thresholds	Manual
to	BSCCo Ltd	SAA-I034	Report Recommended Data Change	Manual
from	BSCCo Ltd	SAA-I035	Receive Instruction for Data Change	Manual
to	BSCCo Ltd	SAA-I036	Report Confirmation of Data Change	Manual
from	BSCCo Ltd	SAA-I038	Excluded Emergency Acceptance Pricing Information	Manual
to	BSCCo Ltd	SAA-I039	Send Excluded Emergency Acceptance Dry Run Results	Manual
from	BSCCo Ltd	SAA-I040	Receive Authorisation To Proceed With Full Settlement Run	Manual
from	BSCCo Ltd	BMRA-I033	STOR Availability Window	Manual
from	BSCCo Ltd	SAA-I046	STOR Availability Window	Manual

2.2.2 FAA Interfaces

Dir’n	User	Agent-id	Name	Type
from	FAA	CRA-I004	BSC Service Agent Details	Manual
to	FAA	CRA-I013	Issue Authentication Report	Electronic data file transfer
to	FAA	CRA-I015	BM Unit and Energy Account Registration Data	Electronic data file transfer
from	FAA	CRA-I034	Flexible Reporting Request	Manual
from	FAA	ECVAA-I006	Credit Limit Data	Electronic data file transfer
to	FAA	ECVAA-I016	ECVAA Data Exception Report	Electronic data file transfer
to	FAA	ECVAA-I025	Credit Cover Minimum Eligible Amount Report	Manual
from	FAA	SAA-I011	Payment Calendar Data	Manual
to	FAA	SAA-I013	Credit/Debit Reports	Electronic data file transfer

2.2.3 NETSO Interfaces

Dir’n	User	Agent-id	Name	Type
from	NETSO	BMRA-I002	Balancing Mechanism Data	Electronic data file transfer, NGC File Format
from	NETSO	BMRA-I003	System Related Data	Electronic data file transfer, NGC File Format
to	NETSO	BMRA-I010	Data Exception Reports	Electronic data file transfer
from	NETSO	BMRA-I014	Price Adjustment Data	Automatic
from	NETSO	BMRA-I020	BM Unit Fuel Type List	Manual
from	NETSO	BMRA-I021	Temperature Reference Data	Manual
from	NETSO	BMRA-I022	Daily Energy Volume Reference Data	Manual
from	NETSO	BMRA-I023	Wind Generation Registered Capacities	Manual
from	NETSO	BMRA-I025	SO-SO Prices	Automatic
from	NETSO	BMRA-I026	SO-SO Standing Data	Manual
to	NETSO	CDCA-i012	Report Raw Meter Data (Part 1)	Electronic Data File Transfer
to	NETSO	CDCA-I014	Estimated Data Report (Part 1)	Electronic data file transfer
to	NETSO	CDCA-I029	Aggregated GSP Group Take Volumes (Part 1)	Electronic Data File Transfer
to	NETSO	CDCA-I042	BM Unit Aggregation Report (Part 1)	Electronic Data File Transfer
to	NETSO	CDCA-I049	Total Demand Per GSP	Electronic data file transfer
to	NETSO	CDCA-I051	Report Meter Technical Details	Manual
from	NETSO	CRA-I007	Boundary Point and System Connection Point Registration Data	Manual
from	NETSO	CRA-I008	Interconnector Registration Details	Manual
to	NETSO	CRA-I013	Issue Authentication Report	Electronic data file transfer
to	NETSO	CRA-I014	Registration Report (Part 1)	Electronic Data File Transfer
to	NETSO	CRA-I020	Operations Registration Report	Electronic data file transfer
to	NETSO	CRA-I028	NGC Standing Data Report	Electronic data file transfer
from	NETSO	CRA-I034	Flexible Reporting Request	Manual
from	NETSO	SAA-I012	Dispute Notification (Part 1)	Manual
to	NETSO	SAA-I014	Settlement Report	Electronic data file transfer
to	NETSO	SAA-I017	SAA Data Exception Report (Part 1)	Electronic data file transfer
to	NETSO	SAA-I018	Dispute Report (Part 1)	Manual

from	NETSO	SAA-I026	Price Adjustment Data	Automatic
from	NETSO	SAA-I033	Receive Request for Data Change	Manual
to	NETSO	SAA-I036	Report Confirmation of Data Change	Manual
from	NETSO	BMRA-I028	Receive REMIT Data	Electronic data file transfer
from	NETSO	BMRA-I029	Receive Transparency Data	Electronic data file transfer
from	NETSO	BMRA-I036	Receive Replacement Reserve Data	Electronic data file transfer
from	NETSO	P0292	ABS MSID Pair Delivered Volume Notification	Electronic data file transfer, Pool Transfer File Format
to	NETSO	P0293	Rejection of ABS MSID Pair Delivered Volume	Electronic data file transfer, Pool Transfer File Format
to	NETSO	P0294	Confirmation of ABS MSID Pair Delivered Volume	Electronic data file transfer, Pool Transfer File Format
to	NETSO	P0295	ABS MSID Pair Delivered Volume Exception Report	Electronic data file transfer, Pool Transfer File Format

2.2.4 Stage 2 Interfaces

Dir’n	User	Agent-id	Name	Type
to	SVAA	CDCA-I043	GSP Group Take to SVAA	Electronic data file transfer, Pool Transfer File Format
from	SVAA	CRA-I004	Agent Details	Manual
from	SVAA	CRA-I034	Flexible Reporting Request	Manual
to	MDDA	CRA-I015	BM Unit Registration Details	Electronic data file transfer, Pool Transfer File Forma
from	SVAA	SAA-I007	BM Unit Allocated Demand Volume	Electronic data file transfer, Pool Transfer File Format
to	SVAA	SAA-I016	Settlement Calendar (Part 1)	Manual
to	SVAA	SAA-I017	SAA Data Exception Report (Part 1)	Manual
from	SVAA	SAA-I041	BM Unit SVA Gross Demand Data File	Electronic data file transfer, Pool Transfer File Format
to	SVAA	BMRA-I032	Demand Control Instructions to SVAA	Electronic data file transfer, Pool Transfer File Format
From	SVAA	SAA-I045	BM Unit Allocated Demand Disconnection Volume	Electronic data file transfer, Pool Transfer File Format
From	SVAA	SAA-I050	Secondary BM Unit Demand Volumes	Electronic data file transfer, Pool Transfer File Format
From	SVAA	SAA-I051	Secondary BM Unit Supplier Delivered Volumes	Electronic data file transfer, Pool Transfer File Format
To	SVAA	SAA-I052	Daily Activations Report	Electronic data file transfer, Pool Transfer File Format
from	SVAA	SAA-I054	Supplier BM Unit Non BM ABSVD	Electronic data file transfer, Pool Transfer File Format
from	SVAA	SAA-I055	BM Unit Settlement Expected Volume	Electronic data file transfer, Pool Transfer File Format
to	SVAA	P0292	ABS MSID Pair Delivered Volume Notification	Electronic data file transfer, Pool Transfer File Format
to	SVAA	P0293	Rejection of ABS MSID Pair Delivered Volume	Electronic data file transfer, Pool Transfer File Format
to	SVAA	P0294	Confirmation of ABS MSID Pair Delivered Volume	Electronic data file transfer, Pool Transfer File Format
to	SVAA	P0295	ABS MSID Pair Delivered Volume Exception Report	Electronic data file transfer, Pool Transfer File Format
From	SVAA	SAA-I057	Supplier BM Unit Period Non-Chargeable Demand	Electronic data file transfer, Pool Transfer File Format
From	SVAA	SAA-I059	Supplier BM Unit Period Total Gross Non-Final Demand	Electronic data file transfer, Pool Transfer File Format
From	SVAA	SAA-I060	BM Unit Period Deviation Volume	Electronic data file transfer, Pool Transfer File Format

2.2.5 Transfer Coordinator Interfaces

Dir’n	User	Agent-id	Name	Type
To	Transfer Coordinator	CRA-I023	Issue Registration Transfer Report	Manual
from	Transfer Coordinator	CRA-I038	Transfer from SMRS information	Manual
to	Transfer Coordinator	CRA-I039	Transfer from SMRS report	Manual
from	Transfer Coordinator	CRA-I040	Transfer to SMRS information	Manual
to	Transfer Coordinator	CRA-I041	Transfer to SMRS report	Manual
from	Transfer Coordinator	CDCA-I055	Transfer from SMRS information	Manual
to	Transfer Coordinator	CDCA-I056	Transfer from SMRS report	Manual
from	Transfer Coordinator	CDCA-I057	Transfer to SMRS information	Manual
to	Transfer Coordinator	CDCA-I058	Transfer to SMRS report	Manual

2.2.6 Internal Interfaces

From	To	Name	Type
BMRA-I007	SAA-I003	SAA Balancing Mechanism Data	Electronic data file transfer
BMRA-I007	ECVAA-I048	SAA/ECVAA Balancing Mechanism Data	Electronic data file transfer
BMRA-I010	CRA-I030	Data Exception Reports	Electronic data file transfer
CDCA-I027	SAA-I004	Aggregated Interconnector Meter Flow Volumes	Electronic data file transfer
CDCA-I028	SAA-I004	Aggregated BM Unit Metered Volumes	Electronic data file transfer
CDCA-I036	SAA-I004	GSP Group Take to SAA	Electronic data file transfer
CDCA-I040⁶	ECVAA-I015	BM Unit ‘Credit Cover’ Meter Volume Data	Electronic data file transfer
CDCA Site Visit Agent	CDCA-I020	Site Visit Inspection Report	Manual
CDCA Site Visit Agent	CDCA-I035	Site Visit Report on Aggregation Rule compliance	Manual
CRA-I013	ECVAA-I001	Issue Authentication Report	Electronic data file transfer
CRA-I013	SAA-I001	Issue Authentication Report	Electronic data file transfer
CRA-I015	BMRA-I001	BM Unit and Energy Account Registration Data	Electronic data file transfer
CRA-I013	BMRA-I001	Issue Authentication Report	Electronic data file transfer
CRA-I015	ECVAA-I001	BM Unit and Energy Account Registration Data	Electronic data file transfer
CRA-I015	SAA-I001	BM Unit and Energy Account Registration Data	Automated interface
CRA-I017	ECVAA-I001	Credit Assessment Export Capability	Electronic data file transfer
CRA-I017	SAA-I002	Credit Assessment Export Capability	Automated interface
CRA-I019	CDCA-I002	Registration Data	Via shared database
CRA-I036	ECVAA-I030	Notification Agent Termination Request	Manual
ECVAA-I011	SAA-I008	Account bilateral Contract Volume Report	Electronic data file transfer
ECVAA-I012	SAA-I008	MVR Notification Report	Electronic data file transfer
ECVAA-I016	CRA-i030	ECVAA Data Exception Report	Electronic data file transfer
ECVAA-I031	CRA-I037	Notification Agent Termination Feedback	Manual
ECVAA-I036	BMRA-I018	Publish Credit Default Notices	Electronic data file transfer
ECVAA-I047	CRA-I045	Withdrawing Party Authorisation and Notification Details	Manual
SAA-I013	ECVAA-I033	Credit/Debit Reports	Electronic data file transfer
SAA-I016	CDCA-I034	Settlement Calendar (Part 1)	Manual
SAA-i017	CDCA-I050	Data Exception Reports (Part 1)	Electronic data file transfer
SAA-i017	CRA-I030	Data Exception Reports (Part 1)	Electronic data file transfer
SAA-i017	ECVAA-I020	Data Exception Reports (Part 1)	Electronic data file transfer
SAA-I037	CRA-I046	Withdrawing Party Settlement Details	Manual
SAA-I043	CDCA-I066	Demand Control Instructions to CDCA	Manual
SAA-I044	CDCA-I068	Period BM Unit Demand Disconnection Volumes	Electronic data file transfer
SAA-I053	n/a	Daily Exchange Rate Report	Electronic data file transfer
SAA-I056	n/a	Settlement BM Unit Metered Volume	Electronic data file transfer

2.2.7 EMR Settlement Services Provider Interfaces

Dir’n	User	Agent-id	Name	Type
to	EMR Settlement Services Provider	SAA-I014	Settlement Report	Electronic data file transfer
to	EMR Settlement Services Provider	SAA-I042	BM Unit Chargeable Demand Report	Electronic data file transfer, XML

3 Interfaces From and To Multiple Parties

This section covers a number of interfaces which are common to more than one party.

3.1 CRA-I004: (input) BSC Service Agent Details

Interface ID:

CRA-I004

(EPFAL ref FAA-I033)

Source:

BSCCo Ltd, BSC Service Agents, FAA, SVAA

Title:

BSC Service Agent Details

BSC Reference:

CRA SD 4.3, CRA BPM 3.1, ERM, CP756, P82

Mechanism:

Manual, by email, letter or fax, or can be sent as an electronic data file over the network

Frequency:

As Necessary

Volumes:

Low

The CRA shall receive the registration details for BSC Service Agents, including FAA and SVAA. The details will come from BSCCo Ltd in the first place. Updates will come from the agents themselves.

Action Description

Authentication Details

Name

Password

BSC Service Agent Details

Agent Name

Agent Identifier

Service Agent Role Details

Agent Type

Effective From Date

Effective To Date

Role Address Details

Address

Telephone No

Fax No

e-mail Address

Physical Interface Details:

A physical structure is defined for this manual interface because the registrant can send this information as an electronic data file over the network; the CRA operator enters the information via a screen-based interface however it is sent.

3.2 CRA-I013: (output) Issue Authentication Report

Interface ID:

From: CRA-I013

To: BMRA-I001

To: ECVAA-I001

To: SAA-I001

EPFAL Ref: FAA-I025

User:

FAA

ECVAA

SAA

NETSO

BSCCO

Title:

Issue Authentication Report

BSC Reference:

CRA SD App B, Serial 4, CRA BPM 4.11, CRA SD 4.1.1.e, CR12, P78, CP918, CP975

CP1193

Mechanism:

Electronic data file transfer

Frequency:

Daily or additionally as necessary

Volumes:

Low

The CRA system shall issue a report containing the authentication details for a BSC Party or Party Agent. The Authentication details shall consist of:

Authentication Details

BSC Party Details

Action Code

BSC Party Name

BSC Party ID

Party Role Details

Action Code

Party Type

Registration Effective From Date

Registration Effective To Date

Role Address Details

Action Code

Address

Telephone No

Fax No

e-mail Address

Settlement Report Details

Action Code

Report Type

Distribution Method

Authorised Signatories

Action Code

Name

Password

Contact Phone No

e-mail Address

Authorisation Levels

Action Code

Activity

Effective From Date

Effective To Date

BSC Party Agent Details

Action Code

Agent Name

BSC Party Agent ID

Agent Role Details

Action Code

BSC Party Agent Type

Registration Effective From Date

Registration Effective To Date

Role Address Details

Action Code

Address

Telephone No

Fax No

e-mail Address

Authorised Signatories

Action Code

Name

Password

Contact Phone No

e-mail Address

Authorisation Levels

Action Code

Activity

Effective From Date

Effective To Date

Market Index Data Provider Details

Action Code

Market Index Data Provider Name

Market Index Data Provider ID

Market Index Data Provider Effective Dates

Action Code

Provider Effective From Settlement Date

Provider Effective To Settlement Date

The first field of each record of the report is an Action Code, indicating whether the record has a) been added or changed; b) been deleted or c) not changed.

On request the CRA will provide the FAA with copies of sample signatures for Authorised Signatories.

Physical Interface Details:

3.3 CRA-I015: (output) BM Unit, Interconnector and GSP Group Data

Interface ID:

From: CRA-I015

To: SAA-I001

To: BMRA-I001

To: ECVAA-I001

EPFAL Ref: FAA-I026

User:

SAA,

BMRA,

ECVAA

FAA,

Stage 2 MDDA

Title:

BM Unit, Interconnector and GSP Group Data

BSC Reference:

CRA BPM 3.8, SCH: 4, B, 2.5.2 RETA SCH: 4, B, 2.6.1 SAA SD: 2.7, 5.3.1, A1 SAA BPM: 3.1, 4.26, 4.6, CRA BPM 4.14, CP551, P100, P215

Mechanism:

Automated interface to SAA, Electronic Data File transfer to BMRA, ECVAA, FAA, SVAA (Pool Transfer File Format to Stage 2 MDDA)

Frequency:

Daily

Volumes:

Interface Requirement:

The CRA Service shall issue Registration data once a day or more frequently if multiple changes occur to the SAA service viaan automated interface.

The CRA Service shall issue Registration data once a day to the BMRA, ECVAA and FAA services. In this case, the information is transferred via file transfer

The Registration data shall include:

BM Unit, Interconnector and GSP Group Details

Proportion of Losses Details

Action Code

Proportion of Losses (alpha)

Effective From Date

Trading Unit Registration

Action Code

Trading Unit Name

BM Unit Details

Action Code

BM Unit ID

Effective From Date

Effective To Date

BM Unit Registration

Action Code

BM Unit Name

BM Unit ID

BM Unit Type

Lead Party ID

NGC BM Unit Name

GSP Group ID (optional)

GSP Group Name (optional)

Generation Capacity (MW)

Demand Capacity (MW)

Production / Consumption Flag⁷

Transmission Loss Factor (TLF_ij))

FPN Flag

Credit Qualifying Status

Demand in Production Flag

Interconnector ID

Working Day BM Unit Credit Assessment Import Capability(MW)

Non-Working Day BM Unit Credit Assessment Import Capability(MW)

Working Day BM Unit Credit Assessment Export Capability(MW)

Non-Working Day BM Unit Credit Assessment Export Capability(MW)

Effective From Date

Effective To Date

Joint BM Unit Details

Action Code

Joint BM Unit ID

Effective From Date

Effective To Date

Joint BM Unit Details

Action Code

BM Unit ID

Interconnector Registration Details

Action Code

Interconnector ID

Interconnector Administrator ID

Interconnector Error Administrator ID

Effective From Date

Effective To Date

GSP Group Registration

Action Code

GSP Group ID

GSP Group Name

Distributor BSC Party ID

Effective From Date

Effective To Date

The first field of each record of the report is an Action Code, indicating whether the record has a) been added or changed; b) been deleted or c) not changed.

Details of the registration of Stage 2 BM Units are sent to the Stage 2 MDDA; this is shown as CRA-I015 sub-flow 2 in the physical flow definition (Stage 2 section). The flow to Stage 2 will always consist of the complete set of BM Unit / GSP Group / Supplier relationships from the CRA database, and will be sent whenever there is a change. A Change is determined to have happened if the flow generated is not the same as the previously generated flow (generally the flow generated on the previous day).

Sub-flow 2 will summarise contiguous BM Unit effective date ranges as a single record in the flow with an Effective From Date equal that of the earliest record in the contiguous block, and an Effective To Date equal to that of the latest (this may be null for open ended records).

Sub-flow 2 will report historic data for a BM Unit in addition to current and future data.

Physical Interface Details:

3.4 CRA-I020: (output) Operations Registration Report

Interface ID:

CRA-I020

User:

BSCCo Ltd, NETSO

Title:

Operations Registration Report

BSC Reference:

CRA SD A-2, CRA BPM 3.8, CRA BPM 4.10, LDM, RETA SCH 4,B, 2.2.2, P100, CP962, CP642, P215, P310

Mechanism:

Electronic data file transfer

Frequency:

Daily

Volumes:

Low

The CRA system shall issue a report detailing centrally registered data to the BSCCo Ltd.

The report is used to ensure that data held between the BSCCo Ltd and CRA are consistent. The report also goes to the NETSO and shall contain the following information:

Operations Registration Details

Proportion of Losses Details

Action Code

Proportion of Losses (alpha)

Effective From Date

Trading Unit Registration

Action Code

Trading Unit Name

BM Unit Registration

Action Code

BM Unit ID

BM Unit Type

Lead Party ID

NGC BM Unit Name

BM Unit Name

GSP Group ID

GSP Group Name

Trading Unit Name

Generation Capacity (MW)

Demand Capacity (MW)

WDCALF⁸

NWDCALF⁹

SECALF¹⁰

WDBMCAIC

NWDBMCAIC

WDBMCAEC

NWDBMCAEC

Production/Consumption Flag

Production / Consumption Status

Exempt Export Flag

Base TU Flag

Transmission Loss Factor

FPN Flag

Manual Credit Qualifying Flag

Credit Qualifying Status

Interconnector ID

Effective From Date

Effective To Date

BM Unit Group Details

Action Code

Joint BM Unit ID

Effective From Date

Effective To Date

Joint BM Unit Details

Action Code

BM Unit Id

Interconnector Registration Details

Action Code

Interconnector ID

Interconnector Administrator ID

Interconnector Error Administrator ID

Effective From Date

Effective To Date

The first field of each record of the report is an Action Code, indicating whether the record has a) been added or changed; b) been deleted or c) not changed.

Physical Interface Details:

This report can be issued either as an incremental report, containing only changes since the last report, or as a full refresh. The CRA system will issue a full refresh report detailing centrally registered data to the BSCCo Ltd on a weekly basis.

For Incremental reports, changed and deleted records are included (with Action Codes (a) and (b) respectively), but for full report all records are reported, including those that have not changed (Action Code (c)).

Where a BM Unit's association with Trading Units changes on a date where no other BM Unit attributes change, the BM Unit information will be reported as separate date ranges in order to accurately report the association.

Where a BM Unit's Production / Consumption Status changes on a date where no other BM Unit attributes change (for example as a result of another BM Unit being added or removed from the Trading Unit to which the BM Unit belongs), the BM Unit information will be reported as separate date ranges in order to accurately report the changing status.

3.5 CRA-I028: (output) NGC Standing Data Report

Interface ID:

CRA-I028

User:

NETSO, BSCCo Ltd

Title:

NGC Standing Data Report

BSC Reference:

CR_991027_06a

Mechanism:

Electronic data file transfer

Frequency:

As required

Volumes:

Very low volume

The CRA system, shall, on a change of details for BM Unit Names, GSP ID, Boundary Point ID, and Party ID’s, issue a report on the change to the NETSO containing the following.

BSC Party Details

BSC Party ID

BSC Party Name

BM Unit Details

BM Unit ID

BM Unit Name

NGC BM Unit Name

GSP Group Details

GSP Group ID

GSP Group Name

GSP Details

GSP ID

Inter-GSP-Connection Details

Inter-GSP-Connection ID

Boundary Point Details

Boundary Point ID

Metering System Details

Metering System ID

Physical Interface Details:

3.6 ECVAA-I016: (output) ECVAA Data Exception Report

Interface ID:

From: ECVAA-I016

To: CRA-I030

EPFAL Ref: FAA-I024

User:

FAA, CRA

Title:

ECVAA Data Exception Report

BSC Reference:

ECVAA SD: 4.2, 5.2

Mechanism:

Electronic data file transfer

Frequency:

As required.

Volumes:

Low

Interface Requirement:

The ECVAA Service shall issue Exception Reports once a day to the CRA to report registration data validation failures.

The ECVAA Service shall issue Exception Reports as required to the FAA, to report credit limit data validation failures.

The Exception Reports shall include:

File Header of file being processed

Exception Type

Exception Description

3.7 ECVAA-I025: (output) Credit Cover Minimum Eligible Amount Report

This interface is defined in Part 1 of the Interface Definition and Design.

3.8 SAA-I013: (output) Credit/Debit Reports

Interface ID:

SAA-I013

ECVAA-I033

EPFAL Ref:

FAA-I022, FAA-I023

User:

FAA

ECVAA

Title:

Credit/Debit Reports

BSC Reference:

RETA SCH: 4, B, 2.1.1

SAA SD: 3.53.2, 3.54, 4.1, 4.2, A2

SAA BPM: 3.17, 4.14, 4.15

SAA IRR: SAA5, SAA7, SAA8, SAA9, CP527, P2, CP632, P344, P415

Mechanism:

Electronic data file transfer

Frequency:

Daily

Volumes:

One per Settlement Run

Interface Requirement:

The SAA Service shall issue Credit/Debit Reports to the ECVAA Service for all Interim Initial Settlement Runs, and to the FAA Service for all other Settlement Runs.

The Credit/Debit Reports shall include:

Settlement Date

Settlement Run Type

BSC Party ID

Charge Type Indicator (may be one of):

Administration Charge

Energy Imbalance Cashflows

Information Imbalance Charges

Non-delivery Charge

Residual Cashflow Reallocations

Daily Party BM Unit Cashflow

System Operator BM Cashflow

Daily Party RR Cashflow

Daily Party RR Instruction Deviation Cashflow

Daily Virtual Lead party Compensation Cashflow

Daily Supplier Compensation Cashflow

Charge

(Charge Type Indicator and Charge repeated for each charge type and for each BSC Party Id, including parties which have no charges in this run)

Physical Interface Details:

4 Interfaces From and To the NETSO

4.1 BMRA-I002: (input) Balancing Mechanism Data

Interface ID:

BMRA-I002

Source:

NETSO

Title:

Balancing Mechanism Data

BSC Reference:

See verification table, P71, CP921, Variation 60, CP1223, P217, P305

Mechanism:

Electronic data file transfer, NGC File Format

Frequency:

Continuous (as made available from the NETSO)

Volumes:

The Balancing Mechanism data consists of the following files, as defined in the NGC tab of the IDD Part 2 Spreadsheet

Gate Closure Data:

Physical Notification File (PN)

Quiescent Physical Notification File (QPN)

Bid-Offer Data File (BOD)

Declaration Data

Maximum Export Limit File (MELS)

Maximum Import Limit File (MILS)

Run Up Rate Export File (RURE)

Run Up Rate Import File (RURI)

Run Down Rate Export File (RDRE)

Run Down Rate Input File (RDRI)

Notice to Deviate From Zero File (NDZ)

Notice to Deliver Offers File (NTO)

Notice to Deliver Bids File (NTB)

Minimum Zero Time File (MZT)

Minimum Non-Zero Time File (MNZT)

Stable Export Limit File (SEL)

Stable Import Limit File (SIL)

Maximum Delivery Volume File (MDV)

Maximum Delivery Period File (MDP)

For Settlement Dates prior to the P217 effective date this flow shall also include:

Acceptance and Balancing Services Data

Bid-Offer Acceptance Level File (BOAL)

BM Unit Applicable Balancing Services Volume (QAS)

For Settlement Dates after and including the P217 effective date this flow shall also include:

Acceptance and Balancing Services Data

Bid-Offer Acceptance Level Flagged File (BOALF)

BM Unit Applicable Balancing Services Volume (QAS)

For Settlement Dates after and including the P305 effective date this flow shall also include:

Demand Control Instructions

STOR Availability Window

Loss of Load Probability and De-rated Margin Data

Loss of Load Probability

De-Rated Margin

For Settlement Dates after and including the P344 effective date this flow shall also include:

Acceptance and Balancing Services Data

RR Instruction Flag

Physical Interface Details:

Further clarification of the content of the input data from the NETSO is given below:

FPN (& QPN) data will arrive as pairs of points, each pair will have a from & to level and a from & to time.

There will ALWAYS be a pair starting at the beginning of a settlement period

There will ALWAYS be a pair ending at the end of a settlement period

pairs will not overlap

If there is more than one pair for a settlement period, the end time of one pair will be the start time of another (but with possibly different levels to indicate a step function)

Bid-Offer values will arrive as pairs of points, each pair will have a from & to level and a from & to time

For day 1, the from & to level will be the same

the level is relative - i.e. it is the width of the current band, so for BO set 1 the level is the increase from FPN; for set 2 the level is the increase from FPN + level 1

Bid-Offer acceptances are absolute.

The records will be ordered by BM Unit and within this by date / time. For

Bid-Offer Acceptances (BOA), the NETSO initially intends to send each BOA in a

separate file. The BOAL records within the file will be ordered according

to date / time. Note that the NETSO reserves the right to include multiple BOAs per

file; in this case, the records will be ordered by BM Unit, acceptance time

and BOAL date / time.

QAS can be positive or negative and is normally only provided where there is a non-zero volume.

Maximum Import and Export Limit Files can be one of two possible formats: MIL /MEL or MILS/MELS. The MILS and MELS files contain additional information, in the form of a timestamp and a sequence number, which is used to ensure that the data stored and published to parties is correct irrespective of the order in which the data is received. Note: the MEL/MIL format files were operationally discontinued since CP921

4.2 BMRA-I003: (input) System Related Data

Interface ID:

BMRA-I003

Source:

The NETSO

Title:

System Related Data

BSC Reference:

See verification table, P172, P243

Mechanism:

Electronic data file transfer, NGC File Format

Frequency:

Continuous (as made available from the NETSO)

Volumes:

Logical:

The System Related data consists of the following files, as defined in the NGC tab of the IDD Part 2 Spreadsheet:

Indicated Generation File (INDGEN)

Indicated Demand File (INDDEM)

National Demand Forecast File (NDF)

Transmission System Demand Forecast File (TSDF)

Initial Demand Out-Turn File (INDO)

Initial Transmission System Demand Out-Turn File (ITSDO)

National Demand Forecast Day File (NDFD)

Transmission System Demand Forecast Day File (TSDFD)

National Demand Forecast Week File (NDFW)

Transmission System Demand Forecast Week File (TSDFW)

Forecast national Surplus Data for 2-14 days File (OCNMFD)¹¹

Forecast national Surplus Data for 2-52 weeks File (OCNMFW)¹²

Forecast national Surplus Data for 2-156 weeks File (OCNMF3Y)

National Generating Plant Demand Margin, 2-14 Day (OCNMFD2)

National Generating Plant Demand Margin, 2-52 Week (OCNMFW2)

National Generating Plant Demand Margin 2-156 Week (OCNMF3Y2)

National Output Usable, 2-14 Day (NOU2T14D)

National Output Usable by Fuel Type, 2-14 Day (FOU2T14D)

National Output Usable by Fuel Type and BM Unit, 2-14 day (UOU2T14D)

National Output Usable, 2-52 Week (NOU2T52W)

National Output Usable, 2-52 Week (NOU2T3YW)

National Output Usable by Fuel Type, 2-52 Week (FOU2T52W)

National Output Usable by Fuel Type, 2-52 Week (FOU2T3YW)

National Output Usable by Fuel Type and BM Unit, 2-52 Week (UOU2T52W)

National Output Usable by Fuel Type and BM Unit, 2-52 Week (UOU2T3YW)

Indicated Margin File (MELNGC)

Indicated Imbalance File (IMBALNGC)

System Warnings (SYS_WARN)

Temperature Outturn (TEMP)

Wind Forecast (WINDFOR)

Instantaneous Generation by Fuel Type (FUELINST)

Half Hourly Generation by Fuel Type (FUELHH)

Daily Energy Volume (INDOD)

Non-BM STOR Instructed Volumes (NONBM)

Transmission System Frequency (FREQ)

System warnings will be received as a “text block” rather than a boolean flag.

Note that the System Warnings functionality will be utilised, within existing constraints, to report the issuing of all Emergency Instructions, and to notify whether or not each instruction should be treated as an Excluded Emergency Acceptance.

In addition to the files above, from time to time the NETSO provides a System Zone Map (in pdf) and a spreadsheet detailing the mapping between NGC and BM Units, for download from the BMRS.

Physical Interface Details:

In cases where Fuel Type data is unavailable, the affected Fuel Types are omitted from any relevant files submitted to the BMRA by the NETSO.

The System Zone Map and BM Unit mapping spreadsheets are submitted to the BMRA as email attachments sent to the BSC Service Desk.

4.3 BMRA-I010: (output, common) Data Exception Reports

This interface is defined in Part 1 of the Interface Definition and Design.

Sub-flow 2 of BMRA-I010 is used when the exception report relates to adjustment data (NGC030). If enabled by a system parameter, a BMRA-I010 report will also be sent to confirm successful receipt of the adjustment data.

4.4 BMRA-I014: (input) Price Adjustment Data

Interface ID:

BMRA-I014

Source:

The NETSO

Title:

Price Adjustment Data

BSC Reference:

P8, P78, CP1223, P217, P305, P399

Mechanism:

Automatic

Frequency:

continuous

Volumes:

Each file will typically contain the data for one Settlement Date (a file may contain data for a single period, or covering multiple dates). Data for each Settlement Period will normally appear in 2-4 files.

Interface Requirement:

The BMRA Service shall receive the following data from the NETSO via an automatic interface.

Balancing Services Adjustment Data

Settlement Date

Settlement Period (1-50)

EBCA_j (Net Buy-Price Cost Adjustment)(Energy)

EBVA_j (Net Buy-Price Volume Adjustment)(Energy)

SBVA_j(Net Buy-Price Volume Adjustment)(System)

BPA_j (Buy-Price Price Adjustment)

ESCA_j (Net Sell-Price Cost Adjustment)(Energy)

ESVA_j (Net Sell-Price Volume Adjustment)(Energy)

SSVA_j (Net Sell-Price Volume Adjustment)(System)

SPA_j (Sell-Price Price Adjustment)

For Settlement Dates after, and including the P217 effective date, this flow shall also include:

Disaggregated Balancing Services Adjustment Data

Settlement Date

Settlement Period

Balancing Services Adjustment Action ID (unique for Settlement Period)

Balancing Services Adjustment Action Cost (£)

Balancing Services Adjustment Action Volume (MWh)

Balancing Services Adjustment Action SO-Flag (True/False)

For Settlement Dates after, and including the P305 effective date, the Disaggregated Balancing Services Adjustment Data file shall also include:

Balancing Services Adjustment Action STOR Provider Flag (‘T’ or ‘F’)

For Settlement Dates after, and including the P399 effective date, the Disaggregated Balancing Services Adjustment Data file shall also include:

BSAD Party Id

BSAD Asset Id (if applicable)

Tendered Status

Service Type

Balancing Services Adjustment Data for Settlement Dates after, and including the P217 effective date will always have a value of zero for the following data items:

Net Energy Buy Price Cost Adjustment (EBCA) (£)

Net Energy Buy Price Volume Adjustment (EBVA) (MWh)

Net System Buy Price Volume Adjustment (SBVA) (MWh)

Net Energy Sell Price Cost Adjustment (ESCA) (£)

Net Energy Sell Price Volume Adjustment (ESVA) (MWh)

Net System Sell Price Volume Adjustment (SSVA) (MWh)

The BMRA will validate these values and, where they are found to be non-zero, set the values to zero and pass the details of the validation failure to BSCCo.

Physical Interface Details:

This file is in NGC File Format, using Group Definitions NGC32 and NGC36 respectively in the NGC tab of the spreadsheet

Issues:

4.5 BMRA-I020: (input) BM Unit Fuel Type List

Interface ID:

BMRA-I020

Source:

The NETSO

Title:

BM Unit Fuel Type List

BSC Reference:

P220

Mechanism:

Manual, MS Excel Spreadsheet, by email.

Frequency:

As Necessary

Volumes:

Infrequent, generally when new BM Units are added

The BMRA shall receive the BM Unit Fuel Type List containing the following data:

BM Unit Details

NGC BM Unit Name

BM Unit Identifier

Primary Fuel Type

Effective From Date

Effective To Date

Registered Wind Generation Capacity Details

Total Registered Capacity

Effective From Date

Physical Interface Details:

The details described above shall be provided to the BMRA as an MS Excel Spreadsheet.

4.6 BMRA-I021: (input) Temperature Reference Data

Interface ID:

BMRA-I021

Source:

The NETSO

Title:

Temperature Reference Data

BSC Reference:

P220

Mechanism:

Manual, CSV, by email.

Frequency:

Annually

Volumes:

One record per day in a calendar year

The BMRA shall receive the Temperature Reference containing the following data:

Temperature Details

Calendar Date

Normal Reference Temperature

Low Reference Temperature

High Reference Temperature

Physical Interface Details:

The details described above shall be provided to the BMRA as a CSV text file.

4.7 BMRA-I022: (input) Daily Energy Volume Reference Data

Interface ID:

BMRA-I022

Source:

The NETSO

Title:

Daily Energy Volume Reference Data

BSC Reference:

P220

Mechanism:

Manual, CSV, by email.

Frequency:

Annually

Volumes:

One record per day in a calendar year

The BMRA shall receive the Daily Energy Volume Reference containing the following data:

Volume Details

Calendar Date

Normal Reference Volume

Low Reference Volume

High Reference Volume

Physical Interface Details:

The details described above shall be provided to the BMRA as a CSV text file.

4.8 BMRA-I023: (input) Wind Generation Registered Capacities

Interface ID:

BMRA-I023

Source:

The NETSO

Title:

Wind Generation Registered Capacities

BSC Reference:

P220

Mechanism:

Manual, MS Excel Spreadsheet, by email.

Frequency:

As Necessary

Volumes:

Infrequent, generally when new Power Park Modules are added

The BMRA shall receive the Wind Generation Registered Capacities containing the following data:

Power Park Module Details

Power Park Module Identifier

Power Park Module Name

Registered Capacity (MW)

Total Registered Capacity of all Power Park Modules (MW)

Physical Interface Details:

The details described above shall be provided to the BMRA as an MS Excel Spreadsheet.

The effective-from date of the Total Registered Capacity shall be included in the body of the email.

4.9 BMRA-I034: (input) Trading Unit Data

This interface is as defined in the SAA-I049 dataflow.

4.10 CDCA-I012: (output, part 1) Report Raw Meter Data

This interface is defined in Part 1 of the Interface Definition and Design.

4.11 CDCA-I029: (output, part 1) Aggregated GSP Group Take Volumes

This interface is defined in Part 1 of the Interface Definition and Design.

4.12 CDCA-I042: (output, part 1) BM Unit Aggregation Report

This interface is defined in Part 1 of the Interface Definition and Design.

4.13 CDCA-I049: (output) Total Demand per GSP

Interface ID:

CDCA-I049

User:

The NETSO

Title:

Total Demand per GSP

BSC Reference:

CDCA SD 19.5

BPM IRR CDCA8, Clarification CR_991027_06a, CP527, CP559

Mechanism:

Electronic data file transfer

Frequency:

Daily, per aggregation run

Volumes:

Of the order of hundreds of GSPs

Interface Requirement:

Reports on aggregated meter flow volumes for each GSP in each GSP Group are sent to the NETSO, as follows for each GSP Group:

GSP Group Id

Settlement Date

Settlement Run Type

CDCA Run Number

Date of aggregation

GSP Id

Settlement Period

Import/Export indicator (I/E)

Estimate Indicator

Meter Volume

Note that, where one GSP feeds multiple GSP Groups, the data for that GSP will be repeated in the section for each of those GSP Groups, and in each case the total Meter Volume for the GSP will be shown; it will not be apportioned between the GSP Groups.

The Import/Export indicator indicates the direction of the energy flow: the Meter Volume is therefore unsigned.

Physical Interface Details:

4.14 CDCA-I051: (output) Report Meter Technical Details

This interface is defined in Part 1 of the Interface Definition and Design.

4.15 CDCA-I067: (input) Disconnected CVA BM Units

This interface is defined in Part 1 of the Interface Definition and Design.

4.16 CRA-I007: (input/output) Boundary Point and System Connection Point Data

This interface is defined in Part 1 of the Interface Definition and Design.

4.17 CRA-I008: (input) Interconnector Registration Details

This interface is defined in Part 1 of the Interface Definition and Design.

4.18 CRA-I013: (output, common) Issue Authentication Report

This interface is defined in Section 4.

4.19 CRA-I014: (output, part 1) Registration Report

This interface is defined in Part 1 of the Interface Definition and Design. Registration reports for Interconnector registrations will be sent to the NETSO.

4.20 CRA-I020: (output) Operations Registration Report

This interface is defined in Section 4.

4.21 CRA-I028: (output) NGC Standing Data Report

This interface is defined in Section 4.

4.22 SAA-I012 (input, part 1) Dispute Notification

This interface is defined in Part 1 of the Interface Definition and Design.

4.23 SAA-I014 (output) Settlement Report

There are four variants of the Settlement Report. The first and fourth variants are sent to BSC Parties and are defined in Part 1 of the IDD. The second variant is sent to the NETSO and the BMRA and is defined here. The third variant is sent to BSCCo Ltd and is defined in section 7 of this document.

Interface ID:

SAA-I014

User:

The NETSO, BSCCo Ltd

BMRA

Title:

Settlement Report

BSC Reference:

CR_991027_06a, CP527, P8, P18A, CP597, CP610, CP754, CP797, P71, P78, P194, P217,CP1397, P305, P344

Mechanism:

Electronic data file transfer

Frequency:

Daily per settlement run

Volumes:

The first part of the report contains general information:

Settlement Day Information

Settlement Date

Settlement Run Type

SAA Run Number

SAA CDCA Settlement Run Number

SVAA CDCA Settlement Date

SVAA CDCA Settlement Run Number

SVAA SSR Run Number

BSC Party Id

Settlement Period Information (for all Settlement Dates)

Settlement Period (1-50) (j)

System Buy Price SBP_j £/MWh

System Sell Price SSP_j £/MWh

Total Demand (sum of all negative QM_ij)

Total Generation (sum of all positive QM_ij)

Information Imbalance Price 1 (£/MWh)

Information Imbalance Price 2 (£/MWh)

Arbitrage Flag

CADL_d Continuous Acceptance Duration Limit

DMAT_d De Minimis Acceptance Threshold

BPA_j (Buy Price Price Adjustment) (£/MWh)

SPA_j (Sell Price Price Adjustment) (£/MWh)

Total Period Applicable Balancing Services Volume (TQAS_j) (MWh)

Price Derivation Code (PDC_j)

Total NIV Tagged Volume (MWh)

Settlement Period Information (for Settlement Dates prior to the P217 effective date)

EBCA_j (Net Energy Buy Price Cost Adjustment) (£)

EBVA_j (Net Energy Buy Price Volume Adjustment) (MWh)

SBVA_j (Net System Buy Price Volume Adjustment) (MWh)

ESCA_j (Net Energy Sell Price Cost Adjustment) (£)

ESVA_j (Net Energy Sell Price Volume Adjustment) (MWh)

SSVA_j (Net System Sell Price Volume Adjustment) (MWh)

Settlement Period Information (for post P217 Settlement Dates):

Total System Accepted Bid Volume

Total System Accepted Offer Volume

Total System Tagged Accepted Bid Volume

Total System Tagged Accepted Offer Volume

Total System Repriced Accepted Bid Volume

Total System Repriced Accepted Offer Volume

Total System Originally-priced Accepted Bid Volume

Total System Originally-priced Accepted Offer Volume

Total System Adjustment Sell Volume

Total System Adjustment Buy Volume

Total System Tagged Adjustment Sell Volume

Total System Tagged Adjustment Buy Volume

Total System Repriced Adjustment Sell Volume

Total System Repriced Adjustment Buy Volume

Total System Originally-priced Adjustment Sell Volume

Total System Originally-priced Adjustment Buy Volume

Replacement Price

Replacement Price Calculation Volume

Settlement Period Information (for post P305 Settlement Dates, otherwise will be null for Pre P305 dates):

STOR Availability Window Flag

Loss of Load Probability

De-rated Margin

Value of Lost Load

Reserve Scarcity Price

Settlement Period Information (for Effective Dates after the TERRE P344 Final Implementation Date):

GBP EUR Exchange Rate

Balancing Energy Deviation Price

Total System RR Cashflow

RR Aggregated Unpriced System Buy Action Volume

RR Aggregated Unpriced System Sell Action Volumes

Period RR Accepted Offer Volume

Period RR Accepted Bid Volume

Settlement Period Information (for Settlement Dates post P415 Final Implementation Date):

Supplier Sourcing Cost

Market Index Information:

Market Index Data Provider

Individual Liquidity Threshold

Market Index Price

Market Index Volume

Balancing Services Adjustment Action Data (post P217 only):

Balancing Services Adjustment Action Id

Balancing Services Adjustment Action Cost (£)

Balancing Services Adjustment Action Volume

Tagged Balancing Services Adjustment Action Volume

Repriced Balancing Services Adjustment Action Volume

Originally-Priced Balancing Services Adjustment Action Volume

Balancing Services Adjustment Action SO-Flag

Balancing Services Adjustment Action STOR Provider Flag (Post P305 only; will be null for Pre P305 dates)

Trading Unit Period Information:

Trading Unit Name

Total Trading Unit Metered Volume (MWh)

BM Unit Period Information:

BM Unit ID (i)

Trading Unit Name

Period FPN (FPN_ij) (MWh)

BM Unit Metered Volume (QM_ij) (MWh)

Transmission Loss Multiplier (TLM_ij)

BM Unit Applicable Balancing Services Volume (QAS_i) (MWh)

Maximum Export Limit Information:

Time From

Level From (MW)

Time to

Level To (MW)

Maximum Import Limit Information:

Time From

Level From (MW)

Time to

Level To (MW)

The second part of the report is split into a section for each BSC Party. Each such section contains the information sent to the individual party in the “first variant” of the Settlement Report as defined in IDD Part 1:

BSC Party Settlement Date information:

Settlement Date

Settlement Run Type

SAA Run Number

SAA CDCA Settlement Run Number

SVAA CDCA Settlement Date

SVAA CDCA Settlement Run Number

SVAA SSR Run Number

BSC Party Id

Aggregate Party Day Charges (defined in IDD Part 1)

Settlement Period Information:

Settlement Period (1-50) (j)

Aggregate Party Period Charges (defined in IDD Part 1)

System Period Data (defined in IDD Part 1)

System Quarter Hour Data (defined in IDD Part 1)

Account Period Information:

Production/Consumption Flag (a)

Account Period Data (defined in IDD Part 1)

Account Period BMU Information:

BM Unit ID (i)

Account Period BMU Data (defined in IDD Part 1)

BM Unit Period Information:

BM Unit ID

BM Unit Period Data (defined in IDD Part 1)

Trading Unit Name

Total Trading Unit Metered Volume (MWh)

BM Unit RR Data

Supplier BM Unit Non BM ABSVD Data

Period BM Unit Settlement Expected Volume

Secondary BM Unit Deviation Volume

Wholesale Market Proportion of Delivered Volume

Wholesale Market Proportion of Delivered Volume Flag

Period BM Unit Supplier Compensation Volume

Period Secondary BM Unit Compensation Volume

Final Demand

Period Supplier Compensation Cashflow

BM Unit Period FPN Spot Points (^fFPN_it):

Time from

FPN Value from

Time to

FPN Value to

BM Unit Period Bid-Offer Information:

Bid-Offer pair number (n)

Bid-Offer Data (defined in IDD Part 1)

BM Unit Period Bid-Offer Spot Points (^fQBOⁿ_ij):

Time from

Bid-Offer Value from

Time to

Bid-Offer Value to

BM Unit Period Bid-Offer Acceptance (for all Settlement Dates):

Bid-Offer Acceptance number

CADL Flag

BM Unit Period Bid-Offer Acceptance (for post P217 Settlement Dates):

Acceptance SO-Flag

BM Unit Period Bid-Offer Acceptance (for post P305 Settlement Dates, otherwise will be null for Pre P305 dates):

Acceptance STOR Provider Flag

Reserve Scarcity Price Flag

BM Unit Period Bid-Offer Acceptance (for Effective Dates after the TERRE P344 Final Implementation Date):

Acceptance Time

RR Instruction Flag

RR Schedule Flag

BM Unit Period Bid-Offer Acceptance Spot Points (qA^k_it):

Time from

Bid-Offer Acceptance Level Value From

Time to

Bid-Offer Acceptance Level Value To

BM Unit Bid-Offer Pair Acceptance Volume Data (post P217 only):

Bid-Offer Pair Number

Bid-Offer Pair Acceptance Bid Volume

Bid-Offer Pair Acceptance Offer Volume

BM Unit MVR Information:

Subsidiary Party ID and Production/Consumption Flag (a)

MVR Data (defined in IDD Part 1)

Physical Interface Details:

This is sub-flow 2 of the Settlement Report, file id S0142.

For the Interim Initial and Final Reconciliation Settlement Runs, the full set of data is included in the file.

For all other Settlement Runs, certain information is only included if it has been changed: this applies to the

Maximum Export Limit Information, (MEL),
Maximum Import Limit Information (MIL),
BM Unit Period FPN Spot Points (FP2),
BM Unit Period Bid-Offer Spot Points (BO2), and
BM Unit Period Bid-Offer Acceptance Spot Points (BO6).
BM Unit Period Bid-Offer Information (BO4) which is only included where

there are changes to prices or
there are changes to underlying BM Unit Period Bid-Offer Spot Points (BO2)) or
accepted bid or offer volume has been flagged as non-zero (i.e. NZⁿ_i is set) in a previous Settlement Run that occurred on or after 11/3/03 or
where accepted bid or offer volumes are non-zero.

BM Unit Bid-Offer Pair Acceptance Volume Data (BO7)

A ‘change’, as referred to above, is any new data generated since the last full run. For runs SF, R1, R2, and R3, this will be changes since the II run. For the DF run, this will be changes since the RF run. For example: if for an II run of the report the version of a particular data item reported was N, and it had a value of 10, then if for a subsequent R3 run’s report the latest version of same item was now higher (version M, where M > N), then this newer version of the data item would be reported, no matter what the value was (i.e. even if it was now 10 again)

For FP2, BO2 and BO6, it is possible that the change being reported is that the record has been deleted; this is indicated by reporting nulls, e.g.

where there had been a record

BO2|10|123456.789|20|123456.789|

deletion of this record would be shown by

BO2|10||20||

Where a Bid-Offer Acceptance has been wholly or partially deleted, the BO3 record will be present, with the CADL Flag and Acceptance SO-Flag populated as normal. BO6 records relating to the deleted acceptance (or the deleted part of the acceptance, as the case may be) will be included on the report, but with NULL values for the Bid Offer Acceptance Level Value From and Bid Offer Acceptance Level Value To.

For avoidance of doubt, all items relating to Replacement Reserve will be reported for all Settlement Runs.

Note:

SAA CDCA Settlement Run Number

Identifies the CDCA run which generated volumes used directly by SAA in the settlement calculations

For all settlement runs, other than Interim Initial for Settlement Dates prior to the P253 effective date:

SVAA CDCA Settlement Date

SVAA CDCA Settlement Run Number

Identify the CDCA run for Settlement Date which generated the GSP Group Take volumes which were allocated by the SVAA

SVAA SSR Run Number

Identifies the SVAA Run for Settlement Date which generated the SVA BM Unit volumes

For Interim Initial Settlement Runs for Settlement Dates prior to the P253 effective date:

SVAA CDCA Settlement Date

SVAA SSR Run Number

Identify the Settlement Date and Initial Settlement (SF) SVAA Run from which SVA volumes are derived

SVAA CDCA Run Number

Will be zero

4.24 SAA-I017: (output, common) SAA Data Exception Report

This interface is defined in Part 1 of the Interface Definition and Design.

Sub-flow 2 of SAA-I017 is used when the exception report relates to adjustment data (NGC030). If enabled by a system parameter, an SAA-I017 report will also be sent to confirm successful receipt of the adjustment data.

4.25 SAA-I018 (output, part 1) Dispute Report

This interface is defined in Part 1 of the Interface Definition and Design.

4.26 SAA-I026: (input) Price Adjustment Data

Interface ID:

SAA-I026

Source:

Title:

Price Adjustment Data

BSC Reference:

P8, P78, P217, P305, P399

Mechanism:

Automatic

Frequency:

continuous

Volumes:

Interface Requirement:

The SAA Service shall receive the following data from the SO via an automatic interface.

Balancing Services Adjustment Data

Settlement Date

Settlement Period (1-50)

EBCA_j (Net Buy-Price Cost Adjustment)(Energy)

EBVA_j (Net Buy-Price Volume Adjustment)(Energy)

SBVA_j(Net Buy-Price Volume Adjustment)(System)

BPA_j (Buy-Price Price Adjustment)

ESCA_j (Net Sell-Price Cost Adjustment)(Energy)

ESVA_j (Net Sell-Price Volume Adjustment)(Energy)

SSVA_j (Net Sell-Price Volume Adjustment)(System)

SPA_j (Sell-Price Price Adjustment)

For Settlement Dates after, and including the P217 effective date, this flow shall also include:

Disaggregated Balancing Services Adjustment Data

Settlement Date

Settlement Period

Balancing Services Adjustment Action ID (unique for Settlement Period)

Balancing Services Adjustment Action Cost (£)

Balancing Services Adjustment Action Volume (MWh)

Balancing Services Adjustment Action System Flag (True/False)

For Settlement Dates after, and including the P305 effective date, the Disaggregated Balancing Services Adjustment Data file shall also include:

Balancing Services Adjustment Action STOR Provider Flag (True/False)

For Settlement Dates after, and including the P399 effective date, the Disaggregated Balancing Services Adjustment Data file shall also include:

BSAD Party Id

BSAD Asset Id (if applicable)

Tendered Status

Service Type

Balancing Services Adjustment Data for Settlement Dates after, and including the P217 effective date will always have a value of zero for the following data items:

EBCAj (Net Buy-Price Cost Adjustment)(Energy)

EBVAj (Net Buy-Price Volume Adjustment)(Energy)

SBVAj (Net Buy-Price Volume Adjustment)(System)

ESCAj (Net Sell-Price Cost Adjustment)(Energy)

ESVAj (Net Sell-Price Volume Adjustment)(Energy)

SSVAj (Net Sell-Price Volume Adjustment)(System)

The SAA will validate these values and, where they are found to be non-zero, set the values to zero and pass the details of the validation failure to BSCCo.

Physical Interface Details:

Note that this file is in NGC File Format, and uses Group Definitions NGC32 and NGC36 respectively in the NGC tab of the spreadsheet

Issues:

4.27 SAA-I033: (input) Receive Request for Data Change

Interface ID:

SAA-I033

Source:

The NETSO, BSCCo

Title:

Receive Request for Data Change

BSC Reference:

CP995, P172, P448

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

Low

Interface Requirement:

The NETSO shall send to the SAA and BSCCo requests for data change where it is found that the data originally submitted was incorrect or incomplete.

BSCCo may also send to the SAA requests for data change on behalf of the Network Gas Supply Emergency Settlement Validation Committee, where that Committee agrees changes to FPNs, Bid-Offer Data or Acceptance Data relating to a Network Gas Supply Emergency Acceptance.

Where such a request relates to Emergency Instructions, the first line of the instruction should contain the words ‘EMERGENCY INSTRUCTION’. In addition, where the Emergency Instruction is to be treated as an ‘Excluded Emergency Acceptance’, the request will also include the words ‘EXCLUDED EMERGENCY ACCEPTANCE’. Where it is not to be treated as an ‘Excluded Emergency Acceptance’ the words ‘EMERGENCY ACCEPTANCE’ will be included in the request.

Where such a request relates to a Network Gas Supply Emergency Acceptance, the first line of the instruction should contain the words ‘NETWORK GAS SUPPLY EMERGENCY ACCEPTANCE’.

Non Functional Requirement:

Data changes are only applicable to the data types: BOAL, BOD, FPN, QPN and RR.

Issues:

4.28 BMRA-I024: (input) Large Combustion Plant Directive Spreadsheet¹³

Interface ID:

BMRA-I024

Source:

BSCCo

Title:

Large Combustion Plant Directive Spreadsheet

BSC Reference:

P226

Mechanism:

Manual, MS Excel Spreadsheet, by email.

Frequency:

As Necessary

Volumes:

Adhoc

The BMRA shall receive the Large Combustion Plant Directive Spreadsheet containing data (in a single spreadsheet) including:

LCP Unit

A register of BM Units that are part of a LCP Unit under the terms of the Directive

The status of each LCP Unit:

The cumulative operational hours from 1 January 2008 to date for each LCP Unit,

The remaining operational hours for each LCP Unit for Opted Out Plant,

NERP and ELV ‘B Specific Limits’ traded since 1 January 2008 and over the last month,

Derogation applications details for each Opted In LCP Unit applied for, awaiting a decision

Derogation applications details for each Opted In LCP Unit that have been granted,

Emission limits for each Opted In LCP Unit.

Details of notification of breakdown or malfunction of abatement equipment.

The spreadsheet is only to be used within the BMRS as a downloadable file.

Previous versions of the spreadsheet will also be available for download

Physical Interface Details:

The details described above shall be provided to the BMRA as an MS Excel Spreadsheet for download from the BMRS website.

4.29 BMRA-I025: (input) SO-SO Prices

Interface ID:

BMRA-I025

Source:

NETSO

Title:

SO-SO Prices

BSC reference:

CP1333

Mechanism:

Electronic data file transfer, XML

Frequency:

Continuous (as made available from SO)

Volumes:

Up to 20 prices per Interconnector per hour (received as one file per Interconnector per hour) plus occasional resends and corrections of data (up to an extra 10% volume)

Logical:

The BMRA shall receive SO-SO prices in an XML file and will include:

The Resource Provider i.e. the Transmission System Operator (TSO) who is offering the price.
The Acquiring Area and Connecting Area. These codes identify the TSO areas involved in a trade, and are used by the BMRA to identify the Interconnector to which the data relates.
The Resolution. This code identifies the length of the period of time to which the price relates (e.g. 60 minutes).
The Time Interval i.e. the start date and time of the period of time to which the price relates.
The Contract Identification, i.e. a code assigned by the NETSO that identifies a particular offer to increase or reduce flows on the Interconnector.
The Direction (up or down) in which the MW level would change.
The Currency (e.g. EUR or GBP).
The MW level and price.

Physical Interface Details:

This file will be received in a format defined by the XML Schema for Merit Order List documents (published in the ENTSO-E Reserve Resource Planning EDI library). The data items will be as defined in the XML Schema

4.30 BMRA-I026: (input) SO-SO Standing Data

Interface ID:

BMRA-I026

Source:

The NETSO

Title:

SO-SO Standing Data

BSC Reference:

CP1333

Mechanism:

Manual, MS Excel Spreadsheet, by email

Frequency:

As necessary

Volumes:

Infrequent, generally when new trading products are added

Logical:

For reporting purposes, the BMRS associates SO-SO prices with a code (the SO-SO Trade Type) that identifies which Interconnector the price relates to, the Party offering the price, and the length of the time period to which it applies (e.g. 60 minutes).

An appropriate SO-SO Trade Type is automatically allocated to each price received via the SO-SO Prices interface (BMRA-I025), based on the Resource Provider, Acquiring Area, Connecting Area and Resolution associated with that price.

In order to support this process, the BMRA shall receive standing data defining the attributes associated with each SO-SO Trade Type:

SO-SO Trade Type
Resource Provider Code
Connecting Area Code
Resolution Code
Currency
Effective From Date
Effective To Date

Physical Interface Details:

The details described above shall be provided to the BMRA as an MS Excel Spreadsheet.

4.31 BMRA-I028: (input) Receive REMIT Data

This interface is defined in Part 1 of the Interface Definition and Design.

4.32 BMRA-I029: (input) Receive Transparency Regulation Data

Interface ID:

BMRA-I029

Source:

The NETSO

Title:

Transparency Data

BSC reference:

P295

Mechanism:

Electronic data file transfer, XML and PDF

Frequency:

Continuous (as made available from the NETSO)

Volumes:

Logical:

The BMRA shall receive Transparency Regulation Data in the form of XML and PDF files relating to the following categories:

Load
Outages
Transmission
Congestion Management
Generation
Balancing

Each category contains a set of individual articles, each of which is represented by a particular file.

Physical Interface Details:

These files will be received in formats as defined by ENTSO-e. Data items in XML files will be defined in the relevant XML Schemas Definition (XSD) and in accordance to the ENTSO-e’s Manual of Procedures (V2.1); details are available from the Transparency section of the ENTSO-E Website (www.entsoe.eu).

4.33 BMRA-I036: (input) Receive Replacement Reserve Data

Interface ID:

BMRA-I036

Source:

The NETSO

Title:

Replacement Reserve Data

BSC reference:

P344

Mechanism:

Electronic data file transfer, XML

Frequency:

Continuous (as made available from the NETSO)

Volumes:

Logical:

The BMRA shall receive Replacement Reserve data from the NETSO. This data shall comprise:

RR Bids
RR Auction Results, including:
RR Activations
Volume of GB Need Met
Interconnector Schedule Data

Note that RR Instruction data is received via the BMRA-I002 as part of Acceptance and Balancing Services Data.

This data shall be shared with the SAA upon receipt.

Physical Interface Details:

These files will be received in formats as defined by ENTSO-e. Data items in XML files will be defined in the relevant XML Schemas Definition (XSD) and in accordance to the ENTSO-e’s Manual of Procedures; details are available from the ENTSO-E Website (www.entsoe.eu).

4.34 P0292: (input) ABS MSID Pair Delivered Volume Notification

Interface ID:

P0292

Source:

The NETSO

Title:

ABS MSID Pair Delivered Volume Notification

BSC reference:

P354

Mechanism:

Electronic data file transfer, XML

Frequency:

Daily

Volumes:

Logical:

The SVAA shall receive ABS MSID Pair Delivered Volume data from the NETSO. This data shall comprise:

Settlement Date

GSP Group Id

Import MSID

Export MSID ((except where there is no Export MSID in the MSID Pair)

Settlement Period Id

Delivered Volume

Physical Interface Details:

These files will be received in the format defined for the P0292 in the IDD Part 1/2 Spreadsheet

4.35 P0293: (output) Rejection of ABS MSID Pair Delivered Volume

Interface ID:

P0293

User:

The NETSO

Title:

Rejection of ABS MSID Pair Delivered Volume Data

BSC reference:

P354

Mechanism:

Electronic data file transfer, XML

Frequency:

Daily

Volumes:

Logical:

If a P0292 file fails validation, the SVAA shall issue a Rejection of ABS MSID Pair Delivered Volume to the NETSO. This data shall comprise:

Delivered Volume Rejection Reason

Physical Interface Details:

These files will be issued in the format defined for the P0293 in the IDD Part 1/2 Spreadsheet

4.36 P0294: (output) Confirmation of ABS MSID Pair Delivered Volume

Interface ID:

P0294

User:

The NETSO

Title:

Confirmation of ABS MSID Pair Delivered Volume Data

BSC reference:

P354

Mechanism:

Electronic data file transfer, XML

Frequency:

Daily

Volumes:

Logical:

If a P0292 file passes validation, the SVAA shall issue a Confirmation of ABS MSID Pair Delivered Volume Data to the NETSO. This data shall comprise:

Settlement Date

Physical Interface Details:

These files will be issued in the format defined for the P0294 in the IDD Part 1/2 Spreadsheet

4.37 P0295: (output) ABS MSID Pair Delivered Volume Exception Report

Interface ID:

P0295

User:

The NETSO

Title:

ABS MSID Pair Delivered Volume Data

BSC reference:

P354

Mechanism:

Electronic data file transfer, XML

Frequency:

Daily

Volumes:

Logical:

Where it has not been possible for the SVAA to allocate one or more ABS MSID Pair Delivered Volume(s) contained in a P0292 to the MSIDs in the relevant MSID Pair(s), the SVAA shall issue an ABS MSID Pair Delivered Volume Exception Report to the NETSO which shall include details of each relevant MSID Pair Delivered Volume. This data shall comprise:

Settlement Date

GSP Group Id

Import MSID

Export MSID (except where there is no Export MSID in the MSID Pair)

Settlement Period Id

Delivered Volume

Delivered Volume Rejection Reason

Physical Interface Details:

These files will be issued in the format defined for the P0295 in the IDD Part 1/2 Spreadsheet

5 Interfaces From and To FAA

5.1 CRA-I004: (input, common) BSC Service Agent Details

This interface is defined in Section 4.

5.2 CRA-I013: (output, common) Issue Authentication Report

This interface is defined in Section 4.

5.3 CRA-I015: (output, common) BM Unit and Energy Account Registration Data

This interface is defined in Section 4.

5.4 ECVAA-I006: (input) Credit Limit Data

Interface ID:

ECVAA-I006

EPFAL Ref: FAA-I019

Source:

FAA

Title:

Credit Limit Data

BSC Reference:

ECVAA SD: 5, A

ECVAA BPM: 3.3, 4.17

RETA SCH: 4, B, 3.3, CR12

Mechanism:

Electronic data file transfer

Frequency:

Continuous, when credit limit data changes

Volumes:

1 file sent per BSC Party initially.

1 file sent per BSC Party upon change to Credit Limit

Interface Requirement:

The ECVAA Service shall receive Credit Limit data from the FAA Service as and when a BSC Party’s credit limit changes.

Note: Currently the FAA service only operates during normal working hours and therefore Credit Limit data will only be expected during these hours.

The Credit Limit data shall include:

Party Credit Limit Details

BSC Party ID

Effective From Settlement Date

Credit Limit (MWh)

5.5 ECVAA-I016: (output, common) ECVAA Data Exception Report

This interface is defined in Section 4.

5.6 SAA-I011: (input) Payment Calendar Data

Interface ID:

SAA-I011

Source:

BSCCo

Title:

Payment Calendar Data

BSC Reference:

RETA SCH: 4, B, 2.3.1

SAA SD: 2.8, A1

SAA BPM: 3.2, 4.27, CP527

CP1223

Mechanism:

Manual (CSV file delivered as an email attachment, plus hard copy)

Frequency:

Annual

Volumes:

Draft: 1 file per year, CSV file.

Agreed 1 file per year, data file plus hard copy.

Interface Requirement:

The SAA Service shall receive Payment Calendar data annually from the BSCCo.

The Payment Calendar data shall include:

Settlement Date

Settlement Run Type

Notification Date (the date by which SAA must provide the settlement data to the FAA)

Payment Date

Notification Period

Payment Period

5.7 SAA-I013: (output, common) Credit/Debit Reports

This interface is defined in Section 4.

6 Interfaces From and To BSCCo Ltd

6.1 BMRA-I010: (output, common) Data Exception Reports

This interface is defined in Part 1 of the Interface Definition and Design.

6.2 BMRA-I011: (output) Performance Reports

Interface ID:

BMRA-I011

User:

BSCCo Ltd

Title:

Performance Reports

BSC Reference:

BMRA SD B1, B2, B3, B4, B5, B6, B7, P78

Mechanism:

Manual, probably in whole or in part produced using a report-formatting tool.

Frequency:

Monthly

Volumes:

As required.

Interface Requirement:

The BMRA Service shall issue Performance Reports to the BSCCo Ltd on a monthly basis.

Performance reports shall include the following:

All occurrences of BMRA outages exceeding 30 minutes;
All occurrences of valid registration data not incorporated in BMRA systems within 1 hour of receipt;
All occurrences of valid new or updated system related data not published within 5 minutes of receipt;
All occurrences of valid new balancing mechanism data not published within 5 minutes of receipt;
All occurrences of derived data not published within 15 minutes of settlement period end;
All tested occurrences of high grade BMR service user main screen not loaded within 10 seconds;
All tested occurrences of high grade BMR service user switch screen operations that exceed 1 second;
All tested occurrences of high grade BMR service user data downloads that do not begin within 1 minute of request.

BMRA will report on the performance of the Market Index Data Providers. This performance data will include the following information:

Month Ending Date

Market Index Data Provider Identifier

Number of Settlement Periods for which Market Index Data was not provided

Number of Settlement Periods where Individual Liquidity Threshold required default by BMRA

Number of Settlement Periods where zeroes were used in Indicative Calculations

Physical Interface Details:

6.3 BMRA-I012: (input) System Parameters

Interface ID:

BMRA-I012

Status:

Mandatory

Title:

System Parameters

BSC Reference:

CR 003, P10, P18A, P194, P217, P305

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

Low – typically one or two per month

Interface Requirement:

The BMRA Service shall receive the following system parameters from the BSCCo Ltd via a manual interface, expected to be either a fax or telephone call:

Effective from Settlement Date

Effective from Settlement Period (1-50)

Effective to Settlement Date

Effective to Settlement Period (1-50)

ETLMO+

ETLMO-

Arbitrage Flag

NRL_j (Notional Reserve Limit) (MW)

DMAT_d (De Minimis Acceptance Threshold) (MWh)

CADL_d (Continuous Acceptance Duration Limit (minutes)

PAR_d (Price Average Reference Volume) (MWh) (0-9,999,999,999)

RPAR_d (Replacement Price Average Reference Volume) (MWh)

VoLL (Value of Lost Load) (£/MWh)

Physical Interface Details:

The BSCCo Ltd system parameter values shall continue to apply to all settlement periods, until a change to a parameter is made.

Issues:

6.4 BMRA-I013: (output) BMRA BSC Section D Charging Data

Interface ID:

BMRA-I013

User:

BSCCo Ltd

Title:

BMRA BSC Section D Charging Data

BSC Reference:

CR 65, CN160

Mechanism:

Manual

Frequency:

Monthly

Volumes:

Interface Requirement:

The system shall, on the 15^th working day of each month, collect information required for charging BSC parties under Section D of the Code and send this to BSCCo Ltd.

The information included shall be:

Month

Participant Id

Participant Name

Count of Physical lines installed

Count of Comms Base Software (up to 5 users)

Count of Comms additional Software (each additional user)

Each month the information will be produced for both the previous calendar month and the month before that. Data used shall be the latest available data from Interim Run and Initial Run only

Physical Interface Details:

6.5 CDCA-I014: (output, part 1) Estimated Data Report

This interface is defined in Part 1 of the Interface Definition and Design.

6.6 BMRA-I016: (input) Receive Market Index Data Provider Thresholds

Interface ID:

BMRA-I016

Source:

BSCCo

Title:

Receive Market Index Data Provider Thresholds

BSC Reference:

P78

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

This manual flow is expected to handle a maximum of 6 date ranges to be defined, for each MIDP, for each year. Each date range to have a maximum of 4 different Liquidity Thresholds.

Interface Requirement:

The BMRA shall receive Market Index Data Provider Liquidity Threshold data from BSCCo. The processing rules for this flow are described in BMRA-F008.

The flow shall include:

Market Index Data Provider Identifier

MIDP Date Range

Action Type

Effective From Settlement Date

Effective To Settlement Date

MIDP Period Data

Effective From Settlement Period (1-50)

Effective To Settlement Period (1-50)

Liquidity Threshold

Action Type describes the type of operation to be performed in relation to the data supplied in the other fields. It can be one of:

Insert;
Update;
Delete.

Physical Interface Details:

Issues:

6.7 BMRA-I017: (output) Report Market Index Data Provider Thresholds

Interface ID:

BMRA-I017

User:

BSCCo

Title:

Report Market Index Data Provider Thresholds

BSC Reference:

P78

Mechanism:

Manual

Frequency:

In response to BMRA-I016, as described in BMRA-F008

Volumes:

This manual flow is expected to handle a maximum of 6 date ranges to be defined, for each DP, for each year. Each date range to have a maximum of 4 different Liquidity Thresholds.

Interface Requirement:

The BMRA shall report Market Index Data Provider Liquidity Threshold to BSCCo.

The flow shall include:

Market Index Data Provider Identifier

MIDP Date Range

Effective From Settlement Date

Effective To Settlement Date

MIDP Period Data

Effective From Settlement Period (1-50)

Effective To Settlement Period (1-50)

Liquidity Threshold

Physical Interface Details:

Issues:

6.8 CDCA-I018: (output, part 1) MAR Reconciliation Report

This interface is defined in Part 1 of the Interface Definition and Design.

6.9 CDCA-I019: (output, part 1) MAR Remedial Action Report

This interface is defined in Part 1 of the Interface Definition and Design.

6.10 CDCA-I022: (input) Distribution Line Loss Factors

The BSC Parties send the Distribution Line Loss Factors to the BSCCo Ltd for validation, then the BSCCo Ltd sends them on to CDCA via this interface:

Interface ID:

CDCA-I022

Source:

BSCCo Ltd

Title:

Distribution Line Loss Factors

BSC Reference:

CDCA SD 15.1

CDCA BPM 4.5 (?), CP548

Mechanism:

Electronic data file transfer

Frequency:

Annually

Volumes:

17568000 factors

(1000 metering systems * 366 * 48)

Interface Requirement:

The CDCA receives Line Loss Factors relating to a Metering System from BSCCo Ltd.

Metering System Identifier

Settlement Date

Settlement Period

Line loss Factor

Note that each instance of the flow may contain up to 200000 records, and that it is legal for replacement data to be provided where necessary.

Physical Interface Details:

6.11 CDCA-I023: (output) Missing Line Loss Factors

Interface ID:

CDCA-I023

User:

BSCCo Ltd

Title:

Missing Line Loss Factors

BSC Reference:

CDCA SD 15.2, CP527

Mechanism:

Manual

Frequency:

Monthly, covering a period of four months from the run date

Volumes:

17520000 factors

(1000 metering systems * 365 * 48)

Interface Requirement:

The CDCA shall validate such Line Loss Factors received from the BSCCo Ltd. Any missing or invalid factor values will be reported back to the BSCCo Ltd.

Attributes are likely to include:

File Reference for Line Loss Factors

Date LLF File Received

File Acceptance Status (all accepted, partially accepted, file rejected)

Date of Acceptance Status

File Rejection Reason (if File Acceptance Status = file rejected)

Details of any individual exceptions:

Metering System Identifier (for site specific Line Losses)

Settlement Date

Time Period

Line Loss Factor

Reason for rejection

Physical Interface Details:

6.12 CDCA-I032: (output) Data Collection and Aggregation Performance Report

Interface ID:

CDCA-I032

User:

BSCCo Ltd (Customer)

Title:

Data Collection and Aggregation Performance Report

BSC Reference:

CDCA SD 19.6

CP1153

Mechanism:

Manual, probably in whole or in part produced using a report-formatting tool.

Frequency:

As below

Volumes:

Interface Requirement:

CDCA shall provide performance reports on the data collection and data aggregation functions to the BSCCo Ltd.

These shall include:

Monthly, or immediately if service level falls below agreed level for each item:

Percentage of total number of Outstation Channels interrogated;

Percentage of total number of Outstation Channels successfully read by agreed time [eg 09:00 at Day+1];

Percentage of data needing to be estimated that was created in time for Interim Initial Settlement;

Percentage of data needing to be estimated that was agreed with BSC Party in time for Initial Settlement;

Percentage of raw meter data sent to relevant BSC Party by agreed time [eg 13:00 on Day+1];

Percentage of aggregated meter data which included estimates sent to SAA for Interim Initial Settlement;

Percentage of aggregated meter data which included estimates sent to SAA for Initial Settlement;

Monthly:

Percentage of changed metered data reported to SAA in time for next Settlement Run for relevant Settlement Day;

Percentage of occasions where Site appointments were kept on agreed date and time;

Percentage of occasions where help desk queries were registered to agreed timescales;

Percentage of occasions where help desk queries were responded to within agreed timescales according to severity level;

Percentage of occasions where help desk queries were resolved to agreed timescales.

Quarterly:

Percentage of responses to MOA for Proving Test requests given by agreed time [eg 5 working days] for remote tests;

Percentage of responses to MOA for Proving Test requests given by agreed time [eg 1 working day] for local tests;

Percentage of suspected metering system faults notified to MOA within agreed time [eg 1 working day];

Percentage of MAR data and reports issued to BSC Party within agreed timescales [eg three, six or twelve months for a given metering system; refer to CDCA-F013 for details];

Percentage of reports issued in complete, accurate and correct format to BSC Parties and SAA over the period;

Quarterly, or immediately if service level falls below agreed level for each item:

Percentage of Proving Test results sent to MOA within agreed time [eg 1 working day] of completion;

By exception and confirmed monthly:

Percentage of cases where receipt of information from a BSC Party is confirmed back to Party within agreed timescales [eg 15 minutes for data received electronically];

Percentage of cases where information received from CRA or a BSC Party is processed within agreed timescales;

Physical Interface Details:

6.13 CDCA-I047: (output, part 1) Correspondence Receipt Acknowledgement

This interface is defined in Part 1 of the Interface Definition and Design

6.14 CDCA-I061 (input) Receive System Parameters

Interface ID:

CDAA-I061

Status:

Mandatory

Title:

System Parameters

BSC Reference:

CP751

Interface Requirement:

The CDCA Service shall receive the following system parameters from the BSCCo Ltd via a manual interface, expected to be either a fax or telephone call:

Primary/Secondary Time-Shift Factor

Physical Interface Details:

The BSCCo Ltd system parameter values shall continue to apply to all settlement periods, until a change to a parameter is made.

Issues:

6.15 CDCA-I062: (input) Receive Sample Settlement Periods¹⁴

Interface ID:

CDCA-I062

Source:

BSCCo Ltd

Title:

Receive Sample Settlement Periods

BSC Reference:

P82

Mechanism:

Manual

Frequency:

Annually

Volumes:

600 periods

Interface Requirement:

CDCA shall receive the specification of all Load Periods and Sample Settlement Periods for the latest Reference Year from BSCCo Ltd, via a manual interface.

CDCA shall receive the data for the latest Reference Year, no later than 5 October in the current BSC Year.

The following information shall be included in the interface:

Reference Year

Load Period Name

Settlement Date

Sample Settlement Period

Total Number of Sample Settlement Periods in Load Period

Total Number of Settlement Periods in Load Period

Physical Interface Details:

A physical structure is defined for this manual interface because it will be processed automatically.

6.16 CDCA-I063: (output) Metered Volume Data for Sample Settlement Periods

Interface ID: CDCA-I063	User: BSCCo	Title: Metered Volume Data for Sample Settlement Periods	ITT reference: P350
Mechanism: Manual	Frequency: Annually	Volumes: 450,000 volumes (600 Sample Settlement Periods * 750 Volume Aggregation Units¹⁵)
Interface Requirement:
CDCA shall send Metered Volume Data for Sample Settlement Periods to BSCCo. The following information shall be included in the interface: Header Reference Year Grid Supply Point Metered Volume Data Grid Supply Point Identifier Settlement Date Settlement Period Metered Volume Interconnector Metered Volume Data Interconnector Identifier Settlement Date Settlement Period Metered Volume BM Unit Metered Volume Data BM Unit Identifier Settlement Date Settlement Period Metered Volume The Metered Volume data will be signed to indicate the direction of energy flow; a positive sign indicates export on to the system and a negative sign indicates import from the system.
Physical Interface Details: A physical structure is defined for this manual interface because it will be processed automatically. The field delimiter will be a single comma (i.e. CSV format) with no comma at the end of a line. A header and footer record will be included in the file, as follows: Header Information
Record Type		Fixed String “HDR”
Reference Year		String YYYY-YYYY
Creation Datetime		String YYYYMMDDHHMISS
Footer Information
Record Type		Fixed String “FTR”
Body Record Count		Count of body records

6.17 CDCA-I064: (output) MOA Proving Tests Report

Interface ID: CDCA-I064	User: BSCCo Ltd	Title: MOA Proving Tests Report		BSC Reference: P99
Mechanism: Manual	Frequency: Monthly	Volumes: Low
Interface Requirement:
CDCA shall report the following information to the BSCCo, after the end of every month: Participant Header Market Sector Market Participant Role Code Meter Operator Agent Id Period End Date Periodicity CVA MOA Serial 1 Data GSP Group ID Number of MSIDs for which Proving Test outstanding Average number of business days for which Proving Test is outstanding after scheduled date of Proving Test, at time of report Count of faults outstanding after scheduled date of Proving Test The report shall be produced in POOL file format, and sent to the BSCCo (as an email attachment) no later than 7 Business Days after the end of the month to which the data pertains.
Physical Interface Details: The filename shall be CDCA133<last digit of the year number>.<MON>, where <MON> is the reporting month (e.g. JAN, FEB, etc.). See the physical flow for details, in the BSCCo Ltd tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Type			='P0133001'
From Role Code			=’Z’
From Participant Id			= 'CDCA'
To Role Code			='Z'
To Participant Id			='POOL''
Creation Time			date and time (local) of file generation YYYYMMDDHHMISS

6.18 CDCA-I065: (output) MOA Fault Resolution Report

Interface ID: CDCA-I065	User: BSCCo Ltd	Title: MOA Fault Resolution Report		BSC Reference: P99
Mechanism: Manual	Frequency: Monthly	Volumes: Low
Interface Requirement:
CDCA shall report the following information to BSCCo Ltd, after the end of every month: Participant Header Market Sector Market Participant Role Code Meter Operator Agent Id Period End Date Periodicity CVA MOA Serial 2 Data GSP Group ID Number of MSIDs with fault Count of faults identified Average number of business days faults outstanding Average number of business days taken to resolve fault The report shall be produced in POOL file format, and sent to BSCCo Ltd (as an email attachment) no later than 7 Business Days after the end of the month to which the data pertains.
Physical Interface Details: The filename shall be CDCA134<last digit of the year number>.<MON>, where <MON> is the reporting month (e.g. JAN, FEB, etc.). See the physical flow for details, in the BSCCo Ltd tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Type			='P0134001'
From Role Code			=’Z’
From Participant Id			= 'CDCA'
To Role Code			='Z'
To Participant Id			='POOL''
Creation Time			date and time (local) of file generation YYYYMMDDHHMISS

6.19 CRA-I001: (input & output, part 1) BSC Party Registration Data

This interface is defined in Part 1 of the Interface Definition and Design.

6.20 CRA-I003: (input, part 1) BSC Party Agent Registration Data

This interface is defined in Part 1 of the Interface Definition and Design.

6.21 CRA-I004: (input, common) BSC Service Agent Details

This interface is defined in Section 4.

6.22 CRA-I009: (input) Receive Manual Credit Qualifying Flag (Redundant)

Interface ID:

CRA-I009

Source:

BSCCo Ltd

Title:

Manual Credit Qualifying Flag

BSC Reference:

P215, P394

Mechanism:

Manual, by email, letter or fax

Frequency:

As necessary

Volumes:

The CRA shall receive, from time to time the Manual Credit Qualifying Flag for a BM Unit from

BSCCo Ltd. The information shall contain:

Credit Qualifying Details

BM Unit Id

Manual Credit Qualifying Flag (True/False)

Effective From Date

Effective To Date (can be undefined)

This interface is not in use following P394 implementation.

Physical Interface Details:

6.23 CRA-I011: (input) Credit Assessment Load Factors

Interface ID:

CRA-I011

Source:

BSCCo Ltd

Title:

CALF

BSC Reference:

CRA SD 5.0, CRA BPM 3.5, CRA 4.5, ERM, RETA SCH 4,B, 2.4.2, CR 12, CP756, P310

Mechanism:

Manual, by email, letter or fax

Frequency:

As necessary

Volumes:

approximately 4 times per year

The CRA shall receive, from time to time the Credit Assessment Load Factors from the BSCCo Ltd. The information shall contain:

Action Description

Authentication Details

Name

Password

BM Unit Credit Assessment Load Factor Details

BM Unit Id

Working Day Credit Assessment Load Factor (WDCALF_i)

Non-Working Day Credit Assessment Load Factor (NWDCALF_i)

Supplier Export Credit Assessment Load Factor (SECALF_i)

Secondary Credit Assessment Load Factor (SCALF)

Effective From Date

Physical Interface Details:

6.24 CRA-I020: (output, common) Operations Registration Report

This interface is defined in Section 4.

6.25 CRA-I028: (output) NGC Standing Data Report

This interface is defined in Section 4.

6.26 CRA-I029: (input) Transmission Loss Factors

Interface ID:

CRA-I029

Source:

BSCCo Ltd

Title:

Transmission Loss Factors

BSC Reference:

SAA SD: 2.6, A1

SAA BPM: 3.6, CP756

Mechanism:

Manual, by email, letter or fax

Frequency:

As required

Volumes:

Very low volume

Interface Requirement:

The CRA Service shall receive Transmission Loss data from BSCCo Ltd from time to time.

The Transmission Loss data shall contain the following details:

Authentication Details

Name

Password

Transmission Loss Details

Proportion of Losses (alpha)

Effective From Date

BM Unit Transmission Loss Details

BM Unit ID

Transmission Loss Factor¹⁶

Effective from Date

Effective to Date

6.27 CRA-I032: (output) CRA Performance Reports

This interface is defined in the CRA URS as a functional requirement rather than an interface requirement. The reference in the CRA URS is CRA-F027.

6.28 CRA-I034: (input) Flexible Reporting Request

Interface ID:

CRA-I034

Source:

BSCCo Ltd

Title:

Flexible Reporting Request

BSC Reference:

CR 53, CP756

Mechanism:

Manual, by email, letter or fax

Frequency:

Volumes:

Interface Requirement:

The CRA shall receive authorisations from BSCCo Ltd. to start or stop sending copies of a BSC Party report to another BSC Party.

Requesting BSC Party Details

BSC Party Id

BSC Party type

Report Details

Report Type

BSC Party Id

BSC Party type

Start/Stop Flag

Physical Interface Details:

The flow may contain requests from one or more BSC Parties, and each request may cover a number of report types/BSC Parties.

6.29 CRA-I035: (output) CRA BSC Section D Charging Data

Interface ID:

CRA-I035

User:

BSCCo Ltd

Title:

CRA BSC Section D Charging Data

BSC Reference:

CR 65, CN160, P100

Mechanism:

Electronic data file transfer

Frequency:

Monthly

Volumes:

Interface Requirement:

The system shall, on the 15^th working day of each month, collect information required for charging BSC parties under Section D of the Code and send this to BSCCo Ltd.

The information included shall be:

Month

Participant Id

Participant Name

Count of CVA Metering Systems

Count of CVA BM Units

Count of CVA Exempt Export BM Units

Count of Secondary BM Units

Count of SVA Base BM Units

Count of SVA additional BM Units

Count of SVA Replacement Base BM Units

Count of SVA Replacement additional BM Units

Count of SVA Exempt Export BM Units

Each month the information will be produced for both the previous calendar month and the month before that. Data used shall be the latest available data from Interim Run and Initial Run only.

Physical Interface Details:

6.30 CRA-I042: (input) Receive Market Index Data Provider Registration Data

Interface ID:

CRA-I042

Source:

MIDP

Title:

Receive Market Index Data Provider Registration Data

BSC Reference:

P78

Mechanism:

Manual

Frequency:

As Necessary

Volumes:

Low

Interface Requirement:

Both initial registration, and updates to details, of a Market Index Data Provider, will be done by BSCCo Ltd.

The CRA shall receive Market Index Data Provider Details including the following:

Action Description

Market Index Data Provider Details

Market Index Data Provider Name

Market Index Data Provider Identifier

Provider Effective From Settlement Date

Provider Effective To Settlement Date

Contact Details

Name

Address

Telephone No

Fax No

e-mail Address

Physical Interface Details:

6.31 CRA-I043: (input) Receive Exempt Export Registration Data

Interface ID:

CRA-I043

Source:

BSCCo Ltd

Title:

Receive Exempt Export Registration Data

BSC Reference:

P100

Mechanism:

Manual, by email, letter or fax

Frequency:

As necessary

Volumes:

Low

CRA shall receive the Exempt Export registration details for a BM Unit from BSCCo Ltd via a manual interface.

The flow shall include the following:

BM Unit Details

BSC Party Id

BM Unit Id

Exempt Export Registration

Effective From Settlement Date

Or,

Exempt Export De-Registration

Effective To Settlement Date

Physical Interface Details:

6.32 CRA-I044: (input) Withdrawals Checklist Request

Interface ID:

CRA-I044

Source:

BSCCo Ltd

Title:

Withdrawals Checklist Request

BSC Reference:

CP974

Mechanism:

Manual, by email or fax

Frequency:

Ad hoc

Volumes:

Low

The CRA shall receive a request for the Withdrawals Checklist from BSCCo Ltd on an ad-hoc basis. The request shall contain the following information:

BSC Party / BSC Party Agent Name, and / or BSC Party / BSC Party Agent Id

Reason for request

Withdrawal Date (optional)

Notes:

Valid reasons for requesting the Withdrawals Checklist shall be defined as (not exclusively):

Information
Final Compliance

The Withdrawal Date shall optionally be included in a request, as an indication of when the 'Final Compliance' report should be run. If included, the CRA shall run the 'Final Compliance' report at 5pm, two Working Days prior to the Withdrawal Date. In this case, there is no need for the BSCCo to submit a specific request for the 'Final Compliance' report, but on the morning of the day that the report is due, the BSCCo shall confirm that the report is required.

Physical Interface Details:

6.33 CRA-I047: (output) Withdrawals Checklist

Interface ID:

CRA-I047

User:

BSCCo Ltd

Title:

Withdrawals Checklist

BSC Reference:

CP974

Mechanism:

Manual, by email or fax

Frequency:

On request

Volumes:

Low

The CRA shall issue a Withdrawals Checklist on receipt of a request from BSCCo Ltd (via Interface Requirement CRA-I044). The report shall contain the following data:

Report Date

Reason for Request

Registration Details

Participation capacities registered

BSC Party / BSC Party Agent Name

BSC Party / BSC Party Agent Id

Market Role Code(s)

Effective From Date

Effective To Date

BM Units registered

BM Unit ID

Effective From Date

Final Effective To Date

Metering Systems registered

MSID

Effective From Date

Final Effective To Date

Communication Lines

High-grade or low-grade line

Own or shared line

FTP accounts/ Encryption keys to be terminated.

Access to BSC Central Systems terminated effective from

Report non deliveries set up for BSC Party/ BSC Party Agent

Flow Type

Effective From Date

Effective To Date

Trading Details

Last Day of Trading

Payment date of the RF run for the Last Day of Trading (if known)

Settlement Details

As received via Interface Requirement CRA-I046

Authorisation and Notification Details

As received via Interface Requirement CRA-I045

Physical Interface Details:

6.34 CRA-I050: GC or DC Breach Estimation Challenge Decision

Interface ID:

CRA-I050

User:

BSCCo

Title:

GC or DC Breach Estimation Challenge Decision

BSC reference:

P359

Mechanism:

Manual

Frequency:

As required

Volumes:

low

Interface Requirement:

Where a BSC Party has Challenged a GC or DC Breach Estimation for a BM Unit, the CRA shall receive details of BSCCo’s decision:

BM Unit Id

Type of GC or DC Breach

Settlement Day

Settlement Period

Decision Type (Upheld or Rejected)

BSCCo-estimated GC or DC Amount*

Effective From Date for BSCCo-estimated GC or DC Amount*

*For an Upheld Challenge only

Physical Interface Details:

6.35 ECVAA-I017: (output) ECVAA Performance Report

Interface ID:

ECVAA-I017

User:

BSCCo Ltd

Title:

ECVAA Performance Report

BSC Reference:

ECVAA SD: B

ECVAA IRR: E6

CR 12, CP519

Mechanism:

Manual, probably in whole or in part produced using a report-formatting tool.

Frequency:

Monthly

Volumes:

Interface Requirement:

The ECVAA Service shall issue ECVAA Performance Reports once a month to BSCCo Ltd.

Percentage of valid new or updated registration data incorporated in ECVAA systems within 1 day of receipt
Percentage of valid new or updated credit limit data incorporated in ECVAA systems within 1 day of receipt
Percentage of Energy Contract Volume Authorisation requests processed within 1 day of receipt
Percentage of Energy Contract Volume Authorisation termination requests processed within 1 day of receipt
Percentage of Metered Volume Reallocation Authorisation requests processed within 1 day of receipt
Percentage of requests to add additional BM Unit Subsidiaries to an existing Metered Volume Reallocation Authorisation processed within 1 day of receipt
Percentage of Metered Volume Reallocation Authorisation termination requests processed within 1 day of receipt
Percentage of Energy Contract Volume Notifications processed within 15 minutes of receipt
Percentage of valid Energy Contract Volume Notifications aggregated for Settlement Day (SD) and Total Energy Contract Volumes calculated and transmitted to SAA by 12:00 on SD + 2
Percentage of Metered Volume Reallocation Notifications processed within 15 minutes of receipt
Percentage of Metered Volume Reallocation Notifications for SD transmitted to SAA by 12:00 on SD + 2.
Percentage of Half Hourly Credit Check Processes completed within 15 minutes of the Submission Deadline (the notification deadline for the purposes of submitting ECVNs and MVRNs for each Settlement Period as defined in Annex X-1).
Percentage of Credit Cover Minimum Eligible Amount Requests processed by the first Working Day after the expiry of the Waiting Period or the date of receipt of the Minimum Eligible Amount Rule Confirmation from BSCCo Ltd, whichever is the later (see ECVAA-F011: Process Credit Cover Minimum Eligible Amount Request).

6.36 ECVAA-I021: (output) Credit Limit Warning

This interface is defined in Part 1 of the Interface Definition and Design.

6.37 ECVAA-I023: (output) ECVAA BSC Section D Charging Data

Interface ID:

ECVAA-I023

User:

BSCCo Ltd

Title:

ECVAA BSC Section D Charging Data

BSC Reference:

CR 65, CN160

Mechanism:

Electronic data file transfer

Frequency:

Monthly

Volumes:

Interface Requirement:

The system shall, on the 21^st calendar day of each month, collect information required for charging BSC parties under Section D of the Code and send this to BSCCo Ltd.

The information included shall be:

Month

Participant Id

Participant Name

Gross Contract Volume

where Gross Contract Volume is

Each month the information will be produced for both the previous calendar month and the month before that. Data used shall be the latest available data from Interim Run and Initial Run only.

Physical Interface Details:

6.38 ECVAA-I026: (output) Minimum Eligible Amount Request

Interface ID:

ECVAA-I026

User:

BSCCo Ltd

Title:

Minimum Eligible Amount Request

BSC Reference:

CP519, CP1313

Mechanism:

Manual

Frequency:

Ad hoc, as a result of receipt of Credit Cover Minimum Eligible Amount Requests

Volumes:

Low

Interface Requirement:

The ECVAA shall issue Minimum Eligible Amount Requests to BSCCo Ltd as a result of the receipt of Credit Cover Minimum Eligible Amount Requests from a BSC Party which is in Section H Default.

The Minimum Eligible Amount Request data shall comprise:

BSC Party ID

Minimum Eligible Amount Request Date

Note: the Minimum Eligible Amount Request Date is the date of receipt of the Credit Cover Minimum Eligible Amount Request by the ECVAA.

6.39 ECVAA-I027: (input) Notification of BSC Parties in Section H Default

Interface ID:

ECVAA-I027

Source:

BSCCo Ltd

Title:

Notification of BSC Parties in Section H Default

BSC Reference:

CP1313

Mechanism:

Manual

Frequency:

Ad hoc, in response to a change in the list

Volumes:

Low

Interface Requirement:

The ECVAA shall receive from BSCCo Ltd a list of all BSC Party Ids that are currently in Section H Default.

6.40 ECVAA-I032: (input) Credit Assessment Price

Interface ID:

ECVAA-I032

Source:

BSCCo Ltd

Title:

Credit Assessment Price

BSC Reference:

Mechanism:

Manual

Frequency:

As required

Volumes:

Low

Interface Requirement:

The ECVAA Service shall receive the Credit Assessment Price from BSCCo from time to time.

The Credit Assessment Price shall comprise:

Credit Assessment Price:

Credit Assessment Price (£/MWh)

Effective from date

Notes:

The effective from date shall be the settlement date upon which the price is to take effect, and shall be no earlier than the day after the price is received by ECVAA.

The Credit Assessment Price shall be in the range 0.00 to 999.99, and shall be held to two decimal places.

Physical Interface Details:

6.41 ECVAA-I040: (output) Issue Notification System Status Report

Interface ID:

ECVAA-I040

Source:

BSCCo Ltd

Title:

Issue Notification System Status Report

BSC Reference:

CP739

Mechanism:

Manual, by email, fax or telephone call.

Frequency:

As required

Volumes:

Low

Interface Requirement:

The ECVAA Service shall issue a status report to BSCCo Ltd. as soon as possible after:

The start of an ECVAA System Failure or ECVAA System Withdrawal;
A change in the Notification Agents affected by an existing ECVAA System Failure or ECVAA System Withdrawal; or
The end of an ECVAA System Failure or ECVAA System Withdrawal.

The notification shall contain

Incident Type (ECVAA System Failure or ECVAA System Withdrawal).

Incident Status (Start, End or Change)

Date and Time (GMT) of Incident Status

Affected Agents (list of affected Notification Agents or ALL).

Physical Interface Details:

6.42 ECVAA-I041: Receive Party Credit Default Authorisation Details

Interface ID:

ECVAA-I041

Source:

BSCCo Ltd

Title:

Receive Party Credit Default Authorisation Details

BSC Reference:

CP975

Mechanism:

Manual, by email, letter or fax

Frequency:

As necessary

Volumes:

approximately 10 times per year

The ECVAA shall receive, from time to time the BSC Party Credit Default Authorisation Flag from the BSCCo Ltd. The information shall contain:

Authentication Details

Name

Password

BSC Party Credit Default Authorisation Details

BSC Party Id

Credit Default Authorisation Flag

Effective From Date

Physical Interface Details:

6.43 SAA-I010: (input) BSCCo Ltd Cost Data (Redundant)

Interface ID:

SAA-I010

Source:

BSCCo Ltd

Title:

BSCCo Ltd Cost Data

BSC Reference:

SAA SD: 2.6

SAA BPM: 3.16, 4.12, CP527, CP1223

Mechanism:

Electronic data file transfer

Frequency:

Monthly/ Annual

Volumes:

Interface Requirement:

The SAA Service shall receive forecast BSCCo Ltd Costs monthly and actual BSCCo Ltd Costs annually from BSCCo Ltd.

The BSCCo Ltd Cost data shall include:

Forecast Costs:

Settlement Date

BSCCo Ltd Forecast Cost (£)

Total Actual Costs:

Year

BSCCo Ltd Actual Cost (£)

This interface is not in use.

6.44 SAA-I012: (input, part 1) Dispute Notification

This interface is defined in Part 1 of the Interface Definition and Design.

6.45 SAA-I014 (output) Settlement Reports

There are three variants of the Settlement Report. The first variant is sent to BSC Parties and is defined in Part 1 of the IDD. The second variant is sent to the NETSO and the BMRA and is defined in section 5 of this document. The third variant is sent to BSCCo Ltd and is defined here:

Interface ID:

SAA-I014

User:

BSCCo Ltd

Title:

Settlement Report

BSC Reference:

CR_991027_06a, CP527, P8, P18A, CP597, CP610, P71, P78, P194, P217, P305

Mechanism:

Electronic data file transfer

Frequency:

Daily per settlement run

Volumes:

The following information is provided:

Settlement Day Information

Settlement Date

Settlement Run Type

SAA Run Number

SAA CDCA Settlement Run Number

SVAA CDCA Settlement Date

SVAA CDCA Settlement Run Number

SVAA SSR Run Number

BSC Party Id

For each BSC Party:

BSC Party Information

BSC Party Id

Aggregate Party Day Charges (defined in IDD Part 1 section 8.4.1)

For each Settlement Period:

Settlement Period Information

Settlement Period (1-50) (j)

Total Demand (sum of all negative QM_ij)

Notional Reserve Limit (MW) (only for Settlement Dates prior to the P78 effective date)

Arbitrage Flag

CADL_d Continuous Acceptance Duration Limit

DMAT_d De Minimis Acceptance Threshold

System Period Data (defined in IDD Part 1 section 8.4.3)

Trading Unit Period Information:

Trading Unit Name

Total Trading Unit Metered Volume (MWh)

BM Unit Period Information:

BM Unit ID (i)

Trading Unit Name

Period FPN (FPN_ij) (MWh)

BM Unit Metered Volume (QM_ij) (MWh)

Transmission Loss Multiplier (TLM_ij)

BM Unit Applicable Balancing Services Volume (QAS_i) (MWh)

BM Unit Period Bid-Offer Information:

Bid-Offer Pair Number (n)

Bid Price (PBⁿ_ij) (£)

Offer Price (POⁿ_ij) (£)

BM Unit Period Bid-Offer Spot Points (^fQBOⁿ_ij):

Time from

Bid-Offer Value from

Time to

Bid-Offer Value to

Maximum Export Limit Information:

Time From

Level From (MW)

Time to

Level To (MW)

Maximum Import Limit Information:

Time From

Level From (MW)

Time to

Level To (MW)

Physical Interface Details:

This is sub-flow 3 of the Settlement Report, file id S0143.

For the Interim Initial Settlement Run, the full set of data is included in the file.

For subsequent Settlement Runs, certain information is only included if it has been changed: this applies to the Maximum Export Limit Information, (MEL), Minimum Export Limit Information (MIL), and BM Unit Period Bid-Offer Spot Points (BO2). BM Unit Period Bid-Offer Information (BBO) is only included where there are changes (to prices or to underlying BM Unit Period Bid-Offer Spot Points (BO2)).

For BO2 it is possible that the change being reported is that the record has been deleted; this is indicated by reporting nulls, e.g.

where there had been a record

BO2|10|123456.789|20|123456.789|

deletion of this record would be shown by

BO2|10||20||

Note:

SAA CDCA Settlement Run Number

Identifies the CDCA run which generated volumes used directly by SAA in the settlement calculations

For all settlement runs, other than Interim Initial for Settlement Dates prior to the P253 effective date:

SVAA CDCA Settlement Date

SVAA CDCA Settlement Run Number

Identify the CDCA run for Settlement Date which generated the GSP Group Take volumes which were allocated by the SVAA

SVAA SSR Run Number

Identifies the SVAA Run for Settlement Date which generated the SVA BM Unit volumes

For Interim Initial Settlement Runs for Settlement Dates prior to the P253 effective date:

SVAA CDCA Settlement Date

SVAA SSR Run Number

Identify the Settlement Date and Initial Settlement (SF) SVAA Run from which SVA volumes are derived

SVAA CDCA Run Number

Will be zero

6.46 SAA-I016: (output, part 1) Settlement Calendar

This interface is defined in Part 1 of the Interface Definition and Design.

6.47 SAA-I018: (output, part 1) Dispute Report

This interface is defined in Part 1 of the Interface Definition and Design.

6.48 SAA-I019: (output) BSC Party Performance Reports (Redundant)

Interface ID:

SAA-I019

User:

BSCCo Ltd

Title:

BSC Party Performance Reports

BSC Reference:

SAA IRR: SAA6, CP1222

Mechanism:

Electronic data file transfer

Frequency:

Monthly

Volumes:

Interface Requirement:

The SAA Service shall issue BSC Party Performance Reports once a month to BSCCo Ltd.

The BSC Party Performance Reports shall include:

BSC Party rankings by number/volume of trades

BSC Party rankings by imbalance volumes

Ranking will be as follows:

Ranking by Number of Trades, then by Volume (i.e. if two parties have the same number of trades, then their relative ranking will be established using volume of trades).

Ranking by Energy Imbalance, then by Information Imbalance (i.e. if two parties have the same energy imbalance, then their relative ranking will be established using information imbalance). Note that the Imbalance Volumes flow for this report contains only a single value for imbalance volume.

This interface is not in use.

6.49 SAA-I020: (output) SAA Performance Reports

Interface ID:

SAA-I020

User:

BSCCo Ltd

Title:

SAA Performance Reports

BSC Reference:

SAA SD: B, CP527, P78

Mechanism:

Manual, probably in whole or in part produced using a report-formatting tool.

Frequency:

Monthly

Volumes:

Interface Requirement:

The SAA Service shall issue SAA Performance Reports once a month to BSCCo Ltd.

The SAA Performance Reports shall include:

Settlement Run Reporting:

Month Ending Date

Settlement Date

Report Run Type

Report Recipient

Expected Settlement Report Date

Settlement Run Date/Time

Actual Settlement Report Date/Time

Settlement Calendar Publishing:

Settlement Calendar Year

Expected Publish Date

Actual Publish Date

BM Unit Credit Assessment Import Capability Reporting:

Month Ending Date

Reason (Month End/CALF Change)

Report Recipient

Expected Report Date

Actual Report Date

Help Desk Reporting:

Call Severity Level

Response Time

Market Index Data Provider Performance:

Month Ending Date

Market Index Data Provider Identifier

Number of Settlement Days for which Market Index Data was not provided in time for the Initial Interim Settlement Run

Number of Settlement Periods where individual Liquidity Threshold required default by SAA

Number of Settlement Periods where zeroes were used in the Initial Interim Settlement Calculation

6.50 SAA-I023: (input) System Parameters

Interface ID:

SAA-I023

Status:

Mandatory

Title:

System Parameters

BSC Reference:

CR 003, P10, P18A, CP632, P194, P217, P305

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

Low – typically one or two per month

Interface Requirement:

The SAA Service shall receive the following system parameters from the BSCCo Ltd via a manual interface, expected to be either a fax or telephone call:

Effective from Settlement Date

Effective from Settlement Period (1-50)

Effective to Settlement Date

Effective to Settlement Period (1-50)

Information Imbalance Price 1

Information Imbalance Price 2

Arbitrage Flag

NRL_j (Notional Reserve Limit) (MW)

DMAT_d (De Minimis Acceptance Threshold) (MWh)

CADL_d (Continuous Acceptance Duration Limit (minutes)

PAR_d (Price Average Reference Volume) (MWh) (0-9,999,999,999)

RPAR_d (Replacement Price Average Reference Volume) (MWh)

VoLL (Value of Lost Load)

Physical Interface Details:

The BSCCo Ltd system parameter values shall continue to apply to all settlement periods, until a change to a parameter is made.

Issues:

6.51 SAA-I025: (output) SAA BSC Section D Charging Data

Interface ID:

SAA-I025

User:

BSCCo Ltd

Title:

SAA BSC Section D Charging Data

BSC Reference:

CR 65, CN160

Mechanism:

Electronic data file transfer

Frequency:

Monthly

Volumes:

Interface Requirement:

The system shall, on the 15^th working day of each month, collect information required for charging BSC parties under Section D of the Code and send this to BSCCo Ltd.

The information included shall be:

Month

Participant Id

Participant Name

Production/Consumption Flag

Volume

where Volume is the aggregated Credited Energy Volume of all BM Units that are not Interconnector BM Units for the Production/Consumption Energy Account belonging to the BSC Party.

Each month the information will be produced for both the previous calendar month and the month before that. Data used shall be the latest available data from Interim Run and Initial Run only.

Physical Interface Details:

6.52 SAA-I027: (output) Report pre-settlement run validation failure

Interface ID:

SAA-I027

Source:

SAA

Title:

Report pre-settlement run validation failure

BSC Reference:

CP639, CP1222

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

As required.

Interface Requirement:

The SAA shall send to BSCCo details of pre-settlement run validation failures. The content of the report shall include

Settlement Date

Settlement Run Type

Failure Reasons

Physical Interface Details:

This interface is likely to take the form of a fax or an e-mail or a telephone call. Failure Reasons will be various.

Issues:

6.53 SAA-I028: (input) Receive settlement run decision

Interface ID:

SAA-I028

Source:

BSCCo

Title:

Receive settlement run decision

BSC Reference:

CP639

Mechanism:

Manual

Frequency:

In response to SAA-I027

Volumes:

Low – typically one or two per month

Interface Requirement:

BSCCo shall send to the SAA a decision on whether a settlement run should continue if the SAA has reported pre-settlement run validation run failures (SAA-I027) for this run.

Settlement Date

Settlement Run Type

Decision

Physical Interface Details:

This interface is likely to take the form of a fax or an e-mail or a telephone call. Failure Reasons will be various.

Issues:

6.54 SAA-I029: (input) Receive settlement run instructions

Interface ID:

SAA-I029

Source:

BSCCo

Title:

Receive settlement run instructions

BSC Reference:

CP639

Mechanism:

Manual

Frequency:

In response to SAA-I027

Volumes:

Low – typically one or two per month

Interface Requirement:

BSCCo shall send to the SAA instructions on how to progress a settlement run that the SAA has reported pre-settlement run validation run failures (SAA-I027) for.

Settlement Date

Settlement Run Type

Instructions

Physical Interface Details:

This interface is likely to take the form of a fax or an e-mail or a telephone call. Failure Reasons will be various.

Issues:

6.55 SAA-I031: (input) Receive Market Index Data Provider Thresholds

Interface ID:

SAA-I031

Source:

BSCCo

Title:

Receive Market Index Data Provider Thresholds

BSC Reference:

P78

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

This manual flow is expected to handle a maximum of 6 date ranges to be defined, for each DP, for each year. Each date range to have a maximum of 4 different Liquidity Thresholds.

Interface Requirement:

The SAA shall receive Market Index Data Provider Liquidity Threshold data from BSCCo. The processing rules for this flow are described in SAA-F023.

The flow shall include:

Market Index Data Provider Identifier

MIDP Date Range

Action Type

Effective From Settlement Date

Effective To Settlement Date

MIDP Period Data

Effective From Settlement Period (1-50)

Effective To Settlement Period (1-50)

Liquidity Threshold

Action Type describes the type of operation to be performed in relation to the data supplied in the other fields. It can be one of:

Insert;
Update;
Delete.

Physical Interface Details:

Issues:

6.56 SAA-I032: (output) Report Market Index Data Provider Thresholds

Interface ID:

SAA-I032

User:

BSCCo

Title:

Report Market Index Data Provider Thresholds

BSC Reference:

P78

Mechanism:

Manual

Frequency:

In response to SAA-I031, as described in SAA-F023

Volumes:

This manual flow is expected to handle a maximum of 6 date ranges to be defined, for each DP, for each year. Each date range to have a maximum of 4 different Liquidity Thresholds.

Interface Requirement:

The SAA shall report Market Index Data Provider Liquidity Threshold to BSCCo.

The flow shall include:

Market Index Data Provider Identifier

MIDP Date Range

Effective From Settlement Date

Effective To Settlement Date

MIDP Period Data

Effective From Settlement Period (1-50)

Effective To Settlement Period (1-50)

Liquidity Threshold

Physical Interface Details:

Issues:

6.57 SAA-I034: (output) Report Recommended Data Change

Interface ID:

SAA-I034

User:

BSCCo

Title:

Report Recommended Data Change

BSC Reference:

CP995, CP1283

Mechanism:

Manual

Frequency:

In response to SAA-I033 for an Emergency Instruction

Volumes:

Low

Interface Requirement:

The SAA will report to the BSCCo and recommend a course of action with regards to a request for data change received from the NETSO (via SAA-I033) where the request is marked as an Emergency Instruction.

Non Functional Requirement:

Issues:

6.58 SAA-I035: (input) Receive Instruction for Data Change

Interface ID:

SAA-I035

Source:

BSCCo

Title:

Receive Instruction for Data Change

BSC Reference:

CP995, CP1283

Mechanism:

Manual

Frequency:

In response to SAA-I034

Volumes:

Low

Interface Requirement:

In response to SAA-I034 for an Emergency Instruction, BSCCo shall send to the SAA instructions for a data change.

Non Functional Requirement:

Issues:

6.59 SAA-I036: (output) Report Confirmation of Data Change

Interface ID:

SAA-I036

User:

BSCCo, the NETSO

Title:

Report Confirmation of Data Change

BSC Reference:

CP995, CP1283

Mechanism:

Manual

Frequency:

In response to SAA-I035 for an Emergency Instruction

In response to SAA-I033 for a non-Emergency Instruction

Volumes:

Low

Interface Requirement:

The SAA shall report to BSCCo and the NETSO confirmation of the completion of an instructed data change (received via SAA-I035) for an Emergency Instruction or via SAA-I033 for a non-Emergency Instruction).

Non Functional Requirement:

Issues:

6.60 SAA- I038: (input) Receive Excluded Emergency Acceptance Pricing Information

Interface ID:

SAA-I038

Source:

BSCCo

Title:

Receive Excluded Emergency Acceptance Pricing Information

BSC Reference:

P172

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

Low

Interface Requirement:

The BSCCo shall send to the SAA recalculated Energy Imbalance Prices resulting from Excluded Emergency Acceptances prior to each subsequent Settlement Run.

The following data items will be included in the communication:

Settlement Day

Settlement Period

Buy Price

Sell Price

Settlement Run Type that was used to calculate the new Energy Imbalance Prices.

Non Functional Requirement:

Issues:

6.61 SAA-I039: (output) Send Excluded Emergency Acceptance Dry Run Results

Interface ID:

SAA-I039

User:

SAA

Title:

Send Excluded Emergency Acceptance Dry Run Results

BSC Reference:

P172

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

Low

Interface Requirement:

The SAA shall, as a result of any additional 'dry run' carried out in response to Excluded Emergency Acceptances received, send to the BSCCo confirmation of whether SAA has matched the prices within the defined threshold. The confirmation will be in the form of a Y/N flag.

Non Functional Requirement:

Issues:

6.62 SAA- I040: (input) Receive Authorisation To Proceed With Full Settlement Run

Interface ID:

SAA-I040

Source:

BSCCo

Title:

Receive Authorisation To Proceed With Full Settlement Run

BSC Reference:

P172

Mechanism:

Manual

Frequency:

Ad-hoc

Volumes:

Low

Interface Requirement:

The BSCCo shall send to the SAA authorisation to proceed with the full Settlement Run.

Non Functional Requirement:

Issues:

6.63 ECVAA-I049: (input) Request to remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default

Interface ID:

ECVAA-I049

Source:

BSCCo Ltd

Title:

Request to remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default

BSC Reference:

CP1140

CP1169

Mechanism:

Manual, by email.

Frequency:

As required

Volumes:

Low

Interface Requirement:

The ECVAA shall receive, from time to time request to remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default, which shall contain:

Party ID
Removal effective from Date
Removal effective from Period
Copy of the BSC Panel resolution
Any notes pertinent to this removal

Physical Interface Details:

6.64 ECVAA-I050: (output) Remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default Feedback.

Interface ID:

ECVAA-I050

User:

BSCCo Ltd

Title:

Remove all ECVNs and MVRNs from ECVAA for a Party in Section H Default feedback

BSC Reference:

CP1140

CP1169

Mechanism:

Manual, by email.

Frequency:

As required

Volumes:

Low

Interface Requirement:

The ECVAA shall issue feedback to BSCCo Ltd following the receipt of a request to remove all ECVNs and MVRNs for a Party in Section H default, which shall contain:

Party ID
Removal effective from Date
Removal effective from Period
Any notes pertinent to this removal

Physical Interface Details:

The ECVAA-I050 shall be used on the following occasions:

Where the dis-application is to commence from Period 1:

To confirm receipt of the ECVAA-I049.
To confirm that all Notifications have been removed and all Authorisations terminated for the defaulting Party,
To confirm that the Credit Check has been restarted.
To confirm that the final check has been completed.

Where the dis-application is to commence from any period other than Period 1:

To confirm receipt of the ECVAA-I049.
To confirm that all Notifications have been removed from the next settlement day and all Authorisations terminated for the defaulting Party,
To confirm that the Credit Check has been restarted.
To confirm that the Volume Nullification process is completed. An update on the progress of each Volume Notification Nullification will be sent every working day if this process takes more than one working day.
To confirm that the final check has been completed.

Note: additional informal communications may occur between the ECVAA and BSCCo by email and/or telephone as individual circumstances dictate.

6.65 ECVAA-I053: Daily Wholesale Market Activity Report

Interface ID:

ECVAA-I053

Source:

SVAA

Title:

Daily Wholesale Market Activity Report

BSC Reference:

P415

Mechanism:

API

Frequency:

Daily

Volumes:

Low

The ECVAA shall for each Settlement Date send details of all Secondary BM Units and Settlement Periods for which it has received Wholesale Market Activity Notifications.

Settlement Date

BM Unit

Settlement Period

Wholesale Market Activity Indicator

Physical Interface Details:

Also refered to as the P0339

6.66 BMRA-I033: (Input) STOR Availability Window

Interface ID:

BMRA-I033

Source:

BSCCo Ltd

Title:

STOR Availability Window

BSC Reference:

P305

Mechanism:

Manual, by email.

Frequency:

As required

Volumes:

Low

Interface Requirement:

The BSCCo will provide the BMRA and SAA with details of STOR Availability Windows.

The following details will be provided:

Document ID

Season Year

Season Number

STOR Availability Dates

Weekday Start Time

Weekday End Time

Non-weekday Start Time

Non-weekday End Time

Physical Interface Details:

BSCCo will send details in CSV format.

6.67 SAA-I046: (Input) STOR Availability Window

SAA receives input file from BSCCo using same format as BMRA-I033.

7 Interfaces From and To Stage 2

The physical formats of these files are defined in the SVA Data Catalogue and in the spreadsheet attached to this document. The definition in the SVA Data Catalogue is the master.

7.1 CDCA-I043: (output) GSP Group Take to SVAA

Interface ID: CDCA-I043	User: SVAA	Title: GSP Group Take to SVAA		BSC Reference: CDCA SD 22, 23.1, A, B CDCA BPM 4.13, CP593
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: Daily, for those Settlement Dates for which a CDCA run (excluding any Interim Initial runs for Settlement Dates prior to the P253 effective date) has taken place that day.	Volumes:
Interface Requirement:
CDCA provides aggregated meter flow volumes for the GSP Groups to SVAA. The physical form of this interface is the existing GSP Group Take file sent from the SSA system to ISRA. One file per GSP Group, containing GSP Group Take Volumes produced by a CDCA Run (excluding any Interim Initial runs for Settlement Dates prior to the P253 effective date) for each Settlement Period of a Settlement Date. There are fields in the existing flow which are meaningless under the BSC, for which dummy or null values are provided. These fields are called Fillers in the physical flow.
Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0012001'
From Stage2 Role Code			=’S’
From Stage2 Participant Id			= Id allocated to CDCA by Stage 2
To Stage2 Role Code			='G'
To Stage2 Participant Id			='CAPG''
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.2 CRA-I004: Agent Details

This interface is defined in Section 4. (SVAA registers itself with CRA.)

7.3 SAA-I007: (input) BM Unit Allocated Demand Volume

Interface ID: SAA-I007	Source: SVAA	Title: Allocated Supplier Volumes		BSC Reference: RETA SCH: 4, B, 2.4.1 SAA SD: 2.5, A1 SAA BPM: 3.4, 4.42, CP632
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: Daily, for each run the SVAA has done that day.	Volumes:
Interface Requirement: The SAA Service shall receive BM Unit Allocated Demand Volume once a day from the SVAA.
The BM Unit Allocated Demand Volume data shall include:
Supplier ID GSP Group ID BM Unit ID CDCA Settlement Date CDCA Run Number SVAA SSR Settlement Date SVAA SSR Run Number Settlement Period (1-50) Energy Volume Reading (MWh) (signed, consumption positive))


Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0182001'
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to CDCA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.4 SAA-I016: (output, part 1) Settlement Calendar

This interface is defined in Part 1 of the Interface Definition and Design.

7.5 SAA-I017: (output, common) SAA Data Exception Report

This interface is defined in Part 1 of the Interface Definition and Design.

7.6 CRA-I015: (output) BM Unit Registration Data

This interface is defined in Section 4 (sub-flow 2 in the physical flow definition is specifically for the Stage 2 MDDA).

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier	same as unique Id part of file name
File Type	='P0181001'
From Stage2 Role Code	=’Z’
From Stage2 Participant Id	= Id allocated to CDCA by Stage 2
To Stage2 Role Code	='U'
To Stage2 Participant Id	='CAPG''
Creation Time
Sending Application Id	=NULL
Receiving Application Id	=NULL
Broadcast	=NULL
Test Data Flag	indicates whether this is live data or test data

7.7 BMRA-I032: (output) Demand Control Instructions to SVAA

Interface ID:

BMRA-I032

User:

SVAA

Title:

Demand Control Instructions to SVAA

BSC Reference:

P305

Mechanism:

Electronic data file transfer, Pool Transfer File Format

Frequency:

As made available by the NETSO

Volumes:

Low

Interface Requirement:

The BMRA provides details of Demand Control Instructions to the SVAA as and when they are made available by the NETSO via BMRA-I002

The Demand Control Instruction data shall include:

Demand Control Event ID

Instruction Sequence Number

Demand Control Event flag

Start Date and Time

End Date and Time

Volume

SO Flag

Amendment Flag

Physical Interface Details:

See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet.

7.8 SAA-I045: (input) BM Unit Allocated Demand Disconnection Volume

Interface ID: SAA-I045	Source: SVAA	Title: Allocated Supplier Volumes		BSC Reference: P305
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For SF run and all subsequent runs the SVAA has done that day where Demand Control was required	Volumes: Low
Interface Requirement: The SAA Service shall receive from the SVAA, BM Unit Allocated Demand Disconnection Volume for each Settlement Day affected by a Demand Control event.
The BM Unit Allocated Demand Disconnection Volume data shall include:
Supplier ID GSP Group ID BM Unit ID CDCA Settlement Date CDCA Run Number SVAA SSR Settlement Date SVAA SSR Run Number Settlement Period (1-50) Disconnected Energy Volume Reading (MWh) (+ve = consumption)


Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0237'
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to CDCA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.9 SAA-I050: (input) Secondary BM Unit Demand Volumes

Interface ID: SAA-I050	User: SAA	Title: Secondary BM Unit Demand Volumes		BSC Reference: P344
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For SF run and all subsequent runs	Volumes: High
Interface Requirement: The SAA Service shall receive from the SVAA, Secondary BM Unit Demand Volumes relating to Replacement Reserve.
The data shall include:
Settlement Date SSR Run Type Id Secondary BM Unit Id Settlement Period Secondary BM Unit Demand Volume

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0289’
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to SAA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.10 SAA-I051: (input) Secondary BM Unit Supplier Delivered Volumes

Interface ID: SAA-I051	User: SAA	Title: Secondary BM Unit Supplier Delivered Volumes		BSC Reference: P344
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For SF run and all subsequent runs	Volumes: High
Interface Requirement: The SAA Service shall receive from the SVAA, Secondary BM Unit Supplier Delivered Volumes relating to Replacement Reserve.
The data shall include:
Settlement Date SSR Run Type Id BM Unit Id Secondary BM Unit Id Settlement Period Secondary BM Unit Supplier Delivered Volume

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0290’
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to SAA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.11 SAA-I052: (output) Daily Activations Report

Interface ID: SAA-I052	User: SVAA	Title: Daily Activations Report		BSC Reference: P344
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For each Settlement Day	Volumes: Medium
Interface Requirement: The SAA Service shall send to the SVAA, a Daily Activations Report identifying those activations made in regard to Replacement Reserve.
The data shall include:
Settlement Date BM Unit Id Settlement Period Secondary BM Unit Id Settlement Period RR Activation data

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0291’
From Stage2 Role Code			=’F’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='G'
To Stage2 Participant Id			= CAPG
Creation Time			= Id allocated to SAA by Stage 2
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.12 SAA-I054: (input) Supplier BM Unit Non BM ABSVD

Interface ID: SAA-I054	User: SAA	Title: Daily Activations Report		BSC Reference: P354
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For each Settlement Day	Volumes: Medium
Interface Requirement: The SAA shall receive Supplier BM Unit Non BM ABSVD from the SVAA Service.
The data shall include:
Settlement Date SSR Run Type BM Unit Id Settlement Period Id Supplier BM Unit Non BM ABSVD Volume

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0296’
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to SAA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.13 SAA-I055: BM Unit Settlement Expected Volumes

Interface ID:

SAA-I055

User:

SAA

Title:

Baselining Expected Volume Report

BSC Reference:

P376

Mechanism:

Electronic data file transfer, Pool Transfer File Format

Frequency:

For each Settlement Day

Volumes:

Medium

Interface Requirement:

The SAA shall receive BM Unit Settlement Expected Volumes from the SVAA Service.

The data shall include:

Settlement Date

SSR Run Type Id

BM Unit Id

Settlement Period

BM Unit Settlement Expected Volume

Physical Interface Details:

See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet.

ZHD Header information:

File Identifier

same as unique Id part of file name

File Type

='P0332’

From Stage2 Role Code

=’G’

From Stage2 Participant Id

='CAPG''

To Stage2 Role Code

='F'

To Stage2 Participant Id

= Id allocated to SAA by Stage 2

Creation Time

Sending Application Id

=NULL

Receiving Application Id

=NULL

Broadcast

=NULL

Test Data Flag

indicates whether this is live data or test data

7.14 SAA-I057: Supplier BM Unit Period Non-Chargeable Demand

Interface ID: SAA-I057	User: SAA	Title: Supplier BM Unit Period Non-chargeable Demand		BSC Reference: P395
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For each Settlement Day	Volumes: Medium
Interface Requirement: The SAA shall receive Supplier BM Unit Period Non-Chargeable Demand from the SVAA Service.
The data shall include:
SSR Run Type Id Settlement Date BM Unit Id Settlement Period Period BM Unit Non-chargeable Demand

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0338’
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to SAA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.15 SAA-I059: Supplier BM Unit Period Total Gross Non-Final Demand

Interface ID: SAA-I059	User: SAA	Title: Supplier BM Unit Period Total Gross Non-Final		BSC Reference: P415
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For each Settlement Day	Volumes: Medium
Interface Requirement: The SAA shall receive Supplier BM Unit Period Total Gross Non-Final Demand from the SVAA Service.
The data shall include:
SSR Run Type Id Settlement Date BM Unit ID Settlement Period BM Unit Period Total Gross Non-Final Demand

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0340’
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to SAA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

7.16 SAA-I060: BM Unit Period Deviation Volume

Interface ID: SAA-I060	User: SAA	Title: BM Unit Period Deviation Volume		BSC Reference: P415
Mechanism: Electronic data file transfer, Pool Transfer File Format	Frequency: For each Settlement Day	Volumes: Medium
Interface Requirement: The SAA shall receive BM Unit Period Deviation Volume from the SVAA Service.
The data shall include:
SSR Run Type Id Settlement Date BM Unit ID Settlement Period BM Unit Deviation Volume

Physical Interface Details: See the physical flow for details, in the Stage 2 tab of the IDD Part 2 spreadsheet. ZHD Header information:
File Identifier			same as unique Id part of file name
File Type			='P0341’
From Stage2 Role Code			=’G’
From Stage2 Participant Id			='CAPG''
To Stage2 Role Code			='F'
To Stage2 Participant Id			= Id allocated to SAA by Stage 2
Creation Time
Sending Application Id			=NULL
Receiving Application Id			=NULL
Broadcast			=NULL
Test Data Flag			indicates whether this is live data or test data

8 Interfaces Within BSC Central Systems

8.1 BMRA-I001 (input): Registration Data

See CRA-I013 and CRA-I015 in section 4.

8.2 BMRA-I007 (output) SAA/ECVAA Balancing Mechanism Data

Interface IDs:

From: BMRA-I007

To: SAA-I003

To: ECVAA-I048

User:

SAA, ECVAA

SAA/ECVAA Balancing Mechanism Data

BSC Reference:

RETA SCH: 4, B, 2.4.1

SAA SD: 2.1, A1,

ITT Query Response Ref R-031

SAA BPM: 3.3, 4.3, 4.4, 4.17, 4.18, P71, P140, P217, P305

Mechanism:

BMRA stores the files it receives from the NETSO in a directory readable by SAA and ECVAA.

Frequency:

As required for SAA and ECVAA.

Volumes:

Between 1000 - 5000 BM units*. In each settlement period, at least 1 FPN data and 1 Bid-Offer Acceptance per BM unit. At most 10 Bid-Offer Pairs per BM unit (estimated 1000) that receives bids and offers.

Interface Requirement:

The BMRA Service shall copy all Balancing Mechanism data that was received from the NETSO on settlement day N to a directory that is readable by SAA. The SAA shall load the data in time for the first (Interim) settlement run for settlement day N. Physical Notification data shall additionally be copied to a directory readable by the ECVAA.

* N.B. Only Physical Notification data will be read by ECVAA.

Balancing mechanism data shall include all data listed in BMRA-I002 that was received from the NETSO, i.e.:

Physical Notification (PN)

Quiescent PN (QPN)

Bid-Offer Data (BOD)

Applicable Balancing Services Volume (QAS)

Maximum Export Limit (MEL)

Maximum Import Limit (MIL)

Run Up Rates Export (RURE)

Run Up Rates Import (RURI)

Run Down Rates Export (RDRE)

Run Down Rates Import (RDRI)

Notice to Deviate from Zero (NDZ)

Notice to Deliver Offers (NTO)

Notice to Deliver Bids (NTB)

Minimum Zero Time (MZT)

Minimum Non-Zero Time (MNZT)

Stable Export Limit (SEL)

Stable Import Limit (SIL)

Maximum Delivery Volume (MDV)

Maximum Delivery Period (MDP)

For Settlement Dates prior to the P217 effective date this flow shall also include:

Bid-Offer Acceptance Level (BOAL)

For Settlement Dates after and including the P217 effective date this flow shall also include:

Bid-Offer Acceptance Level Flagged (BOALF)

For Settlement Dates after and including the P305 effective date this flow shall also include:

Demand Control Instructions

Loss of Load Probability and De-rated Margin Data

STOR Availability Window

Physical Interface Details:

8.3 BMRA-I010: (output, common) Data Exception Reports

This interface is defined in Part 1 of the Interface Definition and Design.

8.4 BMRA-I018: (input) Publish Credit Default Report

See ECVAA-I036 in this section.

8.5 CDCA-I002: (input) Registration Data

See CRA-I019 in this section.

8.6 CDCA-I016: (input) Information from TAA

Interface ID:

CDCA-I016

Source:

TAA

Title:

Request for Metering System details

BSC Reference:

TAA SD 3.2.3

Mechanism:

Manual

Frequency:

Quarterly

Volumes:

Interface Requirement:

The TAA shall request from the CDCA the following details for each Metering Systems identified by the BSCCo Ltd as being in the Sampled category: This information shall be used by the TAA to ensure that a fair sample is selected, and to ensure that any selection guidance given by the BSCCo Ltd can be followed.

Relevant BSC Party
Meter Operator Agent
Metering Equipment technical details
Applicable Code of Practice
GSP and/or GSP Group

8.7 CDCA-I020: (input) Site Visit Inspection Report

Interface ID:

CDCA-I020

Source:

CDCA Site Visit Agent

Title:

Site Visit Inspection Report

BSC Reference:

CDCA SD 13.1- 13.7, CP753, CP756, P190

Mechanism:

Manual, by email, letter or fax

Frequency:

Ad hoc

Volumes:

50 per month

Interface Requirement:

On completion of the site inspection, the Site Visit Agent will provide a written report to CDCA detailing the outcome of the site inspection including, but not limited to meter readings.

Physical Interface Details:

8.8 CDCA-I027: (output) Aggregated Interconnector Meter Flow Volumes

Interface ID:

From: CDCA-I027

To: SAA-I004

User:

SAA

Title:

Aggregated Interconnector Meter Flow Volumes

BSC Reference:

CDCA SD 22, 23.1, A, B

CDCA BPM 4.15, CP527

Mechanism:

via Electronic data file transfer

Frequency:

Daily

Volumes:

Initially 96 (2 interconnectors * 48 readings). The number of interconnectors is expected to increase to 5 or 6.

Interface Requirement:

Aggregated meter flow volumes for the Interconnectors are sent to SAA, as follows for each Interconnector:

Interconnector Identifier

Settlement Date

Settlement Period

Estimate Indicator

Date of aggregation

Meter Volume

CDCA Run Number

Import/Export indicator (I/E)

The Import/Export indicator indicates the direction of the energy flow: the Meter Volume is therefore unsigned.

Physical Interface Details:

8.9 CDCA-I028: (output) Aggregated BM Unit Meter Flow Volumes

Interface ID:

From:CDCA-I028

To: SAA-I004

User:

SAA

Title:

Aggregated BM Unit Meter Flow Volumes

BSC Reference:

CDCA SD 22, 23.1, A, B

CDCA BPM 4.9, CP527

Mechanism:

Electronic data file transfer

Frequency:

Daily

Volumes:

Interface Requirement:

Aggregated meter flow volumes for the BM Units are sent to SAA, as follows for each BM Unit:

BM Unit Identifier

Settlement Date

Settlement Period

Estimate Indicator

Date of aggregation

Meter Volume

CDCA Run Number

Import/Export indicator (I/E)

The Import/Export indicator indicates the direction of the energy flow: the Meter Volume is therefore unsigned.

Physical Interface Details:

8.10 CDCA-I034: Settlement Calendar

This interface is defined in Part One as SAA-I016.

8.11 CDCA-I035: (input) Site Visit Report on Aggregation Rule Compliance

Interface ID:

CDCA-I035

User:

CDCA Site Visit Agent

Title:

Site Visit Report on Aggregation Rule Compliance

BSC Reference:

CDCA SD 22.4, CP756

Mechanism:

Manual, by email, letter or fax

Frequency:

Volumes:

Currently 12 GSP Groups in England & Wales

Interface Requirement:

A report from the site visit agent, after undertaking (where necessary) a site visit to verify the validity of the aggregation rules.

Physical Interface Details:

8.12 CDCA-I036: (output) GSP Group Take to SAA

Interface ID:

From: CDCA-I036

To: SAA-I004

User:

SAA

Title:

GSP Group Take to SAA

BSC Reference:

CDCA SD 22, 23.1, A, B

CDCA BPM 4.13, CP527

Mechanism:

Electronic data file transfer

Frequency:

Daily

Volumes:

Currently 12 GSP Groups in England & Wales

Interface Requirement:

CDCA provides aggregated meter flow volumes for the GSP Groups to SAA, as follows for each GSP Group:

GSP Group Id

Settlement Date

Settlement Period

Estimate Indicator

Date of aggregation

Meter Volume

CDCA Run Number

Import/Export indicator (I/E)

The Import/Export indicator indicates the direction of the energy flow: the Meter Volume is therefore unsigned.

Physical Interface Details:

8.13 CDCA-I039: (output) Information to TAA

Interface ID:

From: CDCA-I039

To: TAA

User:

TAA

Title:

Information to TAA.

BSC Reference:

CDCA SD 11.6

BPM

Mechanism:

Manual

Frequency:

As required

Volumes:

estimate 10 per day (0.2% of 5000)

Interface Requirement:

The CDCA carry out site inspections and liaise with the Technical Assurance Agent (TAA) as necessary.

The CDCA sends the TAA the following Metering System details for all Metering Systems in the Sampled category.

Relevant BSC Party
Meter Operator Agent
Metering Equipment technical details
Applicable Code of Practice
GSP and/or GSP Group

Physical Interface Details:

8.14 CDCA-I050: (input) Data Exception Reports

This interface is defined in Part One as SAA-I017.

8.15 CDCA-I066: (input) Demand Control Instructions to CDCA

See SAA-I043 in this section.

8.16 CDCA-I068: (output) Period BM Unit Demand Disconnection Volumes

Interface ID:

From:CDCA-I068

To: SAA-I044

User:

SAA

Title:

Aggregated BM Unit Meter Flow Volumes

BSC Reference:

CDCA SD 19, P305

Mechanism:

Electronic data file transfer

Frequency:

As required

Volumes:

Low

Interface Requirement:

Aggregated estimates of disconnected meter volumes for the BM Units are sent to SAA, as follows for each BM Unit:

BM Unit Identifier

Settlement Date

Settlement Period

Disconnection Meter Volume

Physical Interface Details:

8.17 CRA-I010

This interface is redundant.

8.18 CRA-I013: (output, common) Issue Authentication Report

This interface is defined in Section 4.

8.19 CRA-I015: (output, common) BM Unit and Energy Account Registration Data

This interface is defined in Section 4.

8.20 CRA-I017 (output): Credit Assessment Capability

Interface ID:

From: CRA-I017

To: ECVAA-I001

To: SAA-I002

User:

ECVAA, SAA

Title:

Credit Assessment Capability

BSC Reference:

SAA SD: 2.7, A1 SAA BPM: 3.1, CRA 7.2.2

Mechanism:

Via automated interface with SAA and electronic data file transfer to ECVAA

Frequency:

Monthly or Ad-hoc

Volumes:

Interface Requirement:

The CRA Service shall issue the Credit Assessment to the SAA and ECVAA Services from time to time. The report shall contain:

Credit Assessment Details

BM Unit ID

Working Day BM Unit Credit Assessment Export Capability (WDBMCAEC)

Non- Working Day BM Unit Credit Assessment Export Capability (NWDBMCAEC)

Working Day BM Unit Credit Assessment Import Capability (WDBMCAIC)

Non- Working Day BM Unit Credit Assessment Import Capability (NWDBMCAIC)

Effective From Date

Effective To Date

Physical Interface Details:

8.21 CRA-I019: (output) Registration Data

Interface ID:

From: CRA-I019

To: CDCA-I002

User:

CDCA

Title:

Registration Data

BSC Reference:

CDCA SD: 4.6-4.14, A

CDCA BPM 4.16, P100, P197, P215

Mechanism:

Via shared database

Frequency:

Daily

Volumes:

Low

Interface Requirement:

The CRA Service shall issue to the CDCA the registered meter data required by that system. This will contain:

Note: Certification /Accreditation refers to Qualification.

BSC Party Details

BSC Party Name

BSC Party ID

Party Role Details

BSC Party Type

Registration Effective From Date

Registration Effective To Date

Role Address Details

Address

Telephone No

Fax No

e-mail Address

Settlement Report Details

Report Type

Distribution Method

Authentication Details

Name

Password

Authorised Signatories

Name

Password

Contact Phone No

e-mail Address

Authorisation Levels

Activity

Effective From Date

Effective To Date

Interconnector Administrator Details

Interconnector Administrator Name

Interconnector Administrator ID

Interconnector ID

GSP Group ID (optional)

Registration Effective From Date

Registration Effective To Date

Contact Details

Name

Telephone No

Fax No

e-mail Address

Effective From Date

Effective To Date

Meter Operator Agent Details

Meter Operation Agent Name

Meter Operation Agent Identifier

Registration Effective From Date

Registration Effective To Date

Role Address Details

Address

Telephone No

Fax No

e-mail Address

Authorised Signatories

Name

Password

Contact Phone No

e-mail Address

Authorisation Levels

Activity

Effective From Date

Effective To Date

Certification/Accreditation Details

Certification/Accreditation Status

Metering System Registration Details

Metering System Identifier

BSC Party ID

Meter Operator Agent ID

Effective From Date

Effective To Date

Boundary Point Details

Boundary Point ID

Boundary Point Type

Effective From Date

Effective To Date

BM Unit Registration Details

BM Unit Name

BM Unit ID

BM Unit Type

NGC BM Unit Name

GSP Group ID

Trading Unit Name

Lead Party Identifier

Generation Capacity (MW)

Demand Capacity (MW)

Production / Consumption Flag

Exempt Export Flag

Base TU Flag

Transmission Loss Factor

FPN flag

Credit Qualifying Status

Interconnector ID

Effective From Date

Effective To Date

Interconnector Registration Details

Name

Additional Details

Interconnector ID

Effective From Date

Effective To Date

GSP Group Registration Details

GSP Group Registrant (ie the responsible distribution business)

GSP Group ID

GSP Group Name

GSP Details

GSP ID

Effective From Date

Effective To Date

Physical Interface Details:

8.22 CRA-I022: (output) Metering System Details

Interface ID:

From: CRA-I022

To: TAA

User:

TAA

Title:

Metering System Details

BSC Reference:

CRA SD 10.3

Mechanism:

Manual

Frequency:

On Request

Volumes:

Low

Interface Requirement:

The CRA system shall issue a report on the metering systems attributed to a given Technical Assurance Agent.

Metering System Registration Data

Metering System Details

Action Code

Metering System Identifier

BSC Party ID (registrant)

Meter Operator Agent ID

Effective From Date

Effective To Date

The first field of each record of the report is an Action Code, indicating whether the record has a) been added or changed; b) been deleted or c) not changed.

Physical Interface Details:

A physical definition is included in the spreadsheet to define the format of the report which is printed out and passed to TAA.

8.23 CRA-I030: (input) Data Exception Reports

This interface is defined in Section 4 asECVAA-I016 and SAA-I017, and in Part 1 of the Interface Definition and Design as BMRA-I010.

8.24 CRA-I045: (input) Withdrawing Party Authorisation and Notification Details

See ECVAA-I047 in this section.

8.25 CRA-I046: (input) Withdrawing Party Settlement Details

8.26 See SAA-I037 in this section.ECVAA-I001 (input): Registration Data

See CRA-I013 and CRA-I015 in section 4, CRA-I017 in this section

8.27 ECVAA-I011: Account Bilateral Contract Volume Report

Interface ID:

From: ECVAA-I011

To: SAA-I008

User:

SAA

Title:

Account Bilateral Contract Volume Report

BSC Reference:

ECVAA SD: 8.5, A

RETA ERR: 6

ECVAA BPM: 3.3, 4.21

RETA SCH: 4, B, 3.1, CP527

Mechanism:

Electronic data file transfer

Frequency:

Daily and in support of disputes

Volumes:

Interface Requirement:

The ECVAA Service shall issue an Account Bilateral Contract Volume Report to the SAA once a day. At the end of each Settlement Day, the ECVAA shall report Account Bilateral Contract Volumes for that Settlement Day to the SAA.

The ECVAA Service shall issue a revised Account Bilateral Contract Volume Report to the SAA as required to support disputes.

Note: Revision of ECVAA data in support of disputes will not cause credit cover tests to be retrospectively applied.

The Account Bilateral Contract Volume Report shall include:

BSC Party ID

Production/Consumption flag

ECVAA Run Number

Settlement Date

Settlement Period (1-50)

Account Bilateral Contract Volume (MWh)

8.28 ECVAA-I012: MVRN Report

Interface ID:

From: ECVAA-I012

To: SAA-I008

User:

SAA

Title:

MVRN Report

BSC Reference:

ECVAA SD: 9.2, 9.4, A

RETA ERR: 2

ECVAA BPM: 3.3, 4.19

RETA SCH: 4, B, 3.1, CP527

Mechanism:

Electronic data file transfer

Frequency:

Daily and in support of disputes

Volumes:

Medium

Interface Requirement:

The ECVAA Service shall issue a Metered Volume Reallocation Notification Report (initial and revised) to the SAA once a day. At the end of each Settlement Day, the ECVAA shall report valid Metered Volume Reallocation Notifications for that Settlement Day to the SAA.

The ECVAA Service shall issue a revised Metered Volume Reallocation Notification Report to the SAA as required to support disputes.

Note: Revision of ECVAA data in support of disputes will not cause credit cover tests to be retrospectively applied.

The Metered Volume Reallocation Notification Report shall comprise:

BM Unit ID

ECVAA Run Number

Settlement Date

Settlement Period (1-50)

Lead Party Production/Consumption flag

Subsidiary Party ID

Subsidiary Party Energy Account Production/Consumption flag

Metered Volume Fixed Reallocation (MWh)

Metered Volume Percentage Reallocation (%)

8.29 ECVAA-I016: (output, common) ECVAA Data Exception Report

This interface is defined in Section 4.

8.30 ECVAA-I020: (input) Data Exception Reports

This interface is defined in Part One as SAA-I017.

8.31 ECVAA-I036: (output) Publish Credit Default Report

Interface ID:

From: ECVAA-I036

To: BMRA-I018

User:

BMRA

Title:

Publish Credit Default Report

BSC Reference:

CP703, Variation 45

Mechanism:

Electronic Data File Transfer

Frequency:

As required

Volumes:

Low

Interface Requirement:

The ECVAA Service shall issue a Publish Credit Default Report to the BMRA as described in requirement ECVAA-F007.

The Publish Credit Default Report shall comprise:

Credit Default Notice:

BSC Party ID

Credit Default Level

Entered Default Settlement Day

Entered Default Settlement Period

Cleared Default Settlement Day

Cleared Default Settlement Period

Cleared Default Reason

Notes:

The Credit Default Level may be one of the following:

Level 1 Default;

Level 2 Default;

The Entered Settlement Day and Entered Settlement Period indicate when the BSC Party entered the reported default level.

The Cleared Settlement Day and Cleared Settlement Period indicate when the BSC Party cleared the reported default level.

The Cleared Default Reason indicates why the Party cleared default and may include one of the following

Credit Cover Percentage <= 75% of Credit Limit (Level 1 Default)

Credit Cover Percentage <= 90% of Credit Limit (Level 2 Default)

Authorisation Withdrawn by BSCCo Ltd (Discretionary).

Authorisation Withdrawn by BSCCo Ltd (Trading Dispute Upheld)

Party Withdrawn from BSC

8.32 ECVAA-I047: (output) Withdrawing Party Authorisation and Notification Details

Interface ID:

ECVAA-I047

User:

CRA

Title:

Withdrawing Party Authorisation and Notification Details

BSC Reference:

CP974

Mechanism:

Manual, by email or fax

Frequency:

On request

Volumes:

Low

Interface Requirement:

The ECVAA shall issue details of outstanding authorisations and notifications for a withdrawing participant, on request from the CRA.

Report Date

BSC Party / BSC Party Agent Name

BSC Party / BSC Party Agent Id

Authorisation and Notification Details

Indication of outstanding ECVNA / MVRNA authorisations for the party / agent¹

Date of last outstanding non-zero notifications for the party²

This field is set to “Yes” if outstanding ECVNA / MVRNA authorisations are in place or “No” otherwise. An outstanding authorisation is one where the effective to date is null or equal to or greater than the report date. If outstanding authorisations are found the maximum effective to date is given.
The date of the last outstanding non-zero notification gives the last date for which there are outstanding non-zero ECVN / MVRN volumes relating to the party. For the avoidance of doubt, this check is done at the individual notification level (i.e. not after netting the notifications to give the overall contract position). Where the party has a notification in place with no effective to date, the date of the last outstanding non-zero notification is reported as “evergreen”.

Physical Interface Details:

8.33 ECVAA-I048 (input) Physical Notification Data

See BMRA-I007 in this section.

8.34 SAA-I013: (output) Credit/Debit

This interface is defined in Section 4.

8.35 SAA-I001 (input): Registration Data

See CRA-I013 and CRA-I015 in section 4.

8.36 SAA-I002 (input): Credit Assessment Capability

See CRA-I017 in this section

8.37 SAA-I003 (input) SAA Balancing Mechanism Data

See BMRA-I007 in this section.

8.38 SAA-I004: (input) Period Meter Data

See CDCA-I027, CDCA-I028 and CDCA-I036 in this section.

8.39 SAA-I008: MVRN Report

See ECVAA-I011 and ECVAA-I012 in this section.

8.40 SAA-I015

This interface is redundant.

8.41 SAA-I016: (output, part 1) Settlement Calendar

This interface is defined in Part 1 of the Interface Definition and Design.

8.42 SAA-I017: (output, common) SAA Data Exception Report

This interface is defined in Part 1 of the Interface Definition and Design.

8.43 SAA-I037: (output) Withdrawing Party Settlement Details

Interface ID:

SAA-I037

User:

CRA

Title:

Withdrawing Party Settlement Details

BSC Reference:

CP974

Mechanism:

Manual,

Frequency:

On request

Volumes:

Low

Interface Requirement:

The SAA shall issue settlement details for a withdrawing participant, on request from the CRA.

Report Date

BSC Party Name

BSC Party Id

Settlement Details

Date of last non-zero metered volumes held in SAA

The date of the last metered volumes held in SAA is the last settlement date for which the party has non-zero metered volumes registered against its Interconnector, Supplier or CDCA metered BM Units.

Physical Interface Details:

8.44 SAA-I043: (output) Demand Control Instructions to CDCA

Interface ID:

SAA-I043

User:

CDCA

Title:

Demand Control Instructions to CDCA

BSC Reference:

P305

Mechanism:

Manual

Frequency:

As required

Volumes:

Low

Interface Requirement:

The SAA provides details of Demand Control Instructions to the CDCA as and when they are received from the NETSO via SAA-I003.

The Demand Control Instruction data shall include:

Demand Control Event ID

Start Date and Time

End Date and Time

Physical Interface Details:

8.45 SAA-I044: (input) Period BM Unit Demand Disconnection Volumes

See CDCA-I068 in this section.

8.46 CRA-I036: (output) Notification Agent Termination Request

Interface ID:

From: CRA-I036

To: ECVAA-I030

User:

ECVAA

Title:

Notification Agent Termination Request

BSC Reference:

CP503

Mechanism:

Manual

Frequency:

As required

Volumes:

Low

Interface Requirement:

The CRA Service shall issue Notification Agent Termination Requests to ECVAA when CRA is in the process of terminating an MVRNA or ECVNA role.

The Notification Agent Termination Request shall comprise:

Notification Agent Termination Request:

BSC Party Agent Id

BSC Party Agent Role (MVRNA or ECVNA)

Termination effective date

Physical Interface Details:

8.47 ECVAA-I031: (output) Notification Agent Termination Feedback

Interface ID:

From: ECVAA-I031

To: CRA-I037

User:

CRA

Title:

Notification Agent Termination Feedback

BSC Reference:

CP503

Mechanism:

Manual

Frequency:

As required

Volumes:

Low

Interface Requirement:

The ECVAA Service shall issue a Notification Agent Termination Feedback to CRA in response to a Notification Agent Termination Request.

The Notification Agent Termination Feedback shall comprise:

Notification Agent Termination Feedback:

BSC Party Agent Id

BSC Party Agent Role (MVRNA or ECVNA)

Termination effective date

Termination Status

Notes:

Termination status may indicate one of two situations:

The notification agent has no outstanding notification authorisations beyond the termination effective date (and therefore CRA may terminate the role)
The notification agent has some outstanding notification authorisations beyond the termination effective date (and therefore CRA may not terminate the role)

Physical Interface Details:

8.48 ECVAA-I033: (input) Credit/Debit Reports

See SAA-I013 in Section 4.

8.49 CDCA-I040: (output) BM Unit ‘Credit Cover’ Meter Volume Data Report

Interface ID:

From: CDCA-I040

To: ECVAA-I015

User:

ECVAA

Title:

BM Unit ‘Credit Cover’ Meter Volume Data Report

BSC Reference:

P215

Mechanism:

Electronic Data File Transfer

Frequency:

As required or daily

Volumes:

Up to 5000 BM Units

Interface Requirement:

Credit Cover meter volume data for BM Units is sent to ECVAA, as follows for each BM Unit:

BM Unit Identifier

Settlement Date

Settlement Period

Meter Volume

A Meter Volume value of NULL is used to represent where no value could be generated.

Physical Interface Details:

8.50 ECVAA-I015: (input) BM Unit ‘Credit Cover’ Meter Volume Data

See CDCA-I040 in section 9.

8.51 BMRA-I027: (input) Settlement Reports

This interface is defined in Section 5 and has the same format as the SAA-I014 Sub Flow 2 sent to the NETSO.

8.52 SAA-I049: Trading Unit Data

Interface ID:

SAA-I049

User:

BMRS

Title:

Trading Unit Data

BSC Reference:

P321

Mechanism:

Electronic

Frequency:

For each Settlement run

Volumes:

Interface Requirement:

The following data items will be sent by the SAA to the BMRS:

Trading Unit Name
Trading Unit Type
Settlement Date
Settlement Period
Settlement Run Type
Delivery Mode
Import Volume
Export Volume
Net Volume

Physical Interface Details:

8.53 SAA-I053: Daily Exchange Rate Report

Interface ID:

SAA-I053

User:

BMRS

Title:

Daily Exchange Rate Report

BSC Reference:

P344

Mechanism:

Electronic

Frequency:

For each Settlement Day

Volumes:

Medium

Interface Requirement:

The following data items will be sent by the BMRS to the SAA

Settlement Date
GBP-EUR Exchange Rate

Physical Interface Details:

8.54 SAA-I056: BM Unit Period Metered Volume

Interface ID:

SAA-I056

User:

CRA

Title:

BM Unit Period Metered Volume

BSC Reference:

CP1569, P415

Mechanism:

Electronic data file transfer

Frequency:

For each Settlement Day

Volumes:

Interface Requirement:

The following data items will be sent by the SAA to the CRA

Settlement Date
Settlement Run Type
BM Unit Id
Settlement Period
BM Unit Period Metered Volume
BM Unit Deviation Volume

Physical Interface Details:

9 Interfaces From and To Transfer Coordinator

9.1 CRA-I023: Issue Registration Transfer Report

Interface ID:

CRA-I023

User:

Transfer Coordinator (BSCCo)

Title:

Issue Registration Transfer Report

BSC Reference:

CRA SD 11.2, CP753, CP1223

Mechanism:

Manual

Frequency:

On Change of Status

Volumes:

Low

Interface Requirement:

On completion of entry of confirmed updates resulting from a transfer of metering system(s) to or from SMRA, the CRA shall issue a report to the Transfer Coordinator detailing the data entered.

Metering System registration details

Metering System Identifier

Meter Operator Agent ID

Effective from date

Effective to date

BM Unit details

BM Unit ID

Effective from date

Effective to date

SVA metering system identifiers

SVA MSID (as supplied with CRA-I005)

Physical Interface Details:

The report is a copy of data held on the database for each item. Note that SVA MSIDs as specified in CRA-I005 are not entered on the database and so, where this is available, a copy of the original CRA-I005 flow as received will form part of this report.

9.2 CRA-I038: Transfer from SMRS information

This interface is defined in Part 1 of the Interface Definition and Design.

9.3 CRA-I039: Transfer from SMRS report

Interface ID:

CRA-I039

User:

Transfer Coordinator

Title:

Transfer from SMRS report

BSC Reference:

CP753

Mechanism:

Manual

Frequency:

On Demand

Volumes:

low

Interface Requirement:

The following information is reported to the Transfer coordinator following receipt of new transfer from SMRS information

SVA registrant

Import SVA MSID

Export SVA MSID

Import CVA MSID

Export CVA MSID

CVA MOA

Site name

BM Unit Id(s)

Whether the CVA registrant is registered as a party in CMRS.

Whether the CVA Registrant has nominated a BM Unit Id to be registered in CMRS.

Whether the Registration Effective From Date is operationally achievable.

Whether the nominated BM Unit Id is ready for Registration in CMRS when the Registration Effective From Date is Confirmed by the Transfer Co-ordinator.

Whether the MOA in the Metering Systems Registration is valid.

Whether the transfer request is valid

comments/reasons for being invalid

Note:

SVA data can only be reported where this has been provided by the registrant

Physical Interface Details:

9.4 CRA-I040: Transfer to SMRS information

This interface is defined in Part 1 of the Interface Definition and Design.

9.5 CRA-I041: Transfer to SMRS report

Interface ID:

CRA-I041

User:

Transfer Coordinator

Title:

Transfer to SMRS report

BSC Reference:

CP753

Mechanism:

Manual

Frequency:

On Demand

Volumes:

low

Interface Requirement:

The following information is reported to the Transfer coordinator following receipt of new transfer to SMRS information

CVA registrant

Import SVA MSID

Export SVA MSID

Import CVA MSID

Export CVA MSID

Site name

BM Unit Id(s)

Whether the Metering System is registered in CRA

Whether the BM Unit(s) are registered in CRA

Whether the effective to date is possible

Whether the BM Unit is ready for deregistration

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

Whether the transfer request is valid

comments/reasons for being invalid

Note:

SVA data can only be reported where this has been provided by the registrant

Physical Interface Details:

9.6 CDCA-I055: (input) Transfer from SMRS information

This interface is defined in Part 1 of the Interface Definition and Design.

9.7 CDCA-I056: (output) Transfer from SMRS report

Interface ID:

CDCA-I056

User:

Transfer Coordinator

Title:

Transfer from SMRS report

BSC Reference:

CP753

Mechanism:

Manual

Frequency:

On Demand

Volumes:

low

Interface Requirement:

The following information is reported to the Transfer coordinator following receipt of new transfer from SMRS information

SVA registrant

Import SVA MSID

Export SVA MSID

Import CVA MSID

Export CVA MSID

CVA MOA

Site name

BM Unit Id(s)

Whether aggregation rules have been registered for the BM Units

Whether the BM Units and CVA Metering Systems are linked by the aggregation rules

Whether the transfer request is valid

comments/reasons for being invalid

Physical Interface Details:

9.8 CDCA-I057: (input) Transfer to SMRS information

This interface is defined in Part 1 of the Interface Definition and Design.

9.9 CDCA-I058: (output) Transfer to SMRS report

Interface ID:

CDCA-I058

User:

Transfer Coordinator

Title:

Transfer to SMRS report

BSC Reference:

CP753

Mechanism:

Manual

Frequency:

On Demand

Volumes:

low

Interface Requirement:

The following information is reported to the Transfer coordinator following receipt of new transfer to SMRS information

CVA registrant

Import SVA MSID

Export SVA MSID

Import CVA MSID

Export CVA MSID

Site name

BM Unit Id(s)

Whether aggregation rules have been registered for the BM Units

Whether the BM Units and CVA Metering Systems are linked by the aggregation rules

Whether the transfer request is valid

comments/reasons for being invalid

Physical Interface Details:

10 Interfaces From and To EMR Settlement Services Provider

10.1 SAA-I042: (output) BM Unit Chargeable Demand Report

Interface ID:

SAA-I042

User:

EMR Settlement Services Provider

Title:

BM Unit Chargeable Demand Report

BSC Reference:

EMRS

Mechanism:

Electronic data file transfer, XML

Frequency:

Daily

Volumes:

One per Settlement Run

Interface Requirement:

The SAA shall issue the BM Unit Chargeable Demand data to a EMR Settlement Services Provider for all Settlement Runs, The report shall include:

Settlement Date

Settlement Run Type

BSC Party ID

BM Unit ID

Settlement Period

TLM-Adjusted BM Unit Chargeable Demand

For each Settlement Period, the report will contain data for the following BM Units:

Supplier BM Units, for which the TLM-Adjusted BM Unit Chargeable Demand is defined as:

TLM-Adjusted BM Unit Chargeable Demand = TLM-Adjusted BM Unit Gross Demand - TLM-Adjusted BM Unit Non-Chargeable Demand

Where

TLM-Adjusted BM Unit Gross Demand = – TLM_ij * BM Unit SVA Gross Demand

TLM-Adjusted BM Unit Non-Chargeable Demand – TLM_ij * BM Unit SVA Non-Chargeable Demand

where BM Unit SVA Gross Demand and BM Unit SVA Non-Chargeable Demand are calculated by SVAA, and will be deemed to be zero if a value has not been received from SVAA; and

CVA BM Units other than Interconnector BM Units, for which the TLM-Adjusted BM Unit Gross Demand is defined as:

TLM-Adjusted BM Unit Gross Demand = TLM_ij * min (BM Unit Metered Volume, 0)

Where a Directly-connected or Embedded CVA BM Unit has been notified to the CRA as part of a EMR CVA BM Unit Declaration:

TLM-Adjusted BM Unit Chargeable Demand = 0

For all other Directly-connected or Embedded CVA BM Units:

TLM-Adjusted BM Unit Chargeable Demand = TLM-Adjusted BM Unit Gross Demand

Physical Interface Details:

This file will be sent in a format defined by an XML Schema established and maintained by the SAA.

1 P226

2 P215

3 P215

4 P226

5 This flow was added for the Introduction of Zonal Transmission Losses on an Average Basis (P82), but will not be used.

6 P215

7 For the interface to ECVAA and BMRA, the Production / Consumption Flag data item actually refers to Production / Consumption Status which is dynamically derived if the Production / Consumption Flag is set to null, or the Production / Consumption Status can be fixed by setting the Production / Consumption Flag for Exempt Export BM Units only.

8 With the exception that any WDCALF value exceeding ±9.9999999 shall be capped and reported as ±9.9999999 in the CRA-I020. The values of WDBMCAIC and WDBMCAEC reported in the CRA-I020 will still be derived using the ‘real’ uncapped WDCALF value.

9 With the exception that any NWDCALF value exceeding ±9.9999999 shall be capped and reported as ±9.9999999 in the CRA-I020. The values of NWDBMCAIC and NWDBMCAEC reported in the CRA-I020 will still be derived using the ‘real’ uncapped NWDCALF value.

10 With the exception that any SECALF value exceeding ±9.9999999 shall be capped and reported as ±9.9999999 in the CRA-I020. The values of WDBMCAEC and NWDBMCAEC reported in the CRA-I020 will still be derived using the ‘real’ uncapped SECALF value.

11 Where OCNMFD is referred to it should be interpreted as being equivalent to SPLD.

12 Where OCNMFW is referred to it should be interpreted as being equivalent to SPLW.

13 P226

14 This functionality was added for the Introduction of Zonal Transmission Losses on an Average Basis (P82), but will not be used.

15 The number of VAUs excludes GSP Groups and BM Units embedded in a Distribution System, which are not used in the calculation of Transmission Loss Factors

16 Indented to show that there may be more than one TLF for a BSC Year

CONTENTS

NETA Interface Definition and Design Document Part 2 – Interfaces to other service providers

0.1 Purpose

0.1.1 Summary

0.2 Scope

0.2.1 The Scope of this Document

0.3 Summary

0.4 Amendment History

0.5 References

0.6 Abbreviations

1 Common Interface Conventions

1.1 Interface Mechanisms

1.1.1 Manual

1.1.2 Electronic Data File Transfer

Common File Format

NGC File Format

Pool Transfer File Format

Interfaces to EMR

1.1.3 Internal Interfaces

1.1.4 Repeating Structure

The Tabs of the Spreadsheet

1.1.5 File names

1.1.6 Unstructured File Format

1.1.7 Acknowledgement Messages and Sequence Numbers

1.1.8 Time

1.1.9 Valid Sets

Activity

BMRA Exception Type

BM Unit Type

Charge Type

Organisation Type

Run Type

2 External Interface Summary

2.1 Interfaces by BSC Agent

2.1.1 BMRA Interfaces

2.1.2 CDCA Interfaces

2.1.3 CRA Interfaces

2.1.4 ECVAA Interfaces

2.1.5 SAA Interfaces

2.2 Interfaces by Corresponding Party

2.2.1 BSCCo Ltd Interfaces

2.2.2 FAA Interfaces

2.2.3 NETSO Interfaces

2.2.4 Stage 2 Interfaces

2.2.5 Transfer Coordinator Interfaces

2.2.6 Internal Interfaces

2.2.7 EMR Settlement Services Provider Interfaces

3 Interfaces From and To Multiple Parties

3.1 CRA-I004: (input) BSC Service Agent Details

3.2 CRA-I013: (output) Issue Authentication Report

3.3 CRA-I015: (output) BM Unit, Interconnector and GSP Group Data

3.4 CRA-I020: (output) Operations Registration Report

3.5 CRA-I028: (output) NGC Standing Data Report

3.6 ECVAA-I016: (output) ECVAA Data Exception Report

3.7 ECVAA-I025: (output) Credit Cover Minimum Eligible Amount Report

3.8 SAA-I013: (output) Credit/Debit Reports

4 Interfaces From and To the NETSO

4.1 BMRA-I002: (input) Balancing Mechanism Data

4.2 BMRA-I003: (input) System Related Data

4.3 BMRA-I010: (output, common) Data Exception Reports

4.4 BMRA-I014: (input) Price Adjustment Data

4.5 BMRA-I020: (input) BM Unit Fuel Type List

4.6 BMRA-I021: (input) Temperature Reference Data

4.7 BMRA-I022: (input) Daily Energy Volume Reference Data

4.8 BMRA-I023: (input) Wind Generation Registered Capacities

4.9 BMRA-I034: (input) Trading Unit Data

4.10 CDCA-I012: (output, part 1) Report Raw Meter Data

4.11 CDCA-I029: (output, part 1) Aggregated GSP Group Take Volumes

4.12 CDCA-I042: (output, part 1) BM Unit Aggregation Report

4.13 CDCA-I049: (output) Total Demand per GSP

4.14 CDCA-I051: (output) Report Meter Technical Details

4.15 CDCA-I067: (input) Disconnected CVA BM Units

4.16 CRA-I007: (input/output) Boundary Point and System Connection Point Data

4.17 CRA-I008: (input) Interconnector Registration Details

4.18 CRA-I013: (output, common) Issue Authentication Report

4.19 CRA-I014: (output, part 1) Registration Report

4.20 CRA-I020: (output) Operations Registration Report

4.21 CRA-I028: (output) NGC Standing Data Report

4.22 SAA-I012 (input, part 1) Dispute Notification

4.23 SAA-I014 (output) Settlement Report

4.28 BMRA-I024: (input) Large Combustion Plant Directive Spreadsheet¹³

6.15 CDCA-I062: (input) Receive Sample Settlement Periods¹⁴