1

WEBSERVICE INTEGRATION GUIDE

FOR DATA CONSUMERS

Vers 1.5

2

Table of Contents Retrieving data using Web services ................................................................................................................ 3

Introduction ................................................................................................................................................ 3

Service URLs ................................................................................................................................................ 3

WITH URL .................................................................................................................................................... 3

Query .......................................................................................................................................................... 4

Response ..................................................................................................................................................... 4

Requesting access: ...................................................................................................................................... 6

Testing ........................................................................................................................................................ 7

Subscribing to a data feed ............................................................................................................................... 9

Note for PRODUCTION_TYPE / GENERATION_UNIT ..................................................................................... 13

References ..................................................................................................................................................... 14

Annexes ......................................................................................................................................................... 15

Query parameters ..................................................................................................................................... 15

Business dimension types ......................................................................................................................... 15

Data items and parameters ...................................................................................................................... 16

3

Retrieving data using Web services

Introduction

Data consumers can use the “Transparency Platform Web Service” to retrieve data.

This web service is based on the standard IEC 61968-100 (referred as [STAN]) and the AF_284

specification (referred as [SPEC]).

The signature needs to use the algorithm SHA-1. At the moment the TP is only expecting that verison.

Data consumers should use the verb “get” and noun “EnergyAccountReport” See [SPEC], Chapter 5.2 Get

Message for more information.

Parameters are passed as a series of key/value pairs as show in “Table 1 – Query parameters”

The description of each business dimension with list of possible values can be found in “Table 2 – Business

dimensions types”

Detailed description of data items and parameters for retrieval can be found in “Table 3 – Data items and

parameters”

Service URLs The WSDL and endpoints are available at1:

Environment Endpoint URL

Test https://62.209.222.27/data-receiver-ws/endpoints/DataService

Production https://62.209.222.22/data-receiver-ws/endpoints/DataService

You can add .wsdl if needed, e.g.: https://62.209.222.27/data-receiver-ws/endpoints/DataService.wsdl

WITH URL Environment Endpoint URL

Production https://transparency-ws.entsoe.eu/data-receiver-ws/endpoints/DataService.wsdl

You can continue accessing web services using DNS record https://transparency-ws.entsoe.eu/ or using IP address

62.209.222.22. Test environment is only accessing by the IP.

1 Subject to change.

4

Query “Figure 1 - Sample data query” shows a sample data query built the following way:

1. Specifying the requested data item using the name/value pair DataItem/Value

2. Specifying the time interval using the name/value TimeInterval/Value

3. Specifying the in and out area (as described more in details in “Table 3 – Data items and

parameters”)

Response Retrieved XML data are wrapped in the QueryData element. See [SPEC], ANNEX I 4.1.2 Response. Binary

data items data are base64 encoded and transmitted in the “Compressed” element. See [SPEC], ANNEX I

3.2 Example with binary data. In case of binary data QueryData element is omitted. “Figure 2 - Sample

data response” included below shows a typical response message.

<soap:Envelope xmlns:msg="http://iec.ch/TC57/2011/schema/message" xmlns:soap="http://www.w3.org/2003/05/soap-envelope">

<soap:Header/>

<soap:Body>

<msg:RequestMessage>

<msg:Header>

<msg:Verb>get</msg:Verb>

<msg:Noun>EnergyAccountReport</msg:Noun>

<msg:Context>PRODUCTION</msg:Context>

<msg:Property>

<msg:Name>DataItem</msg:Name>

<msg:Value>CB_BALANCING_VOLUMES_OF_EXCHANGED</msg:Value>

</msg:Property>

<msg:Property>

<msg:Name>TimeInterval</msg:Name>

<msg:Value>2015-03-08 00:00:00/2015-03-09 00:00:00</msg:Value>

</msg:Property>

<msg:Property>

<msg:Name>AREA|MBA</msg:Name>

<msg:Value>10YFR-RTE------C</msg:Value>

</msg:Property>

<msg:Property>

<msg:Name>AREA|MBA</msg:Name>

<msg:Value>10YES-REE------0</msg:Value>

</msg:Property>

</msg:Header>

</msg:RequestMessage>

