European Network of Transmission System Operators for Electricity ENTSO- E AISBL • Avenue de Cortenbergh, 100 • 1000 Brussels • Belgium • Tel +32 2 741 09 50 • Fax +32 2 741 09 51 • [email protected]• www.entsoe.eu 1 2017-10-27 VERSION 1.0 OUTAGE BUSINESS PROCESS AND FORMAT
64
Embed
OUTAGE BUSINESS PROCESS AND FORMAT - … · 30 18.3 Detailed Network element maintenance scheduling ... Main activities under the definition of outage ... ENTSO-E Outage Business
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Table 1 – Steps of business process ..................................................................................... 10 94
Table 2 - Main activities under the definition of outage coordination regions and 95 relevant assets step .............................................................................................................. 16 96
Table 3 - Main activities under the development and update of availability plans of 97 relevant assets step .............................................................................................................. 19 98
Table 4 - Main activities under the execution of availability plans step .................................. 25 99
Table 14 - Attributes of Network element maintenance scheduling document assembly 109 model::OutageSchedule_MarketDocument ............................................................................ 40 110
Table 15 - Association ends of Network element maintenance scheduling document 111 assembly model::OutageSchedule_MarketDocument with other classes ............................... 41 112
Table 16 - Attributes of Network element maintenance scheduling document assembly 113 model::Alternative_RegisteredResource ............................................................................... 41 114
Table 17 - Attributes of Network element maintenance scheduling document assembly 115 model::Reason ...................................................................................................................... 42 116
Table 18 - Attributes of Network element maintenance scheduling document assembly 117 model::RegisteredResource .................................................................................................. 42 118
Table 19 - Attributes of Network element maintenance scheduling document assembly 119 model::SwitchedBack_Time_Period ...................................................................................... 43 120
Table 20 - Attributes of Network element maintenance scheduling document assembly 121 model::TimeSeries ................................................................................................................ 43 122
Table 21 - Association ends of Network element maintenance scheduling document 123 assembly model::TimeSeries with other classes.................................................................... 46 124
Table 25 - Association ends of Network outage configuration assembly 129 model::Ref_MarketDocument with other classes ................................................................... 51 130
Table 30 - Association ends of Network outage configuration assembly 137 model::TimeSeries with other classes ................................................................................... 55 138
Table 31 - Attributes of ESMPDataTypes::ESMP_DateTimeInterval ...................................... 56 139
– Page 5 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
This document and its whole translations may be copied and furnished to others, and derivative 174 works that comment on or otherwise explain it or assist in its implementation may be prepared, 175 copied, published and distributed, in whole or in part, without restriction of any kind, provided 176 that the above copyright notice and this paragraph are included on all such copies and 177 derivative works. However, this document itself may not be modified in any way, except for 178 literal and whole translation into languages other than English and under all circumstances, the 179 copyright notice or references to ENTSO-E may not be removed. 180
This document and the information contained herein is provided on an "as is" basis. 181
ENTSO-E DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 182 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 183 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 184 FITNESS FOR A PARTICULAR PURPOSE. 185
Maintenance notice: 186
This document is maintained by the ENTSO-E WG EDI. Comments or remarks are to be 187 provided at [email protected] 188
SO GL requires TSOs to establish a common medium- and long-term outage planning process 192 based on predefined standards with the following key objectives: 193
Each TSO participates in the outage planning and coordination in accordance with the principles 203 described in the OPS (SO GL) in order to monitor the availability status of its relevant assets 204 and coordinate their availability plans to ensure the operational security of the transmissio n 205 system. 206
The Outage Planning and Coordination process consists of the following steps: 207
• Definition of Outage Coordination Regions and relevant assets 208
• Development and update of availability plans of relevant assets 209
• Execution of availability plans 210
A brief description of the aforementioned steps of the Business Process is provided in the next 211 table. 212
Table 1 – Steps of business process 213
STEPS Brief Description
Definition of Outage Coordination Regions and
relevant assets
In this step, TSOs ensure their participation in the outage planning of a specific outage coordination region. Within the Outage Coordination Region, a Regional Security Coordinator (RSC) is appointed and his role is to facilitate, coordinate and perform tasks and provide recommendations for the outage planning process. Next, all TSOs shall jointly develop a methodology at least per synchronous area for the assessment of relevant assets (if not available) and use it to define a common single list of relevant assets.
Development and update of availability plans of relevant
assets
In this step, it shall first appoint Outage Planning Agents (OPA), with the task of planning the availability status of the relevant grid elements: each TSO shall act as the OPA for each relevant grid element it operates, for all other relevant assets, the owner shall appoint (or act as) the OPA. TSOs and OPAs shall then assess the indicative yearly availability plans and provide availability plans proposals for the relevant assets. Next, all TSOs shall assess whether outage planning incompatibilities (OPI) arise from the availability plans. In case of OPIs, all relevant parties should be informed and find a solution to eliminate the OPIs. Once no OPIs remain, the preliminary availability plans can be submitted, validated and then finalized (update in the time between the finalisation of the year-ahead outage coordination and before its real-time execution is also possible.)
Execution of availability plans
When it comes to the real-time execution of the availability plans all parties apply the outage planning. Postponement of outage is also possible in case of forced outages or in case a TSO identifies that an outage can lead the transmission system to a not secure state. Due to the change of the network condition forecasted previously.
214
A high level overview of the Coordinated Outage Planning Process is presented in chapter 13,Examples 215
of Outages. 216
217
– Page 11 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Outage Schedule is defined as unavailability information which is exchanged upon the Network 660 Elements. 661 662 Each outage schedule document contains fields as described in Table below: 663 664
codelist StandardProcessTypeList A31 = week ahead, A32 = month ahead, A33 = year ahead A36 = Creation A37 = Modification A39 = Synchronisation process (to be used for request for report from market participant or for all non-weekly, non-monthly- non-yearly report answers)
sender_MarketParticipant.mRID EIC code of sender
sender_MarketParticipant.marketRole.type A04 = SO
receiver_MarketParticipant.mRID EIC code of receiver
Table 6 - create planned outage 671 Table 6 describes a planned unavailability of TSO APG for one element in the transmission 672 grid. 673 674 675 676 677
– Page 32 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Element information is sent by System Operator to the Data Provider who submits information 689 to RSCI (using Ref_MarketDocument). 690 691 Network element is considered as part of the grid treated as relevant or non-relevant asset 692 (defined in GLSO) on which the unavailability information is exchanged between Parties within 693 Outage Schedule document. 694 695 The following sequence diagram shows the submission process for element update information. 696 697
698 Figure 6: submission process for element update information 699 700
sd SQ-Pr ov ide/Submit element infor mat ions
System operator
(from Roles)
Information receiver
(from Roles)
Data provider
(from Roles)
Information receiver
(from Roles)
Out of the scope of
this document.
Note:
This Information
Receiver is RSCSP
provide new element
information
(Ref_MarketDocument)
Element update information
(Ref_MarketDocument )
provide new element
inforamtions
(Ref_MarketDocument)
merge element
information()
ACK / nACK
(Acknowledgement_MarketDocumen
IEC 62325-451-1)
Element Update
(Ref_MarketDocument)
– Page 34 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
713 Table 10 - update / modification des Elements 714 715 Table 10 illustrates deactivation of an element by using „A37-Modification” and changing the 716 “endLifetime_Datum” for specific time in future. 717 Changes of elements can only be applied by element owning TSO except field „CancelledTS” 718 where each TSO may use A01 for marking element as interesting for his TSO or A02 for marking 719 element as non- interesting for his TSO. 720 721
722 Table 11 - delete “interesting for” Information TSO TenneT NL 723 724 Table 11 illustrates how TSO TenneT NL marks element with registeredResource.mRID = 10T-725 PL-SE-000016 by sending process.processType = A39 (Synchronisation) and CancelledTS = 726 A02 (Deactivated), as “non-interesting for” for TenneT NL. 727 728 Example files can be requested from the OPC Project group 729 730 731
– Page 37 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
18.3 Detailed Network element maintenance scheduling document assembly model 759
OutageSchedule_MarketDocument root class 760
An electronic document containing the information necessary to satisfy the requirements of a 761 given business process. 762
This document is to be used to exchange the information to coordinate the maintenance 763 scheduling for network elements that may affect more than one system operators (e.g. such as 764 crossborder lines). 765
Table 14 shows all attributes of OutageSchedule_MarketDocument. 766
Table 14 - Attributes of Network element maintenance scheduling document assembly 767 model::OutageSchedule_MarketDocument 768
Order
mult.
Attribute name / Attribute type Description
0 [1..1]
mRID
ID_String
The unique identification of the document being exchanged within a business process flow.
1 [1..1]
revisionNumber
ESMPVersion_String
The identification of the version that distinguishes one evolution of a document from another.
2 [1..1]
type
MessageKind_String
The coded type of a document. The document type describes the principal characteristic of the document.
3 [1..1]
process.processType
ProcessKind_String
The identification of the nature of process that the document addresses. --- The process dealt with in the document depending upon the document type.
A31 = week ahead,
A32 = month ahead,
A33 = year ahead
A36 =Create
A37 = Modification
A39 = Synchronisation (to be used for request for report from market participant or for all non-weekly, non-monthly- non-yearly report answers)
4 [1..1]
sender_MarketParticipant.mRID
PartyID_String
The identification of a party in the energy market. --- The document owner.
– Page 41 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
The identification of the role played by a market player. --- The document owner. --- The role associated with a MarketParticipant.
6 [1..1]
receiver_MarketParticipant.mRID
PartyID_String
The identification of a party in the energy market. --- The document recipient.
7 [1..1]
receiver_MarketParticipant.marketRole.type
MarketRoleKind_String
The identification of the role played by a market player. --- The document recipient. --- The role associated with a MarketParticipant.
8 [1..1]
createdDateTime
ESMP_DateTime
The date and time of the creation of the document.
ENTSO-E date and time format
Date and time formats shall be used according to the ENTSO-E standards described chapter 4.3.10 in the ESS-Guide (see https://www.entsoe.eu/fileadmin/user_upload/edi/library/schedulev2r3/documentation/ess-guide-v2r3.pdf)
9 [0..1]
schedule_Period.timeInterval
ESMP_DateTimeInterval
The start and end date and time for a given interval. --- This information provides the start and end date and time of the schedule time interval.
10 [1..1]
domain.mRID
AreaID_String
The unique identification of the domain. --- The Domain associated with an electronic document header; it is used for report filtering.
769
Table 15 shows all association ends of OutageSchedule_MarketDocument with other classes. 770
Table 15 - Association ends of Network element maintenance scheduling document 771 assembly model::OutageSchedule_MarketDocument with other classes 772
Order mult. Class name / Role
Description
11 [0..*] TimeSeries
TimeSeries
The timesseries related to a maintenance of a network element. Association Based On: Network element maintenance scheduling document contextual model::OutageSchedule_MarketDocument.[] ----- Network element maintenance scheduling document contextual model::TimeSeries.TimeSeries[0..*]
773
Alternative_RegisteredResource 774
A resource that is registered through the market participant registration system. Examples 775 include generating unit, load, and non-physical generator or load. 776
Table 16 shows all attributes of Alternative_RegisteredResource. 777
Table 16 - Attributes of Network element maintenance scheduling document assembly 778 model::Alternative_RegisteredResource 779
Order mult. Attribute name / Attribute type Description
0 [1..1] mRID
ResourceID_String
The unique identification of a resource.
780
Reason 781
The motivation of an act. 782
– Page 42 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Table 17 - Attributes of Network element maintenance scheduling document assembly 784 model::Reason 785
Order mult. Attribute name / Attribute type
Description
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.
More specific information about the outage can be provided here such as information about substations
786
RegisteredResource 787
A resource that is registered through the market participant registration system. Examples 788 include generating unit, load, and non-physical generator or load. 789
Table 18 shows all attributes of RegisteredResource. 790
Table 18 - Attributes of Network element maintenance scheduling document assembly 791 model::RegisteredResource 792
Order mult. Attribute name / Attribute type Description
0 [1..1] mRID
ResourceID_String
The unique identification of a resource.
1 [1..1] name
String
The name is any free human readable and possibly non unique text naming the object.
The long name for the grid element has to be provided.
The following naming convention should be used for new grid elements:
-- Substation: Voltage level (optional), name
-- Line: Voltage level (optional), Subst. 1, Subst.2, Subst. X , name (optional)
-- transformer: Voltage levels (optional), Subst., name
512 in future
2 [0..1] pSRType.psrType
PsrType_String
The coded type of a power system resource. --- The identification of the type of resource associated with this RegisteredResource.
The bus bar's high voltage limit --- The identification of the type of resource associated with this RegisteredResource. --- The voltage level of the RegisteredResource having the MktPSRType.
- For an internal overheadline or cable (LINE): xxx
The bus bar's low voltage limit. The lower voltage value for a transformer. --- The identification of the type of resource associated with this RegisteredResource. --- The voltage level of the RegisteredResource having the MktPSRType - For a transformer (TRA): xxx/xxx
793
– Page 43 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
The identification of a time interval or a duration. 795
These time intervals are the one when although in the maintenance period the network element 796 is available for operation. 797
Table 19 shows all attributes of SwitchedBack_Time_Period. 798
Table 19 - Attributes of Network element maintenance scheduling document assembly 799 model::SwitchedBack_Time_Period 800
Order mult. Attribute name / Attribute type Description
0 [1..1] timeInterval
ESMP_DateTimeInterval
The start and end date and time for a given interval.
801
TimeSeries 802
A set of time-ordered quantities being exchanged in relation to a product. 803
Table 20 shows all attributes of TimeSeries. 804
Table 20 - Attributes of Network element maintenance scheduling document assembly 805 model::TimeSeries 806
Order mult. Attribute name / Attribute type Description
0 [1..1] mRID
ID_String
A unique identification of the time series. This mRID provides the case identification.
1 [0..1] description
String
The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy. This provides the description of the cause of the maintenance.
2 [1..1] businessType
BusinessKind_String
The identification of the nature of the time series.
B81 = (OUT)planned maintenance,
SSS,
3 [0..1] project_Names.name
String
Any free text that name the object. --- The project identification for the outage, it it exists. If multiple cases belong to the same project, one common project ID for these cases shall be determined by the requesting TSO. This information is additional to case ID.
4 [0..1] caseReference_Names.name
String
Any free text that name the object. --- All names of this identified object. If two cases affect each other and the status of one turns to "approved", then the status of the other shall be changed to "cancelled" and the caseID of the other case shall be entered here for tracking purposes.
If two cases affect each other and the status of one turns to "approved", the status of the other must be changed to "cancelled" and the case ID of the other case must be entered here for tracking reasons.
5 [1..1] outage_Period.timeInterval
ESMP_DateTimeInterval
The start and end date and time for a given interval. --- The total period of the outage for the RegisteredResource.
– Page 44 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
The date and time of the creation of the agreement. --- Information about the last change on the outage agreement. This is given by local tool as soon as a dataset is created or updated.
Given by local tool as soon as a dataset is created or changed.
The duration of the constraint. --- The constraint duration for the process described in the TimeSeries. The number of days to delay the maintenance scheduling period.
The duration of the constraint. --- The constraint duration for the process described in the TimeSeries. The number of days to anticipate the maintenance scheduling period.
9 [0..1] noRestitution_ConstraintDuration.type
String
The type of the constraint. --- The constraint duration for the process described in the TimeSeries. If the type attribute has a value equal to No then there shall be no restitution time duration. Otherwise, the type attribute shall not be used.
The duration of the constraint. --- The constraint duration for the process described in the TimeSeries. The maximum delay to give back the network element under maintenance if required.
"max" field is the must field and must be always filled with a value (N or a time).
If the other "restitution time [h]" fields are filled as well the maximum value of these fields must be put into the "max" field as well.
The duration of the constraint. --- The constraint duration for the process described in the TimeSeries. The time delay to give back during day time period the network element under maintenance if required.
The duration of the constraint. --- The constraint duration for the process described in the TimeSeries. The time delay to give back during night time period the network element under maintenance if required.
The duration of the constraint. --- The constraint duration for the process described in the TimeSeries. The time delay to give back during week end period the network element under maintenance if required.
14 [1..1] marketObjectStatus.status
Status_String
The coded condition or position of an object with regard to its standing. --- The status of the maintenance scheduling identified by the mRID (case-study). The status may be roughly planned, planned in details or cancelled. IT is always filled even if coordination is not necessary for this element.
– Page 45 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Order mult. Attribute name / Attribute type Description
15 [0..1] coordination_MarketObjectStatus.status
Status_String
The coded condition or position of an object with regard to its standing. --- The coordination status; it could be merged, modified, or confirmed. This attribute is used for coordination by both the requester TSO and the requested TSO.
This field is used for coordination by both, the requester TSO and the requested TSO.
Field must be filled if for an element the field “Coordination” in the reference data is not empty; otherwise the field must be left blank.
The requester TSO fills in all information "REQ", confirm "CON" or reject "REJ".
If a change is wished, the requested TSO has to call the TSO who started the coordination process to agree to start a new coordination process (i.e. put the status back to "REQ")
16 [0..1] measurement_Unit.name
MeasurementUnitKind_String
The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit of measure for the unavailable capacity. The unit may be MW for generation units or load and MVar for compensation means.
17 [0..1] unavailableCapacity_Quantity.quantity
Decimal
The quantity value. The association role provides the information about what is expressed. --- The quantity information associated to a TimeSeries. The unavailable capacity induced by the maintenance of the network element. This may be a generation unit, a load or a compensation mean.
Enter the unavailable capacity in MW for generation units/consumers and in Mvar for compensation elements (IND, CAP).
18 [1..1] day_MarketObjectStatus.status
Status_String
The coded condition or position of an object with regard to its standing. --- When attribute has the "Active" value, the maintenance is only done during day ligth time.
To be marked with "A05" if the outage or special switching state is repeated every day referring to the specified times or marked with "A03" if outage is continuously
19 [0..1] week_MarketObjectStatus.status
Status_String
The coded condition or position of an object with regard to its standing. --- When attribute has the "Active" value, the maintenance is only done from Monday to Friday included.
20 [0..1] saturday_MarketObjectStatus.status
Status_String
The coded condition or position of an object with regard to its standing. --- When attribute has the "Active" value, the maintenance s done on Saturday.
21 [0..1] sunday_MarketObjectStatus.status
Status_String
The coded condition or position of an object with regard to its standing. --- When attribute has the "Active" value, the maintenance s done on Sunday.
807
Table 21 shows all association ends of TimeSeries with other classes. 808
– Page 46 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Table 21 - Association ends of Network element maintenance scheduling document 809 assembly model::TimeSeries with other classes 810
Order
mult.
Class name / Role Description
22 [0..*] Reason
Reason
The coordination status of the case-study. The status may be requested, rejected or confirmed. Association Based On: Network element maintenance scheduling document contextual model::Reason.Reason[0..*] ----- Network element maintenance scheduling document contextual model::TimeSeries.[]
23 [1..*] RegisteredResource
RegisteredResource
The identification of the network elemen-t object of the maintenance scheduling. Association Based On: Network element maintenance scheduling document contextual model::TimeSeries.[] ----- Network element maintenance scheduling document contextual model::RegisteredResource.RegisteredResource[1..*]
Enter the code which is used for the unique identification of this grid element.
24 [0..*] Alternative_RegisteredResource
Alternative_RegisteredResource
The identification of a resource associated with a TimeSeries. When used, this list contains alternative network element for the maintenance schedule. Association Based On: Network element maintenance scheduling document contextual model::Alternative_RegisteredResource.Alternative_RegisteredResource[0..*] ----- Network element maintenance scheduling document contextual model::TimeSeries.[]
If at least two elements are used alternatingly, both elements belong to the same case ID and an "X" is required in this column.
For "alternating" at least two elements must be used under one case ID. The first (upper) element is the element that should be handled as switched off during grid calculations.
25 [0..*] SwitchedBack_Time_Period
SwitchedBack_Period
The time interval associated with a TimeSeries within an elec tronic document. When such time intervals are provided, they states that during the maintenance period, the network elements will be back for operation during these time intervals. Association Based On: Network element maintenance scheduling document contextual model::SwitchedBack_Time_Period.SwitchedBack_Period[0..*] ----- Network element maintenance scheduling document contextual model::TimeSeries.[]
Enter all dates for when the unavailability does not exist.
811
812
813 814
– Page 47 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Unique identification of the configuration document being exchanged within a given business process flow.
1 [1..1]
type
MessageKind_String
The coded type of a document. The document type describes the principal characteristic of the document.
2 [1..1]
process.processType
ProcessKind_String
The identification of the nature of process that the document addresses.
3 [1..1]
sender_MarketParticipant.mRID
PartyID_String
The identification of a party in the energy market. --- Document owner.
4 [1..1]
sender_MarketParticipant.marketRole.type
MarketRoleKind_String
The identification of the role played by a market player. --- Document owner. --- The role associated with a MarketParticipant.
5 [1..1]
receiver_MarketParticipant.mRID
PartyID_String
The identification of a party in the energy market. --- Document recipient.
6 [1..1]
receiver_MarketParticipant.marketRole.type
MarketRoleKind_String
The identification of the role played by a market player. --- Document recipient. --- The role associated with a MarketParticipant.
7 [1..1]
createdDateTime
ESMP_DateTime
The date and time of the creation of the document.
ENTSO-E date and time format
Date and time formats shall be used according to the ENTSO-E standards described chapter 4.3.11 in the ESS-Guide (see https://www.entsoe.eu/fileadmin/user_upload/edi/library/schedulev2r3/documentation/ess-guide-v2r3.pdf)
847
Table 25 shows all association ends of Ref_MarketDocument with other classes. 848
– Page 51 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Table 25 - Association ends of Network outage configuration assembly 849 model::Ref_MarketDocument with other classes 850
Order mult. Class name / Role Description
8 [1..*] TimeSeries
TimeSeries
Association Based On: Network outage configuration contextual model::TimeSeries.TimeSeries[1..*] ----- Network outage configuration contextual model::Ref_MarketDocument.[]
851
Domain 852
A domain covering a number of related objects, such as market balance area, grid area, borders 853 etc. 854
Order mult. Attribute name / Attribute type Description
0 [1..1] mRID
PartyID_String
The identification of a party in the energy market.
864
Specific_RegisteredResource 865
A resource that is registered through the market participant registration system. Examples 866 include generating unit, load, and non-physical generator or load. 867
Table 28 shows all attributes of Specific_RegisteredResource. 868
A time series shall exist to describe a specific production unit, generating unit, transmission 873 asset or consumption unit. It conveys the data related to the configuration of the defined 874 information. 875
Order mult. Attribute name / Attribute type Description
0 [1..1] registeredResource.mRID
ResourceID_String
The unique identification of a resource. --- The identification of a resource associated with a TimeSeries. The network element to be configured.
1 [1..1] registeredResource.name
String
The name is any free human readable and possibly non unique text naming the object. --- The identification of a resource associated with a TimeSeries. The network element to be configured.
The long name for the grid element has to be provided.
The following naming convention should be used for new grid elements:
-- Substation: Voltage level (optional), name
-- Line: Voltage level (optional), Subst. 1, Subst.2, Subst. X , name (optional)
-- transformer: Voltage levels (optional), Subst., name
512 in future
2 [0..1] registeredResource.location.name
Characters200_String
The name is any free human readable and possibly non unique text naming the object. The location of the element for the outage. --- The identification of a resource associated with a TimeSeries. The network element to be configured. --- Location of this power system resource.
specification of the location of the unavailable grid element
free text, no restrictions
3 [1..1] registeredResource.pSRType.psrType
PsrType_String
The coded type of a power system resource. --- The identification of a resource associated with a TimeSeries. The network element to be configured. --- The identification of the type of resource associated with this RegisteredResource.
The bus bar's high voltage limit --- The identification of a resource associated with a TimeSeries. The network element to be configured. --- The identification of the type of resource associated with this RegisteredResource. --- The voltage level of the RegisteredResource having the MktPSRType
- For an internal overheadline or cable (LINE): xxx
– Page 53 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
The bus bar's low voltage limit --- The identification of a resource associated with a TimeSeries. The network element to be configured. --- The identification of the type of resource associated with this RegisteredResource. --- The voltage level of the RegisteredResource having the MktPSRType. - For a transformer (TRA): xxx/xxx
6 [0..1] cancelledTS
ESMPBoolean_String
An indicator stating that the TimeSeries, identified by the mRID, is withdrawn as well as all the values sent in a previous version of the TimeSeries in a previous document.
7 [0..1] description
String
Any other information about the network element defined by the mRID of the RegisteredResource. The description is a free human readable text describing or naming the object. It may be non unique and may not correlate to a naming hierarchy.
8 [1..1] owner_MarketParticipant.mRID
PartyID_String
The identification of a party in the energy market. --- The party who provides the information related to the RegisteredResource outage.
TSO that is responsible for reference data maintenance and can send cases (outage planning/availability data for this element).
Exception:
If the element type is TIE more than one TSO can be listed here. The following rules are applicable:
- The TSO, that is listed first is responsible for reference data management
- All TSOs listed under "responsible" can send cases (outage planning/availability data for this element).
- All TSOs listed under "responsible " must be listed under "coordination" as well. (Important for filtering purposes and for coordination process via OPC)
9 [1..1] startLifetime_DateAndOrTime.date
Date
The date as "YYYY-MM-DD", which conforms with ISO 8601. --- The date when the network element was put in service.
10 [0..1] endLifetime_DateAndOrTime.date
Date
The date as "YYYY-MM-DD", which conforms with ISO 8601. --- The date when the network element will be withdrawn of service.
11 [0..1] implementation_DateAndOrTime.date
Date
The date as "YYYY-MM-DD", which conforms with ISO 8601. --- The date of application of the information provided. This identifies the date of the effective implementation of the information provided in the time series. In the case of a creation this signifies that the object will be operational at this date. In the case of modification this signifies that the changes will be operational at this date. In the case of a deactivation this signifies that the deactivation will be effective at this date.
– Page 54 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Order mult. Attribute name / Attribute type Description
12 [0..1] active_Measurement_Unit.name
MeasurementUnitKind_String
The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit for active generation or consumption.
13 [0..1] installedGeneration_Quantity.quantity
Decimal
The quantity value. The association role provides the information about what is expressed. --- The quantity information associated to a TimeSeries. For a generating unit, the installed generation capacity.
- Capacity in [MW] for generation and consumption units
- Capacity in [Mvar] for compensation elements such as CAP and IND
- negative sign ("-") must be used for consumption units and IND; generation units and CAP are given as positive value
14 [0..1] installedConsumption_Quantity.quantity
Decimal
The quantity value. The association role provides the information about what is expressed. --- The quantity information associated to a TimeSeries. For a consumption unit, the installed consumption capacity.
15 [0..1] installedReactive_Quantity.quantity
Decimal
The quantity value. The association role provides the information about what is expressed. --- The quantity information associated to a TimeSeries. For a unit, the reactive capacity.
16 [0..1] reactive_Measurement_Unit.name
MeasurementUnitKind_String
The identification of the formal code for a measurement unit (UN/ECE Recommendation 20). --- The unit for reactive power.
17 [0..1] multipod_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. The network element which is within the multipod.
Enter the element ID which is used for the unique identification of the multipod.
878
Table 30 shows all association ends of TimeSeries with other classes. 879
– Page 55 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Table 30 - Association ends of Network outage configuration assembly 880 model::TimeSeries with other classes 881
Order
mult.
Class name / Role Description
18 [1..*] Domain
Domain
The domain where the resource object associated with a TimeSeries resides. Association Based On: Network outage configuration contextual model::Domain.Domain[1..*] ----- Network outage configuration contextual model::TimeSeries.[]
19 [0..*] Other_MarketParticipant
Coordination_MarketParticipant
The list of parties who are involved in the coordination outage process Association Based On: Network outage configuration contextual model::Other_MarketParticipant.Coordination_MarketParticipant[0..*] ----- Network outage configuration contextual model::TimeSeries.[]
20 [0..*] Other_MarketParticipant
Interested_MarketParticipant
The list of parties that are interested in information about outage of the network element object of the TimeSeries. These parties shall be notified that a case or a change to a case for an element was uploaded/inserted. Association Based On: Network outage configuration contextual model::Other_MarketParticipant.Interested_MarketParticipant[0..*] ----- Network outage configuration contextual model::TimeSeries.[]
21 [0..*] Specific_RegisteredResource
Specific_RegisteredResource
The identification of a resource associated with a TimeSeries. The list of network elements that have a specific relationship to the network element object of this configuration. Association Based On: Network outage configuration contextual model::Specific_RegisteredResource.Specific_RegisteredResource[0..*] ----- Network outage configuration contextual model::TimeSeries.[]
882
883
– Page 56 of 64 –
European Network of Transmission System Operators for Electricity
ENTSO-E Outage Business Process and Format VERSION 1.0
Table 61 - Restrictions of attributes for ESMPDataTypes::YMDHM_DateTime 1065
Name Constraint Type Expression of constraint
value pattern OCL inv: self->Pattern(((([0-9]{4})[\-](0[13578]|1[02])[\-](0[1-9]|[12][0-9]|3[01])|([0-9]{4})[\-]((0[469])|(11))[\-](0[1-9]|[12][0-9]|30))T(([01][0-9]|2[0-3]):[0-5][0-9])Z)|(([13579][26][02468][048]|[13579][01345789](0)[48]|[13579][01345789][2468][048]|[02468][048][02468][048]|[02468][1235679](0)[48]|[02468][1235679][2468][048]|[0-9][0-9][13579][26])[\-](02)[\-](0[1-9]|1[0-9]|2[0-9])T(([01][0-9]|2[0-3]):[0-5][0-9])Z)|(([13579][26][02468][1235679]|[13579][01345789](0)[01235679]|[13579][01345789][2468][1235679]|[02468][048][02468][1235679]|[02468][1235679](0)[01235679]|[02468][1235679][2468][1235679]|[0-9][0-9][13579][01345789])[\-](02)[\-](0[1-9]|1[0-9]|2[0-8])T(([01][0-9]|2[0-3]):[0-5][0-9])Z))
value TruncationOrReduced INV choice=gYearMonthDayHourMinute