ENTSO-E CGMA DATA EXCHANGES IMPLEMENTATION GUIDE

European Network of

Transmission System Operators

for Electricity

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

1

2016-12-07

DOCUMENT – APPROVED

VERSION 1.0

ENTSO-E

CGMA DATA EXCHANGES

IMPLEMENTATION GUIDE

– Page 2 of 41 –

European Network of

Transmission System Operators for

Electricity

ENTSO-E CGMA data exchanges implementation guide

VERSION 1.0


Table of Contents 2

1 Scope ................................................................................................................................................8 3

2 Terms and Definitions ......................................................................................................................8 4

3 The common grid model alignment (CGMA) business processes................................................. 10 5

3.1 Overview ........................................................................................................................ 10 6

3.2 Overall business context ................................................................................................ 10 7

3.3 Use cases........................................................................................................................ 10 8

3.4 Document exchange processes ..................................................................................... 12 9

Overview .................................................................................................... 12 10

Submit pre-processing data ....................................................................... 13 11

Send escalation notification ....................................................................... 14 12

Send input data and CGMA results ............................................................ 14 13

Request substitute data ............................................................................. 15 14

Request CGMA results ............................................................................... 16 15

4 General rules for document exchange .......................................................................................... 18 16

4.1 General rules .................................................................................................................. 18 17

4.2 Notes about using StatusRequest_MarketDocument in CGMA document 18

exchange ........................................................................................................................ 19 19

4.3 Notes about using ProblemStatement_MarketDocument as an escalation 20

notification ..................................................................................................................... 20 21

5 Using the ReportingInformation_MarketDocument in CGMA ..................................................... 21 22

5.1 Overview ........................................................................................................................ 21 23

5.2 Rules governing ReportingInformation_MarketDocument to submit pre-24

processing data .............................................................................................................. 21 25

5.3 Rules governing ReportingInformation_MarketDocument to reply substitute 26

data ................................................................................................................................ 23 27

5.4 Rules governing ReportingInformation_MarketDocument to send input data 28

and CGMA results .......................................................................................................... 24 29

5.5 Rules governing ReportingInformation_MarketDocument to reply CGMA 30

results ............................................................................................................................ 27 31

5.6 Additional rules governing the use of TimeSeries ......................................................... 28 32

6 ReportingInformation_MarketDocument ..................................................................................... 30 33

6.1 Reporting information contextual model ...................................................................... 30 34

Overview of the model ............................................................................... 30 35

IsBasedOn relationships from the European style market profile ............. 30 36

6.2 Reporting information assembly model ........................................................................ 32 37

Overview of the model ............................................................................... 32 38

IsBasedOn relationships from the European style market profile ............. 32 39

Detailed Reporting information assembly model ...................................... 33 40

– Page 3 of 41 –

European Network of


Electricity


VERSION 1.0


6.2.3.1 ReportingInformation_MarketDocument root class ............................. 33 41

6.2.3.2 Point ....................................................................................................... 34 42

6.2.3.3 Reason .................................................................................................... 35 43

6.2.3.4 Series_Period ......................................................................................... 35 44

6.2.3.5 TimeSeries .............................................................................................. 36 45

Datatypes ................................................................................................... 37 46

ReportingInformation_MarketDocument XML schema ............................ 38 47

7 References ..................................................................................................................................... 41 48

List of figures 49

Figure 1 – Use cases ......................................................................................................................... 11 50

Figure 2 – Sequence diagram for submission................................................................................ 13 51

Figure 3 – Sequence diagram for request substitute data ........................................................... 15 52

Figure 4 – Sequence diagram for request CGMA results ............................................................ 16 53

Figure 5 - Reporting information contextual model ............................................................................. 30 54

Figure 6 - Reporting information assembly model ................................................................................ 32 55

Figure 7 - Reporting information schema structure 1/2 ....................................................................... 39 56

Figure 8 - Reporting information schema structure 2/2 ....................................................................... 40 57

List of tables 58

Table 1 – Actor labels and descriptions................................................................................................. 11 59

Table 2 – CGMA data exchange............................................................................................................. 11 60

Table 3 – Time series of pre-processing data ........................................................................................ 13 61

Table 4 – Time series of input data ....................................................................................................... 14 62

Table 5 – Time series of CGMA results .................................................................................................. 15 63

Table 6 – Time series of substitute data ............................................................................................... 16 64

Table 7 – Time series of CGMA results .................................................................................................. 16 65

Table 8 – List of documents for CGMA process exchanges ................................................................... 18 66

Table 9 – StatusRequest_MarketDocument header values .................................................................. 19 67

Table 10 – StatusRequest_MarketDocument AttributeInstanceComponent values ............................ 19 68

Table 11 – ProblemStatement_MarketDocument header values ........................................................ 20 69

Table 12 – ReportingInformation_MarketDocument header ............................................................... 21 70

Table 13 – ReportingInformation_MarketDocument.TimeSeries elements ......................................... 22 71






– Page 4 of 41 –

European Network of


Electricity


VERSION 1.0



Table 20 - IsBasedOn dependency ........................................................................................................ 30 78

Table 21 - IsBasedOn dependency ........................................................................................................ 33 79

Table 22 - Attributes of Reporting information assembly 80

model::ReportingInformation_MarketDocument ................................................................................ 33 81

Table 23 - Association ends of Reporting information assembly 82

model::ReportingInformation_MarketDocument with other classes .................................................. 34 83

Table 24 - Attributes of Reporting information assembly model::Point ............................................... 35 84

Table 25 - Association ends of Reporting information assembly model::Point with other 85

classes .................................................................................................................................................... 35 86

Table 26 - Attributes of Reporting information assembly model: Reason ............................................ 35 87

Table 27 - Attributes of Reporting information assembly model: Series_Period ................................. 36 88

Table 28 - Association ends of Reporting information assembly model: Series_Period with 89

other classes .......................................................................................................................................... 36 90

Table 29 - Attributes of Reporting information assembly model: TimeSeries ...................................... 36 91

Table 30 - Association ends of Reporting information assembly model: TimeSeries with other 92

classes .................................................................................................................................................... 37 93

94

– Page 5 of 41 –

European Network of


Electricity


VERSION 1.0


Copyright notice: 95

Copyright © ENTSO-E. All Rights Reserved. 96

This document and its whole translations may be copied and furnished to others, and 97 derivative works that comment on or otherwise explain it or assist in its implementation may 98 be prepared, copied, published and distributed, in whole or in part, without restriction of any 99 kind, provided that the above copyright notice and this paragraph are included on all such 100 copies and derivative works. However, this document itself may not be modified in any way, 101 except for literal and whole translation into languages other than English and under all 102 circumstances, the copyright notice or references to ENTSO-E may not be removed. 103

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

ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 105 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 106 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 107 FITNESS FOR A PARTICULAR PURPOSE. 108

Maintenance notice: 109

This document is maintained by the ENTSO-E WG EDI. Comments or remarks are to be 110 provided at [email protected] 111

mailto:[email protected]

– Page 6 of 41 –

European Network of


Electricity


VERSION 1.0


