IMPLEMENTATION GUIDE

Transcription

1 ENTSO-E CRITICAL NETWORK ELEMENT DRAFT DOCUMENT VERSION 1.1

2 2 Copyright notice: Copyright ENTSO-E. All Rights Reserved. This document and its whole translations may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, except for literal and whole translation into languages other than English and under all circumstances, the copyright notice or references to ENTSO-E may not be removed. This document and the information contained herein is provided on an "as is" basis. ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. This document is maintained by the ENTSO-E WG EDI. Comments or remarks are to be provided at EDI.Library@entsoe.eu NOTE CONCERNING WORDING USED IN THIS DOCUMENT The force of the following words is modified by the requirement level of the document in which they are used. SHALL: This word, or the terms REQUIRED or MUST, means that the definition is an absolute requirement of the specification. SHALL NOT: This phrase, or the phrase MUST NOT, means that the definition is an absolute prohibition of the specification. SHOULD: This word, or the adjective RECOMMENDED, means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications shall be understood and carefully weighed before choosing a different course. SHOULD NOT: This phrase, or the phrase NOT RECOMMENDED, means that there may exist valid reasons in particular circumstances when the particular behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label. MAY: This word, or the adjective OPTIONAL, means that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.). Page 2 of 48

3 40 Revision History Version Release Date Comments Initial release Review by WG EDI and PT CGM Following the maintenance request from EMFIP, change to the UML model to enable anonymous publication. Page 3 of 48

4 42 CONTENTS Copyright notice:... 2 INTRODUCTION Scope Normative references Terms and definitions The critical network element calculation and publication process Overall business context Critical network elements determination and publication Flow based domain determination and publication Business rules for the critical network element determination process General rules Dependencies governing the CriticalNetworkElement_MarketDocument Contextual and assembly models CriticalNetworkElement contextual model Overview of the model IsBasedOn relationships from the European style market profile CriticalNetworkElement assembly model Overview of the model IsBasedOn relationships from the European style market profile Detailed CriticalNetworkElement assembly model Datatypes CriticalNetworkElement_MarketDocument XML schema List of figures Figure 1 Use case of the critical network elements process Figure 2 Critical network elements determination and publication Figure 3 Flow based domain determination and publication Figure 4 CriticalNetworkElement contextual model Figure 5 CriticalNetworkElement assembly model Figure 6 CriticalNetworkElement_MarketDocument XML schema structure 1/ Figure 7 CriticalNetworkElement_MarketDocument XML schema structure 2/ Figure 8 CriticalNetworkElement_MarketDocument XML schema structure 3/ Figure 9 CriticalNetworkElement_MarketDocument XML schema structure 4/ Figure 10 CriticalNetworkElement_MarketDocument XML schema structure 5/ Figure 11 CriticalNetworkElement_MarketDocument XML schema structure 6/ List of tables Table 1 Flow based Domain dependency Table 2 Flow based Publication dependency Page 4 of 48

5 Table 3 Flow based Market Impact Publication dependency Table 4 NTC Coordinated Determination dependency Table 5 Critical Network Element Publication dependency Table 6 Critical Network Element Market Impact Publication dependency Table 1 IsBasedOn dependency Table 8 IsBasedOn dependency Table 9 Attributes of CriticalNetworkElement assembly model::criticalnetworkelement_marketdocument Table 10 Association ends of CriticalNetworkElement assembly model::criticalnetworkelement_marketdocument with other classes Table 11 Attributes of CriticalNetworkElement assembly model::analog Table 12 Association ends of CriticalNetworkElement assembly model::analog with other classes Table 13 Attributes of CriticalNetworkElement assembly model::analogvalue Table 14 Attributes of CriticalNetworkElement assembly model::constraint_timeseries Table 15 Association ends of CriticalNetworkElement assembly model::constraint_timeseries with other classes Table 16 Attributes of CriticalNetworkElement assembly model::monitored_registeredresource Table 17 Association ends of CriticalNetworkElement assembly model::monitored_registeredresource with other classes Table 18 Attributes of CriticalNetworkElement assembly model::outage_registeredresource Table 19 Attributes of CriticalNetworkElement assembly model::party_marketparticipant Table 20 Attributes of CriticalNetworkElement assembly model::point Table 21 Association ends of CriticalNetworkElement assembly model::point with other classes Table 22 Attributes of CriticalNetworkElement assembly model::ptdf_domain Table 23 Attributes of CriticalNetworkElement assembly model::reason Table 24 Attributes of CriticalNetworkElement assembly model::remedialaction_registeredresource Table 25 Attributes of CriticalNetworkElement assembly model::series_period Table 26 Association ends of CriticalNetworkElement assembly model::series_period with other classes Table 27 Attributes of CriticalNetworkElement assembly model::timeseries Table 28 Association ends of CriticalNetworkElement assembly model::timeseries with other classes Page 5 of 48

6 125 INTRODUCTION This document is drafted based on IEC series. In particular, the IEC methodology was applied to develop the conceptual and assembly models. 1 Scope The objective of this implementation guide is to make it possible for software vendors to develop an IT application for market players to exchange information relative to critical network elements used for interconnection capacity determination process. The implementation guide is one of the building blocks for using UML (Unified Modelling Language) based techniques in defining processes and messages for interchange between actors in the electrical industry in Europe. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. IEC TS , Energy management system application program interface (EMS-API) Part 2: Glossary IEC , Framework for energy market communications Part 301: Common information model (CIM) extensions for markets IEC , Framework for energy market communications Part 351: CIM European market model exchange profile IEC , Framework for energy market communications Part 450: Profile and context modeling rules IEC , Framework for energy market communications Part 451-1: Acknowledgement business process and contextual model for CIM European market IEC , Framework for energy market communications Part 451-3: ENTSO-E Capacity Allocation and Nomination business process and contextual model for CIM European market 3 Terms and definitions 3.1 constraint situation It is a network configuration, corresponding either to the expected nominal state, or to an hypothetical degraded state where one or several contingencies occur. In both cases, associated remedial actions can be included in the network configuration. 3.2 critical network element A network element either within a bidding zone or between bidding zones taken into account in the capacity calculation process, limiting the amount of power that can be exchanged. Depending on the chosen implementation, there may be only one or several critical network elements which will be monitored in a given constraint situation. 3.3 final adjusted margin value FAV This is the amount of MW that is manually added or subtracted to the capacity of the critical network element. A negative value for FAV simulates the effect of an additional margin due to Page 6 of 48

