critical network element implementation guide v1r1 · – page 3 of 48 – european network of...

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

2015-11-10 DRAFT DOCUMENT

VERSION 1.1

ENTSO-E CRITICAL NETWORK ELEMENT

IMPLEMENTATION GUIDE

– of 48 –

European Network of Transmission System Operators for Electricity

ENTSO-E Critical Network Element Process IMPLEMENTATION GUIDE VERSION 1.1 - DRAFT


Copyright notice: 2

Copyright © ENTSO-E. All Rights Reserved. 3

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

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

ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIE D, INCLUDING BUT NOT 12 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMA TION HEREIN WILL NOT 13 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF ME RCHANTABILITY OR 14 FITNESS FOR A PARTICULAR PURPOSE. 15

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

NOTE CONCERNING WORDING USED IN THIS DOCUMENT 18

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

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

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

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

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

• MAY: This word, or the adjective “OPTIONAL”, means that an item is truly optional. One 32 vendor may choose to include the item because a particular marketplace requires it or 33 because the vendor feels that it enhances the product while another vendor may omit the 34 same item. An implementation which does not include a particular option MUST be 35 prepared to interoperate with another implementation which does include the option, 36 though perhaps with reduced functionality. In the same vein an implementation which does 37 include a particular option MUST be prepared to interoperate with another implementation 38 which does not include the option (except, of course, for the feature the option provides.). 39

– of 48 –




Revision History 40

Version Release Date Comments

0 0 2015-01-15 Initial release

1 0 2015-09-01 Review by WG EDI and PT CGM

1 1 2015-11-10 Following the maintenance request from EMFIP, change to the UML model to enable “anonymous” publication.

41

– of 48 –




CONTENTS 42

Copyright notice: ..................................................................................................................... 2 43

INTRODUCTION ..................................................................................................................... 6 44

1 Scope .............................................................................................................................. 6 45

2 Normative references ...................................................................................................... 6 46

3 Terms and definitions ...................................................................................................... 6 47

4 The critical network element calculation and publication process ..................................... 9 48

4.1. Overall business context .................................................................................... 9 49

4.2 Critical network elements determination and publication .................................. 10 50

4.3 Flow based domain determination and publication ........................................... 12 51

4.4 Business rules for the critical network element determination process ............. 13 52

4.4.1 General rules .................................................................................. 13 53

4.4.2 Dependencies governing the 54 CriticalNetworkElement_MarketDocument ...................................... 14 55

5 Contextual and assembly models .................................................................................. 29 56

5.1 CriticalNetworkElement contextual model ........................................................ 29 57

5.1.1 Overview of the model .................................................................... 29 58

5.1.2 IsBasedOn relationships from the European style market 59 profile ............................................................................................. 29 60

5.2 CriticalNetworkElement assembly model .......................................................... 31 61

5.2.1 Overview of the model .................................................................... 31 62

5.2.2 IsBasedOn relationships from the European style market 63 profile ............................................................................................. 31 64

5.2.3 Detailed CriticalNetworkElement assembly model ........................... 32 65

5.2.4 Datatypes ....................................................................................... 42 66

5.2.5 CriticalNetworkElement_MarketDocument XML schema ................. 42 67

68

List of figures 69

Figure 1 – Use case of the critical network elements process ............................................... 10 70

Figure 2 – Critical network elements determination and publication ...................................... 12 71

Figure 3 – Flow based domain determination and publication................................................ 13 72

Figure 4 – CriticalNetworkElement contextual model ............................................................. 29 73

Figure 5 – CriticalNetworkElement assembly model .............................................................. 31 74

Figure 6 – CriticalNetworkElement_MarketDocument XML schema structure 1/6 .................. 43 75




Figure 10 – CriticalNetworkElement_MarketDocument XML schema structure 5/6 ................ 47 79

Figure 11 – CriticalNetworkElement_MarketDocument XML schema structure 6/6 ................ 48 80

81

List of tables 82

Table 1 – Flow based Domain dependency ........................................................................... 17 83

Table 2 – Flow based Publication dependency ...................................................................... 19 84

– of 48 –




Table 3 – Flow based Market Impact Publication dependency ............................................... 21 85

Table 4 – NTC Coordinated Determination dependency ........................................................ 23 86

Table 5 – Critical Network Element Publication dependency ................................................. 25 87

Table 6 – Critical Network Element Market Impact Publication dependency .......................... 27 88

Table 1 – IsBasedOn dependency ........................................................................................ 29 89

Table 8 – IsBasedOn dependency ........................................................................................ 32 90

Table 9 – Attributes of CriticalNetworkElement assembly 91 model::CriticalNetworkElement_MarketDocument ................................................................. 32 92

Table 10 – Association ends of CriticalNetworkElement assembly 93 model::CriticalNetworkElement_MarketDocument with other classes .................................... 33 94

Table 11 – Attributes of CriticalNetworkElement assembly model::Analog ............................. 33 95

Table 12 – Association ends of CriticalNetworkElement assembly model::Analog with 96 other classes ........................................................................................................................ 34 97

Table 13 – Attributes of CriticalNetworkElement assembly model::AnalogValue .................... 34 98

Table 14 – Attributes of CriticalNetworkElement assembly 99 model::Constraint_TimeSeries .............................................................................................. 34 100

Table 15 – Association ends of CriticalNetworkElement assembly 101 model::Constraint_TimeSeries with other classes ................................................................. 35 102

Table 16 – Attributes of CriticalNetworkElement assembly 103 model::Monitored_RegisteredResource ................................................................................. 36 104

Table 17 – Association ends of CriticalNetworkElement assembly 105 model::Monitored_RegisteredResource with other classes .................................................... 37 106

Table 18 – Attributes of CriticalNetworkElement assembly 107 model::Outage_RegisteredResource ..................................................................................... 37 108

Table 19 – Attributes of CriticalNetworkElement assembly 109 model::Party_MarketParticipant ............................................................................................ 38 110

Table 20 – Attributes of CriticalNetworkElement assembly model::Point ............................... 38 111

Table 21 – Association ends of CriticalNetworkElement assembly model::Point with 112 other classes ........................................................................................................................ 39 113

Table 22 – Attributes of CriticalNetworkElement assembly model::PTDF_Domain ................. 39 114

Table 23 – Attributes of CriticalNetworkElement assembly model::Reason ............................ 39 115

Table 24 – Attributes of CriticalNetworkElement assembly 116 model::RemedialAction_RegisteredResource ........................................................................ 40 117

Table 25 – Attributes of CriticalNetworkElement assembly model::Series_Period .................. 40 118

Table 26 – Association ends of CriticalNetworkElement assembly 119 model::Series_Period with other classes ............................................................................... 41 120

Table 27 – Attributes of CriticalNetworkElement assembly model::TimeSeries ...................... 41 121

Table 28 – Association ends of CriticalNetworkElement assembly model::TimeSeries 122 with other classes ................................................................................................................. 41 123

124

– of 48 –




INTRODUCTION 125

This document is drafted based on IEC 62325 series. In particular, the IEC 62325-450 126 methodology was applied to develop the conceptual and assembly models. 127

1 Scope 128

The objective of this implementation guide is to make it possible for software vendors to 129 develop an IT application for market players to exchange information relative to critical 130 network elements used for interconnection capacity determination process. 131

The implementation guide is one of the building blocks for using UML (Unified Modelling 132 Language) based techniques in defining processes and messages for interchange between 133 actors in the electrical industry in Europe. 134

2 Normative references 135

The following documents, in whole or in part, are normatively referenced in this document and 136 are indispensable for its application. For dated references, only the edition cited applies. For 137 undated references, the latest edition of the referenced document (including any 138 amendments) applies. 139

IEC TS 61970-2, Energy management system application program interface (EMS-API) – Part 140 2: Glossary 141

IEC 62325-301, Framework for energy market communications – Part 301: Common 142 information model (CIM) extensions for markets 143

IEC 62325-351, Framework for energy market communications – Part 351: CIM European 144 market model exchange profile 145

IEC 62325-450, Framework for energy market communications – Part 450: Profile and context 146 modeling rules 147

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

