Trader User Guide - Elia/media/files/Elia/Products-and-services/Crossborder2... · ACK Acknowledgement File ... message based interfaces. Trader Employee of a market ... unauthorized

©2016 – Deutsche Börse AG – All rights reserved. The information contained in this document is confidential or protected by law. Any unauthorized copying of this document or part of it or unauthorized distribution of the information contained herein is prohibited. All materials provided by DBAG in this context are and remain the intellectual property of DBAG and all rights therein are reserved.

Intraday Capacity Service

Trader User Guide

Version 1.0

Status FINAL

Deutsche Börse AG Version 1.0


Trader User Guide 08/01/2016

Page 2 of 47


Abbreviations

ACK Acknowledgement File

AMQP Advanced Messaging Queuing Protocol

ATC Available Transmission Capacity = NTC minus CAS and adjusted for

allocations executed on the Intraday Capacity Service platforms according

to the netting principle

BG Balancing Group

CATRINA Capacity Trading Interface Application

CEST Central European Summer Time

CET Central European Time

CSV Character/ Comma separated Values (file structure)

DBAG Deutsche Börse AG

DST Daylight Saving Time

ECAN ENTSO-E Capacity Allocation and Nomination System

EIC ENTSO-E-Identifications-Code-System

The EIC is based on fixed length alphanumeric codes: A 2-character

number identifying the Issuing Office assigned by ENTSO-E. One character

identifying the object type that the code represents. 12 digits, uppercase

characters or minus signs allocated by the issuing office and 1 check

character to ensure the code validity. Valid characters of an EIC code are

A-Z, 0-9 and “-“.

ENTSO-E European Network of Transmission System Operators for Electricity

GUI Graphical User Interface

HTML HyperText Markup Language

ICS Intraday Capacity Service, DBAG’s system to allocate power capacity

ID Identification/ Identity

IE / IE8 Microsoft Internet Explorer / Microsoft Internet Explorer Release 8

MW Megawatts

NTC Network Transfer Capacity

TIC Total Intraday Capacity

TSO Transmission System Operator – Company operating the main power grid

UTC Universal Time Coordinated

XML Extensible Markup Language




Page 3 of 47


Definitions

Administrator Employee of a TSO acting on the Intraday Capacity Service to administrate the

respective border(s).

BG Allocation The interconnection capacity is allocated according to the “first come – first serve”

principle. Only the time of capacity request is used to determine the allocation of

available capacity. A successful capacity request is an allocation.

BG Request Balancing Group Requests can be entered either manually via the GUI or

automatically via BG Request file upload. See also Capacity Request.

Capacity DBAG publishes available transfer capacity (ATC)

The computation and source of the available transfer capacity or offered capacity

is differentiated according to the transmission direction. The initial available

capacity or offered capacity is displayed as calculated from the capacity

information submitted by the respective TSOs :

- The ATC A->B is computed by DBAG based on the network transfer

capacity A->B (NTC = total transfer capacity) and CAS files.

- The ATC B->A is computed by DBAG based on the network transfer

capacity (NTC = total transfer capacity) B->A.

Allocations submitted by a balancing group will reduce the available capacity in

the direction of the transfer and increase the available capacity in the counter-

direction (with netting enabled).

Capacity Request A Capacity Request is the act of requesting permission to physically transfer a

specific amount of power (in MW) over the grid for a specific product and

direction. A capacity request may be entered either manually via the GUI or via

the BG Request file upload (see also BG Request). Capacity requests for more

than one Contract may be submitted at the same time.

Contract A Contract is defined as the Contract Delivery Period.

Contract Allocation

Period

The Contract Allocation Period is a defined period during which capacity can be

requested with regard to a contract.

Contract Delivery Period The Contract Delivery Period is the period between start and end time during

which power is physically transmitted.

Contract Status A contract can have the following states

Delivery = a contract is in the Delivery Period

Inactive = before and after the Contract Allocation Period

Active = a contract is in the allocation period - differentiated between

Allocation: Capacity requests can be entered

HALT: Capacity requests cannot be entered

Product A Product (border) describes the cross-border capacity between two control areas.

It includes allocations in both directions.

Technical User Account for a user to connect to the Intraday Capacity Service through the

message based interfaces.

Trader Employee of a market participant acting on the Intraday Capacity Service to

allocate capacity.

User Account of an individual person (trader) who acts in the Intraday Capacity

Service.




Page 4 of 47


Table of Contents

1. Introduction 6 1.1 Parameters on the French Belgian Border 7

2. Functional overview 9 2.1 Upload of capacity information 9 2.2 Calculation and publication of available capacity 9 2.2.1 NTC/CAS-Approach 9 2.2.2 Publish capacity 10 2.3 Allocation of capacity by traders 10 2.4 Gate closure and communication of allocated capacity 10 2.5 User and user roles 10 2.5.3 Trader 11 2.5.4 Technical user 11 2.6 Prerequisite: Trader registration 11 2.7 Single login 12 2.8 Login with wrong password 12 2.9 Logout 13

3. Technical overview 14 3.1 Client 14 3.2 Preconditions – Internet browser settings 14 3.3 Certificates installation 16 3.3.1 How to install certificates with MS Internet Explorer (Version 7-9) 16 3.3.2 How to install certificates with Mozilla Firefox (Version 3+) 19 3.3.3 Trouble shooting 21 3.4 Session sharing with IE8 and Firefox 22

4. Intraday Capacity Service web portal 25

