ENTSO-E CORRIGENDUM TO THE ERRP … · 115 THIS DOCUMENT IS MAINTAINED BY THE ENTSO-E WG EDI. COMMENTS ... 141 The identification of an error in the ... 146 The workflow outlined

ENTSO-E AISBL • Avenue de Cortenbergh, 100 • 1000 Brussels • Belgium • Tel +32 2 741 09 50 • Fax +32 2 741 09 51 • [email protected] • www.entsoe.eu

European Network of Transmission System Operators

for Electricity

1

ENTSO-E

CORRIGENDUM TO THE ERRP

IMPLEMENTATION GUIDES

2014-11-18

VERSION 1.0

Page 2 of 53



for Electricity

ENTSO-E CORRIGENDUM TO

THE ERRP IMPLEMENTATION GUIDE

VERSION 1.0

Table of Contents 2

1 OBJECTIVE .......................................................................................................... 6 3

2 VERSION 1 RELEASE 0 – 18TH OF NOVEMBER 2014 ................................................... 6 4

2.1 REDISPATCH ACTIVATION ........................................................................................................ 7 5

2.1.1 REDISPATCH WORKFLOW DIAGRAM ...................................................................................... 7 6

2.1.2 REDISPATCH ACTIVATION ........................................................................................................ 8 7

2.1.2.1 ACTIVATION INFORMATION REQUIREMENTS ...................................................................... 10 8

2.1.2.2 MAPPING BETWEEN THE REDISPATCH DOCUMENT AND THE ACTIVATION DOCUMENT11 9

2.1.2.3 RULES GOVERNING THE ACTIVATION DOCUMENT HEADER ............................................ 11 10

2.1.2.3.1 DOCUMENT IDENTIFICATION ................................................................................................. 12 11

2.1.2.3.2 DOCUMENT VERSION ............................................................................................................. 13 12

2.1.2.3.3 DOCUMENT TYPE .................................................................................................................... 13 13

2.1.2.3.4 PROCESS TYPE ....................................................................................................................... 14 14

2.1.2.3.5 SENDER IDENTIFICATION – CODING SCHEME .................................................................... 15 15

2.1.2.3.6 SENDER ROLE.......................................................................................................................... 15 16

2.1.2.3.7 RECEIVER IDENTIFICATION – CODING SCHEME................................................................. 16 17

2.1.2.3.8 RECEIVER ROLE ...................................................................................................................... 16 18

2.1.2.3.9 CREATION DATE AND TIME .................................................................................................... 17 19

2.1.2.3.10 ACTIVATION TIME INTERVAL.................................................................................................. 17 20

2.1.2.3.11 DOMAIN - CODINGSCHEME .................................................................................................... 18 21

2.1.2.3.12 SUBJECTPARTY - CODINGSCHEME ...................................................................................... 18 22

2.1.2.3.13 SUBJECT ROLE ........................................................................................................................ 19 23

2.1.2.3.14 ORDERIDENTIFICATION .......................................................................................................... 19 24

2.1.2.3.15 ORDERIDENTIFICATIONVERSION.......................................................................................... 19 25

2.1.2.4 RULES GOVERNING THE ACTIVATION TIME SERIES CLASS ............................................. 20 26

2.1.2.4.1 ALLOCATIONIDENTIFICATION ................................................................................................ 20 27

2.1.2.4.2 RESOURCEPROVIDER ............................................................................................................ 20 28

2.1.2.4.3 BUSINESS TYPE ....................................................................................................................... 21 29

2.1.2.4.4 ACQUIRINGAREA - CODINGSCHEME .................................................................................... 21 30

2.1.2.4.5 CONNECTINGAREA - CODINGSCHEME ................................................................................ 22 31

2.1.2.4.6 MEASUREUNIT ......................................................................................................................... 22 32

2.1.2.4.7 DIRECTION ................................................................................................................................ 23 33

2.1.2.4.8 STATUS ..................................................................................................................................... 24 34

2.1.2.4.9 RESOURCE OBJECT –CODING SCHEME .............................................................................. 25 35

2.1.2.5 RULES GOVERNING THE PERIOD CLASS ............................................................................. 25 36

2.1.2.5.1 TIME INTERVAL ........................................................................................................................ 26 37

2.1.2.5.2 RESOLUTION ............................................................................................................................ 26 38

2.1.2.6 RULES GOVERNING THE INTERVAL CLASS ......................................................................... 26 39

2.1.2.6.1 POS ............................................................................................................................................ 27 40

2.1.2.6.2 QTY ............................................................................................................................................ 27 41

2.1.2.7 RULES GOVERNING THE REASON CLASS ........................................................................... 27 42

2.1.2.7.1 REASON CODE ......................................................................................................................... 28 43

2.1.2.7.2 REASON TEXT .......................................................................................................................... 28 44

2.2 TRANSMISSION OF HISTORICAL ACTIVATION INFORMATION........................................... 29 45

2.2.1 ACTIVATION HISTORY DOCUMENT ....................................................................................... 30 46

2.2.1.1 DOCUMENT IDENTIFICATION ................................................................................................. 31 47

2.2.1.2 DOCUMENT VERSION ............................................................................................................. 31 48

2.2.1.3 DOCUMENT TYPE .................................................................................................................... 32 49

2.2.1.4 PROCESS TYPE ....................................................................................................................... 32 50

2.2.1.5 SENDER IDENTIFICATION – CODING SCHEME .................................................................... 33 51

2.2.1.6 SENDER ROLE.......................................................................................................................... 33 52

2.2.1.7 RECEIVER IDENTIFICATION – CODING SCHEME................................................................. 34 53

2.2.1.8 RECEIVER ROLE ...................................................................................................................... 34 54

2.2.1.9 CREATION DATE AND TIME .................................................................................................... 34 55

2.2.1.10 ACTIVATION HISTORY TIME INTERVAL ................................................................................. 35 56

2.2.1.11 DOMAIN - CODINGSCHEME .................................................................................................... 35 57

Page 3 of 53



for Electricity



VERSION 1.0

2.2.2 RULES GOVERNING THE ACTIVATION TIME SERIES CLASS ............................................. 36 58

2.2.2.1 ACTIVATION IDENTIFICATION ................................................................................................ 36 59

2.2.2.2 ACTIVATION VERSION ............................................................................................................. 37 60

2.2.2.3 ACTIVATION PROCESS TYPE ................................................................................................. 37 61

2.2.2.4 REQUESTING PARTY – CODING SCHEME ............................................................................ 38 62

2.2.2.5 ACTIVATING PARTY – CODING SCHEME .............................................................................. 38 63

2.2.2.6 ACTIVATION TIME INTERVAL.................................................................................................. 39 64

2.2.2.7 ALLOCATIONIDENTIFICATION ................................................................................................ 39 65

2.2.2.8 RESOURCEPROVIDER ............................................................................................................ 39 66

2.2.2.9 BUSINESS TYPE ....................................................................................................................... 40 67

