SHORT AND MEDIUM TERM ADEQUACY FORECASTS (SMTA ...

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

SHORT AND MEDIUM TERM ADEQUACY FORECASTS

(SMTA) IMPLEMENTATION GUIDE

2018-06-04

DOCUMENT APPROVED VERSION 1.0

– of 48 –

European Network of Transmission System Operators for Electricity

ENTSO-E SMTA data exchange implementation guide Version 1.0


1

– of 48 –




Copyright notice: 2

Copyright © ENTSO-E. All Rights Reserved. 3

This document and its whole translations may be copied and furnished to others, and derivative 4 works that comment on or otherwise explain it or assist in its implementation may be prepared, 5 copied, published and distributed, in whole or in part, without restriction of a ny kind, provided 6 that the above copyright notice and this paragraph are included on all such copies and 7 derivative works. However, this document itself may not be modified in any way, except for 8 literal and whole translation into languages other than Engl ish and under all circumstances, the 9 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 IMPLIED, INCLUDING BUT NOT 12 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 13 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 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 must 26 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 weighed 30 before implementing any behaviour described with this label. 31

• MAY: This word, or the adjective “OPTIONAL”, means that an item is truly optional. 32

mailto:[email protected]

– of 48 –




Revision History 33

Version Release Date Paragraph Comments

0 1 2018-02-15 First draft of the SMTA Implementation guide.

0 2 2018-04-04 Second draft of the SMTA IG. All changes suggested by EDI members have been applied to the guide. New results document has been defined

1 0 2018-06-04 Approved by MC

– of 48 –




CONTENTS 34

Copyright notice: ..................................................................................................................... 3 35

Revision History ...................................................................................................................... 4 36

CONTENTS ............................................................................................................................ 5 37

1 Scope .............................................................................................................................. 8 38

2 References ...................................................................................................................... 8 39

Normative references ......................................................................................... 8 40

Other references ................................................................................................ 8 41

3 Terms and definitions ...................................................................................................... 9 42

4 The SMTA Business Process ......................................................................................... 12 43

Overview.......................................................................................................... 12 44

Use Case ......................................................................................................... 13 45

Document exchange processes ........................................................................ 15 46

Overview ........................................................................................ 15 47

Submit 48 ShortMediumTermAdequacyPrognosis_MarketDocument ............... 16 49

Reply Acknowledgement ................................................................. 17 50

Send ShortMediumTermAdequacyResults_MarketDocument .......... 17 51

5 General rules for document exchange ........................................................................... 18 52

Overview.......................................................................................................... 18 53

ShortMediumTermAdequacyPrognosis_MarketDocument dependency 54 table ................................................................................................................ 19 55

ShortMediumTermAdequacyResults_MarketDocument dependency table ........ 24 56

6 Contextual and assembly models .................................................................................. 30 57

Short medium term adequacy prognosis contextual model ............................... 30 58

Overview of the model .................................................................... 30 59

IsBasedOn relationships from the European style market 60 profile ............................................................................................. 31 61

Short medium term adequacy prognosis assembly model ................................. 32 62



Detailed Short medium term adequacy prognosis assembly 66 model ............................................................................................. 33 67

Datatypes ....................................................................................... 36 68

ShortMediumTermAdequacyPrognosis_MarketDocument XML 69 schema ........................................................................................... 37 70

Short medium term adequacy results contextual .............................................. 38 71



Short medium term adequacy results assembly ................................................ 40 75



Detailed Short medium term adequacy results assembly................. 41 79

Datatypes ....................................................................................... 46 80

7 References .................................................................................................................... 48 81

– of 48 –




82

List of figures 83

Figure 1 - Use Cases ............................................................................................................ 13 84

Figure 2 - Sequence diagram for SMTA ................................................................................ 15 85

Figure 3 - Short medium term adequacy prognosis contextual model .................................... 30 86

Figure 4 - Short medium term adequacy prognosis assembly model ..................................... 32 87

Figure 5 - ShortMediumTermAdequacyPrognosis_MarketDocument schema structure .......... 37 88

Figure 6 - Short medium term adequacy results contextual ................................................... 38 89

Figure 7 - Short medium term adequacy results assembly .................................................... 40 90

Figure 8 - ShortMediumTermAdequacyResults_MarketDocument schema structure .............. 47 91

92

93

List of tables 94

Table 1 - Actor labels and descriptions ................................................................................. 13 95

Table 2 – SMTA Data Exchange ........................................................................................... 14 96

Table 3 - BusinessType Codes for 97 ShortMediumTermAdequacyPrognosis_MarketDocument ...................................................... 16 98

Table 4 - BusinessType Codes for 99 ShortMediumTermAdequacyResults_MarketDocument ......................................................... 17 100

Table 5 – Document Exchange ............................................................................................. 18 101

Table 6 - ShortMediumTermAdequacyPrognosisDocument_MarketDocument 102 dependency table ................................................................................................................. 19 103

Table 7 – TimeSeries Prognosis Document dependency table .............................................. 20 104

Table 8 – Series_Period Prognosis Document dependency table .......................................... 22 105

Table 9 – Point Prognosis Document dependency table ........................................................ 22 106

Table 10 – Percentile_Quantity Prognosis Document dependency table ............................... 23 107

Table 11 - ShortMediumTermAdequacyResults_MarketDocument dependency table ............ 24 108

Table 12 – TimeSeries Results Document dependency table ................................................ 25 109

Table 13 – Series_Period Results Document dependency table ............................................ 28 110

Table 14 - Point Results Document dependency table .......................................................... 28 111

Table 15 - IsBasedOn dependency ....................................................................................... 31 112


Table 17 - Attributes of Short medium term adequacy prognosis assembly 114 model::ShortMediumTermAdequacyPrognosis_MarketDocument .......................................... 33 115

Table 18 - Association ends of Short medium term adequacy prognosis assembly 116 model::ShortMediumTermAdequacyPrognosis_MarketDocument with other classes ............. 34 117

Table 19 - Attributes of Short medium term adequacy prognosis assembly 118 model::Percentile_Quantity ................................................................................................... 34 119

Table 20 - Attributes of Short medium term adequacy prognosis assembly model::Point ....... 34 120

Table 21 - Association ends of Short medium term adequacy prognosis assembly 121 model::Point with other classes ............................................................................................. 35 122

Table 22 - Attributes of Short medium term adequacy prognosis assembly 123 model::Series_Period ............................................................................................................ 35 124

– of 48 –




Table 23 - Association ends of Short medium term adequacy prognosis assembly 125 model::Series_Period with other classes ............................................................................... 35 126

Table 24 - Attributes of Short medium term adequacy prognosis assembly 127 model::TimeSeries ................................................................................................................ 35 128

Table 25 - Association ends of Short medium term adequacy prognosis assembly 129 model::TimeSeries with other classes ................................................................................... 36 130



Table 28 - Attributes of Short medium term adequacy results 133 assembly::ShortMediumTermAdequacyResults_MarketDocument ......................................... 41 134

Table 29 - Association ends of Short medium term adequacy results 135 assembly::ShortMediumTermAdequacyResults_MarketDocument with other classes ............ 42 136

Table 30 - Attributes of Short medium term adequacy results assembly::Point ...................... 43 137

Table 31 - Association ends of Short medium term adequacy results assembly::Point 138 with other classes ................................................................................................................. 43 139

Table 32 - Attributes of Short medium term adequacy results assembly::Reason .................. 43 140

Table 33 - Attributes of Short medium term adequacy results assembly::Series_Period ........ 44 141

Table 34 - Association ends of Short medium term adequacy results 142 assembly::Series_Period with other classes .......................................................................... 44 143

Table 35 - Attributes of Short medium term adequacy results assembly::TimeSeries ............ 44 144

Table 36 - Association ends of Short medium term adequacy results 145 assembly::TimeSeries with other classes .............................................................................. 45 146

147

– of 48 –




148

1 Scope 149

The objective of this implementation guide is to make possible for TSOs and RSCs to develop 150 an IT application to exchange information relative to Short and Medium-Term Adequacy forecast 151 process. 152

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

The implementation guide is developed for the harmonisation of the underlying data exchange 156 process 157

158

2 References 159

Normative references 160

The following documents, in whole or in part, are normatively r eferenced in this document and 161 are indispensable for its application. For dated references, only the edition cit ed applies. For 162 undated references, the latest edition of the referenced document (including any amendments) 163 applies. 164

• European style market profile (ESMP) 165

• IEC 62325-351, Framework for energy market communications – Part 351: CIM 166 European market model exchange profile 167

• IEC 62325-450, Framework for energy market communications – Part 450: Profile and 168 context modelling rules 169

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

Other references 172

• Article 81 of the Guideline on electricity transmission system operation (SO GL), 173

• Coordinated Week Ahead Adequacy Assessment SMTA Methodology v1.5 174

• BP Coordinated Week Ahead Adequacy Assessment v2.4 175

• SMTA - Cross Regional Adequacy Tool - Functional Specification v2.0 176 177

https://extra.entsoe.eu/SOC/Projects/PG%20SMTA%20Documents/Coordinated%20Week%20Ahead%20Adequacy%20Assessment%20SMTA%20Methodology%20v1.5.docx

https://extra.entsoe.eu/SOC/Projects/PG%20SMTA%20Documents/BP%20Coordinated%20Week%20Ahead%20Adequacy%20Assessmen%20v2.4.docx

– of 48 –




3 Terms and definitions 178

Week-ahead (W-1) operational period: Starts on Saturday at 00:00, ends on Friday at 24:00 179 CET/CEST time 180 181 Week-ahead operational granularity: Week Ahead values are hourly values from the Week 182 Ahead operational period. 183 184 Reference point: The dates and times for which power data are collected. Reference points 185 are characteristic enough of the entire period studied to limit the data to be collected to the data 186 at the reference points. Reference point refers to hourly values. An hourly value is a forecast 187 data foreseen at XX:30 (XX is the hour) 188 189 Remaining capacity: The remaining capacity (RC) for a TSO is the measurement of its own 190 possibility to cover its load by its available generation. The Remaining Capacity on a power 191 system is the difference between the Reliably Available Capacity and the Load. 192

Remaining capacity (RC) formula: RC = Reliably Available Capacity – Load 193 A positive RC means that a TSO has more available generation than its load. 194 In the opposite, a negative RC means its load isn’t covered by its reliably available generation. 195 If RC is null, then load and available generation are equal. 196 This item is a pragmatic indicator to define TSOs which need energy to cover their lo ad or are 197 able to export surplus of energy to help others TSOs to feed their load. 198 199 Week Ahead Remaining capacity: This represents Remaining Capacity applied to week-200 ahead operational period. 201 202 Load: Total Load, including losses without power used for energy storage, means a load equal 203 to generation on transmission and distribution grids. 204 205 Week Ahead Load forecast: This represents the load forecast value as predicted by a 206 Transmission System Operator for its control area at W-1. The W-1 load forecast represents 207 hourly average values of the load figures for the entire week. 208 209 PXX Load Forecast: The XXth percentile of load is the value in [MW] below which XX% of the 210 observations may be found at the reference point. 211 212 Week Ahead PXX Load Forecast: This represents the PXX load forecast value as predicted 213 by a system Operator for its control area at W-1. The W-1 system PXX load forecast represents 214 hourly average values of the XXth percentile of load figures for the entire week. 215 216 PXX Solar Forecast: The XXth percentile of PV Solar is the value in [MW] below which XX% 217 of the observations may be found at the reference point. 218 219 Week Ahead PXX PV Solar Forecast: This represents the PXX PV Solar forecast value as 220 predicted by a system Operator for its control area at W-1. The W-1 system PXX PV Solar 221 forecast represents hourly average values of the 5th percentile of PV Solar figures for the entire 222 week. 223 224 PXX Wind Offshore forecast: The XXth percentile of Wind Offshore is the value in [MW] below 225 which XX% of the observations may be found at the reference point. 226 227 Week Ahead PXX Wind Offshore Forecast: This represents the PXX wind offshore forecast 228 value as predicted by a system Operator for its contro l area at W-1. The W-1 system PXX wind 229 offshore forecast represents hourly average values of the XXth percentile of wind offshore 230 figures for the entire week. 231 232 PXX Wind Onshore forecast: The XXth percentile of Wind Onshore is the value in [MW] below 233 which XX% of the observations may be found at the reference point. 234 235 Week Ahead PXX Wind Onshore Forecast: This represents the PXX wind onshore forecast 236 value as predicted by a system Operator for its contro l area at W-1. The W-1 system PXX wind 237

– of 48 –




onshore forecast represents hourly average values of the XXth percentile of wind onshore 238 figures for the entire week W. 239 240 Load reduction: Load Reduction is a voluntary reduction in demand performed by a consumer 241 or a group of consumers in order to help the Balancing of the system. Load Reduction can be 242 remunerated. 243 244 Week Ahead Load reduction forecast: This represents the load reduction forecast value as 245 predicted by a Transmission System Operator for its control area at W -1. The W-1 load forecast 246 represents hourly average values of the load figures for the entire week. 247 248 Reliable Available Capacity (RAC): The RAC on a power system is the difference between 249 the Net Generating capacity (NGC) and the Unavailable Capacity. The RAC is the part of the 250 NGC that is currently available to cover the load at a reference point. 251

Reliable available capacity (RAC) formula: 252 RAC = Net Generating Capacity – Unavailable capacity 253

254 The Reliably Available Capacity definition can be applied to the hourly data needed for SMTA 255 Remaining Capacity and to different generations types. 256 257

Net Generating Capacity (NGC): Net generating capacity is the maximum electrical net active 258

power a power plant can feed-in continuously without exceeding the designed thermal limits. 259

Unavailable Capacity: This is the part of the NGC which is not reliably available to power plant 260 operators due to limitations on the output power of power plants. It consists of the Non-Usable 261 Capacity, power plants in scheduled Maintenance and Overhauls or in forced Outages or 262 reserved for System Services. 263 264 Non-Usable Capacity: Aggregates reductions of the net generating capacities due to the 265 following causes: 266

• Temporary limitation due to constraints, like power stations in mothball or test operation, heat 267

extraction for CHP's; 268

• Limitation due to fuel constraints management; 269

• Limitation reflecting the average availability of the primary energy source (e.g. reservoir level 270

for pump storage hydro units); 271

• Power stations with output power limitation due to environmental and ambient constraints; 272

• Non-available part of the wind and solar total installed capacity due to variable weather 273

conditions. 274

275

Generation in planned Maintenance and Overhauls: Aggregates scheduled unavailability of 276

generating capacity for regular inspection and maintenance. 277

278

Generation in Forced outages: Aggregates forced – i.e. not scheduled - unavailability of 279

generating capacity. 280

281

Generation reserved for system services: This capacity is required to maintain the security 282

of supply according to the operating rules of each TSO with a direct impact on adequacy. 283

Ancillary services refer to a range of functions which TSOs contract so that they can guarantee 284

system security. As system services reserve, TSOs have to consider: 285

- frequency containment reserves (FCR) (to maintain system frequency with automatic 286 and very fast responses); fast reserve 287

- frequency restoration reserves (FRRm/a) (which can provide additional energy when 288 needed) 289

- replacement reserves (RR) can be considered as an important tool for ensuring 290 adequacy 291

292 Biomass: Biomass electrical power in [MW] at the reference point. 293

– of 48 –




294 Fossil Brown coal/lignite: Fossil Brown coal/lignite electrical power in [MW] at the reference 295 point. 296 297 Coal-derived gas: Coal-derived gas electrical power in [MW] at the reference point. 298 299 Gas: Gas electrical power in [MW] at the reference point 300 301 Hard coal: Hard coal electrical power in [MW] at the reference point. 302 303 Oil: Oil electrical power in [MW] at the reference point. 304 305 Fossil oil shale: Fossil oil shale electrical power in [MW] at the reference point. 306 307 Fossil peat: Fossil peat electrical power in [MW] at the reference point. 308 309 Geothermal: Geothermal electrical power in [MW] at the reference point. 310 311 Hydro Pump storage: Pump-Storage is a hydro unit in which water can be raised by means of 312 pumps and stored to be used later for the generation of electrical energy in [MW] at the 313 reference point. 314 315 Hydro Run of the river and poundage: Hydro Run of the river and poundage electrical power 316 in [MW] at the reference point. 317 318 Hydro Water reservoir: Hydro Water reservoir electrical power in [MW] at the reference point. 319 320 Marine: Marine (wave, tidal and sea current) electrical power in [MW] at the reference point. 321 322 Nuclear: Nuclear electrical power in [MW] at the reference point. 323 324 Others Renewable: Others RES are energies from renewable non-fossil sources, namely 325 aerothermal, geothermal, hydrothermal, tidal, ocean energy, hydropower, run of river, biomass, 326 landfill gas, waste, sewage treatment plant gas and biogases in [MW] at the reference point. 327 328 PV Solar: PV Solar electrical power in [MW]at the reference point 329 330 Waste: Waste electrical power in [MW] at the reference point 331 332 Offshore Wind: Offshore wind electrical power in [MW] at the reference point. 333 334 Onshore Wind: Onshore wind electrical power in [MW] at the reference point 335 336 Others: Others are energies from fossil sources not accounted for gas, nuclear and coal, such 337 as oil, oil shades, and mixed fuels in [MW] at the reference point. 338

Must Run: The amount of output of the generators which, for various reasons, must be 339 connected to the transmission/distribution grid. Such reasons may include: network constraints 340 (overload management, voltage control), specific policies, minimum number of units needed to 341 provide system services, system inertia, subsidies, environmental causes etc 342

Force Outage Rate: A measure of the probability that a generating unit will not be available 343 due to forced outages or forced deratings. 344

345

– of 48 –




4 The SMTA Business Process 346

Overview 347

Each Transmission System Operator (TSO) shall provide to the Regional Security Coordinator (RSC) 348 the information necessary to perform the adequacy assessments in its control area: expected total load 349 and available resources of demand response, availability of power generation modules and operational 350 security limits. 351

352

Based on these hourly forecasts for next week (from D-1 until D-7), Regional Security Coordinator shall 353 perform adequacy assessments for at least the week-ahead timeframe with the aim of detecting 354 situations where a lack of adequacy is expected in any of the control areas or at regional level, 355 considering possible cross-border exchanges and operational security limits. 356

357 Following this, 358

• RSC (on a rotating basis) performs a cross-regional adequacy assessment to highlight at 359 ENTSO-E level the situations where a lack of adequacy is expected. 360

• On TSO requests, e.g. due to lack of adequacy assessed or estimation of TSOs, RSC shall 361 perform a regional adequacy assessment in the relevant adequacy coordination region and 362 shall deliver the results of the regional adequacy assessment together with the actions it 363 proposes to reduce risk to the associated TSOs. 364

365

366 High level business process 367

368

369

The current Implementation Guide focuses only on the cross regional adequacy assessment. 370

371

– of 48 –




Use Case 372

373

374

Figure 1 - Use Cases 375 376 377 Table 1 gives a list of actors involved in SMTA data exchange. 378 379

Table 1 - Actor labels and descriptions 380

Actor Label Actor Description

Data provider Data provider is responsible for providing capacity and generation or load data information

System Operator A System Operator, or any other actor on behalf a SO, who is responsible for providing load and generation forecasts

RSC The Regional Security Coordinator calculates SMTA results (Net positions, adequacy flags, interchange zones…) and send the acknowledgements and SMTA results

Information Receiver An Information receiver only receives SMTA results

381

– of 48 –




Table 2 gives a list of use cases for SMTA data exchange. 382 383

Table 2 – SMTA Data Exchange 384

Use case label Actors involved Action descriptions and assertions

Provides Capacity and Generation or Load data information

Data Provider Data Provider sends to the System Operator all the information necessary to calculate forecasts This use case is out of the scope.

Calculates week ahead total load and generation forecast, percentile 5 and 95

System Operator System Operator calculates week ahead total load and generation forecast, percentile 5 and 95 with the information received from Data Provider. This use case is out of the scope.

Submits (forecasts, ack) System Operator, RSC System Operator submits forecasts to RSC. The RSC checks submitted document. It fully accepts or rejects data received and send an acknowledgement to the System Operator. Submitting must include generation and load forecast information documents

Calculates SMTA results RSC RSC calculates SMTA results (Net positions, adequacy flags, interchange zones…) with the information received from System Operator. The calculation is performed according to the deadlines of the business process.

Sends SMTA Results RSC Once RSC has calculated the results, he sends them to the information receivers

Receives SMTA Results Information Receiver Information Receiver receives SMTA results

385

– of 48 –




Document exchange processes 386

Overview 387

The use cases are supported by the following document exchanges: 388

• Submit ShortMediumTermAdequacyPrognosis_MarketDocument 389

• Reply Acknowledgement_MarketDocument 390

• Send ShortMediumTermAdequacyResults_MarketDocument 391

Next figure shows a sequence diagram of the documents exchange processes. 392

393 Figure 2 - Sequence diagram for SMTA 394

395 396

• The above sequence diagram describes how the system operator submits week ahead 397 generation and load forecast to enable the RSC to calculate the SMTA results (Net 398 positions, adequacy flags, interchange zones…). 399

400

– of 48 –




401

Submit ShortMediumTermAdequacyPrognosis_MarketDocument 402

• First, data providers send to the SO: 403 o The Production unit existing and planned capacity, 404 o The Installed generation capacity aggregated, 405 o The Generation or load forecast information, and 406 o The Generation or load results. 407

• These data exchanges between the Data Provider and the SO are out of the scope of 408 this implementation guide. 409

• Once the SO has received these data, the SO calculates total load and generation 410 forecast percentile 5 and 95 and submits them (In an 411 ShortMediumTermAdequacyPrognosis_MarketDocument CIM format) to the RSC. 412

413 414 ShortMediumTermAdequacyPrognosis_MarketDocument consist of the time series listed below 415 in the next table. 416 417

Table 3 - BusinessType Codes for 418 ShortMediumTermAdequacyPrognosis_MarketDocument 419

Label Description Code

Load profile A time series concerning a load profile as calculated by a metered data aggregator.

A13

Available Generation The time series in question provides the available generation.

A38

Frequency containment reserve

The business being described concerns frequency containment reserve.

A95

Automatic frequency restoration reserve

The business being described concerns automatic frequency restoration reserve.

A96

Manual frequency restoration reserve

The business being described concerns manual frequency restoration reserve.

A97

Outage (OUT) Outage process: Element is out of operation due to planned maintenance or due to an unplanned/forced outage. Outage may be used as a synonym for unavailability.

B81

Must Run A time series concerning a generation that must run

B94

420 421

– of 48 –




422

Reply Acknowledgement 423

It is a syntax and business acknowledgment: When the RSC receives the forecasts, the 424 RSC checks that the technical and functional validity of the information and send an 425 acknowledgment to the TSO. The acknowledgement can be positive (A01 fully accepted) 426 or negative (A02 fully rejected). 427

428 429

Send ShortMediumTermAdequacyResults_MarketDocument 430

• Then RSC calculates Adequacy and send the results to the information receiver. 431 432

ShortMediumTermAdequacyResults_MarketDocument consist of the time series listed below in 433 the next table. 434

Table 4 - BusinessType Codes for 435 ShortMediumTermAdequacyResults_MarketDocument 436

Label Description Code

Production The nature of the business being described is production details.

A01

Load profile A time series concerning a load profile as calculated by a metered data aggregator.

A13

Net transfer capacity (NTC) Net transfer capacity as defined in the ETSO document "Definitions of Transfer Capacities in liberalised Electricity Markets" April 2001.

A27

Aggregated netted external schedule

The aggregated netted external schedules for a given border.

B63

Netted area AC position The AC position for a given area.

B64

Netted area position The AC and DC position for a given area.

B65

Load Shedding A timeseries concerning a load shedding used to avoid failure of the power system.

B99

Remaining Capacity A timeseries concerning the remaining capacity

C01

Indicator of generation capacity adequacy

Indicator of adequacy, it indicates if there is final generation remaining capacity after SMTA calculation.

C02

437

– of 48 –




5 General rules for document exchange 438

Overview 439

The document exchange processes of SMTA described in the previous chapter require sending 440 and receiving various EDI documents. The EDI documents to be used are 441

• ShortMediumTermAdequacyPrognosis_MarketDocument 442

• Acknowledgement_MarketDocument IEC62325-451-1 443

• ShortMediumTermAdequacyResults_MarketDocument 444

445 These EDI documents shall be used to carry out the communication tasks 446 447

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

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

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

451

Next table gives an overview, which EDI document shall be used to carry out the communication 452 tasks of document exchange processes (DEP). For reducing the size of the table, I am going to 453 use the next abbreviations: 454

• SMTAPD: ShortMediumTermAdequacyPrognosis_MarketDocument 455

• AMD: Acknowledgement_MarketDocument IEC62325-451-1 456

• SMTARD: ShortMediumTermAdequacyResults_MarketDocument 457

Table 5 – Document Exchange 458

DEP Chapter DEP label send/submit document

Reply document Reply conditions

4.3.2 Submit load and generation forecasts

SMTAPD AMD SMTAPD fully accepted.

Fully rejected due to errors in the SMTAPD

4.3.4 Send SMTA results

SMTARD None

459

460

– of 48 –




ShortMediumTermAdequacyPrognosis_MarketDocument dependency table 461

462

Table 6 - ShortMediumTermAdequacyPrognosisDocument_MarketDocument 463 dependency table 464

ShortMediumTermAdequacyPrognosisDocument _MarketDocument

Attributes Values Description XSD Requirements

mRID Unique ID (Max 35 characters)

Identification of the document.

Mandatory

revisionNumber Consecutive number. Pattern ([1-9]([0-9]){0,2})

Version of the document.

Mandatory

type B14: Energy prognosis document

The document type describes the principal characteristic of the document.

Mandatory

process.processType A31: Week ahead Indicates the nature of process that the document addresses.

Mandatory

sender_MarketParticipant.mRID

EIC-X code of the TSO The identification of the sender.

Mandatory

sender_MarketParticipant.marketRole.type

A04: System Operator The role of the sender.

Mandatory

receiver_MarketParticipant.mRID

EIC-V code of the SMTA IT System

The identification of the receiver.

Mandatory

receiver_MarketParticipant.marketRole.type

A44: RSC The role of the receiver.

Mandatory

createdDateTime E.G: 2018-03-23T12:04:39Z

UTC Time. Mandatory

time_Period.timeInterval E.G: <start>2018-03-16T00:00Z</start>

<end>2018-03-17T00:00Z</end>

SMTA target time interval covered by the document.

Mandatory

– of 48 –




465

Table 7 – TimeSeries Prognosis Document dependency table 466

TimeSeries



Identification of the time series

Mandatory

businessType Generation Forecasts

Load Forecasts

The exact business nature identifying the principal characteristic of time series.

If the prognosis document is going to contain Generation forecasts, you’ll have to use the business type codes under Generation Forecasts column. On the other hand, if the prognosis document is going to contain Load forecasts, you’ll have to use the business type code under Load Forecasts column.

Mandatory.

Note: It’s mandatory to use the codes specified under the column with the values for the businessType attribute.

If the sender for some reason doesn’t provide the information related with the code, then it’s not mandatory to include a Timeseries with that businessType code in the document.

A38: Available generation

A95: Frequency containment reserve

A96: Automatic frequency restoration reserve

A97: Manual frequency restoration reserve

B81: Outage (OUT)

B94: Must Run

A13: Load Profile

curveType A02: Point The type of curve being defined in the time series.

Mandatory

measurement_Unit.name MAW Name of the unit measurement.

Mandatory

domain.mRID EIC-Y Area Code Control area ID.

Mandatory

– of 48 –




mktPSRType.psrType Generation Forecasts Used as asset type: The identification of the type of asset

If the prognosis document is going to contain Generation forecasts, you’ll have to use the asset type codes under Generation Forecasts column.

Else if the prognosis document is going to contain Load forecasts (businessType code A13), is not necessary to specify here any code.

Mandatory only if the document is going to contain only generation forecasts.

Not used if the document is going to contain load forecasts.

B01: Biomass

B02: Fossil Brown coal/Lignite

B03: Fossil Coal-derived gas

B04: Fossil Gas

B05: Fossil Hard coal

B06: Fossil Oil

B07: Fossil Oil shale

B08: Fossil Peat

B09: Geothermal

B10: Hydro Pumped Storage

B11: Hydro Run-of-river and poundage

B12: Hydro Water Reservoir

B13: Marine

B14: Nuclear

B15: Other renewable

B16: Solar

B17: Waste

B18: Wind Offshore

B19: Wind Onshore

B20: Other

flowDirection.direction A01: UP

A02: DOWN

Used to characterize the direction (downward or upward) of the system services.

Mandatory only for Business Type Codes:

• A95: Frequency containment reserve

• A96: Automatic frequency restoration reserve,

– of 48 –




• A97: Manual frequency restoration reserve

467

468

Table 8 – Series_Period Prognosis Document dependency table 469

Series_Period


timeInterval E.G: <start>2018-03-16T00:00Z</start>

<end>2018-03-16T00:30Z</end>

Time interval covered by elements of Point class.

It must be included within header Time_Period.timeInterval.

Mandatory

resolution PT60M Resolution used in the Point class.

Mandatory

470

471

Table 9 – Point Prognosis Document dependency table 472

Point


position Integer value > 0

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

Mandatory

quantity Decimal value (Float)

The principal quantity identified for a point.

Mandatory

generationOutageProbability_Quantity.quantity Decimal value (Float) between 0 and 1

Generation Outage probability value.

Mandatory only for Business Type Code:

• B81: Outage

– of 48 –




473 Table 10 – Percentile_Quantity Prognosis Document dependency table 474

475

Percentile_Quantity


type 05: Percentile 05

95: Percentile 95

The description of the type of percentile.

Mandatory only for Business Type Codes:

• A13: Load Profile

• A38: Available generation


The quantity value. Mandatory only for Business Type Codes:

• A13: Load Profile

• A38: Available generation

476

477

– of 48 –




ShortMediumTermAdequacyResults_MarketDocument dependency table 478

479

Table 11 - ShortMediumTermAdequacyResults_MarketDocument dependency table 480

ShortMediumTermAdequacyResults_MarketDocument



Identification of the document.

Mandatory

revisionNumber Consecutive number. Pattern ([1-9]([0-9]){0,2})

Version of the document.

Mandatory

type B19: Reporting information market document

The document type describes the principal characteristic of the document.

Mandatory

process.processType A31: Week ahead

Indicates the nature of process that the document addresses.

Mandatory

sender_MarketParticipant.mRID EIC-V code of the SMTA IT System

The identification of the sender.

Mandatory

sender_MarketParticipant.marketRole.type

A44: RSC The role of the sender.

Mandatory

receiver_MarketParticipant.mRID EIC-X code of the TSO

The identification of the receiver.

Mandatory

receiver_MarketParticipant.marketRole.type

A04: System Operator

The role of the receiver.

Mandatory

createdDateTime E.G: 2018-03-23T12:04:39Z

UTC Time. Mandatory

time_Period.TimeInterval E.G: <start>2018-03-16T00:00Z</start>

SMTA Results target time interval covered by

Mandatory

– of 48 –




<end>2018-03-17T00:00Z</end>

the document.

Reason.code It can be used all codes in the ReasonCodeType Codelist

Indicates if the results document is correct or has errors.

Optional.

If there’s no reason, there aren’t errors

Reason.text Text Text explaining possible problem.

Optional.

481

Table 12 – TimeSeries Results Document dependency table 482

Timeseries



Identification of the time series.

Mandatory

businessType A01: Production

A13: Load profile

A27: Net transfer capacity (NTC)

B63: Aggregated netted external schedule

B64: Netted area AC position

B65: Netted area position

B99: Load Shedding

C01: Remaining Capacity

C02: Indicator of generation capacity adequacy

The exact business nature identifying the principal characteristic of time series.

Mandatory.

Note: It’s mandatory to use the codes specified under the column with the values for the businessType attribute.

If the sender for some reason doesn’t provide the information related with the code, then it’s not mandatory to include a Timeseries with that businessType code in the document.

product 8716867000016: Active Power

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

Mandatory

– of 48 –




energy, reactive power, etc.

curveType A02: Point The type of curve being defined in the time series.

Mandatory

measurement_Unit.name MAW Name of the unit measurement.

Mandatory

inDomain.mRID EIC-Y Area Code Import control area ID/ Control Area ID

Mandatory

Note: If business type code is B63 (Aggregated netted external schedule), you’ll have to introduce in this attribute the import control area EIC code.

For the other business type codes, you’ll have to introduce in this attribute the control area EIC code.

outDomain.mRID EIC-Y Area Code or

10YEU-CONT-SYNC0 : Synchronous Zone of Continental Europe EIC-Y Code

Export control area ID.

Mandatory

Note: If business type code is B63 (Aggregated netted external schedule), you’ll have to introduce in this attribute the export control area EIC code.

For the other business type codes, you’ll have to introduce in this attribute the Synchronous Zone of Continental Europe EIC code.

– of 48 –




connectingLine_RegisteredResource.mRID

EIC-T Code ID of the connecting line.


• B63: Aggregated netted external schedule

mktPSRType.psrType B01: Biomass

B02: Fossil Brown coal/Lignite

B03: Fossil Coal-derived gas

B04: Fossil Gas

B05: Fossil Hard coal

B06: Fossil Oil

B07: Fossil Oil shale

B08: Fossil Peat

B09: Geothermal

B10: Hydro Pumped Storage

B11: Hydro Run-of-river and poundage

B12: Hydro Water Reservoir

B013: Marine

B14: Nuclear

B15: Other renewable

B16: Solar

B17: Waste

B18: Wind Offshore

B19: Wind Onshore

B20: Other

Used as asset type: The identification of the type of asset.


• A01: Production


Indicates if the timseries are correct or have errors.

Optional.


– of 48 –




Reason.text It can be used all codes in the ReasonCodeType Codelist

Indicates the reason of the error of the timeseries.

Optional.


483 484

Table 13 – Series_Period Results Document dependency table 485

Timeseries


timeInterval E.G: <start>2018-03-16T00:00Z</start>

<end>2018-03-16T00:30Z</end>

Time interval covered by elements of Point class.

It must be included within header Time_Period.timeInterval.

Mandatory

resolution PT60M Resolution used in the Point class.

Mandatory

486 487

Table 14 - Point Results Document dependency table 488

Point


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

Mandatory



Mandatory

posFR_Quantity.quantity Not used Positive feasibility range.

Optional

negFR_Quantity.quantity Not used Negative feasibility range.

Optional


Indicates if the points are correct or have errors.

Optional.


– of 48 –




Reason.text It can be used all codes in the ReasonCodeType Codelist

Indicates the reason of the error of the points.

Optional.


489 490

– of 48 –




6 Contextual and assembly models 491

Short medium term adequacy prognosis contextual model 492

Overview of the model 493

Figure 3 shows the model. 494

495

Figure 3 - Short medium term adequacy prognosis contextual model 496

– of 48 –




IsBasedOn relationships from the European style market profile 497

Table 15 shows the traceability dependency of the classes used in this package towards the 498 upper level. 499

Table 15 - IsBasedOn dependency 500

Name Complete IsBasedOn Path

Domain TC57CIM::IEC62325::MarketManagement::Domain

FlowDirection TC57CIM::IEC62325::MarketManagement::FlowDirection

MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant

MarketRole TC57CIM::IEC62325::MarketCommon::MarketRole

Measure_Unit TC57CIM::IEC62325::MarketManagement::Unit

MktPSRType TC57CIM::IEC62325::MarketManagement::MktPSRType

Percentile_Quantity TC57CIM::IEC62325::MarketManagement::Quantity

Point TC57CIM::IEC62325::MarketManagement::Point

Probability_Quantity TC57CIM::IEC62325::MarketManagement::Quantity

ProcessType_Process TC57CIM::IEC62325::MarketManagement::Process

Series_Period TC57CIM::IEC62325::MarketManagement::Period

ShortMediumTermAdequacyPrognosis_MarketDocument

TC57CIM::IEC62325::MarketManagement::MarketDocument

Time_Period TC57CIM::IEC62325::MarketManagement::Period

TimeSeries TC57CIM::IEC62325::MarketManagement::TimeSeries

501

– of 48 –




Short medium term adequacy prognosis assembly model 502



505

Figure 4 - Short medium term adequacy prognosis assembly model 506

– of 48 –








Percentile_Quantity TC57CIM::IEC62325::MarketManagement::Quantity



ShortMediumTermAdequacyPrognosis_MarketDocument

TC57CIM::IEC62325::MarketManagement::MarketDocument


511

Detailed Short medium term adequacy prognosis assembly model 512

6.2.3.1 ShortMediumTermAdequacyPrognosis_MarketDocument root class 513

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

Table 17 shows all attributes of ShortMediumTermAdequacyPrognosis_MarketDocument. 516

Table 17 - Attributes of Short medium term adequacy prognosis assembly 517 model::ShortMediumTermAdequacyPrognosis_MarketDocument 518

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] processType_Process.processType