Revision History 112

Version Release Date Comments

1 0 2016-12-07 Approved by MC

113

– Page 7 of 41 –

European Network of


Electricity


VERSION 1.0


NOTE CONCERNING WORDING USED IN THIS DOCUMENT 114

The force of the following words is modified by the requirement level of the document in which 115 they are used. 116

MUST: This word, or the terms “REQUIRED” or “SHALL”, means that the definition is an 117 absolute requirement of the specification. 118

MUST NOT: This phrase, or the phrase “SHALL NOT”, means that the definition is an 119 absolute prohibition of the specification. 120

SHOULD: This word, or the adjective “RECOMMENDED”, means that there may exist valid 121 reasons in particular circumstances to ignore a particular item, but the full implications must 122 be understood and carefully weighed before choosing a different course. 123

SHOULD NOT: This phrase, or the phrase “NOT RECOMMENDED”, means that there may 124 exist valid reasons in particular circumstances when the particular behaviour is acceptable or 125 even useful, but the full implications should be understood and the case carefully weighed 126 before implementing any behaviour described with this label. 127

MAY: This word, or the adjective “OPTIONAL”, means that an item is truly optional. One 128 vendor may choose to include the item because a particular marketplace requires it or 129 because the vendor feels that it enhances the product while another vendor may omit the 130 same item. An implementation which does not include a particular option MUST be prepared 131 to interoperate with another implementation which does include the option, though perhaps 132 with reduced functionality. In the same vein an implementation which does include a particular 133 option MUST be prepared to interoperate with another implementation which does not include 134 the option (except, of course, for the feature the option provides.) 135

DEPRECATED: this word means that a previously permitted entity should no longer be used 136 in new implementations as in a future release the object in question may be suppressed. 137

138

– Page 8 of 41 –

European Network of


Electricity


VERSION 1.0


1 Scope 139

The scope of this implementation guide is to describe how to implement the data exchanges 140 related to the Common Grid Model Alignment (CGMA) platform. 141

2 Terms and Definitions 142

CGM: Common Grid Model 143

CGMA: Common Grid Model Alignment; a process that ensures the availability of a set of 144 balanced netted area positions and balanced DC flows for all optimisation areas covered for 145 those target time-horizons for which CGMs are built but for which market schedules are not 146 available. CGMA involves applying a set of rules and methods, notably including the CGMA 147 algorithm, to the CGMA input data in order to obtain the CGMA output data (which include the 148 CGMA results). 149

CGMA input data: For the purposes of this implementation guide, the terms "CGMA input 150 data" and "PPD" can be used interchangeably. 151

CGMA output data: The CGMA output data have three components: 1. the CGMA results; 2. 152 the CGMA input data originally sent to the CGMA platform; 3. the substituted and / or modified 153 CGMA input data (if applicable) 154

CGMA results: The CGMA results are the outcome of applying the CGMA algorithm to the 155 CGMA input data (the PPD) and consist of, for each relevant optimisation area and for each 156 relevant scenario, the following elements: 157

--balanced netted area position 158

--balanced flows on all DC lines (where applicable) 159

Also part of the CGMA results are 160

--indicative AC flows per electrical border 161

--AC net positions 162

CGMA results are a subset of the CGMA output data. 163

CGMA target time-horizon: The time period for which CGMA results are to be obtained. In 164 the case of the (D-2) target time-horizon, for example, this will typically encompass the 165 twenty-four individual hours (respectively twenty-three or twenty-five for daylight saving) from 166 00:00h two days after the day on which the CGMA calculations are run until 24:00h of that 167 day. The CGMA target time-horizon will thus typically encompass multiple scenarios. 168

CGMA platform: The IT System which, among other tasks, runs the CGMA algorithm. 169

Optimisation area: Basic geographical reference unit for the CGMA process. CGMA input 170 data are provided on the level of optimisation areas and so are the CGMA results. Each 171 optimisation area corresponds exactly to a geographical area for which an individual grid 172 model is prepared; i.e., there is a one-to-one correspondence between optimisation areas and 173 IGMs. 174

CGMA area: The CGMA area corresponds to the CGM area. The CGM area is the set of (i) 175 bidding zones whose TSOs contribute their individual grid model (IGM) to the CGM pl us (ii) 176 the interconnections linking these bidding zones with bidding zones that do not contribute an 177 IGM to the CGM (i.e., are not part of the CGM Area). Note that in the context of CGMA the 178 term "optimisation area" (rather than "bidding zone") is used. [1] explains the relevant area 179 concepts. 180

Netted area position:The term "netted area position" (which is used in, for example, the 181 ENTSO-E RG CE Schedule Reporting Process Implementation Guide; version for approval as 182

– Page 9 of 41 –

European Network of


Electricity


VERSION 1.0


of 2016-08-10) corresponds to the term "net position" used in [1]. The net position is defined 183 as the "the netted sum of electricity exports and imports for each market time unit for a 184 bidding zone" (Article 2(5) of Regulation 2015/1222). Implicit in this definition is that a "net 185 position" (as opposed to an "AC net position") always comprises both AC and DC flows into 186 and out of a bidding zone. Note that in the context of the CGMA platform and the CGMA 187 algorithm, the term "optimisation area" (rather than "bidding zone") is used. [1] explains th e 188 relevant area concepts. The "netted area position" (net position) is expressed in the unit MW. 189 Note that a number of additional concepts are derived from the concept of "netted area 190 position"; namely the preliminary "netted area position"; the "netted area AC position" (see 191 below), the absolute maximum netted area position, the absolute minimum netted area 192 position, and the balanced netted area position. 193

Netted area AC position: The term "netted area AC position" (which is used in, for example, 194 the ENTSO-E RG CE Schedule Reporting Process Implementation Guide; version for 195 approval as of 2016-08-10) corresponds to the term "AC net position" used in [1]. The "netted 196 area AC position" is obtained by subtracting from the "netted area position" (net position) for 197 an optimisation area all DC flows into and out of that optimisation area. 198

Feasibility range: A set of two figures expressed in the unit MW that, together with the 199 preliminary netted area position, indicate the range of balanced netted area positio ns (weakly) 200 greater than and (weakly) smaller than the preliminary netted area position that a TSO 201 accepts ex ante for a given scenario. 202

DC flow: Flow on a DC line (i.e., direct current line). Any DC flow – i.e., including both 203 preliminary and balanced DC flows – can be stated in terms of the flow at the exporting end of 204 the DC line or the importing end of the DC line. The difference between the export and the 205 import value corresponds to losses on the DC line. Wherever DC flows are referred to in the 206 present Implementation Guide, both the value at the exporting end and the value at the 207 importing end have to be provided. DC flows are expressed in the unit MW. A DC flow may 208 represent an aggregate of flows on more than one line linking the same optimisation a reas. 209

PPD: Pre-processing data. A set of data that serve as input for the CGMA algorithm. For each 210 scenario and for each optimisation area a separate set of pre-processing data needs to be 211 provided. The following types of data make up the pre-processing data: 212

--preliminary netted area position (mandatory) 213

--feasibility range (mandatory) 214