2.2.2.10 ACQUIRINGAREA - CODINGSCHEME .................................................................................... 40 68

2.2.2.11 CONNECTINGAREA - CODINGSCHEME ................................................................................ 41 69

2.2.2.12 MEASUREUNIT ......................................................................................................................... 41 70

2.2.2.13 DIRECTION ................................................................................................................................ 42 71

2.2.2.14 STATUS ..................................................................................................................................... 43 72

2.2.2.15 RESOURCE OBJECT –CODING SCHEME .............................................................................. 44 73

2.2.3 RULES GOVERNING THE PERIOD CLASS ............................................................................. 44 74

2.2.3.1 TIME INTERVAL ........................................................................................................................ 45 75

2.2.3.2 RESOLUTION ............................................................................................................................ 45 76

2.2.4 RULES GOVERNING THE INTERVAL CLASS ......................................................................... 45 77

2.2.4.1 POS ............................................................................................................................................ 46 78

2.2.4.2 QTY ............................................................................................................................................ 46 79

2.2.5 RULES GOVERNING THE REASON CLASS ........................................................................... 47 80

2.2.5.1 REASON CODE ......................................................................................................................... 47 81

2.2.5.2 REASON TEXT .......................................................................................................................... 48 82

2.3 CORRECTION TO THE RESTRICTED CODELIST OF THE MOL DOCUMENT ..................... 48 83

2.3.1 PROCESSTYPE ........................................................................................................................ 48 84

2.3.2 BUSINESSTYPE ........................................................................................................................ 49 85

2.3.3 REASONTYPE ........................................................................................................................... 49 86

2.4 CORRECTION TO THE DATATYPE OF THE DOMAIN IN THE MOL DOCUMENT ................ 50 87

2.5 CORRECTION TO THE DATATYPE OF THE DOMAIN IN THE ACTIVATION DOCUMENT .. 51 88

2.6 CORRECTION TO THE DATATYPE OF THE DOMAIN IN THE REDISPATCH DOCUMENT . 52 89

2.7 CORRECTION TO THE DEFAULT NAMESPACE OF THE ACTIVATION DOCUMENT ......... 53 90

List of figures 91

FIGURE 1: REDISPATCH WORKFLOW .................................................................................... 7 92

FIGURE 2:REDISPATCH ACTIVATION .................................................................................... 9 93

FIGURE 3: ACTIVATION DOCUMENT INFORMATION MODEL ................................................... 10 94

FIGURE 4: HISTORICAL ACTIVATION DOCUMENT ................................................................. 30 95

FIGURE 5: REVISED MOL DOCUMENT MODEL ..................................................................... 50 96

FIGURE 6: REVISED ACTIVATION DOCUMENT MODEL ........................................................... 51 97

FIGURE 7: REVISED REDISPATCH DOCUMENT MODEL .......................................................... 52 98

99

Page 4 of 53



for Electricity



VERSION 1.0

Copyright notice: 100

Copyright © ENTSO-E. All Rights Reserved. 101

This document and its whole translations may be copied and furnished to others, and 102

derivative works that comment on or otherwise explain it or assist in its implementation may 103

be prepared, copied, published and distributed, in whole or in part, without restriction of any 104

kind, provided that the above copyright notice and this paragraph are included on all such 105

copies and derivative works. However, this document itself may not be modified in any way, 106

except for literal and whole translation into languages other than English and under all 107

circumstances, the copyright notice or references to ENTSO-E may not be removed. 108

This document and the information contained herein is provided on an "as is" basis. 109

ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 110

NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 111

WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 112

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 113

Maintenance notice: 114

THIS DOCUMENT IS MAINTAINED BY THE ENTSO-E WG EDI. COMMENTS OR 115

REMARKS ARE TO BE PROVIDED AT [email protected] 116

mailto:[email protected]

Page 5 of 53



for Electricity



VERSION 1.0

Revision History 117

Version Release Date Comments

1 0 2014-11-18 Corrigendum to permit additional functionality with ERRP to handle redispatch activation and to provide activation historical data. It corrects also the following errors:

error that prevented the use of local codes with the MOL document.

error in the default namespace of the Activation document.

error in the Domain datatype of the Activation, MOL and Redispatch documents.

118

Page 6 of 53



for Electricity



VERSION 1.0

1 OBJECTIVE 119

The objective of this corrigendum is to correct anomalies or to provide additional 120

functionalities that have been identified during the course of the implementation of the ERRP 121

process. 122

All software developers shall therefore refer to the ERRP 5.0 implementation guide approved 123

by the Market Committee in June 2013 and take into account the changes identified in this 124

corrigendum. 125

With each update of this corrigendum a news flash will be published on the ENTSO-E web 126

site providing all the information to enable access to the latest version of this document, and 127

in particular the identification of any schemas that have evolved. 128

A revised ERRP document will be provided as soon sufficient changes in the corrigendum 129

have been identified to require the update of the document. 130

2 VERSION 1 RELEASE 0 – 18TH

OF NOVEMBER 2014 131

Following the approval by the Market Committee of the ERRP Implementation Guide on the 132

6th of June 2013, several issues have been raised that merit the creation of this corrigendum. 133

The issues concern: 134

The requirement to activate cross border redispatch document information 135

The possibility to transmit the history of activation information. 136

The modification of the restricted codelist XSD in order to enable local codelists to be 137

used. 138

The identification of the Domain datatype in the Activation, MOL and Redispatch 139

Documents. 140

The identification of an error in the Activation Document default namespace. 141

Page 7 of 53



for Electricity



VERSION 1.0

2.1 REDISPATCH ACTIVATION 142

2.1.1 REDISPATCH WORKFLOW DIAGRAM 143

144

FIGURE 1: REDISPATCH WORKFLOW 145

act Redispa tch Wor kf low diagr am

Cooper a t ing Sy stem Oper a torInit ia t ing Sy stem Oper a tor

Diagnose

congest ion

situa t ion

Contact

Cooper a t ing

Sy stem

Oper a tor

Discuss

pr oblem

Agree mutual action

Redispatch agreed?

Send

redispatch

notice

Receive

redispatch

notice

Redispatch agreed?

Wait for redispatch notice

Send

negative

ack

OK?Receive

negative

ack

Cor r ect

document

Send

positive

ack

End

Receive

positive

ack

No

Yes

Redispatch Document

Yes

Acknowledgement Document

Yes

No

No


Page 8 of 53



for Electricity



VERSION 1.0

The workflow outlined in Figure 1 is described in the ERRP implementation guide on page 146

194 line 2138 and is reproduced here to facilitate reading. A correction has been made to the 147

diagram to place the transmission flow of the Redispatch Notice in its correct position to 148

enter the join condition. The process is used to establish a redispatch agreement. 149

In order to be able to activate such an agreement the following process should be put into 150

place and shall be described in chapter 11 page 174 concerning the rules governing the 151

Activation Document header. 152

The System Operator that has the resources that are to be used in a redispatch agreement 153

shall be identified as the “Resource Provider”. 154