ProcessKind_String

The identification of the nature of process that the document addresses. --- The Process associated with an electronic document header that is valid for the whole document.

4 [1..1] sender_MarketParticipant.mRID

PartyID_String

The identification of a party in the energy market. --- The MarketParticipant associated with an electronic document header.

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

MarketRoleKind_String

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

6 [1..1] receiver_MarketParticipant.mRID

PartyID_String

The identification of a party in the energy market. --- The MarketParticipant associated with an electronic document header.

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



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. --- The time interval that is associated with an electronic document and which is valid for the whole document.

– of 48 –




519

Table 18 shows all association ends of 520 ShortMediumTermAdequacyPrognosis_MarketDocument with other classes. 521

Table 18 - Association ends of Short medium term adequacy prognosis assembly 522 model::ShortMediumTermAdequacyPrognosis_MarketDocument with other classes 523

Order mult. Class name / Role

Description

10 [1..*] TimeSeries

TimeSeries

The time series that is associated with an electronic document. Association Based On: Short medium term adequacy prognosis contextual model::TimeSeries.TimeSeries[1..*] ----- Short medium term adequacy prognosis contextual model::ShortMediumTermAdequacyPrognosis_MarketDocument.[]

524

6.2.3.2 Percentile_Quantity 525

The quantity attribute provides the information relative to the percentage level of quality of the 526 prognosis quantity. 527