7 complex remedial actions which cannot be modelled and so calculated in the flow based parameter calculation. A positive value for FAV, as a consequence of the verification phase of the flow based domain, leads to the need to reduce the margin on one or more critical network elements for system security reasons. 3.4 flow This is the computed physical flow, resulting from a load flow calculation, corresponding to the critical network element in the constraint situation ("N Situation", N-1 Situation...) after the capacity calculation. The flow is expressed in A, %, or MW. 3.5 flow based remaining available margin RAM This is the remaining available margin (RAM) for one critical network element in a constraint situation. This is the amount of MW or A that is left for the limiting element in a computed constraint situation, i.e. the amount that can be traded or used. 3.6 flow based study domain This is the area for which the flow based study is carried out. 3.7 flow reliability margin This is the flow reliability margin for a given critical network element in each considered constraint situation. The amount of MW or A that is reserved for this critical network element and shall not be used for the computed outage situation, in order to secure the power network. 3.8 long term allocation margin This is the amount of MW that is added to the capacity of the critical network element in order to automatically include the long term allocation domain into the flow based domain. 3.9 market coupling domain This is the market coupling area or a part of the market coupling area for which the social welfare impact due to the critical network element is computed monitored registered resource This is the critical network element of the power network in the constraint situation. Some analog measurements are of interest in order to provide information about the limitation and the physical impact on this element in such a constraint situation outage registered resource This is one of the network elements which are in outage for the studied constraint situation power transfer distribution factor This is a factor (PTDF) representing the impact of 1 MW variation of the net position of the corresponding bidding zone on the critical network element PTDF domain This is a bidding zone of the market coupling region which may be impacted by the critical network element remedial action registered resource This is one of the network element on which remedial action are carried out to improve the constraint situation. Those elements are used to alleviate the constraints induced by the Page 7 of 48

8 constraint situation. The remedial actions may be identified as automatic, preventive or curative. The type of the remedial action includes generation, load and/or topology changes shadow price This is the price variation of the market welfare for the variation of 1 MW or A on this particular critical network element. This identifies the impacts of the limiting element on the market coupling welfare spanning margin value SMV This is the margin that is taken into account when spanning is applied. SMV is an historical based parameter which specifies the amount of MW that reduces the RAM when spanning is applied. 236 Page 8 of 48

9 The critical network element calculation and publication process 4.1. Overall business context The business process described in this document is related to the determination of the critical network elements and their publication for capacity allocation purposes. The critical network elements determination process is based on a set of inputs data that are out of the scope of this document. The focus is put on the results of the critical network elements calculation which is provided to TSOs for operational and publication purposes and market operator, such as power exchanges (PXs), for market coupling allocation process. This document describes for the flow based process or the capacity coordinated determination process the necessary set of results on the critical network elements. The critical network elements are determined based on a set of operational input data which are out of the scope of this document, such as: DACF D-2CF GSK Available preventive remedial actions Potential outage cases Those operational input data are called network data in this document. In a first step the input data are given in individual models; in a second step they will respect the Common Grid Model (CGM). These steps are the identified use cases for the critical network elements determination process and are to be carried out by the TSOs on day ahead (D-1). Figure 1 provides the use case for the critical network element process. Each TSO sends firstly their network data to the capacity coordinator. The data that are sent are out of the scope of this document as considered of operational concerns. Based on the network data of all the TSOs, the capacity coordinator performs a merge of these data and computes the critical network elements. This part of the process refers directly to guidelines CACM and CGMES. The calculation basically enables to identify which are the most important limiting elements of the power network in several studied constraint situation, i.e. outages. Once the calculation performed, the capacity coordinator provides the TSOs with a list of critical network elements for internal process. The critical network elements are provided in day ahead for a specific period of time. The critical network elements enable to define then the net transfer capacity (NTC) on day ahead to be used for daily allocation process. This part of the process refers directly to IEC business process. The critical network elements may be provided, complemented by flow based parameters in case flow based calculation is run instead of NTC determination. Those flow based parameters will include the influence of the critical network elements on the market coupling process. The critical network elements with flow based parameters define the so-called flow based domain. The details of the flow based domain calculation process are out of the scope of this document. This flow based domain is provided by the capacity coordinator to the TSOs. An anonymous version of the flow based domain (without identifying precisely the limiting elements of the network) is sent to the market operator in order to be used for the market coupling calculation process. Page 9 of 48

10 uc Cr itica lnetwor kelement Document use ca se Send TSO network data Out of the Scope of this document Determine the critical networ k elements :Transmission system operator Compute the net transfer capacity :Capacity coor dinator Determine the flow based doma in Publish the critical networ k elements Provide market coupling r esults Publish the impact of critical network elements on the market :Market operator :Market information aggr egator Figure 1 Use case of the critical network elements process The market coupling process itself is out of the scope of this document. However the market coupling results enable to identify the impact of the previously identified critical network elements on the social welfare of the flow based market coupling area. This impact is identified by the shadow price of the critical network element. Finally, the shadow prices are published with the flow based domain to the market information aggregator. In case of NTC determination process, the critical network elements which effectively constrained the allocation market position (market coupling or explication auction) are published to the market information aggregator. 4.2 Critical network elements determination and publication In a context of regional coordinated capacity calculation, it is of interest to perform a capacity calculation on a common grid model (merge of each TSO network model) to identify the main Page 10 of 48

11 critical network elements of the region which will limit the net transfer capacity for the allocation market. The details of such a process are out of the scope of this document and those are summarized by the two steps: Sending of TSOs network data to the capacity coordinator Critical network elements determination Once the critical network elements determination process is performed in day ahead, the capacity coordinator sends the list of identified critical network elements that constraint the power network and induces congestions. Those critical network elements are identified for one specific point of time hour of a delivery day. There may be one or several constraint situations identified on the power network for one specific point of time. Per constraint situation, one or several critical network elements may be identified. It is of TSOs responsibility to monitor each critical network element. In this condition, threshold values are provided as monitored analog measurements of the monitored elements for TSOs internal process. The net transfer capacity (NTC) will be calculated based on the critical network elements determined by the capacity coordinator. The related oriented border associated to the critical network elements calculation is provided in the critical network elements results. This information is needed as an input for NTC determination. For instance, the critical network elements identified in the calculation of the full export situation (from France to Italy) will be used as inputs for NTC calculation on France-to-Italy border. The details of the NTC calculation are out of the scope of this document. The publication of NTC is out of the scope this document since for NTC, as described in IEC , the information is provided by using Capacity_MarketDocument. The critical network elements results are published by the TSOs to the market information aggregator without the monitored measurement information. The NTC is then used for capacity allocation as described within IEC After allocation, the critical network elements which effectively impacted the market position are sent to the market information aggregator. Figure 2 provides the sequence diagram for the critical network elements determination and publication process. The capacity coordinator sends the list of critical network elements to TSOs by using the CriticalNetworkElement_MarketDocument. The TSOs are using the CriticalNetworkElement_MarketDocument to publish the critical network elements. The information about the limiting TSO and the location of the critical network element is also of publication interest. Page 11 of 48

12 sd Cr itical Networ k Elements deter mination and publication Out of the Scope of this document Transmission system operator TSO network data() Capacity coordinator Market information aggregator Critical Network Elements (CriticalNetworkElement_MarketDocument) Critical Network Elements determination() Critical Network Elements (CriticalNetworkElement_MarketDocument) NTC Calculation() NTC(IEC Capacity_MarketDocument) Capacity Allocation (IEC ) Critical Network Elements Market Impact (CriticalNetworkElement_MarketDocument) (from Roles) (from Roles) (from Roles) Figure 2 Critical network elements determination and publication 4.3 Flow based domain determination and publication In the context of flow based capacity calculation, once the critical network elements determination process is performed in day ahead, the capacity coordinator sends the defined flow based domain to TSOs. The flow based domain identifies the domain where the power system is safely operated depending upon commercial exchanged flows and congestion management on the borders. The flow based domain is identified per point of time by a set of critical network elements influencing the allocation market with given weighting factors defined by the PTDF factors and their associated RAM. Those critical network elements are identified for one specific point of time of a delivery day. There may be one or several constraint situations identified on the power network for one specific point of time. Per constraint situation, only one critical network element is identified by the flow based calculation. It is of TSOs responsibility to monitor each critical network element. In this condition, threshold values are provided as monitored analog measurements of the monitored elements for TSOs internal process. The flow based domain is sent by the capacity coordinator to the market operator to take into account the critical network elements with their PTDFs and RAM in the market coupling calculation process. In this case, the critical network elements are sent in an anonymous way and the analog measurements are not sent. The same flow based domain result as for the market operator is also sent to the market information aggregator. Page 12 of 48