The System Operator that requires the redispatch shall be identified as the “Impacted 155

System Operator”. 156

It is the Impacted System Operator that shall always be the party that initiates the activation 157

request whenever redispatch resources are needed. 158

2.1.2 REDISPATCH ACTIVATION 159

The workflow in Figure 2 provides the means of initiating a redispatch activation. 160

This is an additional activation possibility to the different activation scenarios that are 161

possible and that are outlined in the ERRP implementation guide on page 49 line 1298 and 162

following. 163

The redispatch reduction requirements are that same as those outlined in the ERRP 164

implementation guide on page 51 line 1326 and following. 165

Page 9 of 53



for Electricity



VERSION 1.0

166

FIGURE 2:REDISPATCH ACTIVATION 167

act Act iv a t ion wor kf low Business pr ocess

Resour ce P r ov iderImpacted Sy stem Oper a tor

Establ ish

a ct iv a t ion

r equir ements

Al ign with

r edispa tch

r equir ements

Submit

redispatch

activation

Validate

with

redispatch

agreement

Conform with agreement?Reject

request

Act iv a te

r equested

r esour ces

Accept

request

Correct

request

Note

activation

acceptance

End

redispatch

activation

Activation Document


Yes

No

Activation Document

Page 10 of 53



for Electricity



VERSION 1.0

2.1.2.1 ACTIVATION INFORMATION REQUIREMENTS 168

169

FIGURE 3: ACTIVATION DOCUMENT INFORMATION MODEL 170

The model in Figure 3 represents the model as outlined in the ERRP implementation guide 171

on page 173 line 1979 and is provided here to facilitate reading. It should be noted that the 172

datatype of the Domain attribute has been corrected as indicated in section 2.5. 173

Page 11 of 53



for Electricity



VERSION 1.0

2.1.2.2 MAPPING BETWEEN THE REDISPATCH DOCUMENT AND THE 174

ACTIVATION DOCUMENT 175

The Activation Document header shall contain in the OrderIdentification and 176

OrderIdentificationVersion the DocumentIdentification and the DocumentVersion of the 177

Redispatch Document being activated in the case of the Activation Request. In the case of 178

an Activation Response it shall contain the information relating to the activation Request. For 179

the rest of the Redispatch Document the mapping between the Redispatch Document 180

concerns essentially the time series of the two documents. 181

TABLE 1 REDISPATCH – ACTIVATION DOCUMENT TRANSFORMATION TABLE 182

Activation TimeSeries Attribute content

AllocationIdentification The identification of the redispatch Time Series "TSIdentification"

ResourceProvider The identification of the sender of the Redispatch Document "SenderIdentification"

BusinessType The BusinessType of the Redispatch Document; A46 = "System Operator redispatch"

AcquiringArea The area of the impacted System Operator in the Redispatch time series "ImpactedArea"

ConnectingArea The Area of the "Resource Provider" System

MeasureUnit The Unit of Measure of the Redispatch Document "MeasureUnitQuantity"

Direction The Direction of the Redispatch Document "Direction"

Status The Status as defined in the ERRP Implementation Guide

ResourceObject The ResourceObject of the RedispatchDocument 'ResourceObject"

The Period and Interval classes contain the activation duration, resolution and quantities. 183

For facility of reading the complete section 11 (page 173 through to page 190) of the ERRP 184

implementation guide has been reproduced here with all relevant changes marked in red. 185

2.1.2.3 RULES GOVERNING THE ACTIVATION DOCUMENT HEADER 186

If the Activation Time Interval changes then the transmission of a new document is required. 187

If the Activation Time Interval does not change then the transmission of a new version can be 188

used. 189

Only information concerning energy to be activated shall be identified in an Activation 190

Document. Consequently, in the case of SATCR activation, if the Activation Time Interval 191

start time has already passed then the document shall be considered invalid. In the case of 192

DATCR activation this is true in the case of the initial transmission of a document. However, 193

if it is a new version of an existing document then the Activation Time Interval start time may 194

be past since the change in question is reducing the interval in question. 195

In the case of an Activation Response, the Order Identification must provide the identification 196

of the Activation Order being acknowledged. The characteristics of the response document 197

Page 12 of 53



for Electricity



VERSION 1.0

must correspond to that of the activation order. The only characteristic that may change is 198

the quantities where these are being reduced. 199

In the case of a Tender Reduction, the contract Identification must provide the identification 200

of the tender being reduced. 201

2.1.2.3.1 DOCUMENT IDENTIFICATION 202

ACTION DESCRIPTION

Definition of element Unique identification of the document for which the time series data is being supplied.

Description An Activation Document for a given set of time series and a given activation period must have a unique identification assigned by the sender of the document for all transmissions to the receiver. All additions, modifications, or suppressions for the time series and activation period must use the same identification.

Size The identification of a document may not exceed 35 alphanumeric characters.

Applicability This information is mandatory.

Dependence requirements None.

Page 13 of 53



for Electricity



VERSION 1.0

2.1.2.3.2 DOCUMENT VERSION 203

ACTION DESCRIPTION

Definition of element Version of the document being sent. A document may be sent several times, each transmission being identified by a different version number that starts at 1 and increases sequentially.

Description The document version is used to identify a given version of a time series set for a given activation period. The first version number for a given document identification shall normally be 1. The document version number must be incremented for each retransmission of a document that contains changes to the previous version. The receiving system shall only accept a document with a version number which is greater than the previous version number of the same document.

Size A version number may not exceed 3 numeric characters.



2.1.2.3.3 DOCUMENT TYPE 204

ACTION DESCRIPTION

Definition of element The coded type of the document being sent.

Description The document type identifies the information flow characteristics. The following types are permitted: A39 = SATCR Activation A40 = DATCR Activation A41 = Activation Response A42 = Tender reduction A64 = Tender reduction response. A96 = Redispatch activation

Size The document type value must be exactly 3 alphanumeric characters (no blanks).



Page 14 of 53



for Electricity



VERSION 1.0

2.1.2.3.4 PROCESS TYPE 205

ACTION DESCRIPTION

Definition of element The nature of the process that the document is directed at.

Description The process type identifies the process to which the information flow is directed. Permitted codes are: A27 = Reserve resource process. A28 = Primary reserve process A29 = Secondary reserve process A30 = Tertiary reserve process A41 = Redispatch process

Size The process type value must be exactly 3 alphanumeric characters (no blanks).

Applicability This information is dependent.

Dependence requirements The dependency requirement is uniquely to ensure backwards compatability. If a version 5 transmission is implemented then this attribute is mandatory.

Page 15 of 53



for Electricity



VERSION 1.0

2.1.2.3.5 SENDER IDENTIFICATION – CODING SCHEME 206

ACTION DESCRIPTION

Definition of element Identification of the party that is the owner of the document and is responsible for its content.

Description The sender of the document is identified by a unique coded identification. This code identifies the party that is the “owner” of the information being transmitted in the document and who is responsible for its content. In general this identifies the Acquiring System Operator or its representative. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a sender’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.