5. Functional Overview - Trading GUI (Balancing Groups) 27 5.1 Menu bar 27 5.2 Capacity overview 29 5.2.1 Column #1: Avbl. Capacity: 30 5.2.2 Column #2: Act. RCA/Right 30 5.2.2.1 Act RCA 30 5.2.2.2 Rights: 31 5.2.3 Column #3: Request: 31 5.2.4 Column #4: New RCA: 31 5.2.5 Column #4: New Right: (OC-Approach): 31 5.2.6 Column #5: TIC: 31 5.2.7 Capacity overview buttons 31 5.3 Messages 33

6. Reports 34

7. Trader Files 36 7.1.1 BG Request file 36 7.1.1.1 BG Request XML-Schema 36 7.1.1.2 BG Request file structure in CSV 40 7.1.2 BG Allocation file 40




Page 5 of 47


7.1.2.1 BG Allocation XML-Schema 40 7.1.2.2 BG Allocation file structure in CSV 44 7.2 File adaptations regarding switch to daylight saving time 45

8. CATRINA – Capacity Trading Interface Application 47




Page 6 of 47


1. Introduction

Intraday Capacity Service enables transmission system operators (TSO’s) to provide cross-

border capacity timely – including the fulfilment of the EU directive on interconnection

capacity. The application designs the entire processes for explicit and implicit allocation of

cross-border capacity considerably more straightforward and efficient. For example:

Electronic interfaces transfer capacity information from the TSOs automatically

Transfer of capacity allocations for market participants and TSO’s – based on the

ENTSO-E standard – are generated and transferred automatically.

The service provides the

TSOs in their role as administrators with a service for the allocation of intraday

cross-border grid capacity, thus helping to fulfil the EU directive on interconnection

capacity.

Market participants in the role of traders with a facility for making short-term

adjustments to their physical requirements by requesting explicit capacity.

Power exchanges in their role to operate cross-border energy market places to

allocate short-term capacity implicit with the matching of cross border trades.

Intraday Capacity Service enables the

support of multiple borders: each border with separate configuration and

administration to fit in with border-specific functionality

reservation of cross-border capacity up to gate closure: configurable per border

request of whole hours and blocks of whole hours – according to the hours of the

day: with configurable time units per border

request of capacity for all the hours of the next day at a specific time each day:

configurable per border

As a web-based solution Intraday Capacity Service does not require installation of specific

software. TSO’s and traders need only a standard internet browser to allocate cross-border

capacity continuously and anonymously – 24 hours a day, 7 days a week. In addition,

traders can use the CATRINA interface for application to application communication for

continuous, anonymous allocation of cross-border capacity.

Intraday Capacity Service provides traders via web-based GUI with the following functionality

to reserve cross-border capacity on dedicated borders via responsible TSO’s:

Overall picture of available capacity

Allocate capacity

Reporting depicts activities, all changes of available capacities and messages




Page 7 of 47


1.1 Parameters on the French Belgian Border

The aggregated interconnection capacity on the Belgian – French border includes the values

between the Belgian TSO Elia and the French TSO RTE.

The Intraday Capacity Service displays the available transfer capacity (ATC) for both

directions: BE->FR and FR->BE.

Parameter Configuration

RTE Long Name Réseau de Transport d’Electricité

Elia Long Name Elia System Operator

Contract Trading Start (border

opening) on day before delivery

day:

09:05 pm CET / CEST

Contract Trading End

Prior to delivery:

60 min.

Decimal places (.) displayed on

GUI for unit (always in MW)

Yes. 1 decimal place

Smallest Unit (MW)

(Request, manual ATC)

0.1

Max Qty. per Request via the GUI

in MW

999.9




Page 8 of 47


All screenshots in this document serve as illustrative examples

and may be subject to minor changes.




Page 9 of 47


2. Functional overview

Intraday Capacity Service is designed to allocate cross-border interconnection capacity for

power.

The capacity lifecycle of the capacity allocation process consists of the following steps in the

presented order:

1. Upload of capacity information

2. Calculation and publication of available capacity

3. Start allocation of capacity by intraday power trading users when border

opens

4. Gate closure and communication of allocated capacity

The capacity allocation process does not include the nomination with the TSOs by the

Capacity Service. Capacity that is allocated will be automatically nominated by the TSOs on

behalf in the balancing perimeter of the Traders to whom capacity was allocated.

The next sections describe the steps mentioned above in more detail.

2.1 Upload of capacity information

Capacity information has to be made available to the Intraday Capacity Service by the

responsible TSO. The TSO in charge of managing the respective border (operating TSO)

uploads information to Intraday Capacity Service.

2.2 Calculation and publication of available capacity

Once the necessary information has been uploaded to the Intraday Capacity Service by the

responsible TSO, the actual ATC is calculated and published. Publication in this case means

providing the market with the information on the portal, the Trading GUI and through

CATRINA.

The following two sections describe how the ATC values are calculated.

2.2.1 NTC/CAS-Approach

The aggregated interconnection capacity for a defined border contains the available Network

Transfer Capacity (NTC) reduced by already reserved capacity for long term allocations in the

Control Area Schedule (CAS) file(s). The Available Transfer Capacity (ATC) values are

published by the TSOs which are the operators of the control areas on the French Belgian

border.

The ATC for a direction based on NTC and CAS files is computed as follows:

ATC A->B = NTC A->B - CAS A->B + CAS B->A - Intraday Allocations A->B – BM/Genoutage A->B +

Intraday Allocations B->A [with netting enabled]




Page 10 of 47


ATC B->A = NTC B->A - CAS B->A + CAS A->B - Intraday Allocations B->A – BM/Genoutage B->A +

Intraday Allocations A->B [with netting enabled]

The Intraday Capacity Service displays the ATC for both directions per border.