--preliminary DC flows (mandatory for optimisation areas linked to another optimisation area 215 in a different synchronous area by DC line) 216

--maximum DC flows (export/import) (mandatory for optimisation areas linked to another 217 optimisation area in a different synchronous area by DC line) 218

--absolute minimum and/or maximum netted area position (optional) 219

PPD gate closure time: The PPD gate closure time is that time after which the CGMA 220 platform will, in principle, no longer accept pre-processing data for a given set of scenarios. 221 [1] states the PPD gate closure times. 222

RSC: Regional Security Coordinator. An organisation providing certain services for and /or on 223 behalf of TSOs. RSCs are also involved in the CGMA business processes and, in this context, 224 are referred to as "Alignment Agents" in [1]. 225

Substitute data: If one or more elements of the PPD are missing at PPD gate closure time, 226 the missing elements are replaced by substitute (pre-processing) data. 227

228

– Page 10 of 41 –

European Network of


Electricity


VERSION 1.0


3 The common grid model alignment (CGMA) business processes 229

3.1 Overview 230

The business requirements of CGMA, refer to reference [1], lead to several use cases of data 231 exchange which are described in this chapter. Each use case is supported by one or more 232 document exchange processes, as it is described in later subsections of this chapter. 233

3.2 Overall business context 234

CGMA provides, for all relevant target time-horizons, a set of balanced netted area positions 235 and balanced DC flows which are consistent for the entire CGMA area. It does so by applying 236 the CGMA algorithm to the pre-processing data (CGMA input data). 237

For each scenario and for each optimisation area a separate set of pre -processing data needs 238 to be provided. The following types of data make up the pre-processing data: 239

preliminary netted area position (mandatory) 240

feasibility range (mandatory) 241

preliminary DC flows (mandatory for optimisation areas linked to another optimisa tion 242 area in a different synchronous area by DC line) 243

maximum DC flows (export/import) (mandatory for optimisation areas linked to another 244 optimisation area in a different synchronous area by DC line) 245

absolute minimum and/or maximum netted area position (optional) 246

PPD are created by TSOs or by parties acting on behalf of TSOs and are collected by the 247 CGMA platform. There is a gate closure time after which the CGMA platform will, in principle, 248 no longer accept pre-processing data for a given set of scenarios. ("PPD gate closure time"). 249

The set of PPD is complete when PPD are available for all optimisation areas (i.e., the entire 250 CGMA area). The CGMA platform may request substitute data from the Pan European 251 Verification Function (PEVF) if PPD are missing after PPD gate closure time. Substitute data 252 then serve to complete the set of PPD. 253

The CGMA platform calculates the CGMA results, which consist of a set of 254

balanced netted area positions; 255

balanced netted area AC positions; 256

indicative AC flows per electrical border; 257

balanced DC flows with losses and without losses. 258

The CGMA results can be used by a TSO or by a party acting on behalf of a TSO to update an 259 individual grid model. 260

3.3 Use cases 261

Use cases of CGMA data exchange are schematically presented in Figure 1. More detailed 262 descriptions of individual use cases and the actors involved can be found in Table 1 and 263 Table 2. 264

– Page 11 of 41 –

European Network of


Electricity


VERSION 1.0


265

Figure 1 – Use cases 266

Table 1 gives a list of actors involved in CGMA data exchange. 267

Table 1 – Actor labels and descriptions 268

Actor label Actor description

Transmission system operator A TSO, or any other actor on behalf of a TSO, who is responsible for providing pre-processing data of a particular optimisation area.

CGMA platform The Common Grid Model Alignment platform is responsible for collecting and validating pre-processing data. It executes the CGMA algorithm and provides the results. It maintains input and output data of algorithm runs.

PEVF platform The Pan European Verification Function platform holds matched schedules of exchanges between areas. It may provide netted area positions and DC flows, which serve as substitute data for missing CGMA PPD.

Information receiver Any actor, e. g. a TSO or RSC, who wants to use CGMA results.

269

Table 2 gives a list of use cases for CGMA data exchange. 270

Table 2 – CGMA data exchange 271

Use case label Actors involved

Action description and assertions

Submitting

(with send, ack)

TSO,

CGMA platform

A TSO or RSC submits a complete set of pre-processing data (PPD) for a particular optimisation area.

The CGMA platform checks submitted PPD. It fully accepts or rejects a set of PPD.

The action shall be executed only before PPD gate closure time.

– Page 12 of 41 –

European Network of


Electricity


VERSION 1.0


Use case label Actors involved

Action description and assertions

Send output TSO,

CGMA platform

The CGMA platform provides the TSO with a detailed set of its PPD originally transmitted to the CGMA platform, substituted / modified PPD (if applicable), and CGMA results.

The action shall be executed only after the CGMA algorithm run successfully terminated with final results for the target time horizon.

Substitute data CGMA platform,

PEVF platform

The CGMA platform requests netted area positions and DC flows of a particular optimisation area.

The action may be executed only after PPD gate closure time.

Request results CGMA platform,

Information receiver

An information receiver, e. g. a TSO or RSC, requests CGMA results of any particular optimisation area within the entire CGMA area.

The action shall be executed only after the CGMA algorithm run successfully terminated with final results for the target time horizon..

272

3.4 Document exchange processes 273

Overview 274

The use cases are supported by five document exchange processes : 275

Submit pre-processing data 276

Send escalation notification 277

Send input data and CGMA results 278

Request substitute data 279

Request CGMA results 280

Figure 2 shows a sequence diagram of the three document exchange processes 3.4.2 Submit 281 pre-processing data, 3.4.3 Send escalation notification, and 3.4.4 Send input data and CGMA 282 results . 283

284

– Page 13 of 41 –

European Network of


Electricity


VERSION 1.0


285

Figure 2 – Sequence diagram for submission 286

Submit pre-processing data 287

Before PPD gate closure time, a TSO should initiate document exchange by submitting PPD 288 to the CGMA platform. The platform acknowledges the receipt of a document. If PPD 289 contained in the submitted document were rejected by the platform, it sends a negative 290 acknowledgement to the TSO, which gives a list of rejected PPD and reasons for rejection. 291

This process may be executed more than once. 292

A complete set of PPD consists of the time series listed in Table 3. 293

Table 3 – Time series of pre-processing data 294

Label Description BusinessType

Preliminary netted area position

A TSO's best forecast of the netted area position for an optimisation area. The feasibility range of adjustments must also be given and is part of the PPD. However, it is not transmitted as a separate business type.

Mandatory.

B65

Minimum value of netted area position

That value which a balanced netted area position must not fall below for a given optimisation area.

Optional.

B69

Maximum value of netted area position

That value which a balanced netted area position must not exceed for a given optimisation area.

Optional.

B70

Preliminary DC flow with losses

A TSO's best forecast of the DC flows with losses for a given DC line.

Mandatory for each given DC line.

B67

Preliminary DC flow without losses

A TSO's best forecast of the DC flows without losses for a given DC line.


B68

– Page 14 of 41 –

European Network of


Electricity


VERSION 1.0



Minimum value of DC flow

