nordic tso message exchange model … · nordic tso scheduling and ancillary services process...

BRS (BUSINESS REQUIREMENT SPECIFICATION)

A MODEL FOR THE

NORDIC TSO

SCHEDULING AND ANCILLARY

SERVICES PROCESS

Business process: Nordic TSO Schedules

document exchange

Version: 2.1.A

Status: Approved by NEG

Date: February 7th, 2014

Nordic TSO Scheduling and Ancillary Services Process

Nordic Ediel Group Page: 2

CONTENT

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

1.1 BACKGROUND .................................................................................................................................................... 3 1.2 NORDIC ENERGY DOMAIN MODEL .................................................................................................................... 3 1.3 POSSIBLE FURTHER DEVELOPMENTS .................................................................................................................. 3 1.4 PROJECT ORGANISATION .................................................................................................................................... 3 1.5 REFERENCES ...................................................................................................................................................... 4 1.6 TERMS................................................................................................................................................................ 4 1.7 CHANGE LOG ..................................................................................................................................................... 5

2 PLANNING .............................................................................................................................................................. 6

2.1 PLANNING IN THE OVERALL CONTEXT (DOMAIN MODEL) .................................................................................. 6 2.2 BREAKDOWN OF THE SCHEDULING PROCESS WITHIN THE PLANNING PHASE ....................................................... 6

3 OVERVIEW OF THE NORDIC SCHEDULING PROCESS ............................................................................. 8

3.1 SCHEDULE SYSTEM INFORMATION FLOWS .......................................................................................................... 9 3.2 SCHEDULE SYSTEM INFORMATION REQUIREMENTS ............................................................................................ 9

3.2.1 Market schedules ........................................................................................................................................ 10 3.2.2 Operational schedules ................................................................................................................................ 11 3.2.3 Overview of Trading Models ...................................................................................................................... 13 3.2.4 Outages ....................................................................................................................................................... 14

4 HARMONISED ROLES USED IN “EXCHANGE SCHEDULES” ................................................................. 16

5 BUSINESS ENTITY VIEW, EXCHANGE SCHEDULES ................................................................................ 19

5.1 BUSINESS ENTITY VIEW, BUSINESS ENTITIES ................................................................................................... 19 5.2 BUSINESS ENTITY VIEW, BUSINESS ENTITY STATES ......................................................................................... 20

6 PROCESS AREAS WITHIN THE NORDIC SCHEDULING PROCESS....................................................... 22

6.1 PROCESS AREA: EXCHANGE MARKET SCHEDULES ............................................................................................ 22 6.1.1 Process area: Match schedules (Denmark and Sweden) ............................................................................ 23

6.2 PROCESS AREA: EXCHANGE PRODUCTION PROGNOSES (DENMARK) ................................................................ 24 6.3 PROCESS AREA: EXCHANGE OPERATIONAL SCHEDULES ................................................................................... 26 6.4 PROCESS AREA: EXCHANGE CORRIDOR AND CUT CORRIDOR SCHEDULES ........................................................ 28 6.5 PROCESS AREA: EXCHANGE ANCILLARY SERVICES, INCLUDING RESERVE RESOURCES .................................... 29 6.6 PROCESS AREA: PUBLISH OUTAGES .................................................................................................................. 30

6.6.1 Outage information modification ................................................................................................................ 30 6.6.2 Outage information deletion ....................................................................................................................... 30

7 BUSINESS DATA VIEW ...................................................................................................................................... 31

7.1 DOCUMENT RELATED TO MARKET SCHEDULES ................................................................................................ 31 7.1.1 ESS Schedule Document ............................................................................................................................. 31 7.1.2 ESS Anomaly Report ................................................................................................................................... 35 7.1.3 ESS Confirmation Report ............................................................................................................................ 38

7.2 DOCUMENTS RELATED TO OPERATIONAL SCHEDULES ..................................................................................... 41 7.2.1 ERRP Planned Resource Schedule ............................................................................................................. 41 7.2.2 ERRP Resource Schedule Confirmation Report ......................................................................................... 47

7.3 OUTAGE DOCUMENT ........................................................................................................................................ 50 7.3.1 Outage document description ..................................................................................................................... 50 7.3.2 Attribute usage ............................................................................................................................................ 51

8 BUSINESS RULES ................................................................................................................................................ 54

8.1 BALANCE RESPONSIBLE PARTY DEFINITION .................................................................................................... 54 8.2 GENERAL GROUND RULES ................................................................................................................................ 54

APPENDIX A COMMUNICATION OUT OF THE NORDIC AREA ................................................................ 56

A.1 BALANCE RESPONSIBLE SCHEDULE TO SYSTEM OPERATOR (SO) BETWEEN DENMARK AND GERMANY ......... 56

APPENDIX B AN EXAMPLE OF TECHNICAL IMPLEMENTATION ......................................................... 57

B.1 MARKET SCHEDULE DOCUMENTS TO/FROM NOIS ........................................................................................... 57 B.2 OPERATIONAL SCHEDULE DOCUMENTS TO/FROM NOIS .................................................................................. 64

http://www.ediel.org/hjem.htm



1 INTRODUCTION

1.1 Background

Today the Nordic TSOs exchange documents based on several different formats and standards, such as Ediel

(DELFOR/MSCONS), NOIS XML documents based on ENTSO-E IGs and Excel documents. In addition,

the Nordic TSOs have communications towards other European countries, such as Germany, the Netherlands

and Poland, using even more standards, such as NorNed xml and ENTSO-E standards.

For efficiency reasons, the four Nordic TSOs and Nord Pool Spot have set up a project for migration of the

document exchanges towards one common document standard. The project is run as a Nordic project with

the Nordic Ediel Group as the steering group. The aim is to define document exchange models that can be

used for all document exchanges between the Nordic TSOs and Nord Pool Spot, within the framework of the

ENTSO-E implementation guides. Note that this does not necessarily reflect the documents exchanged

today.

This document is a Business Requirement Specification (BRS) detailing the document exchanges related to

schedules, prognosis and Ancillary services (reserve resources) in the Nordic countries. The focus of the

document is the business aspects of the document exchanges and the basis for the document is the ENTSO-E

ESS and ERRP Implementation Guides [1], together with the ebIX®, EFET and ENTSO-E Harmonised role

model [3]. When implementing the BRS, the ENTSO-E ESS and ERRP Implementation guides and the

related ENTSO-E XML schemas should be used.

1.2 Nordic Energy Domain Model

A Nordic Energy market Domain model, giving an overall overview of the structure and processes used in

the Nordic Energy market, can be found in [11].

1.3 Possible further developments

Consumption prognoses

o Norway and Sweden: Only internal process within the TSOs.

o Denmark: Internally generated within the TSO. The Consumption responsible parties can

optionally send these prognoses on an hourly basis, the day before.

Weather prognoses

1.4 Project organisation

The project is organised as a project group within Nordic Ediel Group (NEG), with the following members at

the time of publication:

Steering group: Nordic Ediel Group (NEG):

Christian Odgaard, Energinet.dk, [email protected]

Christian Hoang Huy Le, Statnett, [email protected]

Jari Hirvonen, Fingrid, [email protected]

Oscar Ludwigs, Svenska Kraftnät, [email protected]

Tor Åge Halvorsen, Nord Pool, [email protected]

Tor Heiberg, Statnett, [email protected]

Convenor: Jon-Egil Nordvik, Statnett, [email protected]

Secretary: Ove Nesvik, EdiSys, [email protected]

Project members: Christian Hoang Huy Le, Statnett, [email protected]

Christian Odgaard, Energinet.dk, [email protected]

Eveliina Ishii, Nord Pool Spot, [email protected]

Hanna Blomfelt, Nord Pool Spot, [email protected]

Jari Hirvonen, Fingrid, [email protected]


mailto:[email protected]















Ole Fredsø Weigelt, Energinet.dk, [email protected]

Jan Owe, Svenska Kraftnät, [email protected]

Roar Grindstrand, Statnett, [email protected]

1.5 References

[1] ENTSO-E implementation guides, see https://www.entsoe.eu/resources/edi-library/:

ENTSO-E Modelling Methodology (EMM)

ENTSO-E UCTE (Continental Europe) SO-SO Process

ENTSO-E Scheduling System, ESS

ENTSO-E Settlement Process, ESP

ENTSO-E Reserve Resource Planning, ERRP

ENTSO-E Capacity Allocation and Nomination, ECAN

ENTSO-E Publication Document, EPD

ENTSO-E Acknowledgement process

[2] ECP (Energy communication platform) Functional Specifications

[3] The Harmonised Role Model, ENTSO-E, ebIX® and EFET, see

https://www.entsoe.eu/index.php?id=73

[4] UN/CEFACT Unified Modelling Methodology (UMM), see http://umm-dev.org/

[5] UN/CEFACT XML Naming and Design Rules (NDR), see