2.2.2 Publish capacity

During the publishing process, Intraday Capacity Service calculates the ATC by subtracting

the values in the CAS file from the values in the NTC It furthermore publishes the ATC and

the actual RCA values.

2.3 Allocation of capacity by traders

Once the ATC is published and the border is opened, meaning the time of the gate opening

is reached, the allocation process starts.

Traders who are entitled and registered by the TSO to allocate on a specific border may

allocate capacity according to their needs and as far as there is capacity available.

The interconnection capacity is allocated according to the “first come – first serve” principle.

Only the time of the request is used to determine the priority of the allocation of available

capacity. There is no allocation based on price.

Each capacity request receives a timestamp upon receipt by the application server. No two

requests can receive the same timestamp.

The ATC is updated and will be displayed to all the users and the allocation process may

continue until gate closure.

2.4 Gate closure and communication of allocated capacity

The allocation process ends with gate closes. This is a defined point in time prior to delivery

of the contract. Traders may download their allocations as a consolidated file via the Trading

GUI.

2.5 User and user roles

The Intraday Capacity Service supports different user roles for the connection to the service

via the GUIs and the electronic interfaces. A user is an individual person or technical

connection acting in the Intraday Capacity Service. The different user roles and

responsibilities are described in the following sections.




Page 11 of 47


2.5.3 Trader

A trader is responsible for capacity allocation requests within Intraday Capacity Service. This

user can allocate capacity between two control areas for authorised products.

2.5.4 Technical user

A technical user is required to connect to the Intraday Capacity Service using the electronic

message interface (e. g. CATRINA). The technical user is necessary for security and privacy

reasons.

2.6 Prerequisite: Trader registration

The service supports multiple borders (products) and the corresponding assignment on user

level. Each trader needs to be registered with a balancing group for each border at each side

to request capacity. A balancing group is identified with a unique EIC code.




Page 12 of 47


2.7 Single login

Single login restricts each authorized Intraday Capacity Service user to login to the service

one time per login ID. If a user is already logged into the Intraday Capacity Service with a

login ID, a second login attempt with the same ID will only be successful once the first login

session has been terminated, or thrown out with this login attempt.

In such a situation the following dialogue window is displayed. If the second user decides to

continue, the first user will be logged out.

Figure 1 - Single login dialogue window

2.8 Login with wrong password

A password can be entered incorrectly twice. After entering the wrong password for the third

time, a screen showing “Access to the application was denied” is displayed. However, the

password has not been revoked yet. In order to login again:

1. Close the browser

2. Open the browser again,

3. Enter the login ID and password, correctly.

The user now has two more chances to enter the login ID and password correctly. If the

login ID and password are entered incorrectly two more times, the password will be revoked

and the account has to be reset in order for the user to login again. Intraday Capacity Service

displays the following screen:




Page 13 of 47


Figure 2 – Account has been revoked

2.9 Logout

When finished with an Intraday Capacity Service session, the user can log out selecting the

menu item Logout” from the tab File in the task bar (see screenshot below).

Figure 3 - Logout possibility

A window then pops up, asking the user “Do you really want to logout?”.

Clicking on “Yes” will lead the user to a page stating “You have been logged out

successfully”.The user is now successfully logged out.

After closing the browser window the user can log in again, starting a new (single) user

session.

Clicking on “No” will close the logout dialog window. The user is redirected back to Intraday

Capacity Service.




Page 14 of 47


3. Technical overview

The Intraday Capacity Service is implemented using web-based client server architecture.

Standard access to the Service is provided with a web-browser (Internet Explorer or Firefox)

via an internet connection. Regardless of the connection type, the users are not required to

install any additional software specific to the service except for the user certificate.

3.1 Client

Traders use a standard web-browser (Internet Explorer, Firefox) to connect via HTTPS-

protocol to the Intraday Capacity Service. Login, Password and a qualified user certificate is

used for authentication.

3.2 Preconditions – Internet browser settings

The access to Intraday Capacity Service is browser-based and only requires an Internet

connection with an Internet browser. No application software needs to be installed locally on

the user’s PC. When starting an Internet connection to the Intraday Capacity Service the

browser opens an encrypted SSL connection to the service. The speed of the internet

connection should be at least 128 kb/sec.

When using Internet Explorer, the ActiveX component should be activated.

In order to enable this:

Open the Internet Options window,

Select the “Security” tab and

Enter the Intraday Capacity Service’s Internet address as a trusted site.




Page 15 of 47


Then, modify the custom settings by clicking the Custom Level button, this will open the

Security Settings window where the user needs to enable the following settings:

Download signed ActiveX controls

Download unsigned ActiveX controls

o Run ActiveX controls and plug-ins

o Script ActiveX controls marked safe for scripting

o File download

o Active Scripting




Page 16 of 47


3.3 Certificates installation

Intraday Capacity Service requires an advanced electronic signature which obliges all users

to install a user certificate into their Internet browser before login. All users of Intraday

Capacity Service can only login with a successfully installed certificate.

3.3.1 How to install certificates with MS Internet Explorer (Version 7-9)

1. Double-clicking on the certificate icon will open the Certificate Import

Wizard. Click on Next.

2. The path of your certificate will be visible in the input field. Click on Next.




Page 17 of 47


3. Enter the password in the .txt file provided to you in an email by your TSO. You do

not need to check the two check boxes below. Click on Next.

4. Select the certificate store. In case of doubt select "Automatically select the ...".

Click on Next.

5. Completion – Click on Finish.




Page 18 of 47


6. Only for Windows 7: Security Warning opens. After clicking on Yes the certificate will be