13 Then, once the market coupling process is performed and the calculation done, the impact of each critical network element of the flow based domain on the social welfare of the flow based market coupling region is available. This impact is published as the shadow price of the critical network elements of the flow based domain. Figure 3 provides the sequence diagram for the critical network elements determination and publication process. sd Flow based domain deter mination and publication Out of scope of this document Transmission system operator Capacity coordinator Market operator Market information aggregator TSO network data() Flow based domain (CriticalNetworkElement_MarketDocument) Critical Network Elements determination() Flow based domain (CriticalNetworkElement_MarketDocument) Flow based domain (CriticalNetworkElement_MarketDocument) Market coupling results() Run market coupling() Flow based market impact(criticalnetworkelement_marketdocument) (from Roles) (from Roles) (from Roles) (from Roles) Figure 3 Flow based domain determination and publication The capacity coordinator sends the flow based domain to TSOs by using the CriticalNetworkElement_MarketDocument. The TSOs are using the CriticalNetworkElement_MarketDocument to publish the flow based domain. The information about the limiting TSO and the location of the critical network element is also of a publication interest. When the market coupling process is over, the TSOs are using the CriticalNetworkElement_MarketDocument to publish the flow based domain with the shadow prices. 4.4 Business rules for the critical network element determination process General rules The generic rules defined in IEC applied to all the documents described in this part. In particular, IEC describes the concept of curve type that is to be used to define the pattern of the critical network elements for a day. For each electronic data interchange defined in this document, an application acknowledgement is required as defined in IEC When a document is received, it shall be checked at the application level to ensure that there are no faults in it that could prevent its normal processing. After this check, an Page 13 of 48

14 acknowledgement document, as defined in IEC , shall be generated either accepting in its entirety the document in question or rejecting it Dependencies governing the CriticalNetworkElement_MarketDocument The following rules applied to the CriticalNetworkElement_MarketDocument: A CriticalNetworkElement_MarketDocument may contain for a specific position several Constraint_TimeSeries. In case of NTC Determination process, the TimeSeries of the CriticalNetworkElement_MarketDocument provides the main related oriented border of the calculation study used for NTC calculation: In_Domain.mRID: the area of the related oriented border study where the energy flows into. Out_Domain.mRID: the area of the related oriented border study where the energy comes from. There are two types of Constraint_TimeSeries. The BusinessType is used to distinguish between both types: The studied constraint situation identified by a constraint situation and the associated critical network elements: The Constraint_TimeSeries contains: A mrid which identifies a constraint situation. If a business process used a coding scheme to identify the constraint situation (for example a Critical Network Element and Critical Outage (CBCO) code), the mrid can bring this information. A BusinessType which identifies the case: Critical Network Element, Red flag, etc. A Name which maybe use to provide the outage situation name. A list of Outage_RegisteredResource which identifies the network elements in outage for this studied case: There are as many Outage_RegisteredResource as network elements in outage in the studied case. In case of N Situation studied case, there is no Outage_RegisteredResource present in the Constraint_TimeSeries. The Outage_RegisteredResource is identified by its EIC code. The name of the Outgage_RegisteredResource may be provided. The location of the Outage_RegisteredResource is provided by In_Domain and Out_Domain, using EIC code. For orientation purpose, In_AggregatedNode and Out_AggregatedNode, using EIC code, may be used. A list of RemedialAction_RegisteredResource which identifies the network elements on which remedial action are performed to relieve the constraints for the studied case: There are as many RemedialAction_RegisteredResource as network elements are used to relieve the constraint in the studied case. In case no remedial action is performed, there is no RemedialAction_RegisteredResource present in the Constraint_TimeSeries. The RemedialAction_RegisteredResource is identified by its EIC code. The name of the RemedialAction_RegisteredResource may be provided. The location of the RemedialAction_RegisteredResource is provided by In_Domain and Out_Domain, using EIC code. Page 14 of 48

15 For orientation purpose, In_AggregatedNode and Out_AggregatedNode, using EIC code, may be used. The remedial action type shall be provided as Tieline, Line, Generation, Load, Redispatching, etc. The remedial action status shall be provided as automatic, preventive or curative action. A list of Monitored_RegisteredResource which identifies the limiting network elements (so-called Critical network elements) in the studied case: There are as many Monitored_RegisteredResource as critical network elements identified in the studied case. There is at least one Monitored_RegisteredResource present in the Constraint_TimeSeries. The Monitored_RegisteredResource is identified by its EIC code. The name of the Monitored_RegisteredResource may be provided. The location of the Monitored_RegisteredResource is provided by In_Domain and Out_Domain, using EIC code. For orientation purpose, In_AggregatedNode and Out_AggregatedNode, using EIC code, may be used. A list of measurements of interest for the Monitored_RegisteredResource may be provided through the usage of the class Analog. In case of Flow Based, a set of flow Based Parameters may be provided for the Monitored_RegisteredResource. In this case: The Flow Based Remedial available Margin shall be provided for the studied flow based Studied Area (using EIC code). The shadow price may be provided for the market coupling area (using EIC code). A set of PTDF factors shall be provided. One PTDF factor shall be provided per bidding zone (using EIC code). The external constraint identified by a global capacity constraint as a total transfer capacity (TTC) or a net position limitation (bidding zone import or export) for instance. The Constraint_TimeSeries contains: A BusinessType which identifies the External Constraint. The external constraint may be of TTC (Total Transfer Capacity), NTC (Net Transfer Capacity), ATC min, net position, etc. A Name may be used to provide the external constraint name. The external constraint quantity shall be used to provide the quantity BusinessType-related constraint. In case of external Constraint_TimeSeries, the Outage_RegisteredResource, RemedialAction_RegisteredResource, Monitored_RegisteredResource classes shall not be used. The class Analog shall be used to provide the measurements of interest for the Monitored_RegisteredResource of the Constraint_TimeSeries: There are as many Analog as measurements of interest for the Monitored_RegisteredResource. For one Monitored_RegisteredResource, the Analog contains: A measurementtype which defines the nature of the monitored measurement. The list of authorized measurementtype is: flow, maximum flow, reference flow, flow reliability margin, spanning margin value, long term allocation margin,final adjustment margin value. Page 15 of 48