IEC 62325-451-3, Framework for energy market communications – Part 451-3: ENTSO-E 150 Capacity Allocation and Nomination business process and contextual model for CIM European 151 market 152

3 Terms and definitions 153

3.1 154 constraint situation 155 It is a network configuration, corresponding either to the expected nominal state, or to an 156 hypothetical degraded state where one or several contingencies occur. In both cases, 157 associated remedial actions can be included in the network configuration. 158

159

3.2 160 critical network element 161 A network element either within a bidding zone or between bidding zones taken into account 162 in the capacity calculation process, limiting the amount of power that can be exchanged. 163

Depending on the chosen implementation, there may be only one or several critical network 164 elements which will be monitored in a given constraint situation. 165

3.3 166 final adjusted margin value 167 FAV 168 This is the amount of MW that is manually added or subtracted to the capacity of the critical 169 network element. A negative value for FAV simulates the effect of an additional margin due to 170

– of 48 –




complex remedial actions which cannot be modelled and so calculated in the flow based 171 parameter calculation. A positive value for FAV, as a consequence of the verification phase of 172 the flow based domain, leads to the need to reduce the margin on one or more critical 173 network elements for system security reasons. 174

3.4 175 flow 176 This is the computed physical flow, resulting from a load flow calculation, corresponding to 177 the critical network element in the constraint situation ("N Situation", “N-1 Situation” ...) after 178 the capacity calculation. The flow is expressed in A, %, or MW. 179

3.5 180 flow based remaining available margin 181 RAM 182 This is the remaining available margin (RAM) for one critical network element in a constraint 183 situation. This is the amount of MW or A that is left for the limiting element in a computed 184 constraint situation, i.e. the amount that can be traded or used. 185

3.6 186 flow based study domain 187 This is the area for which the flow based study is carried out. 188

3.7 189 flow reliability margin 190 This is the flow reliability margin for a given critical network element in each considered 191 constraint situation. The amount of MW or A that is reserved for this critical network element 192 and shall not be used for the computed outage situation, in order to secure the power 193 network. 194

3.8 195 long term allocation margin 196 This is the amount of MW that is added to the capacity of the critical network element in order 197 to automatically include the long term allocation domain into the flow based domain. 198

3.9 199 market coupling domain 200 This is the market coupling area or a part of the market coupling area for which the social 201 welfare impact due to the critical network element is computed. 202

3.10 203 monitored registered resource 204 This is the critical network element of the power network in the constraint situation. Some 205 analog measurements are of interest in order to provide information about the limitation and 206 the physical impact on this element in such a constraint situation. 207

3.11 208 outage registered resource 209 This is one of the network elements which are in outage for the studied constraint situation. 210

3.12 211 power transfer distribution factor 212 This is a factor (PTDF) representing the impact of 1 MW variation of the net position of the 213 corresponding bidding zone on the critical network element. 214

3.13 215 PTDF domain 216 This is a bidding zone of the market coupling region which may be impacted by the critical 217 network element. 218

3.14 219 remedial action registered resource 220 This is one of the network element on which remedial action are carried out to improve the 221 constraint situation. Those elements are used to alleviate the constraints induced by the 222

– of 48 –




constraint situation. The remedial actions may be identified as automatic, preventive or 223 curative. The type of the remedial action includes generation, load and/or topology changes. 224

3.15 225 shadow price 226 This is the price variation of the market welfare for the variation of 1 MW or A on this 227 particular critical network element. This identifies the impacts of the limiting element on the 228 market coupling welfare. 229

3.16 230 spanning margin value 231 SMV 232 This is the margin that is taken into account when spanning is applied. SMV is an historical 233 based parameter which specifies the amount of MW that reduces the RAM when spanning is 234 applied. 235

236

– of 48 –




4 The critical network element calculation and publ ication process 237

4.1. Overall business context 238

The business process described in this document is related to the determination of the critical 239 network elements and their publication for capacity allocation purposes. 240

The critical network elements determination process is based on a set of inputs data that are 241 out of the scope of this document. 242

The focus is put on the results of the critical network elements calculation which is provided to 243 TSOs for operational and publication purposes and market operator, such as power 244 exchanges (PXs), for market coupling allocation process. 245

This document describes for the flow based process or the capacity coordinated 246 determination process the necessary set of results on the critical network elements. 247

The critical network elements are determined based on a set of operational input data which 248 are out of the scope of this document, such as: 249

• DACF 250

• D-2CF 251

• GSK 252

• Available preventive remedial actions 253

• Potential outage cases 254

Those operational input data are called “network data” in this document. In a first step the 255 input data are given in individual models; in a second step they will respect the Common Grid 256 Model (CGM). 257

These steps are the identified use cases for the critical network elements determination 258 process and are to be carried out by the TSOs on day ahead (D-1). Figure 1 provides the use 259 case for the critical network element process. 260

Each TSO sends firstly their network data to the capacity coordinator. The data that are sent 261 are out of the scope of this document as considered of operational concerns. 262

Based on the network data of all the TSOs, the capacity coordinator performs a merge of 263 these data and computes the critical network elements. This part of the process refers directly 264 to guidelines CACM and CGMES. The calculation basically enables to identify which are the 265 most important limiting elements of the power network in several studied constraint situation, 266 i.e. outages. Once the calculation performed, the capacity coordinator provides the TSOs with 267 a list of critical network elements for internal process. The critical network elements are 268 provided in day ahead for a specific period of time. 269

The critical network elements enable to define then the net transfer capacity (NTC) on day 270 ahead to be used for daily allocation process. This part of the process refers directly to IEC 271 62325-451-3 business process. 272

The critical network elements may be provided, complemented by flow based parameters in 273 case flow based calculation is run instead of NTC determination. Those flow based 274 parameters will include the influence of the critical network elements on the market coupling 275 process. The critical network elements with flow based parameters define the so-called flow 276 based domain. The details of the flow based domain calculation process are out of the scope 277 of this document. 278

This flow based domain is provided by the capacity coordinator to the TSOs. An “anonymous” 279 version of the flow based domain (without identifying precisely the limiting elements of the 280 network) is sent to the market operator in order to be used for the market coupling calculation 281 process. 282

– of 48 –




283

Figure 1 – Use case of the critical network element s process 284

The market coupling process itself is out of the scope of this document. 285

However the market coupling results enable to identify the impact of the previously identified 286 critical network elements on the social welfare of the flow based market coupling area. This 287 impact is identified by the shadow price of the critical network element. 288

Finally, the shadow prices are published with the flow based domain to the market information 289 aggregator. 290

In case of NTC determination process, the critical network elements which effectively 291 constrained the allocation market position (market coupling or explication auction) are 292 published to the market information aggregator. 293

4.2 Critical network elements determination and pub lication 294

In a context of regional coordinated capacity calculation, it is of interest to perform a capacity 295 calculation on a common grid model (merge of each TSO network model) to identify the main 296

uc Cr i t ica lNetwor kElement Document use ca seuc Cr i t ica lNetwor kElement Document use ca seuc Cr i t ica lNetwor kElement Document use ca seuc Cr i t ica lNetwor kElement Document use ca se

:Ma r ket :Ma r ket :Ma r ket :Ma r ket

infor mat ion infor mat ion infor mat ion infor mat ion

aggr egatoraggr egatoraggr egatoraggr egator

:Ma r ket :Ma r ket :Ma r ket :Ma r ket

oper a toroper a toroper a toroper a tor

:Tr ansmission :Tr ansmission :Tr ansmission :Tr ansmission

sy stem sy stem sy stem sy stem

oper a tor oper a tor oper a tor oper a tor :Capacity :Capacity :Capacity :Capacity

coor dina torcoor dina torcoor dina torcoor dina tor

Send TSO networ k Send TSO networ k Send TSO networ k Send TSO networ k

da tada tada tada ta

Deter mine the cr it ica l Deter mine the cr it ica l Deter mine the cr it ica l Deter mine the cr it ica l

networ k elementsnetwor k elementsnetwor k elementsnetwor k elements

Compute the net Compute the net Compute the net Compute the net

t r ansfer capacityt r ansfer capacityt r ansfer capacityt r ansfer capacity

