implementation guide...implementation guide – afrr capacity market 2 revision history version...

1

Implementation Guide

aFRR capacity market

Business process: aFRR capacity market

Version: 0.8

Status: Draft

Date: 28.06.2018

https://www.google.se/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwiBjPzn7vrZAhWhIpoKHQoGAUgQjRx6BAgAEAU&url=https://en.wikipedia.org/wiki/File:Statnett_logo.svg&psig=AOvVaw1zzo3SHEteSYmfJEFyMNGf&ust=1521634078428609

http://www.google.se/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwiz0LS_7vrZAhWOw6YKHdNaBWgQjRx6BAgAEAU&url=http://www.ergar.org/members/&psig=AOvVaw0cIQ73wN1MaMvPy8gveipH&ust=1521633979626259

https://www.google.se/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwjy9YyH7vrZAhUyxKYKHTWqB_AQjRx6BAgAEAU&url=https://www.fingrid.fi/sv/grid/pagaende-projekt/&psig=AOvVaw2x0DWR-YHN2FWXkt_-3VGl&ust=1521633871804190

https://www.google.se/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwi-wtnV7vrZAhVHJJoKHSjAC0IQjRx6BAgAEAU&url=https://www.svk.se/drift-av-stamnatet/trygg-elforsorjning/underhall-av-stamnatet/&psig=AOvVaw29Ov-VvaU5mxjl4eC2anLP&ust=1521634038990422

Implementation Guide – aFRR capacity market

2

Revision History

Version Release Date Changed by Comments

0.8 Draft A 28.06.2018 Stein-Ole Gabrielsen Initial Release

mailto:[email protected]


3

Table of Content

1 Introduction ........................................................................................................................................................ 4

1.1 Background ................................................................................................................................................. 4

1.2 Terms and definitions.................................................................................................................................. 5

1.3 References .................................................................................................................................................. 5

2 Business process ................................................................................................................................................. 6

2.1 Timeline ...................................................................................................................................................... 6

2.2 System context ........................................................................................................................................... 7

2.2.1 Interface description ............................................................................................................................ 8

2.3 General rules ............................................................................................................................................... 9

2.3.1 Date and time ...................................................................................................................................... 9

2.3.2 Document identification and revision number ..................................................................................... 9

2.3.3 Update/cancel principles ..................................................................................................................... 9

2.3.4 Acknowledgement .............................................................................................................................. 9

2.3.5 Time series period ............................................................................................................................. 10

2.4 Business rules ............................................................................................................................................ 11

2.4.1 The aFRR capacity market sequence diagram ................................................................................... 11

2.4.2 Bid submission .................................................................................................................................. 12

2.4.3 Accepted bids .................................................................................................................................... 17

2.4.4 Market result ..................................................................................................................................... 26

2.4.5 Reserved CZC .................................................................................................................................... 27

3 Annex ............................................................................................................................................................... 28

3.1 Message examples .................................................................................................................................... 28

3.1.1 Bid ..................................................................................................................................................... 28

3.1.2 Accepted bids to BSP ........................................................................................................................ 28

3.1.3 Accepted bids to TSO ........................................................................................................................ 28

3.1.4 Market result ..................................................................................................................................... 28

3.1.5 Reserved CZC .................................................................................................................................... 28

3.1.6 Acknowledgement ............................................................................................................................ 28

3.2 ECP ........................................................................................................................................................... 29


4

1 Introduction

1.1 Background

Automatic frequency restoration reserves (aFRR) is one of a number of different types of Balancing Services that TSOs use for balancing of the Nordic synchronous area. A common Nordic capacity market for aFRR enables the TSOs to have better control of imbalances in the Nordic area and is one of the first steps in developing a new Nordic balancing concept.

The main goals are

1. To create an efficient market with a common process for procuring capacity for aFRR , considering available transmission capacity (ATC) and capacity offers

2. To create a platform that can be extended for supporting other balancing markets in the Nordics in line with Electricity Balancing Guidelines (GLEB)

This guide provides information about the processes required to support a common Nordic capacity market for aFRR. Both functional and technical aspects are covered. The intended users of this document are participating BSPs and the connecting TSOs.