Table 19 shows all attributes of Percentile_Quantity. 528

Table 19 - Attributes of Short medium term adequacy prognosis assembly 529 model::Percentile_Quantity 530

Order mult. Attribute name / Attribute type

Description

0 [1..1] type

String

The description of the type of the quantity.

1 [1..1] quantity

Decimal

The quantity value. The association role provides the information about what is expressed.

531

6.2.3.3 Point 532

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

Table 20 shows all attributes of Point. 534

Table 20 - Attributes of Short medium term adequacy prognosis assembly model::Point 535


0 [1..1] position

Position_Integer


1 [1..1] quantity

Decimal


2 [0..1] generationOutageProbability_Quantity.quantity

Decimal

The quantity value. The association role provides the information about what is expressed. --- The Quantity information associated with a given Point.

536

– of 48 –




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

Table 21 - Association ends of Short medium term adequacy prognosis assembly 538 model::Point with other classes 539

Order mult. Class name / Role Description

3 [0..*] Percentile_Quantity

Percentile_Quantity

The percentile quantity value provided. Association Based On: Short medium term adequacy prognosis contextual model::Point.[] ----- Short medium term adequacy prognosis contextual model::Percentile_Quantity.Percentile_Quantity[0..*]

540

6.2.3.4 Series_Period 541

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