That value which a balanced DC flow must not fall below for a given DC line.

Optional.

B72

Maximum value of DC flow

That value which a balanced DC flow must not exceed for a given DC line.


B71

295

Send escalation notification 296

After PPD gate closure time, the CGMA platform sends notification to a TSO if PPD are 297 missing, which is relevant for the TSO's optimisation area. 298

Send input data and CGMA results 299

After the CGMA platform has successfully terminated a CGMA run with final results for the 300 target time horizon, it sends to the TSO the CGMA algorithm input and CGMA results which 301 are relevant for the TSO's optimisation area. In case of any modification of PPD provided by a 302 TSO (by CGMA platform and/or RSC) the document will contain both the original input data 303 and the modified input data reporting the changes using the marketObjectStatus entity. 304

The time series of input data and CGMA results are listed in Table 4 and Table 5. 305

Table 4 – Time series of input data 306


Preliminary netted area position

The netted area position of an optimisation area used as input to the CGMA algorithm. It may be substituted with values from PEVF (if applicable for the target time horizon) or modified by a RSC.

A feasibility range of adjustments must also be given. However, it is not transmitted as a separate business type. It may be modified by a RSC or CGMA platform.

Mandatory. Repeated occurrence in case of modifications.

B65

Minimum value of netted area position

The minimum netted area position of an optimisation area used as input to the CGMA algorithm. It may be modified by a RSC or CGMA platform.

Optional. Repeated occurrence in case of modifications.

B69

Maximum value of netted area position

The maximum netted area position of an optimisation area used as input to the CGMA algorithm. It may be modified by a RSC or CGMA platform.


B70

Preliminary DC flow with losses

A DC flow with losses for a given DC line used as input to the CGMA algorithm. It may be substituted with values from PEVF (only D-2) or modified by a RSC or CGMA platform.

Mandatory for each given DC line. Repeated occurrence in case of modifications.

B67

Preliminary DC flow without losses

A DC flow without losses for a given DC line used as input to the CGMA algorithm. It may be substituted with values from PEVF (only D-2) or modified by a RSC or CGMA platform.


B68

Minimum value of DC flow

A minimum DC flow with losses for a given DC line used as input to the CGMA algorithm. It may be modified by a RSC or CGMA platform.


B72

Maximum value of DC flow

A maximum DC flow with losses for a given DC line used as input to the CGMA algorithm. It may be modified by a RSC or CGMA platform.


B71

307

– Page 15 of 41 –

European Network of


Electricity


VERSION 1.0


Table 5 – Time series of CGMA results 308


Balanced netted area position

The balanced netted area position of an optimisation area. A balanced netted area position is characterised by the fact that the sum of all netted area positions of the entire CGMA area is zero.

Mandatory.

B65

Balanced netted area AC position

The balanced netted area AC position of an optimisation area is obtained by subtracting from the balanced netted area position all balanced DC flows into and out of that optimisation area.

Mandatory.

B64

Indicative AC flow It is the hypothetical flow on the aggregate of all AC tie lines of an electrical border between two optimisation areas. It results from the adjustments to the preliminary netted area positions of all optimisation areas made by the CGMA algorithm. Indicat ive AC flows are an artefact of the CGMA algorithm, and do not correspond to physical flows.

Mandatory.

B73

Balanced DC flow with losses

The flow at the importing end of the DC line.

Balanced flows on DC lines have the following properties:

(i) the sum of all balanced netted area positions of the entire CGMA area is zero;

(ii) the flow at the exporting end of each DC line is consistent with the flow at the importing end of the DC line corrected for losses on the DC line.


B67

Balanced DC flow without losses

The flow at the exporting end of the DC line.





B68

309

Request substitute data 310

Figure 3 shows the sequence diagram. 311

312

Figure 3 – Sequence diagram for request substitute data 313

– Page 16 of 41 –

European Network of


Electricity


VERSION 1.0


The process may only be executed after PPD gate closure time. 314

Document exchange is initiated by the CGMA platform requesting data from PEVF platform. 315 PEVF platform replies by sending netted area position and DC flows of the requested area, if 316 these data are available. If these data are not available, PEVF platform replies by sending a 317 Acknowledgement_MarketDocument with ReasonCode B08 (Data not yet available) . 318

The time series of substitute data are listed in Table 6. 319

Table 6 – Time series of substitute data 320


Netted area position

The netted area position for an optimisation area.

Mandatory.

B65

Aggregated netted external schedule

The DC flow for a given DC line.


B63

321

Request CGMA results 322

Figure 4 shows a sequence diagram. 323

324

Figure 4 – Sequence diagram for request CGMA results 325

The process may only be executed after the CGMA algorithm run successfully terminated with 326 status final. 327

Document exchange is initiated by the Information receiver requesting data from CGMA 328 platform. CGMA platform replies by sending CGMA results, if these data are available. In any 329 other case, CGMA platform replies a Acknowledgement_MarketDocument with problem 330 details. 331

CGMA results consist of the time series listed below in the table. 332

333

Table 7 – Time series of CGMA results 334


– Page 17 of 41 –

European Network of


Electricity


VERSION 1.0


335

Balanced netted area position

The netted area position of an optimisation area. A balanced netted area position is characterised by the fact that the sum of all netted area positions of the entire CGMA area is zero.

Mandatory.

B65

Balanced netted area AC position

The balanced netted area AC position of an optimisation area is obtained by subtracting from the balanced netted area position all balanced DC flows into and out of that optimisation area.

Mandatory.

B64

Indicative AC flow It is the hypothetical flow on the aggregate of all AC tie lines of an electrical border between two optimisation areas. It results from the adjustments to the preliminary netted area positions of all optimisation areas made by the CGMA algorithm. Indicative AC flows are an artefact of the CGMA algorithm, and do not correspond to physical flows.

Mandatory.

B73

Balanced DC flow with losses

The flow at the importing end of a given DC line.





B67

Balanced DC flow without losses

The flow at the exporting end of the DC line.





B68

– Page 18 of 41 –

European Network of


Electricity


VERSION 1.0


4 General rules for document exchange 336

4.1 General rules 337

The document exchange processes of CGMA described in the previous chapter require 338 sending and receiving various EDI documents. The EDI documents to be used are 339

ReportingInformation_MarketDocument; 340

Acknowledgement_MarketDocument IEC62325-451-1, refer to reference [2]; 341

ProblemStatement_MarketDocument IEC62325-451-5, refer to reference [3]; 342

StatusRequest_MarketDocument IEC62325-451-5, refer to reference [4]. 343

These EDI documents shall be used to carry out the communication tasks 344

submit - The document contains data to be processed by the receiver. 345

get - The document specifies a request for data to be provided by the receiver. 346

reply - It is the reaction to receiving a submit or get document. 347

send - The document contains data which may be processed by the receiver. 348

Table 8 gives an overview, which EDI document shall be used to carry out the communication 349 tasks of document exchange processes (DEP). Note that dependency tables of using 350 ReportingInformation_MarketDocument are provided in chapter 5 of this document. The 351 abbreviations used in the table (e.g., RID) are explained below the table. 352