Applicability Both the identification and the coding scheme are mandatory.


2.1.2.3.6 SENDER ROLE 207

ACTION DESCRIPTION

Definition of element Identification of the role that is played by the sender.

Description The sender role, which identifies the role of the sender within the document. In general this corresponds to the System Operator. Refer to the ENTSO-E Code list document for valid role codes.

Size The maximum length of a sender role is 3 alphanumeric characters.



Page 16 of 53



for Electricity



VERSION 1.0

2.1.2.3.7 RECEIVER IDENTIFICATION – CODING SCHEME 208

ACTION DESCRIPTION

Definition of element Identification of the party who is receiving the document.

Description The receiver of the document is identified by a unique coded identification. In general this identifies the Resource Provider or its representative. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a receiver’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



2.1.2.3.8 RECEIVER ROLE 209

ACTION DESCRIPTION

Definition of element Identification of the role played by the receiver.

Description The receiver role, which identifies the role of the receiver within the document. Refer to the ENTSO-E Code list document for valid role codes.

Size The maximum length of a receiver role is 3 alphanumeric characters.



Page 17 of 53



for Electricity



VERSION 1.0

2.1.2.3.9 CREATION DATE AND TIME 210

ACTION DESCRIPTION

Definition of element Date and time of creation of the document.

Description The date and time that the document was prepared for transmission by the application of the sender.

Size The date and time must be expressed in UTC as: YYYY-MM-DDTHH:MM:SSZ.



2.1.2.3.10 ACTIVATION TIME INTERVAL 211

ACTION DESCRIPTION

Definition of element The beginning and ending date and time of the period covered by the document where the energy is to be activated.

Description This information provides the start and end date and time of the activation period. The receiver will discard any time intervals outside the activation period indicated.

Size The start and end date and time must be expressed as: YYYY-MM-DDTHH:MMZ/YYYY-MM-DDTHH:MMZ.



Page 18 of 53



for Electricity



VERSION 1.0

2.1.2.3.11 DOMAIN - CODINGSCHEME 212

ACTION DESCRIPTION

Definition of element The domain covered within the Activation Document.

Description The identification of the domain that is covered in the Activation Document. This covers what auction identifications may be used. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a domain identification is 18 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.

Applicability This information is dependeant.

Dependence requirements This is used depending on local market rules.

2.1.2.3.12 SUBJECTPARTY - CODINGSCHEME 213

ACTION DESCRIPTION

Definition of element The Party who is requesting the activation.

Description The party that is the Acquiring System Operator requesting the activation. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of this information is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



Page 19 of 53



for Electricity



VERSION 1.0

2.1.2.3.13 SUBJECT ROLE 214

ACTION DESCRIPTION

Definition of element The role of the Subject Party.

Description The role of the Subject Party. Refer to the ENTSO-E Code list document for valid role codes.

Size The maximum length of a Subject Role is 3 alphanumeric characters.



2.1.2.3.14 ORDERIDENTIFICATION 215

ACTION DESCRIPTION

Definition of element The identification of the Activation Order that is being acknowledged or in the case of a Redispatch activation it shall contain the Document Identification of the Redispatch Document

Description The Order Identification must reply to a previous Activation Order that has been received or in the case of a Redispatch activation it shall contain the Document Identification of the Redispatch Document.

Size The maximum length of an Order Identification is 35 alphanumeric characters.


Dependence requirements This is used only in the case where the document represents an Activation Response

2.1.2.3.15 ORDERIDENTIFICATIONVERSION 216

ACTION DESCRIPTION

Definition of element The version of the Activation Order that is being acknowledged or in the case of a Redispatch activation it shall contain the Document Version of the Redispatch Document.

Description The version of the Activation Order that has been received or in the case of a Redispatch activation it shall contain the Document Version of the Redispatch Document.



Dependence requirements This is used only in the case where the document represents an Activation Response.

217

Page 20 of 53



for Electricity



VERSION 1.0

2.1.2.4 RULES GOVERNING THE ACTIVATION TIME SERIES CLASS 218

This defines the time series that covers three aspects: 219

The time series identifying a tender that is to be activated as well as the relevant 220

periods and quantities. These time series can only exist with the document type 221

“activation”. 222

The time series that respond to an Activation order, identifying the time series being 223

activated and indicating the activation results (full, partial, or no longer available). 224

These time series can only exist with a document type “activation response”. 225

The time series that identify the tenders that are to be reduced. The quantities that 226

are available for the tender are provided. These time series can only exist with a 227

document type “tender reduction”. 228

At least one time series Period Class must have a Time Interval which has the same start 229

time as the Activation Time Interval. 230

2.1.2.4.1 ALLOCATIONIDENTIFICATION 231

ACTION DESCRIPTION

Definition of element The identification of the allocation that was established with the Resource Provider to provide reserves

Description A unique identification of the allocation to be activated This corresponds to a unique activation request. In the case of redispatch refer to transformation table in Table 1.

Size The maximum size of a allocation identification is 35 alphanumeric characters.



2.1.2.4.2 RESOURCEPROVIDER 232

ACTION DESCRIPTION

Definition of element The identification of the the Resource Provider related to the contract identification

Description A unique identification of the Resource Provider responsible for reserve activation. In the case of redispatch refer to transformation table in Table 1.

Size The maximum size of a Resource Provider identification is 35 alphanumeric characters.



Page 21 of 53



for Electricity



VERSION 1.0

2.1.2.4.3 BUSINESS TYPE 233

ACTION DESCRIPTION

Definition of element Identifies the nature of an time series.

Description The nature of the time series for which the product is handled. The following codes are permitted: A10 = Tertiary Control reserve A11 = Primary Control reserve A12 = Secondary Control reserve. A46 = System Operator redispatch

Size The maximum length of this information is 3 alphanumeric characters.



2.1.2.4.4 ACQUIRINGAREA - CODINGSCHEME 234

ACTION DESCRIPTION

Definition of element The area where the reserve is contracted for use.

Description The identification of the area where the reserve is destined. In the case of redispatch refer to transformation table in Table 1. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of the area code is 18 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



Page 22 of 53



for Electricity



VERSION 1.0

2.1.2.4.5 CONNECTINGAREA - CODINGSCHEME 235

ACTION DESCRIPTION

Definition of element The area where from the Reserve Object is located.

Description The identification of the area where the Reserve Object is located. In the case of redispatch refer to transformation table in Table 1. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.



Dependence requirements None

2.1.2.4.6 MEASUREUNIT 236

ACTION DESCRIPTION

Definition of element The unit of measure in which the quantities in the time series are expressed.

Description The unit of measurement used for the quantities expressed within the time series. In the case of redispatch refer to transformation table in Table 1. It is recommended that this be always expressed in megawatts (code MAW). Refer to the ENTSO-E Code list document for valid codes.



Page 23 of 53



for Electricity



VERSION 1.0

2.1.2.4.7 DIRECTION 237

ACTION DESCRIPTION

