Advanced Search

CVA Data Catalogue

v 26.0
Download

Balancing and Settlement Code

CVA Data Catalogue

26.0

Date: 1 April 2020

CVA DATA CATALOGUE

1. Reference is made to the Balancing and Settlement Code and, in particular, to the definition of “Data Catalogue” in Section X, Annex X-1 thereof.

2. This CVA Data Catalogue is 26.0.

3. This CVA Data Catalogue is effective from 1 April 2020.

4. This CVA Data Catalogue has been approved by the Panel.

Intellectual Property Rights, Copyright and Disclaimer

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

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

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

AMENDMENT RECORD

Version

Effective Date

Description of Change

Changes Included

Mods/Panel/ Committee Refs

1.0

April 2000

Draft For Review

1.0

May 2000

Post Internal Review

1.1

June 2000

Inclusion of BMRA interfaces

2.0

August 2000

NETA Baseline v1.3

3.0

March 2001

NETA Baseline V3.2

4.0

August 2001

Authorised, Modification P10, Change Proposal 519 and additions for consistency with NETA IDD 3.6 and EPFAL manual flows

5.0

August 2002

Release 2 Final

P8, P18a, P33, CP508, CP527, CP547, CP555, CP560, CP569, CP593, CP595, CP597, CP615, CP619, CP755

6.0

December 2002

December Release Final

CP511, CP532, CP559, CP566, CP632, CP751

7.0

March 2003

February 2003 Release

P55, P71, P78, CP753, CP754, CP797

8.0

June 2003

June Release Final

CP553, CP571, CP577, CP703, CP743, CP750, CP756, CP777, CP832, CP841, CP858, CP869, CP877 (P4 and P78 Previous Releases) and CP708

9.0

November 2003

November 2003 Release Final

10.0

June 2004

CVA June 2004 Release (Final)

P98, CP915, CP998. Further P98 review comments applied. P82 Removal

ISG/40/003

11.0

November 2004

CVA November 2004 Release

P98 Phase 2

12.0

February 2005

CVA February 2005 Release

CP1078, P140

13.0

November 2005

CVA Programme November 2005 Release

CP1061

P192

ISG/48/002

14.0

November 2006

BSC Systems November 2006 Release P194

P194

15.0

23 August 2007

P197 Release

P197

P/115/04

16.0

26 June 2008

June 08 Release

CP1223

ISG84/01

17.0

6 November 2008

November 08 Release

P214

ISG90/04

18.0

25 June 2009

June 09 Release

CP1265

ISG97/01

SVG97/01

19.0

5 November 2009

November 09 Release

P217

Panel 142/06

20.0

7 November 2013

November 2013 Release

CP1399

ISG149/04

21.0

16 December 2014

December 2014 Release

P291, P295

ISG162/01

22.0

29 March 2019

29 March 2019 Standalone Release

P369

Panel 285/12

23.0

7 November 2019

November 2019 Release

P386 Self Governance

Panel 291/05

24.0

11 December 2019

11 December 2019 Standalone Release

CP1517

ISG220/01

ISG222/03

25.0

27 February 2020

27 February 2020 Release

P394 Self Governance

P297/07

26.0

1 April 2020

1 April 2020 Standalone Release

P354

ISG227/0

Annex A Data File Specification.

Annex B Data Dictionary.

Annex C National Electricity Transmission System Operator (NETSO) EDL Interface.

1 Purpose and Scope

1.1 Purpose of this document

This document, the CVA Data Catalogue contains information relating to all the communication interfaces between CVA BSC Agents or the National Electricity Transmission System Operator (NETSO) and BSC Parties and Party Agents.

This document specifies, where appropriate, references to relevant sections of the NETA and EPFAL IDD Part 1 documents. The NETA and EPFAL IDD Part 1 documents contain information on data items and file formats, the participants involved in exchange of each file, and references to the owner of each file and its associated network (where this detailed information is not available in the NETA and EPFAL IDD Part 1 documents, it will be included in this document). It provides a consolidated repository of NGC EDT/EDL specs.