Table 8 – List of documents for CGMA process exchanges 353

DEP chapter

DEP label send/submit/get document

reply document

reply conditions

3.4.2 Submit pre-processing data

RID EAD RID fully accepted.

Syntax error

or fully rejected due to semantic error in PPD

or fully rejected due to closed PPD submission gate.

3.4.3 Send escalation notification

EPSD none

3.4.4 Send input data and CGMA results

RID none

3.4.5 Request substitute data

ESR RID ESR fully accepted

and requested data is available.

EAD Syntax error

or semantic error in ESR header

or error in request attributes.

EAD Requested data not available.

3.4.6 Request CGMA results

ESR RID ESR fully accepted

and requested data available.

EAD Syntax error

or semantic error in ESR header

or error in request attributes .

EAD Requested data not available.

Note: RID - ReportingInformation_MarketDocument; EAD - Acknowledgement_MarketDocument; EPSD - 354 ProblemStatement_MarketDocument; ESR - StatusRequest_MarketDocument 355

– Page 19 of 41 –

European Network of


Electricity


VERSION 1.0


4.2 Notes about using StatusRequest_MarketDocument in CGMA document exchange 356

The header of StatusRequest_MarketDocument shall contain the information listed in Table 9. 357

Table 9 – StatusRequest_MarketDocument header values 358

Attribute Value

mRID Identification of the request

type B20: Status request for a reporting information market document

sender_MarketParticipant.mRID The identification of the sender.

sender_MarketParticipant.marketRole.type The role of the sender.

receiver_MarketParticipant.mRID The identification of the receiver.

receiver_MarketParticipant.marketRole.type The role of the receiver.

A39: Data provider

createdDateTime UTC time.

359

The body of StatusRequest_MarketDocument shall contain a list of attribute -value pairs. 360 Allowed attributes and their dependencies are listed in Table 10. 361

Table 10 – StatusRequest_MarketDocument AttributeInstanceComponent values 362

attribute values dependencies description

type B19: Reporting information market document.

Mandatory.

Type of the reply document.

domain.mRID EIC of optimisation area.

Mandatory.

Reply document shall contain data relevant for that optimisation area.

process.processType A33: Year ahead.

A32: Month ahead.

A31: Week ahead.

A45: Two days ahead.

Mandatory.

time_Period.timeInterval UTC time.

Mandatory.

Start time of CGMA target time interval.

businessType B63: Aggregated netted external schedule.

To be used for requesting substitute data.

Data expected in the reply document.

There must be one or more occurrences of this attribute.

B65: Netted area position.

B67: DC flow with losses.

B68: DC flow without losses.

B73: Indicative AC flow.

To be used for requesting CGMA results.

363

– Page 20 of 41 –

European Network of


Electricity


VERSION 1.0


4.3 Notes about using ProblemStatement_MarketDocument as an escalation 364 notification 365

The header of ProblemStatement_MarketDocument shall contain the information listed in 366 Table 11. 367

Table 11 – ProblemStatement_MarketDocument header values 368

Attribute Value

mRID Unique identification of the document.

revisionNumber Version of the document.

type A34: Escalation document



A39: Data provider. CGMA platform



A04: System operator

A44: RSC


period.timeInterval CGMA target time horizon covered by the document

expected_MarketDocument.type B19: ReportingInformation_MarketDocument

expected_MarketDocument.createdDateTime UTC time. The gate closure time.

expected_MarketDocument.process.processType A33: Year ahead.

A32: Month ahead.

A31: Week ahead.


domain.mRID The optimisation area of concern.

Reason.code A02: Document fully rejected. No valid PPD document was received.

A91: Expected document not received.

B01: Incomplete document.

A78: Sender identification and/or role invalid.

A79: Process type invalid.

A80: Domain invalid.

B08: Data not yet available.

369

– Page 21 of 41 –

European Network of


Electricity


VERSION 1.0


5 Using the ReportingInformation_MarketDocument in CGMA 370

5.1 Overview 371

According to Table 8, the ReportingInformation_MarketDocument is used in four different 372 processes of CGMA document exchange. For each process, specific rules for using 373 ReportingInformation_MarketDocument, so called dependencies, are defined in subsections 374 of this chapter. 375

5.2 Rules governing ReportingInformation_MarketDocument to submit pre-376 processing data 377

Table 12 gives the rules governing attributes and elements of 378 ReportingInformation_MarketDocument header. 379

Table 12 – ReportingInformation_MarketDocument header 380

Re

po

rtin

gIn

form

ati

on

_M

ark

etD

ocu

me

nt

Attribute Description and dependencies

mRID Document identification.




A32: Month ahead.

A31: Week ahead.





A44: RSC



A39: Data provider. CGMA platform.


time_Period.timeInterval CGMA target time horizon covered by the document.


dataset_MarketDocument.mRID Not used.

dataset_MarketDocument.revisionNumber Not used.

docStatus Not used.

referenced_DateAndOrTime.date Not used.

referenced_DateAndOrTime.time Not used.

Reason Not used.

381

The document should contain one or more elements of TimeSeries class. 382

383

– Page 22 of 41 –

European Network of


Electricity


VERSION 1.0


Table 13 gives the rules governing the attributes and sub-elements of 384 ReportingInformation_MarketDocument.TimeSeries elements. 385

Table 13 – ReportingInformation_MarketDocument.TimeSeries elements 386

Tim

eS

eri

es

Tim

eS

eri

es


Netted area position or maximum and

minimum netted area position values

DC flow or maximum and minimum DC flow

values

mRID Identification of the time series.

B65: Netted area position. The net AC and DC position of the optimisation area.

B67: DC flow with losses

B68: DC flow without losses

B70: Maximum netted area position.

B69: Minimum netted area position.

B71: Maximum DC flow.

B72: Minimum DC flow.

product 8716867000016: Active Power

import export import export

in_Domain.mRID Identification of optimi-sation area.

Mandatory.

Not used. Identification of optimi-sation area.

Mandatory.

Identification of the im-porting area.

Mandatory.

out_Domain.mRID Not used. Identification of optimi-sation area.

Mandatory.

Identification of the ex-porting area.

Mandatory.

Identification of optimi-sation area.

Mandatory.

connectingLine_RegisteredResource. mRID

Not used. Identification of the DC link.

Mandatory.

measurement_Unit.name MAW: MW

curveType A02: Point.

marketObjectStatus.status Not used.

Reason Not used.

.Pe

rio

d

resolution Resolution used in the Point class.

timeInterval Time interval covered by elements of Point class.

.Pe

rio

d.P

oin

t

position Position in the time series.

Mandatory.

quantity Value of the netted area position, flow or minimum / maximum (no signed value).

Mandatory.

posFR_Quantity.quantity Positive feasibility range (no signed value).

Mandatory for BusinessType B65. Not used otherwise.

Not used.

negFR_Quantity.quantity Negative feasibility range (signed value).


Not used.

Reason Not used.

387

– Page 23 of 41 –

European Network of


Electricity


VERSION 1.0


5.3 Rules governing ReportingInformation_MarketDocument to reply substitute data 388



Re