16 A unitsymbol which identifies the unit of the measurement. A positiveflowin which identifies on which direction the Monitored_RegisteredResource element is monitored. For each measurement, the values shall be provided by AnalogValues: There are as many AnalogValues as measured occurrence of the Analog measurement. For each AnalogValues: The value of the measurement shall be provided. The constraint duration of such a measurement may be provided. The condition description of such a measurement may be provided as Before Outage, After Outage, After curative action, etc. Two types of document are identified depending on the two processes of critical network elements calculation: The critical network elements determination document that is used for a coordinated NTC calculation process. The flow based domain document that replaces the ATC in usual IEC process and is used directly for Flow Based capacity allocation. Specific types of document for publication are also identified: The critical network elements publication which is used to provide only relevant information to market information aggregator. The critical network elements market impact publication which is used to provide the critical network elements which effectively impacted the allocation market. The flow based domain publication which is used to publish only the relevant information to market information aggregator. The flow based market impact document which is used to publish the shadow prices of the critical network elements to market information aggregator. As defined previously, there shall be at least one monitored element per Constraint_TimeSeries of constraint situation type: For flow based, only one critical network element shall be identified per constraint situation. For coordinated NTC calculation, several critical network elements may be identified per constraint situation. In case any constraint situation can be provided for one specific position of time, the point shall not provide any Constraint_TimeSeries: The reason class associated to the class Point shall be used to inform that no constraint situation is provided. In case any constraint situation can be provided for the whole delivery period, document shall not provide any TimeSeries: The reason class associated to the class MarketDocument shall be used to inform that no constraint situation is provided for the whole delivery period. The dependencies are listed in: Table 1: Flow Based Domain Table 2: Flow Based Domain Publication Table 3: Flow Based Market Impact Publication Table 4: Critical Network Element Determination Table 5: Critical Network Element Publication Table 6: Critical Network Element Market Impact Publication Page 16 of 48

17 526 Table 1 Flow based Domain dependency Class Attribute Flow Based Process CriticalNetworkElem ent MarketDocument type process.processtype sender_marketparticipant.marketrole.type receiver_marketparticipant.marketrole.type domain.mrid B08 = Flow Based Domain A43 = Flow Based domain constraint DayAhead A44 = Flow Based domain constraint Intraday A36 = Capacity Coordinator A04 = TSO used as EIC code of the Flow Based Study Area mrid used to identify the TS Time Series businesstype In_Domain.mRID Out_Domain.mRID B37 = Constraint Situation B38 = Initial Domain B39 = Flow based Domain Adjusted to Long Term schedules Series_Period Point 527 CurveType used Constraint Situation Type External Constraint Type mrid used to identify the Constraint_TimeSeries used to identify the Constraint_TimeSeries Constraint_TimeSeries businesstype name used B40 = Network Element Constraint B41 = Calculation opposition (Red Flag) may be used To provide a Name to the Constraint Situation used B09 = Net position 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 used to provide External Constraint Quantity ptdf_measurement_unit.name used for PTDF shadowprice_measurement_unit.name currency_unit.name Party_MarketParticipant.mRID used to identify the limiting TSOs used to identify the limiting TSOs Outage_RegisteredResourc e mrid used as EIC code of the Outage element name used as the name of the Outage element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation RemedialAction_RegisteredRe source mrid name used as EIC code of the element on which a remedial action is carried out used as the name of the element on which a remedial action is carried out Page 17 of 48 In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation

18 psrtype.psrtype marketobjectstatus_status Constraint Situation Type used to identify the type of the remedial action A01 = Tieline, A02 = line, A04 = Generation, A05 = Load Used to identify the status of the remedial action A18 = Preventive A19 = Curative External Constraint Type mrid used as EIC code of the Monitored element name used as the name of the Monitored element Monitored_RegisteredResource In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode flowbasedstudy_domain.mrd flowbasedstudy_domain.flowbasedmargin_qu antity.quantity used to identify InAggregateNode for element orientation used to identify OutAggregateNode for element orientation used as EIC code of the Flow Based Study Area used for the RAM marketcoupling_domain.mrid marketcoupling_domain.shadow_price.amount Analog measurementtype unitsymbol 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 used to identify the unit of the measurement "A", "MW", "%" positiveflowin may be used to identify on which direction the element is monitored A01 = Direct A02 = Opposite Not used = Double Analog Values value used to provide the measurement value timestamp description may be used to provide the constraint duration may be used to identify the situation of the measurement point "Before Outage", "After Curative Action" PTDF Domain mrid used to identify the impacted bidding zone ptdf_quantity.quantity used to provide the PTFD factor for the Bidding zone 528 Page 18 of 48

19 529 Table 2 Flow based Publication dependency Class Attribute Flow Based Process CriticalNetworkElem ent MarketDocument type process.processtype sender_marketparticipant.marketrole.type receiver_marketparticipant.marketrole.type domain.mrid B09 = Flow Based Domain Publication A43 = Flow Based domain constraint DayAhead A44 = Flow Based domain constraint Intraday A36 = Capacity Coordinator or A04 = TSO A32 = Market Information Aggregator or A11 = Market Operator used as EIC code of the Flow Based Study Area mrid used to identify the TS Time Series In_Domain.mRID Out_Domain.mRID businesstype B39 = Flow based Domain Adjusted to Long Term schedules Series_Period Point 530 CurveType used Constraint Situation Type External Constraint Type mrid used to identify the Constraint_TimeSeries used to identify the Constraint_TimeSeries Constraint_TimeSeries businesstype name used B40 = Network Element Constraint B41 = Calculation opposition (Red Flag) may be used To provide a Name to the Constraint Situation used B09 = Net position 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 used to provide External Constraint Quantity ptdf_measurement_unit.name used for PTDF shadowprice_measurement_unit.name currency_unit.name Party_MarketParticipant.mRID used to identify the limiting TSOs used to identify the limiting TSOs Outage_RegisteredResource RemedialAction_RegisteredRe source mrid used as anonymous EIC code of the Outage element name used as the name of the Outage element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation mrid name In_Domain Out_Domain In_AggregateNode Out_AggregateNode Page 19 of 48

20 Constraint Situation Type External Constraint Type psrtype.psrtype marketobjectstatus_status mrid used as anonymous EIC code of the Monitored element name used as the name of the Monitored element Monitored_RegisteredResource In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode flowbasedstudy_domain.mrd flowbasedstudy_domain.flowbasedmargin_qu antity.quantity used to identify InAggregateNode for element orientation used to identify OutAggregateNode for element orientation used as EIC code of the Flow Based Study Area used for the RAM marketcoupling_domain.mrid marketcoupling_domain.shadow_price.amount Analog Analog Values measurementtype unitsymbol positiveflowin value timestamp description PTDF Domain 531 mrid used to identify the impacted bidding zone ptdf_quantity.quantity used to provide the PTFD factor for the Bidding zone Page 20 of 48