This document is a Code Subsidiary Document and its purpose is to form the Data File Catalogue for all CVA communications, as set out in the BSC Section O.

1.2 Scope of the CVA Data Catalogue

The CVA Data Catalogue includes all data interfaces between CVA BSC Agents (SAA, CRA, BMRA, ECVAA, CDCA, FAA) or the NETSO and Parties or Party Agents. It does not include SVAA interfaces, which are specified in the SVA Data Catalogue, and it does not include communications between central service providers.

Because of the different nature of the NETSO’s EDL interface this has been excluded from the Data Dictionary and included as a separate Annex C.

2 Reference Documents

The following documents are referenced by the CVA Data Catalogue.

2.1 SAA, CRA, BMRA, ECVAA and CDCA Interfaces

NETA Interface Definition and Design Document (Part 1).

NETA Interface Definition and Design Spreadsheet (Part 1).

2.2 NETSO Interfaces

EDT Interface Specification

EDL Interface Specification

2.3 FAA Interfaces

EPFAL Interface Definition and Design (Part 1).

3 Interface Specifications

This section specifies the general principles that apply to all data files in the electronic data file transfer interfaces between Parties (or their agents) and the NETSO’s Electronic Data Transfer (EDT) Interface.

Full details of the NETSO’s Electronic Dispatch Logging (EDL) are given in Annex [C] of this document.

For information on CVA BSC Systems Interface Specifications, please refer to the NETA IDD Part 1 document and spreadsheet.

For information on FAA Interface Specifications, please refer to the EPFAL IDD Part 1 document.

3.1 NETSO EDT Interface Specifications

3.1.1 Data File Format

All data will be submitted using the single file format specified below. All data types for Balancing Mechanism Units (BMUs) assigned to the BSC Parties and their Agents may be included within the file.

Data within the file will be validated on a record by record basis.1

Submissions for each BSC Party or Agent2 will be made in Comma Separated Value (CSV) text formatted files. Each submission file will consist of one or more records, with each record being a single line of text.

3.1.2 File Header

The File header format is as follows.

Field

Format

Comments

Data Record Type

Alphanumeric

Up to 4 Characters.

One of:

PN

Physical Notification

BOD

Bid-Offer Data

MEL

Maximum Export Limit

MIL

Maximum Import Limit

RURE

Run Up Rates Export

RURI

Run Up Rates Import

RDRE

Run Down Rates Export

RDRI

Run Down Rates Import

NDZ

Notice to Deviate from Zero

NTO

Notice to Deliver Offers

NTB

Notice to Deliver Bids

MZT

Minimum Zero Time

MNZT

Minimum Non-Zero Time

SEL

Stable Export Limit

SIL

Stable Import Limit

MDV

Maximum Delivery Volume

MDP

Maximum Delivery Period

BSC Party or Agent Name

Alphanumeric

Up to 9 Characters

BM Unit Name

Alphanumeric

Up to 9 Characters

3.1.3 File Footer

The text string ‘<EOF>’ indicates the end of the file.

3.1.4 Record Formats

Each record will consist of a number of fields, each separated by a comma. Each record will include a record header consisting of the same initial fields, as shown in section 3.1.2 above. The remainder of each record will contain data according to the data record type included in the record header, as defined in the main body of the CVA Data Catalogue below.

Any records that start with an asterisk (‘*’) will be ignored, thereby allowing comments to be included in submission files.

3.1.5 Repeating Structure

The repeating structure is as defined as follows.

Id

Row Type

range

L1

L2

L3

L4

data type

valid set

item name/group description (comments)

EDT01

F (File Type)

Title of Flow (plus sub-flow number where appropriate)

ABCD

R (Record Type)

record type appears as the first field in an electronic file. Record types are unique within a file type but not across all file types. The same file type may be reused in a different flow with a different structure.

Tnnnn

D (Data Item)

Each data item is assigned a Data Item Id. The Data Item Id is used for all occurrences of the same Data Item.

1-*

range indicates how many occurrences of this record type may appear at the current level. (comment may further refine the repeating rules)

0-* indicates unlimited repeat (optional record type)

1-* indicates unlimited repeat with at least one instance of the record type

