The copyright and other intellectual property rights in this document are vested in Elexon or appear with the consent of the copyright owner. These materials are made available for you for the purposes of your participation in the electricity industry. If you have an interest in the electricity industry, you may view, download, copy, distribute, modify, transmit, publish, sell or create derivative works (in whatever format) from this document or in other cases use for personal academic or other non-commercial purposes. All copyright and other proprietary notices contained in the document must be retained on any copy you make.

All other rights of the copyright owner not expressly dealt with above are reserved.

No representation, warranty or guarantee is made that the information in this document is accurate or complete. While care is taken in the collection and provision of this information, Elexon Limited shall not be liable for any errors, omissions, misstatements or mistakes in any information or damages resulting from the use of this information or action taken in reliance on it.

AMENDMENT RECORD

Version	Date	Description of Changes	Changes Included	Mods/ Panel/ Committee Refs
0.1	Code Effective Date	Re-badged AP533 to form BSCP533
1.1	Code Effective Date	Submitted to the Panel for approval	NCR313
2.0	27/03/01	Approved by the Panel on 22/02/2001		P/13/008
3.0	01/11	Changes for Modification P68	P68	NPAB19/210
4.0	01/03/03	Updated to reflect the terminology used in the BSC	CP852	NPAB22/244
5.0	01/08/03	Updated for Modification P62	P62
6.0	06/01/04	Updated for Modification P99	P99
6.1	13/01/04	Updated with SVG and P99 comments	P99
7.0	01/05/04	Approved by SVG	P99
8.0	01/07/04	Consistency Amendments and Working Day timings updates	P99	SVG41/002
9.0	04/11/04	Updated for SVA November 04 Release	CP1016	SVG43/003
10.0	23/02/05	SVA February 2005 Release and BETTA 6.3	P159, CP1084, CP1091, CP1090, BETTA 6.3	SVG47/004
11.0	30/06/05	SVA June 05 Release	CP1057, CP1088	SVG52/005
12.0	03/11/05	SVA November 05 Release	CP1087	SVG56/004
13.0	23/08/07	P197 Release	P197 CP1176	115/04 SVG67/16 ISG68/02
14.0	26/06/08	June 08 Release	CP1223	ISG84/01 SVG84/02 PAB84/11 TDC109/01
15.0	26/11/08	P207 Release	P207	SVG91/06 PAB91/12
16.0	01/11/10	November 10 Release	CP1325	SVG111/01
			CP1339	SVG116/05 PAB116/06
17.0	01/07/11	June 11 Release¹	CP1334	SVG114/02
			CP1344	SVG122/02
			CP1348	SVG125/01
18.0	07/11/13	November 2013 Release	CP1387	PAB145/08 SVG145/04
			CP1399	PAB152/04 SVG152/08
19.0	05/11/15	November 2015 Release	CP1441	PAB174/04 SVG174/05
20.0	01/04/17	1 April 2017 Standalone Release	P339 Self-Governance	P261/06
21.0	01/09/21	1 September 2021 Non-Standard Release	P420	P316/05
22.0	24/02/22	24 February 2022 Standard Release	P429	Ofgem

1. Introduction

1.1 Scope and Purpose of the Procedure

This BSC Procedure covers the provision of Output Data and Market Indicator Data to the Performance Assurance Reporting and Monitoring System (PARMS) or the Performance Assurance Administrator (PAA). The data will be utilised within the following Performance Assurance Techniques (PATs):

Technical Assurance
Removal of Qualification
Monitoring and Reporting
Peer Comparison (public and non-public)
Supplier Charges
Error and Failure Resolution

The procedure will also cover the following techniques that are associated with the PARMS Service:

(i) Monitoring and Reporting; and

(ii) Peer Comparison (public and non-public)

The process will not cover internal activities carried out by the Performance Assurance Administrator.

All data specified in this BSCP to be sent to PARMS should be emailed to parms@parms.bsccentralservices.com.

All data specified in this BSCP to be sent to PAA should be sent to paa@elexon.co.uk.

All PARMS reports will be issued from donotreply@parms.bsccentralservices.com.

All PARMS queries should be raised via the BSC Service Desk (email: bscservicedesk@cgi.com; telephone: 0370 010 6950).

1.2 Risk Based Performance Assurance Framework

Performance Assurance Techniques (PAT) will be applied to a Performance Assurance Party (PAP) based on the net significance of the applicable Settlement Risk and an assessment of the PAP’s contribution to the Settlement Risk. Those PATs that are mandated under the BSC will continue to be applied, regardless of the net significance of the applicable Settlement Risk.

Settlement Risks and their net significance are captured on the Risk Evaluation Register (RER). All the Settlement Risks identified are rated in terms of severity of impact and probability (including a weighting for the strength of controls).

The Settlement Risks are assigned PATs to mitigate those risks and these PATs are recorded in the Risk Operating Plan (ROP) against each Settlement Risk.

The RER and the ROP are produced for a Performance Assurance Operating Period in accordance with the Annual Performance Assurance Timetable and the agreed Risk Evaluation Methodology (REM), which details the processes used to identify and evaluate the Settlement Risks and assess their materiality.

A Risk Management Plan (RMP) is created for each PAP based on the RER and the ROP and in accordance with the REM. The RMP will detail the PATs that will be deployed to a PAP during the course of a Performance Assurance Operating Period based on the Settlement Risks that are applicable to that PAP and the extent that the Settlement Risk applies to the PAP. If a PAP disagrees with their RMP, then there are provisions within the Code for them to query or appeal against it.

At the end of a Performance Assurance Operating Period, the Performance Assurance Board (PAB) will prepare an Annual Performance Assurance Report for the Panel detailing the assurance that has been provided during the course of the period, the extent to which Settlement Risks have been mitigated, and BSCCo costs of providing that assurance.

1.3 Main Users of the Procedure and their Responsibilities