http://www.unece.org/cefact/xml/xml_index.html

[6] ebIX Modelling methodology and process models (EMD), see http://www.ebix.org/

[7] Ediel Implementation guides, see http://www.ediel.org/

[8] Nordic Ediel Group, Common Nordic XML rules and recommendations, see http://www.ediel.org/

[9] Nordic Ediel Group, BRS for the Nordic TSO Determine transfer capacity model, see

http://www.ediel.org/

[10] Nordic Ediel Group, BRS for the Nordic trading system, see http://www.ediel.org/

[11] Nordic Energy Market Domain Model, see http://www.ediel.org/

[12] Agreement regarding operation of the interconnected Nordic power system (System Operation

Agreement)

http://www.entsoe.eu/fileadmin/user_upload/_library/publications/nordic/operations/060613_entso

e_nordic_SystemOperationAgreement_EN.pdf

1.6 Terms

In this document the term Ancillary services is used for services needed to maintain a stable power system,

typically used for instant handling of changes in consumption and outages in generation and transmission.

The Ancillary services consist of primary, secondary and tertiary reserves, characterised by their activation

time. The term Ancillary services are used as a synonym to Reserve resources, as is the term used in the

ENTSO-E Scheduling System [1].

The term document is used instead of message, when this is applicable. However when referencing ENTSO-

E document names, the ENTSO-E name will be used, e.g. message, report or document.

The term Market schedules is used instead of the ENTSO-E term Schedules when this is applicable and

Operational schedules is used instead of the ENTSO-E term Resource schedules when this is applicable.

When the term TSO is used in this document, it may include Nord Pool Spot.

In this document, the term Corridor is used for a group of power cables/lines. In the ENTSO-E ECAN IG,

the term Connecting line is used with similar meaning.





https://www.entsoe.eu/index.php?id=73

http://umm-dev.org/

http://www.unece.org/cefact/xml/xml_index.html

http://www.ebix.org/






http://www.entsoe.eu/fileadmin/user_upload/_library/publications/nordic/operations/060613_entsoe_nordic_SystemOperationAgreement_EN.pdf

http://www.entsoe.eu/fileadmin/user_upload/_library/publications/nordic/operations/060613_entsoe_nordic_SystemOperationAgreement_EN.pdf



1.7 Change log

Ver/rel/rev Changed by Date Changes

2.1.A Ove Nesvik 20140207 ESS Confirmation Report:

o Reason codes (Time Series Confirmation level)

A01 and A02 are replaced by:

A09 Time series not matching

A20 Time Series fully rejected

A63 Time Series modified

o Reason codes (Imposed time series level):

A09 has been removed

A30 has been added

o Reason codes (Interval level):

A43 and A44 are added

Class diagrams include the complete ENTSO-E class

diagram and the attribute usage tables exclude the

elements not used in the Nordic countries

Error corrections and addition of clarifying text

2.0.B Ove Nesvik 20130930 The code A23, Balance management (Used for

operational balance) is removed from the production

and consumption schedule.

Business type A90 Solar is added where relevant

Clarifications and error corrections

2.0.A Ove Nesvik 20130428 Complete recast of the document




2 PLANNING

2.1 Planning in the overall context (Domain model)

The Domain model describes the main business process areas needed to have a well-functioning energy

market. The model is important for having a common and agreed understanding on how the energy market

works as a basis for development of common methods for exchange of information.

Figure 1: UseCase diagram: Domain model

For a more elaborated description of the process include in the domain model, see [11].

2.2 Breakdown of the scheduling process within the planning phase

In the rest of this document the Business area (UseCase) Schedule resources from the Business area Plan is

further elaborated.

Figure 2: UseCase diagram: The Nordic planning process

The Determine transfer capacity process is documented in a separate BRS, see [8].




The Process area Plan, outlined in Figure 2, concerns principally schedules and prognosis supplied by the

different Balance Responsible parties and the System Operator for a given Market Balance Area or a group

of Market Balance Areas. It also deals with the exchange of schedules between two Market Balance Areas

via System Operators and the Market information aggregator. Some of the resulting schedules are afterwards

sent to the Imbalance Settlement Responsible after validation, to be used in the Settlement process.

Furthermore, the planning phase, include exchanges related to Reserve resources and Publication of outages.

Figure 3: Activity diagram: The Nordic planning process




3 OVERVIEW OF THE NORDIC SCHEDULING PROCESS

Figure 4: UseCase diagram: The Nordic Scheduling process

In Figure 4 the Nordic scheduling process is further decomposed into Business areas and Process areas.

Each of these Business areas and Process areas will be further described below.

The Balance Responsible parties, operating within one or several Market Balance Areas sends schedules and

prognosis to the System Operator, ensuring the correct operation of one or several Market Balance Areas.

The System Operator sends the schedules to the Market information aggregator for validation and

publication.

The basic principle upon which this phase has been based is that all the trades between two Balance

Responsible parties must be notified and coherent. For each Market Balance Area all the “in” flows should

balance with all the “out” flows. In the case of imbalance, the System Operator must manage the imbalance

prior to the operation phase.

In this phase also the publication of outages are handled.




Figure 5: Activity diagram: The Nordic Scheduling process

3.1 Schedule system information flows

The schedule document transmission cycle is composed of the following phases:

1. The initial transmission of the schedule document to the System Operator. During this phase the

document is verified for coherence independently of all the schedule documents that have been

transmit by other parties. This phase verifies the coherence of the time series within the document.

The phase ends with the transmission to the sender of a positive or negative acknowledgement of the

time series received and a transmission of the validated schedules to the Market information

aggregator.

2. The matching validation (only in Denmark and Sweden) can be carried out on the time series within

a document once the time series from the complementary parties has been received. If a time series is

found not to match, an anomaly document is transmitted to all the involved parties informing them

of the problem. Time series found to be in error need to be retransmitted via the retransmission of the

applicable schedule document containing the corrected time series.

3. In the third phase, the System Operator informs the Market information aggregator about relevant

received schedules and prognosis. The Market information aggregator is responsible for publication

of the information.

4. In the last phase, the System Operator (Denmark and Sweden) or the Balance Responsible parties

(Finland and Norway) sends the schedules to the ImBalance Responsible parties as input to the

Settlement process.

In addition, the planning phase includes the publication of planned outages.

Related documents are defined according to the UMM Business Data View [3], see chapter 7.

3.2 Schedule system information requirements

The sequence diagrams in Figure 6 and Figure 9 outlines the information that is exchanged between the

different actors in the planning phase of the Nordic energy market scheduling process. The sequence diagram

in Figure 6 outlines the market schedules, which are used in an economic settlement, while the sequence

diagram in Figure 9 outlines the operational schedules used for operational purposes. The information flows




concern essentially the day-ahead and intraday scheduling process as seen from a Market Balance Area

administered by a System Operator and connected to another Market Balance Area administered by an

external System Operator.

3.2.1 Market schedules

Trade can take place between the Market Balance Areas and the transmission capacity between the areas is

allocated to the Balance Responsible parties by the Transmission capacity allocator, see [8].

The Nordic market is relatively simple compared to the typical market structure in central Europe and

requires a simple subset of the ENTSO-E sequence diagrams, see [1].

In Denmark and Sweden, the Balance Responsible parties will inform their System Operator of the bilateral

trades they have carried out within a Market Balance Area. In Denmark, these purchases and sales will

initially be controlled for coherence and if correct, the Balance Responsible parties will be informed by the

System Operator that the schedule has been accepted for processing. In the case of error, both the System

Operator in Denmark and Sweden will inform the Balance Responsible party of the errors through an

anomaly report. The Balance Responsible party may then resubmit the schedules with the necessary

corrections. After cut-off time the System Operator in Denmark and Sweden will send the schedules to the

Imbalance Settlement Responsible, to be used in the Settlement process.

In Finland and Norway the Balance Responsible parties will send their market schedules directly to the

Imbalance Settlement Responsible, to be used in the Settlement process.

To close the process, relevant schedules are sent to the Imbalance Settlement Responsible party. This process

is not covered in this guide.

In addition the System Operators (Denmark and Sweden) exchange cross border market schedules to System

Operators outside of the Nordic area, see arrow 6 in Figure 6.




Figure 6: Sequence diagram of prognosis, market schedules and matching documents (ESS)

Comments to the diagram:

Arrow 3, Market schedules from Balance Responsible parties to the Imbalance Settlement

Responsible, used in Finland and Norway, is seen as a part of the Settlement process and will not be

further elaborated in this document.

3.2.2 Operational schedules

The Continental-System maintains the load-frequency control through the use of primary, secondary and

tertiary control to stabilise the interconnected system.

The Nordic system is stabilised primarily through frequency control. Since the Nordic system is connected

by DC-Links to the Continental European system, their different control mechanisms do not influence one

another. Independent from the control philosophies used, system control is done by a number of reserve