Definition of element Identifies how the energy flow is to be seen from the perspective of the Acquiring System Operator’s area.

Description This identifies the direction of the energy flow. Refer to paragraph 4.3 for more information. In the case of redispatch refer to transformation table in Table 1. Refer to the ENTSO-E Code list document for valid codes. permitted codes are: A01 = UP, this signifies that the available power can be used by the Acquiring area to increase energy. A02 = DOWN, this signifies that the available power can be used by the Acquiring area to decrease energy. A03 = UP and DOWN, this signifies that the UP and Down values are equal.



Page 24 of 53



for Electricity



VERSION 1.0

2.1.2.4.8 STATUS 238

ACTION DESCRIPTION

Definition of element The status of the specific activation request.

Description This information defines the status of the activation request within the document. The permitted status codes are as follows: A08 = In process – the quantities in the time series are requested for activation. A10 = Ordered – the quantities in the time series are to be activated. A07 = Activated – the quantities in the time series have been activated. A11 = No longer available - the tender indicated in the time series is no longer available (in the case where this is in an activation response document the resources are no longer available to the Acquiring System Operator). A06 = Available – the tender indicated in the time series has the indicated quantities available. A09 = cancelled – the tender indicated in the time series has been completely cancelled. In this case the resources are no longer available to all Acquiring System Operators

Size The status is 3 alpha numeric characters long.



Page 25 of 53



for Electricity



VERSION 1.0

2.1.2.4.9 RESOURCE OBJECT –CODING SCHEME 239

ACTION DESCRIPTION

Definition of element Identification of the resource that is used to supply energy capabilities to the System Operator.

Description This identifies the Reserve Object managed by the Resource Provider that is used to supply the energy capabilities. In the case of redispatch refer to transformation table in Table 1. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.



Dependence requirements A Resource Object is only used if a specific Resource Object is to be activated.

2.1.2.5 RULES GOVERNING THE PERIOD CLASS 240

For SATCR activation there may be several period classes for a time series. 241

For DATCR activation only one Period class is permitted. 242

If a time series is cancelled then a Period class must not be provided. 243

In a SATCR activation, where a Period is provided: 244

The overall time interval covered by the period classes shall be within the activation 245

time interval. 246

The resolution must be constant throughout the time series. A time series is 247

suppressed by zeroing out all the interval quantities. 248

A sender’s minimal resolution must respect market rules. 249

At least one Period must have the start time of the Valid Period. 250

At least one Period must have the end time of the Valid Period. 251

The start and end Period may be spanned over several times series. 252

In a DATCR activation, one Period class must be provided: 253

The overall time interval covered by the period class shall be equal to or within the 254

Activation Time Interval. 255

The resolution must correspond to the overall time interval (e.g. there is only one 256

interval). 257

Page 26 of 53



for Electricity



VERSION 1.0

2.1.2.5.1 TIME INTERVAL 258

ACTION DESCRIPTION

Definition of element The start and end date and time of the time interval of the period in question.

Description This information provides the start and end date and time of the period being reported.

Size The start and end date and time must be expressed in compliance with the following format: YYYY-MM-DDTHH:MMZ/YYYY-MM-DDTHH:MMZ.



2.1.2.5.2 RESOLUTION 259

ACTION DESCRIPTION

Definition of element The resolution defining the number of periods that the time interval is divided.

Description This information defines the resolution of a single period. The time interval must contain a whole number of periods as expressed by the resolution.

Size The resolution is expressed in compliance with ISO 8601 in the following format: PnYnMnDTnHnMnS. Where nY expresses a number of years, nM a number of months, nD a number of days. The letter “T” separates the date expression from the time expression and after it nH identifies a number of hours, nM a number of minutes and nS a number of seconds. For example PT15M expresses a 15 minute resolution.



260

2.1.2.6 RULES GOVERNING THE INTERVAL CLASS 261

The interval class contains the relative position within a time interval period and the quantity 262

associated with that position. 263

The position must begin with 1 and increment by 1 for each subsequent position forming a 264

series of contiguous numbers covering the complete range of the period. 265

Any leading zeros in a position shall be suppressed. 266

Page 27 of 53



for Electricity



VERSION 1.0

Negative values are not allowed in time series quantities. 267

Leading zeros in a quantity shall be suppressed before transmission. 268

In a DATCR activation only one Interval class is permitted. 269

2.1.2.6.1 POS 270

ACTION DESCRIPTION

Definition of element The relative position of a period within an activation interval.

Description This information provides the relative position of a period within an activation interval.

Size The relative position must be expressed as a numeric integer value beginning with 1. All leading zeros must be suppressed. The maximum number of characters is 6.



2.1.2.6.2 QTY 271

ACTION DESCRIPTION

Definition of element The quantity that is to be activated for the interval in question.

Description This information defines the quantity that is to be activated for the interval in question and that is expressed in the Measurement Unit Quantity. A decimal point value may be used to express values that are inferior to the defined unit of measurement. The decimal mark that separates the digits forming the integral part of a number from those forming the fractional part (ISO 6093) shall always be a period (“.”). All quantities shall be non-signed.

Size The maximum length of this information is 17 numeric characters (decimal mark and sign, if used, included). The number of decimal places identifying the fractional part of the quantity depends on local market rules.



2.1.2.7 RULES GOVERNING THE REASON CLASS 272

In an Activation Document reason codes can be provided two levels: 273

At the time series level to identify where differences have occurred. 274

Page 28 of 53



for Electricity



VERSION 1.0

At the interval level to indicate where quantities have been decreased. 275

2.1.2.7.1 REASON CODE 276

ACTION DESCRIPTION

Definition of element A code providing the freason for a change.. The following Reason Codes are permitted: At the timeseries level: A63 = Time series modified A27 = Cross border capacity exceeded A57 = Deadline limit exceeded A96 = Technical constraint A95 = Complementry information A59 = Not compliant with local market rules At the interval level: A44 = Quantity decreased A95 = Complementry information A59 = Not compliant with local market rules Other codes defined in the ENTSO-E Code List of Reason Codes may be used as required by local market rules.

Description The reason code provides the status of the item being confirmed. As many reason elements as necessary may be used.



Dependence requirements This information dependent at the time series level to provide related explanatory information for deviations from the original schedule. It may also appear at the Interval level to detail modifications at this level.

2.1.2.7.2 REASON TEXT 277

ACTION DESCRIPTION

Definition of element Textual explanation of the confirmation information.

Description If the code does not provide all the information to clearly identify an Reason code, the reason text may be used.



Dependence requirements Used only if the reason code is insufficient to identify a given situation.

Page 29 of 53



for Electricity



VERSION 1.0

2.2 TRANSMISSION OF HISTORICAL ACTIVATION INFORMATION 278

Note : This section is new to the current ERRP process and will be added to the revised 279

implementation guide. 280

In some contexts it may be necessary to transmit the complete history activation activity for a 281

given period. 282

This is a one-off transmission that may be sent at any time in response to a status request 283