The main processes described are:

o Bid handling process

o Market clearing process


5

1.2 Terms and definitions

Acronym Term Definition

aFRR Automatic frequency restoration reserves

The FRR that can be activated by an automatic control device designed to reduce the FRCE/ACE to zero

BSP Balancing Services Provider A market Participant providing Balancing Service to its Connecting TSO

CIM IEC Common Information Model

CZC Cross Zonal Capacity The cross-zonal transmission capacity between two bidding zones

ECP Energy Communication Platform Reference implementation of MADES standard

MADES Market Data Exchange Standard Communication IEC standard designed by ENTSO-E

NTC Net Transfer Capacity The trading capacity, also called NTC (Net Transfer Capacity), is capacity made available to trading between the bidding zones. The trading capacity is calculated as the transmission capacity less the regulating margin.

TSO Transmission System Operator A party that is responsible for a

stable power system operation

(including the organisation of

physical balance) through a

transmission grid in a geographical

area. In the Nordic synchronous area,

there are four TSOs: Svenska

kraftnät, Fingrid, Energinet.dk and

Statnett.

1.3 References

Ref [1] IEC 62325-451-1, Framework for energy market communications – Part 451-1: Acknowledgement business process and contextual model for CIM European market

Ref [2] The Nordic aFRR Capacity Market rules

Ref [3] ENTSO-E Reserve Bid document – UML model and schema

http://www.statnett.no/Documents/Kraftsystemet/Utvikling%20av%20kraftsystemet/aFRR%20Nordic%20Appendix%202%20aFRR%20Capacity%20Market,%202016-11-07.pdf

https://docstore.entsoe.eu/Documents/EDI/Library/cim_based/schema/Reserve_bid_document_UML_model_and_schema_v1.1.pdf


6

2 Business process

2.1 Timeline

The aFRR capacity market involves several operational phases. The diagram below shows the timeline for the aFRR capacity market.

BCGOTBCGCT(D-2)

TSO approvaldeadline

Market Clearing time

Elspot NTCSubmission time

ElspotClearing time

(D-1)

Delivery date(D)

Bidding period

Figure 1 timeline

o Between the Balancing Capacity Gate Opening Time (BCGOT) and the Balancing Capacity Gate Closure Time (BCGCT), the BSPs can submit bids

o Between BCGCT and the approval deadline, each TSO can view and, if necessary, reject bids within the TSOs control area. The TSOs have also the possibility to extend the bidding period.

o Between approval deadline and market clearing time, the Bid Selection Optimisation process is executed and the market result is published to the BSPs and the TSOs as soon as the process is completed


7

2.2 System context

The diagram below shows the system context for the aFRR capacity market. It shows the internal processes required in the Nordic MMS system and how it integrates with other systems.

aFRR schedules

1) Accepted bids (all)2) Market result3) Reserved CZC

1) Bids (on behalf of BSP)

1) Accepted bids (BSP)2) Market result

1) Bids

NTC,Elspot price

Marketresult

TSO-BSP MADES network

TSO-TSO MADES network

Reserved CZC

Settlement report

Figure 2 System context diagram


8

2.2.1 Interface description

The two tables below provide an overview of the flows between Fifty Nordic MMS and BSPs and TSOs. The tables show that IEC CIM is used as data exchange format and MADES is used as communication platform. More precisely, ECP, which is the reference implementation of MADES, is the communication platform. Consequently, each TSO shall provide an ECP network for communication with its BSPs. These networks will be interconnected to allow for cross-domain communication. In addition, a separate ECP network is used for TSO-TSO communication. Please refer to <<TODO>> for more details related to ECP/EDX.

Table 1 Flow to Fifty Nordic MMS

System/actor Description Data Channel Document

BSP The BSP planning system Bids MADES iec62325-451-7-reservebiddocument.xsd

TSO The TSO MMS system, places bid on behalf of BSP

Bids MADES iec62325-451-7-reservebiddocument.xsd

Table 2 Flow from Fifty Nordic MMS