products that have become part of a liberalised market in almost all European countries.




System balancing

Imbalance settlementSystem control

Continental European

Primary Control:Activation criteria:

Deviation of frequencyAutomatic Activation

Secondary Control:Activation criteria:

Deviation of power and frequency*Automatic Activation

Tertiary Control:Activation criteria:

To restore secondaryReserve Manual Activation (SATCR, DATCR)

Nordic

Primary Control (FCR-N):Activation criteria:

Deviation of frequency Due to consumption**Automatic Activation

Primary Control (FCR-D):Activation criteria:

Deviation of frequency due to disturbance**Automatic Activation

* Refer to the RGCEOperational Handbook policy 1 for the definition of power and frequency error .

** Refer to the Regional Group Nordic guide for the definitions of disturbance and consumption

Tertiary Control (FRR-M):Activation criteria:

To restore secondary reserve Manual Activation (DATCR)

Secondary Control (FRR-A):Activation criteria:

Deviation of frequency Automatic Activation

Figure 7: Continental Europe and Nordic operational schedules differences

The reserve control mechanisms in the operational sense of the Continental European system and the Nordic

system are outlined in the above diagram.

To correctly handle load/generation balance prognosis it has become essential to exchange an ever-growing

amount of information between all involved parties. So much so that the historical phone operations are no

longer feasible. The open market requirements demand that the non-discrimination of information also plays

its part with added complexity. Amongst the primary requirements is the necessity to provide for energy

reserves in order to respond to unexpected events to keep the electricity system operational.

Three types of reserve are collected together in order to guarantee an operational network:

The primary reserve is instantaneous and is activated automatically as a function of the frequency

or to be more exact, the deviation from 50 Hz. The settings of the generators define how much they

contribute when there is a frequency deviation.

The secondary or fast reserves are reserves that within 15 minutes shall be able to eliminate the

unbalance between generation and load and thus re-establish the primary or instantaneous reserve.

The tertiary or slow reserve shall have such qualities that it can replace the fast reserves.

Economical judgement is taken into account when decision is taken regarding the speed of the slow

reserves. The activation of tertiary reserves is handled manually.

In the future the use of secondary control, Frequency Restoration Reserves, Automatic (FRR-A, earlier

LFC), will increase. Secondary control is used in Denmark and planned implemented in Sweden and

Norway by 2012-2013.




3.2.3 Overview of Trading Models

The ENTSO-E Task Force Balance Management (TF BM) has developed several contractual models which

describe how the trading of balancing services across borders could be facilitated. This section provides an

overview of two of these models, covering the roles and responsibilities of each participant. The involved

participants are the Resource Providers (RP) and the System Operators (SO).

The principal role in these models is that of a Resource Provider which is defined as “A role that manages a

resource object and provides the schedules for it”. A Resource Object is defined as being “A resource that

can either produce or consume energy and that is reported in a schedule”.

The two models that have been developed are:

Model 1 – System Operator - Resource Provider, not used in the Nordic area and not further

described in this document.

Model 2 – System Operator - System Operator

Model 2 (System Operator – System Operator)

The main principle behind model 2 is that System Operators will contract for the provision of balancing

services to each other. Each System Operator will then be responsible for taking the necessary action in his

own area to deliver the balancing service to the other System Operator.

Imbalance SettlementArrangements

Imbalance SettlementArrangements

Reserve object

System operator

Resource provider

Reserve object

System operator

Resource provider

Area 1 Area 2

Figure 8: Contractual Arrangements for Trading Balancing Services Using Model 2

The key features of this model, as outlined in the diagram in Figure 8, are:

The System Operators of Area 1 and Area 2 are different. They are responsible for balancing their

own area

The Resource Provider’s Reserve Object in Area 1 is physically connected to the network controlled

by the System Operator of Area 1 (same arrangement in Area 2)

Each area has its own set of electricity market rules, including those relating to imbalance settlement

The Resource Provider’s Reserve Object in Area 1 may provide balancing services for the System

Operator of Area 1

The Resource Provider in Area 1 shall not provide balancing services directly to the System

Operator of Area 2




The System Operator of Area 1 may contract with the System Operator of Area 2 to provide

Balancing Services (and vice versa)

The System Operator of Area 1 is responsible for taking the necessary action in his own area to

deliver balancing service to the System Operator of Area 2 and vice versa.

Figure 9: Sequence diagram of operational schedules

3.2.4 Outages

The System Operator has a complete overview of the tie line maintenance and operation ̧and is in a position

to provide a coherent picture of the situation at a given instance in time. Tie line maintenance and operation

is carried out at two levels, the first with the establishment of a tie line maintenance program plan, the second

during operation with the discovery of a tie line outage. The System Operator informs the Market

Information Aggregator of outages in the system.

The Market Information Aggregator, who in the Nordic countries is played by NOIS, is the one who makes

the information available to the public.




Figure 10: Sequence diagram of outages

The sequence diagram in Figure 2 outlines the typical context where outage information is sent to the Market

Information Aggregator following a particular activity such as the establishment of a planned maintenance

program for tie lines or an unexpected outage of a tie line.




4 HARMONISED ROLES USED IN “EXCHANGE SCHEDULES” In Figure 11 and definitions below the relevant parts of the ebIX, EFET and ENTSO-E Harmonised role

model are outlined.

Figure 11: Outline of the Harmonised role model within the scope of Nordic scheduling process

Definitions (from the ebIX, EFET and ENTSO-E Harmonised role model) :

Balance Responsible party: A party that has a contract providing financial security and

identifying balance responsibility with the Imbalance Settlement

Responsible of the Market Balance Area entitling the party to

operate in the market. This is the only role allowing a party to buy or

sell energy on a wholesale level.

Additional information:

The meaning of the word "balance" in this context signifies that that

the quantity contracted to provide or to consume must be equal to

the quantity really provided or consumed. Such a party is often

owned by a number of market players. Equivalent to "Program

responsible party" in the Netherlands. Equivalent to "Balance

Responsible group" in Germany. Equivalent to "market agent" in

Spain.

Consumption A party who can be brought to rights, legally and financially, for any




Responsible party: imbalance between energy bought and consumed for all associated

metering points.


This is a type of Balance Responsible Party.

Production A party who can be brought to rights, legally and financially, for any

Responsible party: imbalance between energy sold and produced for all associated

metering points.


This is a type of Balance Responsible Party

Imbalance Settlement A party that is responsible for settlement of the difference between

Responsible: the contracted quantities and the realised quantities of energy

products for the Balance Responsible Parties in a Market Balance

Area.

Note: The Imbalance Settlement Responsible has not the responsibility to

invoice. The Imbalance Settlement Responsible may delegate the

invoicing responsibility to a more generic role such as a Billing

Agent.

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.

Market Information Market Information Aggregator, A party that provides market related

Aggregator: information that has been compiled from the figures supplied by

different actors in the market. This information may also be

published or distributed for general use.

Note: The Market Information Aggregator may receive information from

any market participant that is relevant for publication or distribution.

Market operator: The unique power exchange of trades for the actual delivery of

energy that receives the bids from the Balance Responsible Parties

that have a contract to bid. The market operator determines the

market energy price for the Market Balance Area after applying

technical constraints from the System Operator and the bilateral

trade schedules from the Balance Responsible Parties. It may also

establish the price for the reconciliation within a metering grid area.

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. The SO will also determine

and be responsible for cross border capacity and exchanges. If

necessary he may reduce allocated capacity to ensure operational

stability.

Transmission as mentioned above means "the transport of electricity

on the extra high or high voltage network with a view to its delivery




to final customers or to distributors. Operation of transmission

includes as well the tasks of system operation concerning its

management of energy flows, reliability of the system and

availability of all necessary system services." (definition taken from

the RGCE Operation handbook Glossary).

Note:

Additional obligations may be imposed through local market rules.




5 BUSINESS ENTITY VIEW, EXCHANGE SCHEDULES

5.1 Business Entity View, Business entities

In addition to the domains defined in the ebIX, EFET and ENTSO-E Harmonised role model (see chapter 0)

a series of entities have been identified as relevant for the Business area Exchange schedules. These entities

are shown below:

The attributes defined for the entities can be found in the detailed class diagrams shown later in this

document.

Figure 12: Document entities relevant for the Nordic scheduling process




5.2 Business Entity View, Business entity states

The lifecycle of a business entity may be described as a flow of business entity states, which represents the

different business entity states a business entity can exist in. Below is shown the lifecycle of some of the

business documents exchanged in the Nordic TSO scheduling process.

Figure 13: Business entity states for Request of matched schedules

Figure 14: Business entity states for Market schedule processes




Figure 15: Business entity states for Operational schedule processes

Figure 16: Business entity states for Operational schedule confirmation processes

Figure 17: Business entity states for Outage processes




6 PROCESS AREAS WITHIN THE NORDIC SCHEDULING PROCESS