Deter mine the f low Deter mine the f low Deter mine the f low Deter mine the f low

based doma inbased doma inbased doma inbased doma in

Pr ov ide ma r ket P r ov ide ma r ket P r ov ide ma r ket P r ov ide ma r ket

coupl ing r esul tscoupl ing r esul tscoupl ing r esul tscoupl ing r esul ts

Publ ish the cr i t ica l Publ ish the cr i t ica l Publ ish the cr i t ica l Publ ish the cr i t ica l

networ k elementsnetwor k elementsnetwor k elementsnetwor k elements

Publish the impact of Publish the impact of Publish the impact of Publish the impact of

cr it ica l networ k elements cr it ica l networ k elements cr it ica l networ k elements cr it ica l networ k elements

on the ma r keton the ma r keton the ma r keton the ma r ket

Out of the Scope of

this document

– of 48 –




critical network elements of the region which will limit the net transfer capacity for the 297 allocation market. 298

The details of such a process are out of the scope of this document and those are 299 summarized by the two steps: 300

• Sending of TSOs network data to the capacity coordinator 301

• Critical network elements determination 302

Once the critical network elements determination process is performed in day ahead, the 303 capacity coordinator sends the list of identified critical network elements that constraint the 304 power network and induces congestions. Those critical network elements are identified for 305 one specific point of time hour of a delivery day. 306

There may be one or several constraint situations identified on the power network for one 307 specific point of time. Per constraint situation, one or several critical network elements may be 308 identified. It is of TSOs’ responsibility to monitor each critical network element. In this 309 condition, threshold values are provided as “monitored analog measurements” of the 310 “monitored elements” for TSOs internal process. 311

The net transfer capacity (NTC) will be calculated based on the critical network elements 312 determined by the capacity coordinator. The related oriented border associated to the critical 313 network elements calculation is provided in the critical network elements results. This 314 information is needed as an input for NTC determination. For instance, the critical network 315 elements identified in the calculation of the full export situation (from France to Italy) will be 316 used as inputs for NTC calculation on France-to-Italy border. 317

The details of the NTC calculation are out of the scope of this document. The publication of 318 NTC is out of the scope this document since for NTC, as described in IEC 62325-451-3, the 319 information is provided by using Capacity_MarketDocument. 320

The critical network elements results are published by the TSOs to the market information 321 aggregator without the monitored measurement information. 322

The NTC is then used for capacity allocation as described within IEC 62325-451-3. After 323 allocation, the critical network elements which effectively impacted the market position are 324 sent to the market information aggregator. 325

Figure 2 provides the sequence diagram for the critical network elements determination and 326 publication process. 327

The capacity coordinator sends the list of critical network elements to TSOs by using the 328 CriticalNetworkElement_MarketDocument. 329

The TSOs are using the CriticalNetworkElement_MarketDocument to publish the critical 330 network elements. The information about the limiting TSO and the location of the critical 331 network element is also of publication interest. 332

– of 48 –




333

Figure 2 – Critical network elements determination and publication 334

4.3 Flow based domain determination and publication 335

In the context of flow based capacity calculation, once the critical network elements 336 determination process is performed in day ahead, the capacity coordinator sends the defined 337 flow based domain to TSOs. 338

The flow based domain identifies the domain where the power system is safely operated 339 depending upon commercial exchanged flows and congestion management on the borders. 340 The flow based domain is identified per point of time by a set of critical network elements 341 influencing the allocation market with given weighting factors defined by the PTDF factors and 342 their associated RAM. Those critical network elements are identified for one specific point of 343 time of a delivery day. 344

There may be one or several constraint situations identified on the power network for one 345 specific point of time. Per constraint situation, only one critical network element is identified 346 by the flow based calculation. It is of TSOs’ responsibility to monitor each critical network 347 element. In this condition, threshold values are provided as “monitored analog measurements” 348 of the “monitored elements” for TSOs internal process. 349

The flow based domain is sent by the capacity coordinator to the market operator to take into 350 account the critical network elements with their PTDFs and RAM in the market coupling 351 calculation process. In this case, the critical network elements are sent in an anonymous way 352 and the analog measurements are not sent. 353

The same flow based domain result as for the market operator is also sent to the market 354 information aggregator. 355

sd Cr it ica l Networ k Elements deter mina t ion and publ ica t ionsd Cr it ica l Networ k Elements deter mina t ion and publ ica t ionsd Cr it ica l Networ k Elements deter mina t ion and publ ica t ionsd Cr it ica l Networ k Elements deter mina t ion and publ ica t ion

Capacity coordinator

(from Roles)

Transmission system

operator

(from Roles)

Market information

aggregator

(from Roles)

Out of the Scope of

this document

TSO network data()

Critical Network Elements

determination()Critical Network Elements

(CriticalNetworkElement_MarketDocument)



NTC Calculation()

NTC(IEC 62325-451-3 Capacity_MarketDocument)

Capacity Allocation (IEC 62325-451-3)

Critical Network Elements Market Impact (CriticalNetworkElement_MarketDocument)

– of 48 –




Then, once the market coupling process is performed and the calculation done, the impact of 356 each critical network element of the flow based domain on the social welfare of the flow based 357 market coupling region is available. 358

This impact is published as the shadow price of the critical network elements of the flow 359 based domain. 360

Figure 3 provides the sequence diagram for the critical network elements determination and 361 publication process. 362

363

Figure 3 – Flow based domain determination and publ ication 364

The capacity coordinator sends the flow based domain to TSOs by using the 365 CriticalNetworkElement_MarketDocument. 366

The TSOs are using the CriticalNetworkElement_MarketDocument to publish the flow based 367 domain. The information about the limiting TSO and the location of the critical network 368 element is also of a publication interest. 369

When the market coupling process is over, the TSOs are using the 370 CriticalNetworkElement_MarketDocument to publish the flow based domain with the shadow 371 prices. 372

4.4 Business rules for the critical network element determination process 373

4.4.1 General rules 374

The generic rules defined in IEC 62325-351 applied to all the documents described in this 375 part. In particular, IEC 62325-351 describes the concept of curve type that is to be used to 376 define the pattern of the critical network elements for a day. 377

For each electronic data interchange defined in this document, an application 378 acknowledgement is required as defined in IEC 62325-451-1. 379

When a document is received, it shall be checked at the application level to ensure that there 380 are no faults in it that could prevent its normal processing. After this check, an 381

sd Flow ba sed domain deter mina t ion a nd publica t ionsd Flow ba sed domain deter mina t ion a nd publica t ionsd Flow ba sed domain deter mina t ion a nd publica t ionsd Flow ba sed domain deter mina t ion a nd publica t ion

Transmission system

operator

(from Roles)

Capacity coordinator

(from Roles)

Market operator

(from Roles)

Market information

aggregator

(from Roles)

Out of scope of this

document

TSO network data()


determination()Flow based domain


Flow based domain


Flow based domain


Run market coupling()

Market coupling results()

Flow based market

impact(CriticalNetworkElement_MarketDocument)

– of 48 –




acknowledgement document, as defined in IEC 62325-451-1, shall be generated either 382 accepting in its entirety the document in question or rejecting it. 383

4.4.2 Dependencies governing the CriticalNetworkElement_ MarketDocument 384

The following rules applied to the CriticalNetworkElement_MarketDocument: 385

• A CriticalNetworkElement_MarketDocument may contain for a specific position several 386 Constraint_TimeSeries. 387

• In case of NTC Determination process, the TimeSeries of the 388 CriticalNetworkElement_MarketDocument provides the main related oriented border of the 389 calculation study used for NTC calculation: 390

– In_Domain.mRID: the area of the related oriented border study where the energy flows 391 into. 392

– Out_Domain.mRID: the area of the related oriented border study where the energy 393 comes from. 394

• There are two types of Constraint_TimeSeries. The BusinessType is used to distinguish 395 between both types: 396

– The studied constraint situation identified by a constraint situation and the associated 397 critical network elements: 398

• The Constraint_TimeSeries contains: 399

– A mRID which identifies a constraint situation. If a business process used a 400 coding scheme to identify the constraint situation (for example a Critical 401 Network Element and Critical Outage (CBCO) code), the mRID can bring this 402 information. 403