System/actor Description Data Channel Document

BSP The BSP planning system Accepted bids MADES iec62325-451-7-reservationallocationresult.xsd

BSP The BSP planning system Market result MADES iec62325-451-6-balancing.xsd

TSO The TSO MMS system Accepted bids MADES iec62325-451-7-reservationallocationresult.xsd

TSO The TSO MMS system Market result MADES iec62325-451-6-balancing.xsd

TSO The TSO MMS system Reserved CZC MADES iec62325-451-3-capacity.xsd


9

2.3 General rules

The aFRR business process flows assume certain basic rules. These rules are described below.

2.3.1 Date and time

Date and time is expressed using the standard XML format for date and time: YYYY‑MM‑DDThh:mm:ss, formatted using the universal time standard UTC by adding a 'Z' behind the time - like this: 2018-06-14T22:00Z

2.3.1.1 Daylight saving time

In winter the time spread is from 23:00 UTC to 23:00 UTC

In summer time spread is from 22:00 UTC to 22:00 UTC

The change from winter to summer time spread is from 23:00 UTC to 22:00 UTC. This change occurs on the last Sunday in March at 01:00 UTC

The change from summer to wintertime spread is from 22:00 UTC to 23:00 UTC. This change occurs on the last Sunday in October at 01:00 UTC

2.3.1.2 Document coverage

The beginning and ending date and time of the period covered by the document shall cover just one CET/CEST day.

2.3.2 Document identification and revision number

The document identification must be unique for every message exchange. The revision number is not used and shall always be equal to '1'. A document received with the same document identification shall be rejected.

2.3.3 Update/cancel principles

In general, a new received document will always completely replace a previous received document. Update of any time series, are done by sending a new document

• with a new document mRID (document identification)

• the same revision number (always equal to '1')

• a newer created date-time

• for the same period/day, domain, subject market participant (for bids)

I.e. to cancel one or more bids, a new document is submitted adhering to the above rules, omitting the bids that should be cancelled. Consequently, in order to cancel everything, a new document adhering to the above rules is submitted, omitting all time series.

2.3.4 Acknowledgement

An acknowledgement document, as defined in Ref [1] is generated either accepting the completely received document or rejecting it completely. Partly accept is never used.


10

2.3.5 Time series period

Within a time series, the position must begin and increment by '1' for each subsequent position forming a series of contiguous numbers covering the complete range of the period (see example below).

<Period>

<timeInterval>

<start>2018-06-15T02:00Z</start>

<end>2018-06-15T06:00Z</end>

</timeInterval>

<resolution>PT1H</resolution>

<Point>

<position>1</position>

<quantity>2.984</quantity>

<price.amount>46.65</price.amount>

<bid_Price.amount>46.65</bid_Price.amount>

<Reason>

<code>A73</code>

</Reason>

</Point>

<Point>





<Reason>

<code>A73</code>

</Reason>

</Point>

<Point>





<Reason>

<code>A73</code>

</Reason>

</Point>

<Point>





<Reason>

<code>A73</code>

</Reason>

</Point>

</Period>


11

2.4 Business rules

The market rules and the market definition for the aFRR capacity market are described in Ref [2].

2.4.1 The aFRR capacity market sequence diagram

The sequence diagram for the aFRR capacity market is depicted below. Note that the last two shown exchanges are provided for information only and are outside the scope of this document.

Planning system<< Balance Service Provider >>

Nordic MMS<< Reserve Allocator >>

Local MMS<< System operator >>

Accepted bids<< ReserveAllocation_MarketDocument >>Accepted bids

<< ReserveAllocation_MarketDocument >>

Market result<< Balancing_MarketDocument>>Market result

<< Balancing_MarketDocument>>

Reserved CZC<< Capacity_MarketDocument>>

Bid submission<< ReserveBid_MarketDocument >>

aFRR schedule<< EDIEL >>

Settlement report<< EDIEL >>

Bid submission - (on behalf of BSP)<< ReserveBid_MarketDocument >>

Figure 3 Sequence diagram for the aFRR capacity market


12

2.4.2 Bid submission

