ID | Area /Domain(s)/Zone(s) | Name of the Use Case |
---|---|---|
1 | Distribution Management, Users, Distribution System, Real-Time Operation, Transmission System, Energy systems, | edf-2 |
Version No. | Date | Name of author(s) | Changes | Approval status |
---|---|---|---|---|
1 | 2018-08-13T00:00:00 | Francisco Reis & Gonçalo Glória [R&D Nester], | Approved Version |
Scope | The exchange of real time data/information in the observability area between TSO’s and DSO’s |
Objective(s) | Increase observability areas of both TSO and DSO on each other networks, expanding the set of signals (measurements, states …) exchanged in real-time, as well as improving data exchange structure/normalization. Enlarge real-time data exchanged between TSO and DSO for improved supervision and control of their own networks. |
Related business case(s) | ecaa3f43-fc46-4e0c-ae3b-74d9a95ab3b7 45f1db00-6691-479d-b2d3-e7951635afe5 |
Short description
This SUC describes the process to define the exchange of signal/information (measurements, states, … ) between the TSOs and DSOs. Two scenarios are described: one to send the real-time information and another to request the real-time information.
Complete description
The exchange of real-time information between TSO and DSO is essential to real-time control and supervision of the power system. Although it is a usual practice between transmission and distribution operators, it should be revised and improved given the importance that has in the operation of both grids.
The definition of the standardized method to request and send measurements along with setting up a methodology to define the right observability areas of both TSO and DSO at each other networks and by expanding the set of signals (measurements, states …) exchanged are some of the enhancements that this SUC provides.
In the case of Portuguese field test, the exchange of real-time information will use Inter-Control center Communication Protocol (ICCP) in order to allow the communication between TSO and DSO SCADAs. However, other solutions can be adopted.
ID | Name | Description | Reference to mentioned use case objectives |
---|---|---|---|
1 | TSO’s state estimator accuracy (%) | d2fe406c-96f7-4d01-a8ed-72037a66d16b, 553a6680-12e7-44a9-9bc8-b38fddc07f06, |
Assumptions |
---|
TSO and DSO degree of cooperation includes having a certain level of observability over each other networks. |
Prerequisites |
---|
TSO records information on the state of operation of the transmission network (measurements, state of operation of the equipment, etc…). |
Relation to other use cases |
---|
SUC |
Level of depth |
Prioritisation |
High |
Generic, regional or national relation |
Generic |
Nature of the use cases |
SUC |
Further keywords for classification |
Real-time operation, TSO-DSO information exchange, Observability area |
General remarks |
---|
Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
---|---|---|---|
Data exchange platform | System | Platform used by several power system actors to exchange information for different proposes. Three types of data (real-time, scheduled and structural data) can be exchanged through this platform. The operational/control data are not included in real-time type. The exchange of information related with the markets are included in the scheduled data. The platform is a data-agnostic ICT infrastructure that enables a secure and reliable information exchange for different purposes (long-term planning, operational planning, contingencies, …) and within different time scales. | |
Network Operation | System | The Network Operation function includes business activity directly involved with monitoring and operating the power grid as a whole system.
In the presented SUCs, the Network Operation function can refer to either the analysis tools used by TSOs or DSOs. |
No. | References Type | Reference | Status | Impact on Use Case | Organistaor / Organisation | Link |
---|
No. | Scenario Name | Scenario Description | Primary Actor | Triggering Event | Pre-Condition | Post-Condition |
---|---|---|---|---|---|---|
1 | Request Real-time information | In this scenario it’s described the main flux of the activities to request real time information from the observability area that is already stored or not in the data exchange platform. | Every 5 seconds (or other value defined between TSO and DSO) | |||
2 | Send Real-time information | This scenario describes the flux of the main activities to send information from the SO (TSO or DSO) to the data exchange platform | Every 5 seconds (or other value defined between TSO and DSO) |
Notes
Scenario Name: |
---|
Request Real-time information |
Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
---|---|---|---|---|---|---|---|---|
1.1 | Request Real-Time information in the observability area | The SO should request the information in each node in the defined observability area Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | 395198ac-5a33-430c-b38b-5c94bb593604 | 41fe759a-eccc-4e9c-8d5a-427a3550e8e1 | fe8283d0-3bde-4b21-8111-06a651699053 | |||
1.2 | Organisation of the requested information | The information stored in the data exchange platform should organize all the information in the observability area to send to the SO Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | 41fe759a-eccc-4e9c-8d5a-427a3550e8e1 | 395198ac-5a33-430c-b38b-5c94bb593604 | 72c603c9-727f-476f-a60b-66d58c6964f3 | |||
1.3 | Real-time information acknowledge | Acknowledge by the SO of the information sent. | 395198ac-5a33-430c-b38b-5c94bb593604 |
Scenario Name: |
---|
Send Real-time information |
Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
---|---|---|---|---|---|---|---|---|
2.1 | Network real-time data collection | SO (TSO or DSO) collects real-time data on its own network and aggregates it whenever necessary. | 395198ac-5a33-430c-b38b-5c94bb593604 | |||||
2.2 | Real-time information exchange with the DSO | SO send real-time information to the data exchange platform, limited to the defined observability. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | 395198ac-5a33-430c-b38b-5c94bb593604 | 41fe759a-eccc-4e9c-8d5a-427a3550e8e1 | 72c603c9-727f-476f-a60b-66d58c6964f3 | |||
2.3 | Real-time measurements acknowledge | Real-time information acknowledged by Data Exchange Platform. | 41fe759a-eccc-4e9c-8d5a-427a3550e8e1 |
Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
---|---|---|---|
fe8283d0-3bde-4b21-8111-06a651699053 | Request measurements in the observability area | The request of information can be done in two different ways: 1: Observability area ID Time (not defined means the last one) (day; hour; minutes; seconds) 2: Bus ID Line ID Power Transformer ID SGU ID Time (not defined means the last one) (day; hour; minutes; seconds) | —- |
72c603c9-727f-476f-a60b-66d58c6964f3 | Send measurements in the observability area | Send the measurements in the observability area to the data exchange platform. Observability area ID Time (day; hour; minutes; seconds) Bus ID P(MW) Q(MVAr) U(kV) Voltage Angle (°) Observability area ID Time (day; hour; minutes; seconds) Line ID P(MW) Q(MVAr) Observability area ID Time (day; hour; minutes; seconds) Power Transformer ID P(MW) Q(MVAr) U1(kV) U2(kV) OLTC Observability area ID Time (day; hour; minutes; seconds) SGU ID P(MW) Q(MW) | —- |
Key | Value | Refers to Section |
---|