NETA Interface Definition and Design Document Part 1 – Interfaces with BSC Parties and their Agents

v 51.0
Download

complex image of process

NETA Interface Definition and Design: Part 1

Interfaces with BSC Parties and their Agents

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 one only contains details for interfaces which involve BSC Parties and their Agents.

Version

51.0

Effective date

23 February 2023

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.

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

P253

28/06/2012

28.0

CP1364

CP1367, BMRS Zones Review

27/06/2013

29.0

CP1382 – 27 June 2013 Release

ISG140/02

26/06/2014

30.0

CP1397 – 26 June 2014 Release

ISG150/02

01/08/14

31.0

ORD005 – Electricity Market Reform

Directed by the Secretary of State

16/12/14

32.0

P295, P291 – 16 December 2014 Release

ISG162/01

25/06/15

33.0

P310 – 25 June 2015 Release

ISG169/05

05/11/15

34.0

P305, P309, 5 November 2015 Release

ISG174/04

23/02/17

35.0

P326, 23 February 2017 Release

ISG188/05

29/06/2017

36.0

P321 Self-Governance, P329 Alternative 29 June 2017 Release

ISG194/02

02/11/2017

37.0

P336 Self-Governance; P342 Alternative 2 November 2017 Release

ISG198/04

01/11/2018

38.0

CP1503 – 1 November 2018 Release

P277/04

CP1506 – 1 November 2018 Release

P280/09

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

11/12/2019

41.0

11 December 2019 – Standalone Release CP1517

ISG220/01

ISG222/03

18/12/2019

42.0

18 December 2019 – December Standalone Release, CP1516

P292/06

01/04/2020

43.0

01 April 2020 – Standalone Release P354

ISG227/04

03/12/2020

44.0

03 December 2020 – Standalone Release CP1535

P305/06

18/03/2021

45.0

18 March 2021 – Standalone Release P408 Self-Governance

ISG234/02

01/04/2021

46.0

01 April 2021 – Standalone Release CP1538

ISG236/03

01/04/2021

47.0

01 September 2021 Non-Standard Release – P420

P316/05

04/11/2021

48.0

04 November 2021 Standard Release

P310/04

24/02/2021

49.0

24 February 2022 Standard Release

ISG247/01

30/06/2022

50.0

30 June 2022 Standard Release – P375, CP1562

P309/06

ISG253/04

23/02/2022

51.0

23 February 2023 Standard Release

P314/06, ISG259/09

1 Introduction

1.1 Purpose

1.1.1 Summary

This document is Part 1 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 1 is limited to the definition and design of interfaces between the BSC Service System and the 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.

1.2 Scope

1.2.1 The Scope of this Document

This document describes the interfaces relevant to five of the seven BSC Service Systems (and some interfaces relating to a sixth). The interfaces relating to the Funds Administration Agent service are described separately in the FAA Interface Definition and Design. The services within the scope of this document are:

BMRA

Balancing Mechanism Reporting Agent

CDCA

Central Data Collection Agent

CRA

Central Registration Agent

ECVAA

Energy Contract Volume Aggregation Agent

SAA

Settlement Administration Agent

SVAA

Supplier Volume Allocation Agent (certain interfaces only)

These six are termed here the Central Services. Section 3.1.6 specifies which SVAA interfaces fall within the scope of this document (and which are specified elsewhere).

1.2.2 Types of Interface

Interfaces between the Central Services and other systems which are not part of the Central Services are termed External and are the main subject of the Interface Definition and Design. These interfaces are of two kinds:

    • Party interfaces – BSC Parties and Agents, including ECVNA, MVRNA, IA, IEA, SMRA and MOA. These interfaces are covered in Part 1 (this document).

    • System interfaces – to other BSC services: FAA, SVAA, the National Electricity Transmission System Operator (NETSO) and BSCCo Ltd. These interfaces are covered in Part 2 (a separate document).

External interfaces which do not connect to a Central Service, e.g. FAA to Bank, are not included in the Interface Definition and Design.

The interfaces with BSC Parties and Agents will need a wider forum of agreement than the other interfaces, and will be tested in Market Interface Testing (MIT). The Interface Definition and Design is therefore divided into two separate parts for these two interface types. The two parts will be issued independently and will therefore have different version numbers.

1.3 NETA Interface Overview

1.3.1 Introduction

The approach to the interface definition process adopted in this document is a layered top down structure. The highest layer is the business need for the interface to exist. This business transaction is supported by successive lower layers working down via the logical and physical design to the communications protocol and the physical format and media for the data transfer. This is summarised in the table below.

Layer

Defined in Section

Source/Based on

Business Process Definition

1.3.2

Business Process Model

Logical Flow Definition

1.3.3 & 2.2

Industry practice

Physical Message Definition

1.3.4

Industry practice (with MV90 for meter data)

Data Transfer Protocol

1.3.5

FTP over TCP/IP

1.3.2 The Business Process Level

A Business Process can be represented by a ‘transaction’ – a message or sequence of messages that fulfil a business function, for example ‘submit report request’ leads to ‘report sent’ or ‘error message – not available’. Each of these messages can be defined as a logical ‘flow’ to meet the requirement. The flow can classified by its characteristics at the business level:

    • Originating Party

    • Destination Party

    • Initiating event (e.g. user request, another flow, timer expires)

    • Frequency in unit time

    • Data content at the business level.

    • Mechanism: Electronic Data File Transfer or Manual

    • Volume – frequency * mean message size

    • Validation rules.

Flows are given unique identifiers. The same flow can be sent by more than one originator and to more than one party and as a result of different initiating events. These origin/destination/initiation cases are called here different ‘instances’ of the same flow. The same flow can have internal and external instances.

1.3.3 Logical Message Definition

The next step is to define the flow contents at the logical level. This defines what each flow will contain in terms of fields, their attributes and how the fields are grouped within the flow. At the same time, the rules for which fields and groups are optional or mandatory and whether and how often groups can be repeated need to be specified.

To do this, a naming convention and layout standards have been set for those flows so that the information can be presented in a consistent and unambiguous form. The format is based on industry practice, and is similar to that used by the industry to support the Supplier Volume Allocation settlement process.

1.3.4 Physical Message Definition

The Logical Message definition encompasses all the data visible at the user level and is closely aligned to the database design as the flows populate the database and/or are derived from their contents. Physical file formats define, for flows that are transferred electronically, the data representation and control information. Similarly to the logical definition, a naming convention and layout standards have been defined so that the information can be exchanged and validated in a consistent and unambiguous form. The definitions are again based on industry practice.

Details of the physical file format are specified in section 2.2

1.3.5 Data Transfer Protocols

This section only applies to flows which employ the electronic data file transfer mechanism.

Details of the proposed protocols for data transfer are in [COMMS]. For each flow, data transfer will be via FTP over TCP/IP unless specified otherwise.

1.4 Summary

Part 1 of the Interface Definition and Design covers interfaces with BSC Parties and Agents, and is organised as follows:

    • Section 2 describes common interface conventions, in particular defining the approach to interfacing via file transfer.

    • Section 3 gives a summary of the interfaces, organised by BSC agent and by corresponding party.

    • Sections 4 to 7.24.3 define the interfaces to each of the BSC Agents.

Part 2 of this document contains interfaces where the only parties involved are within the Central Volume Allocation system, i.e. interfaces between the following services / systems:

    • BMRA

    • CDCA

    • CRA

    • ECVAA

    • FAA

    • SAA

    • NETSO

    • SVAA

    • BSCCo Ltd

Note that parts 1 and 2 of the Interface Definition and Design are issued separately and will therefore have different issue numbers.

1.5 References

1.5.1 BSC Documents

[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

1.6 Abbreviations

AMVLP

Asset Metering Virtual Lead Party

BM

Balancing Mechanism

BMRA

Balancing Mechanism Reporting Agent

BMU

Balancing Mechanism Unit

BSC

Balancing and Settlement Code

WDCALF

Working Day Credit Assessment Load Factor

NWDCALF

Non-Working Day Credit Assessment Load Factor

CDA

Central Design Authority

CDCA

Central Data Collection Agent

CRA

Central Registration Agent

ECV

Energy Contract Volume

ECVAA

Energy Contract Volume Aggregation Agent

ECVN

Energy Contract Volume Notification

ECVNA

Energy Contract Volume Notification Agent

ECVNAA

Energy Contract Volume Notification Agent Authorisation

ENTSO-E

European Network of Transmission System Operators for Electricity

FAA

Funds Administration Agent

FPN

Final Physical Notification

FTP

File Transfer Protocol

GMT

Greenwich Mean Time

GSP

Grid Supply Point

IA

Interconnector Administrator

IEA

Interconnector Error Administrator

ISO

International Standards Organisation

LAN

Local Area Network

MAR

Meter Advance Reconciliation

MDP

Maximum Delivery Period

MDV

Maximum Delivery Volume

MEL

Maximum Export Limit

MIDP

Market Index Data Provider

MIL

Maximum Import Limit

MOA

Meter Operator Agent

MPAN

Meter Point Administration Number

MVR

Meter Volume Reallocation

MVRN

Meter Volume Reallocation Notification

MVRNA

Meter Volume Reallocation Notification Agent

MVRNAA

Meter Volume Reallocation Notification Agent Authorisation

NETSO

National Electricity Transmission System Operator as the holder of the Transmission Licence and any reference to “NETSO”, “NGESO”, “National Grid Company” or “NGC” in the Code or any Subsidiary Document shall have the same meaning.

NETA

New Electricity Trading Arrangements

NWDBMCAEC

Non-Working Day BM Unit Credit Assessment Export Capability

NWDBMCAIC

Non-Working Day BM Unit Credit Assessment Import Capability

PTFF

Pool Transfer File Format

QPN

Quiescent (final) Physical Notification

RETA

Revised Electricity Trading Arrangements

SAA

Settlement Administration Agent

SECALF

Supplier Export Credit Assessment Load Factor

SMRA

Supplier Meter Registration Agent

SVAA

Supplier Volume Allocation Agent

TAA

Technical Assurance Agent

TCP/IP

Transport Control Protocol/Internet Protocol

VLP

Virtual Lead Party

WAN

Wide Area Network

WDBMCAEC

Working Day BM Unit Credit Assessment Export Capability

WDBMCAIC

Working Day BM Unit Credit Assessment Import Capability

2 Common Interface Conventions

2.1 Interface Mechanisms

This section outlines the different interface mechanisms used.

2.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.

2.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].

A common format is used for data files transferred between the Central Services and the BSC Parties and their Agents. This is specified in Section 2.2.

2.1.3 Meter System Interface

The MV-90 interface is used to interact with meter systems (This is defined in the CDCA Design Specification Appendix A.).

2.1.4 BMRA Publishing Interface

A TIBCO messaging interface running over IP is used for providing screen-based data for BMRA users.

2.2 Data File Format

A common format is used for data files transferred electronically between the Central Services and the BSC Parties and their Agents.

These files use the ASCII character set. They consist of:

    • Standard header

    • Collection of data records using standard format

    • Standard footer

The file format is similar to the Energy Market Data Specification file format defined for use in Supplier Volume Allocation. The difference is that the format defined for Central Volume Allocation has the following enhanced features:

    • sequence number added to the header;

    • Party Ids in the header longer than the 4 character Pool Participant Ids;

    • Role Codes in the header longer than the 1 character Pool Participant Role Codes;

    • Message Role (Data/Response) added to the header;

    • free-format message type allowed

The components of the file are specified below:

2.2.1 File Header

The file header will be a record containing the following fields:

AAA-File Header

Field

Field Name

Type

Comments

1

Record Type

Text(3)

= AAA

2

File Type

Text(8)

5 character type plus 3 character version

3

Message Role

char

‘D’ Data or ‘R’ Response

Note that the P0283, P0284, P0293, P0294 , P0329 and P0330 files produced by SVAA have Role ‘D’

4

Creation Time

datetime

Date/Time file was created. Specified in GMT.

(For Response messages this field contains the Creation Time of the message being replied to)

5

From Role Code

Text(2)

6

From Participant ID

Text(8)

7

To Role Code

Text(2)

8

To Participant ID

Text(8)

9

Sequence Number

integer(9),

rolling over from 999999999 to 0

A separate Sequence Number is used for each From Role Code / From Participant ID / To Role Code / To Participant ID combination.

NB numbers used must be contiguous so recipients can detect missing files. See section 2.2.8 for more details of the use of Sequence Number.

(For Response messages this field contains the Sequence Number of the message being replied to. This includes the P0283, P0284, P0293, P0294, P0329 and P0330 files produced by SVAA.)

10

Test data flag

Text(4)

Indicates whether this file contains test data

=OPER or omitted for operational use, other values for test phases

Either field 6 or field 8 will be the Participant ID of the Central Systems in every case. (For SVAA the Participant ID is ‘CAPG’).

The possible values for role code are

‘AV’

(AMVLP)

‘BM’

(BMRA)

‘BC’

(BSCCo Ltd)

‘BP’

(BSC Party)

‘CD’

(CDCA)

‘CR’

(CRA)

‘DB’

(Distribution Business)

‘EC’

(ECVAA)

‘EN’

(ECVNA)

‘ER’

(Energy Regulator)

‘FA’

(FAA)

‘IA’

(Interconnector Administrator)

‘MI’

(Market Index Data Provider)

‘MO’

(Meter Operator Agent)

‘MV’

(MVRNA)

‘PA’

(BSC Party Agent)

‘PB’

(Public - also used for files made available for shared access)

‘SA’

(SAA)

‘SG’

(BSC Service Agent)

‘SO’

(NETSO)

‘SV’

(SVAA)

‘TS’

(Supplier)

‘VP’

(VLP)

This is a subset of the domain ‘Organisation Type’ defined in section 2.2.11.9, containing only those organisation types which send or receive electronic data files. Considering flows to BSC Parties: when a party receives a file because it is a Distribution Business, the To Role Code will be ‘DB’; when it receives a file because it is an Interconnector Administrator, the To Role Code will be ‘IA’; in all other cases, the To Role Code will be ‘BP’.

Message Role is used for handling receipt acknowledgement, and is further described in Section 2.2.7.

2.2.2 File Footer

The file footer will be a record containing the following fields:

ZZZ-File Footer

Field

Field Name

Type

Comments

1

Record Type

text(3)

= ZZZ

2

Record count

integer(10)

Includes header and footer

3

Checksum

integer(10)

Although type is shown as integer(10) the value is actually a 32-bit unsigned value and hence will fit in an “unsigned long” C variable.

The value of Checksum is defined according to the following sequence:

    • initialise to zero

    • consider each record in turn (including header but excluding trailer)

    • Break each record into four byte (character) sections (excluding the end of line character), padded with nulls if required, and exclusive OR (XOR) them into checksum.

The algorithm for this is illustrated by the following ‘C-like’ pseudo code.

num_chars = strlen (record_buffer)

FOR (i = 0; i < num_chars;)

value = 0

FOR (j = 0; j < 4; i++, j++)

IF i < num_chars

value = ((value << 8 ) + record_buffer[i])

ELSE

value = value << 8

END IF

ENDFOR

checksum = checksum XOR value

ENDFOR

The checksum value is a 32 bit value. This is treated as an unsigned integer and appears in the file footer as integer(10).

2.2.3 Record Formats

Each record in the file is presented as follows:

<record type><field separator><field>[…]<field separator><record delimiter>

Where:

    • record type : 3 characters

    • record delimiter : Line Feed (ASCII 10)

    • field separator: “|” (ASCII 124)

NB field separator will thus appear at end of record (i.e. after last field), prior to the linefeed

A record of n fields will have n+1 field separators.

Data fields are presented as follows:

type

Rules

integer (n)

optional leading “-“ for negative numbers

no leading zeros

maximum n digits

field may have “-“ and from 1 to n digits

decimal (n,d)

maximum n digits

maximum d digits after decimal point

maximum (n-d) digits before decimal point

leading “-” required for negative numbers

no trailing zeros

no leading zeros other than where -1< value <1, then number may start with “0.”

To clarify, the value 0.123 can be represented as:

0.123 or .123,

but not:

00.123 (an invalid leading zero) or 0.1230 (an invalid trailing zero)

Valid representations of zero are:

0 0.0 .0 0. –0 –0.0 -.0 -0.

but not as a decimal point with no digits.

text (n)

up to n characters

field may not contain field separator

no leading spaces

no trailing spaces

boolean

T or F

date

YYYYMMDD

time

HHMM

timestamp

HHMMSS

datetime

YYYYMMDDHHMMSS

char

single character

null

if a field is no longer needed in a future version of a flow, then its data type will be defined to be null, meaning that its value is always null

Text and char fields may contain only the following characters:

Character

ASCII

Character

ASCII

Character

ASCII

space

32

+

43

@

64

!

33

,

44

A-Z

65-90

"

34

-

45

[

91

#

35

.

46

\

92

%

37

/

47

]

93

&

38

0-9

48-57

^

94

'

39

:

58

_

95

(

40

;

59

a-z

97-122

)

41

=

61

{

123

*

42

?

63

}

125

Optional fields are permitted to have nothing between the field separators.

2.2.4 File Types, Record Types and Repeating Structure

The structure of records and their nesting rules are specified using tables. The tables are defined in the NETA Interface Definition and Design Part 1 spreadsheet. The following explains the meaning of data in those tables.

Each interface (flow) may be represented by more than one physical message type (sub-flow) indicated by multiple file types in the physical file format spreadsheet e.g. CRA-I014 has multiple file types R0141, R0142 etc. The file type is made up of three parts: the first character identifies the system (‘B’ (BMRA), ‘C’ (CDCA), ‘R’ (CRA), ‘E’ (ECVAA), or ‘S’ (SAA)); the second to fourth characters are taken from the number within the flow name; the final character identifies the sub-flow id.

These tables are not provided for most manual flows. Where it is useful to provide this information for a manual flow, a note is provided in the “Physical Details” section of the logical definition of the flow.

Nesting is indicated by use of L1, L2 etc. Items at L2 make up a group at L1, items at L3 make up a group at L2 etc.

Id

Row Type

Flow version / range

L1

L2

L3

L4

data type

valid set

item name/group description (comments)

C0011

F

(File Type)

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

ABC

R

(Record Type)

record type appears as the first field in an electronic file. Record types are unique across all file types.

N0001

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

46-50 is a special case meaning 46, 48 or 50 (but not 47 or 49) - this applies to the number of Settlement Periods in a Settlement Day (which might be a clock change day)

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)

N

N indicates that this is an unused data item within the record type (in electronic files, this means that the field will 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

Different versions of flows are documented in the tables as follows. On the ‘File Type’ record, the flow version / range field indicates the version of the flow (a blank entry indicates version 1). For example, the records shown below define version 1 and version 2 of flow E0221.

Id

Row Type

flow version / range

L1

L2

L3

L4

data type

valid set

item name/group description (comments)

E0221

F

ECVAA-I022: Forward Contract Report

E0221

F

002

ECVAA-I022: Forward Contract Report (version 2)

2.2.4.1 The Tabs of the Spreadsheet

There is one tab for each of the Central Systems with which the BSC Parties and Party Agents communicate via electronic data file transfer: BMRA, CRA, ECVAA, CDCA, SAA and SVAA. The Response tab reproduces the structure of the ADT record given in section 2.2.7 below in spreadsheet format. The Valid Set tab reproduces the information given in section 2.2.11 below in spreadsheet format. The Flow Role tab lists which From Role Codes and To Role Codes can validly appear in the header for each File Type. The Groups tab is the master definition of each Record Type; the record type definitions in the BMRA, CRA, ECVAA, CDCA, SAA and SVAA tabs are copied from there. The Items tab is the master definition of each item; the item definitions in the BMRA, CRA, ECVAA, CDCA, SAA and SVAA tabs are copied from there. The Valid Sets, Flow Role, Groups and Items tabs in the IDD Part 1 spreadsheet encompass the contents of the IDD Part 1 and IDD Part 2 spreadsheets.

2.2.5 File names

Files delivered to and sent from NETA must have names which are unique across all Central Systems within any month. The following convention for filenames is proposed, and is in use by the Central Systems:

characters 1-2: Sender role

characters 3-14: Unique identifier (alphanumeric, e.g. may be a sequence number)

(This convention is sufficient for the Central Systems to uniquely identify all incoming files, because these systems move incoming files into a directory whose name identifies the sending participant id. If incoming files have filenames longer than 14 characters, then the Central Systems will truncate the filenames on receipt).

The filenames do not include an extension.

Where files are placed in a shared (read only) area for multiple users to download, the file name will contain meaningful fields to easy allow identification.

2.2.6 Unstructured File Format

To allow for flexibility, an unstructured file format is also defined. This could be used for:

    • Ad hoc data transfers and text reports

    • Newly defined messages which have not yet been allocated formal file formats

The unstructured file format will contain the following elements:

1. Standard header record with File Type set to UNSTR001

2. Any ASCII text, with the proviso that no lines may begin with ‘ZZZ’.

3. Standard trailer record

2.2.7 Response Messages

As described in [COMMS], participants have a choice between two methods of receiving files from the Central Systems: either the Central Systems push files to the participant systems (‘Push Method’), or the participant systems pull files from the Central Systems (‘Pull Method’). For the Push Method, the Central Systems consider that a data file has been successfully delivered when the FTP ‘push’ returns a success code. For the Pull Method, the participant systems indicate that they have successfully pulled a file by deleting it from the source directory.

Note the web submission service will allow an agent to create a notification file within the system, and in reply, receive a response to this on a web screen. The web service will therefore not send a file based response to a web submitted notification.

There is only one method available for sending files to the Central Systems: participant systems push the files to the Central Systems. Participant systems should use the FTP ‘push’ success code to determine that the file has been successfully sent.

The remainder of this section applies to electronic data files sent both to and from the Central Systems, other than SVAA (which responds to incoming data with specific response files such as the P0283, P0284, P0293 and P0294, rather than the generic response files described in this section).

When a system receives a data file, it must reply by sending a response file. The purpose of the response file is to indicate whether the data file has been validated as being syntactically correct.

The Message Role field in the header record is used for differentiating a response file from a data file. A data file is sent with the message role set to data. The response file comprises the header as received, with from/to participant and role reversed and message role set to response (see section 2.2.1), followed by the ADT record(s) and a standard trailer record (ZZZ). There may be more than one ADT record if multiple problems are found with the file.

ADT-Acknowledgement Details

Field

Field Name

Type

Comments

1

Record Type

Text(3)

= ADT

2

Received Time

datetime

(GMT)

Time that the message being acknowledged was received by the receiving party

3

Response Time

datetime

(GMT)

Time that the response message was generated by the receiving party

4

File Name

text(14)

Name of file this response relates to

5

Response Code

integer(3)

A code indicating the nature of the acceptance / rejection

6

Response Data

text (80)

Any data that gives additional information in fixing the problem

The possible values for the Response Code with the meaning and the appropriate action are:

Response Code

Meaning

Appropriate Action

NACK codes

file is rejected

1

Syntax Error in Header Record

Correct and resend.

2

To Participant details in header record are not correct for the actual recipient.

Correct and resend.

3

Unexpected Sequence Number in Header record.

See section 2.2.8

4

Syntax Error in Body. Error Data field contains line number where error detected.

Correct and resend.

5

Syntax Error in Footer Record

Correct and resend.

6

Incorrect Line Count in Footer Record

Correct and resend.

7

Incorrect Checksum in Footer Record

Correct and resend.

ACK codes

file has arrived and been accepted

100

File received

none - file has arrived and its contents have passed the validation checks covered by the NACK response codes

101

Duplicate file received

ensure files are not being resent unnecessarily - a file has arrived with a header identical to one already received

The diagram below illustrates an exchange of files using the push mechanism, where a data file is sent via FTP, and then at a later time, the response file is sent back. Each file transfer consists of an FTP session where the file is first copied to the remote system, and then renamed to a separate directory on the remote system, where it can be accessed for processing.

complex image of process

The diagram below illustrates an exchange of files using the pull mechanism, where a data file is retrieved via FTP, and then at a later time, the response file is sent back as before. The file retrieval consists of an FTP session where the file is detected, copied from the remote system, and then deleted on the remote system.

complex image of process

2.2.7.1 Positive Acknowledgement (ACK Message)

A file must be checked for any of the conditions covered by response codes in the range 1-99. If all the checks pass then an ACK message must be sent.

Standard Receipt Acknowledgement Messages are not explicitly listed in the interface definitions which follow, except where they have been allocated an interface name in the URS - in this case, a section is included which contains only a reference back to this section, 2.2.7.

Receipt acknowledgement does not imply acceptance of the contents of the message.

2.2.7.2 Negative Acknowledgement (NACK Message)

This section applies to electronic data files sent both to and from the Central Systems.

In some cases it may be possible for an addressee to detect a failed message transmission. In this case a message may be returned to the sender with message role set to response.

Standard Negative Acknowledgement Messages are not explicitly listed in the interface definitions which follow.

When a system receives a NACK message, it should alert the operator of the system, informing him of the contents of the ADT record. The operator should read the Response Code field contained in the ADT record (defined in section 2.2.7) and take the appropriate action.

2.2.7.3 Response to response messages

On receipt of a response message, no response is sent.

2.2.7.4 Application Rejection and Acceptance

When a message has been received (and the receipt acknowledged as described above), the content of the message may be accepted or rejected during processing. The approach adopted to this is up to each individual application:

    • Rejection of a message may cause a message to be sent to the sender indicating the identifier of the message being rejected, and the reasons for rejection. The way in which rejections are dealt with will be described in the application specifications. In some cases, the Rejection message may be transmitted by a manual mechanism rather than as an electronic data file. Where a rejection message has been identified, it is listed as an interface in this document.

    • Acceptance of a message will not normally be signalled to the sender. In cases where this is required, a message is explicitly defined for the purpose.

2.2.8 Use of Sequence Numbers

The Central Systems expect each data file from a BSC Party in a certain role to have a sequence number for each Central System role in the file header which increments each time a file is sent. In the following processing rules, greater / less than comparisons will be implemented to cater for when a sequence number wraps round through 0. Note that sequence numbers start from 1.

If the received file has a sequence number less than the next expected, and the header is not identical to the file already received with that sequence number, the system generates an out-of-sequence response for the file.

If the received file has a sequence number greater than the next expected, the Central Systems will save the file, but will not process or acknowledge it until:

a) the missing file(s) arrive and the file becomes the next expected sequence and so is processed as normal (and an appropriate response sent according to the validation rules);