This procedure will be used by authorised staff from Suppliers, Supplier Agents², SMRAs and BSC Agents. BSCCo will use this procedure for the provision of Market Indicator and standing data to the PAA. The procedure also provides an interface to data providers and to the BSC Panel and PAB (which will receive reports via this procedure).

The procedure will be used by the PAA for the collation and validation of data.

Throughout this procedure timescales are referred to in relation to the number of Working Days (WD), unless specifically stated otherwise. Where this procedure requires a communication to be issued on a given working day, users are asked to note the provisions for deemed receipt of post, fax and email set out in Section H of the BSC. When using email, users are advised to send the communication by 1600 hours in order to ensure its delivery by 1700 hours.

1.4 Use of the Procedure

The procedure provides details of the manner in which data should be provided to PARMS, the BSC Service Desk or the PAA, the process for querying the data and the manner in which Ad hoc Data and Drill Down Data can be obtained.

1.5 Balancing and Settlement Code Provision

This BSC Procedure has been produced in accordance with the provisions of the Balancing and Settlement Code, in particular Section S-1, Section J and Section Z. In the event of an inconsistency between the provisions of this BSC Procedure and the Code, the provisions of the Code shall prevail.

1.6 Associated Documents

This BSC Procedure interfaces with:

BSCP535	Technical Assurance of Suppliers and Supplier Agents
BSCP536	Supplier Charges
BSCP537	Qualification Process for SVA Parties, SVA Party Agents and CVA MOAs
BSCP538	Error and Failure Resolution
SVA Data Catalogue
CVA Data Catalogue

1.7 Assistance with using the Procedure

All queries about the use of this BSC Procedure should be made in the first instance to the PAA.

1.8 Acronyms and Definitions

1.8.1. Acronyms

BSC	Balancing and Settlement Code (the Code)
BSCCo	Balancing and Settlement Code Company
BSCP	Balancing and Settlement Code Procedure
CDCA	Central Data Collection Agent
CVA MOA	Central Volume Allocation Meter Operator Agent
DA(s)	Data Aggregator(s)
DC(s)	Data Collector(s)
EFD	Effective From Date
GSP	Grid Supply Point
HH	Half Hourly
HHDA	Half Hourly Data Aggregator
HHDC	Half Hourly Data Collector
Id	Identifier
LDSO	Licensed Distribution System Operator
MDD	Market Domain Data
MTD	Meters Technical Details
MS	Metering System
MSID(s)	Metering System Identifier(s)
NHH	Non Half Hourly
NHHDA	Non Half Hourly Data Aggregator
NHHDC	Non Half Hourly Data Collector
PAA	Performance Assurance Administrator
PAB	Performance Assurance Board
PARMS	Performance Assurance Reporting and Monitoring System
R1	First Reconciliation
R2	Second Reconciliation
R3	Third Reconciliation
RF	Final Reconciliation
RMP	Risk Management Plan
ROP	Risk Operating Plan
SF	First Settlement
SMRA	Supplier Meter Registration Agent
SVAA	Supplier Volume Allocation Agent
SVA HHMOA	Supplier Volume Allocation Half Hourly Meter Operator Agent
SVA NHHMOA	Supplier Volume Allocation Non Half Hourly Meter Operator Agent
SSD	Supplier Start Date
SSR	Supplier Settlement and Reconciliation
SVAA	Supplier Volume Allocation Agent
TA	Technical Assurance
TFF	text file format
WD	Working Day

1.8.2 Definitions

Performance Monitoring Report: is a report, in respect of performance against the Serial specified within the calculation guidelines, as being part of the suite of Serial that contribute to the Performance Monitoring Report, submitted by each Supplier, or by the Supplier’s appointed agents on behalf of each Supplier, for each GSP Group (or across all GSP Groups, as specified in the calculation guidelines) in which it is operating, or by a SMRA for SMRA Serials.

Performance Monitoring Log: will contain the Drill Down or Ad-hoc Data requested of Suppliers by the PAA, in agreed format and timescales.

Drill Down Data: is the data that is required such that:

(a) a calculation, the output of which is included within the Supplier’s Performance Monitoring Report, can be re-performed; and

(b) the context and variability of a measure that is included within the Supplier’s Monthly Performance Report can be established.

Drill down data requests can be made within 3 months of receipt of validated reports.

Ad-hoc Data: Any additional Performance data which can be requested only by a specific PAB mandate. It is assumed that such data will not be required on a regular basis.

Late Data: If data is not received by its due date, as stated within the calendar published by the PAA (see Appendix 5.9), it will be defined as late.

Output Data: is the performance data supplied, as referred to in paragraphs 5.2 to 5.5 by the Data Providers for input into the PARMS I.T. system.

Market Indicator Data: is data supplied as referred to in paragraph 5.8.

Data Provider: is a party responsible for providing data directly into PARMS. Data Providers are the CDCA, Suppliers (or Supplier Agents on behalf of their Suppliers), SMRAs, SVAA and the PAA.

Timing of activities: For the purposes of this BSCP and its Appendices +(x) WD means a number of WD exclusive of and following the day on which the start event occurs. -(x) WD means a number of WD exclusive of and prior to the day on which the start event occurs.

PARMS: Throughout this procedure PARMS refers to the PARMS IT system and PAA refers to the activities carried out by BSCCo in accordance with Section Z of the BSC.

Service Level: The level of performance should be achieved against each Serial and Standard as stated in the Calculation Guidelines (refer to Appendix B PARMS Calculation Guidelines)

2 Not Used

3. PARMS Data Provision - Interface and Timetable Information

3.1 Data Provision Authorisation Procedure

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.1.1	Upon nomination and prior to first data submission.	Provide details of the individual personnel authorised to provide/receive data and any password including one dedicated Email address.	Data Provider, except for SVAA and CDCA	BSC Service Desk	Authorised personnel details and password on Form F533/01	Email
3.1.2	By +1 WD of ref 3.1.1	Acknowledge receipt.	BSC Service Desk	Data Provider	Form F533/01	Email
3.1.3	By +1 WD of ref 3.1.1	Request Authorisation of details.	PARMS	PAA	Form F533/01	Email
3.1.4	By +1 WD of ref 3.1.1, if authorisation from PAA	Log details in Standing Data.	PARMS		Form F533/01	Internal
3.1.5	By +1 WD of ref 3.1.1, if authorisation not gained	Inform Data Provider	PAA	Data Provider		Email

