Flow

These are documents / message made within the NBM Working group for common use.
The work is limited by what should be exchanged between Nordic TSOs.
This is our working documents which we have agreed on.It is the raw documentation which we have discussed within NBM working group, and will probably be published in a different layout in near future.

Change Log

Ver Changed by Date Changes

Draft Version 0.1

Bent Atle Bjørtomt

07.04.2020

Total Planned Flow, update table. Applied for a business type, removed other business types. Removed comment around using A04.

Update

Bent Atle Bjørtomt

16.04.2020

Investigated whether MARI has reason code that we can reuse for capacity document. MARI has no defined codes for capacity, "reason code" is available for future use.

Other updates according to NBM working group meeting 08.04.2020

Updated with Business code from NMEG for Total Planned Flow and Expected Countertrade.

Update

Bent Atle Bjørtomt

28.05.2020

Received Business Types from NMEG

Z90-Power Plan Trade

Z91-Loop transit

Z92- Agreed supportive power (ASP)

Z93- Production adjustments

Update

Bent Atle Bjørtomt

29.05.2020

Clarifications clarified

Update

Bent Atle Bjørtomt

08.06.2020

Updated with Harmonized product codes/agreement types.

Added short name for product codes.

Update

Jon-Egil Nordvik

Bent Atle Bjørtomt

24.06.2020

Split Measured flow into two separate descriptions, and assign own process type for Historic.

Update

Bent Atle Bjørtomt

25.09.2020

Moved documentation to new confluence Space.

Restructured document for temporary purpose to support SvK / Energinet.

Added note to Planned Flow mFRR, Z35 is special, but it might be Z53 in the future if needed.

Temporary Document produced

Change

Bent Atle Bjørtomt

13.10.2020

Z35-FRR-M, Special Regulation is replaced by Z53 - FRR-M, System Regulation. See changes for Planned Flow mFRR TSO

Update

Bent Atle Bjørtomt

18.11.2020

Added an section Generic Harmonized Code list for "Products" to clarify usage of the Harmonized Codes.

Removed country specific codes which were not in use.

Update

Bent Atle Bjørtomt

01.12.20

Message Implementation Guide: Curvetype now in accordance with text A03=Variable sized Block, as defined in overview below.

v1.1

Bent Atle Bjørtomt

08.04.21

  • Converted to Gitlab

  • Corrected reference to 'Activation - aFRR', to be planned-flow-aFRR.

  • Redirected link for MARI IG to the published one on ENTSOE, under reference section.

v1.2

Bent Atle Bjørtomt

14.05.21

Flow Reason codes for System and Balance purposes. Changed from code Z31 to B49, for Balancing, and Z53 to B22 for System Regulation.

v1.3

Bent Atle Bjørtomt

11.03.22

Added support for both ramped and non-ramped values for Planned Flow Power Plan Trade TSO.

v1.4

Bent Atle Bjørtomt

21.09.22

Fixed missing link to Measured Flow Historic TSO.
Added two sections, Total Planned Flow and Power Plan Trade.

Introduction

Nordic Communication Infrastructure is providing FiftyONE with different Flow-values. Data are provided FiftyONE on the same principals as done in the prototype, see Prototype A-B-C: Nordic Data Communication.

FiftyOne will present all Flows in their GUI as shown in figure below, in addition all or single part of these flows will be used for other purposes as shown in Use case detailed flow figure.

image

Business Requirements

Operator wish to see values for planned and measured flow on the corridor in the map. All other values will be shown in a graph. Operator does not need detail card on corridors, just a detail window with graph.

Message Parts

Planned Flow

The planned flow consists of a sum of scheduled flow messages. They are divided up several sub-flows that added together will make up the Total Planned Flow that FiftyOne will display in its GUI.
It is proposed to separate the message in separate documents that all rely on Schedule_MarketDocumet. This is done as a result of the fact that different sub-processes need different parts of the messages, in addition, these CIM messages/documents should go over a streaming technology (e.g. kafka). Another reason is also the downside it will entail to do maintenance on a message in a larger flow message/document. It will thus be easier to publish an update in a document that may be consumed only by a system, with a large document it will affect several systems.

The Planned flow process contain several flows and these are. They are supposed to be produced by each TSO and exchanged to all TSOs and Nordic Common ( see sequence diagram(TBD)). They are divided into separate

Use cases for planned flow:

The following diagram is intended to show that we separate all streams into separate documents, shown as use cases.

image

Total Planned Flow

total planned flow tso

Power Plan Trade

power plan trade