6.1 Process area: Exchange market schedules

Figure 18: UseCase: Exchange market schedules

The Market schedules are high level (aggregated) schedules, which are sent from the Balance Responsible

parties to the Imbalance Settlement Responsible. They are not used for operation. In Finland and Norway the

Market schedules are sent directly from the Balance Responsible parties to the Imbalance Settlement

Responsible, while the schedules are sent via the System Operator in Denmark and Sweden.

Figure 19: Activity diagram: Exchange market schedules




Comments to the activity diagram:

The Business process Trade is described in [8].

The market schedule document from the Balance Responsible Party to the Imbalance Settlement

Responsible, sent in Finland and Norway, concerns only bilateral trade.

The market schedule document from the Balance Responsible Party to the System Operator:

o Sweden concerns only bilateral trade

o Denmark concerns bilateral trade and trade at the Market Operator (Nord Pool Spot)

The Market schedules are sent on hourly basis day-ahead and contain energy values for production

and/or trade. In Denmark it may also contain consumption (optional).

The Market schedules are aggregated per Balance Responsible party and Market Balance Area.

6.1.1 Process area: Match schedules (Denmark and Sweden)

Figure 20: Activity diagram: Match schedules

The matching validation in Sweden is carried out for every received schedule, independent of what is

received from complementary parties.

In Denmark the matching validation is carried out once the time series from the complementary parties has

been received or one hour before cut-off time for the market. If a time series is found not to match, an

anomaly document and an intermediate confirmation report is transmitted to all the involved parties

informing them of the problem. Time series found to be in error need to be retransmitted via the

retransmission of the applicable schedule document containing all relevant time series, both the corrected,




the non-erroneous time series that were sent with the original document, possibly missing time series and

leaving out time series to be removed.

The anomaly report will contain one or two time series. One time series if there are no schedules from the

counterpart and two time series if there the two time series from the involved actors not are matching. A

missing schedule is interpreted as a schedule with zero values.

In addition to the anomaly report an Intermediate confirmation report, containing the actual schedules from

the two parties and an imposed time series if there are differences, will be sent in Denmark.

In Sweden the Intermediate confirmation report will only be used to inform a counterpart of a schedule until

both parties have sent their schedules. Afterwards the anomaly report will be used to report anomalies

(differences) to the parties.

In Denmark the System Operator will send a Market schedule anomaly report to the Balance Responsible

party, if anomalies apply (regardless of market). In Sweden the System Operator will send a Market schedule

anomaly report to the Balance Responsible party, if anomalies apply outside the Elspot market (for bilateral

trade). In Denmark the System Operator will await corrected schedules and if these are not received within

cut-off time an imposed Market schedule confirmation document is sent to the Balance Responsible party. At

cut-off time the schedules (either corrected or imposed) are sent to the Imbalance Settlement Responsible.

The guard ”Within Swedish market rule" relates to the rule that the party with the highest volume can correct.

If the parties disagree by cut-off time the “lesser rule” applies, i.e. the lesser volume is used. This is however

not reported before the settlement. In Denmark it is always the “lesser value” that is used.

For the Elbas market there is no Market schedule anomaly report. In Denmark however, the imposed Market

schedule confirmation document is sent.

6.2 Process area: Exchange production prognoses (Denmark)

Figure 21: UseCase: Exchange production prognoses

The Business area Exchange production prognosis occurs only in Denmark. The production prognoses are

plans that are used in the planning phase for purchase of ancillary services (or reserves).

There are two types of prognoses:

Prognoses sent 4 weeks upfront, with expected production per power plant on a weekly resolution.

This prognosis includes free text.

Prognoses sent day-ahead with hourly values.




Figure 22: Activity diagram: Exchange production prognoses




6.3 Process area: Exchange operational schedules

Figure 23: UseCase: Exchange operational schedules

The Market schedules related to bilateral trade from the Balance Responsible parties and the Market

operator (Nord Pool Spot) are used together with the Operational schedules to calculate Cut-corridor

schedules, balance per Market Balance Area and binding consumption plans.

Operational schedules can be sent “day-ahead” or intraday. Day-ahead schedules can be sent several weeks

before the operational day and be changed up to the cut-off time the day before. Binding Intra-day schedules

can be sent up to 45 minutes ahead of operation. In Sweden and Denmark the schedules may be sent any

time, but values are only accepted forward. If updated later than 45 minutes before operation in Sweden, the

schedules will not be forwarded to the Imbalance Settlement Responsible. The Operational schedules contain

power values and are sent from the Balance Responsible parties (Production responsible parties) to the

System Operator for operational purposes. The resolution varies between the Nordic countries, from 5 to 60

minutes.




Figure 24: Activity diagram: Exchange operational schedules

The extended UseCase Exchange aggregated schedules per Balance Responsible party and Market Balance

Area (see Figure 23), which only is used in Sweden, is included in the activity diagram above.




6.4 Process area: Exchange Corridor and cut corridor schedules

Figure 25: UseCase: Exchange Corridor and cut corridor schedules

The Corridor and cut corridor schedules are sent from the System Operator to the Market information

aggregator and contain the scheduled exchange from the Transmission capacity allocator (Nord Pool) split

on relevant corridors.

A corridor is a group of power cables/lines. Corridors are used in order to give details about individual or

groups of cables. The information is used by the Market information aggregator in balance management to

present details of import/export plans (individual plans display) and to compute surplus/deficit of each

control area. For example, Skagerrak corridor has 3 cables and can be defined as two HVDC corridors

(Skagerrak1-2 and Skagerrak3). The Corridors can be split into three types:

Elspot corridor Corridors between Market Balance Area within the Nordic market area.

Cut corridor Internal corridor within a Market Balance Area

External corridor Corridors external to the Nordic market area (in/out of the Nordic market area).

Figure 26: Activity diagram: Exchange Corridor and cut corridor schedules




6.5 Process area: Exchange Ancillary services, including Reserve resources

Figure 27: UseCase: Exchange Ancillary services

The Ancillary services process in the Nordic countries may contain:

Frequency bias

Frequency Containment Reserves, Disturbance (FCR-D earlier FDR)

Frequency Containment Reserves, Normal (FCR-N earlier FNR)

Unavailable production capacity (only Norway and Sweden)

Available production capacity (only Denmark)

Spinning reserve (only Norway)

Figure 28: Activity diagram: Exchange Ancillary services

Amongst the primary requirements for the System Operators is the necessity to provide for energy reserves

in order to respond to unexpected events to keep the electricity system operational.




6.6 Process area: Publish outages

Whenever an outage situation occurs (either forced or planned) the System Operator sends the information to

the Market Information Aggregator.

Figure 29: Activity diagram: Publish outages

6.6.1 Outage information modification

An outage situation may be modified to indicate its progress or to correct any data that is found to be invalid.

6.6.2 Outage information deletion

A given outage may be deleted with an update that makes use of the “Delete” attribute. This has the effect of

deleting the outage from the published list.




7 BUSINESS DATA VIEW

7.1 Document related to Market schedules

The Schedule document (Market schedule document) is used for market schedules, which later on is used in

the balance settlement process.

7.1.1 ESS Schedule Document

The Schedule document described below is based on the ENTSO-E ESS Schedule Document, see [1].

7.1.1.1 Class diagram

Figure 30: Class diagram: ESS Schedule Document version 4.1




7.1.1.2 Attribute usage

Document Attribute Code and description

ESS Schedule

Document ESS Schedule Document

Document

Identification

Unique identification of the document

Document Version Fixed 1

Document Type A01 Balance Responsible schedule

Process Type A17 Schedule day

Schedule

Classification Type

A01 Detail type

A02 Summary type

Sender Identification Identification of the party who is sending the document

Sender Role A08 Balance Responsible party (Nord Pool Spot is seen as a BRP)

Receiver

Identification

Identification of the party who is receiving the schedules

Receiver Role A04 System Operator

Creation Date Time Date and time for creation of the document

Schedule Time

Interval

The beginning and ending date and time of the period covered by the

document containing the schedule

Domain Market Balance Area (Elspot Area)

Schedule time series

Senders Time Series

Identification

Sender’s identification of the time series instance

Time Series Version Fixed 1

Business Type A01 Production

A77 Production, dispatchable (Used in DK)

A04 Consumption

A78 Consumption, dispatchable (Used in DK)

A06 External trade without explicit capacity

A08 Net internal trade (Within a Market Balance Area)

A79 Production, non-dispatchable (Used in DK)

National rules:

SE: A06 is used for external trade to Poland, Germany and for Nord

Pool Elspot/Elbas trade between SE and NO/DK/FI

DK: A06 is used for external trade to Germany and for Nord Pool

Elspot/Elbas trade between DK and NO/SE

NO: No market schedules are sent to the SO

Product 8716867000030 Active energy

Object Aggregation A01 Area

A03 Party