3.2 Not Used

3.3 Provision of Output Data – Suppliers

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.3.1	To timing stated in Appendix 5.9	Suppliers Agents send Output Data to PARMS.	Supplier	PARMS	PARMS Report in accordance with BSCP533 Appendix A PARMS Data Provider File Formats and BSCP533 Appendix B – PARMS Calculation Guidelines.	Email
3.3.2a	By +1 WD of 3.3.1	Log receipt of data, validate and acknowledge successful processing of data.	PARMS	Supplier	Acknowledgement text on Email	Email
3.3.2b	By +1 WD of 3.3.1	Log receipt of data, validate and acknowledge unsuccessful processing of data.	PARMS	Supplier	Acknowledgement text on Email	Email
3.3.3a	By +1 WD of 3.3.2a	Receive positive acknowledgment. No further action required.	PARMS	Supplier		Email
3.3.3b	By +1 WD of 3.3.2b	Receive negative acknowledgment Supplier must ensure prompt submission of rejected data, in correct format in accordance with 3.11. Process returns to 3.3.1.	PARMS	Supplier		Email

3.4 Provision of Output Data – SMRAs

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.4.1	To timing stated in Appendix 5.9	SMRAs send Output Data.	SMRA	PARMS	PARMS Report in accordance with BSCP533 Appendix A – PARMS Data Provider File Formats and BSCP533 Appendix B – PARMS Calculation Guidelines.	Email F533/02 via e-mail
3.4.2a	By +1 WD of 3.4.1	Log receipt of data, validate and acknowledge successful processing of data.	PARMS	SMRA	Acknowledgement text on Email	Email
3.4.2b	By +1 WD of 3.4.1	Log receipt of data, validate and acknowledge unsuccessful processing of data.	PARMS	SMRA	Acknowledgement text on Email	Email
3.4.3a	By +1 WD of 3.4.2a	Receive positive acknowledgment. No further action required.	PARMS	SMRA		Email
3.4.3b	By +1 WD of 3.4.2b	Receive negative acknowledgment SMRA must ensure prompt submission of rejected data, in correct format in accordance with 3.11. Process returns to 3.4.1.	PARMS	SMRA		Email

3.5 Provision of Output Data – SVAA

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.5.1	To timing stated in Appendix 5.9	Send Output Data.	SVAA	PARMS	PARMS Report in accordance with BSCP533 Appendix A – PARMS Data Provider File Formats and BSCP533 Appendix B – PARMS Calculation Guidelines.	Email
3.5.2a	By +1 WD of 3.5.1	Log receipt of data, validate and acknowledge successful processing of data.	PARMS	SVAA	Acknowledgement text on Email	Email
3.5.2b	By +1 WD of 3.5.1	Log receipt of data, validate and acknowledge unsuccessful processing of data.	PARMS	SVAA	Acknowledgement text on Email	Email
3.5.3a	By +1 WD of 3.5.2a	Receive positive acknowledgment. No further action required.	SVAA	PARMS		Email
3.5.3b	By +1 WD of 3.5.2b	Receive negative acknowledgment SVAA must ensure prompt submission of rejected data, in correct format in accordance with 3.11. Process returns to 3.5.1.	SVAA	PARMS		Email

3.6 Provision of Standing Data (SVAA)

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.6.1	To timing stated in App. 5.9 or By +1 WD of updates to standing data.	Send data to PARMS.	SVAA	PARMS.	PARMS Report in accordance with BSCP533 Appendix A – PARMS Data Provider File Formats and BSCP533 Appendix B – PARMS Calculation Guidelines.	Email.
3.6.2a	By +1 WD of 3.6.1	Log receipt of data, validate and acknowledge successful processing of data.	PARMS	SVAA	Acknowledgement text on Email	Email
3.6.2b	By +1 WD of 3.6.1	Log receipt of data, validate and acknowledge unsuccessful processing of data.	PARMS	SVAA	Acknowledgement text on Email	Email
3.6.3a	By +1 WD of 3.6.2a	Receive positive acknowledgment. No further action required.	SVAA	PARMS		Email
3.6.3b	By +1 WD of 3.6.2b	Receive negative acknowledgment. SVAA must ensure prompt submission of rejected data, in correct format in accordance with 3.11. Process returns to 3.6.1.	SVAA	PARMS		Email

3.7 Not Used

3.8 Supplier Validation (SVAA Data)

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.8.1	By +5 WD of receipt of data	Query SVAA data provided to Supplier explaining what data is incorrect and why.	Supplier	PAA	Query Form F533/03	Email
3.8.2	By +1 WD of 3.8.1	Log query and acknowledge receipt	PAA	Supplier	Query Form F533/03 plus query number	Email
3.8.3	By +2 WD of 3.8.2	Analyse query in conjunction with SVAA, where appropriate. SVAA to provide revised data where necessary, in agreed format. PAA will acknowledge receipt of data sent by email.	PAA SVAA	SVAA PAA	Query Form F533/03, data F533/03, F533/04	Telephone Email
3.8.4	By +1 WD of 3.8.3	Provide response to Supplier, attach revised data as appropriate	PAA	Supplier	Query Response Form F533/04 and revised data	Email
3.8.5	Either: By +2 WD of receipt of data in 3.8.4	Either: a) Agree query resolution and proceed from Ref. 3.8.6. b) Disagree query resolution and give reasons. Proceed from Ref. 3.8.7.	Supplier	PAA	Query Response Form F533/04 and revised data Letter stating reason for appeal	Email
3.8.6	As required	Utilise data, corrected where appropriate. Go back to relevant section	PAA and/or PARMS		Revised data, or existing data	Internal
3.8.7	PAB Meeting	Notify the PAB that the Supplier wishes to appeal the decision of PAA/SVAA and provide reasons.	PAA	PAB	Query Response Form F533/04 and reasons for appeal from Supplier	Paper
3.8.8	PAB Meeting	PAB rules in the appeal: 1. Appeal upheld – go to section 3.8.6, then 3.8.9 2. Appeal dismissed – go to 3.8.6, then 3.8.9 3. Defer for more information	PAB	PAA	PAB decision	Internal
3.8.9	2 WD after PAB meeting	Communicate PAB decision to Supplier	PAA	Supplier	PAB decision	E-mail