</soap:Body>

</soap:Envelope>

Figure 1 - Sample data query

5

As you can see responses are signed by the transparency platform, and the calling client can verify the

data authenticity by verifying the signature. For more information about this signature, please refer to

[SPEC], “Chapter 10 Security” with example in “Annex A. 6 Digital Signature.”

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <env:Header/> <env:Body> <msg:ResponseMessage xmlns:msg="http://iec.ch/TC57/2011/schema/message"> <msg:Header> <msg:Verb>reply</msg:Verb> <msg:Noun>GL_MarketDocument</msg:Noun> <msg:Context>PRODUCTION</msg:Context> <msg:Property> <msg:Name>DataItem</msg:Name> <msg:Value>DAY_AHEAD_AGGREGATED_GENERATION</msg:Value> </msg:Property> <msg:Property> <msg:Name>TimeInterval</msg:Name> <msg:Value>2015-02-01 00:00:00/2016-01-01 00:00:00</msg:Value> </msg:Property> <msg:Property> <msg:Name>AREA|CTA</msg:Name> <msg:Value>10YFR-RTE------C</msg:Value> </msg:Property> <Signature:Signature xmlns:Signature="http://www.w3.org/2000/09/xmldsig#"> <Signature:SignedInfo> <Signature:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/> <Signature:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> <Signature:Reference URI=""> <Signature:Transforms> <Signature:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Signature:Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/> </Signature:Transforms> <Signature:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <Signature:DigestValue>cq83wgRtWNYD8WCkR9KjeKQJpRk=</Signature:DigestValue> </Signature:Reference> </Signature:SignedInfo> <Signature:SignatureValue>…==</Signature:SignatureValue> <Signature:KeyInfo> <Signature:X509Data> <Signature:X509IssuerSerial> <Signature:X509IssuerName>CN=ETP Test, O=ENTSO-E, ST=European Union, C=EU</Signature:X509IssuerName> <Signature:X509SerialNumber>1409822142</Signature:X509SerialNumber> </Signature:X509IssuerSerial> <Signature:X509SubjectName>CN=ETP Test,O=ENTSO-E,ST=European Union,C=EU</Signature:X509SubjectName> <Signature:X509Certificate>MII…==</Signature:X509Certificate> </Signature:X509Data> </Signature:KeyInfo> </Signature:Signature> </msg:Header> <msg:Reply> <msg:Result>OK</msg:Result> </msg:Reply> <msg:Payload> <GL_MarketDocument:GL_MarketDocument xmlns:GL_MarketDocument="urn:iec62325.351:tc57wg16:451-6:generationloaddocument:3:0" xmlns="urn:iec62325.351:tc57wg16:451-6:generationloaddocument:3:0"> <mRID>487d7244d7ec496f82f9441336d7ded0</mRID> <revisionNumber>1</revisionNumber> <type>A71</type> <process.processType>A01</process.processType> <sender_MarketParticipant.mRID codingScheme="A01">10X1001A1001A450</sender_MarketParticipant.mRID> <sender_MarketParticipant.marketRole.type>A32</sender_MarketParticipant.marketRole.type> <receiver_MarketParticipant.mRID codingScheme="A01">10X1001A1001A450</receiver_MarketParticipant.mRID> <receiver_MarketParticipant.marketRole.type>A33</receiver_MarketParticipant.marketRole.type> <createdDateTime>2015-02-03T11:03:09Z</createdDateTime> <time_Period.timeInterval> <start>2015-02-01T00:00Z</start> <end>2015-02-03T23:00Z</end> </time_Period.timeInterval> <TimeSeries> <mRID>1</mRID> <businessType>A01</businessType> <objectAggregation>A01</objectAggregation> <inBiddingZone_Domain.mRID codingScheme="A01">10YFR-RTE------C</inBiddingZone_Domain.mRID> <quantity_Measure_Unit.name>MAW</quantity_Measure_Unit.name> <curveType>A01</curveType> <Period> <timeInterval> <start>2015-02-01T00:00Z</start> <end>2015-02-02T00:00Z</end> </timeInterval> <resolution>PT60M</resolution> <Point> <position>1</position> <quantity>71862</quantity> </Point> <Point> <position>2</position> <quantity>70890</quantity> </Point> … </Period> </TimeSeries> </GL_MarketDocument:GL_MarketDocument> </msg:Payload> </msg:ResponseMessage> </env:Body> </env:Envelope>