po

rtin

gIn

form

ati

on

_M

ark

etD

ocu

me

nt





process.processType A01: Day ahead



A39: Data provider. PEVF platform.



A39: Data provider. CGMA platform.






docStatus A01 = Intermediate

A02 = Final



Reason B08 = Data not yet available.

392




Tim

eS

eri

es

Tim

eS

eri

es


Netted area position DC flow


businessType B65: Netted area position. The net AC and DC position of the optimisation area.

B63 = Aggregated netted external schedule

product 8716867000016: Active Power


in_Domain.mRID Identification of the optimi-sation area.

Mandatory.

Not used. Identification of the optimi-sation area.

Mandatory.


Mandatory.

– Page 24 of 41 –

European Network of


Electricity


VERSION 1.0


Tim

eS

eri

es

Tim

eS

eri

es Attribute Description and dependencies

Netted area position DC flow

out_Domain.mRID Not used. Identification of the optimi-sation area.

Mandatory.


Mandatory.

Identification of the optimi-sation area.

Mandatory.

connectingLine_RegisteredResource

.mRID


Mandatory.



marketObjectStatus.status Not used.

Reason A28 = Counterpart time series missing

A29 = Counterpart time series quantity differences

A63 = Time Series modified

A88 = Time series matched

.Pe

rio

d



.Pe

rio

d.P

oin

t


Mandatory.

quantity Value of the netted area position or flow (no signed value).

Mandatory.

posFR_Quantity.quantity Not used. Not used.

negFR_Quantity.quantity Not used. Not used.

Reason A43 = Quantity increased

A44 = Quantity decreased

397

5.4 Rules governing ReportingInformation_MarketDocument to send input data and 398 CGMA results 399



Re

po

rtin

gIn

form

ati

on

_M

ark

etD

ocu

me

nt






A32: Month ahead.

A31: Week ahead.








A44: RSC

– Page 25 of 41 –

European Network of


Electricity


VERSION 1.0


Re

p

ort

in

gIn

for

ma

ti

on

_M

ar

ke

t

Do

c

um

en

t Attribute Description and dependencies






docStatus Not used.



Reason Not used.

403




Tim

eS

eri

es

Tim

eS

eri

es


netted (AC) area position or maximum and minimum netted area position values


values or indicative AC flow


businessType B64: Netted AC area position.


B69: Minimum netted area position.

B70: Maximum netted area position.



B71: Maximum DC flow.

B72: Minimum DC flow.


product 8716867000016: Active Power.



Mandatory.

Not used.


Mandatory.


Mandatory.

out_Domain.mRID Not used.


Mandatory.


Mandatory.


Mandatory.


.mRID


Mandatory for B67 and B68: DC flow with losses and DC flow without losses,

Not used for indicative AC flow (B73).



– Page 26 of 41 –

European Network of


Electricity


VERSION 1.0


Tim

eS

eri

es

Tim

eS

eri

es


netted (AC) area position or maximum and minimum netted area position values


values or indicative AC flow

marketObjectStatus.status Coded description of a time series. To be used for providing information about life cycle status.

A29: Submitted. The object was submitted to be processed by CGMA platform.

A30: Substituted. CGMA platform used data originating from PEVF platform.

A31: Modified. The values were modified by RSC or CGMA platform.

A32: Result. The object is the final result of CGMA algorithm.

Mandatory.

Reason Not used.

.Pe

rio

d



.Pe

rio

d.P

oin

t


Mandatory.

quantity Value of the netted (AC) area position, flow or minimum / maximum (no signed value).

Mandatory.

posFR_Quantity.quantity Positive feasibility range (no signed value).


Not used.

negFR_Quantity.quantity Negative feasibility range (signed value).


Not used.

Reason.code May optionally be provided.

A63 = Time Series modified.

Reason.text Optionally used to provide additional information about the reason for modification in case of marketObjectStatus.status

A30: Substituted, or A31: Modified.

408

– Page 27 of 41 –

European Network of


Electricity


VERSION 1.0


5.5 Rules governing ReportingInformation_MarketDocument to reply CGMA results 409



Re

po

rtin

gIn

form

ati

on

_M

ark

etD

ocu

me

nt






A32: Month ahead.

A31: Week ahead.








A44: RSC






docStatus Not used.



Reason Not used.

413




Tim

eS

eri

es

Tim

eS

eri

es


Netted (AC) area position

DC flow or indicative AC flow


businessType B64: Netted AC area position.





product 8716867000016: Active Power.

– Page 28 of 41 –

European Network of


Electricity


VERSION 1.0


Tim

eS

eri

es

Tim

eS

eri

es


Netted (AC) area position

DC flow or indicative AC flow



Mandatory.

Not used. Identification of the optimi-sation area.

Mandatory.


Mandatory.

out_Domain.mRID Not used. Identification of the optimi-sation area.

Mandatory.


Mandatory.


Mandatory.


.mRID


Mandatory for B67: DC flow with losses and B68: DC flow without losses

Not used for B73: Indicative AC flow.

measurement_Unit.name MAW: MW.


marketObjectStatus.status A32: Result. The object is the final result of CGMA algorithm.

Mandatory.

Reason Not used.

.Pe

rio

d



.Pe

rio

d.P

oin

t


Mandatory.

quantity Value of the netted (AC) area position or flow (no signed value).

Mandatory.

posFR_Quantity.quantity Not used.

negFR_Quantity.quantity Not used.

Reason Not used.

418

5.6 Additional rules governing the use of TimeSeries 419

Netted AC area position and netted area position of an optimisation area are always provided 420 through the use of two time series. 421

One time series for import into the optimisation area A with in_Domain.mRID = 422 “mRID_A”, out_Domain.mRID = ”” (empty). 423

One time series for export from the optimisation area A with in_Domain.mRID = ”” 424 (empty), out_Domain.mRID = ”mRID_A”. 425

These two time series shall have the same Period.resolution and the same 426 Period.timeInterval. For a given Point.position, the Point.quantity of one time series 427 must be zero, whereas the Point.quantity of the other time series may have a value 428 larger than zero (pair of netted values). Point.quantity of both time series must be zero 429 when the netted area position of the optimisation area is zero for the given 430 Point.position. 431

– Page 29 of 41 –

European Network of


Electricity


VERSION 1.0


A feasibility range (Point.posFR_Quantity.quantity and Point.negFR_Quantity.quantity) 432 shall be provided for every point.quantity. If PPD contain more than one time series of 433 BusinessType A65 (import and export values in one document), the TSO has to make 434 sure that the feasibility ranges for a given Point have the same values in both time 435 series. Otherwise the PPD will be rejected due to inconsistency. This applies to all 436 kinds of net positions (zero, import, export). 437

DC flows with and without losses as well as indicative AC flows of an optimisation area A 438 towards another area B are always provided through the use of two time series. One time 439 series for import into the optimisation area A with in_Domain.mRID = “mRID_A”, 440 out_Domain.mRID = ”mRID_B”. 441

One time series for export from the optimisation area A with in_Domain.mRID 442 = ”mRID_B”, out_Domain.mRID = ”mRID_A”. 443