installed successfully.

7. Import of certificate was successful.




Page 19 of 47


3.3.2 How to install certificates with Mozilla Firefox (Version 3+)

1. Open Firefox.

2. Click on menu "Tools"-> "Options".

3. Click on the last Icon "Advanced".

4. Select Tab "Encryption".

5. Click on "View Certificates".

6. Certificate Manager opens. Click on Import.

7. Browse to the location of your Certificate, select it and click on Open.




Page 20 of 47


8. Enter the password provided to you in the .txt file by email and click on Ok.

9. Finish.




Page 21 of 47


3.3.3 Trouble shooting

Problem Reason Solution

If clicking on Login, in the Intraday Capacity

Service web portal, shows “ The page cannot be

displayed”:

1.

The certificate

is not correctly

installed into

the Internet

Browser.

2.

A wrong

certificate has

been selected.

1.

Please install the user

certificate into your

Internet Browser.

2.

Please close ALL open

Internet Browser

windows, click on Login

on the Intraday Capacity

Service web portal and

select the correct

certificate

If encountering problems when logging in with

Windows 7:

Certificate

handling of

Windows 7.

Do not log in from


portal but directly from

the following path:

https://www.intraday-

capacity.com/capacity-

allocation

If encountering any other problems with user

certificate:

Full SSL State Clear SSL State in your

Internet Browser under

Tools->Internet Options-

>Content->Clear SSL

State

Please note: For Mozilla Firefox versions 4.x and 5.x it is necessary to set the parameter

“security.ssl.allow_unrestricted_renego_everywhere__temporarily_available_pref” to the

value “true”. This parameter can be modified if the command “about:config” is entered as

URL in the browser.




Page 22 of 47


3.4 Session sharing with IE8 and Firefox

Microsoft Internet Explorer 8 has implemented a feature change where multiple open

browser windows or frames share the same session cookies across all open tabs and

windows. This includes any new IE frame windows opened by double clicking the blue E

shortcut icon or by using the New Window command in the menu bar (Ctrl-N keyboard

shortcut). This means that all logins and logouts will automatically be reflected and affected

on all other IE8 windows.

The change was introduced from IE8 Beta 2 to merge frame processes, with just one frame

process for all windows that contain tabs on the launch of IE. All subsequent launches will

only start a new tab process or make a new tab in an existing tab process.

As a workaround, Microsoft provides a -nomerge switch parameter for IE8 executable. With

the -nomerge switch, which is also trigger able via “New Session” in menu bar, IE8 default

behavior will be overridden and it will start each new browser window in a new, unique and

separate frame process, and session. The “nomerge” setting can be used as a workaround to

login to multiple user accounts on the same web service.

So, in order to have multiple concurrent logins to a web application, load a new instance of

the IE8 web browser by using one of the following three methods.

1.) Method 1: New Session

In an existing IE8 web browser window, go to File-drop down menu, and then select “New

Session”.




Page 23 of 47


2.) Method 2: -nomerge Switch for iexplorer.exe

To start a separate session IE8 browser frame, type the following at Start Search, Run

command box or in Command Prompt: iexplore.exe -nomerge

Please note: You may have to change directory (cd) to …ProgramFiles\Internet

Explorer\folder if the path is not defined in command prompt and/or Run command box.

3.) Method 3: Modify IE8 Shortcut to Permanently Launch New IE Browser Window in New

Session

Right click on the IE8 shortcut (all IE8 shortcuts or icons on desktop, Start Menu, Quick

Launch bar or Taskbar that you want it to run as a new instance session have to be

changed), and choose Properties from the right click context menu. Append -nomerge to the

end of the of the program path in the “Target” text box on the “Shortcut” tab.

Please note: Mozilla Firefox windows or frames share the same session cookies across all

open tabs and windows analogue to MS IE8.




Page 24 of 47


In Firefox 2 and above, you can use the -no-remote command line option to start a new

Firefox process that is invisible to the first process. By using -no-remote along with the -P

option to select a different profile, you can open multiple instances of Firefox at the same

time, using separate profiles. Selecting a different profile from the one used in the first

process is necessary because profiles are "locked" when in use.

Important: Never use -no-remote to start the "default" profile (the one that is set to open

without asking when you launch Firefox) as this will result in an error message stating that

Firefox is already running but is not responding when launching Firefox, for example, by

clicking a link in your mail program, if the default profile is already in use. The solution is to

always start the default profile normally and launch all others with -no-remote.

Example (path can be different):

"C:\Program Files\Mozilla Firefox\Firefox.exe" -P "My Profile" -no-remote




Page 25 of 47


4. Intraday Capacity Service web portal

The Intraday Capacity Service can be accessed via https://www.intraday-capacity.com which

directs the user to the entry page of the Capacity Portal. The Capacity Portal webpage is

layered into six main sections. They can be accessed by clicking on the menu items on the

tab bar at the top.

The portal of ICS is updated once every 5 min. (update data can have 2-3 min. delay) in

general.

1. Start: A map of central Europe displays the respective interconnectors. By clicking

on the arrow of an interconnector or by clicking on the product tabs to the left of the

map the respective ATC values table is displayed on the left of the map (negative

values are displayed as zero values). The timestamp of the latest refresh is below

the ATC value table. On the bottom of the entry page is the disclaimer.

2. Login: Opens the login dialog window for users with an installed certificate.

3. ATC Archive: ATC values archive: Last values of ATCs for these contracts of the day,

downloadable into a CSV file for the past 31 days.

4. News Archive: Portal news messages archive: Downloadable into a CSV file for the

past 180 days.