– A BusinessType which identifies the case: Critical Network Element, Red flag, 404 etc. 405

– A Name which maybe use to provide the outage situation name. 406

– A list of Outage_RegisteredResource which identifies the network elements in 407 outage for this studied case: 408

• There are as many Outage_RegisteredResource as network elements in 409 outage in the studied case. 410

• In case of N Situation studied case, there is no Outage_RegisteredResource 411 present in the Constraint_TimeSeries. 412

• The Outage_RegisteredResource is identified by its EIC code. 413

• The name of the Outgage_RegisteredResource may be provided. 414

• The location of the Outage_RegisteredResource is provided by In_Domain 415 and Out_Domain, using EIC code. 416

• For orientation purpose, In_AggregatedNode and Out_AggregatedNode, 417 using EIC code, may be used. 418

– A list of RemedialAction_RegisteredResource which identifies the network 419 elements on which remedial action are performed to relieve the constraints for 420 the studied case: 421

• There are as many RemedialAction_RegisteredResource as network 422 elements are used to relieve the constraint in the studied case. 423

• In case no remedial action is performed, there is no 424 RemedialAction_RegisteredResource present in the Constraint_TimeSeries. 425

• The RemedialAction_RegisteredResource is identified by its EIC code. 426

• The name of the RemedialAction_RegisteredResource may be provided. 427

• The location of the RemedialAction_RegisteredResource is provided by 428 In_Domain and Out_Domain, using EIC code. 429

– of 48 –





• The remedial action type shall be provided as Tieline, Line, Generation, 432 Load, Redispatching, etc. 433

• The remedial action status shall be provided as automatic, preventive or 434 curative action. 435

– A list of Monitored_RegisteredResource which identifies the limiting network 436 elements (so-called Critical network elements) in the studied case: 437

• There are as many Monitored_RegisteredResource as critical network 438 elements identified in the studied case. 439

• There is at least one Monitored_RegisteredResource present in the 440 Constraint_TimeSeries. 441

• The Monitored_RegisteredResource is identified by its EIC code. 442

• The name of the Monitored_RegisteredResource may be provided. 443

• The location of the Monitored_RegisteredResource is provided by 444 In_Domain and Out_Domain, using EIC code. 445


• A list of measurements of interest for the Monitored_RegisteredResource 448 may be provided through the usage of the class Analog. 449

• In case of Flow Based, a set of flow Based Parameters may be provided for 450 the Monitored_RegisteredResource. In this case: 451

The Flow Based Remedial available Margin shall be provided for the studied 452 flow based Studied Area (using EIC code). 453

The shadow price may be provided for the market coupling area (using EIC 454 code). 455

A set of PTDF factors shall be provided. One PTDF factor shall be provided 456 per bidding zone (using EIC code). 457

– The external constraint identified by a global capacity constraint as a total transfer 458 capacity (TTC) or a net position limitation (bidding zone import or export) for instance. 459

• The Constraint_TimeSeries contains: 460

– A BusinessType which identifies the External Constraint. The external 461 constraint may be of TTC (Total Transfer Capacity), NTC (Net Transfer 462 Capacity), ATC min, net position, etc. 463

– A Name may be used to provide the external constraint name. 464

– The external constraint quantity shall be used to provide the quantity 465 BusinessType-related constraint. 466

• In case of external Constraint_TimeSeries, the Outage_RegisteredResource, 467 RemedialAction_RegisteredResource, Monitored_RegisteredResource classes 468 shall not be used. 469

• The class Analog shall be used to provide the measurements of interest for the 470 Monitored_RegisteredResource of the Constraint_TimeSeries: 471

– There are as many Analog as measurements of interest for the 472 Monitored_RegisteredResource. 473

– For one Monitored_RegisteredResource, the Analog contains: 474

• A measurementType which defines the nature of the monitored measurement. The 475 list of authorized measurementType is: flow, maximum flow, reference flow, flow 476 reliability margin, spanning margin value, long term allocation margin,final 477 adjustment margin value. 478

– of 48 –




• A unitSymbol which identifies the unit of the measurement. 479

• A positiveFlowIn which identifies on which direction the 480 Monitored_RegisteredResource element is monitored. 481

– For each measurement, the values shall be provided by AnalogValues: 482

• There are as many AnalogValues as measured occurrence of the Analog 483 measurement. 484

• For each AnalogValues: 485

– The value of the measurement shall be provided. 486

– The constraint duration of such a measurement may be provided. 487

– The condition description of such a measurement may be provided as “Before 488 Outage”, “After Outage”, “After curative action”, etc. 489

• Two types of document are identified depending on the two processes of critical network 490 elements calculation: 491

– The critical network elements determination document that is used for a coordinated 492 NTC calculation process. 493

– The flow based domain document that replaces the ATC in usual IEC 62325-451-3 494 process and is used directly for Flow Based capacity allocation. 495

• Specific types of document for publication are also identified: 496

– The critical network elements publication which is used to provide only relevant 497 information to market information aggregator. 498

– The critical network elements market impact publication which is used to provide the 499 critical network elements which effectively impacted the allocation market. 500

– The flow based domain publication which is used to publish only the relevant 501 information to market information aggregator. 502

– The flow based market impact document which is used to publish the shadow prices of 503 the critical network elements to market information aggregator. 504

• As defined previously, there shall be at least one monitored element per 505 Constraint_TimeSeries of constraint situation type: 506

– For flow based, only one critical network element shall be identified per constraint 507 situation. 508

– For coordinated NTC calculation, several critical network elements may be identified 509 per constraint situation. 510

• In case any constraint situation can be provided for one specific position of time, the point 511 shall not provide any Constraint_TimeSeries: 512

– The reason class associated to the class Point shall be used to inform that no 513 constraint situation is provided. 514

• In case any constraint situation can be provided for the whole delivery period, document 515 shall not provide any TimeSeries: 516

– The reason class associated to the class MarketDocument shall be used to inform that 517 no constraint situation is provided for the whole delivery period. 518

The dependencies are listed in: 519

• Table 1: Flow Based Domain 520

• Table 2: Flow Based Domain Publication 521

• Table 3: Flow Based Market Impact Publication 522

• Table 4: Critical Network Element Determination 523

• Table 5: Critical Network Element Publication 524

• Table 6: Critical Network Element Market Impact Publication 525

– of 48 –




Table 1 – Flow based Domain dependency 526

Class Attribute Flow Based Process

Cri

tica

lNe

two

rkE

lem

en

t M

ark

etD

ocu

me

nt

type B08 = Flow Based Domain

process.processType A43 = Flow Based domain constraint DayAhead

A44 = Flow Based domain constraint Intraday

sender_MarketParticipant.marketRole.type A36 = Capacity Coordinator

receiver_MarketParticipant.marketRole.type A04 = TSO

domain.mRID used as EIC code of the Flow Based Study Area

Tim

e S

eri

es

mRID used to identify the TS

businessType B37 = Constraint Situation

B38 = Initial Domain

B39 = Flow based Domain Adjusted to Long Term schedules

In_Domain.mRID not used

Out_Domain.mRID not used

CurveType used

Series_Period

Point

527

Constraint Situation Type External Constraint Type

Co

nst

rain

t_T

ime

Se

rie

s

mRID used to identify the Constraint_TimeSeries used to identify the Constraint_TimeSeries

businessType used

B40 = Network Element Constraint

B41 = Calculation opposition (Red Flag)

used

B09 = Net position

name may be used

To provide a Name to the Constraint Situation

may be used

To provide a Name to the External Constraint

Quantity_Measurement_Unit.name used for the Flow Based Margin used for External Constraint (= MW)

ExternalConstraint_Quantity.quantity not used used to provide External Constraint Quantity

pTDF_Measurement_Unit.name used for PTDF not used

shadowPrice_Measurement_Unit.name not used not used

currency_Unit.name not used not used

Party_MarketParticipant.mRID used to identify the limiting TSOs used to identify the limiting TSOs

Ou

tag

e_

Re

gis

tere

dR

eso

urc

e