Figure 2 - Sample data response

6

Requesting access: The platform contains a trust store of clients that are allowed to retrieve data. As a new data consumer

you first have to deliver to the platform administrator the X509 client certificate that will be use to

establish the two-way SSL connection.

For this, send an email to transparency@entsoe.eu titled “X509 certificate for Data Consumer access”,

with an attachment containing the client certificate (in PEM format) to be trusted.

If you want to use different certificates for the test and the production environments, attach both

certificates and specify in the email body, which certificate has to be trusted on which environment.

The platform administrator might contact you to request additional information if necessary. In any case,

you will eventually receive a feedback telling you when your access has been granted.

The platform accepts both certificates delivered by a known CAs and self-signed certificates.

A self-signed certificate can be generated with OpenSSL2 using the following command:

1) Generate the certificate :

Openssl> req -x509 -newkey rsa:2048 -keyout dataconsumer_key.pem -out

dataconsumer_cert.pem -days 1825

-> Please be sure to provide all details otherwise the certificate won’t be accepted by the platform.

In this case the file “dataconsumer_cert.pem” is the one that should be sent to the platform

administrator when requesting access.

2) In order to get the correct keystore to be used in SoapUI you can use the following command:

Openssl> pkcs12 -export -name entsoe -in dataconsumer_cert.pem -inkey

dataconsumer_key.pem -out keystore.p12

If you want to use java keystore to import the keytool :

keytool3 -importkeystore -destkeystore keystore.jks -srckeystore

keystore.p12 -srcstoretype pkcs12 -alias entsoe

3) Then you have to add the dataconsumer.p12 file to the SSL option of SoapUI.

2 OpenSSL is available for most platforms at: https://www.openssl.org/

3 http://docs.oracle.com/javase/8/docs/technotes/tools/windows/keytool.html

7

Testing Once the registration phase has been completed we recommend to send some data query using the

provided SOAPUI project that demonstration how to retrieve data.

First, you need to configure the SSL Settings to include your certificate in the web service call.

Configure SOAPUI has shown on “Figure 3 - SSL Settings configuration”.

In this case you have to use file: keystore.p12 and the password provided during the generation.

Figure 3 - SSL Settings configuration

Once this is done, you can open the project and proceed with sending a request:

1. To do so, Import the file EMFIP-data-consumer-soapui-project.xml

2. Open the provided project, select a request as described in “Figure 4 - Calling the service”

3. Execute the request

4. Check the response is valid

5. If there is an error, send the contents of “http log” and “error log” to transparency@entsoe.eu

8

Figure 4 - Calling the service

9

Subscribing to a data feed Data consumer can subscribe to data feed: the platform will them push updates.

Note: You web service needs to use SOAP 12 standard and not 11.

The first step is to create an account on the web portal. Then send an email to transparency@entsoe.eu

titled “Data Consumer subscription rights request” containing the user mane for the previously created

account.

Once the access rights have been granted you'll then be able to see on the data items portal a "Subscribe"

link as shown below.

10

Before being able to actually subscribe to a data item update, you first have to go to the subscription

configuration menu "your@email.com->"My Subscriptions channels" and define a Web service channel or

an ECP channel.

You can see the details by clicking on “My subscriptions”:

11

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope"> <env:Header/> <env:Body> <msg:RequestMessage xmlns:msg="http://iec.ch/TC57/2011/schema/message"> <msg:Header> <msg:Verb>create</msg:Verb> <msg:Noun>ETP-DOCUMENT</msg:Noun> <msg:Context>PRODUCTION</msg:Context> <msg:AckRequired>true</msg:AckRequired> <Signature:Signature xmlns:Signature="http://www.w3.org/2000/09/xmldsig#"> <Signature:SignedInfo> <Signature:CanonicalizationMethod Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/> <Signature:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> <Signature:Reference URI=""> <Signature:Transforms> <Signature:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/> <Signature:Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/> </Signature:Transforms> <Signature:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <Signature:DigestValue>275/2HzXps6MtbC6San5IYBcTKQ=</Signature:DigestValue> </Signature:Reference> </Signature:SignedInfo> <Signature:SignatureValue>…KA==</Signature:SignatureValue> <Signature:KeyInfo> <Signature:X509Data> <Signature:X509IssuerSerial> <Signature:X509IssuerName>CN=ETP Test, O=ENTSO-E, ST=European Union, C=EU</Signature:X509IssuerName> <Signature:X509SerialNumber>1409822142</Signature:X509SerialNumber> </Signature:X509IssuerSerial> <Signature:X509SubjectName>CN=ETP Test,O=ENTSO-E,ST=European Union,C=EU</Signature:X509SubjectName> <Signature:X509Certificate>…==</Signature:X509Certificate> </Signature:X509Data> </Signature:KeyInfo> </Signature:Signature> </msg:Header> <msg:Request/> <msg:Payload> <Unavailability_MarketDocument:Unavailability_MarketDocument xmlns="urn:iec62325.351:tc57wg16:451-6:outagedocument:3:0" xmlns:Unavailability_MarketDocument="urn:iec62325.351:tc57wg16:451-6:outagedocument:3:0"> <mRID>764a9c7e48e0417686e23c037b34f80b</mRID> <revisionNumber>1</revisionNumber> <type>A80</type> <process.processType>A26</process.processType> <createdDateTime>2015-03-30T15:11:34Z</createdDateTime> <sender_MarketParticipant.mRID codingScheme="A01">10X1001A1001A450</sender_MarketParticipant.mRID> <sender_MarketParticipant.marketRole.type>A32</sender_MarketParticipant.marketRole.type> <receiver_MarketParticipant.mRID codingScheme="A01">10X1001A1001A450</receiver_MarketParticipant.mRID> <receiver_MarketParticipant.marketRole.type>A33</receiver_MarketParticipant.marketRole.type> <unavailability_Time_Period.timeInterval> <start>2014-08-22T01:16Z</start> <end>2014-08-22T03:03Z</end> </unavailability_Time_Period.timeInterval> <docStatus> <value>A05</value> </docStatus> <TimeSeries> <mRID>1</mRID> <businessType>A54</businessType> <biddingZone_Domain.mRID codingScheme="A01">10YGB----------A</biddingZone_Domain.mRID> <start_DateAndOrTime.date>2014-08-22</start_DateAndOrTime.date> <start_DateAndOrTime.time>01:16:00Z</start_DateAndOrTime.time> <end_DateAndOrTime.date>2014-08-22</end_DateAndOrTime.date> <end_DateAndOrTime.time>03:03:00Z</end_DateAndOrTime.time> <quantity_Measure_Unit.name>MAW</quantity_Measure_Unit.name> <curveType>A03</curveType> <production_RegisteredResource.mRID codingScheme="A01">48WSTN0000DRAXXK</production_RegisteredResource.mRID> <production_RegisteredResource.name>DRAXX</production_RegisteredResource.name> <production_RegisteredResource.location.name>GB</production_RegisteredResource.location.name> <production_RegisteredResource.pSRType.psrType>B05</production_RegisteredResource.pSRType.psrType> <production_RegisteredResource.pSRType.powerSystemResources.mRID codingScheme="A01">48W00000DRAXX-2C</production_RegisteredResource.pSRType.powerSystemResources.mRID> <production_RegisteredResource.pSRType.powerSystemResources.name>DRAXX-2</production_RegisteredResource.pSRType.powerSystemResources.name> <production_RegisteredResource.pSRType.powerSystemResources.nominalP unit="MAW">645</production_RegisteredResource.pSRType.powerSystemResources.nominalP> <Available_Period> <timeInterval> <start>2014-08-22T01:16Z</start> <end>2014-08-22T03:03Z</end> </timeInterval> <resolution>PT1M</resolution> <Point> <position>1</position> <quantity>550</quantity> </Point> </Available_Period> </TimeSeries> <Reason> <code>B18</code> </Reason> </Unavailability_MarketDocument:Unavailability_MarketDocument> <msg:Format>Plain</msg:Format> </msg:Payload> </msg:RequestMessage> </env:Body> </env:Envelope>