5. Impressum & Contacts: Impressum and contact information; disclaimer at the

bottom.

6. Latest News: Portal news panel with latest five news messages (truncated to 100

characters), displayed with date, time and product stamp.

After the successful trader login the trader GUI opens automatically.




Page 26 of 47


Figure 4 – Intraday Capacity Service Portal




Page 27 of 47


5. Functional Overview - Trading GUI (Balancing Groups)

After successful user login, the Trading GUI opens automatically. If login messages are

available, the user will receive a pop-up window (please refer to chapter 6.4). The Intraday

Capacity Service Trading GUI window is divided into 3 panels Menu Bar , Capacity

Overview and Messages as shown in the following example:

Figure 5 - Example of Intraday Capacity Service Trading GUI

Menu Bar

File

Change Password

Logout

Product

TSO

Reports

Help

Reload

Capacity Overview

Messages

5.1 Menu bar

The Intraday Capacity Service Menu bar has the items File, Product, TSO, Reports, Help

and Reload. It also displays the selected trader’s balancing group (the EIC code) and the

selected TSO.

The menu item File allows the trader to change the password and to logout.

1

2

3




Page 28 of 47


The menu item Product allows the trader to switch to another product. The product list only

displays products for which the trader’s balancing group is registered.

The menu item TSO, allows the trader to switch to another TSO if the balancing group is

registered with more than one TSO area. The selected TSO is displayed in the right corner of

the menu bar next to the trader’s balancing group.