mRID used as EIC code of the Outage element not used

name used as the name of the Outage element not used

In_Domain used to identify InArea not used

Out_Domain used to identify OutArea not used

In_AggregateNode may be used to identify InAggregateNode for element orientation

not used

Out_AggregateNode may be used to identify OutAggregateNode for element orientation

not used

Re

me

dia

lAct

ion

_R

eg

iste

red

Re

sou

rce

mRID used as EIC code of the element on which a remedial action is carried out

not used

name used as the name of the element on which a remedial action is carried out

not used




not used


not used

– of 48 –





pSRType.psrType used to identify the type of the remedial action

A01 = Tieline, A02 = line, A04 = Generation, A05 = Load

not used

marketObjectStatus_status Used to identify the status of the remedial action

A18 = Preventive

A19 = Curative

not used

Mo

nit

ore

d_

Re

gis

tere

dR

eso

urc

e

mRID used as EIC code of the Monitored element not used

name used as the name of the Monitored element not used



In_AggregateNode used to identify InAggregateNode for element orientation

not used

Out_AggregateNode used to identify OutAggregateNode for element orientation

not used

flowBasedStudy_Domain.mRD used as EIC code of the Flow Based Study Area

not used

flowBasedStudy_Domain.flowBasedMargin_Quantity.quantity

used for the RAM not used

marketCoupling_Domain.mRID not used not used

marketCoupling_Domain.shadow_Price.amount not used not used

An

alo

g

measurementType used to identify the monitored measurements

A01 = Flow

A02 = Maximum Flow

A03 = Flow Reliability Margin

A04 = Spanning Margin Value

A05 = Long Term Allocation Margin

A06 = Final adjustment margin value

not used

unitSymbol used to identify the unit of the measurement

"A", "MW", "%"…

not used

positiveFlowIn may be used to identify on which direction the element is monitored

A01 = Direct

A02 = Opposite

Not used = Double

not used

An

alo

g V

alu

es

value used to provide the measurement value not used

timeStamp may be used to provide the constraint duration

not used

description may be used to identify the situation of the measurement point

"Before Outage", "After Curative Action"…

not used

PTDF

Domain

mRID used to identify the impacted bidding zone not used

pTDF_Quantity.quantity used to provide the PTFD factor for the Bidding zone

not used

528

– of 48 –




Table 2 – Flow based Publication dependency 529


Cri

tica

lNe

two

rkE

lem

en

t M

ark

etD

ocu

me

nt

type B09 = Flow Based Domain Publication



sender_MarketParticipant.marketRole.type A36 = Capacity Coordinator or A04 = TSO

receiver_MarketParticipant.marketRole.type A32 = Market Information Aggregator or A11 = Market Operator


Tim

e S

eri

es




businessType B39 = Flow based Domain Adjusted to Long Term schedules

CurveType used

Series_Period

Point

530


Co

nst

rain

t_T

ime

Se

rie

s


businessType used



used

B09 = Net position

name may be used


may be used








Ou

tag

e_

Re

gis

tere

dR

eso

urc

e mRID used as anonymous EIC code of the Outage

element not used





not used


not used

Re

me

dia

lAct

ion

_R

eg

iste

red

Re

sou

rce

mRID not used not used

name not used not used

In_Domain not used not used

Out_Domain not used not used

In_AggregateNode not used not used

Out_AggregateNode not used not used

– of 48 –





pSRType.psrType not used not used

marketObjectStatus_status not used not used

Mo

nit

ore

d_

Re

gis

tere

dR

eso

urc

e

mRID used as anonymous EIC code of the Monitored element

not used





not used


not used


not used





An

alo

g measurementType not used not used

unitSymbol not used not used

positiveFlowIn not used not used

An

alo

g

Va

lue

s

value not used not used

timeStamp not used not used

description not used not used

PTDF

Domain



not used

531

– of 48 –




Table 3 – Flow based Market Impact Publication depe ndency 532


Cri

tica

lNe

two

rkE

lem

en

t M

ark

etD

ocu

me

nt

type B10 = Flow Based domain Market Impact Publication




receiver_MarketParticipant.marketRole.type A32 = Market Information Aggregator or A11 = Market Operator


Tim

e S

eri

es


businessType B39 = Domain Adjusted to Long Term schedules



CurveType used

Series_Period

Point

533


Co

nst

rain

t_T

ime

Se

rie

s


businessType used



used

B09 = Net position

name may be used


may be used





shadowPrice_Measurement_Unit.name used for Shadow Price (per MW or A) not used

currency_Unit.name used for Shadow Price not used


Ou

tag

e_

Re

gis

tere

dR

eso

urc


element not used





not used


not used

Re

me

dia

lAct

ion

_R

eg

iste

red

Re

sou

rce







– of 48 –







Mo

nit

ore

d_

Re

gis

tere

dR

eso

urc

e


not used





not used


not used


not used



marketCoupling_Domain.mRID used as EIC code of the Flow Based Market Coupling Area

not used

marketCoupling_Domain.shadow_Price.amount used to provide the shadow price of the critical network element for the area

not used

An

alo




An

alo

g

Va

lue

s




PTDF

Domain



not used

534

– of 48 –




Table 4 – NTC Coordinated Determination dependency 535

Class Attribute NTC Coordinated Calculation Process

Cri

tica

lNe

two

rkE

le

me

nt

Ma

rke

tDo

cum

en

t type B06 = Critical Network Element Determination

process.processType A15 = Capacity Determination or A40 = Intraday Process

sender_MarketParticipant.marketRole.type A36 = Capacity Coordinator

receiver_MarketParticipant.marketRole.type A04 = TSO

domain.mRID used as EIC code of the coordinated area

Tim

e S

eri

es



In_Domain.mRID used as EIC code of the InArea of the oriented border study impacted by the listed Critical network elements

Out_Domain.mRID used as EIC code of the OutArea of the oriented border study impacted by the listed Critical network elements

CurveType used

Series_Period

Point

536


Co

nst

rain

t_T

ime

Se

rie

s


businessType used



used

A81 = TTC

name may be used


may be used


Quantity_Measurement_Unit.name not used used for External Constraint (= MW)


pTDF_Measurement_Unit.name not used not used




Ou

tag

e_

Re

gis

tere

dR

eso

urc

e

mRID used as EIC code of the Outage element not used





not used


not used

Re

me

dia

lAct

ion

_R

eg

iste

red

Re

sou

rce

mRID used as EIC code of the element on which a remedial action is carried out

not used

name used as the name of the element on which a remedial action is carried out

not used




not used


not used

pSRType.psrType used to identify the type of the remedial action

not used

– of 48 –





A01 = Tieline, A02 = line, A04 = Generation, A05 = Load

marketObjectStatus_status Used to identify the status of the remedial action

A18 = Preventive

A19 = Curative

not used

Mo

nit

ore

d_

Re

gis

tere

dR

eso

urc

e

mRID used as EIC code of the Monitored element not used





not used


not used

flowBasedStudy_Domain.mRD not used not used


not used not used



An

alo

g

measurementType used to identify the monitored measurements

A01 = Flow

A02 = Maximum Flow

A03 = Flow Reliability Margin

A04 = Spanning Margin Value

A05 = Long Term Allocation Margin

A06 = Final adjustment margin value

not used

unitSymbol used to identify the unit of the measurement

"A", "MW", "%"…

not used

positiveFlowIn may be used to identify on which direction the element is monitored

A01 = Direct

A02 = Opposite

Not used = Double

not used

An

alo

g V

alu

es

value used to provide the measurement value not used

timeStamp may be used to provide the constraint duration

not used

description may be used to identify the situation of the measurement point

"Before Outage", "After Curative Action"…

not used

PTDF

Domain


pTDF_Quantity.quantity not used not used

537

– of 48 –




Table 5 – Critical Network Element Publication depe ndency 538


Cri

tica

lNe

two

rkE

le

me

nt

Ma

rke

tDo

cum

en

t type B07 = Critical Network Element Publication



receiver_MarketParticipant.marketRole.type A32 = Market Information Aggregator


Tim

e S

eri

es



In_Domain.mRID used as EIC code of the InArea of the oriented border study impacted by the listed Critical network elements