21 532 Table 3 Flow based Market Impact Publication dependency Class Attribute Flow Based Process CriticalNetworkElem ent MarketDocument type process.processtype sender_marketparticipant.marketrole.type receiver_marketparticipant.marketrole.type domain.mrid B10 = Flow Based domain Market Impact Publication A43 = Flow Based domain constraint DayAhead A44 = Flow Based domain constraint Intraday A36 = Capacity Coordinator or A04 = TSO A32 = Market Information Aggregator or A11 = Market Operator used as EIC code of the Flow Based Study Area mrid used to identify the TS Time Series businesstype In_Domain.mRID Out_Domain.mRID B39 = Domain Adjusted to Long Term schedules Series_Period Point 533 CurveType used Constraint Situation Type External Constraint Type mrid used to identify the Constraint_TimeSeries used to identify the Constraint_TimeSeries Constraint_TimeSeries businesstype name used B40 = Network Element Constraint B41 = Calculation opposition (Red Flag) may be used To provide a Name to the Constraint Situation used B09 = Net position 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 used to provide External Constraint Quantity ptdf_measurement_unit.name used for PTDF shadowprice_measurement_unit.name used for Shadow Price (per MW or A) currency_unit.name used for Shadow Price Party_MarketParticipant.mRID used to identify the limiting TSOs used to identify the limiting TSOs Outage_RegisteredResource RemedialAction_RegisteredReso urce mrid used as anonymous EIC code of the Outage element name used as the name of the Outage element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation mrid name In_Domain Out_Domain In_AggregateNode Out_AggregateNode Page 21 of 48

22 Constraint Situation Type External Constraint Type psrtype.psrtype marketobjectstatus_status mrid used as anonymous EIC code of the Monitored element name used as the name of the Monitored element Monitored_RegisteredResource In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode flowbasedstudy_domain.mrd flowbasedstudy_domain.flowbasedmargin_qu antity.quantity marketcoupling_domain.mrid used to identify InAggregateNode for element orientation used to identify OutAggregateNode for element orientation used as EIC code of the Flow Based Study Area used for the RAM used as EIC code of the Flow Based Market Coupling Area marketcoupling_domain.shadow_price.amount used to provide the shadow price of the critical network element for the area Analog Analog Values measurementtype unitsymbol positiveflowin value timestamp description PTDF Domain mrid used to identify the impacted bidding zone ptdf_quantity.quantity used to provide the PTFD factor for the Bidding zone 534 Page 22 of 48

23 535 Table 4 NTC Coordinated Determination dependency Class Attribute NTC Coordinated Calculation Process CriticalNetworkEl ement MarketDocument type process.processtype sender_marketparticipant.marketrole.type receiver_marketparticipant.marketrole.type domain.mrid B06 = Critical Network Element Determination A15 = Capacity Determination or A40 = Intraday Process A36 = Capacity Coordinator A04 = TSO used as EIC code of the coordinated area mrid used to identify the TS Time Series businesstype In_Domain.mRID Out_Domain.mRID B37 = Constraint Situation used as EIC code of the InArea of the oriented border study impacted by the listed Critical network elements used as EIC code of the OutArea of the oriented border study impacted by the listed Critical network elements Series_Period Point 536 CurveType used Constraint Situation Type External Constraint Type mrid used to identify the Constraint_TimeSeries used to identify the Constraint_TimeSeries Constraint_TimeSeries businesstype name used B40 = Network Element Constraint B41 = Calculation opposition (Red Flag) may be used To provide a Name to the Constraint Situation used A81 = TTC may be used To provide a Name to the External Constraint Quantity_Measurement_Unit.name used for External Constraint (= MW) ExternalConstraint_Quantity.quantity used to provide External Constraint Quantity ptdf_measurement_unit.name shadowprice_measurement_unit.name currency_unit.name Party_MarketParticipant.mRID used to identify the limiting TSOs used to identify the limiting TSOs Outage_RegisteredResou rce RemedialAction_RegisteredResource mrid used as EIC code of the Outage element name used as the name of the Outage element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode mrid name may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation used as EIC code of the element on which a remedial action is carried out used as the name of the element on which a remedial action is carried out In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode psrtype.psrtype may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation used to identify the type of the remedial action Page 23 of 48

24 marketobjectstatus_status Constraint Situation Type A01 = Tieline, A02 = line, A04 = Generation, A05 = Load Used to identify the status of the remedial action A18 = Preventive A19 = Curative External Constraint Type mrid used as EIC code of the Monitored element name used as the name of the Monitored element Monitored_RegisteredResource In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation flowbasedstudy_domain.mrd flowbasedstudy_domain.flowbasedmargin_qu antity.quantity marketcoupling_domain.mrid marketcoupling_domain.shadow_price.amount Analog measurementtype unitsymbol 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 used to identify the unit of the measurement "A", "MW", "%" positiveflowin may be used to identify on which direction the element is monitored A01 = Direct A02 = Opposite Not used = Double Analog Values value used to provide the measurement value timestamp description may be used to provide the constraint duration may be used to identify the situation of the measurement point "Before Outage", "After Curative Action" PTDF Domain 537 mrid ptdf_quantity.quantity Page 24 of 48

25 538 Table 5 Critical Network Element Publication dependency Class Attribute NTC Coordinated Calculation Process CriticalNetworkEl ement MarketDocument type process.processtype sender_marketparticipant.marketrole.type receiver_marketparticipant.marketrole.type domain.mrid B07 = Critical Network Element Publication A15 = Capacity Determination or A40 = Intraday Process A36 = Capacity Coordinator or A04 = TSO A32 = Market Information Aggregator used as EIC code of the coordinated area mrid used to identify the TS Time Series businesstype In_Domain.mRID Out_Domain.mRID B37 = Constraint Situation used as EIC code of the InArea of the oriented border study impacted by the listed Critical network elements used as EIC code of the OutArea of the oriented border study impacted by the listed Critical network elements Series_Period Point 539 CurveType used Constraint Situation Type External Constraint Type mrid used to identify the Constraint_TimeSeries used to identify the Constraint_TimeSeries Constraint_TimeSeries businesstype name used B40 = Network Element Constraint B41 = Calculation opposition (Red Flag) may be used To provide a Name to the Constraint Situation used A81 = TTC may be used To provide a Name to the External Constraint Quantity_Measurement_Unit.name used for External Constraint (= MW) ExternalConstraint_Quantity.quantity used to provide External Constraint Quantity ptdf_measurement_unit.name shadowprice_measurement_unit.name currency_unit.name Party_MarketParticipant.mRID used to identify the limiting TSOs used to identify the limiting TSOs Outage_RegisteredResource RemedialAction_RegisteredReso urce mrid used as anonymous EIC code of the Outage element name used as the name of the Outage element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation mrid name In_Domain Out_Domain In_AggregateNode Out_AggregateNode Page 25 of 48

26 Constraint Situation Type External Constraint Type psrtype.psrtype marketobjectstatus_status mrid used as anonymous EIC code of the Monitored element Monitored_RegisteredResource name used as the name of the Monitored element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation flowbasedstudy_domain.mrd flowbasedstudy_domain.flowbasedmargin_qu antity.quantity marketcoupling_domain.mrid marketcoupling_domain.shadow_price.amount Analog Analog Values measurementtype unitsymbol positiveflowin value timestamp description PTDF Domain 540 mrid ptdf_quantity.quantity Page 26 of 48