1 indicates the record type appears exactly once

2 indicates the record type appears exactly twice

48 indicates that this record type is repeated 48 times

46-50 is used where a record type is repeated 46, 48 or 50 times to contain settlement data.

G

G indicates that this is a repeating group i.e. a record type

1

1 indicates that this is a data item within a record type

O

O indicates that this is an optional data item within the record type (in electronic files, this means that the field may be empty)

Data items and nested record types must appear in the order stated.

L1, L2… define the nesting structure.

text(9)

this field will contain a text string with up to 9 characters

integer(n)

this field will contain an integer with an optional leading “-“ followed by up to n digits

decimal

this field will contain a real number

decimal (n,d)

this field will contain a real number. There will be an optional leading “-“ followed by up to d digits after the decimal point and up to (n-d) before the decimal point

char

this field will contain a single character

boolean

this field will contain a single character T or F

date

this field will contain a date YYYYMMDD

datetime

this field will contain a date and time YYYYMMDDHHMMSS

valid set id

the field’s values are constrained to be within the definition of the identified valid set - see section 2.2.11

3.1.6 File naming

Each submission file will have a file name consisting of two parts and a file extension. The file extension will be ‘.SBM’ to indicate that the file contains submission data defined to be as follows:

Title

Meaning

Field Size

Field Format

Comments

TANAME

BSC Party or Agent Name

9

XXXXXXXXX

name should be padded with ‘_’ to the full field width

SEQNO

Sequence number

4

9999

the submission sequence number

Thus, the filename will be of the form

XXXXXXXXX9999.SBM

For example, for a BSC Party or their Agent the name 'TR_AGT', for which the previously submitted file sequence number was 20, the file name would be:

TR_AGT___0021.SBM

The BSC Party or their Agent portion of the name must correspond with the agreed name of the submitting agent. All submission files must have a 'SBM' file type marker. If these conditions are not met, the submitted file will be rejected in its entirety.

3.1.7 Use of Sequence Numbers

The submission sequence number contained within the file name must be submitted successively. Each time a file is submitted the sequence number should be incremented by one. Should a file be submitted out of sequence it will be rejected in its entirety. All subsequent out of sequence files will be rejected until a file with sequence number corresponding to the last successful submission sequence incremented by one is submitted.

The first submission made via EDT to the NETSO by a BSC Parties or their Agents should have a submission sequence number of 0001. Leading zeroes should be included to the full field width. After submission 9999 the next submission number should roll over to 0001.

3.1.8 Time

All times are GMT and must be a whole number of minutes. In the table definitions, the following field format conventions are used:

Time format: [CCYY-MM-DD hh:mm] where the following definitions apply:

CCYY year (numeric) MM month (numeric) DD day (numeric) a single space separator between date and time:3 hh hours mm minutes

3.2 NETSO EDL Interface Specifications

3.2.1 Principle

The EDL Interface is a message based rather than file based system, and as such is not part of this document. For completeness, however, an overview has been included in Annex C. The interface between the NETSO and Participants will in general be implemented by one of the suppliers providing this service. The necessary information for producing such an interface is available directly from the NETSO.

4 Data File Description Standards

All standards relating to electronic CVA BSC Agent interfaces and the data items contained therein are specified in the NETA IDD Part 1 document.

1 Although, hypothetically, there is no upper limit to the frequency with which data may be submitted or to the size of data files, it is possible that an error on a Client system might jeopardise the stability of the entire EDT submission system by resubmitting a large file at frequent intervals. For this reason, if BSC Party’s frequency of submissions exceeds a defined normal rate for a sustained period, then that Party’s, or their Agent's, account shall be locked until they contact NGC to resume normal service.

2 All nomenclature of Agents and their respective BMUs, including the 9-character field above, will be agreed between NGC and the relevant Agent or their representative as part of the Agent/BMU registration process.

3 Whilst all data handling is automatic, the NGC format is intended to be as legible as possible. Generally additional spaces are allowed either side of fields. The only restriction on additional spaces is in the date/time field separating the date and time portions, where only a single space character must be present.