Out_Domain.mRID used as EIC code of the OutArea of the oriented border study impacted by the listed Critical network elements

CurveType used

Series_Period

Point

539


Co

nst

rain

t_T

ime

Se

rie

s


businessType used



used

A81 = TTC

name may be used


may be used








Ou

tag

e_

Re

gis

tere

dR

eso

urc


element not used





not used


not used

Re

me

dia

lAct

ion

_R

eg

iste

red

Re

sou

rce







– of 48 –







Mo

nit

ore

d_

Re

gis

tere

dR

eso

urc

e


not used





not used


not used



not used not used



An

alo




An

alo

g

Va

lue

s




PTDF

Domain



540

– of 48 –




Table 6 – Critical Network Element Market Impact Pu blication dependency 541


Cri

tica

lNe

two

rkE

le

me

nt

Ma

rke

tDo

cum

en

t type B12 = Critical Network Element Market Impact Publication



receiver_MarketParticipant.marketRole.type A32 = Market Information Aggregator


Tim

e S

eri

es



In_Domain.mRID used as EIC code of the InMarketArea which was effectively impacted by the listed Critical network elements

Out_Domain.mRID used as EIC code of the OutMarketArea which was effectively impacted by the listed Critical network elements

CurveType used

Series_Period

Point

542


Co

nst

rain

t_T

ime

Se

rie

s


businessType used



used

A81 = TTC

name may be used


may be used








Ou

tag

e_

Re

gis

tere

dR

eso

urc


element not used





not used


not used

Re

me

dia

lAct

ion

_R

eg

iste

red

Re

sou

rce







– of 48 –







Mo

nit

ore

d_

Re

gis

tere

dR

eso

urc

e


not used





not used


not used



not used not used



An

alo




An

alo

g

Va

lue

s




PTDF

Domain



543

– of 48 –




5 Contextual and assembly models 544

5.1 CriticalNetworkElement contextual model 545

5.1.1 Overview of the model 546

Figure 4 shows the model. 548

549

Figure 4 – CriticalNetworkElement contextual model 550

5.1.2 IsBasedOn relationships from the European sty le market profile 551

Table 7 shows the traceability dependency of the classes used in this package towards the 552 upper level. 553

Table 7 – IsBasedOn dependency 554

Name Complete IsBasedOn Path

AggregateNode TC57CIM::IEC62325::MarketOperations::ReferenceData::AggregateNode

Analog TC57CIM::IEC61970::Base::Meas::Analog

AnalogValue TC57CIM::IEC61970::Base::Meas::AnalogValue

Constraint_TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

CriticalNetworkElement_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument

– of 48 –





Currency_Unit TC57CIM::IEC62325::MarketManagement::Unit

Domain TC57CIM::IEC62325::MarketManagement::Domain

ExternalConstraint_Quantity TC57CIM::IEC62325::MarketManagement::Quantity

FlowBasedMargin_Quantity TC57CIM::IEC62325::MarketManagement::Quantity

FlowBasedStudy_Domain TC57CIM::IEC62325::MarketManagement::Domain

MarketCoupling_Domain TC57CIM::IEC62325::MarketManagement::Domain

MarketObjectStatus TC57CIM::IEC62325::MarketManagement::MarketObjectStatus

MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant

MarketRole TC57CIM::IEC62325::MarketCommon::MarketRole

Measure_Unit TC57CIM::IEC62325::MarketManagement::Unit

MktPSRType TC57CIM::IEC62325::MarketManagement::MktPSRType

Monitored_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Outage_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Party_MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant

Point TC57CIM::IEC62325::MarketManagement::Point

Process TC57CIM::IEC62325::MarketManagement::Process

PTDF_Domain TC57CIM::IEC62325::MarketManagement::Domain

PTDF_Quantity TC57CIM::IEC62325::MarketManagement::Quantity

Reason TC57CIM::IEC62325::MarketManagement::Reason

RemedialAction_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Series_Period TC57CIM::IEC62325::MarketManagement::Period

Shadow_Price TC57CIM::IEC62325::MarketManagement::Price

Time_Period TC57CIM::IEC62325::MarketManagement::Period

TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

555

– of 48 –




5.2 CriticalNetworkElement assembly model 556

5.2.1 Overview of the model 557

Figure 5 shows the model. 558

559

Figure 5 – CriticalNetworkElement assembly model 560

5.2.2 IsBasedOn relationships from the European sty le market profile 561

Table 8 shows the traceability dependency of the classes used in this package towards the 562 upper level. 563

– of 48 –




Table 8 – IsBasedOn dependency 564


Analog TC57CIM::IEC61970::Base::Meas::Analog

AnalogValue TC57CIM::IEC61970::Base::Meas::AnalogValue

Constraint_TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

CriticalNetworkElement_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument

Monitored_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Outage_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Party_MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant

Point TC57CIM::IEC62325::MarketManagement::Point

PTDF_Domain TC57CIM::IEC62325::MarketManagement::Domain

Reason TC57CIM::IEC62325::MarketManagement::Reason

RemedialAction_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Series_Period TC57CIM::IEC62325::MarketManagement::Period

TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

565

5.2.3 Detailed CriticalNetworkElement assembly mode l 566

5.2.3.1 CriticalNetworkElement_MarketDocument root class 567

This document provides the computed critical network elements to be used for capacity 568 allocation and publication. The critical network elements are the main limiting elements 569 identified after a coordinated network study. 570

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

Table 9 shows all attributes of CriticalNetworkElement_MarketDocument. 573

Table 9 – Attributes of CriticalNetworkElement asse mbly 574 model::CriticalNetworkElement_MarketDocument 575

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 with in the document.

4 [1..1] sender_MarketParticipant.mRID

PartyID_String

The identification of a party in the energy market. --- Document owner.

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

MarketRoleKind_String

The identification of the role played by a market player. --- Document owner. --- The role associated with a MarketParticipant.

6 [1..1] receiver_MarketParticipant.mRID

PartyID_String

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

– of 48 –





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

MarketRoleKind_String

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

8 [1..1] createdDateTime

ESMP_DateTime

The date and time of the creation of the document.

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 critical network elements study time interval. All time intervals for the time series in the document shall be within the total time interval for the study. The receiver will discard any time intervals outside the time period.

10 [0..1] domain.mRID

AreaID_String

The unique identification of the domain. --- The identification of the domain that is covered in the critical network element document. It is in general the coordinated capacity determination area that is the subject of the schedule plan.

576

Table 10 shows all association ends of CriticalNetworkElement_MarketDocument with other 577 classes. 578

Table 10 – Association ends of CriticalNetworkEleme nt assembly 579 model::CriticalNetworkElement_MarketDocument with o ther classes 580

Order mult. Class name / Role

Description

11 [0..*] TimeSeries

TimeSeries

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

581

5.2.3.2 Analog 582

Analog represents an analog Measurement. 583

Analog provides the analog measurements monitored for one specific 584 Monitored_RegisteredResource. 585

Table 11 shows all attributes of Analog. 586

Table 11 – Attributes of CriticalNetworkElement ass embly model::Analog 587

Order mult. Attribute name / Attribute type

Description

0 [1..1] measurementType

AnalogType_String

Specifies the type of measurement. For example, this specifies if the measurement represents line flow, maximum line flow, reference line flow, etc.

1 [1..1] unitSymbol

UnitSymbol

The unit of measure of the measured quantity.

2 [0..1] positiveFlowIn

ESMPBoolean_String

If true then this measurement is an active power, reactive power or current with the convention that a positive value measured at the Terminal means power is flowing into the related Monitored_RegisteredResource depending on the In_AggregateNode and the Out_AggregateNode.

588

Table 12 shows all association ends of Analog with other classes. 589

– of 48 –




Table 12 – Association ends of CriticalNetworkEleme nt assembly model::Analog with 590 other classes 591

Order mult. Class name / Role Description

3 [1..*] AnalogValue

AnalogValues

Measurement to which this value is connected. Association Based On : CriticalNetworkElement contextual model::AnalogValue.AnalogValues[1..*] ----- CriticalNetworkElement contextual model::Analog.[]