A04 Agreement Identification

In Area Market Balance Area, usage: see 0

Out Area Market Balance Area, usage: see 0

In Party Balance Responsible party, usage: see 0

Out Party Balance Responsible party, usage: see 0

Capacity Contract

Type

Not used internally in the Nordic market

Measurement Unit MWH MWh or

KWH kWh

Period

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

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

divided

Interval

Pos The position of the observation in a time series

Qty The quantity for the interval in question

Table 1: Usage of ESS Schedule Document, Balance Responsible schedule to System Operator





ESS Schedule

Document,

Balance

Responsible

schedule to

Imbalance

Settlement

Responsible

(ISR)

ESS Schedule Document

Document

Identification





Schedule

Classification Type

A01 Detail type

A02 Summary type


Sender Role A08 Balance Responsible party (Nord Pool Spot is seen as a BRP)

Receiver

Identification


Receiver Role A05 Imbalance Settlement Responsible


Schedule Time

Interval




Schedule time series

Senders Time Series

Identification


Time Series Version Fixed 1

Business Type A06 External trade without explicit capacity

A08 Net internal trade (Within a Market Balance Area)

National rules:

SE/DK: No market schedules are sent from BRP to ISR


Object Aggregation A03 Party

In Area Market Balance Area, usage: see 0

Out Area Market Balance Area, usage: see 0

In Party Balance Responsible party, usage: see 0

Out Party Balance Responsible party, usage: see 0


KWH kWh

Period



divided

Interval

Pos The relative position of a period within a time interval

Qty The quantity of the product for the position within the time interval in

question

Table 2: Usage of ESS Schedule Document, Balance Responsible schedule to Imbalance Settlement

Responsible




7.1.1.3 Business type dependencies

Business

type

Name Area Party

In Out In Out

A01 Production M M

A77 Production, dispatchable (used in

DK)

M M

A04 Consumption M M

A78 Consumption, dispatchable (used in

DK)

M M

A06 External trade without explicit

capacity

M M M M

A08 Net internal

trade

M*) M*) M M

A79 Production, non-dispatchable (Used in

DK)

M M

Table 3: Dependency matrix for ESS Schedule Document

*) The In Area and the Out Area are the same Market Balance Area

7.1.1.4 National remarks

Norway:

An Out party (buyer), an In Party (seller), an In Area and an Out Area identifying the Market

Balance Area, will replace the Norwegian Bulk supply code (B-code) used today




7.1.2 ESS Anomaly Report

Document used for reporting Market schedules anomalies.

The ESS Anomaly Report described below is based on the ENTSO-E ESS Anomaly report version 4.1, see

[1].

Figure 31: Class diagram: ESS Anomaly Report

Comments to the diagram:

For the matching process, the ESS Anomaly Report will contain one or two time series. One time

series if there are no schedules from the counterpart and two time series if there the two time series

from the involved actors not are matching. A missing schedule is interpreted as a schedule with zero

values. In Sweden and Denmark today, one time series is used, containing the difference between the




two non-matching schedules. This is however expected to be changed to the principles of sending

two time series.

7.1.2.1 Attribute usage Document Attribute Code and description

ESS Anomaly

Report ESS Anomaly Report

Document

Identification


Creation Date Time Date and time for transmission of the document


Sender Role A04 System Operator

Receiver

Identification


Receiver Role A08 Balance Responsible party

Schedule Time

Interval




Anomaly Time Series

Document Sender

Identification

The identification of the party whose time series is in anomaly

Senders Document

Identification

The identification of the document where the time series is in error

Senders document

version

Fixed 1

Senders Time Series

Identification

The identical value of the time series in the referenced document

Senders Time Series

Version

The identical value of the time series in the referenced document, i.e. Fixed

1

Business Type The identical value of the time series in the referenced document, i.e.:

A01 Production

A04 Consumption


A08 Net internal trade




A80 Consumption, non-dispatchable (DK)

Product The identical value of the time series in the referenced document, i.e.:

8716867000030 Active energy

Object Aggregation The identical value of the time series in the referenced document, i.e.:

A03 Party

In Area The identical value of the time series in the referenced document, i.e.:

Market Balance Area, usage: see 7.1.2.2

Out Area The identical value of the time series in the referenced document, i.e.:

Market Balance Area, usage: see 7.1.2.2

In Party The identical value of the time series in the referenced document, i.e.:

Balance Responsible party, usage: see 7.1.2.2

Out Party The identical value of the time series in the referenced document, i.e.:

Balance Responsible party, usage: see 7.1.2.2

Measurement Unit The identical value of the time series in the referenced document, i.e.:

MWH MWh or

KWH kWh

Period



divided

Interval






question

Reason

Reason Code At the time series level:


A27 Cross border capacity exceeded

A28 Counterpart time series missing

A29 Counterpart time series quantity differences

Table 4: Usage of ESS Anomaly Report


Business

type

Name Area Party

In Out In Out

A01 Production M M

A77 Production, dispatchable (Used in DK) M M

A04 Consumption M M

A78 Consumption, dispatchable (Used in DK) M M

A80 Consumption, non-dispatchable (Used in

DK)

M M

A06 External trade without explicit capacity M M M M

A08 Net internal trade M*) M*) M M

A79 Production, non-dispatchable (Used in DK) M M

Table 5: Dependency matrix for ESS Anomaly Report

*) The In Area and the Out Area are the same Market Balance Area if Internal Trade.




7.1.3 ESS Confirmation Report

The ESS Confirmation Report is used for reporting confirmed Market schedules. The ESS Confirmation

Report described below is based on the ENTSO-E ESS Confirmation report, see [1].

Figure 32: Class diagram: ESS Confirmation Report





ESS

Confirmation

Report

ESS Confirmation Report

Document Identification Unique identification of the document


A07 Intermediate confirmation report




Receiver Identification Identification of the party who is receiving the schedules


Schedule Time Interval The beginning and ending date and time of the period covered by the


Confirmed Document

Identification

The identification of the original document containing the confirmed time

series

Confirmed Document

Version

The version of the original document containing the confirmed time

series


Process Type A01 Day ahead (Sweden and Denmark)

A17 Schedule day (Sweden)

A18 Intraday total (Denmark)

Reason (Confirmation Report level)

Reason Code A06 Schedule accepted

A07 Schedule partially accepted

A08 Schedule rejected

Time Series Confirmation

Senders Time Series

Identification



A02 Internal trade (used for reporting from Nord Pool Spot)



Definition:

Net internal trade - where the direction from out party

(seller) to in party (buyer) is positive and the opposite

direction is negative (with minus signs)

A19 Balance energy deviation

A24 Total trade


A80 Consumption, non-dispatchable (Used in DK)



In Area Market Balance Area, usage: see 7.1.2.2

Out Area Market Balance Area, usage: see 7.1.2.2

In Party Balance Responsible party, usage: see 7.1.2.2

Out Party Balance Responsible party, usage: see 7.1.2.2

Reason (Time Series Confirmation level)

Reason Code Only used in Denmark:


A20 Time Series fully rejected

A63 Time Series modified

Imposed time series

Imposed Time Series

Identification

Identification of the original time series that is imposed



A04 Consumption







A24 Total trade

A19 Balance energy deviation





In Area Market Balance Area, usage: see 7.1.2.2

Out Area Market Balance Area, usage: see 7.1.2.2

In Party Balance Responsible party, usage: see 7.1.2.2

Out Party Balance Responsible party, usage: see 7.1.2.2


KWH kWh

Reason (Imposed time series level)

Reason Code A27 Cross border capacity exceeded

A28 Counterpart time series missing

A29 Counterpart time series quantity differences

Only used in Denmark:

A30 Imposed Time series from nominated party's time series

Period

Time Interval The start and end date and time of the time interval of the period in

question


divided

Interval



question

Reason (Interval level)

Reason Code Only used in Denmark

A43 Quantity increased

A44 Quantity decreased

Table 6: Usage of ESS Confirmation Report




7.2 Documents related to Operational schedules

The ESS Planned Resource Schedule (Operational schedule document) is used for operational schedules and

production prognoses day-ahead.

7.2.1 ERRP Planned Resource Schedule

The ERRP Planned Resource Schedule described below is based on the ENTSO-E ERRP Planned resource

schedule, see [1].

7.2.1.1 Class diagram

Figure 33: Class diagram: Planned resource schedule




7.2.1.2 Attribute usage Production and consumption schedule


Planned

Resource

Schedule,

production

and

consumption

schedule

ERRP Planned Resource Schedule Document



Document Type A09 Finalised schedule

A14 Resource Provider Resource Schedule (Operational schedule)

Process Type A01 Day-ahead (Used in Denmark for day-ahead prognoses)

A14 Forecast (Used in Denmark for 4 weeks ahead prognoses)

A17 Schedule day (Used for production and consumption

schedules in all Nordic countries)

Rules:

If A14 is used as Document Type, then A01, A14 or A17 shall

be used as Process Type.

If A09 is used as Document Type, then A17 shall be used as

Process Type.



A08 Balance Responsible party


Receiver Role A32 Market information aggregator

A04 System Operator

A05 Imbalance Settlement Responsible

Creation Date Time Date and time of creation of the document.

Time Period Covered The beginning and ending date and time of the period covered by the

document

Domain Any known area from the Harmonised role model covering the areas

within the time series level of the document, e.g. Market Balance Area

(Elspot Area), National Area, etc.

Planned Resource Time Series

Time Series Identification Sender’s identification of the time series instance


A04 Consumption

A60 Minimum possible

A61 Maximum available


A90 Solar

Z17 Technical minimum

Z18 Technical maximum

Z38 Hydro production

Z39 Nuclear production

Z40 Thermal production

Z41 Wind production

Z42 Decentralised production

Z43 Gas turbine and diesel production

Z44 Other thermal production

National rules:

DK: Z42 is only used in Denmark (aggregated production for small

production units)

Product 8716867000016 Active power

Connecting Area Market Balance Area. This is the In-area for production and Out-area

for consumption.

Resource Object Station group (NO), Regulation object (SE), GSRN (power units in

DK)

Resource Provider TSO or BRP

Measurement Unit MAW MW or

KWT kW





Curve Type A01 Sequential fixed size blocks

A04 Overlapping break points

A05 Non-overlapping break points

Curve type element is only required if different from A01 Sequential

fixed size blocks

Period


question


divided

Interval



question

Unavailable Reserves Time Series (Not used)

Table 7: Usage of Planned resource schedule, Production and consumption schedule




7.2.1.3 Attribute usage Ancillary services schedule


ERRP

Planned

Resource

Schedule

Document,

ancillary

services

schedule


Document

Identification



Document Type A14 Resource Provider Resource Schedule (Operational schedule)



Sender Role A08 Balance Responsible party

A04 System Operator

Receiver

Identification




A32 Market information aggregator



document

Domain Any known area from the Harmonised role model cowering the areas within

the time series level of the document, e.g. Market Balance Area (Elspot

Area), National Area, etc


Time Series

Identification


Business Type A10 Tertiary control (A time series concerning tertiary reserve), used

for Fast reserve

A12 Secondary control (A time series concerning secondary reserve),

used for Frequency Restoration Reserves, Automatic (FRR-A,

earlier LFC)

A70 Production, unavailable

A71 Supplementary available generation

A72 Interruptible consumption

Z02 Frequency bias (Nordic code)

Z03 Frequency Containment Reserves, Normal (FCR-N earlier FNR)

(Nordic code)

Z06 Frequency Containment Reserves, Disturbance (FCR-D earlier

FDR) (Nordic code)

A89 Spinning reserve

National rules:

DK: A10, A12, A70, Z02, Z03, Z06 (15 minutes reserve), and A89 are

used in Denmark

NO: A10, A12, A70, Z02, Z03, Z06 and A89 are used in Norway

SE: A10, A70, A71, A72, Z03 and Z06 are used in Sweden


Connecting Area Market Balance Area

Resource Object Only used for Object Aggregation = A06, i.e. Station group, regulation

object

Resource Provider System Operator or Balance Responsible party


KWT kW

E08 MW/Hz


A06 Resource Object

Curve Type Curve type element is not used. It will always be the default Curve type

used, i.e. A01 Sequential fixed size blocks

Period







divided

Interval



question

Table 8: Usage of Planned resource schedule, Ancillary services schedule




7.2.1.4 Attribute usage Corridor and cut corridor schedules


ERRP

Planned

Resource

Schedule

Document,

corridor and

cut corridor

schedules


Document

Identification



Document Type A04 System Operator area schedule



Sender Role A08 Balance Responsible party

A04 System Operator

Receiver

Identification




A32 Market information aggregator



document

Domain Any known area from the Harmonised role model cowering at least either

the In Areas or Out Areas within the time series level of the document, e.g.

Market Balance Area (Elspot Area), National Area, etc


Time Series

Identification


Business Type A66 Energy flow


Connecting Area Market Balance Area or National Area. The Connecting area is always the

Out-area.

Resource Object Corridor or cut corridor

Resource Provider TSO

Acquiring Area Market Balance Area or National Area. The Acquiring area is always the In-

area.


KWT kW

Object Aggregation A06 Resource Object

Curve Type A01 Sequential fixed size blocks

A04 Overlapping break points

A05 Non-overlapping break points

Curve type element is only required if different from A01 Sequential fixed

size blocks

Period



divided

Interval



question

Table 9: Usage of Planned resource schedule, Corridor and cut corridor schedules




7.2.2 ERRP Resource Schedule Confirmation Report

The ERRP Resource Schedule Confirmation Report described below is based on the ENTSO-E ERRP

Resource schedule confirmation report, see [1].

Figure 34: Class diagram ERRP Resource Schedule Confirmation Report





ERRP

Resource

Schedule

Confirmation

Report

ERRP Resource Schedule Confirmation Report


Document Type A18 Confirmation report








document

Domain Any known area from the Harmonised role model cowering the areas

within the time series level of the document, e.g. Market Balance Area

(Elspot Area), National Area, etc


Time Series Identification Sender’s identification of the time series instance


A04 Consumption

A90 Solar

Z38 Hydro production

Z39 Nuclear production

Z40 Thermal production

Z41 Wind production

Z42 Decentralised production

Z43 Gas turbine and diesel production

Z44 Other thermal production

National rules:

DK: Z42 is only used in Denmark (aggregated production for small

production units)


Connecting Area Relevant area, such as National Area or Market Balance Area

Resource Object Only used for Classification type = A01, i.e. Station group, regulation

object

Resource Provider The ID of the relevant Balance Responsible party


KWT kW


A03 Party

A06 Resource object

Curve Type Curve type element is only used if Curve type A05, Non-overlapping

break points is sent, otherwise the default Curve type will used, i.e. A01

Sequential fixed size blocks

Period


question


divided

Interval



question

Reason (Interval level)

Reason Code Reason Code

Reason Text Reason Text

Table 10: Usage of ERRP Resource Schedule Confirmation Report





Business

type

Name Area

In Out

A01 Production M

A04 Consumption M

A90 Solar M

Z38 Hydro production M

Z39 Nuclear production M

Z40 Thermal production M

Z41 Wind production M

Z42 Decentralised production M

Z43 Gas turbine and diesel

production

M

Z44 Other thermal production M

Table 11: Dependency matrix for ERRP Resource Schedule Confirmation Report




7.3 Outage document

The outage document is used for “four weeks prognoses” in Denmark and as an extended version to NOIS.

7.3.1 Outage document description

The outage document described below is based on the ENTSO-E Outage Document (EOD), see [1], and on

the extended NOIS specification. The Outage document has been extended with additional tags that contain

the group, the version, the reconnect / disconnect information, the impact types and values over corridors.

Figure 35: Class diagram: Outage document

An Outage Document is issued by a System Operator to provide information to the Market Information

Aggregator whenever outages concerning a specific object are planned or as soon as an unplanned outage of

a specific object occurs. Upon reception the Market Information Aggregator makes this information

promptly available to the market.




7.3.2 Attribute usage


Outage to

NOIS Outage document






Receiver Role A32 Market information aggregator

Creation Creation date and time

Document Type Not used

Process Type Not used

Outage

Identification Unique identification of the outage

Group ID A string identifying a group of outages that are linked

Version Version of the Outage being sent.

Each outage change must be identified by a different version number that

starts at 1 and increases sequentially. A new outage must be identified with

version 1.

Business Type A53 Planned maintenance

A54 Forced outage

Measurement Unit MAW MW

Start Date The date that the outage will or has begun, expressed as

YYYY-MM-DD

Start Time Time that the outage has begun or will begin, expressed in UTC as

HH:MM:SSZ

End Date The date that the outage is expected to end, expressed as

YYYY-MM-DD

End Time Time that the outage is expected to end, expressed in UTC as

HH:MM:SSZ

Delete A01 YES – delete the outage

A02 NO – no deletion

Reconnect A01 YES (A positive indication )

A02 NO (A negative indication )

Disconnect A01 YES (A positive indication )


Reconnect Night A01 YES (A positive indication )


Reconnect Night In Time Connect Night in time, expressed in UTC as, HH:MM:SSZ

Reconnect Night Out Time Connect Night out time, expressed in UTC as, HH:MM:SSZ

Reconnect Time Time necessary to reconnect the equipment if reconnect is possible,

expressed in UTC as, HH:MM:SSZ

Category X01 Generation

X02 Transmission

Affected TSOs Identification of affected TSOs (repeatable)

UMM X01 Generation

X02 Transmission

Outage Subject

Asset Type X01 AC line ( within same control area)

X02 AC tie line ( between two control areas)