During the tendering phase, the participating BSPs provide all information related to offers for the aFRR capacity market. The ReserveBid_MarketDocument is used to provide this information. Alternatively, bids can be submitted via the Nordic MMS web application.

For a general description of the ReserveBid_MarketDocument schema, please refer to Ref [3] .

2.4.2.1 Business rules

• A Reserve Bid Document contains a set of bids (a bid is represented by a time series)

• A Reserve Bid Document shall be for only one subject party

•

<< TODO >>


13

2.4.2.2 Dependency matrix

ReserveBid_MarketDocument

mRID M Unique identification of the document

revisionNumber M Constant value of "1"

type M A37 - Reserve bid document

createdDateTime M Date and time of document creation (in ISO 8601 UTC format)

YYYY-MM-DDTHH:MM:00Z

reserveBid_Period.timeInterval M Period covered (in ISO 8601 UTC format)

process.processType C A51 - Automatic frequency restoration reserve

receiver_MarketParticipant.mRID M

EIC of Fifty Nordic MMS Or should this be the EIC

of the operator of Nordic

MMS (Statnett SF) A01 - EIC coding scheme

receiver_MarketParticipant.marketRole.type M A34 – Reserve Allocator

sender_MarketParticipant.mRID M

Identification of the party sending the document

Denmark: GS1 or EIC (A10 or A01)

Finland: Finnish national coding scheme (NFI)

Norway: GS1 (A10)

Sweden: Swedish national coding scheme (NSE)

sender_MarketParticipant.marketRole.type M A08 - Balance responsible party This is not yet finalised

and has to be discussed


14

subject_MarketParticipant.mRID M

Identification of the party responsible for the bid



Norway: GS1 (A10)


subject_MarketParticipant.marketRole.type M A08 - Balance responsible party This is not yet finalised


domain.mRID M

EIC of the Control Area

Denmark (DK2): 10YDK-2--------M

Finland: 10YFI-1--------U

Norway: 10YNO-0--------C

Sweden: 10YSE-1--------K

A01 - EIC coding scheme


15

Bid_TimeSeries


auction.mRID M Constant value of "AFRR_CAPACITY_MARKET"

businessType M B74 - The time series contain an offer to provide reserves

acquiring_Domain.mRID M 10Y1001A1001A91G (Nordic Market Area)


connecting_Domain.mRID M The EIC of the area where the resource is located


quantity_Measure_Unit.name M MAW – megawatt

currency_Unit.name C EUR – euro

price_Measure_Unit.name C MWH - megawatt hours

divisible M A01 = YES - quantity may be reduced to the minimum bid size by increments of 5 MW

A02 = NO - No reduction possible on the quantity

blockBid C A01 = YES - all quantities within the time interval must be selected

A02 = NO


16

linkedBidsIdentification C

The identification used to associate bids that are to be linked together.

For aFRR CM, this element is restricted to Up/Down-linking of bids. I.e. if the

Up-bid is selected, then the Down-bid with the same identification must be

selected.

The attribute is not used if

the bid is not linked

exclusiveBidsIdentification C

The identification used to associate bids that are to be linked together.

If one bid is selected then all others with the same identification cannot be

selected

The attribute is not used if

the bid is not linked

flowDirection.direction M

A01 - Up (signifies that the available power can be used by the Purchasing area to increase energy)

A02 - Down (signifies that the available power can be used by the Purchasing area to decrease energy)

marketAgreement.type C A01 – daily

Series_Period

timeInterval M Period covered (in ISO 8601 UTC format)

resolution M PT1H or PT60M one-hour resolution

Point

position M Sequential value beginning with 1

quantity.quantity M Quantity offered. Formatted with three decimals

price.amount C The price of the product offered The same value for all

positions in the time series

minimum_Quantity.quantity C The minimum quantity of energy that can be activated at a given time

position.

Required if divisible = A01

The same value for all



17

2.4.3 Accepted bids

The ReserveAllocation_MarketDocument is used to provide information related to the bids that have been accepted (TSO and BSP) as well as the bids that are not accepted (BSP only). Note that the TSOs will receive information about all accepted bids in all control areas.