592

5.2.3.3 AnalogValue 593

AnalogValue represents an analog MeasurementValue. 594

Table 13 shows all attributes of AnalogValue. 595

Table 13 – Attributes of CriticalNetworkElement ass embly model::AnalogValue 596


Description

0 [1..1] value

ESMP_Float

The value to supervise.

1 [0..1] timeStamp

DateTime

The date and time to which the value refers to; it may be before or after the outage time (attribute position of class Point).

2 [0..1] description

String

It provides information about when the measurement point is computed, i.e. before the outage, after the outage, after curative action, etc.

597

5.2.3.4 Constraint_TimeSeries 598

A set of constraint situations for one specific position which results from the critical network 599 elements determination process and which may have an impact on the market by inducing 600 congestions. 601

Table 14 shows all attributes of Constraint_TimeSeries. 602

Table 14 – Attributes of CriticalNetworkElement ass embly 603 model::Constraint_TimeSeries 604


0 [1..1] mRID

ID_String

A unique identification of the constraint time series.

1 [1..1] businessType

BusinessKind_String

The identification of the nature of the Constraint_TimeSeries. The constraint is the result of a study of an N situation, N-1 situation, or N-K situation. The constraint could also be more general such as a TTC limitation. In this case, it is an external constraint.

2 [0..1] name

String

The name of the outage described in this constraint time series.

3 [0..1] quantity_Measurement_Unit.name

MeasurementUnitKind_String

The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit of the external quantity when applicable. The unit of the remaining available margin when applicable.

– of 48 –





4 [0..1] externalConstraint_Quantity.quantity

Decimal

The quantity value associated to the business type of the Constraint_TimeSeries. The association role provides the information about what is expressed. --- The quantity value of the external constraint identified in the business type of the Constraint_TimeSeries.

5 [0..1] externalConstraint_Quantity.quality

Quality_String

The description of the quality of the quantity. --- The quantity value of the external constraint identified in the business type of the Constraint_TimeSeries.

6 [0..1] pTDF_Measurement_Unit.name


The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit of the PTDF quantity.

7 [0..1] shadowPrice_Measurement_Unit.name


The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit of measurement for shadow price, e.g. per MW, per A.

8 [0..1] currency_Unit.name

CurrencyCode_String

The identification of the formal code for a currency (ISO 4217). --- The currency unit of the shadow price for flow based market coupling.

605

Table 15 shows all association ends of Constraint_TimeSeries with other classes. 606

Table 15 – Association ends of CriticalNetworkEleme nt assembly 607 model::Constraint_TimeSeries with other classes 608


9 [0..*] Party_MarketParticipant

Party_MarketParticipant

The list of limiting TSO(s) for the Constraint_TimeSeries. There may be several limiting TSOs, e.g. for the outage of an interconnection line. Association Based On : CriticalNetworkElement contextual model::Party_MarketParticipant.Party_MarketParticipant[0..*] ----- CriticalNetworkElement contextual model::Constraint_TimeSeries.[]

10 [0..*] Outage_RegisteredResource

Outage_RegisteredResource

The identification of an outage resource associated with a Constraint_TimeSeries. This is the outage element in the constraint situation. Association Based On : CriticalNetworkElement contextual model::Outage_RegisteredResource.Outage_RegisteredResource[0..*] ----- CriticalNetworkElement contextual model::Constraint_TimeSeries.[]

11 [0..*] RemedialAction_RegisteredResource

RemedialAction_RegisteredResource

The identification of a remedial action resource associated with a Constraint_TimeSeries. This identified the resource on which actions are carried out in order to remedy to a constraint of the Constraint_TimeSeries. Association Based On : CriticalNetworkElement contextual model::RemedialAction_RegisteredResource.RemedialAction_RegisteredResource[0..*] ----- CriticalNetworkElement contextual model::Constraint_TimeSeries.[]

12 [0..*] Monitored_RegisteredResource

Monitored_RegisteredResource

The identification of a monitored resource associated with a Constraint_TimeSeries. This is the resource monitored via Analog measurement. Association Based On : CriticalNetworkElement contextual model::Monitored_RegisteredResource.Monitored_RegisteredResource[0..*] ----- CriticalNetworkElement contextual model::Constraint_TimeSeries.[]

– of 48 –





13 [0..*] Reason

Reason

The complementary information provided for the Constraint_TimeSeries. Association Based On : CriticalNetworkElement contextual model::Reason.Reason[0..*] ----- CriticalNetworkElement contextual model::Constraint_TimeSeries.[]

609

5.2.3.5 Monitored_RegisteredResource 610

This is the critical network element of the power network in the constraint situation described 611 by the Constraint_TimeSseries. Analog measurements are monitored for this resource to 612 identify the impact of this critical network element on the market. 613

Table 16 shows all attributes of Monitored_RegisteredResource. 614

Table 16 – Attributes of CriticalNetworkElement ass embly 615 model::Monitored_RegisteredResource 616


0 [0..1] mRID

ResourceID_String

This is the network element of the power network in the constraint situation described by the Constraint_TimeSseries. The unique identification of a resource.

1 [0..1] name

String

The name is any free human readable and possibly non unique text naming the object.

2 [0..1] in_Domain.mRID

AreaID_String

The unique identification of the domain. --- The control area where the flow measurement enters for the monitored resource.

3 [0..1] out_Domain.mRID

AreaID_String

The unique identification of the domain. --- The control area connected to the monitored resource where the flow measurement comes out.

4 [0..1] in_AggregateNode.mRID

MeasurementPointID_String

The unique identification of an AggregateNode. --- The node connected to the monitored resource from which the flow measurement enters.

5 [0..1] out_AggregateNode.mRID


The unique identification of an AggregateNode. --- The node connected to the monitored resource from which the flow measurement comes out.

6 [0..1] flowBasedStudy_Domain.mRID

AreaID_String

The area used for running the flow based calculation. The unique identification of the domain. --- The identification of the flow based study area linked to the critical network element.

7 [0..1] flowBasedStudy_Domain.flowBasedMargin_Quantity.quantity

Decimal

The quantity value of remaining available margin of the critical network element identified in Monitored_RegisteredResource.. The association role provides the information about what is expressed. --- The identification of the flow based study area linked to the critical network element. --- This is the associated RAM quantity of the critical network element for a flow based study domain.

– of 48 –





8 [0..1] flowBasedStudy_Domain.flowBasedMargin_Quantity.quality

Quality_String

The description of the quality of the quantity. --- The identification of the flow based study area linked to the critical network element. --- This is the associated RAM quantity of the critical network element for a flow based study domain.

9 [0..1] marketCoupling_Domain.mRID

AreaID_String

The identification of the flow based market coupling area. The unique identification of the domain. --- The identification of the flow based market coupling domain impacted by the critical network element.

10 [0..1] marketCoupling_Domain.shadow_Price.amount

Amount_Decimal

A number of monetary units specified in a unit of currency. --- The identification of the flow based market coupling domain impacted by the critical network element. --- The impact of the critical network element on the variation of the social welfare of the market coupling domain.

617

Table 17 shows all association ends of Monitored_RegisteredResource with other classes. 618

Table 17 – Association ends of CriticalNetworkEleme nt assembly 619 model::Monitored_RegisteredResource with other clas ses 620


Description

11 [0..*] PTDF_Domain

PTDF_Domain

The bidding zone impacted by the critical network element and for which a PTDF factor is calculated. Association Based On : CriticalNetworkElement contextual model::PTDF_Domain.PTDF_Domain[0..*] ----- CriticalNetworkElement contextual model::Monitored_RegisteredResource.[]

12 [0..*] Analog

Measurements

The monitored measurements for the critical network element. Association Based On : CriticalNetworkElement contextual model::Analog.Measurements[0..*] ----- CriticalNetworkElement contextual model::Monitored_RegisteredResource.[]

621

5.2.3.6 Outage_RegisteredResource 622

This is one of the network elements which are in outage for the studied constraint situation 623 defined be the Constraint_TimeSeries. 624

Table 18 shows all attributes of Outage_RegisteredResource. 625