3.9 Request for Ad-hoc Data

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.9.1	At any time	Request Ad-hoc data.	PAB	PAA	Any data as requested by the PAB.	Verbal by PAB agreement.
3.9.2	By +1 WD of 3.9.1	Request Ad-hoc data. Agree format of data and date upon which it will be provided (provision time-scale can be anything up to a maximum of 20 WD).	PAA	Data Provider (if the data to be provided is from a Supplier Agent then the request is made via the associated Supplier).	Request For Information Form F533/02, stating date upon which information required	Email
3.9.3	Within timeframe agreed under 3.9.2	Provide data in format and to timescales agreed in 3.9.2.	Data Provider	PAA	Data in format agreed under 3.9.2	Email
3.9.4a	By +2 WD 3.9.3	Assess data, log and acknowledge receipt seeking clarification if necessary.	PAA	Data Provider	Ad-hoc data in agreed format. Form F533/02.	Email or other agreed format
3.9.4b	By +5 WD of 3.9.4a	Receive acknowledgement and send clarification as necessary.	Data Provider	PAA	Acknowledgement form, F533/03	Email
3.9.5	By +10 WD of 3.9.4a or b (whichever is later).	Process data as required	PAA		Ad-hoc data	Internal

3.10 Request for Drill Down Data

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.10.1	As required	Request Drill Down data and agree format in which data will be provided.	PAA	Data Provider	Request For Information form F533/02 stating method for data provision.	Email
3.10.2	Within 20 WD of request	Provide data in format agreed with PAA	Data Provider	PAA	Provision of data form F533/02	Email
3.10.3a	By +4 WD of 3.10.2	Validate data and check for completeness. Log receipt of data and acknowledge receipt requesting clarification as required	PAA	Data Provider	Data acknowledgement form F533/03 Data and validation/ completeness rules (Appendix 5.12.)	Email Verbal
3.10.3b	By +4 WD of 3.10.3a	Receive acknowledgement and provide clarification if necessary.	Data Provider	PAA	Clarification Data as agreed	Email
3.10.4	As required	Process data as required	PAA		Validated data	Internal action

3.11 Request for Late Report

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
3.11.1	1 WD after date that data/reports required.	Identify those reports that are not received on due date. Request report from Data Provider (Supplier if the Data Provider is a Supplier Agent).	BSC Service Desk	Data Provider	Frequency of report provision and calendar (App 5.9) and Output Data Schedule Request For Information Form F533/02	Internal Email
3.11.2a	1 WD after 3.11.1	Acknowledge request and confirm date upon which report will be provided	Data Provider	BSC Service Desk	Letter stating date upon which report will be provided and reason for delay	Email
3.11.2b	By time agreed with PAA	Receive reports	Data Provider	PARMS	Reports requested in 3.11.1	Email
3.11.3	On date agreed with PAA	Proceed from ref. 3.2.1 or 3.3.1 or 3.4.1 or 3.5.1 as appropriate.

4 Monitoring and Publication of Peer Comparison Data Interface and Timetable Information

4.1 Monitoring and Reporting

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
4.1.1	On the 26th WD after the last day of the calendar month	Run reports and send to the PAA PAA reviews data	PARMS PAA	PAA	Validated PARMS data as determined by the PAB from the selection of Serials and Market Indicators noted within this BSCP	Email Internal
4.1.2	At any time after 4.1.1	If appropriate seek clarification of information/drill down data	PAA	Data Provider	Reports	Telephone, Email.
4.1.3	In time for PAB	As determined by the PAB from the selection of Serials and Market Indicators noted within this BSCP produce monthly validated PARMS data	PAA	PAB	PARMS Data	Paper
4.1.4	At PAB meeting	Request additional information if required	PAB	PAA	Validated PARMS Data as in 4.1.3	At meeting, via minutes or via Technical Secretary
4.1.5	1 WD after PAB meeting. Request information from Data Providers.	Agree format and timing of data provision (In accordance with ref. 3.9/3.10)	PAA	Data Providers	Instructions from PAB Request for Information Form F533/02	Telephone, Email,
4.1.6	To timescale agreed with PAA	Provide additional information (In accordance with ref. 3.9/3.10)	Data Provider	PAA	Request for additional information Form F533/02	As agreed with PAA
4.1.7	Within 1 WD of 4.1.6 and then as requested	Log receipt of data and acknowledge Analyse data as appropriate and forward to PAB as requested (In accordance with ref. 3.9/3.10)	PAA PAA	Data Provider PAB	Form F533/02 Additional information (and supporting analysis from PAA where appropriate)	Email/ Paper

4.2 Non Public Peer Comparison

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
4.2.1	26 WD after the last calendar day of the month	Produce Peer Comparison Reports and send to the PAA. PAA takes Peer Comparison Reports to PAB for authorisation Note: reports are produced quarterly, containing information for performance across the quarter period	PARMS PAA	PAA PAB	Performance Data for utilisation in PARMS and reports to PAB (ref. Appendix 5.15)	Email Paper
4.2.2	At next PAB	Review reports and determine if reports can be circulated. Notify PAA	PAB	PAA	Reports From PAA. Authorisation by majority vote from PAB.	Paper
4.2.3	Following PAB decision to circulate reports	Notify PARMS of PAB decision	PAA	PARMS		Email
4.2.4	Within 5 WD of receipt of decision	Circulate reports to authorised recipients (ref. Appendix 5.16)	PARMS	Report Recipients	Peer Comparison Reports	Via Email to authorised contacts (as per F533/06) of each Report recipient/Post.