The menu item Reports allows the trader to download traders` messages report for the

current day (today) -2 days. For details please see chapter 6 Reports.

The menu item Help provides the trader with the information about the current software

version in production.

The menu item Reload allows the trader to updated Intraday Capacity Service window by

clicking “Reload” on the menu bar. The window is only updated by clicking the button

“Reload” on the menu bar.

The trader’s balancing group is displayed to the left of the label “TSO” on the menu bar.




Page 29 of 47


5.2 Capacity overview

There are two tabs in the Capacity Overview window, one for the current day (today) and

one for the next day (tomorrow). When the calendar days change, the tabs switch to the new

days (current and next). This is a time-driven event.

Figure 6 – Example for Capacity Overview window

The columns in the Capacity Overview display the following information:

A->B B->A

Column # 1 2 3 4 5 1 2 3 4 5

Time

(Contracts)

Status

Symbol

Avbl.

Capacity

A->B

Actual

RCA

A->B

Request

A->B

Manual

entry field

New RCA

A->B

Projected

RCA after

pressing

Update

TIC

A->B

Allocated

capacity) in

intraday only

Avbl. Capacity

B->A

Actual

RCA

B->A

Request

B->A

Manual

entry field

New RCA

B->A

Projected

RCA after

pressing

Update

TIC

B->C

Allocated

Capacity

in intraday only)




Page 30 of 47


Each column of the Capacity Overview window displays the following information and is

product specific:

Time

Status Icons (status of contract)

Available Capacity

Actual RCA / Actual Right (for each direction)

Request (for each direction)

New RCA / New Capacity (for each direction)

TIC (for each direction)

The column Time displays all contracts, which have not been delivered yet and which are in

delivery, for the selected date. Inactive capacity allocation periods are disabled (a respective

icon is shown and input is no longer possible in the requested columns).

The following status icons display the contract status:

Active contract.

Active but currently in HALT (Service HALT / Contract HALT) or

Inactive contract after delivery period.

Inactive contract currently being delivered.

Inactive contract before delivery.

Capacity for a specific capacity allocation period can only be requested for a limited period

of time, this time period is called the contract allocation period. Capacity can only be

requested by traders for contracts which are active and not in HALT.

Traders can allocate capacity for contracts until a configurable time before the contract

delivery.

5.2.1 Column #1: Avbl. Capacity:

The available transfer capacity is calculated by the Intraday Capacity Service and is

displayed in the columns #1 Avbl. Cap. The available transfer capacity is updated in real-

time. The label in the column header displays the selected product and direction.

5.2.2 Column #2: Act. RCA/Right

5.2.2.1 Act RCA

In the column #2 Act. RCA, the total capacity of the balancing group is shown which has

already been allocated (e.g. allocations taken from the CAS files sent by the TSO). The label

displays the selected product and direction. This value contains the capacity from the CAS

which has been uploaded by the TSO plus (+) any capacity allocated via a request to the

Intraday Capacity Service.




Page 31 of 47


5.2.2.2 Rights:

In the column #2 Act. Right, the total capacity which has been allocated intraday to all the

balancing groups by the Intraday Capacity Service is shown. The label displays the selected

product and direction.

5.2.3 Column #3: Request:

In the columns#3 Request, additional capacity can be requested for each active contract

and direction by manually entering values into the entry fields. The label in the column

header displays the selected product and direction.

5.2.4 Column #4: New RCA:

The columns #4 New RCA display the projected total allocated capacity in MW for the

trader’s balancing group (sum of the columns Actual RCA and Request) after having

manually entered values into column #3 Request and having clicked on the button

“Update”. The label in the column header is dependent on the selected product and

direction.

5.2.5 Column #4: New Right: (OC-Approach):

The columns #4 New Right display the projected total capacity allocated intraday in un-

netted values in MW for the trader’s balancing group (sum of the columns Act. Right and

Request) after having manually entered values into column #3 Request and having clicked

on the button “Update”. The column will contain the same value as the TIC column after

pressing the submit button (if the capacity is allocated). The label in the column header is

dependent on the selected product and direction.

5.2.6 Column #5: TIC:

The columns #5 TIC A->B and TIC B->A show the allocated capacity for the trader’s

balancing group only in Intraday Capacity Service (via web-based application or interfaces)

per direction without netting.

5.2.7 Capacity overview buttons

With the “Import” button the user can upload a BG Request file (in XML or CSV format)

containing new capacity requests for both directions of the selected product. Upon

successful upload the requests will be automatically processed according to the same

principles as the “Submit” button (and not “Submit AON”).

The allocated capacity in each direction (columns Actual RCA / Actual Right) for the trader’s

balancing group, the selected TSO and product can be downloaded for the selected day

(according to the active tab) by the user with the “Export” button. This file is called the BG

Allocation file.




Page 32 of 47


With the Button “Update” the user can re-inquire the current available transfer capacity and

refreshes the columns Avbl. Cap. and New RCA.

The “Reset” button clears all entries in the “Request” fields (fields are set to blank) and

updates the columns Avbl. Cap. and New RCA / New Right.

Capacity is requested by clicking the “Submit” button. If the “Submit” button is used, the

user gets the requested capacity as far as it is available for each individual contract. If the

available capacity for a contract is less than the requested capacity, the requested volume

can not be fully executed, however all available capacity will be allocated.

The “Submit AON” (All or Nothing) button is used, if the user wants to get all requested

capacity in all requested contracts or no capacity at all (All or Nothing).

For example: If 20 MW are available, but the user requests 30 MW

via the “Submit” button: the user will only get 20 MW, or

via the “SUBMIT AON” button: the user will get nothing.




Page 33 of 47


5.3 Messages

In the Messages panel, the user is informed about activities and changes on the Intraday

Capacity Service. The messages can be triggered by the service, the administrator, the user

or another user of the same balancing group. The window displays up to 25 messages at the

same time.

Figure 7 - Messages panel




Page 34 of 47


6. Reports

The menu item Reports on the menu bar allows users to download reports on demand. All

reports are border-specific.

Figure 8 - Reports Download item

Message reports can be downloaded by traders for the current calendar day and up to 2

calendar days. The Message Report lists all messages of the trader’s Balancing Group for the

assigned product and all public messages. The timestamp in the footer and next to each

message is CET.

The user can choose the start / end dates via pull down. The columns ID and Name

specify the type of report.

Figure 9 – Download Reports dialog window – user role: Trader

The button “Close” closes the report dialog window.




Page 35 of 47


Sample Messages Report:

Figure 10 Sample Messages Report




Page 36 of 47


7. Trader Files

7.1.1 BG Request file

With the “Import” button on the Trading GUI, a user can upload a Balancing Group Request

file (in XML or CSV format) containing capacity requests for the balancing group.

Balancing Mechanism requests are also supported and can be imported via a BG Request

file.

A popup appears asking the trader to search for that file. After the right path to the file is

displayed, the trader can start or cancel the procedure by pressing OK or Cancel.

The file name of the imported file is assigned by the Balancing Group and is not validated by

the service.

7.1.1.1 BG Request XML-Schema

XML-Tags m/o Data Type No. Short Description/Comment

AuctionMessage m structure 1 Defines the XML-schema version and release.

-DtdRelease=”0”

-DtdVersion=”1” DocumentIdentification o 35

alphanumeric

1 Unique identification of the document for

which the time series data is being supplied.

Not mandatory, any desired string. DocumentType m 3

alphanumeric

1 The document type identifies the information

of the document.

ICS expects the value:

X04=Intraday request DocumentVersion m 3 numeric 1

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.

Version number (integer): 1-999

Note: Has to be higher than already uploaded

file during a calendar day. DocumentProcessType m 3

alphanumeric

1 Indicates the nature of process that the

schedule addresses.


A01=Day ahead DocumentClassification

Type

m 3

alphanumeric

1 A type that is used to classify the document by

aggregation or classification.




Page 37 of 47




A01=Detailed Type DateOfDocumentCreati

on

m 20

alphanumeric

1 The date and time must be expressed in UTC

as YYYY-MM-DDTHH:MM:SSZ.

e.g. 2011-10-05T13:00:00Z SenderIdentification m 16

alphanumeric

1 Identification of the party who is sending the

document (BG-User, which imports the file).

codingScheme=”A01”

A01=EIC (Preferred)

The coding scheme for the preceding attribute

is the Energy Identification Coding Scheme

(EIC), maintained by ENTSO-E.

SenderRole m 3

alphanumeric

1 Identification of the role that is played by the

sender.


A01=Balancing Group participant ReceiverIdentification m 16

alphanumeric

1 Identification of the party who is receiving the

document.


A01=EIC (Preferred)



(EIC), maintained by ENTSO-E. ReceiverRole m 3

alphanumeric


receiver.

ICS expects the values:

A07=Transmission capacity allocator AuctionTimeInterval m 35

alphanumeric

1 The beginning and ending date and time of the

period covered by the document.

The start and end date and time must be

expressed as YYYY-MM-DDTHH:MMZ/YYYY-

MM-DDTHH:MMZ. The time must always be

expressed in UTC.

e.g. v="2011-11-11T23:00Z/2011-11-12T23:00Z"

AuctionTimeSeries m structure 2 Object used for the transmission of specific

time series. A time series may be considered

as a sequence of observations of a single

process taken at equal time intervals.




Page 38 of 47



AuctionTimeSeriesI

dentification

m 35

alphanumeric

1 The identification of the time series instance.

This must be a unique number that is assigned

by the auction office for each time series in the

document

Will be ignored by Intraday Capacity Service.

All Information about TSO, BG, Border will be

extracted from InArea, OutArea, InParty,

OutParty, etc. BusinessType m 3

alphanumeric

1 The exact business nature identifying the

principal characteristic of a schedule time

series.


Y09=Intraday request Product m 13 numeric 1 The identification of the nature of an energy

product such as power, energy, reactive

power, etc.

8716867000016=Power ObjectAggregation m 3

alphanumeric

1 ICS expects the value:

A01=Area InArea m 18

alphanumeric

1 The Area where the energy is to be delivered.


A01=EIC (Preferred)



(EIC), maintained by ENTSO-E. OutArea m 18

alphanumeric

1 The Area where the energy comes from.


A01=EIC (Preferred)



(EIC), maintained by ENTSO-E. InParty m 16

alphanumeric

1 The identification of the party of concern.


A01=EIC (Preferred)




In-/OutParty code dependent of the BG nation

- EIC for German BGs




Page 39 of 47



- EAN for Dutch BGs

OutParty m 16

alphanumeric



A01=EIC (Preferred)





- EIC for other BGs MeasureUnit m 3

alphanumeric

1 The unit of measure that is applied to the

quantities in which the time series is

expressed.


MAW=Mega watt Period m Structure 2 Object used to identify the period that the

interval quantities cover and the resolution of

each step within the period. TimeInterval m 35

alphanumeric

1 The start and end date and time of the time

interval of the period in question.


expressed in compliance with the following

format: YYYY-MM-DDTHH:MMZ/YYYY-MM-

DDTHH:MMZ.

E.g. v="2011-11-11T23:00Z/2011-11-

12T23:00Z"

The time must always be expressed in UTC. Resolution m 35

alphanumeric

1 Defines the number of units of time that

compose an individual step within a period.


PT15M=Quarter-hourly contracts (15 min.) Interval m structure 96 Object used for the transmission of each

individual period and its associated quantity.

On summer- and the winter-time change there

will be 92 (23 hours day) and 100 (25 hours

day) intervals. Pos m 6 numeric 1 This information provides the relative position

of a period within a tender interval. Qty m 17 numeric 1 This information defines the quantity that is

tendered for the interval in question and that is

expressed in the Measurement Unit Quantity.




Page 40 of 47



Quantity: < 999 MW will be ignored!

7.1.1.2 BG Request file structure in CSV

The BG Request file can also be uploaded as CSV format. The CSV format is structured:

Header: MessageVersion;[Version Number]

OutArea;[EIC/EAN-Area code of TSO A];[EIC/EAN-Area code of TSO B]

InArea;[EIC/EAN-Area code of TSO B];[EIC/EAN-Area code of TSO A]

Party;[EIC/EAN-code of balancing group who requests capacity]

Body: Column 1: [Contract (Date and Time)];

Column 2: [Value for direction A->B];

Column 3: [Value for direction B->A]

7.1.2 BG Allocation file

The Balancing Group Allocation file can be exported online from the Trading GUI by the user

as XML or CSV. They are offered to the balancing group user with the capacity allocations for

the own balancing group and the currently assigned TSO.

The files are created

Per Balancing Group

Per assigned TSO

Per calendar day

7.1.2.1 BG Allocation XML-Schema

Filename: <YYYYMMDD>_AIR_<BG_user[EIC Code]>_<Auctionskoordinator[EIC

Code]>_<Version number>_RESULT_<yyyy-mm-ddThh-mm-ssZ>

<YYYYMMDD> = Date of delivery

<VVV> = Version Number of file is equal to the Document Version of the Capacity

Request file.

<yyyy-mm-ddThh-mm-ssZ> = Date and Time of document creation




Page 41 of 47



AuctionResultMessage m structure 1 Defines the XML-schema version and release.

-DtdRelease=”0”

-DtdVersion=”1” DocumentIdentification o 35

alphanumeric

1 The value will be filled with ”Handeingabe”.

DocumentType m 3

alphanumeric

1 Document Type of the last imported Capacity

Request file.

The value will be filled with ”XXX”. DocumentVersion m 3 numeric 1

Document Version of the last imported

Capacity Request file.

The value will be filled with ”XXX”. DocumentProcessType m 3

alphanumeric

1 Indicates the nature of process that the

schedule addresses.


A01=Day ahead DocumentClassification

Type

m 3

alphanumeric

1 A type that is used to classify the document by

aggregation or classification.


A01=Detailed Type DateOfDocumentCreati

on

m 20

alphanumeric

1 The date and time must be expressed in UTC

as YYYY-MM-DDTHH:MM:SSZ.

e.g. 2011-10-05T13:00:00Z DocumentStatus m 3

alphanumeric

1 The coded status of the document being sent.

SenderIdentification m 16

alphanumeric

1 Identification of the party who is sending the

document (BG-User, which imports the file).


A01=EIC (Preferred)



(EIC), maintained by ENTSO-E. SenderRole m 3

alphanumeric


sender.


A07=Transmission capacity allocator ReceiverIdentification m 16

alphanumeric

1 Identification of the party who is receiving the

document.


A01=EIC (Preferred)




Page 42 of 47






BG-user, which exports the file - always equal

to the rights holder ReceiverRole m 3

alphanumeric


receiver.


A01=Balancing Group participant AuctionTimeInterval m 35

alphanumeric

1 The beginning and ending date and time of the

period covered by the document.


expressed as YYYY-MM-DDTHH:MMZ/YYYY-

MM-DDTHH:MMZ. The time must always be

expressed in UTC.

e.g. v="2011-11-11T23:00Z/2011-11-12T23:00Z" AuctionTimeSeries m structure 2 Object used for the transmission of specific

time series. A time series may be considered

as a sequence of observations of a single

process taken at equal time intervals. AuctionTimeSeriesI

dentification

m 35

alphanumeric

1 The identification of the time series instance.

This must be a unique number that is assigned

by the auction office for each time series in the

document

Will be ignored by Intraday Capacity Service.

All Information about TSO, BG, Border will be

extracted from InArea, OutArea, InParty,

OutParty, etc. AuctionTimeSeriesV

ersion

m 3 numeric 1 The same as BG-Request document version

BusinessType m 3

alphanumeric

1 The exact business nature identifying the

principal characteristic of a schedule time

series.


Y04=Capacity Min

Y05=Capacity Max

Product m 13 numeric 1 The identification of the nature of an energy

product such as power, energy, reactive

power, etc.

8716867000016=Power ObjectAggregation m 3 1 ICS expects the value:




Page 43 of 47



alphanumeric A01=Area

InArea m 18

alphanumeric

1 The Area where the energy is to be delivered.


A01=EIC (Preferred)



(EIC), maintained by ENTSO-E. OutArea m 18

alphanumeric

1 The Area where the energy comes from.


A01=EIC (Preferred)



(EIC), maintained by ENTSO-E. InParty m 16

alphanumeric



A01=EIC (Preferred)





(EIC or EAN code) OutParty m 16

alphanumeric



A01=EIC (Preferred)





- EIC for German BGs MeasureUnit m 3

alphanumeric

1 The unit of measure that is applied to the

quantities in which the time series is

expressed.


MAW=Mega watt Period m Structure 1 Object used to identify the period that the

interval quantities cover and the resolution of

each step within the period. TimeInterval m 35 1 The start and end date and time of the time




Page 44 of 47



alphanumeric interval of the period in question.


expressed in compliance with the following

format: YYYY-MM-DDTHH:MMZ/YYYY-MM-

DDTHH:MMZ.

E.g. v="2011-11-11T23:00Z/2011-11-

12T23:00Z"

The time must always be expressed in UTC. Resolution m 35

alphanumeric

1 Defines the number of units of time that

compose an individual step within a period.


PT15M=Quarter-hourly contracts (15 min.) Interval m structure 96 Object used for the transmission of each

individual period and its associated quantity.

On summer- and the winter-time change there

will be 92 (23 hours day) and 100 (25 hours

day) intervals. Pos m 6 numeric 1 This information provides the relative position

of a period within a tender interval. Qty m 17 numeric 1 This information defines the quantity that is

tendered for the interval in question and that is

expressed in the Measurement Unit Quantity.

7.1.2.2 BG Allocation file structure in CSV

The BG Allocation file can also be downloaded as CSV format. The CSV format is structured:

Header: Time;[Time]

[EIC/EAN-Area code of TSO A] -> [EIC/EAN-Area code of TSO B]

[EIC/EAN-Area code of TSO B] -> [EIC/EAN-Area code of TSO A]

Body: Column 1: [Contract (Date and Time)];

Column 2: [Value for direction A->B];

Column 3: [Value for direction B->A]




Page 45 of 47


7.2 File adaptations regarding switch to daylight saving time

Because of summer- and winter time changes the UTC time in the files has to be adapted.

After time change to summer time (day with 23 hours) and during summer time (CEST),

UTC time for delivery start and end in the files will be 2 hours behind the CEST time.

After time change to winter time (day with 25 hours) and during winter time (CET), UTC

time in the files is 1 hour behind the CET time. This is also valid for reports which contain

the time interval and the following tags are the XML-tags which need to be modified within

the files:

Tags in the files during summer time:

<ScheduleTimeInterval v="2010-03-26T22:00Z/2010-03-27T22:00Z"/>

<CapacityTimeInterval v="2010-03-27T22:00Z/2010-03-28T22:00Z"/>

<TimeInterval v="2010-03-27T22:00Z/2010-03-28T22:00Z"/>

Tags in the files during winter time:




Tags for the 23 hours files:




Tags for the 25 hours files:




It depends on the resolution how the files (XML and CSV) are structured for hourly intervals or

quarter-hourly intervals (PT60M or PT15M), the files have 24 time interval rows or 96 time

interval rows.

On 23 hour-days when DST starts, files are expected to contain only 23 or 92 time interval

rows. All intervals from 1 to 23 or 1 to 92 have to be consecutively filled out and completely

listed.

On 25 hour-days the files are expected to contain 25 or 100 time interval rows. All time

interval rows from 1 to 25 or 1 to 100 have to be consecutively filled out and completely

listed.




Page 46 of 47


All files are in UTC and therefore no time shifts exist. The files need to be reduced or

extended for this 1 hour on these days to fit to the summer- and winter time.




Page 47 of 47


8. CATRINA – Capacity Trading Interface Application

With Intraday Capacity Service R8.7.0 the connection to the service via a Capacity Trader

Interface for Applications (CATRINA) was introduced. CATRINA is configurable for the

borders Germany-France (DE-FR), France-Switzerland (CH-FR) and Germany-Switzerland

(CH-DE). It can also be configured for the French-Belgium border.

Communication with CATRINA is based on an open source, open standard for messaging

middleware (AMQP=Advanced Messaging Queuing Protocol) via XML messages.

CATRINA handles a heartbeat broadcast by Intraday Capacity Service, further requests and

responses and even Balancing Mechanism allocations are supported.

For the detailed description regarding CATRINA please refer to the document Capacity API

Specs.docx

Trader User Guide - Elia/media/files/Elia/Products-and-services/Crossborder2... · ACK Acknowledgement File ... message based interfaces. Trader Employee of a market ... unauthorized

Documents