27 541 Table 6 Critical Network Element Market Impact Publication dependency Class Attribute NTC Coordinated Calculation Process CriticalNetworkEl ement MarketDocument type process.processtype sender_marketparticipant.marketrole.type receiver_marketparticipant.marketrole.type domain.mrid B12 = Critical Network Element Market Impact Publication A15 = Capacity Determination or A40 = Intraday Process A36 = Capacity Coordinator or A04 = TSO A32 = Market Information Aggregator used as EIC code of the coordinated area mrid used to identify the TS Time Series businesstype In_Domain.mRID Out_Domain.mRID B37 = Constraint Situation used as EIC code of the InMarketArea which was effectively impacted by the listed Critical network elements used as EIC code of the OutMarketArea which was effectively impacted by the listed Critical network elements Series_Period Point 542 CurveType used Constraint Situation Type External Constraint Type mrid used to identify the Constraint_TimeSeries used to identify the Constraint_TimeSeries Constraint_TimeSeries businesstype name used B40 = Network Element Constraint B41 = Calculation opposition (Red Flag) may be used To provide a Name to the Constraint Situation used A81 = TTC may be used To provide a Name to the External Constraint Quantity_Measurement_Unit.name used for External Constraint (= MW) ExternalConstraint_Quantity.quantity used to provide External Constraint Quantity ptdf_measurement_unit.name shadowprice_measurement_unit.name currency_unit.name Party_MarketParticipant.mRID used to identify the limiting TSOs used to identify the limiting TSOs Outage_RegisteredResource RemedialAction_RegisteredReso urce mrid used as anonymous EIC code of the Outage element name used as the name of the Outage element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation mrid name In_Domain Out_Domain In_AggregateNode Out_AggregateNode Page 27 of 48

28 Constraint Situation Type External Constraint Type psrtype.psrtype marketobjectstatus_status mrid used as anonymous EIC code of the Monitored element Monitored_RegisteredResource name used as the name of the Monitored element In_Domain used to identify InArea Out_Domain used to identify OutArea In_AggregateNode Out_AggregateNode may be used to identify InAggregateNode for element orientation may be used to identify OutAggregateNode for element orientation flowbasedstudy_domain.mrd flowbasedstudy_domain.flowbasedmargin_qu antity.quantity marketcoupling_domain.mrid marketcoupling_domain.shadow_price.amount Analog Analog Values measurementtype unitsymbol positiveflowin value timestamp description PTDF Domain 543 mrid ptdf_quantity.quantity Page 28 of 48

29 ENTSO-E Critical Network Element Process Contextual and assembly models Figure 4 shows the model. CriticalNetworkElement contextual model Overview of the model Figure 4 CriticalNetworkElement contextual model IsBasedOn relationships from the European style market profile Table 7 shows the traceability dependency of the classes used in this package towards the upper level. 554 Table 7 IsBasedOn dependency 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 Page 29 of 48 ENTSO-E AISBL Avenue de Cortenbergh, Brussels Belgium Tel Fax info@entsoe.eu

30 Name Currency_Unit Domain ExternalConstraint_Quantity FlowBasedMargin_Quantity FlowBasedStudy_Domain MarketCoupling_Domain MarketObjectStatus MarketParticipant MarketRole Measure_Unit MktPSRType Monitored_RegisteredResource Outage_RegisteredResource Party_MarketParticipant Point Process PTDF_Domain PTDF_Quantity Reason RemedialAction_RegisteredResource Series_Period Shadow_Price Time_Period TimeSeries Complete IsBasedOn Path TC57CIM::IEC62325::MarketManagement::Unit TC57CIM::IEC62325::MarketManagement::Domain TC57CIM::IEC62325::MarketManagement::Quantity TC57CIM::IEC62325::MarketManagement::Quantity TC57CIM::IEC62325::MarketManagement::Domain TC57CIM::IEC62325::MarketManagement::Domain TC57CIM::IEC62325::MarketManagement::MarketObjectStatus TC57CIM::IEC62325::MarketCommon::MarketParticipant TC57CIM::IEC62325::MarketCommon::MarketRole TC57CIM::IEC62325::MarketManagement::Unit TC57CIM::IEC62325::MarketManagement::MktPSRType TC57CIM::IEC62325::MarketCommon::RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource TC57CIM::IEC62325::MarketCommon::MarketParticipant TC57CIM::IEC62325::MarketManagement::Point TC57CIM::IEC62325::MarketManagement::Process TC57CIM::IEC62325::MarketManagement::Domain TC57CIM::IEC62325::MarketManagement::Quantity TC57CIM::IEC62325::MarketManagement::Reason TC57CIM::IEC62325::MarketCommon::RegisteredResource TC57CIM::IEC62325::MarketManagement::Period TC57CIM::IEC62325::MarketManagement::Price TC57CIM::IEC62325::MarketManagement::Period TC57CIM::IEC62325::MarketManagement::TimeSeries 555 Page 30 of 48

31 CriticalNetworkElement assembly model Overview of the model Figure 5 shows the model Figure 5 CriticalNetworkElement assembly model IsBasedOn relationships from the European style market profile Table 8 shows the traceability dependency of the classes used in this package towards the upper level. Page 31 of 48

32 564 Table 8 IsBasedOn dependency Name Complete IsBasedOn Path Analog AnalogValue Constraint_TimeSeries TC57CIM::IEC61970::Base::Meas::Analog TC57CIM::IEC61970::Base::Meas::AnalogValue TC57CIM::IEC62325::MarketManagement::TimeSeries CriticalNetworkElement_MarketDocument TC57CIM::IEC62325::MarketManagement::MarketDocument Monitored_RegisteredResource Outage_RegisteredResource Party_MarketParticipant Point PTDF_Domain Reason RemedialAction_RegisteredResource Series_Period TimeSeries TC57CIM::IEC62325::MarketCommon::RegisteredResource TC57CIM::IEC62325::MarketCommon::RegisteredResource TC57CIM::IEC62325::MarketCommon::MarketParticipant TC57CIM::IEC62325::MarketManagement::Point TC57CIM::IEC62325::MarketManagement::Domain TC57CIM::IEC62325::MarketManagement::Reason TC57CIM::IEC62325::MarketCommon::RegisteredResource TC57CIM::IEC62325::MarketManagement::Period TC57CIM::IEC62325::MarketManagement::TimeSeries Detailed CriticalNetworkElement assembly model CriticalNetworkElement_MarketDocument root class This document provides the computed critical network elements to be used for capacity allocation and publication. The critical network elements are the main limiting elements identified after a coordinated network study. An electronic document containing the information necessary to satisfy the requirements of a given business process. Table 9 shows all attributes of CriticalNetworkElement_MarketDocument. Table 9 Attributes of CriticalNetworkElement assembly model::criticalnetworkelement_marketdocument Order mult. Attribute name / Attribute type Description 0 [1..1] mrid ID_String 1 [1..1] revisionnumber ESMPVersion_String 2 [1..1] type MessageKind_String 3 [1..1] process.processtype ProcessKind_String 4 [1..1] sender_marketparticipant.mrid PartyID_String 5 [1..1] sender_marketparticipant.marketrole.type MarketRoleKind_String 6 [1..1] receiver_marketparticipant.mrid PartyID_String The unique identification of the document being exchanged within a business process flow. The identification of the version that distinguishes one evolution of a document from another. The coded type of a document. The document type describes the principal characteristic of the document. The identification of the nature of process that the document addresses. --- The process dealt with in the document. The identification of a party in the energy market. --- Document owner. The identification of the role played by a market player. --- Document owner. --- The role associated with a MarketParticipant. The identification of a party in the energy market. --- Document recipient. Page 32 of 48