4.3 Public Peer Comparison

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
4.3.1	26 WD after the last calendar day of the relevant month	Produce public Peer Comparison Report(s) and provide to the PAA and authorised Supplier contacts	PARMS PARMS	PAA Suppliers	Public Peer Comparison Report(s)	Email Email
4.3.2	Within 5 WD of receipt of 4.3.1	Notify PAA of any queries. If no response is received by 5 WD then PAA shall deem the public Peer Comparison Report(s) as fit for use and proceed to 4.3.3	Supplier	PAA	Query details on Form F533/07.	Email
4.3.3	Within 2 WD of 4.3.2, if no Query is received from any Supplier	Publish public Peer Comparison Report(s) on BSC Website	PAA		Copy of authorised public Peer Comparison Report(s	Internal Process
4.3.4	Within 5 WD of 4.3.2, if a Query is received from one or more Suppliers	Acknowledge query and discuss query with Supplier and either:	PAA	Supplier	Query details, relevant public Peer Comparison Report(s)	Email/Phone
		(a) take corrective action and regenerate relevant public Peer Comparison Report(s);	PAA	Suppliers		Email
		(b) determine that query can be resolved with no further action; or	PAA
		(c) if query cannot be resolved, refer to PAB for decision	PAA	PAB		Email
4.3.5	If action (c): At next PAB following 4.3.4	Review reports and determine if public Peer Comparison Report(s) can be published. Notify PAA	PAB	PAA	Public Peer Comparison Report(s) From PAA. Authorisation by majority vote from PAB	Paper
4.3.6	Within 2 WD of receipt of PAB decision; or following 4.3.4(a) or (b)	Publish public Peer Comparison Report(s) on BSC Website	PAA	Website	Copy of authorised public Peer Comparison Report(s)	BSC Website

4.4 Selecting a New Public Peer Comparison Subject

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
4.4.1	As required	Decide which new Serials/Standards appropriate for publication in public Peer Comparison Report(s)	PAB		Identification of a significant Settlement Risk, non-compliance or performance issue in accordance with the provisions of Section Z of the BSC	Internal process
4.4.2	At least 2 months before publication	Circulate details of new Serials/Standards to be published in public Peer Comparison Reports Circulate details of publication frequency	PAB	Supplier	Details of new Serials/Standards Details of frequency of publication Appendix 5.15	Email

REF

WHEN

ACTION

FROM

INFORMATION REQUIRED

METHOD

4.4.1

As required

Decide which new Serials/Standards appropriate for publication in public Peer Comparison Report(s)

PAB

Identification of a significant Settlement Risk, non-compliance or performance issue in accordance with the provisions of Section Z of the BSC

Internal process

4.4.2

At least 2 months before publication

Circulate details of new Serials/Standards to be published in public Peer Comparison Reports

Circulate details of publication frequency

PAB

Supplier

Details of new Serials/Standards

Details of frequency of publication

Appendix 5.15

4.5 Selecting a New Non-Public Peer Comparison Subject

REF	WHEN	ACTION	FROM	TO	INFORMATION REQUIRED	METHOD
4.5.1	As required	Decide which new Serials/Standards appropriate for publication in non-public Peer Comparison Report(s)	PAB		Identification of a significant Settlement Risk, non-compliance or performance issue in accordance with the provisions of Section Z of the BSC.	Internal process
4.5.2	At least 2 months before publication	Circulate details of new Serials/Standards to be published in non-public Peer Comparison Reports Circulate details of publication frequency	PAB	Report Recipients	Details of new Serials/Standards Details of frequency of publication Appendix 5.15	Email

REF

WHEN

ACTION

FROM

INFORMATION REQUIRED

METHOD

4.5.1

As required

Decide which new Serials/Standards appropriate for publication in non-public Peer Comparison Report(s)

PAB

Identification of a significant Settlement Risk, non-compliance or performance issue in accordance with the provisions of Section Z of the BSC.

Internal process

4.5.2

At least 2 months before publication

Circulate details of new Serials/Standards to be published in non-public Peer Comparison Reports

Circulate details of publication frequency

PAB

Report Recipients

Details of new Serials/Standards

Details of frequency of publication

Appendix 5.15

5. Appendices

5.1 Report Formats

A standard format for the submission of all data items will be used based upon the information contained within the appendices associated with this BSCP (Appendix A: PARMS Data Provider File Formats and Appendix B: PARMS Calculation Guidelines).

Data Files will be provided in the agreed formats by Email message addressed to PARMS.

NOTE: Data Providers must ensure that their files have undergone appropriate virus checking. Infected Emails are automatically deleted by PARMS and no notification sent to the Data Provider. Emails deleted for this reason will not be considered as having been delivered.

5.2 Not Used

5.3 SMRA Output Data Provision

The table below defines the data that will be provided to PARMS by the SMRAs. The ‘FILETYPE’ column references the SVA Data Catalogue. The 8 digit references beginning with a ‘P’ have an equivalent Technical Specification data flow.

Serial	Titled	FILETYPE
SP07	SMRA & SVAA MSID Count – SMRA File	P0045002

5.4 SVAA Output Data Provision

The table below defines the data that will be provided to PARMS by the SVAA. The ‘FILETYPE’ column references the SVA Data Catalogue. The 8 digit references beginning with a ‘P’ have an equivalent Technical Specification data flow.

Serial	Titled	FILETYPE
TA01	GSP Group Correction Factor	P0137001
TA02	Annual Demand Ratio	P0138001
SP07	SMRA & SVAA MSID Count – SVAA File	P0164001
SP08	Energy and MSIDs on Actuals	P0145002
SP09	NHH Defaults	P0146001

5.5 CDCA Output Data

The table below defines the data that will be provided to PARMS by the CDCA. The ‘FILETYPE’ column references the SVA Data Catalogue. The 8 digit references beginning with a ‘P’ have an equivalent Technical Specification data flow.

Serial	Titled	FILETYPE
CM01	CVA MOA Proving Tests	P0133001
CM02	CVA MOA Fault Resolution	P0134001

5.6 Standing Data

The following Standing Data will be submitted to PARMS for use in validating data submissions. The ‘FILETYPE’ column references the SVA Data Catalogue. The 8 digit references beginning with a ‘P’ have an equivalent Technical Specification data flow.

Standing Data	Data Provider	FILETYPE
PARMS Market Domain Data	SVAA	P0136001
Suppliers Trading / Ceased Trading in GSP Groups	SVAA	P0127001

5.7 Not Used

5.8 Market Indicator Information

The table below defines the data that will be provided to PARMS for the analysis of market indicators/processes. This data may be stored outside of PARMS.

Data Flow Description	Data Provider	Data Catalogue Flow Ref
GSP Group Correction Factor	SVAA	P0048001
Energy Settlement Mix	SVAA	P0049003
Energy Breakdown (Settlement Period and BM Unit)	SVAA	P0213001
Energy Breakdown (BM Unit)	SVAA	P0214001

5.9 Frequency of Report and Data Submission

Output Data Reports should be provided to PARMS in accordance with the following timetable:

Note: Data Providers are asked to note the provisions for deemed receipt of email communications as set out in Section H of the BSC, and are advised to send Output Data Reports by 1600 hours in order to ensure their delivery to PARMS by 1700 hours. Reports sent after 1600 hours and delivered by 1700 hours will still be counted as submitted on that working day. However, any Data Provider sending an Output Data Report after 1600 hours will bear the risk of its non-delivery by 1700 hours – and therefore the risk of the report being counted by PARMS as a late submission.

Data Provider	Timescale
Supplier (Performance Monitoring Reports)	20 WD after last calendar day of each month
Supplier (Performance Monitoring Logs)	As agreed with the PAA.
SMRA	10 WD after last calendar day of each month
SVAA	7 WD after last calendar day of each month or quarter as appropriate with the exception of: 1. Market Indicator data – 1 WD after the end of the previous week 2. MDD – as specified in BSCP509 3. Information on GSP Group Take and Supplier Group Take (needed for calculation of SCs) – 20 WD after last calendar day of each month. 4. Annual GSP Group Take Data – 20 WD after last calendar day of each financial year.
Standing Data (SVAA) Standing Data (Supplier DPI file)	1 WD after update 15 WD after last calendar day of each month

Note: Data from SVAA relates to Volume Allocation Runs carried out by SVAA in the previous calendar month.

A calendar stating specific dates for receipt of data will be published by the PAA on a yearly basis.

The table below defines the timing requirements for the relevant parties to provide data to PARMS for analysis of Market Indicators.

Market Indicator	Frequency
Energy Settlement mix	Weekly
Energy Breakdown (Settlement Period and BM Unit)	Weekly
Energy Breakdown (BM Unit)	Weekly

5.10 Standing Data

The following standing data will be maintained by PARMS. An SVA Data Catalogue Flow Reference number has been assigned where appropriate which relates to a Technical Specification data flow within the SVA Data Catalogue:

Authorised Data Providers

Suppliers must make the BSC Service Desk aware of any changes to their authorised Data Providers by using form F533/01.

Supplier Charges

National Monthly Cap for each year
Annual GSP Group Take Data (provided by SVAA) – SVA Data Catalogue Flow Reference P0125001
- For each GSP Group, the total GSP Group Take in the previous 12 months
- The total GSP Group Take for all GSP Groups in the previous 12 months
Supplier Payment Disbursement Factor
Trading Parties Payment Disbursement Factor
Performance Level for each Supplier Serial/Standard and SC payable per unit of failure to meet the level
Trading Party Main Funding Shares for each month
Apportionment data (provided by SVAA or determined from data provided by SVAA) – SVA Data Catalogue Flow Reference P0120002.
- For each Supplier in a GSP Group, the Total Supplier deemed take for each month
- For each GSP Group the total GSP Group take for each month
- For each Supplier in a GSP Group, the Supplier NHH Energy for each month
- For each GSP Group, the Total NHH Energy in GSP Group for each month

Market Domain Data

MDD is required so that the performance data received can be validated. The data will be provided by the SVAA.

The categories of MDD that will be maintained are:-

GSP Groups
Market participants
Market participant roles (supplier, SVA NHHMOA, SVA HHMOA, NHHDC, HHDC, NHHDA, HHDA, SMRA)
Reconciliation Run types

Output Data Schedule

The following data flow is required from the SVAA 7 WD after the end of each calendar month to support the construction of the Output Data Schedule.

Suppliers Start Trading/Cease Trading in GSP Group: To identify which Suppliers are trading in which GSP Group with a start effective date and if they have ceased trading in the GSP Group, an end effective date – P0127001.

5.11 Other Data Provision

The PARMS system will support and SP02, as follows:

Serial SP02 – Delivery of Performance Logs:

Total number of days late per Supplier (for all requested logs and all relevant GSP Groups) for the previous reporting period. Timescales for receipt of Performance Monitoring Logs are agreed with the PAA.

5.12 Validation and Completeness Rules

This section of the BSC Procedure contains the rules associated with the checking of data validity and completeness.

The data provided to PARMS will be validated to determine if:

(a) data provided by authorised person (valid Email address)

(b) all report details complete

If anomalies are discovered, or if additional data is required, the PAA will request additional or replacement data.

The PAA will maintain an output data schedule that will specify the report type and content for each category of data provider. A complete set of data reports is defined as:

all the output data provided by a particular data provider for a Supplier and its Agents operating in a single GSP Group, where appropriate, for a reporting month in accordance with the output data schedule.

If the completeness check fails then Output Data will only be passed for further processing where it is complete for a Serial. Thus, if any element of the data which applies to a single Serial for one Agent working for one Supplier in a single GSP Group is incomplete, then all data for that Serial for that Agent working for that Supplier in that GSP Group is not passed for further processing.

PARMS will run with all Complete Data even if it is currently being queried.

The Output Data is validated against the data format requirement as defined in the standard template (or as agreed with PAA for Ad-hoc and Drill Down data) and any codification is validated against the MDD and Supplier Data Provider Information.

If re-submission is required, the total set of data for the Data Provider for the relevant Serial is required.

If the PAA amends data, an audit log of the amendment will be generated by PARMS. A copy of this audit log will be sent to the PAB and any affected Data Provider (if the Data Provider is Supplier Agent then both Supplier Agent and associated Supplier will be informed).

SVAA Data used for Peer Comparison

SVAA sourced data which is to be used for Peer Comparison and Supplier Charges (SC) purposes will be copied to the relevant Supplier for checking.

The Supplier is invited to approve the data or raise a query within the given timescales. If no response is received, it will be assumed that the data has been cleared for use.

In the event that a Supplier queries peer comparison/SC data and the PAA/Supplier/SVAA cannot agree ahead of the timetabled production of the Peer Comparison/SC reports, the PAA will take instruction from the PAB to either:

(a) Exclude the Supplier from all Peer Comparison/SC reports for that quarter;

(b) Exclude the Supplier from the Peer Comparison/SC report to which the queried data relates;

5.13 Not Used

5.14 Monitoring & Reporting

The PAA will run monthly reports that will support the analysis of:

the performance of Suppliers (Serials SP02);
trends in those PARMS reports that are stated in this BSCP.

These reports will form the basis of a monthly PARMS data report that will be produced by the PAA for review by the PAB (as detailed in section 4.1). The PARMS data report will include a summary and analysis of that information provided in the report, including consideration of the trends in performance and market indicators over any reporting period that is specified by the PAB. Any unusual occurrences/anomalies/areas of concern will be highlighted to the PAB.

The PAA will maintain a log of reports despatched to other parties, and must record the despatch and receipt dates for confidential and/or commercially sensitive reports.

5.15 Peer Comparison Serials & Standards

The Peer Comparison Technique will apply to the following Serials and standards (as defined within the PARMS Calculation Guidelines). The PAB will determine those PARMS Serials to be included in the Public and Quarterly Peer Comparison Reports and as per sections 4.2 and 4.3.

Serial	Titled	Reporting Level for PC (National or GSP)
CM01	CVA MOA Proving Tests	National by CVA MOA
CM02	CVA MOA Fault Resolution	National by CVA MOA
NC11	Missing NHH Meter Reads & History from Old NHHDC to New NHHDC	GSP Group by NHHDC
SP02	Delivery of Performance Logs	National by Supplier
SP07	SMRA & SVAA MSID Count	GSP by Supplier
SP08	Energy and MSIDs on Actuals	GSP by Supplier
SP09	NHH Defaults	GSP by Supplier

5.16 Peer Comparison Report Distribution and Publication

5.16.1 PAA Distribution of Peer Comparison Reports

PARMS will distribute Peer Comparison Reports as follows:

Recipient Content

Panel All reports (upon request)

PAB All reports

Suppliers All reports (except CM01 and CM02)

Suppliers’ Agents Respective Agent report (where Agent appears on the graph)

BSC Website All reports notified to Suppliers as being subject to publication in accordance with paragraphs 4.4 and 5.16.2

5.16.2 Publication Criteria

PAB may choose to publish all, none or some of the Serials and Standards set out within this BSCP
PAB is not obligated to choose to publish the same subset of Serials and Standards publicly to those that are made available to the nominated recipient at each Supplier or Supplier Agent
PAB may elect to change (in accordance with this BSCP) the subset of Serials and Standards published to highlight a specific performance issue that has been identified as requiring attention by either the BSC Auditor, the Authority, the Panel or BSCCo in accordance with Section 4.4
PAB shall not change the subset of public Peer Comparison Reports published in order to highlight the performance of a Supplier or Supplier Agent in a month for which PAB has already seen performance data for that or any other Supplier or Supplier Agent
Public Peer Comparison Reports shall be routinely updated - at least every two months or at another frequency determined by the PAB
Each public Peer Comparison Report published must include the performance data of all Suppliers or Supplier Agents for which a full set of data is available across the reporting period
The PAB shall ensure that the format of each Serial or Standard to be published is meaningful for purposes of comparing Supplier or Supplier Agent performance against that Serial or Standard. This means that the PAB shall, amongst other relevant factors, consider in relation to each Serial or Standard to be published, whether to present the data as actual results or as percentages.

5.17 Error and Failure Resolution and Escalation

Once a performance issue is identified and initial investigation undertaken, the PAA may wish to refer this matter to the PAB. The procedure for this referral and any subsequent escalation to the PAB or the Panel is in accordance with BSCP538, Error and Failure Resolution.

Appendix A: PARMS Data Provider File Formats

The PARMS File Formats Specification is associated with BSCP533 but is a separate document.

Appendix B: PARMS Calculation Guidelines

The PARMS Calculation Guidelines document is associated with BSCP533 but is a separate document.

6. Forms

F533/01

Data Provision Authorisation Form

To:	BSC Service Desk
From:		Date:
Company Name:
Address:		Participant Id:


Category of Data Provider	SMRA Supplier * Delete as appropriate
Authorised Personnel: Names:
Telephone No:
Data submission email address:

These contact details are: In addition to existing contact(s) / A replacement for existing contact(s) *

* Delete as appropriate

Please email BSC Service Desk.

F533/02

Request for Information

To:
Company Name:
From:	PAA	Date:
Contact No:

Reporting Period: From:		To:

Log Query* No:
* Delete as appropriate
Description/Request:

Please email information/data PAA.

F533/03

Query Form

To:	PAA		Date:
From:			Authorised Signature
Telephone No:
Category of Data Provider		SMRA/Supplier/SVAA/CDCA:
Log No:

Description of Query:

Please send to PAA.

F533/04

Query Response

To:		Company Name:
From:	Performance Assurance Administrator	Signature:
Date:		Telephone No:
Query No:
Response to Query:

F533/05

Supplier Validation Response (Supplier Agent submitted data)

To:

BSC Service Desk

From (Supplier Name):

Date:

Telephone No:

I hereby wish to confirm the following data and agree its use in PARMS techniques.

File ID (Taken from the relevant received report)	Reporting Period	Serial	Data Provider

I hereby wish to reject the following data and do not agree its use in PARMS techniques.

File ID (Taken from the relevant received report)	Reporting Period	Serial	Data Provider	Reason for rejection of Data

Please send to BSC Service Desk.

F533/06

Peer Comparison Contact Authorisation Form

Email to BSC Service Desk

Authorised Contact to Receive Peer Comparison Reports

Authorised Contact Name: ……………………………………..

Organisation Name: …………………………………………….

Participant Role (Delete as appropriate):

Supplier

Market Sector (Delete as appropriate):

Half Hourly / Non Half Hourly

Participant Id: ………………………………..

Address: ……………………………………………………………..

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

Tel: …………………………………………………………

Authorised contact Email Address: ……………………………………………

This contact is: In addition to existing contact(s) / To replace existing contact(s)*

* Delete as appropriate

F533/07

Peer Comparison Query Form

To:	Performance Assurance Administrator
From:		Authorised Signature:
Tel:
Log No:
Description of Query:

Please Email the PAA.

THIS SECTION TO BE USED BY PAA

I hereby acknowledge receipt of your query.

Name:

Signature:

Query Number assigned:

Date:

7. Data Processing Reports

The following reports are those generated by PARMS and issued to participants to support data processing, validation and authorisation activities. The file naming convention for each report is included beneath each report type.

7.1 Email Receipt Report

ER_<Email Received Number>.txt

P_A_R_M_S

Email received from:

Received on:

Subject:

The following attachments were processed from this email:

The following problems were encountered when processing this email:

Report created:

7.2 Data Receipt Report

DR_<Date File Received>_<File Load Number>.log

P_A_R_M_S

Data file:

File type:

Attached to email received on: [DATETIME] from:

Creation date time:

Period End date:

Validation Results:

Report created:

7.3 Not Used

7.4 Third Party Output Data Report

TR_<Reporting Period>_<Supplier ID>_X_<Serial ID>_<Corresponding DR Log Number>.txt

TR_<Reporting Period>_<Agent ID>_<Agent Role Code>_<Supplier ID>_X_<Serial ID>_<Corresponding DR Log Number>.txt

TR_<Reporting Period>_<Agent ID>_<Agent Role Code>_<Serial ID>_<Corresponding DR Log Number>.txt

P_A_R_M_S

The following data has been submitted to PARMS on your behalf by the Participant detailed below. No queries raised on this data by close of business [DD-MMM-YYYY] will be taken as acceptance. It remains your responsibility to ensure all reporting is complete, accurate and BSC compliant.

PARMS Reference:

Serial:

From Participant Id:

From Role Code:

File Name:

Received:

Period End Date:

Contents:

[(spooled details)]

Report created: [Sys date/time]

7.5 Not Used

1 Please note: CP1334, CP1344 and CP1348 were implemented as part of the June 2011 Release, effective from 01 July 2011

2 SVA MOAs will be subject to the requirements of this PARMS URS for the period of the “SVA MOA Performance Assurance Transition Period” detailed in Section Z 5.1.1A – 5.1.1C

CONTENTS

BSCP533 : PARMS Data Provision, Reporting and Publication of Peer Comparison Data

1. Introduction

1.1 Scope and Purpose of the Procedure

1.2 Risk Based Performance Assurance Framework

1.3 Main Users of the Procedure and their Responsibilities

1.4 Use of the Procedure

1.5 Balancing and Settlement Code Provision

1.6 Associated Documents

1.7 Assistance with using the Procedure

1.8 Acronyms and Definitions

1.8.1. Acronyms

1.8.2 Definitions

2 Not Used

3. PARMS Data Provision - Interface and Timetable Information

3.1 Data Provision Authorisation Procedure

3.2 Not Used

3.3 Provision of Output Data – Suppliers

3.4 Provision of Output Data – SMRAs

3.5 Provision of Output Data – SVAA

3.6 Provision of Standing Data (SVAA)

3.7 Not Used

3.8 Supplier Validation (SVAA Data)

3.9 Request for Ad-hoc Data

3.10 Request for Drill Down Data

3.11 Request for Late Report

4 Monitoring and Publication of Peer Comparison Data Interface and Timetable Information

4.1 Monitoring and Reporting

4.2 Non Public Peer Comparison

4.3 Public Peer Comparison

4.4 Selecting a New Public Peer Comparison Subject

4.5 Selecting a New Non-Public Peer Comparison Subject

5. Appendices

5.1 Report Formats

5.2 Not Used

5.3 SMRA Output Data Provision

5.4 SVAA Output Data Provision

5.5 CDCA Output Data

5.6 Standing Data

5.7 Not Used

5.8 Market Indicator Information

5.9 Frequency of Report and Data Submission

5.10 Standing Data

5.11 Other Data Provision

5.12 Validation and Completeness Rules

5.13 Not Used

5.14 Monitoring & Reporting

5.15 Peer Comparison Serials & Standards

5.16 Peer Comparison Report Distribution and Publication

5.16.1 PAA Distribution of Peer Comparison Reports

5.16.2 Publication Criteria

5.17 Error and Failure Resolution and Escalation

6. Forms

7. Data Processing Reports

7.1 Email Receipt Report

7.2 Data Receipt Report

7.3 Not Used

7.4 Third Party Output Data Report

7.5 Not Used