Measured flow

Measured Flow consists of the following data exchanges:

  • Measured Real-time values ( what about measured versus estimated?)

  • Measured Historical values is made to meet the requirements to obtain historical data (F-BR-3, see description).

Use cases for measured flow:

image

Capacity

Capacity consists of the following messages that are also sent as separate messages /documents. It is proposed to separate the message in separate documents that all rely on Capacity_MarketDocumet.

  • Day ahead NTC

  • Intraday NTC

  • Current NTC

  • Current mFRR ATC

Use cases for capacity:

image

Generic business process

In an NBM viewing perspective, all messages included in Planned Flow, Measured Flow and Capacity will follow this sequence as given in the figure below.

As the user case shows, the same message(s)/document(s) can be used in other internal processes, which this documentation does not cover.

image

Data model and dependencies

Figure below shows an example of application functions and their dependencies to the different flows in SN/Svk in the Fifty environment.

image

Flow

Document types, message types, process types and business types

Document Message type Definition Process type Definition Business type Definition Curv type Definition Reason Code Definition Market Agreement Type Definition

Schedule_MarketDocument

Planned flow

Total Planned Flow-TSO

A30

Cross border schedule

A39

Synchronisation process

Z88

Total Planned Flow

A05

Non-overlapping breakpoint

Schedule_MarketDocument

Planned flow

Planned Flow Power Plan Trade TSO

A30

Cross border schedule

A39

Synchronisation process

Z90

Power Plan Trade

A05 (ramped)

A01 (non-ramped)

Non-overlapping breakpoint

Sequential fixed size block

Schedule_MarketDocument

Planned flow

Planned flow Day aheadTSO

A30

Cross border schedule

A39

Synchronisation process

B68

B67

DC flow without losses.

DC flow without losses refers to the values at the exporting end of the DC line

DC flow with losses.

DC flow with losses refers to the values at the importing end of the DC line.

A01

Sequential Fixed Size Blocks

A01

Day Ahead

Schedule_MarketDocument

Planned flow

Planned Flow Intraday TSO

A30

Cross border schedule

A39

Synchronisation process.

B09

Net Position

A01

-

A07

Intraday

Schedule_MarketDocument

Planned flow

Planned Flow mFRR TSO

A30

Cross border schedule (for cross-border flows)

A39

Synchronisation process.

A97

Manual frequency restoration reserve

A03

Variable sized Block

B49

B22

[Harmonizing product codes]

FRR-M, Balancing Power
(NO: Ordinary regulation)

FRR-M, System Regulation

Schedule_MarketDocument

Planned flow

Loop Transit solved in Planned Flow Agreed Supportive Power(ASP) TSO

A30

Cross border schedule

A39

Synchronisation process

Z91

Loop transit

A05 (ramped)

Non-overlapping breakpoint

[Harmonizing product codes]

Schedule_MarketDocument

Planned flow

Planned Flow Agreed Supportive Power(ASP) TSO

A30

Cross border schedule

A39

Synchronisation process

Z92

Agreed supportive power (ASP)

A05 (incl. ramping)

Non-overlapping breakpoint

 
Z22

[Harmonizing product codes]

Supportive power

Schedule_MarketDocument

Planned flow

Planned Flow Replacement ReserveTSO

A30

Cross border schedule

A39

Synchronisation process

A46

Planned Flow Replacement ReserveTSO in use with total flow message.

A05 (incl. ramping)

Non-overlapping breakpoint

Schedule_MarketDocument

Planned flow

{planned-flow-afrr}

A30

Cross border schedule

A39

Synchronisation process

A96

Automatic frequency restoration reserve

---

Schedule_MarketDocument

Planned flow

Planned Flow Period Shift-Adjustment TSO

A30

Cross border schedule

A39

Synchronisation process

Z93

Production adjustments

A05 (incl. ramping)

Non-overlapping breakpoint

Schedule_MarketDocument

Planned flow

Expected-countertrade-TSO

A30

Cross border schedule

A39

Synchronisation process

Z89

Expected countertrade

A03

A05(POG)

Variable sized Block

MeasurementValue_MarketDocument

Measured flow

Measured Flow Point Value

A45

Measurement Value Document

A39

Synchronisation process

A64

Meter Measurement data

A02 (Point Values)

Point Value

MeasurementValue_MarketDocument

Measured flow

Measured Flow Historic TSO

A45

Measurement Value Document

Z13

Reporting / historic

A64

Meter Measurement data

A02 (Point Values)

Point Value

Capacity_MarketDocument