Table 22 shows all attributes of Series_Period. 543

Table 22 - Attributes of Short medium term adequacy prognosis assembly 544 model::Series_Period 545


Description

0 [1..1] timeInterval


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.

546

Table 23 shows all association ends of Series_Period with other classes. 547

Table 23 - Association ends of Short medium term adequacy prognosis assembly 548 model::Series_Period with other classes 549


2 [1..*] Point

Point

The Point information associated with a given Series_Period.within a TimeSeries. Association Based On: Short medium term adequacy prognosis contextual model::Series_Period.[] ----- Short medium term adequacy prognosis contextual model: :Point.Point[1..*]

550

6.2.3.5 TimeSeries 551

A set of time-ordered quantities being exchanged. 552

Table 24 shows all attributes of TimeSeries. 553

Table 24 - Attributes of Short medium term adequacy prognosis assembly 554 model::TimeSeries 555


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.

2 [1..1] curveType

CurveType_String

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

– of 48 –





Description

3 [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 quantities in a TimeSeries.

4 [1..1] domain.mRID

AreaID_String

The unique identification of the domain. --- The domain associated with a TimeSeries that provides the identification of the area concerned by the prognosis.

5 [0..1] mktPSRType.psrType

PsrType_String

The coded type of a power system resource. --- The identification of the type of resource associated with a TimeSeries.

6 [0..1] flowDirection.direction

DirectionKind_String

The coded identification of the direction of energy flow. --- The flow direction associated with a TimeSeries.

556

Table 25 shows all association ends of TimeSeries with other classes. 557

Table 25 - Association ends of Short medium term adequacy prognosis assembly 558 model::TimeSeries with other classes 559


Description

7 [1..*] Series_Period

Series_Period

The time interval and resolution for a period associated with a TimeSeries. Association Based On: Short medium term adequacy prognosis contextual model::TimeSeries.[] ----- Short medium term adequacy prognosis contextual model::Series_Period.Series_Period[1..*]

560

Datatypes 561

The list of datatypes used for the Short medium term adequacy prognosis assembly model is 562 as follows: 563

• ESMP_DateTimeInterval compound 564

• AreaID_String datatype, codelist CodingSchemeTypeList 565

• BusinessKind_String datatype, codelist BusinessTypeList 566

• CurveType_String datatype, codelist CurveTypeList 567

• DirectionKind_String datatype, codelist DirectionTypeList 568

• ESMP_DateTime datatype 569

• ESMPVersion_String datatype 570

• ID_String datatype 571

• MarketRoleKind_String datatype, codelist RoleTypeList 572

• MeasurementUnitKind_String datatype, codelist UnitOfMeasureTypeList 573

• MessageKind_String datatype, codelist MessageTypeList 574

• PartyID_String datatype, codelist CodingSchemeTypeList 575

• Position_Integer datatype 576

• ProcessKind_String datatype, codelist ProcessTypeList 577

• PsrType_String datatype, codelist AssetTypeList 578

• YMDHM_DateTime datatype 579 580

– of 48 –




ShortMediumTermAdequacyPrognosis_MarketDocument XML schema 581

The XSD file to be used with this implementation guide is : 582

urn:iec62325.351:tc57wg16:451-n:smtaprognosisdocument:1:0 583

584

Figure 5 - ShortMediumTermAdequacyPrognosis_MarketDocument schema structure 585 586

– of 48 –




Short medium term adequacy results contextual 587



590

Figure 6 - Short medium term adequacy results contextual 591

– of 48 –








ConnectingLine_RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource

Domain TC57CIM::IEC62325::MarketManagement::Domain

MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketParticipant

MarketRole TC57CIM::IEC62325::MarketCommon::MarketRole

Measure_Unit TC57CIM::IEC62325::MarketManagement::Unit

MktPSRType TC57CIM::IEC62325::MarketManagement::MktPSRType


Process TC57CIM::IEC62325::MarketManagement::Process

Quantity TC57CIM::IEC62325::MarketManagement::Quantity

Reason TC57CIM::IEC62325::MarketManagement::Reason


ShortMediumTermAdequacyResults_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument

Time_Period TC57CIM::IEC62325::MarketManagement::Period


596

– of 48 –




Short medium term adequacy results assembly 597



600

Figure 7 - Short medium term adequacy results assembly 601

– of 48 –









Reason TC57CIM::IEC62325::MarketManagement::Reason


ShortMediumTermAdequacyResults_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument


606

Detailed Short medium term adequacy results assembly 607

6.4.3.1 ShortMediumTermAdequacyResults_MarketDocument root class 608

An electronic document containing the information necessary to satis fy the requirements of a 609 given business process. 610

Table 28 shows all attributes of ShortMediumTermAdequacyResults_MarketDocument. 611

Table 28 - Attributes of Short medium term adequacy results 612 assembly::ShortMediumTermAdequacyResults_MarketDocument 613


0 [1..1] mRID

ID_String

The unique identification of the document being exchanged within a business process flow. In the ESMP context, the "model authority" is defined as a party (originator of the exchange) that provides an identification in the context of a business exchange such as document identification, ... Master resource identifier issued by a model authority. The mRID is globally unique within an exchange context. Global uniqueness is easily achieved by using a UUID for the mRID. It is strongly recommended to do this. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.

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 associated with an electronic document header that is valid for the whole document.

4 [1..1] sender_MarketParticipant.mRID

PartyID_String

The identification of a party in the energy market. In the ESMP context, the "model authority" is defined as an authorized issuing office that provides an agreed identification coding scheme for market participant, domain, measurement point, resources (generator, lines, substations, etc.) identification. Master resource identifier issued by a model authority. The mRID is globally unique within an exchange context. Global uniqueness is easily achieved by using a UUID for the mRID. It is strongly recommended to do this. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. --- The MarketParticipant associated with an electronic document header.

– of 48 –





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



6 [1..1] receiver_MarketParticipant.mRID

PartyID_String

The identification of a party in the energy market. In the ESMP context, the "model authority" is defined as an authorized issuing office that provides an agreed identification coding scheme for market participant, domain, measurement point, resources (generator, lines, substations, etc.) identification. Master resource identifier issued by a model authority. The mRID is globally unique within an exchange context. Global uniqueness is easily achieved by using a UUID for the mRID. It is strongly recommended to do this. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. --- The MarketParticipant associated with an electronic document header.

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



8 [1..1] createdDateTime

ESMP_DateTime

The date and time of the creation of the document.

9 [1..1] time_Period.timeInterval


The start and end date and time for a given interval. --- The time interval that is associated with an electronic document and which is valid for the whole document.

614

Table 29 shows all association ends of ShortMediumTermAdequacyResults_MarketDocument 615 with other classes. 616

Table 29 - Association ends of Short medium term adequacy results 617 assembly::ShortMediumTermAdequacyResults_MarketDocument with other classes 618


Description

10 [0..*] TimeSeries

TimeSeries

The time series that is associated with an electronic document. Association Based On: Short medium term adequacy results contextual::TimeSeries.TimeSeries[0..*] ----- Short medium term adequacy results contextual::ShortMediumTermAdequacyResults_MarketDocument.[]

11 [0..*] Reason

Reason

The Reason associated with the electronic document header providing different motivations for the creation of the document. Association Based On: Short medium term adequacy results contextual::Reason.Reason[0..*] ----- Short medium term adequacy results contextual::ShortMediumTermAdequacyResults_MarketDocument.[]

619

– of 48 –




6.4.3.2 Point 620

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

Table 30 shows all attributes of Point. 622

Table 30 - Attributes of Short medium term adequacy results assembly::Point 623


Description

0 [1..1] position

Position_Integer


1 [1..1] quantity

Decimal


2 [0..1] posFR_Quantity.quantity

Decimal


3 [0..1] negFR_Quantity.quantity

Decimal


624

Table 31 shows all association ends of Point with other classes. 625

Table 31 - Association ends of Short medium term adequacy results assembly::Point 626 with other classes 627


4 [0..*] Reason

Reason

The Reason information associated with a Point providing motivation information. Association Based On: Short medium term adequacy results contextual::Reason.Reason[0..*] ----- Short medium term adequacy results contextual::Point.[]

628

6.4.3.3 Reason 629

The motivation of an act. 630

Table 32 shows all attributes of Reason. 631

Table 32 - Attributes of Short medium term adequacy results assembly::Reason 632


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.

633

– of 48 –




6.4.3.4 Series_Period 634

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

Table 33 shows all attributes of Series_Period. 636

Table 33 - Attributes of Short medium term adequacy results assembly::Series_Period 637


Description

0 [1..1] timeInterval


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.

638

Table 34 shows all association ends of Series_Period with other classes. 639

Table 34 - Association ends of Short medium term adequacy results 640 assembly::Series_Period with other classes 641


2 [1..*] Point

Point

The Point information associated with a given Series_Period.within a TimeSeries. Association Based On: Short medium term adequacy results contextual::Point.Point[1..*] ----- Short medium term adequacy results contextual::Series_Period.[]

642

6.4.3.5 TimeSeries 643

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

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

Table 35 shows all attributes of TimeSeries. 647

Table 35 - Attributes of Short medium term adequacy results assembly::TimeSeries 648


0 [1..1] mRID

ID_String

A unique identification of the time series. In the ESMP context, the "model authority" is defined as a party (originator of the exchange) that provides a unique identification in the context of a business exchange such as time series identification, bid identification, ... Master resource identifier issued by a model authority. The mRID is globally unique within an exchange context. Global uniqueness is easily achieved by using a UUID for the mRID. It is strongly recommended to do this. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements.

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 [1..1] curveType

CurveType_String

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

4 [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 quantities in a TimeSeries.

– of 48 –





5 [0..1] in_Domain.mRID

AreaID_String

The unique identification of the domain. In the ESMP context, the "model authority" is defined as an authorized issuing office that provides an agreed identification coding scheme for market participant, domain, measurement point, resources (generator, lines, substations, etc.) identification. Master resource identifier issued by a model authority. The mRID is globally unique within an exchange context. Global uniqueness is easily achieved by using a UUID for the mRID. It is strongly recommended to do this. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. --- The domain associated with a TimeSeries.

6 [0..1] out_Domain.mRID

AreaID_String

The unique identification of the domain. In the ESMP context, the "model authority" is defined as an authorized issuing office that provides an agreed identification coding scheme for market participant, domain, measurement point, resources (generator, lines, substations, etc.) identification. Master resource identifier issued by a model authority. The mRID is globally unique within an exchange context. Global uniqueness is easily achieved by using a UUID for the mRID. It is strongly recommended to do this. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. --- The domain associated with a TimeSeries.

7 [0..1] connectingLine_RegisteredResource.mRID

ResourceID_String

The unique identification of a resource. In the ESMP context, the "model authority" is defined as an authorized issuing office that provides an agreed identification coding scheme for market participant, domain, measurement point, resources (generator, lines, substations, etc.) identification. Master resource identifier issued by a model authority. The mRID is globally unique within an exchange context. Global uniqueness is easily achieved by using a UUID for the mRID. It is strongly recommended to do this. For CIMXML data files in RDF syntax, the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. --- The identification of a resource associated with a TimeSeries.

8 [0..1] mktPSRType.psrType

PsrType_String

The coded type of a power system resource. --- The identification of the type of resource associated with a TimeSeries.

649

Table 36 shows all association ends of TimeSeries with other classes. 650

Table 36 - Association ends of Short medium term adequacy results 651 assembly::TimeSeries with other classes 652


Description

9 [1..*] Series_Period

Period

The time interval and resolution for a period associated with a TimeSeries. Association Based On: Short medium term adequacy results contextual::Series_Period.Period[1..*] ----- Short medium term adequacy results contextual::TimeSeries.[]

10 [0..*] Reason

Reason

The reason information associated with a TimeSeries providing motivation information. Association Based On: Short medium term adequacy results contextual::Reason.Reason[0..*] ----- Short medium term adequacy results contextual::TimeSeries.[]

– of 48 –




653

Datatypes 654

The list of datatypes used for the Short medium term adequacy results assembly is as follows: 655

• ESMP_DateTimeInterval compound 656

• AreaID_String datatype, codelist CodingSchemeTypeList 657

• BusinessKind_String datatype, codelist BusinessTypeList 658

• CurveType_String datatype, codelist CurveTypeList 659

• EnergyProductKind_String datatype, codelist EnergyProductTypeList 660

• ESMP_DateTime datatype 661

• ESMPVersion_String datatype 662

• ID_String datatype 663

• MarketRoleKind_String datatype, codelist RoleTypeList 664

• MeasurementUnitKind_String datatype, codelist UnitOfMeasureTypeList 665

• MessageKind_String datatype, codelist MessageTypeList 666

• PartyID_String datatype, codelist CodingSchemeTypeList 667

• Position_Integer datatype 668

• ProcessKind_String datatype, codelist ProcessTypeList 669

• PsrType_String datatype, codelist AssetTypeList 670

• ReasonCode_String datatype, codelist ReasonCodeTypeList 671

• ReasonText_String datatype 672

• ResourceID_String datatype, codelist CodingSchemeTypeList 673

• YMDHM_DateTime datatype 674 675

– of 48 –




ShortMediumTermAdequacyResults_MarketDocument XML schema 676

The XSD file to be used with this implementation guide is : 677

urn:iec62325.351:tc57wg16:451-n:smtaresultsdocument:1:0 678

679

Figure 8 - ShortMediumTermAdequacyResults_MarketDocument schema structure 680 681

– of 48 –




7 References 682

[1] Coordinated Week Ahead Adequacy Assessment SMTA Methodology 683

[2] Coordinated Short and Medium Term Adequacy Assessment High Level Business Process 684

[3] Acknowledgement_MarketDocument (AMD) IEC 62325-451-1 685

SHORT AND MEDIUM TERM ADEQUACY FORECASTS (SMTA ...

Documents

Transcript of SHORT AND MEDIUM TERM ADEQUACY FORECASTS (SMTA ...