33 Order mult. Attribute name / Attribute type Description 7 [1..1] receiver_marketparticipant.marketrole.type The identification of the role played by a market player. MarketRoleKind_String --- Document recipient. --- The role associated with a MarketParticipant. 8 [1..1] createddatetime ESMP_DateTime 9 [1..1] time_period.timeinterval ESMP_DateTimeInterval 10 [0..1] domain.mrid AreaID_String The date and time of the creation of the document. 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. 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 Table 10 shows all association ends of CriticalNetworkElement_MarketDocument with other classes. Table 10 Association ends of CriticalNetworkElement assembly model::criticalnetworkelement_marketdocument with other classes Order mult. Class name / Role 11 [0..*] TimeSeries TimeSeries Description The time series that is associated with an electronic document. Association Based On : CriticalNetworkElement contextual model::criticalnetworkelement_marketdocument.[] CriticalNetworkElement contextual model::timeseries.timeseries[0..*] Analog Analog represents an analog Measurement. Analog provides the analog measurements monitored for one specific Monitored_RegisteredResource. Table 11 shows all attributes of Analog. Table 11 Attributes of CriticalNetworkElement assembly model::analog Order mult. Attribute name / Attribute type 0 [1..1] measurementtype AnalogType_String 1 [1..1] unitsymbol UnitSymbol 2 [0..1] positiveflowin ESMPBoolean_String Description Specifies the type of measurement. For example, this specifies if the measurement represents line flow, maximum line flow, reference line flow, etc. The unit of measure of the measured quantity. 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 Table 12 shows all association ends of Analog with other classes. Page 33 of 48

34 Table 12 Association ends of CriticalNetworkElement assembly model::analog with other classes 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.[] AnalogValue AnalogValue represents an analog MeasurementValue. Table 13 shows all attributes of AnalogValue. Table 13 Attributes of CriticalNetworkElement assembly model::analogvalue Order mult. Attribute name / Attribute type Description 0 [1..1] value ESMP_Float 1 [0..1] timestamp DateTime 2 [0..1] description String The value to supervise. The date and time to which the value refers to; it may be before or after the outage time (attribute position of class Point). It provides information about when the measurement point is computed, i.e. before the outage, after the outage, after curative action, etc Constraint_TimeSeries A set of constraint situations for one specific position which results from the critical network elements determination process and which may have an impact on the market by inducing congestions. Table 14 shows all attributes of Constraint_TimeSeries. Table 14 Attributes of CriticalNetworkElement assembly model::constraint_timeseries Order mult. Attribute name / Attribute type Description 0 [1..1] mrid ID_String 1 [1..1] businesstype BusinessKind_String 2 [0..1] name String 3 [0..1] quantity_measurement_unit.name MeasurementUnitKind_String A unique identification of the constraint time series. 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. The name of the outage described in this constraint time series. 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. Page 34 of 48