These two time series shall have the same Period.resolution and the same 444 Period.timeInterval. For a given Point.position, the Point.quantity of one time series 445 must be zero, whereas the Point.quantity of the other time series may have a value 446 larger than zero (pair of netted values).Point.quantity of both timeseries must be zero 447 when there is no flow between the two areas for the given target time interval. 448

– Page 30 of 41 –

European Network of


Electricity


VERSION 1.0


6 ReportingInformation_MarketDocument 449

6.1 Reporting information contextual model 450

Overview of the model 451

Figure 5 shows the model. 452

453

Figure 5 - Reporting information contextual model 454

IsBasedOn relationships from the European style market profile 455

Table 20 shows the traceability dependency of the classes used in this package towards the 456 upper level. 457

Table 20 - IsBasedOn dependency 458

Name Complete IsBasedOn Path

ConnectingLine_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Dataset_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument

Domain TC57CIM::IEC62325::MarketManagement::Domain

MarketObjectStatus TC57CIM::IEC62325::MarketManagement::MarketObjectStatus

MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant

MarketRole TC57CIM::IEC62325::MarketCommon::MarketRole

– Page 31 of 41 –

European Network of


Electricity


VERSION 1.0



Measure_Unit TC57CIM::IEC62325::MarketManagement::Unit

Point TC57CIM::IEC62325::MarketManagement::Point

Process TC57CIM::IEC62325::MarketManagement::Process

Quantity TC57CIM::IEC62325::MarketManagement::Quantity

Reason TC57CIM::IEC62325::MarketManagement::Reason

Referenced_DateAndOrTime TC57CIM::IEC62325::MarketManagement::DateAndOrTime

ReportingInformation_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument

Series_Period TC57CIM::IEC62325::MarketManagement::Period

Time_Period TC57CIM::IEC62325::MarketManagement::Period

TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

459

– Page 32 of 41 –

European Network of


Electricity


VERSION 1.0


6.2 Reporting information assembly model 460

Overview of the model 461

Figure 6 shows the model. 462

463

Figure 6 - Reporting information assembly model 464

IsBasedOn relationships from the European style market profile 465

Table 21 shows the traceability dependency of the classes used in this package towards the 466 upper level. 467

– Page 33 of 41 –

European Network of


Electricity


VERSION 1.0


Table 21 - IsBasedOn dependency 468


Point TC57CIM::IEC62325::MarketManagement::Point

Reason TC57CIM::IEC62325::MarketManagement::Reason

ReportingInformation_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument

Series_Period TC57CIM::IEC62325::MarketManagement::Period

TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

469

Detailed Reporting information assembly model 470

6.2.3.1 ReportingInformation_MarketDocument root class 471

This document provides either: 472

all the information relating to a status request made by an interested party concerning 473 aggregated netted external schedules, aggregated netted external market schedules, 474 aggregated netted external TSO schedules, compensation program schedules, netted 475 area position schedules and netted area AC position schedules. 476

the net position for an area (scheduling area, bidding zone, NEMO trading hub, control 477 area, ...). 478

An electronic document containing the information necessary to satisfy the requirements of a 479 given business process. 480

Table 22 shows all attributes of ReportingInformation_MarketDocument. 481

Table 22 - Attributes of Reporting information assembly 482 model::ReportingInformation_MarketDocument 483

Order mult. Attribute name / Attribute type Description

0 [1..1] mRID

ID_String

The unique identification of the document being exchanged within a business process flow.

1 [1..1] revisionNumber

ESMPVersion_String

The identification of the version that distinguishes one evolution of a document from another.

2 [1..1] type

MessageKind_String

The coded type of a document. The document type describes the principal characteristic of the document.

3 [1..1] process.processType

ProcessKind_String

The identification of the nature of process that the document addresses. --- The Process dealt within the document.

4 [1..1] sender_MarketParticipant.mRID

PartyID_String

The identification of a party in the energy market. --- The sender of the document.

5 [1..1] sender_MarketParticipant.marketRole.type

MarketRoleKind_String

The identification of the role played by a market player. --- The sender of the document. --- The role associated with a MarketParticipant.

6 [1..1] receiver_MarketParticipant.mRID

PartyID_String

The identification of a party in the energy market. --- The recipient of the document.

7 [1..1] receiver_MarketParticipant.marketRole.type

MarketRoleKind_String

The identification of the role played by a market player. --- The recipient of the document. --- The role associated with a MarketParticipant.

8 [1..1] createdDateTime

ESMP_DateTime

The date and time of the creation of the document.

– Page 34 of 41 –

European Network of


Electricity


VERSION 1.0



9 [1..1] time_Period.timeInterval

ESMP_DateTimeInterval

The start and end date and time for a given interval. --- This information provides the start and end date and time of the period covered by the document.

10 [0..1] domain.mRID

AreaID_String

The unique identification of the domain. --- The identification of the domain that is covered in the reporting information market document.

11 [0..1] dataset_MarketDocument.mRID

ID_String

The identification of an individually predefined dataset in a data base system (e. g. Verification Platform). --- The identification of information in the reporting information market document that is related to a predefined dataset. In the CGMA process, the identification of the received document containing errors. Both the mRID and the revisionNumber of the received document are provided.

12 [0..1] dataset_MarketDocument.revisionNumber

ESMPVersion_String

The identification of the version that distinguishes one evolution of a document from another. --- The identification of information in the reporting information market document that is related to a predefined dataset. In the CGMA process, the identification of the received document containing errors. Both the mRID and the revisionNumber of the received document are provided.

13 [0..1] docStatus

Action_Status

The identification of the condition or position of the document with regard to its standing. A document may be intermediate or final.

14 [0..1] referenced_DateAndOrTime.date

Date

The date as "YYYY-MM-DD", which conforms with ISO 8601. --- The reference date and time for which the reporting information market document information is to be provided.

15 [0..1] referenced_DateAndOrTime.time

Time

The time as "hh:mm:ss.sssZ", which conforms with ISO 8601. --- The reference date and time for which the reporting information market document information is to be provided.

484

Table 23 shows all association ends of ReportingInformation_MarketDocument with other 485 classes. 486

Table 23 - Association ends of Reporting information assembly 487 model::ReportingInformation_MarketDocument with other classes 488

Order mult. Class name / Role

Description

16 [0..*] TimeSeries

TimeSeries

The time series that is associated with an electronic document. Association Based On: Reporting information contextual model::ReportingInformation_MarketDocument.[] ----- Reporting information contextual model::TimeSeries.TimeSeries[0..*]

17 [0..*] Reason

Reason

The Reason associated with the electronic document header providing different motivations for the creation of the document. Association Based On: Reporting information contextual model::ReportingInformation_MarketDocument.[] ----- Reporting information contextual model::Reason.Reason[0..*]

489

6.2.3.2 Point 490

The identification of the values being addressed within a specific interval of time. 491

– Page 35 of 41 –

European Network of


Electricity


VERSION 1.0


Table 24 shows all attributes of Point. 492

Table 24 - Attributes of Reporting information assembly model::Point 493