document. 284

Page 30 of 53



for Electricity



VERSION 1.0

2.2.1 ACTIVATION HISTORY DOCUMENT 285

286

FIGURE 4: HISTORICAL ACTIVATION DOCUMENT 287

Page 31 of 53



for Electricity



VERSION 1.0

2.2.1.1 DOCUMENT IDENTIFICATION 288

ACTION DESCRIPTION

Definition of element Unique identification of the document for which the time series data is being supplied.

Description A Historical Activation Document for a given set of time series and a given activation period must have a unique identification assigned by the sender of the document for all transmissions to the receiver. All additions, modifications, or suppressions for the time series and activation period must use the same identification.

Size The identification of a document may not exceed 35 alphanumeric characters.


Dependence requirements None

2.2.1.2 DOCUMENT VERSION 289

ACTION DESCRIPTION

Definition of element Version of the document being sent.





Page 32 of 53



for Electricity



VERSION 1.0

2.2.1.3 DOCUMENT TYPE 290

ACTION DESCRIPTION

Definition of element The coded type of the document being sent.

Description The document type identifies the information flow characteristics. The following type is permitted: A97 = Detailled history of activations. A98 = Aggregated history of activations

Size The document type value must be exactly 3 alphanumeric characters (no blanks).



2.2.1.4 PROCESS TYPE 291

ACTION DESCRIPTION

Definition of element The nature of the process that the document is directed at.

Description The process type identifies the process to which the information flow is directed. Permitted codes are: A42 = Activation history. A28 = Primary reserve process A29 = Secondary reserve process A30 = Tertiary reserve process A96 = Redispatch activation



Dependence requirements The dependency requirement is uniquely to ensure backwards compatibility. If a version 5 transmission is implemented then this attribute is mandatory.

Page 33 of 53



for Electricity



VERSION 1.0

2.2.1.5 SENDER IDENTIFICATION – CODING SCHEME 292

ACTION DESCRIPTION

Definition of element Identification of the party that is the owner of the document and is responsible for its content.

Description The sender of the document is identified by a unique coded identification. This code identifies the party that is the “owner” of the information being transmitted in the document and who is responsible for its content. In general this identifies the Acquiring System Operator or its representative. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a sender’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



2.2.1.6 SENDER ROLE 293

ACTION DESCRIPTION

Definition of element Identification of the role that is played by the sender.

Description The sender role, which identifies the role of the sender within the document. In general this corresponds to the System Operator. Refer to the ENTSO-E Code list document for valid role codes.

Size The maximum length of a sender role is 3 alphanumeric characters.



Page 34 of 53



for Electricity



VERSION 1.0

2.2.1.7 RECEIVER IDENTIFICATION – CODING SCHEME 294

ACTION DESCRIPTION

Definition of element Identification of the party who is receiving the document.

Description The receiver of the document is identified by a unique coded identification. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a receiver’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



2.2.1.8 RECEIVER ROLE 295

ACTION DESCRIPTION

Definition of element Identification of the role played by the receiver.

Description The receiver role, which identifies the role of the receiver within the document. Refer to the ENTSO-E Code list document for valid role codes.

Size The maximum length of a receiver role is 3 alphanumeric characters.



2.2.1.9 CREATION DATE AND TIME 296

ACTION DESCRIPTION

Definition of element Date and time of creation of the document.

Description The date and time that the document was prepared for transmission by the application of the sender.

Size The date and time must be expressed in UTC as: YYYY-MM-DDTHH:MM:SSZ.



Page 35 of 53



for Electricity



VERSION 1.0

2.2.1.10 ACTIVATION HISTORY TIME INTERVAL 297

ACTION DESCRIPTION

Definition of element The beginning and ending date and time of the period covered by the document where the energy has been activated.

Description This information provides the start and end date and time of the historical activation period.




2.2.1.11 DOMAIN - CODINGSCHEME 298

ACTION DESCRIPTION

Definition of element The domain covered within the Activation Document.

Description The identification of the domain that is covered in the Activation Document. This covers what auction identifications may be used. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a domain identification is 18 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



299

Page 36 of 53



for Electricity



VERSION 1.0

2.2.2 RULES GOVERNING THE ACTIVATION TIME SERIES 300

CLASS 301

This defines the time series that covers three aspects: 302

The time series identifying a tender that is to be activated as well as the relevant periods and 303

quantities. These time series can only exist with the document type “activation”. 304

The time series that respond to an Activation order, identifying the time series being 305

activated and indicating the activation results (full, partial, or no longer available). These time 306

series can only exist with a document type “activation response”. 307

The time series that identify the tenders that are to be reduced. The quantities that are 308

available for the tender are provided. These time series can only exist with a document type 309

“tender reduction”. 310

At least one time series Period Class must have a Time Interval which has the same start 311

time as the Activation Time Interval. 312

2.2.2.1 ACTIVATION IDENTIFICATION 313

ACTION DESCRIPTION

Definition of element The identification of the activation document requesting or confirming activation

Description A unique identification of the activation request or confirmation

Size The maximum size of a activiation identification is 35 alphanumeric characters.


Dependence requirements This is used for detailed activation history information. It is not used for aggregated historic information.

Page 37 of 53



for Electricity



VERSION 1.0

2.2.2.2 ACTIVATION VERSION 314

ACTION DESCRIPTION

Definition of element Version of the activation request or response.





2.2.2.3 ACTIVATION PROCESS TYPE 315

ACTION DESCRIPTION

Definition of element The nature of the process of the activation document.

Description The process type identifies the process to which the information flow was directed. Permitted codes are: A28 = Primary reserve process A29 = Secondary reserve process A30 = Tertiary reserve process A96 = Redispatch activation




Page 38 of 53



for Electricity



VERSION 1.0

2.2.2.4 REQUESTING PARTY – CODING SCHEME 316

ACTION DESCRIPTION

Definition of element Identification of the party that requested the activation.

Description The requestor of the activation is identified by a unique coded identification. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a requesting party’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



2.2.2.5 ACTIVATING PARTY – CODING SCHEME 317

ACTION DESCRIPTION

Definition of element Identification of the party who carried out the activation.

Description The party that carried out the activation is identified by a unique coded identification. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.

Size The maximum length of a activating party’s identification is 16 alphanumeric characters. The maximum length of the coding scheme code is 3 alphanumeric characters.



Page 39 of 53



for Electricity



VERSION 1.0

2.2.2.6 ACTIVATION TIME INTERVAL 318

ACTION DESCRIPTION

Definition of element The beginning and ending date and time of the period of the activation.

Description This information provides the start and end date and time of the activation period.




2.2.2.7 ALLOCATIONIDENTIFICATION 319

ACTION DESCRIPTION

Definition of element The identification of the allocation that was established with the Resource Provider to provide reserves

Description A unique identification of the allocation to be activated This corresponds to a unique activation request.

Size The maximum size of a allocation identification is 35 alphanumeric characters.



2.2.2.8 RESOURCEPROVIDER 320