b) more than [n] (configurable) files have subsequently arrived all of which are flagged as out-of-sequence. The system generates an out-of-sequence response for the file;

c) more than [t] (configurable) minutes have elapsed since the file arrived. The system generates an out-of-sequence response for the file;

d) an operator manually sets the next expected sequence number to be greater than that of the file.

An out-of-sequence response is a response message with response code 3 and the expected sequence number in the Response Data field of the ADT record of the response message. It is up to the sender of the original file to correct the problem and send back a file with the correct sequence number.

The Central Systems will not process any subsequent files sent until a file with the expected sequence number is received. The sender will have to resend any such files after the sequence number problem has been corrected.

There is no automatic process by which the Central Systems will alter the value of the next expected sequence number which it holds (either up or down), apart from the normal increment when a file is successfully received. The only method by which a BSC Party or Agent can achieve a change in the value of the next expected sequence number held by a Central System will be by manual agreement.

The rules for updating the next expected sequence number in the case of a NACK being generated are as follows:

    • if a file is rejected because of problems with the HEADER the sequence number is not "used up" and so the next expected sequence number remains unchanged (NACK codes 1,2,3);

    • if a file is rejected because of problems with the BODY or TRAILER (record count, checksum), the sequence number is used up and the next expected sequence number is incremented (NACK codes 4,5,6,7).

Note that sequence number validation for the P0282, P0292 and P0328 flows sent to SVAA is slightly different. SVAA also looks for a separate Sequence Number for each From Role Code / From Participant ID / To Role Code / To Participant ID combination. It will reject a new file if it has a lower sequence number than one that has already been processed, but it will allow gaps in the sequence.

2.2.9 Time

All data items with data format datetime are in GMT.

Settlement Periods are integers defining a half hour period within a Settlement Day. These start at midnight local time, and are numbered sequentially from 1 to 46/48/50.

2.2.10 The CRA Encryption Key

In flow CRA-I012, the CRA system sends out an Encryption Key. How this is used is explained in [COMMS]. This flow is not sent electronically.

2.2.11 Valid Sets

This section defines the Valid Sets referred to in the repeating structure tables.

Note also that BSC Party Ids and BSC Party Agent Ids may contain only characters from this restricted set:

    • A-Z

    • 0-9

    • - (dash)

BM Unit Ids, GSP Ids, GSP Group Ids, Interconnector Ids, Joint BMU Unit Ids and Metering System Ids may contain only characters from this restricted set:

    • A-Z

    • 0-9

    • - (dash)

    • _ (underscore)

2.2.11.1 Action Code

One of the values:

‘Change’ (New or updated record)

‘No Action’ (Record unchanged)

‘Delete’ (record deleted)

Note: The Action Code field is used in CRA reports to indicate changes since the previous issue of the report, which could include the application of several registration requests. The Action Description field is a free format text field used in registration requests to allow the participant to identify the reason and nature of the change to the CRA operator.

2.2.11.2 Action Indicator

One of the values:

‘N’ (New)

‘U’ (Update)

‘C’ (Change of Registrant)

‘D’ (Delete)

2.2.11.3 Activity

One of the values:

‘A’ (Changing Authorisations)

‘B’ (Accept / Reject Data Estimation)

‘C’ (Site Witness of Meter Readings and on-site Meter Readings)

‘D’ (Work on Metering Systems)

‘E’ (Submitting SVA Entry Process Requests)

‘EA’ – Discontinued (Raise / Agree Standing Data Changes)

‘F’ (BM Units)

‘G’ (Metering System Registrations and MOA Appointment)

‘H’ (Metering System Technical Details and Proving Tests)

‘I’ – Discontinued (TA Site Visit Acceptance)

‘J’ (Party Registration / Changes)

‘K’ (Submit / Terminate ECVNAA or MVRNAA)

‘L’ (Submitting Aggregation Rules)

‘M’ (Amend Report Requirements)

‘N’ (Banking Details Registration / Changes)

‘O’ (Query / Dispute Process)

‘P’ (Submitting CVA Line Loss Factors)

‘Q’ (Registration & Deregistration of Trading Units)

‘R’ (Metering Dispensations applications)

‘S’ (Party Withdrawal)

‘T’ (Transfer of Metering Systems between SMRS and CMRS)

‘U’ (Party Agent Registration & Changes to Details)

‘V’ (Transmission of Reports to all Parties)

‘W’ (Submitting SVA Standing Data Changes)

‘X’ (Submitting SVA Line Loss Factors)

‘Y’ (Submitting MDD Change Reports)

‘Z’ (Manage ECVAA Web Service access)

‘ZA’ (Register LDSO TSO Boundary Point)

‘ZB’ (Signing the SAD and the Qualification Letter and delegating authority for the signing of other Qualification related documentation)

‘ZC’ (A delegated person acting as the signing authority for that company’s Annual Statement of Qualified Status process, re-Qualification Letter and any other documentation relating to Qualification)

2.2.11.4 Alarm Code

One of the values:

Interval Status Codes:

‘PO’ (Power outages)

‘SI’ (Short intervals)

‘LI’ (Long intervals)

‘CR’ (CRC checksum errors)

‘RA’ (RAM checksum errors)

‘RO’ (ROM checksum errors)

‘LA’ (Data missing)

‘CL’ (Clock errors)

‘BR’ (Recorder hardware resets)

‘WT’ (Watchdog timeouts)

‘TR’ (Time resets)

‘TM’ (Test mode)

‘LC’ (Load control)

Channel Status Codes:

‘AD’ (Added interval)

‘RE’ (Replaced data)

‘ES’ (Estimated data)

‘OV’ (Data overflow)

‘HL’ (Data out of limits)

‘XC’ (Excluded data)

‘PY’ (Parity error)

‘TY’ (Energy type change)

‘LR’ (Alarm error)

‘DI’ (Harmonic distortion)

2.2.11.5 AMSID Pair Differencing Indicator

One of the values:

‘T’ (AMSID Pair used for Differencing)

'F' (AMSID Pair used for Asset Metering)

2.2.11.6 Asset Metering Type

One of the values:

‘1’ (Metering of circuits with a rated capacity greater than 100MVA)

‘2’ (Metering of circuits with a rated capacity not exceeding 100MVA)

‘3’ (Metering of circuits with a rated capacity not exceeding 10MVA)

‘4’ (Metering of energy transfers with a Maximum Demand of up to (and including) 1MW)

‘5’ (Metering (embedded within another device) for energy transfers with a Maximum Demand of up to (and including) 100kW).

2.2.11.7 Baselining Indicator

One of the values:

    • S (Submitted)

    • I (Inactive)

    • B (Baselined)

2.2.11.8 Baselining Methodology

One of the values:

    • BL01

    • Null

2.2.11.9 Baselining Status

One of the values:

    • T (Baselined)

    • F (Non-Baselined)

2.2.11.10 BM Unit Type

One of the values:

‘T’ (directly connected to the Transmission network)

‘E’ (Embedded)

‘G’ (GSP Group, default BM unit for a supplier)

‘I’ (Interconnector User)

‘S’ (GSP Group, Specific BM unit identified by a supplier)

‘V’ Secondary BM Unit

2.2.11.11 Certification/Accreditation Status

One of the values:

‘1’ (applied for certification)

‘2’ (completed certification return)

‘3’ (certification report completed)

‘4’ (accredited)

‘5’ (accreditation removed)

2.2.11.12 Estimation method

One of the values:

‘A’ (Generation: Main meter data missing or incorrect in Primary and Secondary Outstations, Check meter data available – copied from Primary Check)

‘D’ (Demand: Main meter data missing or incorrect, Check meter data available – copied from Primary Check)

‘E’ (Demand: Main meter data missing or incorrect, Check meter not fully functional, but Main meter or Check meter register advance available – profiled using Meter Reading Estimation Tool)

‘I’ (Demand: Main meter data missing or incorrect, Check meter not fully functional, Main meter and Check meter register advance NOT available – profiled using Trend)

‘J’ (Generation: Main meter data missing, or incorrect, in Primary Outstation, Secondary Outstation main meter data available – substituted from Secondary Main)

‘K’ (Generation: Main and Check meter data missing or incorrect in Primary and Secondary Outstations, data estimated to zero awaiting confirmation of generation)

‘L’ (Demand; Primary Main meter data missing, or incorrect, Secondary Outstation Main meter data available – substituted from Secondary Main)

‘M’ (Demand: Main meter data missing or incorrect, data copied from suitable settlement period(s))

‘N’ (Validation Failure: Main meter data deemed correct)

‘U’ (Used party’s own reading)

‘X’ (Used different estimation method)

2.2.11.13 Event Day Type

One of the values:

    • B (Balancing Service)

    • O (Other)

    • D (Delete)

2.2.11.14 I/E Flag

One of the values:

‘I’ (Import)

‘E’ (Export)

2.2.11.15 L/S Flag

Either ‘L’ (Lead) or ‘S’ (Subsidiary). This is used in the Forward Contract Report (ECVAA-I022) to indicate whether the recipient of the report was the lead or subsidiary Party specified in a reported MVRNA Authorisation.

2.2.11.16 Main / Check Indicator

One of the values:

‘M’ (Main)

‘C’ (Check)

2.2.11.17 Measurement Class Id

One of the values:

‘C’ Half Hourly metered in 100kW Premises

‘E’ Half Hourly sub-100kW Non-Domestic Current Transformer

‘F’ Half Hourly sub-100kW domestic

‘G’ Half Hourly sub 100kW non-domestic whole-current

2.2.11.18 Measurement Quantity

One of the values:

‘AE’ (Active Export)

‘AI’ (Active Import)

‘RE’ (Reactive Export)

‘RI’ (Reactive Import)

2.2.11.19 Meter Reading Status

One of the values:

‘A’ (Valid)

‘B’ (Invalid)

‘C’ (Unavailable)

‘D’ (Substituted from Secondary Outstation Meter Data)

2.2.11.20 MSID Pair Indicator

‘T’ MSID Pair is not an Associated MSID Pair to an AMSID Pair in a Secondary BM Unit

‘A’ MSID Pair is an Associated MSID Pair to an AMSID Pair that will be used for the purposes of Asset Metering in a Secondary BM Unit

‘M’ MSID Pair is an Associated MSID Pair to an AMSID Pair that will be used for the purposes for Asset Differencing.

2.2.11.21 Multi-day Flag

One of the values:

‘M’ (Multi-day)

‘S’ (Single day)

Note that this flag is not used in any current report.

2.2.11.22 Organisation Type

One of the values:

‘AV’ (AMVLP)

‘BM’ (BMRA)

‘BC’ (BSCCo Ltd)

‘BP’ (BSC Party)

‘CD’ (CDCA)

‘CR’ (CRA)

‘DB’ (Distribution Business)

‘EC’ (ECVAA)

‘EN’ (ECVNA)

‘ER’ (Energy Regulator)

‘FA’ (FAA)

‘HA’ (Half Hourly Data Aggregator)

‘HC’ (Half Hourly Data Collector)

‘HP’ (Helpdesk)

‘IA’ (Interconnector Administrator)

‘IE’ (Interconnector Error Administrator)

‘MA’ (Meter Administration Agent)

‘MI’ (Market Index Data Provider)

‘MO’ (Half Hourly Meter Operator Agent))

‘MS’ (Supplier Meter Administration Agent)

‘MV’ (MVRNA)

‘NA’ (Non Half Hourly Data Aggregator)

‘NC’ (Non Half Hourly Data Collector)

‘NO’ (Non Half Hourly Meter Operator Agent)

‘PA’ (BSC Party Agent)

‘SA’ (SAA)

‘SG’ (BSC Service Agent)

‘SM’ (SMRA)

‘SO’ (NETSO)

‘SV’ (SVAA)

‘TA’ (TAA)

‘TG’ (Trading Party - Generator)

‘TI’ (Trading Party - Interconnector User)

'TL' (Transmission Loss Factor Agent)1

‘TN’ (Trading Party - Non-physical)

‘TS’ (Trading Party - Supplier)

‘VP’ (VLP)

2.2.11.23 Party Sequence

Either ‘1’ or ‘2’. This is used in the Forward Contract Report (ECVAA-I022) to indicate whether the recipient of the report was the first or second Party specified in a reported ECVNA Authorisation.

2.2.11.24 P/C Flag

One of the values:

‘P’ (Production)

‘C’ (Consumption)

2.2.11.25 P/C Status

One of the values:

‘P’ (Production)

‘C’ (Consumption)

2.2.11.26 Point Type

One of the values:

‘BG’ (Gensets connected to TS; boundary point)

‘BS’ (Station Transformer connected to TS; boundary point)

‘BD’ (Demand sites connected to TS; boundary point)

‘BI’ (Interconnector with other TS from TS; boundary point)

‘BE’ (Embedded > 50MW; boundary point)

‘BO’ (Other embedded; boundary point)

‘BT’ (Interconnector with other TS from DS; boundary point)

‘SG’ (Grid Supply Points; system connection point)

‘SD’ (Interconnector between Distribution Networks; system connection point)

2.2.11.27 Price Derivation Code

One of the values:

‘A’

(SBP = Main price; SSP = Reverse Price)

‘B’

(SSP Capped to SBP)

‘C’

(SSP Defaulted to SBP)

‘D’

(SBP & SSP Defaulted to Market Price)

‘E’

(SSP & SBP Defaulted to Zero)

‘F’

(SSP = Main Price; SBP = Reverse Price)

‘G’

(SBP Capped to SSP)

‘H’

(SBP Defaulted to SSP)

‘I’

(SBP & SSP Defaulted to Market Price)

‘J’

(SSP & SBP Defaulted to Zero)

‘K’

(SSP & SBP Defaulted to Market Price)

‘L’

(SSP & SBP Defaulted to Zero)

‘N’

(SSP Defaulted to Main price; SBP = SSP)

‘P’

(SBP Defaulted to Main price; SSP = SBP)

2.2.11.28 Registration Status

One of the values:

‘S’ (Successful Registration)

‘P’ (Registration Pending)

2.2.11.29 Registration Type

One of the values:

‘PY’ (BSC Party)

‘PA’ (BSC Party Agent)

‘SA’ (BSC Service Agent)

‘BM’ (BM Unit)

‘EI’ (Interconnector)

‘TU’ (Trading Unit)

‘BP’ (Boundary Point/System Connection Point)

‘MS’ (Metering System)

‘GG’ (GSP Group)

‘GS’ (GSP)

‘MI’ (Market Index Data Provider)

2.2.11.30 Run Type

One of the values:

‘II’ (Interim Initial)

‘SF’ (Initial Settlement)

‘R1’ (First Reconciliation)

‘R2’ (Second Reconciliation)

‘R3’ (Third Reconciliation)

‘RF’ (Final Reconciliation)

‘D’ (Dispute)

‘DF’ (Final Dispute)

(Multiple dispute runs for the same Settlement Date are distinguished using run number.)

2.2.12 Example File Formats

The first example is based on CDCA-I0041. A file defined like this in the spreadsheet:

C0411

F

CDCA-I041: Interconnector Aggregation Report

AIV

R

1-*

G

Interconnector Aggregation Report

N0125

D

1

integer(10)

Interconnector Id

N0200

D

1

date

Settlement Date

AIP

R

46-50

G

Aggregated Interconnector Volume - Period

N0201

D

1

integer(2)

Settlement Period

N0090

D

1

boolean

Estimate Indicator

N0062

D

1

date

Date of Aggregation

N0139

D

1

decimal(10,3)

Meter Volume

N0049

D

1

integer(2)

CDCA Run Number

N0121

D

1

char

I/E Flag

Import/Export Indicator

looks like this:

AAA|C0411001|D|20000204093055|CD|LOGICA|IA|FRANCE|516||

AIV|FRANCE|20000203|

AIP|1|F|20000204|501.2|1|E|

AIP|2|F|20000204|498.6|1|E|

..

AIP|48|F|20000204|468.9|1|E|

ZZZ|51|1067512|

Here are some more examples, based on the ECVN flow ECVAA-I004

An ECVN is defined as follows in the spreadsheet:

E0041

F

ECVAA-I004: ECVNs

EDN

R

1

G

ECVNs

N0080

D

1

text(10)

ECVNAA Id

N0297

D

1

text(10)

ECVNAA Key

M0310

D

1

text(10)

ECVN ECVNAA Id

N0077

D

1

text(10)

ECVN Reference Code

N0081

D

1

date

Effective From Date

N0083

D

O

date

Effective To Date

OTD2

R

0-1

G

Omitted Data No Change

N0483

D

1

boolean

No Change to Existing Data

CD9

R

0-*

G

Energy Contract Volumes

N0201

D

1

integer(2)

Settlement Period

N0085

D

1

decimal(10,3)

MWh

energy contract volume

This allows the following file formats:

1) An open-ended ECVN for a single period (effective-to date field omitted):

AAA|E0041001|D|20000204093055|EN|ECVNA1|EC|LOGICA|545546||

EDN|00195|3444343|00195|ECV65011|20000207||

CD9|23|1445233.323|

ZZZ|4|1313360725|

2) Termination of the previous ECVN after a month (no CDV records):

AAA|E0041001|D|20000204103055|EN|ECVNA1|EC|LOGICA|545676||

EDN|00195|3444343|00195|ECV65011|20000207|20000307|

ZZZ|3|51341339|

3) ECVN covering a single (long) day (multiple CDV records):

AAA|E0041001|D|20000204113055|EN|ECVNA1|EC|LOGICA|545873||

EDN|1095|0634343|1095|ECV65043|20000208|20000208|

CD9|1|100|

CD9|2|100|

CD9|3|110.323|

CD9|4|0.9|

CD9|5|0|

….

CD9|45|120|

CD9|46|0|

CD9|47|-120|

CD9|48|-120.5|

CD9|49|-121.0|

CD9|50|-121.0|

ZZZ|53|456423424|

3 External Interface Summary

This section provides convenient summary lists of the interfaces by system and by party or party agent type. 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.

3.1 Interfaces by BSC Agent

3.1.1 BMRA Interfaces

The BMRA publishes balancing mechanism information to BSC Parties, including:

    • Balancing Mechanism Data

    • System Related Data

    • Derived Data

    • Replacement Reserve Data

The BMRA interfaces to BSC Parties, Agents and Market Index Data Providers are listed below. Note that the numbering convention for the interfaces includes internal interfaces and interfaces with other Service Providers (including the NETSO) which are not listed here because they are included in the IDD Part 2.

Agent-id

Name

Dirn

User

Type

BMRA-I004

Publish Balancing Mechanism Data

to

BMR Service

User

BMRA

Publishing

Interface

BMRA-I005

Publish System Related Data

to

BMR Service

User

BMRA

Publishing

Interface

BMRA-I006

Publish Derived Data

to

BMR Service

User

BMRA

Publishing

Interface

BMRA-I019

Publish Credit Default Notices

to

BMR Service

User

BMRA

Publishing

Interface

BMRA-I010

Data Exception Report

to

MIDP

Electronic data file transfer

BMRA-I015

Receive Market Index Data

from

MIDP

Electronic data file transfer

BMRA-I028

Receive REMIT Data

from

BMR Service User,

NETSO

Electronic data file transfer

BMRA-I030

Publish REMIT Data

to

BMR Service

User

BMRA

Publishing

Interface

BMRA-I031

Publish Transparency Regulation Data

to

BMR Service

User,

ENTSO-E

BMRA

Publishing

Interface

BMRA-I035

Publish Trading Unit Data

to

BMR Service

User

BMRA

Publishing

Interface

BMRA-I037

Publish Replacement Reserve Data

to

BMR Service User

BMRA Publishing Interface

3.1.2 CDCA Interfaces

The CDCA interfaces to BSC Parties and Agents are listed below. Note that the numbering convention for the interfaces includes internal interfaces (which are not listed).

Agent-id

Name

Dirn

User

Type

CDCA-I001

Aggregation Rules

From

BSC Party

Manual

CDCA-I003

Meter Technical Data

From

MOA

Manual

CDCA-I003

Meter Technical Data

From

Registrant

Manual

CDCA-I004

Notify new Meter Protocol

To

MOA

Manual

CDCA-I005

Load New Meter Protocol

From

MOA

Manual

CDCA-I006

Meter Data for Proving Test

To

MOA

Manual

CDCA-I007

Proving Test Report/Exceptions

To

BSC Party

Manual

CDCA-I007

Proving Test Report/Exceptions

To

MOA

Manual

CDCA-I008

Obtain Metered Data from Metering Systems

From

Physical meters

Meter System Interface

CDCA-I009

Meter Period Data collected via site visit

From

Hand Held Device/Data Capture Device (MV-90)

Manual

CDCA-I010

Exception Report for missing and invalid meter period data

To

BSC Party

Electronic data file transfer

CDCA-I010

Exception Report for missing and invalid meter period data

To

MOA

Electronic data file transfer

CDCA-I011

Dial Readings from meter, for MAR

From

Hand Held Device/Data Capture Device (MV-90)

Manual

CDCA-I012

Report raw meter data

To

BSC Party

Electronic data file transfer

CDCA-I012

Report raw meter data

To

Distribution Business

Electronic data file transfer

CDCA-I013

Response to Estimated data

From

BSC Party

Manual

CDCA-I014

Estimated Data Report

To

BSC Party

Electronic data file transfer

CDCA-I014

Estimated Data Report

To

MOA

Electronic data file transfer

CDCA-I015

Reporting Metering Equipment Faults

From

MOA

Manual

CDCA-I017

Meter Reading Schedule for MAR

To

BSC Party

Manual

CDCA-I017

Meter Reading Schedule for MAR

To

MOA

Manual

CDCA-I018

MAR Reconciliation Report

To

BSC Party

Manual

CDCA-I018

MAR Reconciliation Report

To

Distribution Business

Manual

CDCA-I018

MAR Reconciliation Report

To

MOA

Manual

CDCA-I019

MAR Remedial Action Report

To

BSC Party

Manual

CDCA-I019

MAR Remedial Action Report

To

Distribution Business

Manual

CDCA-I019

MAR Remedial Action Report

To

MOA

Manual

CDCA-I021

Notification of Metering Equipment Work

From

MOA

Manual

CDCA-I025

Aggregation Rule Exceptions

To

BSC Party

Manual

CDCA-I026

Aggregated Meter Volume Exceptions

To

BSC Party

Manual

CDCA-I029

Aggregated GSP Group Take Volumes

To

BSC Party

Electronic data file transfer

CDCA-I029

Aggregated GSP Group Take Volumes

To

Distribution Business

Electronic data file transfer

CDCA-I030

Meter Period Data for Distribution Area

To

Distribution Business

Electronic data file transfer

CDCA-I037

Estimated Data Notification

To

BSC Party

Manual

CDCA-I037

Estimated Data Notification

To

MOA

Manual

CDCA-I038

Reporting Metering Equipment Faults

To

BSC Party

Manual

CDCA-I038

Reporting Metering Equipment Faults

To

MOA

Manual

CDCA-I041

Interconnector Aggregation Report

To

IA

Electronic data file transfer

CDCA-I042

BM Unit Aggregation Report

To

BSC Party

Electronic data file transfer

CDCA-I044

Meter System Proving Validation

From

MOA

Manual

CDCA-I045

Meter Data from routine work and Metering Faults

From

MOA/Data Capture Device (MV-90)

Manual

CDCA-I046

Site Visit Inspection Report

To

BSC Party

Manual

CDCA-I046

Site Visit Inspection Report

To

MOA

Manual

CDCA-I047

Correspondence Receipt Acknowledgement

To

BSC Party

Manual

CDCA-I048

Report of Aggregation Rules

To

BSC Party

Manual

CDCA-I051

Report Meter Technical Details

To

BSC Party,

Manual

CDCA-I051

Report Meter Technical Details

To

Distribution Business

Manual

CDCA-I051

Report Meter Technical Details

To

MOA

Manual

CDCA-I054

Meter Status Report

To

BSC Party,

Electronic data file transfer

CDCA-I054

Meter Status Report

To

Distribution Business

Electronic data file transfer

CDCA-I054

Meter Status Report

To

MOA,

Electronic data file transfer

CDCA-I055