The platform will then be able to push the data to your endpoint using a web service call to the URL

previously configured. Below a sample web service call:

12

XSD file

A correct answer is mandatory otherwise the channel is disabled.

The XSD file for the response can be found here:

https://62.209.222.22/data-receiver-ws/schemas/dataService/http-iec-ch-TC57-2011-schema-message.xsd

Since the web service pushes a put request, put response should follow, as for example in the REE WS

standard (attached).

One of the following elements is expected, ResponseMessage should be used.

<{http://iec.ch/TC57/2011/schema/message}ResponseMessage>

<{http://iec.ch/TC57/2011/schema/message}EventMessage>,

<{http://iec.ch/TC57/2011/schema/message}FaultMessage>,

<{http://iec.ch/TC57/2011/schema/message}Message>,

<{http://iec.ch/TC57/2011/schema/message}RequestMessage>

13

Note for PRODUCTION_TYPE / GENERATION_UNIT

The actual specification is not correct and a different request parameter should be used in case of this

data item.

Currently, 3 parameters are used.

<msg:Name>TimeInterval</msg:Name>

<msg:Name>AREA|CTA</msg:Name>

<msg:Name>PRODUCTION_TYPE</msg:Name>

This means however, that should there be several generation units of the same production type (lets say

"Wind Offshore"), on the same CTA, then some of them will remain unreachable. The reason is that query

data retrieves only one document per call, which needs to be identifiable.

A fix exists and resolves this, however parameters have changed.

Instead of PRODUCTION_TYPE, we would use GENERATION_UNIT. Value of this tag would be the EIC code

the generation unit in question.

Example of the new parameters.

<msg:Property>

<msg:Name>TimeInterval</msg:Name>

<msg:Value>2015-10-25 00:00:00/2015-10-27 00:00:00</msg:Value>

</msg:Property>

<msg:Property>

<msg:Name>AREA|CTA</msg:Name>

<msg:Value>10YES-REE------0</msg:Value>

</msg:Property>

<msg:Property>

<msg:Name>GENERATION_UNIT</msg:Name>

<msg:Value>18WABO1-12345-D7</msg:Value>

</msg:Property>

This way every unit could be pinpointed and easily extracted, it would also eliminate the case when

multiple documents would be discovered.

14

References SPEC

AF_284

Electronic data interchanges on the Internal Electricity Market

(To be superseded by IEC TS 62325-504 when published)

STAND

IEC 61968-100

Application integration at electric utilities – System interfaces for distribution management –Part 100:

Implementation Profiles

15

Annexes

Query parameters

Business dimension types

Parameter name Parameter value Example

Data Item Code of the data item. ACTUAL_TOTAL_LOAD

Time Interval Data item instance time interval. 2013-12-19 00:00:00/2013-12-20 00:00:00

Business

Dimensions

Up to 3 business dimensions (depends on

the data type). For each dimension user has

to specify it’s type and it’s value.

Type: AREA|BZN

Value: 10YFR-RTE------C

Table 1 – Query parameters

Code Name Description

AREA|CTA Control Area A ‘control area’ means a coherent part of the interconnected system, operated by a

single system operator and shall include connected physical loads and/or

generation units if any

EIC codes available in Energy Identification Codes (EIC) Lists at ENTSO-E web

sites (Y codes).

AREA|BZN Bidding Zone A ‘bidding zone’ means the largest geographical area within which market

participants are able to exchange energy without capacity allocation

EIC codes available in Energy Identification Codes (EIC) Lists at ENTSO-E web

sites (Y codes).

AREA|CTY Country A country (state) has often the same shape as Control Area or Bidding Zone. EIC

codes of different area types can be therefore used also for country.

AREA|MBA Market Balance

Area

A geographic Area consisting of one or more Metering Grid Areas with common

market rules for which the settlement responsible Party carries out a balance

settlement and which has the same price for imbalance. A Market Balance Area

may also be defined due to bottlenecks.

CONTRACT_TYPE_TOTAL_

CAPACITY_NOMINATED

Contract Type Values of ContractTypeList in ENTSO-E Code List document

(e.g. yearly=A04)

PRODUCTION_TYPE Production Type Values starting with letter “B” of AssetTypeList in ENTSO-E Code List document

(e.g. Solar=B16)

PRODUCTION_TYPE_

WIND_AND_SOLAR

Production Type

(for wind and

solar)

Subset of values starting with letter “B” of AssetTypeList in ENTSO-E Code List

document

(e.g. Solar=B16)

RESERVE_TYPE_R2 Reserve Type Values of BusinessTypeList in ENTSO-E Code List document

Table 2 – Business dimensions types

16

Data items and parameters

Domain Data Item Interval

Range

Data Item Code BD1 Code BD1

Eligible

Values

BD2 Code BD2 Eligible Values BD3 Code BD3

Eligible

Values

Load Actual Total Load [6.1.A] DAY ACTUAL_TOTAL_LOAD AREA|BZN, AREA|CTA, AREA|CTY Area EIC

Load Day-ahead Total Load

Forecast [6.1.B]

DAY DAY_AHEAD_TOTAL_LOAD_FORECAST AREA|BZN, AREA|CTA, AREA|CTY Area EIC

Load Week-ahead Total Load

Forecast [6.1.C]

WEEK WEEK_AHEAD_TOTAL_LOAD_FORECAST AREA|BZN, AREA|CTA, AREA|CTY Area EIC

Load Month-ahead Total Load

Forecast [6.1.D]

WEEK-

BASED

MONTH

MONTH_AHEAD_TOTAL_LOAD_FORECAST AREA|BZN, AREA|CTA, AREA|CTY Area EIC

Load Year-ahead Total Load

Forecast [6.1.E]

WEEK-

BASED

YEAR

YEAR_AHEAD_TOTAL_LOAD_FORECAST AREA|BZN, AREA|CTA, AREA|CTY Area EIC

Load Year-ahead Forecast

Margin [8.1]

YEAR YEAR_AHEAD_FORECAST_MARGIN AREA|BZN, AREA|CTA, AREA|CTY Area EIC

Generation Installed Generation

Capacity Aggregated

[14.1.A]

YEAR INSTALLED_GENERATION_CAPACITY_AGGREGATED AREA|BZN, AREA|CTA, AREA|CTY Area EIC PRODUCTION_TYPE B01, B02, B03, B04, B05, B06, B07,

B08, B09, B10, B11, B12, B13, B14,

B15, B16, B17, B18, B19, B20

Generation Day-ahead Aggregated

Generation [14.1.C]

DAY DAY_AHEAD_AGGREGATED_GENERATION AREA|BZN, AREA|CTA, AREA|CTY Area EIC

Generation Day-ahead Generation

Forecasts for Wind and

Solar [14.1.D]

DAY DAY_AHEAD_GENERATION_FORECAST_WIND_SOLAR AREA|BZN, AREA|CTA, AREA|CTY Area EIC PRODUCTION_TYPE_WIND_A

ND_SOLAR

B16, B18, B19

Generation Aggregated Generation

per Type [16.1.B&C]

DAY AGGREGATED_GENERATION_PER_TYPE AREA|BZN, AREA|CTA, AREA|CTY Area EIC PRODUCTION_TYPE B01, B02, B03, B04, B05, B06, B07,

B08, B09, B10, B11, B12, B13, B14,

B15, B16, B17, B18, B19, B20

Generation Actual Generation Output

per Generation Unit

[16.1.A]

DAY ACTUAL_GENERATION_OUTPUT_PER_UNIT AREA|BZN, AREA|CTA Area EIC PRODUCTION_TYPE B01, B02, B03, B04, B05, B06, B07,

B08, B09, B10, B11, B12, B13, B14,

B15, B16, B17, B18, B19, B20

Generation Aggregate Filling Rate of

Water Reservoirs and

Hydro Storage Plants

WEEK-

BASED

YEAR

AGGREGATE_FILLING_RATE_OF_WATER_RESERVOIRS AREA|BZN, AREA|CTA, AREA|CTY Area EIC

17

[16.1.D]

Balancing Accepted Aggregated

Offers [17.1.D]

DAY ACCEPTED_AGGREGATED_OFFERS AREA|MBA Area EIC RESERVE_TYPE_R2 A95, A96, A97, A98

Balancing Activated Balancing

Energy [17.1.E]

DAY ACTIVATED_BALANCING_ENERGY AREA|MBA Area EIC RESERVE_TYPE_R2 A95, A96, A97, A98

Balancing Prices of Activated

Balancing Energy [17.1.F]

DAY PRICES_OF_ACTIVATED_BALANCING_ENERGY AREA|MBA Area EIC RESERVE_TYPE_R2 A95, A96, A97, A98

Balancing Imbalance Prices [17.1.G] DAY IMBALANCE_PRICES AREA|MBA Area EIC

Balancing Total Imbalance Volumes

[17.1.H]

DAY TOTAL_IMBALANCE_VOLUMES AREA|MBA Area EIC

Balancing Financial Expenses and

Income for Balancing

[17.1.I]

MONTH FINANCIAL_EXPENSES_AND_INCOME_FOR_BALANCING AREA|MBA Area EIC

Balancing Cross-border Balancing -

Volumes of Exchanged

Bids and Offers [17.1.J]

DAY CB_BALANCING_VOLUMES_OF_EXCHANGED AREA|MBA Area EIC AREA|MBA Area EIC

Balancing Cross-border Balancing -

Prices [17.1.J]

DAY CB_BALANCING_PRICES AREA|MBA Area EIC AREA|MBA Area EIC

Balancing Cross-border Balancing -

Energy Activated [17.1.J]

DAY CB_BALANCING_ENERGY_ACTIVATED AREA|MBA Area EIC AREA|MBA Area EIC

Transmission Physical Flows [12.1.G] DAY NET_CROSS_BORDER_PHYSICAL_FLOWS AREA|BZN, AREA|CTA, AREA|CTY Area EIC AREA|BZN, AREA|CTA,

AREA|CTY

Area EIC

Transmission Forecasted Day-ahead

Transfer Capacities [11.1]

DAY DAY_AHEAD_NTC AREA|BZN, AREA|CTA Area EIC AREA|BZN, AREA|CTA Area EIC

Transmission Forecasted Week-ahead

Transfer Capacities [11.1]

WEEK WEEK_AHEAD_NTC AREA|BZN, AREA|CTA Area EIC AREA|BZN, AREA|CTA Area EIC

Transmission Forecasted Month-ahead

Transfer Capacities [11.1]

MONTH MONTH_AHEAD_TRANSFER_CAPACITIES AREA|BZN, AREA|CTA Area EIC AREA|BZN, AREA|CTA Area EIC

Transmission Forecasted Year-ahead

Transfer Capacities [11.1]

YEAR YEAR_AHEAD_NTC AREA|BZN, AREA|CTA Area EIC AREA|BZN, AREA|CTA Area EIC

18

Transmission Total Capacity Nominated

[12.1.B]

DAY TOTAL_CAPACITY_NOMINATED CONTRACT_TYPE_TOTAL_CAPACITY_

NOMINATED

A01, A05, A06,

A07 4

AREA|BZN, AREA|CTA Area EIC AREA|BZN,

AREA|CTA

Area EIC

Transmission Day-ahead Prices [12.1.D] DAY DAY_AHEAD_PRICES AREA|BZN, AREA|CTY Area EIC

Transmission Implicit Allocations - Net

Positions [12.1.E]

(intraday)

DAY IMPL_ALLOC_NET_POSITIONS_INTRADAY AREA|BZN Area EIC

Transmission Implicit Allocations - Net

Positions [12.1.E] (daily)

DAY IMPL_ALLOC_NET_POSITIONS_DAILY AREA|BZN Area EIC

Transmission Scheduled Commercial

Exchanges [12.1.F]

DAY SCHEDULED_COMMERCIAL_EXCHANGES AREA|BZN, AREA|CTA Area EIC AREA|BZN, AREA|CTA Area EIC

Table 3 – Data items and parameters

4 Only A05 displayed on DV