35 Order mult. Attribute name / Attribute type Description 4 [0..1] externalconstraint_quantity.quantity Decimal 5 [0..1] externalconstraint_quantity.quality Quality_String 6 [0..1] ptdf_measurement_unit.name MeasurementUnitKind_String 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. The description of the quality of the quantity. --- The quantity value of the external constraint identified in the business type of the Constraint_TimeSeries. 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 MeasurementUnitKind_String (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 Table 15 shows all association ends of Constraint_TimeSeries with other classes. Table 15 Association ends of CriticalNetworkElement assembly model::constraint_timeseries with other classes Order mult. Class name / Role Description 9 [0..*] Party_MarketParticipant Party_MarketParticipant 10 [0..*] Outage_RegisteredResource Outage_RegisteredResource 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.[] 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_RegisteredResour ce RemedialAction_RegisteredResour ce 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_regi steredresource[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_registeredreso urce[0..*] CriticalNetworkElement contextual model::constraint_timeseries.[] Page 35 of 48

36 Order mult. Class name / Role Description 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.[] Monitored_RegisteredResource This is the critical network element of the power network in the constraint situation described by the Constraint_TimeSseries. Analog measurements are monitored for this resource to identify the impact of this critical network element on the market. Table 16 shows all attributes of Monitored_RegisteredResource. Table 16 Attributes of CriticalNetworkElement assembly model::monitored_registeredresource Order mult. Attribute name / Attribute type Description 0 [0..1] mrid ResourceID_String 1 [0..1] name String 2 [0..1] in_domain.mrid AreaID_String 3 [0..1] out_domain.mrid AreaID_String 4 [0..1] in_aggregatenode.mrid MeasurementPointID_String 5 [0..1] out_aggregatenode.mrid MeasurementPointID_String 6 [0..1] flowbasedstudy_domain.mrid AreaID_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. The name is any free human readable and possibly non unique text naming the object. The unique identification of the domain. --- The control area where the flow measurement enters for the monitored resource. The unique identification of the domain. --- The control area connected to the monitored resource where the flow measurement comes out. The unique identification of an AggregateNode. --- The node connected to the monitored resource from which the flow measurement enters. The unique identification of an AggregateNode. --- The node connected to the monitored resource from which the flow measurement comes out. 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 The quantity value of remaining available Decimal 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. Page 36 of 48

37 Order mult. Attribute name / Attribute type Description 8 [0..1] flowbasedstudy_domain.flowbasedmargin_quantity.quality Quality_String 9 [0..1] marketcoupling_domain.mrid AreaID_String 10 [0..1] marketcoupling_domain.shadow_price.amount Amount_Decimal 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. 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. 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 Table 17 shows all association ends of Monitored_RegisteredResource with other classes. Table 17 Association ends of CriticalNetworkElement assembly model::monitored_registeredresource with other classes Order mult. Class name / Role 11 [0..*] PTDF_Domain 12 [0..*] Analog PTDF_Domain Measurements Description 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.[] The monitored measurements for the critical network element. Association Based On : CriticalNetworkElement contextual model::analog.measurements[0..*] CriticalNetworkElement contextual model::monitored_registeredresource.[] Outage_RegisteredResource This is one of the network elements which are in outage for the studied constraint situation defined be the Constraint_TimeSeries. Table 18 shows all attributes of Outage_RegisteredResource. Table 18 Attributes of CriticalNetworkElement assembly model::outage_registeredresource Order mult. Attribute name / Attribute type 0 [1..1] mrid 1 [0..1] name ResourceID_String String Description 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. The name is any free human readable and possibly non unique text naming the object. Page 37 of 48

38 Order mult. Attribute name / Attribute type 2 [0..1] in_domain.mrid AreaID_String 3 [0..1] out_domain.mrid AreaID_String 4 [0..1] in_aggregatenode.mrid MeasurementPointID_String 5 [0..1] out_aggregatenode.mrid MeasurementPointID_String Description The unique identification of the domain. --- The control area where an extremity of the resource is located. This is used to provide orientation information. The unique identification of the domain. --- The control area where an extremity of the resource is located. This is used to provide orientation information. The unique identification of an AggregateNode. --- The node connected to the resource; it is used to provide flow orientation information. The unique identification of an AggregateNode. --- The node connected to the resource; it is used to provide flow orientation information Party_MarketParticipant The identification of the limiting TSOs of the critical network element for the associated Constraint_TimeSeries. The identification of the party participating in energy market business processes. Table 19 shows all attributes of Party_MarketParticipant. Table 19 Attributes of CriticalNetworkElement assembly model::party_marketparticipant Order mult. Attribute name / Attribute type 0 [1..1] mrid PartyID_String Description The identification of the limiting TSO associated to the Constraint_TimeSeries Point The identification of the values being addressed within a specific interval of time. Table 20 shows all attributes of Point. Table 20 Attributes of CriticalNetworkElement assembly model::point Order mult. Attribute name / Attribute type 0 [1..1] position Position_Integer Description A sequential value representing the relative position within a given time interval Table 21 shows all association ends of Point with other classes. Page 38 of 48

39 Table 21 Association ends of CriticalNetworkElement assembly model::point with other classes Order mult. Class name / Role Description 1 [0..*] Constraint_TimeSeries The set of constraint time series for the associated position coming from the Constraint_TimeSeries 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..*] PTDF_Domain The bidding zone impacted by the critical network element. A domain covering a number of related objects, such as market balance area, grid area, borders etc. Table 22 shows all attributes of PTDF_Domain. Table 22 Attributes of CriticalNetworkElement assembly model::ptdf_domain Order mult. Attribute name / Attribute type 0 [1..1] mrid AreaID_String 1 [1..1] ptdf_quantity.quantity Decimal 2 [0..1] ptdf_quantity.quality Quality_String Description The bidding zone impacted by the critical network element. The unique identification of the domain. 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. The description of the quality of the quantity. --- The PTDF factor value associated to the bidding zone for the critical network element Reason The motivation of an act. Table 23 shows all attributes of Reason. Table 23 Attributes of CriticalNetworkElement assembly model::reason Order mult. Attribute name / Attribute type 0 [1..1] code ReasonCode_String 1 [0..1] text ReasonText_String Description The motivation of an act in coded form. The textual explanation corresponding to the reason code. 657 Page 39 of 48

40 RemedialAction_RegisteredResource 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 remedial actions may be identified as automatic, preventive or curative. The type of the remedial action is also provided: generation, load and topology. Table 24 shows all attributes of RemedialAction_RegisteredResource. Table 24 Attributes of CriticalNetworkElement assembly model::remedialaction_registeredresource Order mult. Attribute name / Attribute type 0 [1..1] mrid 1 [0..1] name ResourceID_String String 2 [0..1] in_domain.mrid AreaID_String 3 [0..1] out_domain.mrid AreaID_String 4 [0..1] in_aggregatenode.mrid MeasurementPointID_String 5 [0..1] out_aggregatenode.mrid MeasurementPointID_String 6 [1..1] psrtype.psrtype PsrType_String 7 [1..1] marketobjectstatus.status Status_String Description 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. The name is any free human readable and possibly non unique text naming the object. The unique identification of the domain. --- The control area where an extremity of the resource is located. This is used to provide orientation information. The unique identification of the domain. --- The control area where an extremity of the resource is located. This is used to provide orientation information. The unique identification of an AggregateNode. --- The node connected to the resource; it is used to provide flow orientation information. The unique identification of an AggregateNode. --- The node connected to the resource; it is used to provide flow orientation information. 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. 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, Series_Period The identification of the period of time corresponding to a given time interval and resolution. Table 25 shows all attributes of Series_Period. Table 25 Attributes of CriticalNetworkElement assembly model::series_period Order mult. Attribute name / Attribute type 0 [1..1] timeinterval 1 [1..1] resolution ESMP_DateTimeInterval Duration Description The start and end time of the period. The definition of the number of units of time that compose an individual step within a period. Page 40 of 48

41 Table 26 shows all association ends of Series_Period with other classes. Table 26 Association ends of CriticalNetworkElement assembly model::series_period with other classes Order mult. Class name / Role Description 2 [1..*] Point Point The Point information associated with a given Series_Period.within a TimeSeries. Association Based On : CriticalNetworkElement contextual model::series_period.[] CriticalNetworkElement contextual model::point.point[1..*] TimeSeries A set of time-ordered quantities being exchanged in relation to a product. Table 27 shows all attributes of TimeSeries. Table 27 Attributes of CriticalNetworkElement assembly model::timeseries Order mult. Attribute name / Attribute type 0 [1..1] mrid ID_String 1 [1..1] businesstype BusinessKind_String 2 [0..1] in_domain.mrid AreaID_String 3 [0..1] out_domain.mrid AreaID_String 4 [1..1] curvetype CurveType_String Description A unique identification of the time series. The identification of the nature of the time series. 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. 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. The identification of the coded representation of the type of curve being described Table 28 shows all association ends of TimeSeries with other classes. Table 28 Association ends of CriticalNetworkElement assembly model::timeseries with other classes Order mult. Class name / Role 5 [1..*] Series_Period Period 6 [0..*] Reason Reason Description 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..*] 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 Page 41 of 48

42 Datatypes The list of datatypes used for the CriticalNetworkElement assembly model is as follows: ESMP_DateTimeInterval compound Amount_Decimal datatype AnalogType_String datatype, codelist AnalogTypeList AreaID_String datatype, codelist CodingSchemeTypeList BusinessKind_String datatype, codelist BusinessTypeList CurrencyCode_String datatype, codelist CurrencyTypeList CurveType_String datatype, codelist CurveTypeList ESMP_DateTime datatype ESMP_Float datatype ESMPBoolean_String datatype, codelist IndicatorTypeList ESMPVersion_String datatype ID_String datatype MarketRoleKind_String datatype, codelist RoleTypeList MeasurementPointID_String datatype, codelist CodingSchemeTypeList MeasurementUnitKind_String datatype, codelist UnitOfMeasureTypeList MessageKind_String datatype, codelist MessageTypeList PartyID_String datatype, codelist CodingSchemeTypeList Position_Integer datatype ProcessKind_String datatype, codelist ProcessTypeList PsrType_String datatype, codelist AssetTypeList Quality_String datatype, codelist QualityTypeList ReasonCode_String datatype, codelist ReasonCodeTypeList ReasonText_String datatype ResourceID_String datatype, codelist CodingSchemeTypeList Status_String datatype, codelist StatusTypeList YMDHM_DateTime datatype CriticalNetworkElement_MarketDocument XML schema Figure 6 to Figure 11 provide the structure of the schema. Page 42 of 48

43 Figure 6 CriticalNetworkElement_MarketDocument XML schema structure 1/6 Page 43 of 48

44 Figure 7 CriticalNetworkElement_MarketDocument XML schema structure 2/6 Page 44 of 48

45 Figure 8 CriticalNetworkElement_MarketDocument XML schema structure 3/6 Page 45 of 48

46 Figure 9 CriticalNetworkElement_MarketDocument XML schema structure 4/6 Page 46 of 48

47 Figure 10 CriticalNetworkElement_MarketDocument XML schema structure 5/6 Page 47 of 48