<< TODO >>


<< TODO >>


18

2.4.3.2 Dependency matrix – document sent to BSP

ReserveAllocation_MarketDocument



type M A38 - Reserve allocation result document






sender _MarketParticipant.marketRole.type M A34 – Reserve Allocator


Identification of the BSP receiving the document



Norway: GS1 (A10)


receiver_MarketParticipant.marketRole.type M A08 - Balance responsible party This is not yet finalised






19

domain.mRID M

EIC of the Control Area

Denmark (DK2): 10YDK-2--------M

Finland: 10YFI-1--------U

Norway: 10YNO-0--------C

Sweden: 10YSE-1--------K


TimeSeries

mRID M An identification that uniquely identified the time series

bid_Original_MarketDocument.mRID M Constant value of "NA"

bid_Original_MarketDocument.revisionNumber M Constant value of "1"

bid_Original_MarketDocument.bid_TimeSeries.mRID M The identification of the time series that was used in the original tender - the reference

to the bid

bid_Original_MarketDocument.tendering_MarketParticipant.mRID M

The ID of the tendering party



Norway: GS1 (A10)



businessType M B95 – Procured capacity


20





marketAgreement.type M A01 – daily

marketAgreement.mRID M Constant value of "NA"




flowDirection.direction M A01 - Up (signifies that the available power can be used by the Purchasing area to

increase energy)

A02 - Down (signifies that the available power can be used by the Purchasing area to

decrease energy)

Series_Period




21

Point


quantity M Quantity accepted. Formatted with three decimals

price.amount C The price of the product accepted The same value for all


bid_Price.amount C The original bid price. For pay-as-bid this will be the same as price.amount

Reason

code M A73 - Tender in question has been accepted

B09 - Bid not accepted

The BSP will receive

information about all bids

submitted

text C A reason for rejection can be specified by the TSO and will be included here


22

2.4.3.3 Dependency matrix – document sent to TSO

ReserveAllocation_MarketDocument



type M A38 - Reserve allocation result document






sender _MarketParticipant.marketRole.type M A34 – Reserve Allocator


EIC of the TSO that is receiving the document

10X1001A1001A248 (Energinet.dk)

10X1001A1001A264 (Fingrid Oyj)

10X1001A1001A38Y (Statnett SF)

10X1001A1001A418 (Svenska kraftnät)

receiver_MarketParticipant.marketRole.type M A04 – System operator





23

domain.mRID M

10Y1001A1001A91G (Nordic Market Area)


TimeSeries

mRID M An identification that uniquely identified the time series

bid_Original_MarketDocument.mRID M Constant value of "NA"

bid_Original_MarketDocument.revisionNumber M Constant value of "1"

bid_Original_MarketDocument.bid_TimeSeries.mRID M The identification of the time series that was used in the original tender - the reference

to the bid

bid_Original_MarketDocument.tendering_MarketParticipant.mRID M

The ID of the tendering party



Norway: GS1 (A10)



businessType M B95 – Procured capacity


24





marketAgreement.type M A01 – daily

marketAgreement.mRID M Constant value of "NA"




flowDirection.direction M A01 - Up (signifies that the available power can be used by the Purchasing area to

increase energy)

A02 - Down (signifies that the available power can be used by the Purchasing area to

decrease energy)

Series_Period




25

Point


quantity M Quantity accepted. Formatted with three decimals

price.amount C The price of the product accepted The same value for all


bid_Price.amount C The original bid price. For pay-as-bid this will be the same as price.amount

Reason

code M A73 - Tender in question has been accepted

The TSO will only receive

information about

accepted bids


26

2.4.4 Market result

<< TODO >>


<< TODO >>


27

2.4.5 Reserved CZC

<< TODO >>


<< TODO >>


28

3 Annex

3.1 Message examples

3.1.1 Bid

3.1.2 Accepted bids to BSP

3.1.3 Accepted bids to TSO

3.1.4 Market result

3.1.5 Reserved CZC

3.1.6 Acknowledgement


29

3.2 ECP

<< TODO >>