Table 18 – Attributes of CriticalNetworkElement ass embly 626 model::Outage_RegisteredResource 627


Description

0 [1..1] mRID

ResourceID_String

This is one of the network elements which are in outage for the studied constraint situation defined by the Constraint_Time Series. The unique identification of a resource.

1 [0..1] name

String


– of 48 –





Description


AreaID_String

The unique identification of the domain. --- The control area where an extremity of the resource is located. This is used to provide orientation information.


AreaID_String




The unique identification of an AggregateNode. --- The node connected to the resource; it is used to provide flow orientation information.




628

5.2.3.7 Party_MarketParticipant 629

The identification of the limiting TSOs of the critical network element for the associated 630 Constraint_TimeSeries. 631

The identification of the party participating in energy market business processes. 632

Table 19 shows all attributes of Party_MarketParticipant. 633

Table 19 – Attributes of CriticalNetworkElement ass embly 634 model::Party_MarketParticipant 635


Description

0 [1..1] mRID

PartyID_String

The identification of the limiting TSO associated to the Constraint_TimeSeries.

636

5.2.3.8 Point 637

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

Table 20 shows all attributes of Point. 639

Table 20 – Attributes of CriticalNetworkElement ass embly model::Point 640


Description

0 [1..1] position

Position_Integer

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

641

Table 21 shows all association ends of Point with other classes. 642

– of 48 –




Table 21 – Association ends of CriticalNetworkEleme nt assembly model::Point with 643 other classes 644


1 [0..*] Constraint_TimeSeries

Constraint_TimeSeries

The set of constraint time series for the associated position coming from the critical network element determination process. Association Based On : CriticalNetworkElement contextual model::Point.[] ----- CriticalNetworkElement contextual model::Constraint_TimeSeries.Constraint_TimeSeries[0..*]

2 [0..*] Reason

Reason

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

645

5.2.3.9 PTDF_Domain 646

The bidding zone impacted by the critical network element. 647

A domain covering a number of related objects, such as market balance area, grid area, 648 borders etc. 649

Table 22 shows all attributes of PTDF_Domain. 650

Table 22 – Attributes of CriticalNetworkElement ass embly model::PTDF_Domain 651


Description

0 [1..1] mRID

AreaID_String

The bidding zone impacted by the critical network element. The unique identification of the domain.

1 [1..1] pTDF_Quantity.quantity

Decimal

The PTDF factor value associated to the bidding zone for the critical network element. The association role provides the information about what is expressed. --- The PTDF factor value associated to the bidding zone for the critical network element.

2 [0..1] pTDF_Quantity.quality

Quality_String

The description of the quality of the quantity. --- The PTDF factor value associated to the bidding zone for the critical network element.

652

5.2.3.10 Reason 653

The motivation of an act. 654

Table 23 shows all attributes of Reason. 655

Table 23 – Attributes of CriticalNetworkElement ass embly model::Reason 656


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.

657

– of 48 –




5.2.3.11 RemedialAction_RegisteredResource 658

This is one of the network element on which remedial action are carried out to improve the 659 constraint situation. Those elements are used to remedy to critical constraints induced by the 660 constraint situation. 661

The remedial actions may be identified as automatic, preventive or curative. 662

The type of the remedial action is also provided: generation, load and topology. 663

Table 24 shows all attributes of RemedialAction_RegisteredResource. 664

Table 24 – Attributes of CriticalNetworkElement ass embly 665 model::RemedialAction_RegisteredResource 666


Description

0 [1..1] mRID

ResourceID_String

This is one of the network element on which remedial action are carried out to improve the constraint situation. Those elements are used to remedy to critical constraints induced by the constraint situation. The unique identification of a resource.

1 [0..1] name

String



AreaID_String



AreaID_String








6 [1..1] pSRType.psrType

PsrType_String

The coded type of the remedial action carried out on the associated resource. --- The coded type of the remedial action carried out on the associated resource.

7 [1..1] marketObjectStatus.status

Status_String

The status of the remedial action resource. It may be preventive or curative. The coded condition or position of an object with regard to its standing. --- The status of the registered resource, e.g. connected, disconnected, outage, ...

667

5.2.3.12 Series_Period 668

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

Table 25 shows all attributes of Series_Period. 670

Table 25 – Attributes of CriticalNetworkElement ass embly model::Series_Period 671


Description

0 [1..1] timeInterval

ESMP_DateTimeInterval

The start and end time of the period.

1 [1..1] resolution

Duration

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

– of 48 –




672

Table 26 shows all association ends of Series_Period with other classes. 673

Table 26 – Association ends of CriticalNetworkEleme nt assembly model::Series_Period 674 with other classes 675


2 [1..*] Point

Point

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

676

5.2.3.13 TimeSeries 677

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

Table 27 shows all attributes of TimeSeries. 679

Table 27 – Attributes of CriticalNetworkElement ass embly model::TimeSeries 680


Description

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.


AreaID_String

The unique identification of the domain. --- In case of NTC determination process, this is the area of the related oriented border study in which the energy flows into.


AreaID_String

The unique identification of the domain. --- In case of NTC determination process, this is the area of the related oriented border study in which the energy comes from.

4 [1..1] curveType

CurveType_String

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

681

Table 28 shows all association ends of TimeSeries with other classes. 682

Table 28 – Association ends of CriticalNetworkEleme nt assembly model::TimeSeries 683 with other classes 684


Description

5 [1..*] Series_Period

Period

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

6 [0..*] Reason

Reason

At the TimeSeries level the reason code is used to enable processing of the reason text which, depending on market conditions, should be provided in intra day trading. In this context only one reason code has been defined (A48, modification reason). No other codes are permitted. Association Based On : CriticalNetworkElement contextual model::TimeSeries.[] ----- CriticalNetworkElement contextual model::Reason.Reason[0..*]

685

– of 48 –




5.2.4 Datatypes 686

The list of datatypes used for the CriticalNetworkElement assembly model is as follows: 687

• ESMP_DateTimeInterval compound 688

• Amount_Decimal datatype 689

• AnalogType_String datatype, codelist AnalogTypeList 690

• AreaID_String datatype, codelist CodingSchemeTypeList 691

• BusinessKind_String datatype, codelist BusinessTypeList 692

• CurrencyCode_String datatype, codelist CurrencyTypeList 693

• CurveType_String datatype, codelist CurveTypeList 694

• ESMP_DateTime datatype 695

• ESMP_Float datatype 696

• ESMPBoolean_String datatype, codelist IndicatorTypeList 697

• ESMPVersion_String datatype 698

• ID_String datatype 699

• MarketRoleKind_String datatype, codelist RoleTypeList 700

• MeasurementPointID_String datatype, codelist CodingSchemeTypeList 701

• MeasurementUnitKind_String datatype, codelist UnitOfMeasureTypeList 702

• MessageKind_String datatype, codelist MessageTypeList 703

• PartyID_String datatype, codelist CodingSchemeTypeList 704

• Position_Integer datatype 705

• ProcessKind_String datatype, codelist ProcessTypeList 706

• PsrType_String datatype, codelist AssetTypeList 707

• Quality_String datatype, codelist QualityTypeList 708

• ReasonCode_String datatype, codelist ReasonCodeTypeList 709

• ReasonText_String datatype 710

• ResourceID_String datatype, codelist CodingSchemeTypeList 711

• Status_String datatype, codelist StatusTypeList 712

• YMDHM_DateTime datatype 713 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734

5.2.5 CriticalNetworkElement_MarketDocument XML sch ema 735

Figure 6 to Figure 11 provide the structure of the schema. 736

– of 48 –




737

Figure 6 – CriticalNetworkElement_MarketDocument XM L schema structure 1/6 738

– of 48 –




739 Figure 7 – CriticalNetworkElement_MarketDocument XM L schema structure 2/6 740

– of 48 –




741


– of 48 –




743


– of 48 –




745

Figure 10 – CriticalNetworkElement_MarketDocument X ML schema structure 5/6 746

– of 48 –




747

Figure 11 – CriticalNetworkElement_MarketDocument X ML schema structure 6/6 748

critical network element implementation guide v1r1 · – page 3 of 48 – european network of...

Documents