Document title: We appreciate your feedback · submitting the report to the reporting system. L...

Document title:

Publishing date: 02/07/2014

We appreciate your feedback

Please click on the icon to take a 5’ online surveyand provide your feedback about this document

http://www.acer.europa.eu/Lists/Survey/NewForm.aspx?documentid=ACER-2015-19612&Source=http%3a%2f%2fwww.acer.europa.eu

REMIT ELECTRICITY NOMINATIONS REPORTING SCHEMA USAGE GUIDELINES ARIS IMPLEMENTATION AGENCY FOR THE COOPERATION OF ENERGY REGULATORS

REVISION 1.0

DRAFT 27/05/2014

REMIT Electricity nominations Reporting Schema Usage Guidelines ARIS Implementation

Draft Page 2 / 12

27/05/2014

TABLE OF CONTENTS

1 INTRODUCTION ...................................................................................................................... 3

1.1 Purpose ........................................................................................................................................ 3

1.1.1 Topics Covered .............................................................................................................................3

1.1.2 Covered Elsewhere .......................................................................................................................3

1.2 Audience ....................................................................................................................................... 3

1.3 Definition of Terms ....................................................................................................................... 3

2 REMIT ELECTRICITY NOMINATIONS REPORTING SCHEMAS ........................................... 4

2.1 Overview ....................................................................................................................................... 4

2.2 Electricity Nominations Reports .................................................................................................... 4

2.3 Creating Electricity Nominations Reports ..................................................................................... 4

3 ELECTRICITY NOMINATIONS REPORTS .............................................................................. 5

4 POPULATING ELECTRICITY NOMINATIONS REPORTS ..................................................... 7


Draft Page 3 / 12

27/05/2014

1 INTRODUCTION Under the ARIS project, data will be collected by ACER for the purpose of market monitoring under

the guidance of the REMIT Implementing Acts.

To allow ACER to perform the market monitoring tasks, they will be collecting data from market

participants (and Reporting entities) within the European Union.

1.1 Purpose

This document details the guidelines for using the Electricity nominations reporting data schemas

for reporting fundamental data relating to Electricity nominations, to ACER.

1.1.1 Topics Covered

This document covers the following topics:

Electricity nominations Reporting

1.1.2 Covered Elsewhere

The following information is not covered by this document:

ENTSO-E platform reporting

ENTSOG platform reporting

Gas Nominations and Schedule reporting

LNG reporting

Gas Storage reporting

1.2 Audience

This document is used by:

Market Participants / Reporting entities for the purpose of understanding the reporting

schema templates and providing the correct data.

1.3 Definition of Terms

Terms Definition

ARIS ACER reporting information system for applying REMIT

REMIT Regulation on Energy Market Integrity and Transparency

TSO Transmission system operator


Draft Page 4 / 12

27/05/2014

2 REMIT ELECTRICITY NOMINATIONS REPORTING SCHEMAS The REMIT Electricity Nominations Reporting schemas are schemas dedicated for reporting

Electricity Nominations fundamental data to ACER under the regulations pertaining to fundamental

data reporting in the REMIT implementing acts.

2.1 Overview

The REMIT Electricity Nominations Reporting schemas provide reporting elements for Electricity

fundamental data reporting.

2.2 Electricity Nominations Reports

The Reports provide Electricity TSOs with the ability to report the updates relevant to electricity

fundamental data on capacity and use of infrastructure, in accordance with (draft) Implementing

acts, namely related to nominations.

2.3 Creating Electricity Nominations Reports

All reports are created as XML files based on the [PM- name to be specified after consultation].

This XML file(s) contain(s) the reported details from the reporting entity.

The value populated in V[x] is dependent on the version of the schema used for reporting.

All reports must contain two mandatory fields. The following two fields must always be populated;

- Reporting Timestamp – this field is used for technical validation of the time taken between

generating / submitting the report to the time at which the data is received by the reporting

system.

- Reporting Participant – the reporting participant is the identifier of the participant who is

submitting the report to the reporting system.

Note: These fields are not required under the implementing acts, but are required as part of the

reporting mechanism for registered reporting participants.


Draft Page 5 / 12

27/05/2014

3 ELECTRICITY NOMINATIONS REPORTS

Electricity TSOs in the European Union shall provide the Agency fundamental electricity

transmission data related to Cross border nominations1:

Long term (yearly and monthly2), day-ahead and intraday cross border nominations values

as a result of explicit allocations related to the relevant borders for each [reporting] day, in

Schedule Document format (IEC62325-451-2-schedule; see chapter 4 with explanation of

data fields applicable and not applicable from the used schema) in at least hourly

resolution.

The nominations would be provided, per direction between bidding zones, is:

E.g. an example for Croatia: HR►SI, SI►HR, HR►HU and HU►HR.

The nominations would be gathered by the end of the schedule day and reported

afterwards to the Agency in [two files one for each of the [relevant] borders] OR [one file

per TSO] in accordance with technical requirements.

The Agency aims to rely on existing data fields and supporting documentation from ENTSO-E transparency platform. Further detailed information explaining all used data fields shall be available on [PM –insert/update relevant Weblinks after consultation:

https://www.entsoe.eu/publications/electronic-data-interchange-edi-library/edi-work-products-library/entso-e-net/

https://www.entsoe.eu/major-projects/common-information-model-cim/cim-for-energy-markets/

1 The Agency notes that Industry also uses the term ‘schedule’ to refer to ‘nomination’.

2 The Agency notes that in some European market rules additional ‘long term’ nominations exist in

accordance with local market rules such as weekly.


Draft Page 6 / 12

27/05/2014

https://www.entsoe.eu/major-projects/central-information-transparency-

platform/information-for-data-providers/

https://www.entsoe.eu/major-projects/central-information-transparency-

platform/manual-of-procedures/ ].

The Agency reserves the right not to update its systems for further schema’s releases and may continue to use existing standards as they are at the ARIS release date.


Draft Page 7 / 12

27/05/2014

4 POPULATING ELECTRICITY NOMINATIONS REPORTS

Electricity TSOs in the European Union shall provide the Agency fundamental electricity

transmission data related to Cross border nominations3 in line with Schedule Document format

IEC62325-451-2-schedule. We now explain data fields applicable and not applicable from the

used schema below.

3 The Agency notes that Industry also uses the term ‘schedule’ to refer to ‘nomination’.


Draft Page 8 / 12

27/05/2014

Field No Field Identifier Description (Definition) Remarks Agency

Schedule document header

NB: please note RED fields,those are not used from existing IEC format. Still the fields remain but do not need to be

filled or are considered optional.

NB: please note GREEN fields are for Clarification in standard and may

differ to wording in IEC Implementation guides.

1 Document identification Unique identification of the document for which the time series data is being supplied.

2 Document version Version of the document being sent. A document may be sent several times, each transmission being identified by a different version number that starts at 1 and increases sequentially

Adresses 'Lifecycle'-fields need by allowing to keep track of updates to

previosly provided information .

3 Document type The coded type of the document being sent.

4 Process type The nature of the process that the document is directed at.

See examples of current values.

Possible values are : A17 - Schedule day

A01 - Day ahead A02 - Intraday incremental

A12 - Long term A18 - Intraday total

A19 - Intraday accumulated depending on whether the reporting is made within a single reporting (LT / DA / ID at the end of day) or within several

reportings covering the day.

5 schedule classification type A type that is used to classify the schedule by aggregation or classification.

Code allowing to summarise eg per day transactions per trader, or all

nominations through day.

6 Sender identification Identification of the reporting party who is sending the document

EIC code for the reporting party. This is commonly expected to be a TSO.


Draft Page 9 / 12

27/05/2014

7 Sender role Identification of the role that is played by the sender.

The TSO reporting, for some countries potentially common system who deals

with it - such as Nordic and GB.

8 Receiving identification Identification of the organisation who is receiving the schedules. ACER

9 Receiver role Identification of the role played by the receiver.

ACER - REMIT; This refers to a role (describes a function)

10 Creation date time Date and time of transmission of the scheduling data.

This is the creation date and time of document, which indicated when the document was created. This is a key field, Agency considers important to

know when market participant submitted his/her nominations to the

TSO.

11 Schedule time interval The beginning and ending date and time of the period covered by the document containing the schedule.

This covers period, eg year or day.

12 Domain The domain covered within the Schedule Document.

Bidding zone. May help to guide where data belongs in ARIS.

13 Subject party (if applicable) The Party that is the subject of the Schedule Document.