ACTION DESCRIPTION

Definition of element The identification of the the Resource Provider related to the contract identification

Description A unique identification of the Resource Provider responsible for reserve activation.

Size The maximum size of a Resource Provider identification is 35 alphanumeric characters.



Page 40 of 53



for Electricity



VERSION 1.0

2.2.2.9 BUSINESS TYPE 321

ACTION DESCRIPTION

Definition of element Identifies the nature of an time series.

Description The nature of the time series for which the product is handled. The following codes are permitted: A10 = Tertiary Control reserve A11 = Primary Control reserve A12 = Secondary Control reserve.




2.2.2.10 ACQUIRINGAREA - CODINGSCHEME 322

ACTION DESCRIPTION

Definition of element The area where the reserve is contracted for use.

Description The identification of the area where the reserve is destined. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.




Page 41 of 53



for Electricity



VERSION 1.0

2.2.2.11 CONNECTINGAREA - CODINGSCHEME 323

ACTION DESCRIPTION

Definition of element The area where from the Reserve Object is located.

Description The identification of the area where the Reserve Object is located. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.




2.2.2.12 MEASUREUNIT 324

ACTION DESCRIPTION

Definition of element The unit of measure in which the quantities in the time series are expressed.

Description The unit of measurement used for the quantities expressed within the time series. It is recommended that this be always expressed in megawatts (code MAW). Refer to the ENTSO-E Code list document for valid codes.



Page 42 of 53



for Electricity



VERSION 1.0

2.2.2.13 DIRECTION 325

ACTION DESCRIPTION

Definition of element Identifies how the energy flow is to be seen from the perspective of the Acquiring System Operator’s area.

Description This identifies the direction of the energy flow. Refer to the ENTSO-E Code list document for valid codes. permitted codes are: A01 = UP, this signifies that the available power can be used by the Acquiring area to increase energy. A02 = DOWN, this signifies that the available power can be used by the Acquiring area to decrease energy. A03 = UP and DOWN, this signifies that the UP and Down values are equal.




Page 43 of 53



for Electricity



VERSION 1.0

2.2.2.14 STATUS 326

ACTION DESCRIPTION

Definition of element The status of the specific activation request.

Description This information defines the status of the activation request within the document. The permitted status codes are as follows: A08 = In process – the quantities in the time series are requested for activation. A10 = Ordered – the quantities in the time series are to be activated. A07 = Activated – the quantities in the time series have been activated. A11 = No longer available - the tender indicated in the time series is no longer available (in the case where this is in an activation response document the resources are no longer available to the Acquiring System Operator). A06 = Available – the tender indicated in the time series has the indicated quantities available. A09 = cancelled – the tender indicated in the time series has been completely cancelled. In this case the resources are no longer available to all Acquiring System Operators

Size The status is 3 alpha numeric characters long.


Page 44 of 53



for Electricity



VERSION 1.0

2.2.2.15 RESOURCE OBJECT –CODING SCHEME 327

ACTION DESCRIPTION

Definition of element Identification of the resource that is used to supply energy capabilities to the System Operator.

Description This identifies the Reserve Object managed by the Resource Provider that is used to supply the energy capabilities. The codification scheme used for the coded identification is indicated by the coding scheme attribute. It is a 3 character alphanumeric code. Refer to the ENTSO-E Code list document for valid coding scheme codes.



Dependence requirements A Resource Object is only used if a specific Resource Object is to be activated.

328

2.2.3 Rules governing the period class 329

For SATCR activation there may be several period classes for a time series. 330

For DATCR activation only one Period class is permitted. 331

If a time series is cancelled then a Period class must not be provided. 332

In a SATCR activation, where a Period is provided: 333

The overall time interval covered by the period classes shall be within the activation 334

time interval. 335

The resolution must be constant throughout the time series. A time series is 336

suppressed by zeroing out all the interval quantities. 337

A sender’s minimal resolution must respect market rules. 338

At least one Period must have the start time of the Valid Period. 339

At least one Period must have the end time of the Valid Period. 340

The start and end Period may be spanned over several times series 341

In a DATCR activation, one Period class must be provided: 342

The overall time interval covered by the period class shall be equal to or within the 343

Activation Time Interval. 344

The resolution must correspond to the overall time interval (e.g. there is only one 345

interval). 346

Page 45 of 53



for Electricity



VERSION 1.0

2.2.3.1 TIME INTERVAL 347

ACTION DESCRIPTION

Definition of element The start and end date and time of the time interval of the period in question.

Description This information provides the start and end date and time of the period being reported.

Size The start and end date and time must be expressed in compliance with the following format: YYYY-MM-DDTHH:MMZ/YYYY-MM-DDTHH:MMZ.



2.2.3.2 RESOLUTION 348

ACTION DESCRIPTION

Definition of element The resolution defining the number of periods that the time interval is divided.

Description This information defines the resolution of a single period. The time interval must contain a whole number of periods as expressed by the resolution.

Size The resolution is expressed in compliance with ISO 8601 in the following format: PnYnMnDTnHnMnS. Where nY expresses a number of years, nM a number of months, nD a number of days. The letter “T” separates the date expression from the time expression and after it nH identifies a number of hours, nM a number of minutes and nS a number of seconds. For example PT15M expresses a 15 minute resolution.



349

2.2.4 RULES GOVERNING THE INTERVAL CLASS 350

The interval class contains the relative position within a time interval period and the quantity 351

associated with that position. 352

The position must begin with 1 and increment by 1 for each subsequent position forming a 353

series of contiguous numbers covering the complete range of the period. 354

Any leading zeros in a position shall be suppressed. 355

Page 46 of 53



for Electricity



VERSION 1.0

Negative values are not allowed in time series quantities. 356

Leading zeros in a quantity shall be suppressed before transmission. 357

In a DATCR activation only one Interval class is permitted. 358

2.2.4.1 POS 359

ACTION DESCRIPTION

Definition of element The relative position of a period within an activation interval.

Description This information provides the relative position of a period within an activation interval.

Size The relative position must be expressed as a numeric integer value beginning with 1. All leading zeros must be suppressed. The maximum number of characters is 6.



2.2.4.2 QTY 360

ACTION DESCRIPTION

Definition of element The quantity that is to be activated for the interval in question.

Description This information defines the quantity that is to be activated for the interval in question and that is expressed in the Measurement Unit Quantity. A decimal point value may be used to express values that are inferior to the defined unit of measurement. The decimal mark that separates the digits forming the integral part of a number from those forming the fractional part (ISO 6093) shall always be a period (“.”). All quantities shall be non-signed.

Size The maximum length of this information is 17 numeric characters (decimal mark and sign, if used, included). The number of decimal places identifying the fractional part of the quantity depends on local market rules.



361

Page 47 of 53



for Electricity



VERSION 1.0

2.2.5 RULES GOVERNING THE REASON CLASS 362

In an Activation Document reason codes can be provided two levels: 363

At the time series level to identify where differences have occurred. 364