X03 Busbar

X04 Generator

X05 HVDC Line

X06 HVDC Tie line

X07 Series Capacitor

X08 Transformer

X09 Substation ( Misc. Device)

Affected Asset Identification of the asset




Affected Interconnector Not used

Installed Effect Installed Effect

Available Effect Available Effect

Affected Interconnector

Corridor Type X01 ELSPOT corridor

X02 Cut corridor

X03 External corridor

Direction1

In Area Identification of the In Area

Out Area Identification of the Out Area

Impact Type X01 Absolute

X02 Delta

X03 Percentage

Impact Value The total capacity that is effected by the outage

Direction2

In Area Identification of the In Area

Out Area Identification of the Out Area

Impact Type X01 Absolute

X02 Delta

X03 Percentage

Impact Value The total capacity that is effected by the outage

Reason

Reason Code The reason code identifying the outage reason :

NOIS codes:

X20 Annual revision

X21 Condition control

X22 Essential fault correction

X23 Mechanical

X24 Protective gear

X25 Reconstruction

X26 Replacements

X27 Routine maintenance

X28 Waterways

X29 Work in control system

X30 Work while voltage on

X31 Complementary information

X32 Other

X33 Until further notice

X34 Duration unknown

X35 Back in operation

X36 Yearly maintenance

X37 Required maintenance

X38 Maintenance

X39 New estimated start-up time

Danish codes:

Z01 Operational (The given unit has a status of operational)

Z02 Reduced Operational (The given unit has a status of

reduced operational)

Z03 Non Operational (The given unit has a status of non-

operational)

Z04 Revision (The given unit is under revision)

Z05 Suspended (The given unit is suspended)

Z06 Crashed (The given unit is crashed)

Z07 Discarded (The given unit is discarded)

Reason Text Optional textual additional information concerning the reason for the

outage

Description

Description X01 Work Description

X02 Contact person




X03 Contact phone

Description Text Optional textual additional information concerning the description of the

outage

Table 12: Usage of Outage document




8 BUSINESS RULES

8.1 Balance Responsible Party definition

The term Balance Responsible Party is used throughout this implementation guide and has two meanings:

1. It identifies a Legal entity that has a contract within a Market Balance Area (as is defined in the Role

Model).

2. It identifies the entity that a Balance Responsible Party must ensure is in balance in the scheduling

system.

In general in the schedule document the first definition is used in the document header and the second

definition is used in the time series header. These headers are defined elsewhere in this document. Local

market rules use these definitions with different terms. The following examples will help clarify these

definitions:

Definition 1 will generally correspond to the identification of the entity behind the codes used in the

“Sender Identification” attribute in the document header, for example:

o A Balance Responsible Party.

o A third party responsible for the transmission of schedules on behalf of a Balance

Responsible Party.

Definition 2 will generally correspond to the identification of the entities behind the codes used in

the “In Party” and “Out Party” attributes in the time series header.

8.2 General ground rules

The process flow assumes that a certain number of basic rules are respected. This does not include the

specific rules that have been defined in an interchange agreement. These basic rules are:

1. The last valid schedule document received before cut-off time is the valid schedule.

2. A time series shall be sent for each unique combination of the product, business type, object

aggregation, in area, out area, metering point identification, in party, out party, capacity contract type

and capacity agreement identification.

3. Resending of schedules:

Denmark: All time series in a document must be sent in all retransmitted documents. If a Market

schedule is left out, it is interpreted as the time series will be deleted. If an Operational

schedule is left out the document is rejected.

Finland: TBD

Norway: If changes to a time series, it is enough to resend the changed time series. However, in the

case of errors, the whole document (all time series in a document) will be rejected. There

shall always be a whole day-and-night in a schedule.

Sweden: If changes to a time series, it is enough to resend the changed observations. In case of

errors only the observations in error are rejected.

4. All version numbers shall be positive integer values and leading zeros shall be suppressed.

5. All scheduling documents received shall have an acknowledgement (acceptance, rejection or errors).

6. All the time series information that has been validated in phase 1 (validation at document level) for

formal correctness may be used to balance their complementary time series as soon as these become

available.

7. All the times related to energy products in the documents are expressed in Coordinated Universal

Time (the acronym of which is UTC) in compliance with ISO 8601. This is restricted to YYYY-

MM-DDTHH:MMZ in order to remain in conformity with XML schema requirements.

8. All the time intervals in the documents are expressed in compliance with ISO 8601 This is restricted

to YYYY-MM-DDTHH:MMZ/YYYY-MMDDTHH:MMZ. The time interval has an inclusive start

time and an exclusive end time and is expressed in minutes (i.e. 00:00Z to 00:00Z is exactly a 24

hour period).

9. The time interval defined in the period class shall always be a multiple of its resolution.

10. For a schedule document the time interval of a period class shall always be equal to the Schedule

time interval.

11. Negative quantities for a time series are only permitted for certain categories of time series.




12. An Operational schedule cannot be cancelled or deleted. However it is possible to send zero-value

schedules.

13. It is preferred that the quantity for a Balance Responsible time series in a day-ahead and an intraday

schedule is given in power units’ as the average value over the time interval, i.e. MW (code MAW).

14. Whenever a coded value within a document is associated with a coding scheme, the coding scheme

must always be supplied. The coding scheme is an independent attribute with a size of 3

alphanumeric characters.




Appendix A COMMUNICATION OUT OF THE NORDIC AREA

This appendix describes additional or different usage of exchanges out of the Nordic area. These additions or

changes are listed for information, among others to be able to harmonise new exchanges in the future.

A.1 Balance Responsible schedule to System Operator (SO) between Denmark and Germany

The element Capacity Contract Type is added with the following possible codes:

A01 Day ahead

A03 Monthly

A04 Yearly

A07 Intraday




Appendix B AN EXAMPLE OF TECHNICAL IMPLEMENTATION

Message exchanges to/from NOIS are in this appendix presented as an example of where the schedule

documents will be used in the Nordic countries.

B.1 Market Schedule documents to/from NOIS

The Nordic TSOs Energinet.dk, Fingrid, Statnett and Svenska Kraftnät are sending ENTSO-E based ESS

documents to NOIS. The following rules apply for the ESS document:

The Schedule Document (ESS) encapsulates schedule time series.

Every time a schedule document is transmitted, the time series contained in the document will be

inserted in database. In case the schedule document is retransmitted the enclosed time series will

override the existing time series in NOIS database (for the same time interval)

Each document transmission can contain version numbers for information but supplied version

numbers are ignored by NOIS system.

A TSO can usually transmit several time series to notify his position for a given time interval,

message type, process type and classification type. A document sent without any time series signifies

that the party has no information to transmit.

The sender must assign a unique identification for a time series within a message.

A time series must contain a period that covers a subset of the schedule time interval. The period

also contains a resolution of the period within the time interval. The time interval must be

completely covered by a whole multiple of the resolution.

If a time series is suppressed then the interval quantities are all zeroed out.

The following Market schedule documents may be sent to NOIS:

PPH Production Plan Hydro

PPT Production Plan Thermal

PPW Production Plan Wind

PPN Production Plan Nuclear

Business rules:

o Production Plan documents are sent in day ahead or in intraday by TSO’s.

o The Schedule Time Interval must cover a full day.

o The time interval of each time series must be a subset of the Schedule Time Interval

o The sender identification must be the identification of a known TSO.

o The domain area must be a known control area managed by the sender TSO.

o The in area must be a known production area managed by the sender TSO .

PPM Production Plan of Major power plant

Business rules:

o Production Plan of major power plants documents are sent in intraday by TSO’s.

o The Schedule Time Interval should cover a full day.




o The in area of each time series must identify a known control area ( same as domain area)

o The Metering Point Identification must be a known resource id attached to the in area

(control area)

o Resolution is PT5M only

CP Consumption Plan

Business rules:

o Consumption Plan documents are sent in day ahead or in intraday by TSO’s.








o The out area must be a known consumption area managed by the sender TSO .

DCP HVDC Plan

Business rules:

HVDC corridors are defined in NOIS database in order to give details about individual cables.

This information is used in balance management to present details of import/export plans

(individual plans display) and to compute surplus/deficit of each control area (total plans

display). For example, Skagerrak corridor has 3 cables and can be defined has two HVDC

corridors (Skagerrak12 and Skagerrak3)

o HVDC Plan documents are sent in day ahead or in intraday by TSO’s.





o The in and the out area of each time series must identify known control areas

o The Metering Point Identification must be a known HVDC corridor attached to the in and

the out area

ACP AC corridor plan

Business rules:

AC corridors are defined in NOIS database in order to represent major AC lines connexions

between Nordel countries or between a Nordel country and a foreign country. This information

is used in balance management to present details of import/export plans (individual plans

display) and to compute surplus/deficit of each control area (total plans display)