Capacity *

Capacity Current NTC TSO

A31

Agreed Capacity

A15

Capacity determination

A27

Net transfer capacity (NTC)

A01

Sequential fixed size block

Capacity_MarketDocument

Capacity

Capacity Day Ahead NTC TSO

A31

Agreed Capacity

A01

Day ahead

A27

Net transfer capacity (NTC

A01

Sequential fixed size block

Capacity_MarketDocument

Capacity

Capacity Intraday NTC TSO

A31

Agreed Capacity

A19

Intraday accumulated

A27

Net transfer capacity (NTC

A01

Sequential fixed size block

Capacity_MarketDocument

Capacity

mFRR ATC AOF

A31

Agreed Capacity

A15

Capacity determination

A26

Available transfer capacity (ATC)

A03

Variable sized Block

All messages marked with * have first priority and will be in a draft version of PI1.

  • Add support for products

    • Remove or wait until further notice. Not in this scope.

Requirements

This section contain Business requirements(BR), the F-prefix is the name for Flow.

Planned flow

For Planned flow, Nordic Communication Infrastructure will provide messages for the following values to FiftyONE.

Within Total Planned flow these message are needed:

Req.No. Message Sending frequency Resolution Period Comments

F-BR-1

Total Planned Flow

Resend when updated

PT1M

24 hours

In practice the curve type should be A04 with PT1M (for mFRR EAM), but that make it difficult to compare planned vs measured flow in ACE calculation. So maybe we should use A05 with PT10S
FuTm[1]:
Event based. Less than 3 min after TSO received updated data for energy exchange for 99,9% updates for a day. Not more often than each 1 min.

F-BR-2

Power Plan Trade

?

?

?

F-BR-3

Day ahead

Resend when updated

PT15M

24 hours

MNA

F-BR-4

Intraday

Resend when updated

PT15M

24 hours

IEC62325-451-2 Ed.2

Gate closure each hour.

XBID

F-BR-5

mFRR

Resend when updated

PT1M

Max 24 hours.

Only Period with mFRR exchange

A47 = Manual frequency restoration reserves (mFRR)

F-BR-6

Ramping***

Resend when updated

PT1M

Max 24 hours.

Only period with ramping

F-BR-7

Loop transit

Resend when updated

PT1M

Max 24 hours

Only period with Loop transit

Schedule_MarketDocument versus

IEC62325-451-7 : Activation_MarketDocument :

Pros: Contains - acquiring_Domain.mRID and connecting_Domain.mRID.

cons: It is not about activations,

Schedule_MarketDocument : One document with all connection bidding zones within same document.

F-BR-8

Agreed supportive power

Resend when updated

PT1M

Max 24 hours

Only period with ASP

Flow resulting from agreed supporting power

F-BR-9

RR

Resend when updated

PT1M

Max 24 hours

Only period with RR

Output from any future participation on the RR platform

F-BR-10

aFRR

Resend when updated

PT10S

Output from a future aFRR energy activation market. At present no values are available

F-BR-11

Period shift adjustments

Resend when updated

PT1M

Max 24 hours

Only period with period shift regulations

Impact of cross-border flow due to smoothing and production shifting

[1] FuTm: Follow up Target model
***Not in this Scope (PI)

Expected counter trade

For Planned flow, Nordic Communication Infrastructure will provide messages for the following values to FiftyONE.

Req. Attribute Sending frequency Resolution Period Comments

F-BR-12

Expected counted trade

Resend when updated

PT1M

24 hours

For borders with agreements regarding supportive power exchange the planned supportive power corrections should be shared.
It shall not necessarily be included in the planned flow to be used in the ACE OL calculation.

Measured flow

For Planned flow, Nordic Communication Infrastructure will provide messages for the following values to FiftyONE.

Req. Attribute Sending frequency Resolution Period Comments

F-BR-13

Measured flow

10 sec

PT10S

Max 3h

Need to clarify how to calculate measured flow; Reference side of corridor.

Must provide complete series of data, have historical data.

Must include quality attribute.

FuTm[1]: Periodic: 10 sec. Value no older than 10 sec, received at least each 10 sec for 98% of time for each QH.

Measured Flow Historic

each 3 mnutes, long term 2 hours??

10 sec

Transfer patterns as ACE OL?

[1] FuTm: Follow up Target model

Cross-border capacity

For Cross-border capacity, Nordic Communication Infrastructure will provide messages for the following values to FiftyONE.

Req. Attribute Sending frequency Resolution Period Comments

F-BR-14

Day Ahead NTC

Event driven - when data is changed

PT15M

24 Hours

Does not change after 10:00 D-1. Periode D+1

A27 NTC (Estimated capacity)

From NOIS.

F-BR-15

Intraday NTC

Event driven - when data is changed

PT15M

24 Hours

Can be updated during the day. Fixed after H-2. Periode current day plus one. D and D+1

F-BR-16

Current NTC

Event driven - when data is changed

PT15M

24 Hours

Equal to final Intra-day NTC, unless manual changes (operator ).

F-BR-17

Current mFRR ATC

Event driven - when data is changed

PT1M

Max 24 hours

Current day, up to t+1h

Same value as sent to AOF. Current mFRR ATC = Current NTC - aFRR.

** NTC = Net Transfer Capacities. (ATC = Available Transfer Capacities)

Definitions of flows and other classifications

Definition Description

Total Planned Flow

Sum of all intended exchange between bid areas.
Total planned flow includes planned exchange from energy markets as weel as agreed exchanges resulting from balancing and system operations.
Total planned flow includes ramping

Power Plan Trade (ID+DA incl. Ramping).

The power plan including ramping resulting from trades and planned actions.
Includes Day-ahead, and intra-day trade as well as loop transit flows.
The power plan trade will be the basis for the ACE OL calculation

Details on what side of an interconnector the plan should be defined for (reference side) to be agreed

Day ahead

The day-ahead market is the main market for power trading in the Nordic region. Trading flow resulting from the day-ahead market. 15-min values without ramping. Included in Power plan trade

Intraday

Trading flow resulting from the intra-day market.
15-min values without ramping
Included in Power plan trade

mFRR**

Flow from mFRR. Includes ramping
Today: Agreed exchange on mFRR bids in special situations
After introduction of the AOF: All mFRR exchange will result in a agreed flow from AOF

Ramping***

Will be discontinued. Ramping is included in the individual data series, and in the power plan.

Loop transit**

Flow resulting from agreed loop flows and transit agreement.
15-min values without ramping
Included in Power plan trade

ASP - Agreed supportive power **

Flow from agreed supportive power. Includes ramping

RR - Replacement reserve

Flow from replacement reserves exchange. Currently not in use. No plans to start using this reserve.

aFRR

Flow from aFRR exchange. Currently not in use. Data on energy exchange of aFRR will only be available once we have an AOF for aFRR as part of NBM 2nd generation

Period shift adjustments

Flow from Period shift adjustments.
Produksjonsflytting/kvartsaffär: Period shift products activated in the balancing time frame where the activation and need are in different areas.

Expected Countertrade

Expected flow from counter trade.
For example if the day ahead trade flow exceeds the physical capacity the difference is the expected counter trade volume.
Not included in the total planned flow. The counter trade wil we effectuated with one of the products (such as a transit agreement, intra-day trade, ASP, RR or mFRR)

Measured flow

Sum of all measured flow on an interconnector.

Details on what side of an interconnector the measurment should be made (reference side) to be agreed

Current NTC

Total market capacity for an interconnector.
Normally equal to Intra-day NTC, but can be (manually) updated in operations.

Day-ahead NTC

Market capacity made available for the day-ahead trade. Communicated from the TSO to the market D-1 at 10:00

Intraday NTC

Market capacity made available for the intra-day trade. Communicated from the TSO to the market throughout the intra-day trading period. Normally equal to the Day-ahead NTC, but can be updated.

Current mFRR ATC

Available capacity for mFRR trade. Input to the AOF. Normally equal to the Current NTC minus already agreed exchange (from Day-ahead, Intra-day, Loop Transit, ASP, RR).
Can be (manually) updated in operations

Harmonized Products definitions

Due to a change request for Flows, where we should not aggregate values but use separate Flows for each product. To support this we must uniquely identify these products and assign product codes for this purpose. Product codes are provided by NMEG and will be added to this list on an ongoing basis as we get values from NMEG.In the CIM document, the product code value will be used in the Reason code field without additional text support.

NMEG and ENTSOE Codes can be found here.

Generic Harmonized Code list for "Products"

This is a guide on how to implement and support combinations of supportive power components, which are different types of HVDC contributions.

To specify a contribution of HVDC power, select a corresponding business code(see list below), then select a reason code and specify out- and inDomain to specify which cable/area it used for.

Following table contains allowed Business codes:

Business Code Short Name Description

Supportive Power Components

Z91

Loop transit

Flow resulting from agreed loop flows and transit agreement.

Z92

Agreed supportive power (ASP)

Flow from agreed supportive power.

Not a part of Supportive power component.

A54

Unplanned Outage

An unplanned outage has occurred on the object in question. Not a part of Agreed Supportive Power

B60

Emergency Power control (EPC) / SPS

The TimeSeries describes the network elements managed by a Special Protection System (automation).

B67

DC flow with losses

DC flow with losses refers to the values at the importing end of the DC line.

B68

DC flow without losses

DC flow without losses refers to the values at the exporting end of the DC line.

Following table contains allowed Reason codes:

ReasonCode Short Name Description

Z22

Supportive Power

Z26

Transit

Z27

Transit Kontiskan

Suggest to remove this, only use Z26

Z28

Transit SB Long

Z50

Special

Z51

Disturbance

Z52

Transit SB Short

Z69

Shadow Auction

Z68

Emergency

B49

Balancing

B22

System

Z71

Midnight

Capacity change at midnight

Z72

Outage

Planned outage.

Z87

Transit Fennoskan: FS Loop

Z88

Comment to the Business/Reason codes above:
Z92-ASP is an actual supportive power component, it can be a part of the Z91-Loop transit, therefore we distinguish these two codes.
B67/B68 is a part of the Day-ahead result. In absence of the Day-ahead result, an estimated Day-ahead flow with reason code Z69-Shadow Auction be used as a backup.

The following matrix can then be set up:

Business Code Reason code Description

Z92

N/A

Agreed Supportive power: Standard usage.

Z92

Z50

Agreed Supportive power: Special ramp.

Z92

Z22

Agreed Supportive power:TSO-TSO exchange assistance.

Z92

B55

Agreed Supportive power:TSO-TSO exchange redispatch.

Z92

Z68

Agreed Supportive power:TSO-TSO exchange Emergency power.

Z92

B22

Agreed Supportive power for system regulation purpose:RK Special

Z92

B49

Agreed Supportive power for balancing regulation purpose: RK Balance.

Z92

Z71

Agreed Supportive power for balancing flow during planned flow drop/raise over midnight:Special ramping midnight

Z92

Z72

Agreed Supportive power for balancing flow during planned outages: Special ramping outage (RK Balance).

A54

Z51

Unplanned Outage, disturbance. The following value must be covered.

B60

N/A

Emergency protection control (EPC).

B67

Z69

Used in the absence of in Day-ahead-market connection. Shadow auction trade.

B68

Z69

Used in the absence of in Day-ahead-market connection: Shadow auction trade.

Z91

Z26

Loop transit : Transit triangle.

Z91

Z28

Loop transit: SB Loop Long.

Z91

Z52

Loop transit: SB Loop Short.

Z91

Z87

Transit Fennoskan: FS Loop

Z91

Z88

Transit DC loop Poland: PL Loop

Harmonized product codes

Examples using new codes in accordance with existing NOIS codes.

NOIS Code Description BusinessType ReasonCode Short Name OutArea InArea

FS00000000000004

Transit Finland Norge

Z91

Z26

Transit

10YFI-1--------U

10YNO-4--------9

FS00000000000032

Transit Finland - Finland Syd-Sverige-Finland Nord - (sv syn Finland Syd) - akt MWh

Z91

Z26

Transit

10YFI-2--------K

10YFI-1--------U

FS00000000000033

Supportive Power Special FI→SE1 MWh

Z92

Z50

Supportive Power Special

10YFI-1--------U

10Y1001A1001A44P

FS00000000000035

Supportive Power Disturbance FI→SE1 MWh

Z92

Z51

Supportive Power Disturbance

10YFI-1--------U

10Y1001A1001A44P

FS00000000000039

Supportive Power Special FI→SE3 MWh

Z92

Z50

Supportive Power Special

10YFI-1--------U

10Y1001A1001A46L

FS00000000000041

Supportive Power Disturbance FI→SE3 MWh

Z92

Z51

Supportive Power Disturbance

10YFI-1--------U

10Y1001A1001A46L

FS00000000000043

Transit Åland Energi

Z91

Z26

Transit

?

?

NS00000000000003

Transit trekant Kontiskan Svensk syn - godkänd MWh

Z91

Z26

Transit

10YDK-1--------W

10Y1001A1001A46L

NS00000000000004

Transit omfördelning Kontiskan Svensk syn - godkänd MWh

Z91

Z27

Transit Kontiskan

10YDK-1--------W

10Y1001A1001A46L

NS00000000000026

Transit DC-loop Själland-Sverige-Norge (svensk syn mot Själland SB LONG) MWH

Z91

Z28

Transit SB Long

10YNO-2--------T

10YDK-1--------W

NS00000000000033

Raf netto - avropad energi - Oslo (Norge) MWh ? Transit Finlan Norge

Z91

?

NS00000000000044

Supportive Power Special NO4→SE1 MWh Systemreglering

Z92(Old:A46)

Z50

Supportive Power Special

10YNO-4--------9

10Y1001A1001A44P

NS00000000000046

Supportive Power Disturbance NO4→SE1 Mwh Annan orsak

Z92(Old:A46)

Z51

Supportive Power Disturbance

10YNO-4--------9

10Y1001A1001A44P

NS00000000000048

Supportive Power Special NO4→SE2 MWh Systemreglering

Z92(old:A46)

Z50

Supportive Power Special

10YNO-4--------9

10Y1001A1001A44P

NS00000000000050

Supportive Power Disturbance NO4→SE2 MWh Annan orsak

Z92

Z51

Supportive Power Disturbance

10YNO-4--------9

10Y1001A1001A45N

NS00000000000052

Supportive Power Special NO3→SE2 MWh Systemreglering

Z92

Z50

Supportive Power Special

10YNO-3--------J

10Y1001A1001A45N

NS00000000000054

Supportive Power Disturbance NO3→SE2 MWh Anna orsak

Z92

Z51

Supportive Power Disturbance

10YNO-3--------J

10Y1001A1001A45N

NS00000000000056

Supportive Power Special NO1→SE3 MWh Systemreglering

Z92

Z50

Supportive Power Special

10YNO-1--------2

10Y1001A1001A46L

NS00000000000058

Supportive Power Disturbance NO1→SE3 MWh Annan orsak

Z92

Z51

Supportive Power Disturbance

10YNO-1--------2

10Y1001A1001A46L

SED0000000000004

Transit DC-loop Polen-Sverige-Själland (svensk syn mot Polen) MW

Z91

Z26

Transit

10YPL-AREA-----S

10YDK-1--------W

SED0000000000005

Underlag dygnsavstämning RAF - SvK - DK2 ASP Special MWh

SED0000000000007

Underlag dygnsavstämning RAF - SvK - DK2 Gräns ASP Disturbance MWh

?

SED0000000000011

Körplan fysikaliskt utbyte Område 4/Bornholm MWh

SED0000000000013

Transit DC-loop Själland-Sverige-Norge (svensk syn mot Själland SB Long) MWH

Z91

Z28

Transit SB Long

10YDK-1--------W

10YNO-2--------T

SED0000000000014

Transit Danmark Själland-Sverige-Jylland Stora Bält (svensk syn mot Själland SB SHort) MWh

Z91

Z52

Transit SB Short

10YDK-2--------M

10YDK-1--------W

SWD0000000000003

Transit Danmark Själland-Sverige-Jylland övrigt (svensk syn mot Själland) (MW)

Z91

Z26

Transit

10YDK-2--------M

10YDK-1--------W

SWD0000000000004

Transit omfördelning Kontiskan Svensk syn - godkänd MW

Z91

Z27 Z26

Transit Kontiskan

10YDK-1--------W

10Y1001A1001A46L

SWD0000000000006

Underlag dygnsavstämning RAF - SvK - DK1 ASP Balans DK1 MWh

SWD0000000000008

Underlag dygnsavstämning RAF - SvK - DK1 ASP Special MWh

SWD0000000000010

Underlag dygnsavstämning RAF - SvK - DK1 Gräns ASP Disturbance MWh

SWD0000000000012

SE3-DK1 Ramping

SWD0000000000014

SB Loop Short

Z91

Z52

Transit SB Short

10YDK-2--------M

10YDK-1--------W

How to specify who ordered

If needed in the future, this is how to indicate which TSO needed the ASP.
The TSO who placed the order is the TSO that needs help with a possible imbalance.
This can be given by in Schedule_MarketDocument by the attributes, in_MarketParticipant.mRID or out_MarketParticipant.mRID.

NOTE

In future it will be preferred using PlannedResourceSchedule_MarketDocument schema. The attributes will be more descriptive for the purpose, the attribute acquiring_Domain.mRID used to indicate which TSO ordered. FlowDirection.direction indicate the direction of energy flow.

Terms and Definitions

Acronym Term Definition Ref.

ASP

Agreed supportive power

HVDC

aFFR

Automatic frequency restoration reserves

FRR that can be activated by an automatic control device designed to reduce the Frequency Restoration Control Error (FRCE) to zero.

Entso-e

AOF

Activation Optimisation Function

EMS

Energy Management System

IEC-60870-6-503

MMS

Manufacturing Message Specification

IEC-60870-6-503

mFRR

Manual frequency restoration reserves

Active power reserves that may be manually activated, available to restore system frequency to the nominal frequency and, for a synchronous area consisting of more than one LFC area, to restore power balance to the scheduled value.

Entso-e

RGCE

Regional Group Continental Europe

Entso-e

RR

Replacement reserves

The reserves used to restore/support the required level of FRR to be prepared for additional system imbalances. This category includes 164operating reserves with activation time from Time to Restore Frequency up to hours.

Ramping

Loop transit

Change in flow between two bidding zones compared to trade (DA+ID) flow. This is "forced" change in flow from one or more HVDC-connections. Does not include ramping.

Period shift adjustments

TASE.2

Telecontrol Application Service Element 2,

Telecontrol Application Service Element 2, also known as Inter-Control Centre
Communications Protocol (ICCP).

IEC-60870-6-503

UBEEP

Updated Balancing Energy Exchange Plans (UBEEP)

UBEEPs main task is to update other systems about changes in plans due to ordered mFRR activations.

Analyse Updated Balancing Energy Exchange Plans (UBEEP)

Clarifications

This section intends to clarify definitions can be misinterpreted and thus can lead to incorrect implementation.

These are general principles and should be followed unless otherwise clarified

These definitions help us to remove certain uncertainties and to provide a common understanding of what the attributes will deliver.

Flow direction

If flowdDirection is supported in a schema then signed values must not be used, otherwise the following rules should be followed:

These are clarifications and principles we use for planned flow processes. These definitions help us to remove certain uncertainties and to provide a common understanding of what the attributes will deliver.

In/Out Domain Definition:

in_Domain.mRID

AreaID_String

The unique identification of the domain.

--- The area where the product is being delivered otherwise a negative value is given, then it is the extracted area.

out_Domain.mRID

AreaID_String

The unique identification of the domain.

--- The area where the product is being extracted delivered otherwise a negative value is given, then it is the delivered area.

Figure flow.

image

Curve types

Curve types and definitions. Curves and Time series are related to each other and is important to understand how to read and use these data. Detailed description about usage and reference to table below, is this ENTSOE document Timeseries-curve-types_v1r1.pdf

Code Title Example Description

A01

Sequential fixed size block
image

The curve is made of successive Intervals of time (Blocks) of constant duration (size), where the size of the Blocks is equal to the Resolution of the Period.

Example

<!--Example is given according to example image.-->

<Period>

<timeInterval>

<start>2020-04-23T23:00Z</start>

<end>2020-04-24T23:00Z</end>

</timeInterval>

<!-- If Curve type A01 we have the requirement of constant duration (size), and therefor we cannot select independent size by using PT1M , but fixed size and sequential increase of 1.

As given in example, resolution is fixed to PT4H -->

<resolution>PT4H</resolution>

<Point>

<position>1</position>

<quantity>50.00</quantity>

</Point>

<Point>

<position>2</position>

<quantity>100.00</quantity>

</Point>

<Point>

<position>3</position>

<quantity>100.00</quantity>

</Point>

<Point>

<position>4</position>

<quantity>150.00</quantity>

</Point>

<Point>

<position>5</position>

<quantity>150.00</quantity>

</Point>

<Point>

<position>6</position>

<quantity>0.00</quantity>

</Point>

<Point>

<position>7</position>

<quantity>0.00</quantity>

</Point>

</Period>

A02

Point
image

The curve is made of successive instants of time (Points).

Example

<!--Example is given according to example image.-->

<Period>

<timeInterval>

<start>2020-04-23T23:00Z</start>

<end>2020-04-24T23:00Z</end>

</timeInterval>

<resolution>PT1M</resolution>

<Point>

<position>1</position>

<quantity>50.00</quantity>

</Point>

<Point>

<position>241</position>

<quantity>100.00</quantity>

</Point>

<Point>

<position>481</position>

<quantity>100.00</quantity>

</Point>

<Point>

<position>961</position>

<quantity>150.00</quantity>

</Point>

<Point>

<position>1201</position>

<quantity>0.00</quantity>

</Point>

</Period>

A03

Variable sized Block
image

The curve is made of successive Intervals of time (Blocks) of variable duration (size), where the end date and end time of each Block are equal to the start date and start time of the next Interval. For the last Block the end date and end time of the last Interval would be equal to EndDateTime of TimeInterval.

Example

<!--Example is given according to example image.-->

<Period>

<timeInterval>

<start>2020-04-23T23:00Z</start>

<end>2020-04-24T23:00Z</end>

</timeInterval>

<resolution>PT1M</resolution>

<Point>

<position>1</position>

<quantity>50.00</quantity>

</Point>

<Point>

<position>241</position>

<quantity>100.00</quantity>

</Point>

<Point>

<position>721</position>

<quantity>150.00</quantity>

</Point>

<Point>

<position>961</position>

<quantity>50.00</quantity>

</Point>

</Period>

A04

Overlapping breakpoint
image

The curve is made of successive Intervals of time of variable duration (size), where the end date and end time of each interval are equal to the start date and start time of the next Interval.

Example

<!--Example is given according to example image.-->

<Period>

<timeInterval>

<start>2020-04-23T23:00Z</start>

<end>2020-04-24T17:00Z</end>

</timeInterval>

<resolution>PT1M</resolution>

<Point>

<position>1</position>

<quantity>50.00</quantity>

</Point>

<Point>

<position>661</position>

<quantity>100.00</quantity>

</Point>

<Point>

<position>721</position>

<quantity>100.00</quantity>

</Point>

<Point>

<position>1081</position>

<quantity>100.00</quantity>

</Point>

</Period>

<Period>

<timeInterval>

<start>2020-04-24T17:00Z</start>

<end>2020-04-24T23:00Z</end>

</timeInterval>

<resolution>PT1M</resolution>

<Point>

<position>1</position>

<quantity>0.00</quantity>

</Point>

<Point>

<position>241</position>

<quantity>0.00</quantity>

</Point>

<Point>

<position>121</position>

<quantity>50.00</quantity>

</Point>

</Period>

A05

Non-overlapping breakpoint
image

This curve is a restriction of the curve type A04, i.e. overlapping breakpoints. The restriction is that a single Period is allowed.

Example

<!--Example is not given according to example image.-->

<Period>

<timeInterval>

<start>2020-04-23T23:00Z</start>

<end>2020-04-24T23:00Z</end>

</timeInterval>

<resolution>PT1M</resolution>

<!--If need of 5 minutes intervals -->

<Point>

<position>1</position>

<quantity>748.00</quantity>

</Point>

<Point>

<position>6</position>

<quantity>748.00</quantity>

</Point>

<!--If adjustment with ramping and 5 minutes intervals -->

<Point>

<position>11</position>

<quantity>900.00</quantity>

</Point>

<Point>

<position>1441</position>

<quantity>900.00</quantity>

</Point>

</Period>

References:

Definitions at ENTSO-E: electronic-data-interchange-edi-library

Description: ENTSO-E: Timeseries-curve-types_v1r1.zip

Diagrams

Measured flow

|image

References

Documentation and XSDs

Documentation and XSDs can be found here Attachments.

MARI IG can be found on ENTSOE by this link, MARI IG v1.0.

Message Definitions

Message definitions and document versions

Dataobject Document Schema version

Total Planned Flow-TSO

Schedule_MarketDocument

5.2

Planned Flow Power Plan Trade TSO
(ID+DA incl. Ramping).

Schedule_MarketDocument

5.2

Planned flow Day aheadTSO
Not ramped

Schedule_MarketDocument

5.2

Planned Flow Intraday TSO
Not ramped

Schedule_MarketDocument

5.2

Planned Flow mFRR TSO

Schedule_MarketDocument

5.2

Loop Transit solved in Planned Flow Agreed Supportive Power(ASP) TSO

Schedule_MarketDocument

5.2

Planned Flow Agreed Supportive Power(ASP) TSO

Schedule_MarketDocument

5.2

Planned Flow Replacement ReserveTSO

Schedule_MarketDocument

5.2

{planned-flow-afrr}

Schedule_MarketDocument

5.2

Planned Flow Period Shift-Adjustment TSO

Schedule_MarketDocument

5.2

Expected-countertrade-TSO

Schedule_MarketDocument

5.2

Measured

Measured Flow Point Value

measurementdata

0.8

Measured Flow Historic TSO

measurementdata

0.8

Capacity

Capacity Current NTC TSO

Capacity_MarketDocument

8.0

Capacity Day Ahead NTC TSO

Capacity_MarketDocument

8.0

Capacity Intraday NTC TSO

Capacity_MarketDocument

8.0

mFRR ATC AOF

Capacity_MarketDocument

8.0