At the interval level to indicate where quantities have been decreased. 365

2.2.5.1 REASON CODE 366

ACTION DESCRIPTION

Definition of element A code providing the freason for a change.. The following Reason Codes are permitted: At the timeseries level: A63 = Time series modified A27 = Cross border capacity exceeded A57 = Deadline limit exceeded A96 = Technical constraint A95 = Complementry information A59 = Not compliant with local market rules At the interval level: A44 = Quantity decreased A95 = Complementry information A59 = Not compliant with local market rules Other codes defined in the ENTSO-E Code List of Reason Codes may be used as required by local market rules.

Description The reason code provides the status of the item being confirmed. As many reason elements as necessary may be used.



Dependence requirements This information dependent at the time series level to provide related explanatory information for deviations from the original schedule. It may also appear at the Interval level to detail modifications at this level.

Page 48 of 53



for Electricity



VERSION 1.0

2.2.5.2 REASON TEXT 367

ACTION DESCRIPTION

Definition of element Textual explanation of the confirmation information.

Description If the code does not provide all the information to clearly identify an Reason code, the reason text may be used.



Dependence requirements Used only if the reason code is insufficient to identify a given situation.

368

2.3 CORRECTION TO THE RESTRICTED CODELIST OF THE MOL 369

DOCUMENT 370

The Restricted code schema for the MOL Document for the codelists listed below has been 371

specified in a manner where the use of the Local codelist restrictions is not possible. It does 372

not prevent the normal execution of the Schemas where no local code restriction is required. 373

2.3.1 PROCESSTYPE 374

The current specification in the restricted codelist is as follows: 375

<xsd:complexType name="ProcessType"> 376

<xsd:attribute name="v" type="RestrictedProcessType" use="required"/> 377

</xsd:complexType> 378

<xsd:simpleType name="RestrictedProcessType"> 379

<xsd:restriction base="ecl:StandardProcessTypeList"> 380

<xsd:enumeration value="A27"/> 381




</xsd:restriction> 385

</xsd:simpleType> 386

It should be specified as follows : 387

<xsd:complexType name="ProcessType"> 388

<xsd:attribute name="v" type="RestrictedProcessType" use="required"/> 389


<xsd:simpleType name="StandardRestrictedProcessType"> 391

<xsd:restriction base="ecl:StandardProcessTypeList"> 392







<xsd:simpleType name="RestrictedProcessType"> 399

<xsd:union memberTypes="StandardRestrictedProcessType LocalRestrictedProcessType"/> 400


Page 49 of 53



for Electricity



VERSION 1.0

2.3.2 BUSINESSTYPE 402

<xsd:complexType name="BusinessType"> 403

<xsd:attribute name="v" type="RestrictedBusinessType" use="required"/> 404


<xsd:simpleType name="RestrictedBusinessType"> 406

<xsd:restriction base="ecl:StandardBusinessTypeList"> 407







<xsd:complexType name="BusinessType"> 414

<xsd:attribute name="v" type="RestrictedBusinessType" use="required"/> 415


<xsd:simpleType name="StandardRestrictedBusinessType"> 417

<xsd:restriction base="ecl:StandardBusinessTypeList"> 418






<xsd:simpleType name="RestrictedBusinessType"> 424

<xsd:union memberTypes="StandardRestrictedBusinessType LocalRestrictedBusinessType"/> 425


2.3.3 REASONTYPE 427

<xsd:complexType name="ReasonCodeType"> 428

<xsd:attribute name="v" type="RestrictedReasonCodeType" use="required"/> 429


<xsd:simpleType name="RestrictedReasonCodeType"> 431

<xsd:restriction base="ecl:StandardReasonCodeTypeList"> 432








<xsd:complexType name="ReasonCodeType"> 440

<xsd:attribute name="v" type="RestrictedReasonCodeType" use="required"/> 441


<xsd:simpleType name="StandardRestrictedReasonCodeType"> 443

<xsd:restriction base="ecl:StandardReasonCodeTypeList"> 444







<xsd:simpleType name="RestrictedReasonCodeType"> 451

<xsd:union memberTypes="StandardRestrictedReasonCodeType 452

LocalRestrictedReasonCodeType"/> 453


Page 50 of 53



for Electricity



VERSION 1.0

2.4 CORRECTION TO THE DATATYPE OF THE DOMAIN IN THE MOL 455

DOCUMENT 456

The DataType of the Domain in the header of the MOL document is currently incorrect 457

(ResourceObjectType). It should be changed to “AreaType”. This impacts the model as well 458

as the XSD. 459

460

FIGURE 5: REVISED MOL DOCUMENT MODEL 461

Page 51 of 53



for Electricity



VERSION 1.0

2.5 CORRECTION TO THE DATATYPE OF THE DOMAIN IN THE 462


The DataType of the Domain in the header of the Activation document is currently incorrect 464


as the XSD. 466

467

FIGURE 6: REVISED ACTIVATION DOCUMENT MODEL 468

Page 52 of 53



for Electricity



VERSION 1.0

2.6 CORRECTION TO THE DATATYPE OF THE DOMAIN IN THE 469

REDISPATCH DOCUMENT 470

The DataType of the Domain in the header of the Redispatch document is currently incorrect 471


as the XSD. 473

474

FIGURE 7: REVISED REDISPATCH DOCUMENT MODEL 475

Page 53 of 53



for Electricity



VERSION 1.0

2.7 CORRECTION TO THE DEFAULT NAMESPACE OF THE 476


The header of the Action Document XSD currently reads as follows: 478

<?xml version="1.0" encoding="UTF-8"?> 479

<xsd:schema xmlns:ecc="urn:entsoe.eu:wgedi:components" 480

xmlns:xsd="http://www.w3.org/2001/XMLSchema" 481

xmlns="urn:entsoe.eu:wgedi:errp:activatondocument:5:0" 482

targetNamespace="urn:entsoe.eu:wgedi:errp:activatondocument:5:0" 483

elementFormDefault="qualified" attributeFormDefault="unqualified" 484

ecc:VersionRelease="15.0"> 485

It can be noted that the default namespace reads “activatondocument” where it should read 486

“activationdocument”. This is also true naturally enough for the targetNamespace. 487

The correct namespace name should be: 488

<?xml version="1.0" encoding="UTF-8"?> 489

<xsd:schema xmlns:ecc="urn:entsoe.eu:wgedi:components" 490

xmlns:xsd="http://www.w3.org/2001/XMLSchema" 491

xmlns="urn:entsoe.eu:wgedi:errp: activationdocument:5:0" 492

targetNamespace="urn:entsoe.eu:wgedi:errp:activationdocument:5:0" 493

elementFormDefault="qualified" attributeFormDefault="unqualified" 494

ecc:VersionRelease="15.0"> 495

These changes of the schema will only be incorporated in the schemas for release 6 of 496

ERRP. The existing XSD of the Activation Document in release 5 shall continue to be used 497

until the formal release of ERRP 6.0 that will incorporate the complete corrigendum. 498