In some countries 3rd party reports on behalf of TSO (like Elexon in GB; see

http://www.elexon.co.uk/about/other-services/data-flows/ ); optional field

14 Subject Role (if applicable) The Role of the Subject Party.

see field 13

15 Matching Period (if applicable)

The beginning and ending date and time of the period that is to be matched within the schedule.

Potentially this field specifies at which gate closure time this nomination was

sent (see field 10 - this allows to determine link to timing when

nomination was received by TSO)


Draft Page 10 / 12

27/05/2014

Schedule Timeseries

16 Senders time series ID Sender’s identification of the time series instance. This must be unique for the whole document and guarantee the non-duplication of the product, business type, object aggregation, in area, out area, metering point identification, in party, out party, capacity contract type and capacity agreement identification

Allows unique ID of this nomination. Similar to UTI in trades. Does not

function in isolation - this does not relate to reporting of data as such, but

is used for validation.

17 Senders time series version The time series version is changed only if a given time series has changed. The time series version must be the same as the document version number in which it has been added or changed. All time series, whether changed or not, must be retransmitted when a document is resent. In the case of the deletion of a time series, it is resent with all periods zeroed out.

Versioning belonging to updates of time series, allows to do data validation

and control.

18 Business type Identifies the trading nature of an energy product.

Possible codes include for example (not

exhaustive) : A03 - External trade explicit capacity A06 - External trade without explicit

capacity …

19 Product Identification of an energy product such as Power, energy, reactive power, transport capacity, etc.

Electricity.

Possible codes include for example (not exhaustive) :

8716867000016 - Active power …

20 Object Aggregation Identifies how the object is aggregated.

Default value: Per Party. Mainly aggregated per party for REMIT. So to specify that is BY PARTY; A03 is party


Draft Page 11 / 12

27/05/2014

21 In area (if applicable) The area where the product is being delivered.

E.g. from zone related to TSO A. Optional field - needs to be filled unless

Bidding zone affected is known from other reported field.

22 Out area (if applicable) The area where the product is being extracted.

E.g. frome zone related to TSO B. Optional field - needs to be filled unless

Bidding zone affected is known from other reported field.

23 Metering Point Identification (if applicable)

The identification of the location where one or more products are metered.

It is USED FOR DC (Direct current)- cables. FR-UK DC-cable nominations

could have use for such field. For DC links, it is sometimes used in

planning phase (nomination/matching process), and later used for imbalance

settlement accounting process. Field is used to differenciate the

delivery point.

24 In party (if applicable) The market participantthat is putting the product into the area.

To be reported as field; MP identified by EIC or ACER code. Key field allowing

to link through MP-ID to other monitoring information about that MP.

25 Out Party (if applicable) The market participant taking the product out of the area.

To be reported as field; MP identified by EIC or ACER code; Key field allowing

to link through MP-ID to other monitoring information about that MP. NB: note that there can be one to many nominations, in some countries. Those

would be split in several nomination files.

26 Capacity contract type (if applicable)

The contract type defines the conditions under which the capacity was allocated and handled.

27 capacity agreement ID (if applicable)

The identification of an agreement for the allocation of capacity to a market participant.

To be reported; Link to Transportation contracts - key information allowing to link data within ARIS to Transportation

data.

Please note that the link to transportation contracts is not always

possible with this field, because LT nominations can be made by the party

once for all the capacity acquired in several long-term allocations.


Draft Page 12 / 12

27/05/2014

28 Measurement unit The unit of measure which is applied to the quantities in which the time series is expressed.

MW (always; in accordance with Electricity Transparency regulation)

29 Curve type (if applicable) The coded representation of the type of curve being described.

To be reported field. BLOCK or Continuous. Example values.

Reason (if applicable)

30 Reason Code (if applicable) A code indication that a textual reason for modification will be provided in the reason text.

Would be Optional. For nominations this field would only be used in

exceptional circumstance by TSO denying nomin ations to MPs; example value 'Secutity curtailment' which only

applies when eg TSO rejects nominations.

31 Reason text (if applicable) Textual reason for a modification.

FREE TEXT, explaining 30. Limitation of allowed text size could be introduced.

Period

32 Time interval The start and end date and time of the time interval of the period in question.

In a pre-defined format. ISO 8601. See fields 33, 34, 35.

33 Resolution The resolution defining the number of periods that the time interval is divided.

ISO 8601. Hourly, 30 min or 15 min depending on market. Through EU

different granulatity of data is customary; key issue to manage in ARIS

for aggregation and analysis of data, with trading data.

Interval

34 Position The relative position of a period within a time interval.

Linked to field 32. Fields 34 and 35 define position and value, eg (1, 150),

eg ( 2, 250), eg (3,200). This would define eg that on Day X, in first hour, 150 MW would flow; in 2nd hour 250 MW flow, in 3rd hour 200 MW would

flow etc.

35 Quantity The quantity of the product scheduled for the position within the time interval in question.

NB: one will see that per 1 sender, in 1 file, multiple nominations, time series

can be provided.

Document title:

Publishing date: 02/07/2014

We appreciate your feedback

Please click on the icon to take a 5’ online surveyand provide your feedback about this document

http://www.acer.europa.eu/Lists/Survey/NewForm.aspx?documentid=ACER-2015-19612&Source=http%3a%2f%2fwww.acer.europa.eu

Document title: We appreciate your feedback · submitting the report to the reporting system. L...

Documents

Transcript of Document title: We appreciate your feedback · submitting the report to the reporting system. L...