Order mult. Attribute name / Attribute type

Description

0 [1..1] position

Position_Integer

A sequential value representing the relative position within a given time interval.

1 [1..1] quantity

Decimal

The principal quantity identified for a point. The quantity of the product scheduled for the position within the time interval.

2 [0..1] posFR_Quantity.quantity

Decimal

The quantity value. The association role provides the information about what is expressed. --- The positive feasibility range to be used for the alignment process of the netted area position provided in the quantity attribute of the class Point. The Quantity information associated with a given Point.

3 [0..1] negFR_Quantity.quantity

Decimal

The quantity value. The association role provides the information about what is expressed. --- The negative feasibility range to be used for the alignment process of the netted area position provided in the quantity attribute of the class Point. This value shall be either zero or a negative value. The Quantity information associated with a given Point.

494

Table 25 shows all association ends of Point with other classes. 495

Table 25 - Association ends of Reporting information assembly model::Point with other 496 classes 497

Order mult. Class name / Role Description

4 [0..*] Reason

Reason

The Reason information associated with a Point providing motivation information. Association Based On: Reporting information contextual model::Point.[] ----- Reporting information contextual model::Reason.Reason[0..*]

498

6.2.3.3 Reason 499

The motivation of an act. 500

Table 26 shows all attributes of Reason. 501

Table 26 - Attributes of Reporting information assembly model: Reason 502


0 [1..1] code

ReasonCode_String

The motivation of an act in coded form.

1 [0..1] text

ReasonText_String

The textual explanation corresponding to the reason code.

503

6.2.3.4 Series_Period 504

The identification of the period of time corresponding to a given time interval and resolution. 505

Table 27 shows all attributes of Series_Period. 506

– Page 36 of 41 –

European Network of


Electricity


VERSION 1.0


Table 27 - Attributes of Reporting information assembly model: Series_Period 507

Order mult. Attribute name / Attribute type

Description

0 [1..1] resolution

Duration

The definition of the number of units of time that compose an individual step within a period.

1 [1..1] timeInterval

ESMP_DateTimeInterval

The start and end time of the period.

508

Table 28 shows all association ends of Series_Period with other classes. 509

Table 28 - Association ends of Reporting information assembly model: Series_Period 510 with other classes 511

Order mult. Class name / Role Description

2 [1..*] Point

Point

The Point information associated with a given Series_Period.within a TimeSeries. Association Based On: Reporting information contextual model::Series_Period.[] ----- Reporting information contextual model::Point.Point[1..*]

512

6.2.3.5 TimeSeries 513

A set of time-ordered quantities being exchanged in relation to a product. 514

In the ESMP profile, the TimeSeries provides not only time-ordered quantities but also time-515 ordered information. 516

Table 29 shows all attributes of TimeSeries. 517

Table 29 - Attributes of Reporting information assembly model: TimeSeries 518


0 [1..1] mRID

ID_String

A unique identification of the time series.

1 [1..1] businessType

BusinessKind_String

The identification of the nature of the time series.

2 [1..1] product

EnergyProductKind_String

The identification of the nature of an energy product such as power, energy, reactive power, etc.

3 [0..1] in_Domain.mRID

AreaID_String

The unique identification of the domain. --- The area where the product is being delivered.

4 [0..1] out_Domain.mRID

AreaID_String

The unique identification of the domain. --- The area where the product is being extracted.

5 [0..1] connectingLine_RegisteredResource.mRID

ResourceID_String

The unique identification of a resource. --- The identification of the DC link(s) or controllable AC link(s) between areas.

6 [1..1] measurement_Unit.name

MeasurementUnitKind_String

The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit of measure associated with the quantity in the Point class or in the Quantity class.

7 [1..1] curveType

CurveType_String

The identification of the coded representation of the type of curve being described.

– Page 37 of 41 –

European Network of


Electricity


VERSION 1.0



8 [0..1] marketObjectStatus.status

Status_String

The coded condition or position of an object with regard to its standing. --- The status of an object associated with a TimeSeries. For CGMA process, it provides the status of the time series, e.g. PPDtime series, result time series, substituted time series.

519

Table 30 shows all association ends of TimeSeries with other classes. 520

Table 30 - Association ends of Reporting information assembly model: TimeSeries with 521 other classes 522

Order mult. Class name / Role

Description

9 [1..*] Series_Period

Period

The time interval and resolution for a period associated with a TimeSeries. Association Based On: Reporting information contextual model::TimeSeries.[] ----- Reporting information contextual model::Series_Period.Period[1..*]

10 [0..*] Reason

Reason

The reason information associated with a TimeSeries providing motivation information. Association Based On: Reporting information contextual model::TimeSeries.[] ----- Reporting information contextual model::Reason.Reason[0..*]

523

Datatypes 524

The list of datatypes used for the Reporting information assembly model is as follows: 525

Action_Status compound 526

ESMP_DateTimeInterval compound 527

AreaID_String datatype, codelist CodingSchemeTypeList 528

BusinessKind_String datatype, codelist BusinessTypeList 529

CurveType_String datatype, codelist CurveTypeList 530

EnergyProductKind_String datatype, codelist EnergyProductTypeList 531

ESMP_DateTime datatype 532

ESMPVersion_String datatype 533

ID_String datatype 534

MarketRoleKind_String datatype, codelist RoleTypeList 535

MeasurementUnitKind_String datatype, codelist UnitOfMeasureTypeList 536

MessageKind_String datatype, codelist MessageTypeList 537

PartyID_String datatype, codelist CodingSchemeTypeList 538

Position_Integer datatype 539

ProcessKind_String datatype, codelist ProcessTypeList 540

– Page 38 of 41 –

European Network of


Electricity


VERSION 1.0


ReasonCode_String datatype, codelist ReasonCodeTypeList 541

ReasonText_String datatype 542

ResourceID_String datatype, codelist CodingSchemeTypeList 543

Status_String datatype, codelist StatusTypeList 544

YMDHM_DateTime datatype 545

ReportingInformation_MarketDocument XML schema 546

The XSD file to be used with this implementation guide is 547 urn:iec62325.351:tc57wg16:ReportingInformation_MarketDocument:2;0 548

Figure 7 and Figure 8 provide the structure of the schema. 549

– Page 39 of 41 –

European Network of


Electricity


VERSION 1.0


550

Figure 7 - Reporting information schema structure 1/2 551

– Page 40 of 41 –

European Network of


Electricity


VERSION 1.0


552

Figure 8 - Reporting information schema structure 2/2 553

– Page 41 of 41 –

European Network of


Electricity


VERSION 1.0


554

7 References 555

[1] All TSO's Common Grid Model Alignment Methodology in accordance with Article 25 (3)(c) 556 of the Common Grid Model Methodology 557

[2] Acknowledgement_MarketDocument (EAD) IEC 62325-451-1 558

[3] ProblemStatement_MarketDocument (EPSD) IEC 62325-451-5 559

[4] StatusRequest_MarketDocument (ESR) IEC62325-451-5 560

Documents

ENTSO-E CGMA DATA EXCHANGES IMPLEMENTATION GUIDE