`Transfer from SMRS information

From

BSC Party

Manual

CDCA-I057

Transfer to SMRS information

from

BSC Party

Manual

CDCA-I059

Initial Meter Reading Report

To

BSC Party

Manual

CDCA-I060

SVA Party Agent Details

From

SVA Registrant, CVA Registrant

Manual

CDCA-I067

Disconnected CVA BM Units

From

Distribution Businesses,

NETSO

Manual

3.1.3 CRA Interfaces

The CRA interfaces to BSC Parties and Agents are listed below. Note that the numbering convention for the interfaces includes internal interfaces (which are not listed).

Agent-id

Name

Dirn

User

Type

CRA-I001

BSC Party Registration Data

from

BSC Party

Manual

CRA-I002

Interconnector Admin Registration Data

from

BSC Party

Manual

CRA-I003

BSC Party Agent Registration Data

from

BSC Party Agent

Manual

CRA-I005

BM Unit Registration Data

from

BSC Party

Manual

CRA-I006

Trading Unit Registration

from

BSC Party

Manual

CRA-I007

Boundary Point and System Connection Point Registration Data

from

DB

manual

CRA-I008

Interconnector Registration

from

Distribution Business

Manual

CRA-I012

CRA Encryption Key

to

BSC Party

Manual

CRA-I012

CRA Encryption Key

to

BSC Party Agent

Manual

CRA-I012

CRA Encryption Key

to

MIDP

Manual

CRA-I014

Registration Report

to

BSC Party

Electronic data file transfer

CRA-I014

Registration Report

to

BSC Party Agent

Electronic data file transfer

CRA-I021

Registered Service List

to

BSC Party

Electronic data file transfer

CRA-I021

Registered Service List

to

Public

Manual

CRA-I024

Certification and Accreditation Status Report

to

BSC Party

Electronic data file transfer

CRA-I024

Certification and Accreditation Status Report

to

BSC Party Agents

Electronic data file transfer

CRA-I027

GSP Group and GSP Registration

from

Distribution Business

Manual

CRA-I031

Metering System Data

from

BSC Party

Manual

CRA-I034

Flexible Reporting Request

from

BSC Party

Manual

CRA-I034

Flexible Reporting Request

from

BSC Party Agent

Manual

CRA-I034

Flexible Reporting Request

from

BSC Service Agent

Manual

CRA-I034

Flexible Reporting Request

from

BSCCo Ltd

Manual

CRA-I034

Flexible Reporting Request

from

NETSO

Manual

CRA-I038

Transfer from SMRS Information

from

BSC Party

Manual

CRA-I040

Transfer to SMRS Information

from

BSC Party

Manual

CRA-I048

GC Breach or DC Breach Notification

to

BSC Party, BSCCo

Manual

CRA-I049

GC Breach or DC Breach Estimation Challenge

from

BSC Party

Manual

CRA-I051

Notification of Breach Challenge Data

to

BSC Party

Manual

3.1.4 ECVAA Interfaces

The ECVAA interfaces to BSC Parties and Agents are listed below. Note that the numbering convention for the interfaces includes internal interfaces (which are not listed).

Agent-id

Name

Dirn

User

Type

ECVAA-I002

ECVNAA Data

from

BSC Party

Manual

ECVAA-I002

ECVNAA Data

from

ECVNA

Manual

ECVAA-I003

MVRNAA Data

from

BSC Party

Manual

ECVAA-I003

MVRNAA Data

from

MVRNA

Manual

ECVAA-I004

ECVN

from

ECVNA

Electronic data file transfer

ECVAA-I005

MVRNs

from

MVRNA

Electronic data file transfer

ECVAA-I007

ECVNAA Feedback

to

BSC Party

Manual / Electronic data file transfer

ECVAA-I007

ECVNAA Feedback

to

ECVNA

Manual / Electronic data file transfer

ECVAA-I008

MVRNAA Feedback

to

BSC Party

Manual / Electronic data file transfer

ECVAA-I008

MVRNAA Feedback

to

MVRNA

Manual / Electronic data file transfer

ECVAA-I009

ECVN Feedback (Rejection)

to

BSC Party

Electronic data file transfer

ECVAA-I009

ECVN Feedback (Rejection)

to

ECVNA

Electronic data file transfer

ECVAA-I010

MVRN Feedback (Rejection)

to

BSC Party

Electronic data file transfer

ECVAA-I010

MVRN Feedback (Rejection)

to

MVRNA

Electronic data file transfer

ECVAA-I013

Authorisation Report

to

BSC Party

Electronic data file transfer

ECVAA-I013

Authorisation Report

to

ECVNA

Electronic data file transfer

ECVAA-I013

Authorisation Report

to

MVRNA

Electronic data file transfer

ECVAA-I014

Notification Report

to

BSC Party

Electronic data file transfer

ECVAA-I014

Notification Report

to

ECVNA

Electronic data file transfer

ECVAA-I014

Notification Report

to

MVRNA

Electronic data file transfer

ECVAA-I021

Credit Limit Warning

to

BSC Party

Manual

ECVAA-I022

Forward Contract Report

to

BSC Party

Electronic data file transfer

ECVAA-I024

Credit Cover Minimum Eligible Amount Request

from

BSC Party

Manual

ECVAA-I025

Credit Cover Minimum Eligible Amount Report

to

BSC Party

Manual

ECVAA-I028

ECVN Acceptance Feedback

to

BSC Party

Electronic data file transfer

ECVAA-I028

ECVN Acceptance Feedback

to

ECVNA

Electronic data file transfer

ECVAA-I029

MVRN Acceptance Feedback

to

BSC Party

Electronic data file transfer

ECVAA-I029

MVRN Acceptance Feedback

to

MVRNA

Electronic data file transfer

ECVAA-I035

Forward Contract Report Start Period Override

from

BSC Party

Manual

ECVAA-I037

Receive Volume Notification Nullification Request

from

BSC Party

Manual

ECVAA-I038

Issue Volume Notification Nullification Confirmation Report

to

BSC Party

Manual

ECVAA-I039

Issue Nullification Completion Report

to

BSC Party

Manual

ECVAA-I042

Banning/Unbanning Individual User Access to the ECVAA Web Service

from

BSC Party

ECVNA

MVRNA

Manual

ECVAA-I043

ECVAA Web Service – BSC Party View ECVNs

to

BSC Party

Electronic

ECVAA-I044

ECVAA Web Service – BSC Party View MVRNs

to

BSC Party

Electronic

ECVAA-I045

ECVAA Web Service –

ECVNA View ECVNs

to

ECVNA

Electronic

ECVAA-I046

ECVAA Web Service – MVRNA View MVRNs

to

MVRNA

Electronic

3.1.5 SAA Interfaces

The SAA interfaces to BSC Parties and Agents are listed below. Note that the numbering convention for the interfaces includes internal interfaces (which are not listed).

Agent-id

Name

Dirn

User

Type

SAA-I006

BM Unit Metered Volumes for Interconnector Users

from

IA

Electronic data file transfer

SAA-I012

Dispute Notification

from

BSC Party

Manual

SAA-I014

Settlement Reports

to

BSC Party

Electronic data file transfer

SAA-I016

Settlement Calendar

to

BSC Party

Manual

SAA-I016

Settlement Calendar

to

BSC Party Agent

Manual

SAA-I017

SAA Exception Reports

to

BSC Party (IA), MIDP

Electronic data file transfer

SAA-I018

Dispute Reports

to

BSC Party

Manual

SAA-I030

Receive Market Index Data

From

MIDP

Electronic data file transfer

3.1.6 SVAA Interfaces

The SVAA interfaces to BSC Parties are listed below. Note that these flows are specific to Wider Access, Metering Behind the Boundary Point, VLPs, AMVLPs and Secondary BM Units, and transferred using the electronic data transfer mechanisms described in [COMMS]. All other interfaces between SVAA and BSC Parties for Supplier Volume Allocation purposes use the SVA transfer mechanisms described in the SVA Data Catalogue and are not defined in the IDD documents and spreadsheets.

Agent-id

Name

Dirn

User

Type

P0282

Delivered Volume Notification

from

VLP, AMVLP

Electronic data file transfer

P0283

Rejection of Delivered Volume

to

VLP, AMVLP

Electronic data file transfer

P0284

Confirmation of Delivered Volume

to

VLP, AMVLP

Electronic data file transfer

P0285

Delivered Volume Exception Report

to

VLP, AMVLP

Electronic data file transfer

P0287

Metering System Half Hourly Volume Adjustments

to

Supplier

Electronic data file transfer

P0288

Secondary Half Hourly Consumption Volumes

to

VLP, AMVLP

Electronic data file transfer

P0297

Asset Registration

from

AMVLP

Self-Service Gateway or email

P0298

Rejection of Asset Registration

to

AMVLP

Self-Service Gateway or email

P0299

Confirmation of Asset Registration

to

AMVLP

Self-Service Gateway or email

P0300

Registration of AMVLP Agents

from

AMVLP

Self-Service Gateway or email

P0301

Rejection of AMVLP Agent Registration

to

AMVLP

Self-Service Gateway or email

P0302

Confirmation of AMVLP Agent Registration

to

AMVLP

Self-Service Gateway or email

P0303

Registration of Asset Meters

from

AMVLP

Self-Service Gateway or email

P0304

Rejection of Asset Meter Registration

to

AMVLP

Self-Service Gateway or email

P0305

Confirmation of Asset Meter Registration

to

AMVLP

Self-Service Gateway or email

P0306

AMSID Pair Allocation to a Secondary BM Unit

from

AMVLP

Self-Service Gateway or email

P0307

Confirmation of AMSID Pair Allocation to a Secondary BM Unit

to

AMVLP

Self-Service Gateway or email

P0308

Rejection of AMSID Pair Allocation to a Secondary BM Unit

to

AMVLP

Self-Service Gateway or email

P0309

Notification of use of AMSID Pair by another AMVLP

to

AMVLP

Self-Service Gateway or email

P0310

Missing Metering System Data

to

HHDA, HHDC, AMVLP

Electronic Data Transfer

P0311

Invalid Metering System Data

to

HHDA, HHDC, AMVLP

Electronic Data Transfer

P0320

Loss of AMSID Pair Allocation

to

AMVLP

Self-Service Gateway or email

3.2 Interfaces by Corresponding Party

3.2.1 BSC Party Interfaces

The interfaces to BSC Parties in general are listed below.

Dir’n

User

Agent-id

Name

Type

to

BSC Party

BMRA flows

Publish Balancing Mechanism Reports

Publishing

from

BSC Party

CDCA-I001

Aggregation Rules

Manual

to

BSC Party

CDCA-I007

Proving Test Report/Exceptions

Manual

to

BSC Party

CDCA-I010

Exception Report for missing and invalid meter period data

Electronic data file transfer

to

BSC Party

CDCA-I012

Report raw meter data

Electronic data file transfer

from

BSC Party

CDCA-I013

Response to Estimated data

Manual

to

BSC Party

CDCA-I014

Estimated Data Report

Electronic data file transfer

to

BSC Party

CDCA-I017

Meter Reading Schedule for MAR

Manual

to

BSC Party

CDCA-I018

MAR Reconciliation Report

Manual

to

BSC Party

CDCA-I019

MAR Remedial Action Report

Manual

to

BSC Party

CDCA-I025

Aggregation Rule Exceptions

Manual

to

BSC Party

CDCA-I026

Aggregated Meter Volume Exceptions

Manual

to

BSC Party

CDCA-I029

Aggregated GSP Group Take Volumes

Electronic data file transfer

to

BSC Party

CDCA-I037

Estimated Data Notification

Manual

to

BSC Party

CDCA-I038

Reporting Metering Equipment Faults

Manual

to

BSC Party

CDCA-I042

BM Unit Aggregation Report

Electronic data file transfer

to

BSC Party

CDCA-I046

Site Visit Inspection Report

Manual

to

BSC Party

CDCA-I047

Correspondence Receipt Acknowledgement

Manual

to

BSC Party

CDCA-I048

Report of Aggregation Rules

Manual

to

BSC Party

CDCA-I051

Report Meter Technical Details

Manual

to

BSC Party

CDCA-I054

Meter Status Report

Electronic data file transfer

to

BSC Party

CDCA-I059

Initial Meter Reading Report

Manual

From

SVA Registrant, CVA Registrant

CDCA-I060

SVA Party Agent Details

Manual

from

BSC Party

CRA-I001

BSC Party Registration Data

Manual

from

BSC Party

CRA-I002

Interconnector Admin Registration Data

Manual

from

BSC Party

CRA-I005

BM Unit Registration Data

Manual

from

BSC Party

CRA-I006

Trading Unit Registration

Manual

From

DB

CRA-I007

Boundary Point and System Connection Point Registration Data

manual

to

BSC Party

CRA-I012

CRA Encryption Key

Manual

to

BSC Party

CRA-I014

Registration Report

Electronic data file transfer

to

BSC Party

CRA-I021

Registered Service List

Electronic data file transfer

to

BSC Party

CRA-I024

Certification and Accreditation Status Report

Electronic data file transfer

from

BSC Party

CRA-I031

Metering System Data

Manual

to

BSC Party

CRA-I048

GC or DC Breach Notification

Manual

from

BSC Party

CRA-I049

GC Breach or DC Breach Challenge

Manual

to

BSC Party

CRA-I051

Notification of Breach Challenge Data

Manual

from

BSC Party

ECVAA-I002

ECVNAA Data

Manual

from

BSC Party

ECVAA-I003

MVRNAA Data

Manual

to

BSC Party

ECVAA-I007

ECVNAA Feedback

Manual / Electronic data file transfer

to

BSC Party

ECVAA-I008

MVRNAA Feedback

Manual / Electronic data file transfer

to

BSC Party

ECVAA-I009

ECVN Feedback

Electronic data file transfer

to

BSC Party

ECVAA-I010

MVRN Feedback

Electronic data file transfer

to

BSC Party

ECVAA-I013

Authorisation Report

Electronic data file transfer

to

BSC Party

ECVAA-I014

Notification Report

Electronic data file transfer

to

BSC Party

ECVAA-I021

Credit Limit Warning

Manual

to

BSC Party

ECVAA-I022

Forward Contract Report

Electronic data file transfer

from

BSC Party

ECVAA-I024

Credit Cover Minimum Eligible Amount Request

Manual

to

BSC Party

ECVAA-I025

Credit Cover Minimum Eligible Amount Report

Manual

to

BSC Party

ECVAA-I028

ECVN Acceptance Feedback

Electronic data file transfer

to

BSC Party

ECVAA-I029

MVRN Acceptance Feedback

Electronic data file transfer

from

BSC Party

ECVAA-I035

Forward Contract Report Start Period Override

Manual

from

BSC Party

ECVAA-I037

Receive Volume Notification Nullification Request

Manual

to

BSC Party

ECVAA-I038

Issue Volume Notification Nullification Confirmation Report

Manual

to

BSC Party

ECVAA-I039

Issue Nullification Completion Report

Manual

from

BSC Party

CRA-I034

Flexible Reporting Request

Manual

from

BSC Party

SAA-I012

Dispute Notification

Manual

to

BSC Party

SAA-I014

Settlement Reports

Electronic data file transfer

to

BSC Party

SAA-I016

Settlement Calendar

Manual

to

BSC Party

SAA-I017

SAA Exception Reports

Electronic data file transfer

to

BSC Party

SAA-I018

Dispute Reports

Manual

from

VLP, AMVLP

P0282

Delivered Volume Notification

Electronic data file transfer

to

VLP, AMVLP

P0283

Rejection of Delivered Volume

Electronic data file transfer

to

VLP, AMVLP

P0284

Confirmation of Delivered Volume

Electronic data file transfer

to

VLP, AMVLP

P0285

Delivered Volume Exception Report

Electronic data file transfer

to

BSC Party

P0287

Metering System Half Hourly Volume Adjustments

Electronic data file transfer

to

VLP, AMVLP

P0288

Secondary Half Hourly Consumption Volumes

Electronic data file transfer

from

AMVLP

P0297

Asset Registration

Self Service Gateway, Email

to

AMVLP

P0298

Rejection of Asset Registration

Self Service Gateway, Email

to

AMVLP

P0299

Confirmation of Asset Registration

Self Service Gateway, Email

from

AMVLP

P0300

AMVLP Agent Registration

Self Service Gateway, Email

to

AMVLP

P0301

Rejection of AMVLP Agent Registration

Self Service Gateway, Email

to

AMVLP

P0302

Confirmation of AMVLP Agent Registration

Self Service Gateway, Email

from

AMVLP

P0303

Registration of Asset Meters

Self Service Gateway, Email

to

AMVLP

P0304

Rejection of Asset Meter Registration

Self Service Gateway, Email

to

AMVLP

P0305

Confirmation of Asset Meter Registration

Self Service Gateway, Email

from

AMVLP

P0306

AMSID Pair Allocation to a Secondary BM Unit

Self Service Gateway, Email

to

AMVLP

P0307

Rejection of AMSID Pair Allocation to a Secondary BM Unit

Self Service Gateway, Email

to

AMVLP

P0308

Confirmation of AMSID Pair Allocation to a Secondary BM Unit

Self Service Gateway, Email

to

AMVLP

P0309

Notification of use of AMSID Pair by another AMVLP

Self Service Gateway, Email

to

HHDA,HHDC, AMVLP

P0310

Missing Metering System Data

Electronic Data Transfer

to

HHDA,HHDC, AMVLP

P0311

Invalid Metering System Data

Electronic Data Transfer

to

AMVLP

P320

Loss of AMSID Pair Allocation

Self Service Gateway, Email

Interfaces specific to distribution businesses are listed below:

Dir’n

User

Agent-id

Name

Type

to

Distribution Business

CDCA-I012

Report raw meter data

Electronic data file transfer

to

Distribution Business

CDCA-I018

MAR Reconciliation Report

Manual

to

Distribution Business

CDCA-I019

MAR Remedial Action Report

Manual

to

Distribution Business

CDCA-I029

Aggregated GSP Group Take Volumes

Electronic data file transfer

to

Distribution Business

CDCA-I030

Meter Period Data for Distribution Area

Electronic data file transfer

to

Distribution Business

CDCA-I051

Report Meter Technical Details

Manual

to

Distribution Business

CDCA-I054

Meter Status Report

Electronic data file transfer

from

Distribution Business

CDCA-I067

Disconnected BM Units

Manual

from

Distribution Business

CRA-I008

Interconnector Registration

Manual

from

Distribution Business

CRA-I027

GSP Group and GSP Registration

Manual

Interfaces specific to the Interconnector Administrator are listed below:

Dir’n

User

Agent-id

Name

Type

to

IA

CDCA-I041

Interconnector Aggregation Report

Electronic data file transfer

from

IA

SAA-I006

BM Unit Metered Volumes for Interconnector Users

Electronic data file transfer

to

IA

SAA-I017

SAA Exception Reports

Electronic data file transfer

For completeness, interfaces specific to meter reading are listed below:

Dir’n

User

Agent-id

Name

Type

from

Physical meters

CDCA-I008

Obtain Metered Data from Metering Systems

Meter System Interface

from

Hand Held Device/Data Capture Device (MV-90)

CDCA-I009

Meter Period Data collected via site visit

Manual

from

Hand Held Device/Data Capture Device (MV-90)

CDCA-I011

Dial Readings from meter, for MAR

Manual

from

MOA/Data Capture Device (MV-90)

CDCA-I045

Meter Data from routine work and Metering Faults

Manual

3.2.2 BSC Party Agent Interfaces

The interfaces specific to BSC Party Agents in general are listed below.

Dir’n

User

Agent-id

Name

Type

from

BSC Party Agent

CRA-I003

BSC Party Agent Registration Data

Manual

to

BSC Party Agent

CRA-I012

CRA Encryption Key

Manual

to

BSC Party Agent

CRA-I014

Registration Report

Electronic data file transfer

To

BSC Party Agent

CRA-I024

Certification and Accreditation Status Report

Electronic data file transfer

from

BSC Party Agent

CRA-I034

Flexible Reporting Request

Manual

to

BSC Party Agent

SAA-I016

Settlement Calendar

Manual

Interfaces specific to Meter Operator Agents are listed below:

Dir’n

User

Agent-id

Name

Type

to

MOA

TAA-I006

Notification of Metering Systems to be subject to site visits and request for site details

Manual

to

MOA

TAA-I024

Rectification Plan Response

Manual

from

MOA

CDCA-I003

Meter Technical Data

Manual

to

MOA

CDCA-I004

Notify new Meter Protocol

Manual

from

MOA

CDCA-I005

Load New Meter Protocol

Manual

to

MOA

CDCA-I006

Meter Data for Proving Test

Manual

to

MOA

CDCA-I007

Proving Test Report/Exceptions

Manual

to

MOA

CDCA-I010

Exception Report for missing and invalid meter period data

Electronic data file transfer

to

MOA

CDCA-I014

Estimated Data Report

Electronic data file transfer

from

MOA

CDCA-I015

Reporting Metering Equipment Faults

Manual

to

MOA

CDCA-I017

Meter Reading Schedule for MAR

Manual

to

MOA

CDCA-I018

MAR Reconciliation Report

Manual

to

MOA

CDCA-I019

MAR Remedial Action Report

Manual

from

MOA

CDCA-I021

Notification of Metering Equipment Work

Manual

to

MOA

CDCA-I037

Estimated Data Notification

Manual

to

MOA

CDCA-I038

Reporting Metering Equipment Faults

Manual

from

MOA

CDCA-I044

Meter System Proving Validation

Manual

from

MOA

CDCA-I045

Meter Data from routine work and Metering Faults

Manual

to

MOA

CDCA-I046

Site Visit Inspection Report

Manual

to

MOA

CDCA-I051

Report Meter Technical Details

Manual

to

MOA

CDCA-I054

Meter Status Report

Electronic data file transfer

Interfaces specific to Meter Volume Reallocation Notification Agents are listed below:

Dir’n

User

Agent-id

Name

Type

from

MVRNA

ECVAA-I003

MVRNAA Data

Manual

from

MVRNA

ECVAA-I005

MVRNs

Electronic data file transfer

to

MVRNA

ECVAA-I008

MVRNAA Feedback

Manual / Electronic data file transfer

to

MVRNA

ECVAA-I010

MVRN Feedback

Electronic data file transfer

to

MVRNA

ECVAA-I013

Authorisation Report

Electronic data file transfer

to

MVRNA

ECVAA-I014

Notification Report

Electronic data file transfer

to

MVRNA

ECVAA-I029

MVRN Acceptance Feedback

Electronic data file transfer

Interfaces specific to ECVN Agents are listed below:

Dir’n

User

Agent-id

Name

Type

from

ECVNA

ECVAA-I002

ECVNAA Data

Manual

from

ECVNA

ECVAA-I004

ECVN

Electronic data file transfer

to

ECVNA

ECVAA-I007

ECVNAA Feedback

Manual / Electronic data file transfer

to

ECVNA

ECVAA-I009

ECVN Feedback

Electronic data file transfer

to

ECVNA

ECVAA-I013

Authorisation Report

Electronic data file transfer

to

ECVNA

ECVAA-I014

Notification Report

Electronic data file transfer

to

ECVNA

ECVAA-I028

ECVN Acceptance Feedback

Electronic data file transfer

3.2.3 Market Index Data Provider Interfaces

The interfaces to Market Index Data Providers in general are listed below:

Dir’n

User

Agent-id

Name

Type

to

MIDP

CRA-I012

CRA Encryption Key

Manual

to

MIDP

BMRA-I010

Data Exception Report

Electronic data file transfer

from

MIDP

BMRA-I015

Market Index Data

Electronic data file transfer

to

MIDP

SAA-I017

SAA Exception Report

Electronic data file transfer

from

MIDP

SAA-I030

Market Index Data

Electronic data file transfer

4 BMRA External Inputs and Outputs

The outputs from BMRA which are presented to users are available in two formats - near real time broadcast of data using TIBCO messaging software and data download files available from the BMRA web site. The TIBCO type messages are available only on the High Grade Service, whereas the data files for download are obtainable from both the High Grade Service and the Low Grade Service.

The precise nature of the data available is specified in the BMRA URS. As noted in section 2.1.4, some of this data is provided via a publishing interface and it is not appropriate to include the physical structure of the screens data in this document.

Sections 4.1 to 4.3 comprise the logical definition of the data. Section 4.4 gives information on the contents of the raw data published in TIB message format from the BMRA High Grade Service, and section 4.5 gives information on the contents of the data files which are available for download from both the BMRA High Grade Service and the BMRA Low Grade Service web sites.

4.1 BMRA-I004: (output) Publish Balancing Mechanism Data

Interface ID:

BMRA-I004

User:

BMR Service User

Title:

Publish Balancing Mechanism Data

BSC reference:

BMRA SD 8.2, P71, P217

Mechanism:

BMRA Publishing Interface

Frequency:

Continuous (as made available from the NETSO)

Volumes:

Between 1000 - 5000 BM units. In each settlement period, at least 1 FPN data, 1 dynamic 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.

Up to 5000 Balancing Services Volume data items per day.

Interface Requirement:

The BMRA Service shall publish Balancing Mechanism data continuously, as it is received from the NETSO.

The Balancing Mechanism data consists of the following:

Gate Closure Data

Acceptance and Balancing Services Data

Declaration Data

The following breakdown summarises the details which will be available.

4.1.1 Gate Closure Data

Point FPN Data

BM Unit ID

Time From

Level From (MW)

Time To

Level To (MW)

Point Quiescent FPN Data

BM Unit ID

Time From

Level From (MW)

Time To

Level To (MW)

Bid-Offer Data:

BM Unit ID

Time From

Time To

Bid-Offer Pair Number

Level From (MW)

Level To (MW)

Offer Price (£/MWh)

Bid Price (£/MWh)

Maximum Export Limit:

BM Unit ID

Time From

Maximum Export Level From (MW)

Time To

Maximum Export Level To (MW)

Maximum Import Limit:

BM Unit ID

Time From

Maximum Import Level From (MW)

Time To

Maximum Import Level To (MW)

4.1.2 Acceptance and Balancing Services Data

For Settlement Dates prior to the P217 effective date:

Bid-Offer Acceptance Level Data:

BM Unit ID

Acceptance Time

Deemed Acceptance Flag

Time From

Level From (MW)

Time To

Level To (MW)

For Settlement Dates on or after the P217 effective date:

Bid-Offer Acceptance Level Flagged Data:

BM Unit ID

Acceptance Time

Deemed Acceptance Flag

SO-Flag

Time From

Level From (MW)

Time To

Level To (MW)

Acceptance STOR Provider Flag (for dates after the P217 effective date and before the P305 effective date the STOR Provider Flag will be reported as null)

Applicable Balancing Services Volume Data

BM Unit ID

Settlement Date

Settlement Period

Applicable Balancing Services Volume (MWh)

4.1.3 Declaration Data

Run Up Rates Export

BM Unit ID

Effective Time

Run-Up Rate 1 (MW / minute)

Run-Up Elbow 2 (MW)

Run-Up Rate 2 (MW / minute)

Run-Up Elbow 3 (MW)

Run-Up Rate 3 (MW / minute)

Run Up Rates Import

BM Unit ID

Effective Time

Run-Up Rate 1 (MW / minute)

Run-Up Elbow 2 (MW)

Run-Up Rate 2 (MW / minute)

Run-Up Elbow 3 (MW)

Run-Up Rate 3 (MW / minute)

Run Down Rates Export

BM Unit ID

Effective Time

Run-Down Rate 1 (MW / minute)

Run-Down Elbow 2 (MW)

Run-Down Rate 2 (MW / minute)

Run-Down Elbow 3 (MW)

Run-Down Rate 3 (MW / minute)

Run Down Rates Import

BM Unit ID

Effective Time

Run-Down Rate 1 (MW / minute)

Run-Down Elbow 2 (MW)

Run-Down Rate 2 (MW / minute)

Run-Down Elbow 3 (MW)

Run-Down Rate 3 (MW / minute)

Notice to Deviate from Zero

BM Unit ID

Effective Time

Notice To Deviate From Zero (Minutes)

Notice to Deliver Offers

BM Unit ID

Effective Time

Notice to Deliver Offers (Minutes)

Notice to Deliver Bids

BM Unit ID

Effective Time

Notice to Deliver Bids (Minutes)

Minimum Zero Time

BM Unit ID

Effective Time

Minimum Zero Time (Minutes)

Minimum Non-Zero Time

BM Unit ID

Effective Time

Minimum Non-Zero Time (Minutes)

Stable Export Limit

BM Unit ID

Effective Time

Stable Export Limit (MW)

Stable Import Limit

BM Unit ID

Effective Time

Stable Import Limit (MW)

Maximum Delivery Volume

BM Unit ID

Effective Time

Maximum Delivery Limit (MWh)

Maximum Delivery Period

BM Unit ID

Effective Time

Maximum Delivery Period (Minutes)

Physical Interface Details:

4.2 BMRA-I005: (output) Publish System Related Data

Interface ID:

BMRA-I005

User:

BMR Service User

Title:

Publish System Related Data

BSC reference:

BMRA SD 7.2, P8, P78, P172, P219, P220, P217, P243, P244, CP1333, CP1367, P399

Mechanism:

BMRA Publishing Interface

Frequency:

Continuous (as made available from the NETSO)

Volumes:

Various

Interface Requirement:

The BMRA Service shall publish System data continuously, as it is received from the NETSO.

The System Related data consists of the following:

Indicated Generation

Publishing Period Commencing Time

Start Time of ½ Hour Period

National/Boundary Identifier

Sum of PN Generation (MW)

Indicated Demand

Publishing Period Commencing Time

Start Time of ½ Hour Period

National/Boundary Identifier

Sum of PN Demand (MW)

National Demand Forecast3

Publishing Period Commencing Time

Start Time of ½ Hour Period

National/Boundary Identifier

Demand (MW)

Transmission System Demand Forecast4

Publishing Period Commencing Time

Start Time of ½ Hour Period

National/Boundary Identifier

Demand (MW)

Initial National Demand Out-Turn

Publishing Period Commencing Time

Start Time of ½ Hour Period

Demand (MW)

Initial Transmission System Demand Out-Turn

Publishing Period Commencing Time

Start Time of ½ Hour Period

Demand (MW)

National Demand Forecast Day, 2-14 Day

Publishing Period Commencing Time

Day of Forecast

Demand (MW)

Transmission System Demand Forecast Day, 2-14 Day

Publishing Period Commencing Time

Day of Forecast

Demand (MW)

National Demand Forecast Week, 2-52 Week

Publishing Period Commencing Time

Calendar Week Number

Demand (MW)

National Surplus Forecast, 2-156 Week

Publishing Period Commencing Time

Calendar Week Number

Surplus (MW)

Transmission System Demand Forecast Week, 2-52 Week

Publishing Period Commencing Time

Calendar Week Number

Demand (MW)

National Surplus Forecast, 2-14 Day

Publishing Period Commencing Time

Day of Forecast

Surplus (MW)

National Surplus Forecast, 2-52 Week

Publishing Period Commencing Time

Calendar Week Number

Surplus (MW)

Indicated Margin

Publishing Period Commencing Time

Start Time of ½ Hour Period

National/Boundary Identifier

Margin (MW)

Indicated Imbalance

Publishing Period Commencing Time

Start Time of ½ Hour Period

National/Boundary Identifier

Imbalance Value (MW)

National Output Usable, 2-14 Day

Publication Time

System Zone

Settlement Date

Output Usable (MW)

National Output Usable by Fuel Type, 2-14 Day

Fuel Type

Publication Time

System Zone

Settlement Date

Output Usable (MW)

National Output Usable by Fuel Type and BM Unit, 2-14 Day

BM Unit

Fuel Type

Publication Time

System Zone

Settlement Date

Output Usable (MW)

National Output Usable, 2-52 Week

Publication Time

System Zone

Calendar Week Number

Calendar Year

Output Usable (MW)

National Output Usable, 2-156 Week

Publication Time

System Zone

Calendar Week Number

Calendar Year

Output Usable (MW)

National Output Usable by Fuel Type, 2-52 Week

Fuel Type

Publication Time

System Zone

Calendar Week Number

Calendar Year

Output Usable (MW)

National Output Usable by Fuel Type, 2-156 Week

Fuel Type

Publication Time

System Zone

Calendar Week Number

Calendar Year

Output Usable (MW)

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

BM Unit

Fuel Type

Publication Time

System Zone

Calendar Week Number

Calendar Year

Output Usable (MW)

National Output Usable by Fuel Type and BM Unit, 2-156 Week

BM Unit

Fuel Type

Publication Time

System Zone

Calendar Week Number

Calendar Year

Output Usable (MW)

Generating Plant Demand Margin, 2-14 Days

Publication Time

Settlement Date

Generating Plant Demand Margin (MW)

Generating Plant Demand Margin, 2-52 Weeks

Publication Time

Calendar Week Number

Generating Plant Demand Margin (MW)

Generating Plant Demand Margin, 2-156 Weeks

Publication Time

Calendar Week Number

Generating Plant Demand Margin (MW)

System Zone Map

NGC-BSC BM Unit Mapping

System Warnings

SO-SO Prices

Balancing Services Adjustment Data:

Settlement Date

Settlement Period

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

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

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

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

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

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

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

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

Balancing Services Adjustment Action Data (for Settlement Dates after, and including the P217 effective date):

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 (T/F)

Balancing Services Adjustment Action STOR Flag (T/F) (for dates after the P217 effective date and before the P305 effective date the STOR Provider Flag will be reported as null)

Balancing Services Adjustment Action Data (for Settlement Dates after, and including the P399 effective date):

BSAD Party Id

BSAD Asset Id

Tendered Status

Service Type

Market Index Data:

Market Index Data Provider Identifier

Settlement Date

Settlement Period (1-50)

Market Index Price

Market Index Volume

Missing Market Index Data Messages

Temperature Data

Publishing Period Commencing Time

Settlement Date

Outturn Temperature (degrees Celsius)

Normal Reference Temperature (degrees Celsius)

High Reference Temperature (degrees Celsius)

Low Reference Temperature (degrees Celsius)

Wind Generation Forecast

Publishing Period Commencing Time

Start Time of ½ Hour Period

Generation Forecast (MW)

Total Registered Capacity (MW)

Instantaneous Generation By Fuel Type

Publishing Period Commencing Time

Start Time of ½ Hour Period

Spot Time

Fuel Type – ID representing one of:

CCGT

Oil Plant

OCGT

Coal

Nuclear

Power Park Module

Pumped Storage Plant

Non Pumped Storage Hydro Plant

External Interconnector Flows from France to England

External Interconnector Flows from Northern Ireland to Scotland

External Interconnector Flows from the Netherlands to England

External Interconnector Flows from Ireland to Wales

External Interconnector Flows from Belgium to England

Biomass

Other

Generation (MW)

Half Hourly Generation By Fuel Type

Publishing Period Commencing Time

Start Time of ½ Hour Period

Fuel Type – ID representing one of:

CCGT

Oil Plant

OCGT

Coal

Nuclear

Power Park Module

Pumped Storage Plant

Non Pumped Storage Hydro Plant

External Interconnector Flows from France to England

External Interconnector Flows from Northern Ireland to Scotland

External Interconnector Flows from the Netherlands to England

External Interconnector Flows from Ireland to Wales

External Interconnector Flows from Belgium to England

Biomass

Other

Generation (MW)

Daily Energy Volume Data

Publishing Period Commencing Time

Settlement Date

Outturn Volume (MWh)

Normal Volume (MWh)

High Volume (MWh)

Low Volume (MWh)

Realtime Transmission System Frequency Data

Publishing Period Commencing Time

Spot Time

Frequency (Hz)

Non-BM STOR Out-Turn

Publishing Period Commencing Time

Start Time of ½ Hour Period

Non-BM STOR Volume (MWh)

Loss of Load Probability and De-rated Margin

Settlement Date

Settlement Period

1200 Forecast – LoLP and DRM

8 hour forecast – LoLP and DRM

4 hour forecast – LoLP and DRM

2 hour forecast – LoLP and DRM

1 hour forecast – LoLP and DRM

Demand Control Instruction

Demand Control ID

Affected DSO

Instruction Sequence

Demand Control Event Flag

Time From

Time To

Demand Control Level

SO-Flag

STOR Availability Window

Season Year

Season Number

STOR Availability Dates

Weekday Start Time

Weekday End Time

Non-weekday Start Time

Non-weekday End Time

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.

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)

Net System Buy Price Volume Adjustment (SBVA)

Net Energy Sell Price Cost Adjustment (ESCA)

Net Energy Sell Price Volume Adjustment (ESVA)

Net System Sell Price Volume Adjustment (SSVA)

Physical Interface Details:

Within the Balancing Services Adjustment Action Data the SO-Flag will be set to ‘T’ where the associated Action has been flagged by the NETSO as potentially impacted by transmission constraints.

4.3 BMRA-I006: (output) Publish Derived Data

Interface ID:

BMRA-I006

User:

BMR Service User

Title:

Publish Derived Data

BSC reference:

BMRA SD 9.1, CP560, P18A, P78, P217, CP1333, P305, CP1517

Mechanism

BMRA Publishing Interface

Frequency:

Once, for each settlement period.

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 12 Bid-Offer Pairs per BM unit (estimated 1000) that receives bids and offers.

Interface Requirement:

The BMRA Service shall normally publish Derived data once for each settlement period, as soon as it is calculated. Where as a result of an outage, calculations have been based on incomplete or incorrect data from the NETSO, derived data may be republished.

The Derived data shall include:

Derived BM Unit Data (for all Settlement Dates)

Period Bid and Offer Acceptance Volumes (QABknij, QAOknij and CADL Flag)

Estimated Period Balancing Mechanism Bid and Offer Cashflows (CBnij and CO nij)

Derived BM Unit Data (for Settlement Dates prior to the P217 effective date)

Estimated Period BM Unit Total Accepted Bid and Offer Volume (QABnij and QAOnij)

Derived BM Unit Data (for Settlement Dates after, and including the P217 effective date)

Estimated Period BM Unit Original Accepted Bid and Offer Volume (QABnij and QAOnij)

Estimated Period BM Unit Tagged Accepted Bid and Offer Volume (QTABnij and QTAOnij)

Estimated Period BM Unit Repriced Accepted Bid and Offer Volume (QRABnij and QRAOnij)

Estimated Period BM Unit Originally-Priced Accepted Bid and Offer Volume (QOABnij and QOAOnij)

Derived System-wide Data (for Settlement Dates prior to the P217 effective date)

Estimated System Sell/Buy Prices (SBPj and SSPj)

Price Derivation Code (PDCj)

Indicative Net Imbalance Volume (NIVj)

Total Accepted Bid Volume and Total Accepted Offer Volume

Total Unpriced Accepted Bid Volume and Total Unpriced Accepted Offer Volume

Total Priced Accepted Bid Volume and Total Priced Accepted Offer Volume

Total Bid Volume and Total Offer Volume

Derived System-wide Data (for Settlement Dates after, and including the P217 effective date)

Estimated System Sell/Buy Prices (SBPj and SSPj)

Price Derivation Code (PDCj)

Indicative Net Imbalance Volume (NIVj)

Replacement Price (RPj)

Replacement Price Calculation Volume (RPVj)

Total Accepted Bid Volume

Total Accepted Offer Volume

Tagged Accepted Bid Volume

Tagged Accepted Offer Volume

Total Adjustment Buy Volume

Total Adjustment Sell Volume

Tagged Adjustment Buy Volume

Tagged Adjustment Sell Volume

Reserve Scarcity Price (for dates after the P217 effective date and before the P305 effective date the STOR Provider Flag will be reported as null)

The BMRA Service shall publish details of the Indicative System Price Stacks once for each Settlement Period. This will detail all items on both the Buy and Sell Stacks including a description of the ordering of items within each stack. Each stack item will have the following data reported against it:

Indicative System Price Stack Item (see below for further details)

Index

Component Identifier

Acceptance Number

Bid-Offer Pair Number

CADL Flag (T/F)

SO-Flag (T/F)

Acceptance STOR Provider Flag (T/F)

Repriced Indicator (T/F)

Bid-Offer Original Price (£/MWh)

Volume (MWh)

DMAT Adjusted Volume (MWh)

Arbitrage Adjusted Volume (MWh)

NIV Adjusted Volume (MWh)

PAR Adjusted Volume (MWh)

Reserve Scarcity Price (£/MWh)

Stack Item Original Price (£/MWh)

Final Price (£/MWh)

Transmission Loss Multiplier

TLM Adjusted Volume (MWh)

TLM Adjusted Cost (£)

Notes:

i. The Index will be a unique positive integer representing the item’s relative position in the stack. The first item in the stack has an index of 1. The reported ordering of items reflects the final order of the stack.

ii. The Component Identifier will hold any of the following: the associated BM Unit’s Identifier for Acceptance Volume stack items, the NETSO allocated ID for Disaggregated BSAD stack items or a unique ID that BSC Agent System derives for Demand Control Volume stack items, a specific identifier for Replacement Reserve actions and Volume of GB Need Met,.

iii. For Disaggregated BSAD and Demand Control Volume stack items no Acceptance Number and Bid Offer Pair Number values will be reported.

iv. The Repriced Indicator will reflect whether or not the stack item has been repriced.

v. The Price value will be the final derived price for the stack item as used to derive the TLM Adjusted Cost (i.e. it will be the Replacement Price where appropriate).

vi. The various “Adjusted Volume” values will be that part of the original volume that remains untagged after applying the associated process – e.g. PAR Adjusted Volume will be that volume which remains untagged after having carried out PAR Tagging.

vii. The Transmission Loss Multiplier will be the Transmission Loss Multiplier for the stack item’s associated BM Unit. For Disaggregated BSAD stack items, which have no associated BM Unit, this will always be a value of 1.

viii. TLM Adjusted Volume = PAR Adjusted Volume x TLM

ix. TLM Adjusted Cost = PAR Adjusted Volume x TLM x Price

x. The Bid-Offer Original Price is the Bid or Offer Price associated to the System Action based on its associated Bid-Offer Data or Balancing Services Adjustment Data sent by the NETSO. For STOR Actions, the Bid-Offer Original Price is sometimes referred to as the Utilisation Price.

xi. The Reserve Scarcity Price will be null for System Actions that are not STOR Actions.

xii. The Stack Item Original Price is a System Action’s initial price when first added to a price stack (i.e. the System Action Price (SAP)). Typically the Stack Item Original Price will be equal to the Bid-Offer Original Price except if it is a STOR Action in which case it will be the greater of the Bid-Offer Original Price and the Reserve Scarcity Price.

For a full derivation of the various data items, refer to the Indicative System Price Calculation in the BMRA URS.

Derived data will be published for each Settlement Period within <CADL> + 15 (parameterised) minutes from the end of the Settlement Period.

Physical Interface Details:

See SAA URS for Price Derivation Codes.

4.3.1 Indicative System Price Stack Data

For a full definition of what the variables mean and their derivation, refer to the Indicative System Price Calculation in the BMRA URS.

Each stack (Buy or Sell) will consist of a number of stack items listed in descending price order. Each stack item’s data consists of the following:

Data Item

Description

Index

A unique positive integer representing the item’s relative position in the stack. The first item in the stack has an index of 1. The reported ordering of items reflects the final order of the stack.

Component Identifier

For Acceptance Volume stack items the Component Identifier will represent the associated BM Unit’s Identifier. For Balancing Services Adjustment Action stack items Component Identifier will represent the NETSO allocated ID.

For Replacement Reserve actions, the Component Identifier will take the form ‘RRAUSB’ and ‘RRAUSS’ for the Buy and Sell stacks respectively.

For Volume of GB Need Met, the Component Identifier will take the form of ‘Q1’ and ‘Q2’ for each of the Quarter Hour periods within the Settlement Period.

For Demand Control Volume stack items a unique ID that the BSC Agent’s System derives.

Acceptance Number

Only reported for Acceptance Volume stack items (null for Balancing Services Adjustment Action and Demand Control Volume stack items.)

Bid-Offer Pair Number

Only reported for Acceptance Volume stack items (null for Balancing Services Adjustment Action and Demand Control Volume stack items.)

CADL Flag

A value of ‘T’ indicates where an Acceptance stack item is considered to be a Short Duration Acceptance.

SO-Flag

A value of ‘T’ indicates where the NETSO has flagged this stack item as potentially impacted by transmission constraints.

STOR Provider Flag

A value of ‘T’ indicates where the NETSO has flagged this stack item as relating to STOR Providers. This flag only indicates that the action MAY be a STOR Action.

Repriced Indicator

A value of ‘T’ indicates where a stack item has been repriced.

Bid-Offer Original Price

The Offer or Bid Price or BSAA Cost of the stack item (£/MWh) as reported in the original BOD or BSAD

Reserve Scarcity Price

For a particular Settlement Period, the price determined as the product of VOLL and LoLP.

Stack Item Original Price

The original price of the stack item (£/MWh), typically the Stack Item Original Price will be equal to the Bid-Offer Original Price except if it is a STOR Action in which case it will be the greater of the Bid-Offer Original Price and the Reserve Scarcity Price.

Volume

The initial volume of the stack item (MWh).

DMAT Adjusted Volume

The volume of the stack item which is not considered to be impacted by DMAT (MWh).

Arbitrage Adjusted Volume

The volume of the stack item which is not impacted by Arbitrage (MWh).

NIV Adjusted Volume

The volume of the stack item which is not NIV tagged (MWh).

PAR Adjusted Volume

The volume of the stack item which is not PAR tagged (MWh).

Final Price

The final price of the stack item (as used to determine the TLM Adjusted Cost) (£/MWh).

Transmission Loss Multiplier

The Transmission Loss Multiplier associated with the stack item. For Acceptance Volume stack items this will be determined from the related BM Unit.

For Balancing Services Adjustment Action stack items This will be considered to be 1.

TLM Adjusted Volume

PAR Adjusted Volume x TLM (MWh)

TLM Adjusted Cost

TLM Adjusted Volume x Price (£)

4.4 BMRA-I019: (output) Publish Credit Default Notices

Interface ID:

BMRA-I019

User:

BMR Service User

Title:

Publish Credit Default Notices

BSC reference:

CP703

Mechanism:

BMRA Publishing Interface

Frequency:

Ad-Hoc

Volumes:

Low.

Interface Requirement:

The BMRA Service shall publish Credit Default Notices, as they are received from the ECVAA.

Credit Default Notices shall include all data listed in BMRA-I018, i.e.:

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:

1. The Credit Default Level may be one of the following:

  • Level 1 Default;

  • Level 2 Default;

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

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

4. The Cleared Default Reason indicates why the Party cleared default as supplied by ECVAA.

Data shall be published according to the formats defined in BMRA URS Appendix C. For more information please refer to the BMRA System Specification and Design Specification.

Credit Default Notices will be published 3 (parameterised) times at 20 minute (parameterised) intervals after receipt.

Physical Interface Details:

4.5 BMRA-I010: (output) BMRA Data Exception Reports

Interface ID:

BMRA-I010

User:

NETSO, BSCCo Ltd, CRA, MIDP

Title:

BMRA Data Exception Reports

BSC reference:

BMRA SD 6.2, 7.3, 8.3, 8.4, P78

Mechanism:

Electronic data file transfer

Frequency:

Continuous

Volumes:

The BMRA Service shall issue Exception Reports to the NETSO, BSCCo Ltd, MIDPs or CRA if an input message fails validation, or if insufficient data has been received or, in the case of Adjustment Data, if a system parameter is set to indicate that an exception file is required. This covers errors in all message types.

The exception reports shall include:

Header of file being processed

File Type

Creation Time

From Role Code

From Participant Id

To Role Code

To Participant Id

Sequence Number

Test Data Flag

Header of NGC file being processed

NGC Filename

BMRA Data Exceptions

Exception Type

Exception Description

The header of file being processed may be a NETA File Header, a NGC File Header, or it may be omitted if, for example, the exception is that a file is missing.

The exception type may be one of the following:

  • Balancing Mechanism data incomplete

  • Input file validation error

Note that the file may contain one or many exception descriptions. A file may contain several problems, all of which will be reported in the one file. For example, exceptions on a FPN file may be reported against two different BMU identifiers which are not recognised by BMRA.

4.6 BMRA-I015: (input) Receive Market Index Data

Interface ID:

BMRA-I015

Source:

MIDP

Title:

Receive Market Index Data

BSC reference:

P78

Mechanism:

Automatic

Frequency:

Continuous for each Settlement Period

Volumes:

Up to 5 Providers, each sending data for each Settlement Period. Each Provider will submit either 1 file per period, or 1 file per day.

Interface Requirement:

The BMRA shall receive Market Index Data, from Market Index Data Providers, for each Settlement Period.

The flow shall include:

Market Index Data

Market Index Data Provider ID

Settlement Date

Settlement Period Market Index Data (1-50)

Settlement Period

Market Index Price

Market Index Volume

Traded Price (to be ignored)

Traded Volume (to be ignored)

Note:

1. Data submitted after the related period’s Indicative System Buy and Sell Price calculation has begun will be rejected.

2. Amendments to previously submitted data will be loaded and published by the BMRA as the most recent data, only if received before the related period’s calculation has begun.

3. No validation is carried out between BMRA and SAA to determine whether or not the same Market Index Data is submitted to both systems for each Settlement Period.

Physical Interface Details:

4.7 BMRA-I028: (input) Receive REMIT Data

Interface ID:

BMRA-I028

Source:

BMR Service User,

NETSO

Title:

Receive REMIT Data

BSC reference:

P291, P329

Mechanism:

Electronic data file transfer, XML

Frequency:

Continuous

Volumes:

Up to 3000 messages per day

Interface Requirement:

The BMRA shall receive REMIT message data from BMR Service Users (via the ELEXON Portal) and the NETSO. The data will be received in individual XML files and will include:

  • Message Type (Unavailabilities Of Electricity Facilities or Other Market Information)

  • Message ID

  • Message Heading

  • Participant ID

  • Participant Registration Code

  • Asset ID

  • Asset Type

  • Affected Unit and EIC code*

  • Affected Area

  • Bidding Zone*

  • Fuel Type*

  • Event Type*

  • Unavailability Type*

  • Event Status

  • Event Start and End dates

  • Duration uncertainty

  • Normal , Available and Unavailable Capacity*

  • Event cause

  • Outage Profile

    • Outage Profile Start

    • Outage Profile End

    • Outage Profile Capacity

* Only required forUnavailabilities Of Electricity Facilities’ Message Type

Physical Interface Details:

These files will be received in a format defined by an XML Schema (REMIT XSD version 2.0) established and maintained by the BMRA.

4.8 BMRA-I030: (output) Publish REMIT Data

Interface ID:

BMRA-I030

User:

BMR Service User,

Title:

Publish REMIT Data

BSC reference:

P291, P329

Mechanism:

BMRA Publishing Interface

Frequency:

Continuous upon receipt

Volumes:

Up to 3000 individual messages per day.

Interface Requirement:

The BMRA Service shall publish messages submitted under REMIT (Regulation on Energy Market Integrity and Transparency) as soon as they are received from BMR Service Users or the NETSO.

REMIT message data shall include:

  • Message Type (Unavailabilities Of Electricity Facilities or Other Market Information)

  • Message ID

  • Message Heading

  • Participant ID

  • Participant Registration Code

  • Asset ID

  • Asset Type

  • Affected Unit and EIC code*

  • Affected Area

  • Bidding Zone*

  • Fuel Type*

  • Event Type*

  • Unavailability Type*

  • Event Status

  • Event Start and End dates

  • Duration uncertainty

  • Normal, Available, and Unavailable Capacity*

  • Event cause

  • Outage Profile

    • Outage Profile Start

    • Outage Profile End

    • Outage Profile Capacity

* Only required forUnavailabilities Of Electricity Facilities’ Message Type

Physical Interface Details:

The detailed contents of this interface are defined by an XML Schema (REMIT XSD version 2.0) established and maintained by the BMRA.

4.9 BMRA-I031: (output) Publish Transparency Regulation Data

Interface ID:

BMRA-I031

Source:

BMR Service User,

ENTSO-E

Title:

Publish Transparency Regulation Data

BSC reference:

P295

Mechanism:

BMRA Publishing Interface;

Electronic data file transfer

Frequency:

Continuous upon receipt

Volumes:

Interface Requirement:

The BMRA Service shall publish data provided under the Transparency Regulations as soon as it has been received from the NETSO. Data shall be provided to BMR Service Users through the publishing interface and directly to ENTSO-E for further publication on the Electricity Market Fundamental Information Platform (EMFIP).

Transparency Regulation Data shall include information relating to the following categories:

  • Load

  • Outages

  • Transmission

  • Congestion Management

  • Generation

  • Balancing

Details of the individual articles reported are provided in Section 4.10.

Physical Interface Details:

The interface to ENTSO-e shall comprise an FTP connection to the Energy Communications Platform (ECP). The files will be published in XML and PDF formats defined by ENTSO-e. Data items in XML files will be defined in the relevant XML Schema 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.10 BMRA-I035: (output) Publish Trading Unit Data

Interface ID:

BMRA-I035

Source:

BMR Service User,

Title:

Publish Trading Unit Data

BSC reference:

P321

Mechanism:

BMRA Publishing Interface

Frequency:

Continuous upon receipt

Volumes:

Interface Requirement:

The BMRA Service shall publish Trading Unit Data as soon as it has been received from the SAA.

The following data items shall be included:

      • Trading Unit Name

      • Trading Unit Type

      • Settlement Date

      • Settlement Period

      • Settlement Run Type

      • Delivery Mode

      • Import Volume

      • Export Volume

      • Net Volume

This information will be available through a BMRS API, although it will not be available through the Tibco service.

Physical Interface Details:

4.11 BMRA-I037: (output) Publish Replacement Reserve Data

Interface ID:

BMRA-I037

Source:

BMR Service User,

Title:

Publish Replacement Reserve Data

BSC reference:

CP1517

Mechanism:

BMRA Publishing Interface

Frequency:

Continuous upon receipt and/or derivation

Volumes:

High

Interface Requirement:

The BMRA Service shall publish data relating to Replacement Reserve.

The information shall include:

  • RR Bid Data

  • RR Activation Data

  • RR GB Need Met

  • RR Interconnector Schedule

  • Indicative Accepted RR Bid and Offer Volumes, by Settlement Period and Quarter Hour Period

  • Indicative RR Cashflows, by Settlement Period and Quarter Hour Period

  • Aggregated RR information

Physical Interface Details:

4.12 BMRA TIBCO Message Publishing - Data Formats

The BMRA service publishes all data received from the NETSO and additional data derived by the BMRA Service via the use of TIBCO messaging software. TIB messages are broadcast over the High Grade Service WAN and will be received by any client software that explicitly listens for them. The messages are anticipated to be used in one or both of two ways: firstly to provide the Near Real Time update to data screens used by traders, and secondly to load market data into participant bespoke applications.

The material in this section defines the structure of all the TIB messages sent from the BMRA service which subscribing client software may receive.

The hardware and software specification for the TIBCO client software required to support the High Grade Service is given in [COMMS]. Guidelines for how to subscribe to published TIBCO messages are given in section 4.10.5

This section of the document describes the following information

    • message types

    • subject naming conventions

    • field definitions and formats

    • message definitions and formats

    • any special formatting or arrangement of data in messages

4.12.1 Message Types

The following table lists all of the message types sent from BMRA and specifies the External Interface Requirement met by each one.

External Interface Requirement

Data Type

Message Type

BMRA-I004

Final Physical Notification

FPN

BMRA-I004

Quiescent Physical Notification

QPN

BMRA-I004

Bid-Offer Pairs

BOD

BMRA-I004

Maximum Export Limit

MEL

BMRA-I004

Maximum Import Limit

MIL

BMRA-I004

Bid-Offer Acceptances

BOAL

BMRA-I004

Bid-Offer Acceptance Level Flagged

BOALF

BMRA-I004

BM Unit Applicable Balancing Services Volume

QAS

BMRA-I004

Run Up Rates Export

RURE

BMRA-I004

Run Up Rates Import

RURI

BMRA-I004

Run Down Rates Export

RDRE

BMRA-I004

Run Down Rates Import

RDRI

BMRA-I004

Notice to Deviate from Zero

NDZ

BMRA-I004

Notice to Deliver Offers

NTO

BMRA-I004

Notice to Deliver Bids

NTB

BMRA-I004

Minimum Zero Time

MZT

BMRA-I004

Minimum Non-Zero Time

MNZT

BMRA-I004

Stable Export Limit

SEL

BMRA-I004

Stable Import Limit

SIL

BMRA-I004

Maximum Delivery Volume

MDV

BMRA-I004

Maximum Delivery Period

MDP

BMRA-I005

Indicated Generation

INDGEN

BMRA-I005

Indicated Demand

INDDEM

BMRA-I005

National Demand Forecast

NDF

BMRA-I005

Transmission System Demand Forecast

TSDF

BMRA-I005

Initial National Demand Out-turn

INDO

BMRA-I005

Initial Transmission System Demand Out-Turn

ITSDO

BMRA-I005

Demand forecast. 2 -14 days ahead

NDFD

BMRA-I005

Demand forecast. 2 -52 weeks ahead

NDFW

BMRA-I005

Transmission System Demand Forecast, 2 -14 day

TSDFD

BMRA-I005

Transmission System Demand Forecast, 2 -52 week

TSDFW

BMRA-I005

Surplus forecast. 2 -14 days ahead

OCNMFD5

BMRA-I005

Surplus forecast. 2 -52 weeks ahead

OCNMFW6

BMRA-I005

Surplus forecast. 2-156 weeks ahead

OCNMF3Y

BMRA-I005

Indicated Margin

MELNGC

BMRA-I005

Indicated Imbalance

IMBALNGC

BMRA-I005

System Warnings

SYSWARN

BMRA-I005

SO-SO Prices

SOSO

BMRA-I005

Net Balancing Services Adjustment Data

NETBSAD

BMRA-I005

Balancing Services Adjustment Action Data

DISBSAD

BMRA-I005

System Message

SYSMSG

BMRA-I005

Market Index Data

MID

BMRA-I005

Temperature Data

TEMP

BMRA-I005

Wind Generation Forecast

WINDFOR

BMRA-I005

Instantaneous Generation by Fuel Type

FUELINST

BMRA-I005

Half-Hourly Generation by Fuel Type

FUELHH

BMRA-I005

Daily Energy Volume Data

INDOD

BMRA-I005

Realtime Transmission System Frequency Data

FREQ

BMRA-I005

Non-BM STOR Out-turn

NONBM

BMRA-I005

National Output Usable by Fuel Type, 2-14 days ahead

FOU2T14D

BMRA-I005

National Output Usable by BM Unit and Fuel Type, 2-14 days ahead

UOU2T14D

BMRA-I005

National Output Usable by Fuel Type, 2-52 weeks ahead

FOU2T52W

BMRA-I005

National Output Usable by BM Unit and Fuel Type, 2-52 weeks ahead

UOU2T52W

BMRA-I005

National Output Usable by Fuel Type, 2-156 weeks ahead

FOU2T3YW

BMRA-I005

National Output Usable by BM Unit and Fuel Type, 2-156 weeks ahead

UOU2T3YW

BMRA-I005

Generating Plant Demand Margin, 2-14 days ahead

OCNMFD2

BMRA-I005

Generating Plant Demand Margin, 2-52 weeks ahead

OCNMFW2

BMRA-I005

Generating Plant Demand Margin, 2-156 weeks ahead

OCNMF3Y2

BMRA-I005

Loss of Load Probability and De-rated Margin

LOLP

BMRA-I005

Demand Control Instructions

DCONTROL

BMRA-I006

Period B-O Acceptance Volumes

BOAV

BMRA-I006

Period Total B-O Acceptance Volume

PTAV

BMRA-I006

Disaggregated Period Total B-O Acceptance Volume

DISPTAV

BMRA-I006

Estimated period B-O cash flows

EBOCF

BMRA-I006

Net Estimated Buy/Sell Price and Total Accepted Bid/Offer Volumes

NETEBSP

BMRA-I006

Disaggregated Estimated Buy/Sell Price and Total Accepted Bid/Offer Volumes

DISEBSP

BMRA-I006

Total Bid Volume and Total Offer Volume

TBOD

BMRA-I006

Indicative System Price Stack

ISPSTACK

BMRA-I019

Credit Default Notices

CDN

BMRA-I030

REMIT Data

REMIT

BMRA-I031

Transparency Regulation Data

TRANSPARENCY

BMRA-I037

Replacement Reserve Data

RR

Data has been divided up into a granular level, i.e. publication of data on a record by record basis. This allows the programmatic interface to insert the data more efficiently into any bespoke applications that need to receive the data feed.

BMRA publishes data using the TIBCO subject-based addressing messaging system - data is broadcast across the WAN in messages, each associated with a unique subject name which describes the type of data within the message. Any client software will ‘subscribe’ to the data by subject name. Thus, although all data is available, each piece of client software will only accept and process the data it specifically subscribes to.

4.12.2 Message Subject Naming

Subject names are used not only to provide an insight into the kind of data contained within the message, but also to divide the data into logical segments. TIBCO subject names consist of a string of characters that is divided into elements by a dot(.), and so data is organised hierarchically by assigning a specific meaning to each element in a subject name.

4.12.2.1 Base subject name

All subject names published by the BMRA system will have the following prefix:-

BMRA

It is important to prefix all messages from the BMRA system with an ‘identity key’ to allow BMRA data to be distinguished from other TIBCO message data. By establishing a prefix for BMRA messages now, possible confusion or corruption of data may be avoided in the future.

4.12.2.2 Sub-division of data through Subject Names

Published data will further be divided by data type - that is that all BM related data will be grouped together under an extended prefix, all system related data will be grouped together and all dynamic data will be grouped together.

The following table lists the subject name prefixes that the different types of data will be grouped under:

Data Group

Subject name prefix

System related data

BMRA.SYSTEM

BM related data

BMRA.BM.<BM_UNIT>

Dynamic Data

BMRA.DYNAMIC.<BM_UNIT>

Party Related Data

BMRA.BP.<PARTICIPANT>

REMIT Data

REMIT.BMRS

Transparency Regulation Data

TRANSPARENCY.BMRS.<ARTICLE>

Replacement Reserve Data

BMRA.RR

Informational

BMRA.INFO

System Data will contain all data that applies at a national (or zonal) level, rather than at BM Unit level. This includes all forecasting data, system warnings, National Demand Out-turn and estimated Buy and Sell prices (derived).

BM related data will contain the principal data relating to the Balancing mechanism. This includes FPN, QPN, B-O pairs, Acceptances, Maximum Import and Export Limits, Acceptance Volumes (derived) and B-O Cash Flows (derived).

Dynamic data will contain all the dynamic data relating to a BM Unit.

Replacement Reserve data will contain data relating to RR auctions and activations. Some data is available per BM Unit.

Transparency Regulation data will contain data relating to the individual articles that comprise the Transparency Regulations, each of which may contain data for a range of time periods and BM Units.

REMIT data will contain information submitted by individual participants in compliance with the Regulation on Energy Market Integrity and Transparency. Each message will relate to a specific event, e.g. failure, outage or return to service of a particular asset identified by the participant.

Party related data will contain all published data related to a participant. At present, this will include only Credit Default notices.

Information data will contain subjects relating to the BMRS itself. Its initial use will be for test messages and heartbeats for the TIBCO messaging protocol. These should currently be ignored by participants but the message definitions are given here for completeness.

This sub-division of data by subject name has been done to ease subscription to data by grouping related data types together. This means that wildcards may be used to subscribe to a selection of subject names which may all be plotted on the same graph, or listed in the same table. For example, much of the BM data may be viewed on the same graph and much of the dynamic data may be listed in the same table.

4.12.3 Message Formats

The messages are published using TIBCO Rendezvous software, using a subject-based addressing system and self describing data. A standard TIBCO message is composed of a header which contains the subject name, and an optional reply subject name, following by a string of data fields. Each field contains a single element of data together with details describing the data for platform independence.

Messages are built from a list of defined field types which have been identified to describe all of the data published by BMRA. Each of these two character BMRA Field Types is described later in this section, and has associated with it a unique field name and data types. No message will be published by BMRA containing fields outside of this set.

Note that the message definitions in this document contain only the data fields created by BMRA. Additional fields added to messages by Rendezvous - such as header fields and data description elements - will also be present in the published messages, but these are not listed in the definitions given in this document. Details of the standard TIBCO header fields may be found in TIBCO Rendezvous documentation.

In addition, certain messages published via TIBCO will consist of an XML payload rather than the standard message structure as described above. In these cases, subscribers will need to refer to relevant XML Schemas in order to process the payload. See section 4.10.5 ‘Message Definitions for further details on the schemas in use.

4.12.4 Field Type Definitions

This section identifies and defines all of the fields which are used to compose the BMRA messages. Each field in a message is associated with a Field Name, TIB Data type and a valid set of values. The fields are described using the following format:-

Field Data Type :

The data the field represents.

Field Type :

The reference identity of the field type, as used in message definitions.

Field Name :

The field name used within the message to identify the field.

Description :

A brief description of the data the field represents.

TIB Data Type :

The data type used in the TIB wire format of the message. This is a data type defined in and used internally by the TIBCO Rendezvous software. They are platform and network independent.

C/Java Type :

The C and Java data types which correspond to the TIB data type. The TIBCO Rendezvous software will convert the incoming TIB data type into this data type when the API is used for bespoke applications. Due to the nature of the C data type “float”, it should be noted that where the data type “float” is given, it is the responsibility of the participant’s API software to perform rounding to the appropriate accuracy (see section 4.10.7 and its subsections for additional information).

Messages containing field :

The TIB message types which are broadcast by BMRA which contain the field.

Additional Information :

Any additional information - such as the units of the data and the valid set of values if appropriate (note that £ and £/MWh are always to 2 decimal places).

Field Type Index by Data Type

Data Type

Field Type

Acceptance Level Value

VA

Acceptance Number

NK

Acceptance Time

TA

Adjustment Cost

JC

Adjustment Identifier

AI

Adjustment Volume

JV

Amendment Flag

AM

Applicable Balancing Services Volume

SV

Arbitrage Adjusted Volume

AV

Affected LDSO

DS

Bid Cashflow

BC

Bid Price

BP

Bid Volume

BV

Bid/Offer Indicator

BO

Bid-Offer Level Value

VB

Bid-Offer Pair Number

NN

BMRS Informational Text

IN

BSAD Asset Id

AX

BSAD Defaulted

BD

Buy Price

PB

BSAD Party Id

PX

Buy Price Cost Adjustment

A4

Buy Price Price Adjustment

A6

Buy Price Volume Adjustment

A5

CADL Flag

CF

Calendar Year

CY

Calendar Week Number

WN

Cleared Default Settlement Date

CD

Cleared Default Settlement Period

CP

Component Identifier

CI

Contract Identification

IC

Credit Default Level

DL

Deemed Bid-Offer Flag

AD

Demand Control Event Flag

EV

Demand Control ID

ID

Demand Control Level

VO

Demand Margin

DM

Demand Value

VD

DMAT Adjusted Volume

DA

Effective From Time

TE

Entered Default Settlement Date

ED

Entered Default Settlement Period

EP

Energy Volume Daily High Reference

EH

Energy Volume Daily Low Reference

EL

Energy Volume Daily Normal Reference

EN

Energy Volume Outturn

EO

Export Level Value

VE

Fuel Type

FT

Fuel Type Generation

FG

GB Reference High Noon Temperature

TH

GB Noon Temperature Outturn

TO

GB Reference Low Noon Temperature

TL

GB Reference Normal Noon Temperature

TN

Generation Value

VG

Imbalance Value

VI

Import Level Value

VF

Indicative Net Imbalance Volume

NI

Instruction Sequence No

SQ

Margin/Surplus Value

VM

Market Index Data Provider ID

MI

Market Index Price

M1

Market Index Volume

M2

Maximum Delivery Period

DP

Maximum Delivery Volume

DV

Message Type

MT

Minimum non-Zero Time

MN

Minimum Zero Time

MZ

Net Energy Buy Price Cost Adjustment

A9

Net Energy Buy Price Volume Adjustment

A10

Net Energy Sell Price Cost Adjustment

A7

Net Energy Sell Price Volume Adjustment

A8

Net System Buy Price Volume Adjustment

A12

Net System Sell Price Volume Adjustment

A11

NIV Adjusted Volume

NV

Non-BM STOR Volume

NB

Notice to Deliver Bids

DB

Notice to Deliver Offers

DO

Notice to Deviate from Zero

DZ

Number of Records

NR

Number Of Spot Points

NP

Offer Cashflow

OC

Offer Price

OP

Offer Volume

OV

Output Usable

OU

PAR Adjusted Volume

PV

Period Originally-Priced BM Unit Bid Volume

P6

Period Originally-Priced BM Unit Offer Volume

P3

Period Repriced BM Unit Bid Volume

P5

Period Repriced BM Unit Offer Volume

P2

Period Tagged BM Unit Bid Volume

P4

Period Tagged BM Unit Offer Volume

P1

PN Level Value

VP

Price Derivation Code

PD

Publishing Time

TP

Replacement Price

RP

Replacement Price Calculation Volume

RV

Repriced Indicator

RI

Reserve Scarcity Price

RSP

RR Accepted Bid Volume

BI

RR Accepted Offer Volume

OF

RR Associated TSO

AT

RR Auction Period End

AE

RR Auction Period Start

AS

RR Bid Resolution

BR

RR Business Type

TY

RR Cashflow

CR

RR Divisible

DI

RR Exclusive Bid Id

EB

RR Flow Direction

FD

RR Instruction Flag

RN

RR Interconnector Identifier

II

RR Linking Bid Id

LB

RR Market Balance Area

BA

RR Maximum Quantity

QX

RR Multipart Bid Id

MB

RR Position

PO

RR Price

PR

RR Quantity

QI

RR Quarter Hour Period

QP

RR Schedule Flag

SC

RR Status

RS

Run Down Elbow 2

RB

Run Down Elbow 3

RC

Run Down Rate 1

R1

Run Down Rate 2

R2

Run Down Rate 3

R3

Run Up Elbow 2

UB

Run Up Elbow 3

UC

Run Up Rate 1

U1

Run Up Rate 2

U2

Run Up Rate 3

U3

Sell Price

PS

Sell Price Cost Adjustment

A1

Sell Price Price Adjustment

A3

Sell Price Volume Adjustment

A2

Sequence Number

SN

Service Type

SX

Settlement Date

SD

Settlement Period

SP

Short Acceptance Flag

SA

Spot Time

TS

Stable Export Limit

SE

Stable Import Limit

SI

Stack Item Final Price

FP

Stack Item Original Price

IP

Stack Item Volume

IV

STOR Provider Flag

PF

SO-Flag

SO

SO-SO Start Time

ST

SO-SO Trade Type

TT

System Frequency

SF

System Message Text

SM

System Total Priced Accepted Bid Volume

PC

System Total Priced Accepted Offer Volume

PP

System Total Unpriced Accepted Bid Volume

AC

System Total Unpriced Accepted Offer Volume

AP

System Warning Text

SW

Tagged Accepted Bid Volume

T2

Tagged Accepted Offer Volume

T1

Tagged Adjustment Buy Volume

J4

Tagged Adjustment Sell Volume

J3

Tendered Status

TX

Time From

TF

Time To

TI

TLM Adjusted Cost

TC

TLM Adjusted Volume

TV

Total Accepted Bid Volume

AB

Total Accepted Offer Volume

AO

Total Adjustment Buy Volume

J2

Total Adjustment Sell Volume

J1

Total Bid Volume

BT

Total Offer Volume

OT

Total Registered Capacity

TR

Total Volume of Activated Bids

BS

Total Volume of Offered Bids

OS

Total Volume of Unavailable Bids

US

Trade Direction

TD

Trade Price

PT

Trade Quantity

TQ

Transmission Loss Multiplier

TM

Bid-Offer Original Price

UP

Week Start Date

WD

Zone Indicator

ZI

4.12.4.2 Field Type Index

Field Type

Data Type

A1

Sell Price Cost Adjustment

A10

Net Energy Buy Price Volume Adjustment

A11

Net System Sell Price Volume Adjustment

A12

Net System Buy Price Volume Adjustment

A2

Sell Price Volume Adjustment

A3

Sell Price Price Adjustment

A4

Buy Price Cost Adjustment

A5

Buy Price Volume Adjustment

A6

Buy Price Price Adjustment

A7

Net Energy Sell Price Cost Adjustment

A8

Net Energy Sell Price Volume Adjustment

A9

Net Energy Buy Price Cost Adjustment

AB

Total Accepted Bid Volume

AC

System Total Unpriced Accepted Bid Volume

AD

Deemed Bid-Offer Flag

AE

RR Auction Period End

AI

Adjustment Identifier

AM

Amendment Flag

AO

Total Accepted Offer Volume

AP

System Total Unpriced Accepted Offer Volume

AS

RR Auction Period Start

AT

RR Associated TSO

AV

Arbitrage Adjusted Volume

AX

BSAD Asset Id

BA

RR Market Balance Area

BC

Bid Cashflow

BD

BSAD Defaulted

BI

RR Accepted Bid Volume

BO

Bid/Offer Indicator

BP

Bid Price

BR

RR Bid Resolution

BS

Total Volume of Activated Bids

BT

Total Bid Volume

BV

Bid Volume

CD

Cleared Default Settlement Date

CF

CADL Flag

CI

Component Identifier

CP

Cleared Default Settlement Period

CR

RR Cashflow

CY

Calendar Year

DA

DMAT Adjusted Volume

DB

Notice to Deliver Bids

DI

RR Divisible

DL

Credit Default Level

DM

Demand Margin

DO

Notice to Deliver Offers

DP

Maximum Delivery Period

DS

Affected LDSO

DV

Maximum Delivery Volume

DZ

Notice to Deviate from Zero

EB

RR Exclusive Bid Id

ED

Entered Default Settlement Date

EH

Energy Volume Daily High Reference

EL

Energy Volume Daily Low Reference

EN

Energy Volume Daily Normal Reference

EO

Energy Volume Outturn

EP

Entered Default Settlement Period

FD

RR Flow Direction

FG

Fuel Type Generation

FP

Stack Item Final Price

FT

Fuel Type

IC

Contract Identification

ID

Demand Control ID

II

RR Interconnector Identifier

IN

BMRS Informational Text

IP

Stack Item Original Price

IV

Stack Item Volume

J1

Total Adjustment Sell Volume

J2

Total Adjustment Buy Volume

J3

Tagged Adjustment Sell Volume

J4

Tagged Adjustment Buy Volume

JC

Adjustment Cost

JV

Adjustment Volume

LB

RR Linking Bid Id

M1

Market Index Price

M2

Market Index Volume

MB

RR Multipart Bid Id

MI

Market Index Data Provider ID

MN

Minimum non-Zero Time

MT

Message Type

MZ

Minimum Zero Time

NB

Non-BM STOR Volume

NI

Indicative Net Imbalance Volume

NK

Acceptance Number

NN

Bid-Offer Pair Number

NP

Number Of Spot Points

NR

Number of Records

NV

NIV Adjusted Volume

OC

Offer Cashflow

OF

RR Accepted Offer Volume

OP

Offer Price

OS

Total Volume of Offered Bids

OT

Total Offer Volume

OU

Output Usable

OV

Offer Volume

P1

Period Tagged BM Unit Offer Volume

P2

Period Repriced BM Unit Offer Volume

P3

Period Originally-Priced BM Unit Offer Volume

P4

Period Tagged BM Unit Bid Volume

P5

Period Repriced BM Unit Bid Volume

P6

Period Originally-Priced BM Unit Bid Volume

PB

Buy Price

PC

System Total Priced Accepted Bid Volume

PD

Price Derivation Code

PF

STOR Provider Flag

PI

Party Id

PO

RR Position

PP

System Total Priced Accepted Offer Volume

PR

RR Price

PS

Sell Price

PT

Trade Price

PV

PAR Adjusted Volume

PX

BSAD Party Id

QI

RR Quantity

QP

RR Quarter Hour Period

QX

RR Maximum Quantity

R1

Run Down Rate 1

R2

Run Down Rate 2

R3

Run Down Rate 3

RB

Run Down Elbow 2

RC

Run Down Elbow 3

RI

Repriced Indicator

RN

RR Instruction Flag

RP

Replacement Price

RS

RR Status

RSP

Reserve Scarcity Price

RV

Replacement Price Calculation Volume

SA

Short Acceptance Flag

SC

RR Schedule Flag

SD

Settlement Date

SE

Stable Export Limit

SF

System Frequency

SI

Stable Import Limit

SM

System Message Text

SN

Sequence Number

SO

SO-Flag

SP

Settlement Period

SQ

Instruction Sequence No

ST

SO-SO Start Time

SV

Applicable Balancing Services Volume

SW

System Warning Text

SX

Service Type

T1

Tagged Accepted Offer Volume

T2

Tagged Accepted Bid Volume

TA

Acceptance Time

TC

TLM Adjusted Cost

TD

Trade Direction

TE

Effective From Time

TF

Time From

TH

GB Reference High Noon Temperature

TI

Time To

TL

GB Reference Low Noon Temperature

TM

Transmission Loss Multiplier

TN

GB Reference Normal Noon Temperature

TO

GB Noon Temperature Outturn

TP

Publishing Time

TQ

Trade Quantity

TR

Total Registered Capacity

TS

Spot Time

TT

SO-SO Trade Type

TV

TLM Adjusted Volume

TY

RR Business Type

TX

Tendered Status

U1

Run Up Rate 1

U2

Run Up Rate 2

U3

Run Up Rate 3

UB

Run Up Elbow 2

UC

Run Up Elbow 3

UP

Bid-Offer Original Price

US

Total Volume of Unavailable Bids

VA

Acceptance Level Value

VB

Bid-Offer Level Value

VD

Demand Value

VE

Export Level Value

VF

Import Level Value

VG

Generation Value

VI

Imbalance Value

VM

Margin/Surplus Value

VO

Demand Control Level

VP

PN Level Value

WD

Week Start Date

WN

Calendar Week Number

ZI

Zone Indicator

4.12.4.3 Acceptance Level Value

Field Data Type :

Acceptance Level Value

Field Type :

VA

Field Name :

“VA”

Description :

Level of Acceptance. Used to describe either a ‘from level’ or a ‘to level’.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

BOAL, BOALF

Additional Information :

Value in MW.

Valid Values: -9999 to +9999.

4.12.4.4. Acceptance Number

Field Data Type :

Acceptance Number

Field Type :

NK

Field Name :

“NK”

Description :

The number of an individual acceptance.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

BOAL, BOAV, BOALF, ISPSTACK

Additional Information :

Valid values: 1 to 2147483647.

4.12.4.5 Acceptance Time

Field Data Type :

Acceptance Time

Field Type :

TA

Field Name :

“TA”

Description :

The time an acceptance was made.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

BOAL, BOALF

Additional Information :

4.12.4.6 Adjustment Cost

Field Data Type :

Adjustment Cost

Field Type :

JC

Field Name :

“JC”

Description :

The defined cost of the Adjustment item.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISBSAD

Additional Information :

Value in £. Can be NULL.

4.12.4.7 Adjustment Identifier

Field Data Type :

Adjustment Identifier

Field Type :

AI

Field Name :

“AI”

Description :

The unique identifier allocated to a single Balancing Services Adjustment Action item.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

DISBSAD

Additional Information :

Unique within each Settlement Period.

4.12.4.8 Adjustment Volume

Field Data Type :

Adjustment Volume

Field Type :

JV

Field Name :

“JV”

Description :

The defined volume of the Adjustment item.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISBSAD

Additional Information :

Value in MWh.

4.12.4.9 Applicable Balancing Services Volume

Field Data Type :

BM Unit Applicable Balancing Services Volume

Field Type :

SV

Field Name :

“SV”

Description :

Energy Volume associated with provision of balancing services

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

QAS

Additional Information :

Value in MWh

4.12.4.10 Arbitrage Adjusted Volume

Field Data Type :

Arbitrage Adjusted Volume

Field Type :

AV

Field Name :

“AV”

Description :

The volume remaining against a stack item after applying Arbitrage.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in MWh.

4.12.4.11 Bid Cashflow

Field Data Type :

Bid Cashflow

Field Type :

BC

Field Name :

“BC”

Description :

The period bid cashflow for a single Bid-Offer pair.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

EBOCF

Additional Information :

Value in £.

4.12.4.12 Bid Price

Field Data Type :

Bid Price

Field Type :

BP

Field Name :

“BP”

Description :

The bid price attached to a Bid-Offer pair for a given settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

BOD

Additional Information :

Value in £/MWh.

4.12.4.13 Bid Volume

Field Data Type :

Bid Volume

Field Type :

BV

Field Name :

“BV”

Description :

Bid volume accepted for a Bid-Offer pair.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

BOAV, PTAV

Additional Information :

Value in MWh

4.12.4.14 Bid/Offer Indicator

Field Data Type :

Bid/Offer Indicator

Field Type :

BO

Field Name :

“BO”

Description :

Indicates whether the associated stack item is from the Bid or Offer Stack.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

ISPSTACK

Additional Information :

Single character. Can be either “B” or “O”.

4.12.4.15 Bid-Offer Level Value

Field Data Type :

Bid-Offer Level Value

Field Type :

VB

Field Name :

“VB”

Description :

Level of Bid-Offer. Used to describe either a ‘from level’ or a ‘to level’.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

BOD

Additional Information :

Value in MW.

4.12.4.16 Bid-Offer Pair Number

Field Data Type :

Bid-Offer Pair Number

Field Type :

NN

Field Name :

“NN”

Description :

The number of a Bid-Offer pair.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

BOD, BOAV, PTAV, EBOCF, DISPTAV

Additional Information :

Valid values: -6 to 6.

4.12.4.17 BMRS Informational Text

Field Data Type :

BMRS Informational Text

Field Type :

IN

Field Name :

“IN”

Description :

General Informational message

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

MSG

Additional Information :

For future use. Should currently be ignored

4.12.4.18 BSAD Defaulted

Field Data Type :

BSAD Defaulted

Field Type :

BD

Field Name :

“BD”

Description :

Flag to indicate that the BSAD data shown is default values

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.19 Buy Price

Field Data Type :

Buy Price

Field Type :

PB

Field Name :

“PB”

Description :

The system buy price for a particular settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Value in £/MWh.

4.12.4.20 Buy Price Price Adjustment

Field Data Type :

Buy Price Price Adjustment

Field Type :

A6

Field Name :

“A6”

Description :

Adjustment applied to quotient in computation of Buy Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

NETBSAD, NETEBSP, DISEBSP

Additional Information :

Value in £/MWh.

4.12.4.21 CADL Flag

Field Data Type :

CADL Flag

Field Type :

CF

Field Name :

“CF”

Description :

A value of ‘T’ indicates where the associated stack item is considered to be a Short Duration Acceptance.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

ISPSTACK

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.22 Calendar Week Number

Field Data Type :

Calendar Week Number

Field Type :

WN

Field Name :

“WN”

Description :

The number of a week in the year.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

OCNMFW, NDFW, TSDFW, FOU2T52W, UOU2T52W, OCNMFW2, OCNMF3Y, FOU2T3YW, UOU2T3YW, OCNMF3Y2

Additional Information :

Valid values: 1 - 53.

The first week in the year with 4 days or more is Week number 1.

4.12.4.23 Calendar Year

Field Data Type :

Calendar Year

Field Type :

CY

Field Name :

“CY”

Description :

The year to which data in a message pertains.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

FOU2T52W, UOU2T52W, OCNMFW2, FOU2T3YW, UOU2T3YW, OCNMF3Y2

Additional Information :

4.12.4.24 Cleared Default Settlement Date

Field Data Type :

Cleared Default Settlement Date

Field Type :

CD

Field Name :

“CD”

Description :

The settlement date on which a party cleared credit default, at the level specified elsewhere in the message.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

CDN

Additional Information :

The time section of the DateTime is truncated to zero hours, zero minutes and zero seconds

4.12.4.25 Cleared Default Settlement Period

Field Data Type :

Cleared Default Settlement Period

Field Type :

CP

Field Name :

“CP”

Description :

The settlement Period on which a party cleared credit default, at the level specified elsewhere in the message.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

CDN

Additional Information :

Valid values : 1 – 50

4.12.4.26 Cleared Default Text

Field Data Type :

Cleared Default Text

Field Type :

CT

Field Name :

“CT”

Description :

Reason that a party has cleared credit default, at the level specified elsewhere in the message.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

CDN

Additional Information :

The cleared default text will be plain ascii text, in the majority of cases, be less than 128 bytes in length.

4.12.4.27 Component Identifier

Field Data Type :

Component Identifier

Field Type :

CI

Field Name :

“CI”

Description :

For Acceptance items this is the associated BM Unit’s Identifier. For Balancing Services Adjustment Action items this is the NETSO allocated, unique ID. For RR items this is an identifier that distinguishes the item as being related to Replacement Reserve.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

ISPSTACK

Additional Information :

4.12.4.28 Contract Identification

Field Data Type :

Contract Identification

Field Type :

IC

Field Name :

“IC”

Description :

A unique identifier for an offered SO-SO trade.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

SOSO

Additional Information :

4.12.4.29 Credit Default Level

Field Data Type :

Credit Default Level

Field Type :

DL

Field Name :

“DL”

Description :

The credit default level.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

CDN

Additional Information :

Valid values : 1, 2

4.12.4.30 Deemed Bid-Offer Flag

Field Data Type :

Deemed Bid-Offer Flag

Field Type :

AD

Field Name :

“AD”

Description :

Indicates whether Bid-Offer was made for an acceptance.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

BOAL, BOALF

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.31 Demand Margin

Field Data Type:

Demand Margin

Field Type :

DM

Field Name :

“DM”

Description :

A value of the demand margin from generating plants.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

OCNMFD2, OCNMFW2, OCNMF3Y2

Additional Information :

Value in MW.

Valid values: -99999 to +99999.

4.12.4.32 Demand Value

Field Data Type :

Demand Value

Field Type :

VD

Field Name :

“VD”

Description :

A value of demand.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NDFD, NDFW, INDDEM, INDO, NDF, TSDF, TSDFD, TSDFW, ITSDO

Additional Information :

Value in MW.

Valid values:

INDDEM: -99999 to 0

others: 0 to +99999.

4.12.4.33 DMAT Adjusted Volume

Field Data Type :

DMAT Adjusted Volume

Field Type :

DA

Field Name :

“DA”

Description :

The volume remaining against a stack item after applying DMAT.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in MWh.

4.12.4.34 Effective From Time

Field Data Type :

Effective From Time

Field Type :

TE

Field Name :

“TE”

Description :

The date and time that a value of dynamic data starts to be effective.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

RURE, RURI, RDRE, RDRI, NDZ, NTO, NTB, MZT, MNZT, SEL, SIL, MDV, MDP

Additional Information :

4.12.4.35 Energy Volume Daily High Reference

Field Data Type :

Energy Volume Daily High Reference

Field Type :

EH

Field Name :

“EH”

Description :

MWh.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

INDOD

Additional Information :

4.12.4.36 Energy Volume Daily Low Reference

Field Data Type :

Energy Volume Daily Low Reference

Field Type :

EL

Field Name :

“EL”

Description :

MWh.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

INDOD

Additional Information :

4.12.4.37 Energy Volume Daily Normal Reference

Field Data Type :

Energy Volume Daily Normal Reference

Field Type :

EN

Field Name :

“EN”

Description :

MWh.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

INDOD

Additional Information :

4.12.4.38 Energy Volume Daily Outturn

Field Data Type :

Energy Volume Daily Outturn

Field Type :

EO

Field Name :

“EO”

Description :

MWh.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

INDOD

Additional Information :

4.12.4.39 Entered Default Settlement Date

Field Data Type :

Entered Default Settlement Date

Field Type :

ED

Field Name :

“ED”

Description :

The settlement date on which a party entered credit default, at the level specified elsewhere in the message.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

CDN

Additional Information :

The time section of the DateTime is truncated to zero hours, zero minutes and zero seconds

4.12.4.40 Entered Default Settlement Period

Field Data Type :

Entered Default Settlement Period

Field Type :

EP

Field Name :

“EP”

Description :

The settlement Period on which a party entered credit default, at the level specified elsewhere in the message.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

CDN

Additional Information :

Valid values : 1 – 50

4.12.4.41 Export Level Value

Field Data Type :

Export Level Value

Field Type :

VE

Field Name :

“VE”

Description :

A level of export capability.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

MEL

Additional Information :

Value in MW.

4.12.4.42 Fuel Type

Field Data Type :

Fuel Type

Field Type :

FT

Field Name :

“FT”

Description :

The class of generation fuel type.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

FUELINST, FUELHH, FOU2T14D, FOU2T52W, FOU2T3YW, UOU2T14D, UOU2T52W, UOU2T3YW

Additional Information :

One of:

CCGT

OIL

COAL

NUCLEAR

WIND

PS

NPSHYD

OCGT

OTHER

INTFR

INTIRL

INTNED

Combined Cycle Gas Turbine

Oil Plant

Coal Plant

Nuclear Plant

Power Park Modules metered by the Transmission Operator

Pumped Storage Plant

Non Pumped Storage Hydro Plant

Open Cycle Gas Turbine Plant

Any other generation not covered by the other categories

External Interconnector flows with France (IFA)

External Interconnector flows with Ireland (Moyle)

External Interconnector flows with the Netherlands (BritNed)

INTEW

BIOMASS

INTNEM

External Interconnector flows with Ireland (East-West)

Biomass Plant

External Interconnector flows with Belgium (Nemo Link)

INTELEC

External Interconnector flows with France (ElecLink)

INTIFA2

External Interconnector flows with France (IFA2)

INTNSL

External Interconnector flows with Norway 2 (North Sea Link)

4.12.4.43 Fuel Type Generation

Field Data Type :

Fuel Type Generation

Field Type :

FG

Field Name :

“FG”

Description :

Fuel Type Generation (MW).

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

FUELINST, FUELHH

Additional Information :

Value in MW.

Valid values: -99999 to +99999.

4.12.4.44 GB Noon Temperature

Field Data Type :

GB Noon Temperature Outturn

Field Type :

TO

Field Name :

“TO”

Description :

Degree celsius Outturn temperature.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

TEMP

Additional Information :

Value in degrees Celsius.

Valid Values: -99.9 to 99.9

4.12.4.45 GB Reference Normal Noon Temperature

Field Data Type :

GB Reference Normal Temperature

Field Type :

TN

Field Name :

“TN”

Description :

Degree celsius temperature.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

TEMP

Additional Information :

Value in degrees Celsius.

Valid Values: -99.9 to 99.9

4.12.4.46 GB Reference High Noon Temperature

Field Data Type :

GB Reference High Noon Temperature

Field Type :

TH

Field Name :

“TH”

Description :

Degree celsius temperature.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

TEMP

Additional Information :

Value in degrees Celsius.

Valid Values: -99.9 to 99.9

4.12.4.47 GB Reference Low Noon Temperature

Field Data Type :

GB Reference Low Noon Temperature

Field Type :

TL

Field Name :

“TL”

Description :

Degree celsius temperature.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

TEMP

Additional Information :

Value in degrees Celsius.

Valid Values: -99.9 to 99.9

4.12.4.48 Generation Value

Field Data Type :

Generation Value

Field Type :

VG

Field Name :

“VG”

Description :

A value of Generation.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

INDGEN, WINDFOR

Additional Information :

Value in MW.

Valid values: 0 to +99999.

4.12.4.49 Imbalance Value

Field Data Type :

Imbalance Value

Field Type :

VI

Field Name :

“VI”

Description :

A value of Imbalance.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

IMBALNGC

Additional Information :

Value in MW.

Valid values: -99999 to +99999.

4.12.4.50 Import Level Value

Field Data Type :

Import Level Value

Field Type :

VF

Field Name :

“VF”

Description :

A level of Import capability.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

MIL

Additional Information :

Value in MW.

4.12.4.51 Indicative Net Imbalance Volume

Field Data Type :

Indicative Net Imbalance Volume

Field Type :

NI

Field Name :

“NI”

Description :

The Indicative Net Imbalance Volume

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

4.12.4.52 Margin/Surplus Value

Field Data Type :

Margin/Surplus Value

Field Type :

VM

Field Name :

“VM”

Description :

A value of margin or surplus.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

OCNMFD, OCNMFW, OCNMF3Y, MELNGC

Additional Information :

Value in MW.

Valid values: -99999 to +99999.

4.12.4.53 Market Index Data Provider ID

Field Data Type :

Market Index Data Provider ID

Field Type :

MI

Field Name :

“MI”

Description :

The Identifier of a Market Index Data Provider.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

MID

Additional Information :

The Identifier will be plain ascii text, in the majority of cases, be less than 4Kb in length.

4.12.4.54 Market Index Price

Field Data Type :

Market Index Price

Field Type :

M1

Field Name :

“M1”

Description :

Market Index Price.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

MID

Additional Information :

Value in £/MWh.

4.12.4.55 Market Index Volume

Field Data Type :

Market Index Volume

Field Type :

M2

Field Name :

“M2”

Description :

Market Index Volume.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

MID

Additional Information :

Value in MWh.

4.12.4.56 Maximum Delivery Period

Field Data Type :

Maximum Delivery Period

Field Type :

DP

Field Name :

“DP”

Description :

The minimum length of time in which the maximum delivery volume may be delivered.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

MDP

Additional Information :

Value in Minutes.

Valid Values: 1 to 239.

4.12.4.57 Maximum Delivery Volume

Field Data Type :

Maximum Delivery Volume

Field Type :

DV

Field Name :

“DV”

Description :

The maximum amount which may be delivered within the maximum delivery period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

MDV

Additional Information :

Value in MWh.

Valid Values: -99999 to +99999.

4.12.4.58 Message Type

Field Data Type :

Message type

Field Type :

MT

Field Name :

“MT”

Description :

A 6 character code that specifies a system message type

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

SYSMSG

Additional Information :

Valid Values: ‘MIDNP’, and such values that are allocated from time to time.

4.12.4.59 Minimum non-Zero Time

Field Data Type :

Minimum non-Zero Time

Field Type :

MN

Field Name :

“MN”

Description :

The minimum time a BM unit may operate at non-zero level as a result of accepted BM action.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

MNZT

Additional Information :

Value in Minutes.

Valid values: 0 to 999.

4.12.4.60 Minimum Zero Time

Field Data Type :

Minimum Zero Time

Field Type :

MZ

Field Name :

“MZ”

Description :

The minimum time a BM unit must operate at zero or import before returning to export.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

MZT

Additional Information :

Value in Minutes.

Valid values: 0 to 999.

4.12.4.61 Net Energy Buy Price Cost Adjustment

Field Data Type :

Net Energy Buy Price Cost Adjustment

Field Type :

A9

Field Name :

“A9”

Description :

Adjustment included in computation of Buy Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETBSAD, NETEBSP

Additional Information :

Value in £

4.12.4.62 Net Energy Buy Price Volume Adjustment

Field Data Type :

Net Energy Buy Price Volume Adjustment

Field Type :

A10

Field Name :

“A10”

Description :

Adjustment included in computation of Buy Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETBSAD, NETEBSP

Additional Information :

Value in MWh.

4.12.4.63 Net Energy Sell Price Cost Adjustment

Field Data Type :

Net Energy Sell Price Cost Adjustment

Field Type :

A7

Field Name :

“A7”

Description :

Adjustment included in computation of Sell Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETBSAD, NETEBSP

Additional Information :

Value in £

4.12.4.64 Net Energy Sell Price Volume Adjustment

Field Data Type :

Net Energy Sell Price Volume Adjustment

Field Type :

A8

Field Name :

“A8”

Description :

Adjustment included in computation of Sell Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETBSAD, NETEBSP

Additional Information :

Value in MWh.

4.12.4.65 Net System Buy Price Volume Adjustment

Field Data Type :

Net System Buy Price Volume Adjustment

Field Type :

A12

Field Name :

“A12”

Description :

Adjustment included in computation of Buy Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETBSAD, NETEBSP

Additional Information :

Value in MWh.

4.12.4.66 Net System Sell Price Volume Adjustment

Field Data Type :

Net System Sell Price Volume Adjustment

Field Type :

A11

Field Name :

“A11”

Description :

Adjustment included in computation of Sell Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETBSAD, NETEBSP

Additional Information :

Value in MWh.

4.12.4.67 NIV Adjusted Volume

Field Data Type :

NIV Adjusted Volume

Field Type :

NV

Field Name :

“NV”

Description :

The volume remaining against a stack item after applying NIV.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in MWh.

4.12.4.68 Non-BM STOR Volume

Field Data Type :

Non-BM STOR Volume

Field Type :

NB

Field Name :

“NB”

Description :

Non-BM STOR Instructed Volume (MWh).

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

NONBM

Additional Information :

Value in MWh.

Valid values: 0 to +99999.

4.12.4.69 Notice to Deliver Bids

Field Data Type :

Notice to Deliver Bids

Field Type :

DB

Field Name :

“DB”

Description :

Notification time for BM unit to deliver a bid

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

NTB

Additional Information :

Value in Minutes.

Valid values: 0 to 239.

4.12.4.70 Notice to Deliver Offers

Field Data Type :

Notice to Deliver Offers

Field Type :

DO

Field Name :

“DO”

Description :

Notification time for BM unit to deliver an offer.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

NTO

Additional Information :

Value in Minutes.

Valid values: 0 to 239.

4.12.4.71 Notice to Deviate from Zero

Field Data Type :

Notice to Deviate from Zero

Field Type :

DZ

Field Name :

“DZ”

Description :

Notification time required for BM unit to change operating level from zero.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

NDZ

Additional Information :

Value in Minutes.

Valid values: 0 to 999.

4.12.4.72 Number of Records

Field Data Type :

Number of Records

Field Type :

NR

Field Name :

“NR”

Description :

A number of records contained within the message. The context of this field will be described at the message definition level.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

OCNMFD, OCNMFW, OCNMF3Y, NDFD, NDFW, MELNGC, IMBALNGC, INDDEM, INDGEN, NDF, TSDF, TSDFD, TSDFW, WINDFOR, FOU2T14D, FOU2T52W, FOU2T3YW, UOU2T14D, UOU2T52W, UOU2T3YW, OCNMFD2, OCNMFW2, OCNMF3Y2

Additional Information :

4.12.4.73 Number of Spot Points

Field Data Type :

Number of Spot Points

Field Type :

NP

Field Name :

“NP”

Description :

The number of spot times and levels that are contained within a message.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

FPN, QPN, BOD, BOAL, MIL, MEL, BOALF

Additional Information :

See section on ‘Conversion of Effective From/To Time Data to Spot Time Data’.

4.12.4.74 Offer Cashflow

Field Data Type :

Offer Cashflow

Field Type :

OC

Field Name :

“OC”

Description :

The period offer cashflow for a single Bid-Offer pair.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

EBOCF

Additional Information :

Value in £.

4.12.4.75 Offer Price

Field Data Type :

Offer Price

Field Type :

OP

Field Name :

“OP”

Description :

The offer price attached to a Bid-Offer pair for a given settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

BOD

Additional Information :

Value in £/MWh.

4.12.4.76 Offer Volume

Field Data Type :

Offer Volume

Field Type :

OV

Field Name :

“OV”

Description :

The offer volume accepted for a Bid-Offer pair.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

BOAV, PTAV

Additional Information :

Value in MWh.

4.12.4.77 Output Usable

Field Data Type :

Output Usable

Field Type :

OU

Field Name :

“OU”

Description :

The volume of energy expected to be available over a given period (in the case of Interconnectors, this is the expected capacity).

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

FOU2T14D, FOU2T52W, FOU2T3YW, UOU2T14D, UOU2T52W, UOU2T3YW

Additional Information :

Value in MW.

Valid values: 0 to +99999

4.12.4.78 PAR Adjusted Volume

Field Data Type :

PAR Adjusted Volume

Field Type :

PV

Field Name :

“PV”

Description :

The volume remaining against a stack item after applying PAR.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in MWh.

4.12.4.79 Period Originally-Priced BM Unit Bid Volume

Field Data Type :

Period Originally-Priced BM Unit Bid Volume

Field Type :

P6

Field Name :

“P6”

Description :

The total originally-priced bid volume of the associated BM Unit for a given Bid-Offer pair and settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISPTAV

Additional Information :

Value in MWh.

4.12.4.80 Period Originally-Priced BM Unit Offer Volume

Field Data Type :

Period Originally-Priced BM Unit Offer Volume

Field Type :

P3

Field Name :

“P3”

Description :

The total originally-priced offer volume of the associated BM Unit for a given Bid-Offer pair and settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISPTAV

Additional Information :

Value in MWh.

4.12.4.81 Period Repriced BM Unit Bid Volume

Field Data Type :

Period Repriced BM Unit Bid Volume

Field Type :

P5

Field Name :

“P5”

Description :

The total repriced bid volume of the associated BM Unit for a given Bid-Offer pair and settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISPTAV

Additional Information :

Value in MWh.

4.12.4.82 Period Repriced BM Unit Offer Volume

Field Data Type :

Period Repriced BM Unit Offer Volume

Field Type :

P2

Field Name :

“P2”

Description :

The total repriced offer volume of the associated BM Unit for a given Bid-Offer pair and settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISPTAV

Additional Information :

Value in MWh.

4.12.4.83 Period Tagged BM Unit Bid Volume

Field Data Type :

Period Tagged BM Unit Bid Volume

Field Type :

P4

Field Name :

“P4”

Description :

The total tagged bid volume of the associated BM Unit for a given Bid-Offer pair and settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISPTAV

Additional Information :

Value in MWh.

4.12.4.84 Period Tagged BM Unit Offer Volume

Field Data Type :

Period Tagged BM Unit Offer Volume

Field Type :

P1

Field Name :

“P1”

Description :

The total tagged offer volume of the associated BM Unit for a given Bid-Offer pair and settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISPTAV

Additional Information :

Value in MWh.

4.12.4.85 PN Level Value

Field Data Type :

PN Level Value

Field Type :

VP

Field Name :

“VP”

Description :

Level of Physical Notice. Used to describe either a ‘from level’ or a ‘to level’ of Final or Quiescent PN.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

FPN, QPN

Additional Information :

Value in MW.

4.12.4.86 Price Derivation Code

Field Data Type :

Price Derivation Code

Field Type :

PD

Field Name :

“PD”

Description :

A 2 character code that describes how the SBP and SSP were derived

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Valid Values: are defined in BMRA-I006

4.12.4.87 Publishing Time

Field Data Type :

Publishing Time

Field Type :

TP

Field Name :

“TP”

Description :

The time a message or a particular field was originally published. The context of this field will be described at the message definition level.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

OCNMFD, OCNMFW, OCNMF3Y, NDFD, NDFW, MELNGC, IMBALNGC, INDDEM, INDGEN, SYSWARN, INDO, MSG, NDF, TSDF, TSDFD, TSDFW, ITSDO, TEMP, FUELINST, FUELHH, WINDFOR, NONBM, INDOD, FOU2T14D, FOU2T52W, FOU2T3YW, UOU2T14D, UOU2T52W, UOU2T3YW, OCNMFD2, OCNMFW2, OCNMF3Y2

Additional Information :

4.12.4.88 Replacement Price

Field Data Type :

Replacement Price

Field Type :

RP

Field Name :

“RP”

Description :

The Replacement Price used for a given settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in £/MWh.

4.12.4.89 Replacement Price Calculation Volume

Field Data Type :

Replacement Price Calculation Volume

Field Type :

RV

Field Name :

“RV”

Description :

The derived Replacement Price Calculation Volume for a given Settlement Period (as defined in the Indicative System Price Calculation function in the BMRA URS).

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in MWh.

4.12.4.90 Repriced Indicator

Field Data Type :

Repriced Indicator

Field Type :

RI

Field Name :

“RI”

Description :

A value of ‘T’ indicates where the associated stack item has been repriced.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

ISPSTACK

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.91 Run Down Elbow 2

Field Data Type :

Run Down Elbow 2

Field Type :

RB

Field Name :

“RB”

Description :

The point at which run down rate 2 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.92 Run Down Elbow 3

Field Data Type :

Run Down Elbow 3

Field name :

RC

Field Name :

“RC”

Description :

The point at which run down rate 3 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.93 Run Down Elbow 4

Field Data Type :

Run Down Elbow 4

Field Type :

RD

Field Name :

“RD”

Description :

The point at which run down rate 4 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.94 Run Down Elbow 5

Field Data Type :

Run Down Elbow 5

Field Type :

RE

Field Name :

“RE”

Description :

The point at which run down rate 5 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.95 Run Down Elbow 6

Field Data Type :

Run Down Elbow 6

Field Type :

RF

Field Name :

“RF”

Description :

The point at which run down rate 6 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.96 Run Down Elbow 7

Field Data Type :

Run Down Elbow 7

Field Type :

RG

Field Name :

“RG”

Description :

The point at which run down rate 7 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.97 Run Down Elbow 8

Field Data Type :

Run Down Elbow 8

Field Type :

RH

Field Name :

“RH”

Description :

The point at which run down rate 8 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.98 Run Down Elbow 9

Field Data Type :

Run Down Elbow 9

Field Type :

RJ

Field Name :

“RJ”

Description :

The point at which run down rate 9 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.99 Run Down Elbow 10

Field Data Type :

Run Down Elbow 10

Field Type :

RK

Field Name :

“RK”

Description :

The point at which run down rate 10 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RDRE, RDRI

Additional Information :

Value in whole MW.

4.12.4.100 Run Down Rate 1

Field Data Type :

Run Down Rate 1

Field Name :

R1

Field Name :

“R1”

Description :

Decrease in active power consumption between zero and run down elbow 2.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

RDRE, RDRI

Additional Information :

Value in MW/Minute.

Valid values: 0.2 to 999.0.

4.12.4.101 Run Down Rate 2

Field Data Type :

Run Down Rate 2

Field Name :

R2

Field Name :

“R2”

Description :

Decrease in active power consumption between run down elbows 2 and 3.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

RDRE, RDRI

Additional Information :

Value in MW/Minute.

Valid values: 0.2 to 999.0 or 0 (representing a null value).

4.12.4.102 Run Down Rate 3

Field Data Type :

Run Down Rate 3

Field Name :

R3

Field Name :

“R3”

Description :

Decrease in active power consumption after run down elbow 3.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

RDRE, RDRI

Additional Information :

Value in MW/Minute.

Valid values: 0.2 to 999.0 or 0 (representing a null value).

4.12.4.103 Run Up Elbow 2

Field Data Type :

Run Up Elbow 2

Field Type :

UB

Field Name :

“UB”

Description :

The point at which run up rate 2 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RURE, RURI

Additional Information :

Value in whole MW.

4.12.4.104 Run Up Elbow 3

Field Data Type :

Run Up Elbow 3

Field Type :

UC

Field Name :

“UC”

Description :

The point at which run up rate 3 applies.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RURE, RURI

Additional Information :

Value in whole MW.

4.12.4.105 Run Up Rate 1

Field Data Type :

Run Up Rate 1

Field Type :

U1

Field Name :

“U1”

Description :

Increase in active power production between zero and run up elbow 2.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

RURE, RURI

Additional Information :

Value in MW/Minute.

Valid values: 0.2 to 999.0.

4.12.4.106 Run Up Rate 2

Field Data Type :

Run Up Rate 2

Field Type :

U2

Field Name :

“U2”

Description :

Increase in active power production between run up elbows 2 and 3.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

RURE, RURI

Additional Information :

Value in MW/Minute.

Valid values: 0.2 to 999.0 or 0 (representing a null value).

4.12.4.107 Run Up Rate 3

Field Data Type :

Run Up Rate 3

Field Type :

U3

Field Name :

“U3”

Description :

Increase in active power production after run up elbow 3.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

RURE, RURI

Additional Information :

Value in MW/Minute.

Valid values: 0.2 to 999.0 or 0 (representing a null value).

4.12.4.108 Sell Price

Field Data Type :

Sell Price

Field Type :

PS

Field Name :

“PS”

Description :

The system sell price for a particular settlement period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Value in £/MWh.

4.12.4.109 Sell Price Price Adjustment

Field Data Type :

Sell Price Price Adjustment

Field Type :

A3

Field Name :

“A3”

Description :

Adjustment applied to quotient in computation of Sell Price

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

NETBSAD, NETEBSP, DISEBSP

Additional Information :

Value in £/MWh.

4.12.4.110 Sequence Number

Field Data Type :

Sequence Number

Field Type :

SN

Field Name :

“SN”

Description :

The stack item’s Index number, representing the relative position of the associated stack item within its related stack. A value of 1 represents the first item in a stack.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

ISPSTACK

Additional Information :

A positive integer greater than zero.

4.12.4.111 Settlement Date

Field Data Type :

Settlement Date

Field Type :

SD

Field Name :

“SD”

Description :

The settlement date.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

OCNMFD, NDFD, MELNGC, IMBALNGC, INDDEM, INDGEN, INDO, FPN, QPN, BOD, MIL, MEL, BOAV, PTAV, EBOCF, NETEBSP, TBOD, NDF, TSDF, TSDFD, ITSDO, FUELINST, FUELHH, WINDFOR, NONBM, INDOD, DISEBSP, NETBSAD, DISBSAD, DISPTAV, ISPSTACK, OCNMFD2, FOU2T14D, UOU2T14D

Additional Information :

The time section of the DateTime is truncated to zero hours, zero minutes and zero seconds

4.12.4.112 Settlement Period

Field Data Type :

Settlement Period

Field Type :

SP

Field Name :

“SP”

Description :

The settlement Period.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

OCNMFD, NDFD, MELNGC, IMBALNGC, INDDEM, INDGEN, INDO, FPN, QPN, BOD, MIL, MEL, BOAV, PTAV, EBOCF, NETEBSP, TBOD, NDF, TSDF, TSDFD, ITSDO, FUELINST, FUELHH, WINDFOR, NONBM, DISEBSP, NETBSAD, DISBSAD, DISPTAV, ISPSTACK, LOLP, DCONTROL

Additional Information :

Valid values: 1 - 50

4.12.4.113 Short Acceptance Flag

Field Data Type :

Short Acceptance Flag

Field Type :

SA

Field Name :

“SA”

Description :

Flag indicating whether the Acceptance was of “short” duration

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

BOAV

Additional Information :

Valid values: ‘S’ or ‘L’

4.12.4.114 SO-Flag

Field Data Type :

SO-Flag

Field Type :

SO

Field Name :

“SO”

Description :

A value of ‘T’ indicates where an Acceptance or Balancing Services Adjustment Action item should be considered to be potentially impacted by transmission constraints.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

BOALF, ISPSTACK, DISBSAD

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.115 SO-SO Start Time

Field Data Type :

SO-SO Start Time

Field Type :

ST

Field Name :

“ST”

Description :

The date and time from which an SO-SO price applies.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

SOSO

Additional Information :

4.12.4.116 SO-SO Trade Direction

Field Data Type :

SO-SO Trade Direction

Field Type :

TD

Field Name :

“TD”

Description :

Flag indicating whether the direction of an SO-SO trade is up or down.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

SOSO

Additional Information :

Valid values: ‘A01’ (up) or ‘A02’ (down)

4.12.4.117 SO-SO Trade Type

Field Data Type :

SO-SO Trade Type

Field Type :

TT

Field Name :

“TT”

Description :

The type of SO-SO Trade.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

SOSO

Additional Information :

4.12.4.118 Spot Time

Field Data Type :

Spot Time

Field Type :

TS

Field Name :

“TS”

Description :

The time applicable to a given value in a Spot Point pair.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

FPN, QPN, BOD, BOAL, MIL, MEL, TEMP, FREQ, FUELINST, BOALF

Additional Information :

See section on ‘Conversion of Effective From/To times to Spot Times’

4.12.4.119 Stable Export Limit

Field Data Type :

Stable Export Limit

Field Type :

SE

Field Name :

“SE”

Description :

Range in which power export is stable.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

SEL

Additional Information :

Value in MW.

Valid Values: 0 to 9999.

4.12.4.120 Stable Import Limit

Field Data Type :

Stable Import Limit

Field Type :

SI

Field Name :

“SI”

Description :

Range in which power import is stable.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

float

Messages containing field :

SIL

Additional Information :

Value in MW.

Valid Values: -9999 to 0.

4.12.4.121 Stack Item Final Price

Field Data Type :

Stack Item Final Price

Field Type :

FP

Field Name :

“FP”

Description :

The final price of the associated stack item as used to determine the item’s final cost.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in £/MWh.

4.12.4.122 Stack Item Original Price

Field Data Type :

Stack Item Original Price

Field Type :

IP

Field Name :

“IP”

Description :

The original price of the associated stack item. Typically the Bid-Offer Original Price except for STOR Actions where the Stack Item Original Price is the derived price based on either the Bid-Offer Original Price or Reserve Scarcity Price (i.e. the STOR Action Price).

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in £/MWh.

4.12.4.123 Stack Item Volume

Field Data Type :

Stack Item Volume

Field Type :

IV

Field Name :

“IV”

Description :

The volume of the associated stack item.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in MWh.

4.12.4.124 System Frequency

Field Data Type :

System Frequency

Field Type :

SF

Field Name :

“SF”

Description :

System Frequency in Hz.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

FREQ

Additional Information :

Value in Hz.

Valid Values: 0 to 99.999

4.12.4.125 System Message Text

Field Data Type :

System Message text

Field Type :

SM

Field Name :

“SM”

Description :

This field contains the body text of any system messages that are generated by BMRA.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

SYSMSG

Additional Information :

The message text will be plain ascii text, in the majority of cases, be less than 4Kb in length.

4.12.4.126 System Total Priced Accepted Bid Volume

Field Data Type :

System Total Priced Accepted Bid Volume

Field Type :

PC

Field Name :

“PC”

Description :

System wide total Priced Accepted Bid Volume for the Settlement Period

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Value in MWh.

4.12.4.127 System Total Priced Accepted Offer Volume

Field Data Type :

System Total Priced Accepted Offer Volume

Field Type :

PP

Field Name :

“PP”

Description :

System wide total Priced Accepted Offer Volume for the Settlement Period

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Value in MWh.

4.12.4.128 System Total Unpriced Accepted Offer Volume

Field Data Type :

System Total Unpriced Accepted Offer Volume

Field Type :

AP

Field Name :

“AP”

Description :

System wide total Unpriced Accepted Offer Volume for the Settlement Period

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETEBSP

Additional Information :

Value in MWh.

4.12.4.129 System Total Unpriced Accepted Bid Volume

Field Data Type :

System Total Unpriced Accepted Bid Volume

Field Type :

AC

Field Name :

“AC”

Description :

System wide total Unpriced Accepted Bid Volume for the Settlement Period

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETEBSP

Additional Information :

Value in MWh.

4.12.4.130 System Warning Text

Field Data Type :

System Warning text

Field Type :

SW

Field Name :

“SW”

Description :

This field contains the body text of any system warnings that are announced by the NETSO.

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

SYSWARN

Additional Information :

The warning text will be plain ascii text, in the majority of cases, be less than 4Kb in length.

4.12.4.131 TLM Adjusted Cost

Field Data Type :

TLM Adjusted Cost

Field Type :

TC

Field Name :

“TC”

Description :

The derived cost of a stack item based on the final untagged volume, price and associated transmission loss multiplier.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in £.

4.12.4.132 TLM Adjusted Volume

Field Data Type :

TLM Adjusted Volume

Field Type :

TV

Field Name :

“TV”

Description :

The derived volume of a stack item based on the final untagged volume and associated transmission loss multiplier.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Value in MWh.

4.12.4.133 Total Bid Volume

Field Data Type :

Total Bid Volume

Field Type :

BT

Field Name :

“BT”

Description :

System wide total Bid Volume for the Settlement Period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

TBOD

Additional Information :

Value in MWh

4.12.4.134 Total Offer Volume

Field Data Type :

Total Offer Volume

Field Type :

OT

Field Name :

“OT”

Description :

System wide total Offer Volume for the Settlement Period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

TBOD

Additional Information :

Value in MWh

4.12.4.135 Total Registered Capacity

Field Data Type :

Total Registered Capacity

Field Type :

TR

Field Name :

“TR”

Description :

Total Registered Wind Generation Capacity (MW).

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

Int

Messages containing field :

WINDFOR

Additional Information :

4.12.4.136 Total System Accepted Bid Volume

Field Data Type :

Total System Accepted Bid Volume

Field Type :

AB

Field Name :

“AB”

Description :

System wide total Accepted Bid Volume for the Settlement Period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Value in MWh

4.12.4.137 Total System Accepted Offer Volume

Field Data Type :

Total System Accepted Offer Volume

Field Type :

AO

Field Name :

“AO”

Description :

System wide total Accepted Offer Volume for the Settlement Period.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

NETEBSP, DISEBSP

Additional Information :

Value in MWh

4.12.4.138 Total System Adjustment Buy Volume

Field Data Type :

Total System Adjustment Buy Volume

Field Type :

J2

Field Name :

“J2”

Description :

Total volume of Adjustment items held on the Buy Stack.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in MWh.

4.12.4.139 Total System Adjustment Sell Volume

Field Data Type :

Total System Adjustment Sell Volume

Field Type :

J1

Field Name :

“J1”

Description :

Total volume of Adjustment items held on the Sell Stack.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in MWh.

4.12.4.140 Total System Tagged Accepted Bid Volume

Field Data Type :

Total System Tagged Accepted Bid Volume

Field Type :

T2

Field Name :

“T2”

Description :

Total tagged Accepted Bid volume.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in MWh.

4.12.4.141 Total System Tagged Accepted Offer Volume

Field Data Type :

Total System Tagged Accepted Offer Volume

Field Type :

T1

Field Name :

“T1”

Description :

Total tagged Accepted Offer volume.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in MWh.

4.12.4.142 Total System Tagged Adjustment Buy Volume

Field Data Type :

Total System Tagged Adjustment Buy Volume

Field Type :

J4

Field Name :

“J4”

Description :

Total tagged volume of Adjustment items held on the Buy Stack.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in MWh.

4.12.4.143 Total System Tagged Adjustment Sell Volume

Field Data Type :

Total System Tagged Adjustment Sell Volume

Field Type :

J3

Field Name :

“J3”

Description :

Total tagged volume of Adjustment items held on the Sell Stack.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DISEBSP

Additional Information :

Value in MWh.

4.12.4.144 Trade Quantity

Field Data Type :

Trade Quantity

Field Type :

TQ

Field Name :

“TQ”

Description :

Level of an offered SO-SO trade.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

SOSO

Additional Information :

Value in MW

4.12.4.145 Trade Price

Field Data Type :

Trade Price

Field Type :

PT

Field Name :

“PT”

Description :

The price of an SO-SO trade.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

SOSO

Additional Information :

Value in unit currency per MWh. The currency used (e.g. EUR or GBP) will potentially be different for different SO-SO Trade Types (i.e. different Interconnectors and products)

4.12.4.146 Transmission Loss Multiplier

Field Data Type :

Transmission Loss Multiplier

Field Type :

TM

Field Name :

“TM”

Description :

The Transmission Loss Multiplier for the associated stack item derived from its associated BM Unit (for Balancing Services Adjustment Action items the value is set as 1.)

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

ISPSTACK

Additional Information :

Always a positive value.

4.12.4.147 Week Start Date

Field Data Type :

Week Start Date

Field Type :

WD

Field Name :

“WD”

Description :

The date of the Monday in a particular week.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

OCNMFW, OCNMF3Y, NDFW, TSDFW

Additional Information :

The time section of the DateTime will be truncated to zero hours, zero minutes and zero seconds.

4.12.4.148 Zone Indicator

Field Data Type :

Zone Indicator

Field Type :

ZI

Field Name :

“ZI”

Description :

The Zone that a forecast is applicable to

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

INDDEM, INDGEN, MELNGC, IMBALNGC, NDF, TSDF

Additional Information :

Valid Values: ”B1”, “B2”, “B3”, “B4”, “B5”, “B6”, “B7”, “B8”, “B9”, “B10”, “B11”, “B12”, “B13”, “B14”, “B15”, “B16”, “B17” and “N”

4.12.4.149 STOR Provider Flag

Field Data Type :

STOR Provider Flag

Field Type :

PF

Field Name :

“PF”

Description :

A value of ‘T’ indicates where an Acceptance or Balancing Services Adjustment Action item should be considered being related to a STOR Provider

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

BOALF, ISPSTACK, DISBSAD

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.150 De-rated Margin

Field Data Type :

De-rated Margin

Field Type :

DR

Field Name :

“DR”

Description :

***.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

LOLP

Additional Information :

Value in MW

4.12.4.151 Loss of Load Probability

Field Data Type :

Loss of Load Probability

Field Type :

LP

Field Name :

“LP”

Description :

***.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

LOLP

Additional Information :

Always less than or equal to 1

4.12.4.152 Affected LDSO

Field Data Type :

Affected LDSO

Field Type :

DS

Field Name :

“DS”

Description :

The LDSO affected by a demand control instruction

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

DCONTROL

Additional Information :

4.12.4.153 Demand Control ID

Field Data Type :

Demand Control ID

Field Type :

ID

Field Name :

“ID”

Description :

The unique identifier for a demand control instruction

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

DCONTROL

Additional Information :

4.12.4.154 Instruction Sequence No

Field Data Type :

Instruction Sequence No

Field Type :

SQ

Field Name :

“SQ”

Description :

The sequence number relating to the demand control event

TIB Data Type :

TIBRVMSG_32

C/Java Type :

Int

Messages containing field :

DCONTROL

Additional Information :

4.12.4.155 Demand Control Event Flag

Field Data Type :

Demand Control Event Flag

Field Type :

EV

Field Name :

“EV”

Description :

A value of ‘I’ indicates an instruction initiated by the NETSO or an Emergency Manual Disconnection. A Value of ‘L’ indicates an Automatic Low Frequency Demand Disconnection

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

char*/String

Messages containing field :

DCONTROL

Additional Information :

4.12.4.156 Time From

Field Data Type :

Time From

Field Type :

TF

Field Name :

“TF”

Description :

The time from which the demand control instruction takes effect

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

Time_t/Date

Messages containing field :

DCONTROL

Additional Information :

4.12.4.157 Time To

Field Data Type :

Time To

Field Type :

TI

Field Name :

“TI”

Description :

The time to which the demand control instruction takes effect

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

Time_t/Date

Messages containing field :

DCONTROL

Additional Information :

4.12.4.158 Demand Control Level

Field Data Type :

Demand Control Level

Field Type :

VO

Field Name :

“VO”

Description :

The level of demand during the demand control event in MW

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

DCONTROL

Additional Information :

4.12.4.159 Amendment Flag

Field Data Type :

Amendment Flag

Field Type :

AM

Field Name :

“AM”

Description :

ORI (Original), INS (Insert), UPD (Update)

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

DCONTROL

Additional Information :

4.12.4.160 Reserve Scarcity Price

Field Data Type :

Reserve Scarcity Price

Field Type :

RSP

Field Name :

“RSP”

Description :

The Reserve Scarcity Price for a given Settlement Period. This field will be NULL where related to an action that is not a STOR Action.

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Double

Messages containing field :

ISPSTACK, DISEBSP

Additional Information :

Value in £/MWh

4.12.4.161 Bid-Offer Original Price

Field Data Type :

Bid-Offer Original Price

Field Type :

UP

Field Name :

“UP”

Description :

The Offer or Bid Price or BSAA Cost of the System Action (£/MWh) as derived from the original BOD or BSAD

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Double

Messages containing field :

ISPSTACK

Additional Information :

Value in £/MWh

4.12.4.162 RR Quarter Hour Period

Field Data Type :

RR Quarter Hour Period

Field Type :

QP

Field Name :

“QP”

Description :

The Quarter Hour Period within a given Settlement Period.

TIB Data Type :

TIBRVMSG_I32

C/Java Type :

int

Messages containing field :

RRBD, AD, GBNM, IS, QRRC

Additional Information :

Valid values 1 - 2.

4.12.4.163 Party Id

Field Data Type :

Party Id

Field Type :

PI

Field Name :

“PI”

Description :

The unique identifier of a BSC Party

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

4.12.4.164 RR Market Balance Area

Field Data Type :

RR Market Balance Area

Field Type :

BA

Field Name :

“BA”

Description :

The identifier of the balancing area for Replacement Reserve

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

4.12.4.165 RR Associated TSO

Field Data Type :

RR Associated TSO

Field Type :

AT

Field Name :

“AT”

Description :

The identifier of the Transmission System Operator associated with Replacement Reserve data

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

4.12.4.166 RR Divisible

Field Data Type :

RR Divisible

Field Type :

DI

Field Name :

“DI”

Description :

Indicator of whether a RR bid is divisible

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

Valid values: ‘A01’ (yes) or ‘A02’ (no)

4.12.4.167 RR Linking Bid Id

Field Data Type :

RR Linking Bid Id

Field Type :

LB

Field Name :

“LB”

Description :

Identifier to link bids, where applicable

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

4.12.4.168 RR Multipart Bid Id

Field Data Type :

RR Multipart Bid Id

Field Type :

MB

Field Name :

“MB”

Description :

Identifier to establish multipart bids, where applicable

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

4.12.4.169 RR Exclusive Bid Id

Field Data Type :

RR Exclusive Bid Id

Field Type :

EB

Field Name :

“EB”

Description :

Identifier to establish exclusive bids, where applicable

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

4.12.4.170 RR Flow Direction

Field Data Type :

RR Flow Direction

Field Type :

FD

Field Name :

“FD”

Description :

Indicator of direction of bid

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD, AD, GBNM, IS

Additional Information :

Valid values: ‘A01’ (up) or ‘A02 (down)

4.12.4.171 RR Quantity

Field Data Type :

RR Quantity

Field Type :

QI

Field Name :

“QI”

Description :

A quantity of an RR bid

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

RRBD, AD, GBNM, IS

Additional Information :

Value in MW

4.12.4.172 RR Maximum Quantity

Field Data Type :

RR Maximum Quantity

Field Type :

QX

Field Name :

“QX”

Description :

Quantity offered in bid

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

RRBD

Additional Information :

Value in MW

4.12.4.173 RR Bid Resolution

Field Data Type :

RR Bid Resolution

Field Type :

BR

Field Name :

“BR”

Description :

Resolution of bid

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

Valid Values: ‘PT60M’, ‘PT30M’, ‘PT15M’

4.12.4.174 RR Position

Field Data Type :

RR Position

Field Type :

PO

Field Name :

“PO”

Description :

Position within the bid resolution interval

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

4.12.4.175 RR Price

Field Data Type :

RR Price

Field Type :

PR

Field Name :

“PR”

Description :

Price of RR bid

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

TIBRVMSG_F32

Messages containing field :

RRBD, AD, GBNM

Additional Information :

Value in £/MWh

4.12.4.176 RR Status

Field Data Type :

RR Status

Field Type :

RS

Field Name :

“RS”

Description :

Status of the RR bid

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

RRBD

Additional Information :

Valid values: ‘A06’ (available, ‘A28’ (unshared), ‘A11’ (restricted)

4.12.4.177 RR Auction Period Start

Field Data Type :

Auction Period Start

Field Type :

AS

Field Name :

“AS”

Description :

The datetime of the start of an Auction Period.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

RRAGGINFO

Additional Information :

4.12.4.178 RR Auction Period End

Field Data Type :

Auction Period End

Field Type :

AE

Field Name :

“AE”

Description :

The datetime of the end of an Auction Period.

TIB Data Type :

TIBRVMSG_DATETIME

C/Java Type :

time_t/Date

Messages containing field :

RRAGGINFO

Additional Information :

4.12.4.179 RR Total Volume of Offered Bids

Field Data Type :

Total Volume of Offered Bids

Field Type :

OS

Field Name :

“OS”

Description :

Total volume of offered RR bids

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

RRAGGINFO

Additional Information :

Value in MWh

4.12.4.180 RR Total Volume of Activated Bids

Field Data Type :

Total Volume of Activated Bids

Field Type :

BS

Field Name :

“BS”

Description :

Total volume of activated RR bids

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

RRAGGINFO

Additional Information :

Value in MWh

4.12.4.181 RR Total Volume of Unavailable Bids

Field Data Type :

Total Volume of Unavailable Bids

Field Type :

US

Field Name :

“US”

Description :

Total volume of unavailable RR bids

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

RRAGGINFO

Additional Information :

Value in MWh

4.12.4.182 RR Business Type

Field Data Type :

RR Business Type

Field Type :

TY

Field Name :

“TY”

Description :

Type of Replacement Reserve

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

AD, GBNM, IS

Additional Information :

Value in MW

4.12.4.183 RR Interconnector Identifier

Field Data Type :

RR Interconnector Identifier

Field Type :

II

Field Name :

“II”

Description :

Identifier of interconnector

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

IS

Additional Information :

Value in MW

4.12.4.184 RR Cashflow

Field Data Type :

RR Cashflow

Field Type :

CR

Field Name :

“CR”

Description :

Cashflow associated with RR

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

QRRC, PRRC

Additional Information :

Value in £

4.12.4.185 RR Accepted Bid Volume

Field Data Type :

RR Accepted Bid Volume

Field Type :

BV

Field Name :

“BI”

Description :

Volume of accepted RR offers

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

RRBOAV, RRPTAV

Additional Information :

Value in MWh

4.12.4.186 RR Accepted Offer Volume

Field Data Type :

RR Accepted Offer Volume

Field Type :

OV

Field Name :

“OV”

Description :

Volume of accepted RR offers

TIB Data Type :

TIBRVMSG_F32

C/Java Type :

Float

Messages containing field :

RRBOAV, RRPTAV

Additional Information :

Value in MWh

4.12.4.187 RR Instruction Flag

Field Data Type :

RR Instruction Flag

Field Type :

RN

Field Name :

“RN”

Description :

Indicator of whether an acceptance is part of an RR instruction

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

BOALF

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.188 RR Schedule Flag

Field Data Type :

RR Schedule Flag

Field Type :

SC

Field Name :

“SC”

Description :

Indicator of when an acceptance is part of an RR schedule

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

BOALF

Additional Information :

Valid Values: ‘T’ or ‘F’.

4.12.4.189 Marketobjectstatus

Field Data Type:

Marketobjectstatus

Field Type:

MOS

Field Name:

“MOS”

Description:

Status of RR Bid

TIB Data Type:

TIBRVMSG_STRING

C/Java Type:

Char*/String

Messages containing field:

AD

Additional Information:

Valid values: Ordered, Available and Cancelled, which correspond to the LIBRA codes A10, A06 and A09 respectively

4.12.4.190 BSAD Party Id

Field Data Type :

BSAD Party Id

Field Type :

PX

Field Name :

“PX”

Description :

The name or unique identifier of the person who provides Balancing Services outside of the Balancing Mechanism

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

DISBSAD

Additional Information :

4.12.4.191 BSAD Asset Id

Field Data Type :

BSAD Asset Id

Field Type :

AX

Field Name :

“AX”

Description :

The name or unique identifier of the asset providing the relevant Balancing Services Adjustment Action

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

DISBSAD

Additional Information :

4.12.4.192 Tendered Status

Field Data Type :

Tendered Status

Field Type :

TX

Field Name :

“TX”

Description :

Whether the Balancing Service was procured by NETSO through a tender

TIB Data Type :

TIBRVMSG_STRING

C/Java Type :

Char*/String

Messages containing field :

DISBSAD

Additional Information :

4.12.4.193 Service Type

Field Data Type :

Service Type

Field Type :

SX

Field Name :

“SX”

Description :

The type of Balancing Service procured

TIB Data Type :

TIBRVMSG_STRINGT

C/Java Type :

Char*/String

Messages containing field :

DISBSAD

Additional Information :

4.12.5 Message Definitions

4.12.5.1 OCNMFD - Surplus Forecast 2-14 days ahead

This message contains peak-of-the-day surplus forecast values for the following 2 weeks. The data is published by BMRA as it is received from the NETSO. The Publishing Time in the message is applicable to the forecast as a whole. The records in the message are ordered by time.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Number of records

NR

The number of times the next THREE fields are repeated.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Margin/Surplus Value

VM

The surplus in MW.

Message Subject Name

BMRA.SYSTEM.OCNMFD

4.12.5.2 OCNMFW - Surplus Forecast 2-52 weeks ahead

This message contains peak-of-the-week surplus forecast values for the following year. The data is published by BMRA as it is received from the NETSO. The Publishing Time in the message is applicable to the forecast as a whole. The records in the message are ordered by time.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Number of Records

NR

The number of times the next THREE fields are repeated.

Calendar Week Number

WN

The number of the week.

Week Start Date

WD

The start date of the week (in GMT).

Margin/Surplus Value

VM

The Surplus in MW.

Message Subject Name

BMRA.SYSTEM.OCNMFW

4.12.5.2A OCNMF3Y - Surplus Forecast 2-156 weeks ahead

This message contains peak-of-the-week surplus forecast values for the following three years. The data is published by BMRA as it is received from the NETSO. The Publishing Time in the message is applicable to the forecast as a whole. The records in the message are ordered by time.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Number of Records

NR

The number of times the next THREE fields are repeated.

Calendar Week Number

WN

The number of the week.

Week Start Date

WD

The start date of the week (in GMT).

Margin/Surplus Value

VM

The Surplus in MW.

Message Subject Name

BMRA.SYSTEM.OCNMF3Y

4.12.5.3 NDFD - Demand Forecast 2-14 days ahead

This message contains peak-of-the-day demand forecast values for the following 2 weeks. The data is published by BMRA as it is received from the NETSO. The Publishing Time in the message is applicable to the forecast as a whole. The records in the message are ordered by time.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Number of Records

NR

The number of times the next THREE fields are repeated.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Demand Value

VD

The demand in MW.

Message Subject Name

BMRA.SYSTEM.NDFD

4.12.5.4 TSDFD – Transmission System Demand Forecast 2-14 days ahead

This message contains peak-of-the-day Transmission System demand forecast values for the following 2 weeks. The data is published by BMRA as it is received from the NETSO. The Publishing Time in the message is applicable to the forecast as a whole. The records in the message are ordered by time.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Number of Records

NR

The number of times the next THREE fields are repeated.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Demand Value

VD

The demand in MW.

Message Subject Name

BMRA.SYSTEM.TSDFD

4.12.5.5 NDFW - Demand Forecast 2-52 weeks ahead

This message contains peak-of-the-week demand forecast values for the following year. The data is published by BMRA as it is received from the NETSO. The Publishing Time in the message is applicable to the forecast as a whole. The records in the message are ordered by time.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Number of Records

NR

The number of times the next THREE fields are repeated.

Calendar Week Number

WN

The number of the week.

Week Start Date

WD

The start date of the week (in GMT).

Demand Value

VD

The Demand in MW.

Message Subject Name

BMRA.SYSTEM.NDFW

4.12.5.6 TSDFW – Transmission System Demand Forecast 2-52 weeks ahead

This message contains peak-of-the-week Transmission System demand forecast values for the following year. The data is published by BMRA as it is received from the NETSO. The Publishing Time in the message is applicable to the forecast as a whole. The records in the message are ordered by time.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Number of Records

NR

The number of times the next THREE fields are repeated.

Calendar Week Number

WN

The number of the week.

Week Start Date

WD

The start date of the week (in GMT).

Demand Value

VD

The Demand in MW.

Message Subject Name

BMRA.SYSTEM.TSDFW

4.12.5.7 NDF – National Demand Forecast

This message contains the National Demand Forecast values for every half hour period from the start of the current day to the furthest ahead forecast that has so far been received by the BMRA.

Every time an updated forecast is received from the NETSO, BMRA publishes the data in this message and additionally includes previously received forecast values from period 1 of the current day onwards. The Publishing Time field is therefore applicable to each period in the forecast and indicates the time that data for a particular period was last received and the data reported is always that most recently received for each period. The records in the message are ordered by Settlement Date and Period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Zone Indicator

ZI

The zone that this forecast applies to.

N for national data.

Number of Records

NR

This field indicates how many times the next FOUR fields appear in the message.

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO. It is included so users can see which forecast this value comes from, and therefore which weather forecast the value was based upon.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Demand

VD

The Demand in MW.

Message Subject Name

BMRA.SYSTEM.NDF.c

(where c is ‘N’ and indicates the forecast is National)

4.12.5.8 TSDF – Transmission System Demand Forecast

This message contains the Transmission System Demand Forecast values for every half hour period from the start of the current day to the furthest ahead forecast that has so far been received by the BMRA.

Every time an updated forecast is received from the NETSO, BMRA publishes the data in this message and additionally includes previously received forecast values from period 1 of the current day onwards. The Publishing Time field is therefore applicable to each period in the forecast and indicates the time that data for a particular period was last received and the data reported is always that most recently received for each period. The records in the message are ordered by Settlement Date and Period.

The NETSO cannot provide Demand values for Interconnectors and pumped storage (Transmission System Demand forecast) for the 09:00am hour forecast. Therefore NETSO estimates these values or enters them as a ‘zero’ value.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Zone Indicator

ZI

The zone that this forecast applies to.

B1-B17 for zonal data, N for national data.

Number of Records

NR

This field indicates how many times the next FOUR fields appear in the message.

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO. It is included so users can see which forecast this value comes from, and therefore which weather forecast the value was based upon.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Demand

VtD

The Demand in MW.

Message Subject Name

BMRA.SYSTEM.TSDF.c

(where c is ‘N’, or ‘B1’ to ‘B17’ and indicates whether the forecast is National or Regional)

4.12.5.9 MELNGC - Indicated Margin

This message contains margin forecast values for every half hour period from the start of the current day to the furthest ahead forecast that has so far been received by the BMRA.

Every time an updated forecast is received from the NETSO, BMRA publishes the data in this message and additionally includes previously received forecast values from period 1 of the current day onwards. The Publishing Time field is therefore applicable to each period in the forecast and indicates the time that data for a particular period was last received and the data reported is always that most recently received for each period. The records in the message are ordered by Settlement Date and Period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Zone Indicator

ZI

The zone that this forecast applies to.

B1-B17 for zonal data, N for national data.

Number of Records

NR

This field indicates how many times the next FOUR fields appear in the flow.

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO. It is included so users can see which forecast this value comes from, and therefore which weather forecast the value was based upon.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Indicated Margin

VM

The indicated margin in MW.

Message Subject Name

BMRA.SYSTEM.MELNGC.c

(where c is ‘N’, or ‘B1’ to ‘B17’ and indicates whether the forecast is National or Regional)

4.12.5.10 IMBALNGC - Indicated Imbalance

This message contains imbalance forecast values for every half hour period from the start of the current day to the furthest ahead forecast that has so far been received by the BMRA.

Every time an updated forecast is received from the NETSO, BMRA publishes the data in this message and additionally includes previously received forecast values from period 1 of the current day onwards. The Publishing Time field is therefore applicable to each period in the forecast and indicates the time that data for a particular period was last received and the data reported is always that most recently received for each period. The records in the message are ordered by Settlement Date and Period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Zone Indicator

ZI

The zone that this forecast applies to.

B1-B17 for zonal data, N for national data.

Number of Records

NR

This field will indicate how many times the next FOUR fields appear in the flow.

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO. It is included so users can see which forecast this value comes from, and therefore which weather forecast the value was based upon.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Indicated Imbalance

VI

The indicated imbalance in MW.

Message Subject Name

BMRA.SYSTEM.IMBALNGC.c

(where c is ‘N’, or ‘B1’ to ‘B17’ and indicates whether the forecast is National or Regional)

4.12.5.11 INDGEN - Indicated Generation

This message contains generation forecast values for every half hour period from the start of the current day to the furthest ahead forecast that has so far been received by the BMRA.

Every time an updated forecast is received from the NETSO, BMRA publishes the data in this message and additionally includes previously received forecast values from period 1 of the current day onwards. The Publishing Time field is therefore applicable to each period in the forecast and indicates the time that data for a particular period was last received and the data reported is always that most recently received for each period. The records in the message are ordered by Settlement Date and Period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Zone Indicator

ZI

The zone that this forecast applies to.

B1-B17 for zonal data, N for national data.

Number of Records

NR

This field will indicate how many times the next FOUR fields appear in the flow.

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO. It is included so users can see which forecast this value comes from, and therefore which weather forecast the value was based upon.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Indicated Generation

VG

The indicated generation in MW.

Message Subject Name

BMRA.SYSTEM.INDGEN.c

(where c is ‘N’, or ‘B1’ to ‘B17’ and indicates whether the forecast is National or Regional)

4.12.5.12 INDDEM - Indicated Demand

This message contains indicated demand forecast values for every half hour period from the start of the current day to the furthest ahead forecast that has so far been received by the BMRA.

Every time an updated forecast is received from the NETSO, BMRA publishes the data in this message and additionally includes previously received forecast values from period 1 of the current day onwards. The Publishing Time field is therefore applicable to each period in the forecast and indicates the time that data for a particular period was last received and the data reported is always that most recently received for each period. The records in the message are ordered by Settlement Date and Period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Zone Indicator

ZI

The zone that this forecast applies to.

B1-B17 for zonal data, N for national data.

Number of Records

NR

This field will indicate how many times the next FOUR fields appear in the flow.

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO. It is included so users can see which forecast this value comes from, and therefore which weather forecast the value was based upon.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Indicated Demand

VD

The indicated demand in MW.

Message Subject Name

BMRA.SYSTEM.INDDEM.c

(where c is ‘N’, or ’B1’ to ‘B17’ and indicates whether the forecast is National or Regional)

4.12.5.13 SYSWARN - System Warnings

This message contains the text of any system warnings that are issued by the NETSO. Note that the Publishing Time is the time that the message was published by BMRA, not NETSO.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Time

TP

The time (in GMT) the warning was published by BMRA.

System Warning Text

SW

The body text of the system warning.

Message Subject Name

BMRA.SYSTEM.SYSWARN

4.12.5.14 INDO - Initial National Demand Out-turn

This message is published when the appropriate data is received from the NETSO. A single message is published every settlement period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

This is the time that the data was published by the NETSO.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Demand Out-turn

VD

The average demand in MW.

Message Subject Name

BMRA.SYSTEM.INDO

4.12.5.15 ITSDO – Initial Transmission System Demand Out-turn

This message is published when the appropriate data is received from the NETSO. A single message is published every settlement period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

This is the time that the data was published by the NETSO.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Demand Out-turn

VD

The average demand in MW.

Message Subject Name

BMRA.SYSTEM.ITSDO

4.12.5.16 TEMP – Temperature Data

This message contains the weighted average temperature as measured at noon local time in a number of GB locations, along with 3 additional reference data values for the Normal, High and Low temperatures.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that the data was originally published by the NETSO.

Spot Time

TS

The datetime at which the temperature was measured.

Outturn temperature

TO

Temperature in degrees celsius.

Normal Reference temperature

TN

Temperature in degrees celsius.

Low Reference temperature

TL

Temperature in degrees celsius.

High Reference temperature

TH

Temperature in degrees celsius.

Message Subject Name

BMRA.SYSTEM.TEMP

4.12.5.17 FREQ – System Frequency

This message contains the System Frequency at a spot time, measured in Hz.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Spot Time

TS

The datetime at which the frequency was measured.

System Frequency

SF

System Frequency in Hz.

Message Subject Name

BMRA.SYSTEM.FREQ

4.12.5.18 FUELINST – Instantaneous Generation by Fuel Type

This message contains the Instantaneous Generation by Fuel Type for a particular Settlement Period.

It should be noted that the TIBCO messages cap negative values received from NETSO at zero for all fuel types (including interconnectors).

Furthermore, the BMRA does NOT publish a Total Instantaneous figure across all fuel types.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that this element was originally published by the NETSO.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Spot Time

TS

The datetime at which the generation was measured.

Fuel Type

FT

Fuel Type.

Generation

FG

The Generation in MW.

Message Subject Name

BMRA.SYSTEM.FUELINST

4.12.5.19 FUELHH – Half-Hourly Generation by Fuel Type

This message contains the Generation by Fuel Type for a particular Half Hour.

It should be noted that the TIBCO messages cap negative values received from NETSO at zero for all non-interconnector fuel types. For interconnector fuel types, NO capping is applied, values are publish exactly as received.

Furthermore, the BMRA does NOT publish a Total Half-Hourly Outturn figure across all fuel types.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Fuel Type

FT

Fuel Type.

Generation

FG

The Generation in MW.

Message Subject Name

BMRA.SYSTEM.FUELHH

4.12.5.20 WINDFOR – Forecast Peak Wind Generation

This message contains the peak wind generation forecast values for various half hour periods from the start of the current day to the furthest ahead forecast that has so far been received by the BMRA.

Each forecast file contains data for the following local times:

21:00 D

00:00 D+1

05:00 D+1

08:00 D+1

12:00 D+1

17:00 D+1

21:00 D+1

00:00 D+2

05:00 D+2

08:00 D+2

12:00 D+2

17:00 D+2

21:00 D+2

Every time an updated forecast is received from the NETSO, BMRA publishes the data in this message and additionally includes previously received forecast values from period 1 of the current day onwards (where previously received). The Publishing Time field is therefore applicable to each period in the forecast and indicates the time that data for a particular period was last received and the data reported is always that most recently received for each period. The records in the message are ordered by Settlement Date and Period.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Number of Records

NR

This field indicates how many times the next FOUR fields appear in the message.

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO. It is included so users can see which forecast this value comes from, and therefore which forecast the value was based upon.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Generation

VG

The Generation in MW.

Total Registered Capacity

TR

Total Registered Wind Generation Capacity (MW)

Message Subject Name

BMRA.SYSTEM.WINDFOR

4.12.5.21 INDOD – Daily Energy Volume Data

This message is published when the appropriate data is received from the NETSO. A single message is published every settlement day.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

This is the time that the data was published by the NETSO.

Settlement Date

SD

The settlement date.

Energy Volume Out-turn

EO

The Outturn Daily Energy Volume in MWh.

Energy Volume Low Reference

EL

The Daily Energy Low Reference Volume in MWh.

Energy Volume High Reference

EH

The Daily Energy High Reference Volume in MWh.

Energy Volume Normal Reference

EN

The Daily Energy Normal Reference Volume in MWh.

Message Subject Name

BMRA.SYSTEM.INDOD

4.12.5.22 NONBM – Non-BM STOR Generation Instructed Volume

This message contains the total volume of instructions issued to non-BM STOR units under Short Term Operating Reserve (STOR) contracts for a particular Half Hour.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Publishing Date

TP

The time that this element of the forecast was originally published by the NETSO.

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Non-BM STOR Volume

NB

The Non-BM STOR Instructed Volume in MWh.

Message Subject Name

BMRA.SYSTEM.NONBM

4.12.5.23 FPN - Final Physical Notice

This message contains FPN values for a single BM Unit, for a single settlement period. The data is published as it is received from the NETSO.

Note that the Effective From Time and Effective To Times are converted to spot times for purposes of distribution. One message will contain the data for a whole settlement period.

If the Number of Records field is set to zero, BMRA has received invalid data for that settlement period and BM Unit.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Number of Spot Points

NP

The number of spot points. Implies that what follows is a series of spot data points, each of which consist of TWO fields.

Spot Time

TS

The time at which the following VP field value is valid.

FPN Level

VP

FPN in MW at the above spot time.

Message Subject Name

BMRA.BM.<BM_UNIT>.FPN

4.12.5.24 QPN - Quiescent Physical Notice

This message contains QPN values for a single BM Unit, for a single settlement period. The data is published as it is received from the NETSO.

Note that the Effective From Time and Effective To Times are converted to spot times for purposes of distribution. One message will contain the data for a whole settlement period.

If the Number of Records field is set to zero, BMRA has received invalid data for that settlement period and BM Unit.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Number of Spot Points

NP

The number of spot points. Implies that what follows is a series of spot data points, each of which consist of TWO fields.

Spot Time

TS

The time at which the following VP field value is valid.

QPN Level

VP

QPN in MW at the above spot time.

Message Subject Name

BMRA.BM.<BM_UNIT>.QPN

4.12.5.25 BOD - Bid-Offer Pairs

This message contains Bid-Offer values for a single BM Unit, for a single settlement period, for a single bid-offer pair number. The data is published as it is received from the NETSO.

Note that the Effective From Time and Effective To Times are converted to spot times for purposes of distribution. One message will contain the data for a whole settlement period.

If the Number of Records field is set to zero, BMRA has received invalid data for that settlement period and BM Unit.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Bid-Offer pair number

NN

B-O pair number.

Offer price

OP

Offer price.

Bid price

BP

Bid price.

Number of Spot Points

NP

The number of spot points. Implies that what follows is a series of spot data points, each of which consist of TWO fields.

Spot time

TS

The time at which the following VB field value is valid.

Bid-Offer Level Value

VB

Bid-Offer level in MW at the above spot time.

Message Subject Name

BMRA.BM.<BM_UNIT>.BOD.n

(where n represents the Bid-Offer Pair number, in the range -6 to 6 excluding 0).

4.12.5.26 BOAL - Bid-Offer Acceptances

This message contains acceptance data for a single BM Unit, for a single acceptance for Settlement Dates prior to the P217 effective date. The data is published as it is received from the NETSO.

Note that the Effective From Time and Effective To Times are converted to spot times for purposes of distribution. One message will contain the data for a single acceptance.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Acceptance number

NK

The acceptance number described in this message.

Acceptance Time

TA

Time that acceptance was made.

Deemed Acceptance flag

AD

If true, no Bid-Offer was made.

Number of Spot Points

NP

The number of spot points. Implies that what follows is a series of spot data points, each of which consist of TWO fields.

Spot Time

TS

The time at which the following VA field value is valid.

Acceptance Level Value

VA

Acceptance in MW at the above spot time.

Message Subject Name

BMRA BM.<BM_UNIT>.BOAL

4.12.5.27 BOALF – Bid-Offer Acceptance Level Flagged

This message contains acceptance data for a single BM Unit, for a single acceptance for Settlement Dates on and after the P217 effective date. The data is published as it is received from the NETSO.

Note that the Effective From Time and Effective To Times are converted to spot times for purposes of distribution. One message will contain the data for a single acceptance.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Acceptance number

NK

The acceptance number described in this message.

SO-Flag

SO

A value of 'T' indicates the Acceptance should be considered to be potentially impacted by transmission constraints.

STOR Provider Flag

PF

Indicates the item relates to a STOR Provider

RR Instruction Flag

RN

Indicates the item relates to an RR Instruction

RR Schedule Flag

SC

Indicates the item relates to the RR Schedule

Acceptance Time

TA

Time that acceptance was made.

Deemed Acceptance flag

AD

If true, no Bid-Offer was made.

Number of Spot Points

NP

The number of spot points. Implies that what follows is a series of spot data points, each of which consist of TWO fields.

Spot Time

TS

The time at which the following VA field value is valid.

Acceptance Level Value

VA

Acceptance in MW at the above spot time.

Message Subject Name

BMRA BM.<BM_UNIT>.BOALF

4.12.5.28 MEL - Maximum Export Limit

This message contains MEL values for a single BM Unit, for a single settlement period. The data is published as it is received from the NETSO.

Note that the Effective From Time and Effective To Times are converted to spot times for purposes of distribution. One message will contain the data for a whole settlement period.

If the Number of Records field is set to zero, BMRA has received invalid data for that settlement period and BM Unit.

Message Definition

The following table lists the fields that are required in the message.

Field

Field Type

Description of field

Settlement Date

SD

The settlement date.

Settlement Period

SP

The settlement period.

Number of Spot Points

NP

The number of spot points. Implies that what follows is a series of spot data points, each of which consist of TWO fields.

Spot Time

TS

The time at which the following VE field value is valid.

MEL

VE

MEL in MW at the above spot time.

Message Subject Name

BMRA.BM.<BM_UNIT>.MEL

4.12.5.29 MIL - Maximum Import Limit

This message contains MIL values for a single BM Unit, for a single settlement period. The data is published as it is received from the