o AC corridor Plan documents are sent in day ahead or in intraday by TSO’s.






o The Metering Point Identification must be a known AC corridor attached to the in and the

out area

EPTP Elspot Transmission Plan

Business rules:

o Elspot Transmission Plan documents are sent in day ahead by TSO’s.

o The Elspot Transmission Plan must cover a full day.



o The in or the out area must belong to the domain area the

o The in and the out area of each time series must identify known ELSPOT areas.

o The metering point identification must identify a known ELSPOT corridor

EBTP Elbas Transmission Plan

Business rules:

o Elbas Transmission Plan documents are sent in intra day by TSO’s.





o The in and the out area of each time series must identify known ELSPOT areas

CTP Cuts Transmission Plan




Business rules:

o Cuts Transmission Plan documents are sent in day ahead or in intra day by TSO’s.

o The Cut Transmission Plan must cover a full day.



o The in and the out area of each time series must identify a known cut area linked to the

domain area.

ONTP Out of Nordel Transmission Plan

Business rules:

o Out of Nordel Transmission Plan documents are sent in day ahead or in intraday by TSO’s.

o The Out of Nordel Transmission Plan must cover a full day.



o The domain area must be equal to the in or the out area of each time series.


o The metering point identification must identify a known external corridor

FRP Frequency response plans

Business rules:

o Frequency response Plan documents are sent in day ahead or in intraday by TSO’s.





o The domain area must be equal to the in area of each time series.

GMH Real-time hydro Generation measurements

GMT Real-time Thermal Generation measurements

GMW Real-time Wind Generation measurements

GMN Real-time Nuclear Generation measurements

GMM Real-time generation measurements of major power plant

CM Real-time Consumption measurements

DCM Real-time HVDC corridor measurements

ACM Real-time AC corridor measurements

MTIC Real-time Measured transmission of cross border interconnections

MTC Real-time Measured transmission of cut corridors

MTON Real-time Measured transmission of Out of Nordel connections (external corridors)

Business rules:

o Near Real-time generation measurements documents are sent in intraday by TSO’s.

o The Schedule Time Interval must cover the current day.




o The in area must be a known production area managed by the sender TSO.

o A reason is linked to each time series to specify the quality of the measurement: X01

indicates a Good Quality / X02 indicates a Suspect Quality

o Resolution is PT5M

MSAF Measured synchronous area frequency

Business rules:

o Measured synchronous area frequency documents are sent in intraday by TSO’s.








o The in area must be a known control area managed by the sender TSO.

o A reason can be linked to each time series to specify the quality of the measurement: X01


MUAF Measured UCTE area frequency

Business rules:

o Measured UCTE area frequency documents are sent in intraday by TSO’s.






HGMH Hourly Hydro Generation measurements

HGMT Hourly Thermal Generation measurements

HGMW Hourly Wind Generation measurements

HGMN Hourly Nuclear Generation measurements

HCM Hourly Consumption measurements

HDCM Hourly HVDC corridor measurements

HACM Hourly AC corridor measurements

HMTIC Hourly Measured transmission of cross border interconnections

HMTC Hourly Measured transmission of cut corridors

HMTON Hourly Measured transmission of Out of Nordel connections (external corridors)

Business rules:

o “Hourly validated” generation measurements documents are sent in intraday or after the

business day by TSO’s.





o The in area must be a known production area managed by the sender TSO.

o A reason can be linked to each time series to specify the quality of the measurement: X01


o Resolution is PT1H

o No particular process Type will be defined for time series that apply to a day in the past

(day-ahead or intra-day process type can be used)

FNR (FCR-N) real-time FNR (FCR-N) measurements

Business rules:

o Near Real-time FNR (FCR-N) measurements documents are sent in intraday by TSO’s.








o Resolution is PT5M or PT1H

FDR (FCR-D) real-time FDR (FCR-D) measurements

Business rules:

o Near Real-time FDR (FCR-D) measurements documents are sent in intraday by TSO’s.











o Resolution is PT5M or PT1H

DF Dimensioning fault

Business rules:

o Area dimensioning fault documents are sent in day ahead or in intraday by TSO’s.

o Area dimensioning fault must cover one business delivery day (24 hours)



o The in area of each time series must be a known reserve area managed by the sender TSO.

AMP Activated moved production per control area - 5 minutes resolution time series

Business rules:

o Activated moved production quantities are sent in intraday by TSO’s.







PAB Planned activation for “balance” reason and per control area: 5 minutes resolution time series

PAS Planned activation for “special” reason and per control area: 5 minutes resolution time series

PAQ Planned activation Quarterly: 5 minutes resolution time series

Business rules:

o Planned activation quantities for a control area are sent in intraday by TSO’s.







HAAR Hourly Automatic Activated Reserves caused by frequency response per elspot area

Business rules:

o “Hourly validated” Automatic Activated Reserve measurements documents are sent in

intraday or after the business day by TSO’s.





o The in area must be a known elspot area managed by the sender TSO.




HMPS Hourly Moved Production Start per elspot area

Business rules:

o “Hourly Moved Production Start” documents are sent in intraday or after the business day

by TSO’s.








o The in area must be a known Elspot Area managed by the sender TSO.




HSMF Hourly Sum of Measured Flow per Elspot Area

Business rules:

o Business rules: “Hourly Sum of Measured flow” documents are sent in intraday or after the

business day by TSO’s.









HLFCV Hourly LFC (FRR-A) Volume per Elspot Area

Business rules:

o “Hourly LFC (FRR-A) Volume” documents are sent in intraday or after the business day by

TSO’s.









The following schedule documents may be received by NOIS:

DF Dimensioning Fault

Business rules:

o Area dimensioning fault documents are sent to TSO’s folder on operator request

o Area dimensioning fault must cover one business delivery day (24 hours)

o The receiver identification must be the identification of a known TSO.

o The sender identification is NOIS identification

o The in area of each time series must be known reserve areas

o The domain is “Nordel”

BRV Balance Regulation Volume

Business rules:

o Balance Regulation Volume documents are sent to NORDPOOL folder every hour

o Balance Regulation Volume must cover one business delivery day (24 hours)

o The receiver identification must be the identification of NordPool.


o The in area of each time series must be a known Elspot Area


SRV Special Regulation Volume

Business rules:

o Special Regulation Volume documents are sent to NORDPOOL folder every hour

o Special Regulation Volume must cover one business delivery day (24 hours)








AIV Area Imbalance Volume

Business rules:

o Area Imbalance Volume documents are sent to NORDPOOL folder every hour

o Area Imbalance Volume must cover one business delivery day (24 hours)








B.2 Operational Schedule documents to/from NOIS

The Nordic TSOs Energinet.dk, Fingrid, Statnett and Svenska Kraftnät are sending ENTSO-E based ERRP

documents to NOIS. The following rules apply for the ERRP Planned Resource Schedule Document:

The ERRP Planned Resource Schedule Document encapsulates Planned Resource schedule time

series.

There is one single document identification per sender, delivery day, message type and process type

(e.g. a TSO should transmit its entire reserve plan in a single document for a given delivery day).

A TSO can usually transmit several time series to notify his position for a given time interval,

document type and process type. A document sent without any time series signifies that the TSO has

no information to transmit.

The sender must assign a unique identification for a time series within a message.

A time series must contain a period that covers a subset of the schedule time interval. The period

also contains a resolution of the period within the time interval. The time interval must be

completely covered by a whole multiple of the resolution.

If a time series is suppressed then the interval quantities are all zeroed out.

The following operational schedule documents may be sent to NOIS:

RP Reserve Plan

Business rules:

o FNR (FCR-N) Plan

FNR (FCR-N) Reserve Plan documents are sent in day ahead or in intraday by TSO’s.

FNR (FCR-N) Reserve Plan must cover one business delivery day (24 hours)

The sender identification must be the identification of a known TSO.

The connecting area of each time series must be a known control area managed by the

sender TSO.

o FDR (FCR-D) Plan

FDR (FCR-D) Reserve Plan documents are sent in day ahead or in intraday by TSO’s.

FDR (FCR-D) Reserve Plan must cover one business delivery day (24 hours)



sender TSO.

o FNR (FCR-N) Trade Plan

FNR (FCR-N) Reserve Trade Plan documents are sent in day ahead or in intraday by

TSO’s.

FNR (FCR-N) Reserve Trade Plan must cover one business delivery day (24 hours)



sender TSO.

o FDR (FCR-D) Trade Plan

FDR (FCR-D) Reserve Trade Plan documents are sent in day ahead or in intraday by

TSO’s.

FDR (FCR-D) Reserve Trade Plan must cover one business delivery day (24 hours)



sender TSO.

o Additional FAR Plan

Additional FAR Plan documents are sent in day ahead or in intraday by TSO’s.

Additional FAR Plan must cover one business delivery day (24 hours)


The connecting area of each time series must be a known reserve area managed by the

sender TSO.
