=Paper=
{{Paper
|id=Vol-3195/paper9
|storemode=property
|title=Coordination Platform for Handling Emergencies and Restoration of Power Grid
|pdfUrl=https://ceur-ws.org/Vol-3195/paper9.pdf
|volume=Vol-3195
|authors=Dušan Popadić,Marko Batić
}}
==Coordination Platform for Handling Emergencies and Restoration of Power Grid==
https://ceur-ws.org/Vol-3195/paper9.pdf
Coordination Platform for Handling Emergencies and
Restoration of Power Grid
Dušan Popadić1 and Marko Batić1
1
Institute Mihajlo Pupin, University of Belgrade, Belgrade, Serbia
dusan.popadic@pupin.rs
Abstract. Transmission service operators (TSOs), regional security centres
(RSCs), distribution service operators (DSOs), generation units (GUs) and bal-
ancing service providers (BSPs) need quick and reliable way of communication
in order to secure power grid balance. They need to exchange information about
grid stability, problems on the grid and defence plans in an easy and traceable
way. This paper presents a software solution for handling these situations effi-
ciently.
Keywords: Power grid, Coordination, Transmission service operator, Genera-
tion unit.
1 Introduction
Transmission service operators (TSOs), regional security centres (RSCs), distribution
service operators (DSOs), generation units (GUs) and balancing service providers
(BSPs) need quick and reliable way of communication in order to secure power grid
balance [1, 2]. They need to exchange information about grid stability, problems on
the grid and defence plans in an easy and traceable way. This paper covers three sepa-
rate use cases and their sub-cases:
Dispatch order
o Balancing order
o Availability and readiness
Critical information exchange
o Event
o Warning
Defence plan coordination
These use cases shall be integrated as a part of the Coordination platform devel-
oped in the TRINITY project framework. An overview of actors and use cases can be
seen in Figure 1.
Copyright © 2021 for this paper by its authors. Use permitted under Creative Com-
mons License Attribution 4.0 International (CC BY 4.0).
uc HL Use Case 4.19
Generation Transmission Distribution DER Customer Premise
Market
Emergency Information Exchange (UC 4.19)
Enterprise
«Primary Use Case»
HLUC4.19 - UC 1 Balancing
Order
«Logical Actor»
GEN GROUP OPERATOR
(from
Actors)
«Primary Use Case»
Operation
HLUC 4.19 - UC 3 Defence Plan
Preparation
«Logical Actor»
TSO RDC OPERATOR
«Logical Actor»
TSO OPERATOR (from
Actors)
(from
Actors)
«Primary Use Case»
HLUC4.19 - UC 2 Critical «Logical Actor»
Information Exchange DSO OPERATOR
«Logical Actor» (from
GEN OPERATOR Actors)
(from
Actors)
«Logical Actor»
RSC OPERATOR
(from
«Logical Actor» Actors)
«Logical Actor» «Logical Actor» ADJACENT TSO
GEN OPERATOR GEN OPERATOR 110 OPERATOR
400/220 (from (from
(from Actors) Actors)
Station Actors)
Field
Process
Fig. 1. Overview of use cases
2 Solution
The Coordination platform is based on the OperatorFabric [3] which supports sending
notifications to users in form of cards. The platform is web based application for reli-
able and secure communication and coordination that utilize the OAuth2 protocol [4]
for authorization and thus ensure that only authorized people can access this sensitive
process.
2.1 Balancing order
TSO operator can use the coordination platform to create and sent balancing (dis-
patch) orders to generation units or balancing service providers with, for instance, a
request to increase or decrease the power production. Balancing orders can be issued
manually through the platform using a predefined form or automatically by a third
party software used by TSO. A Balancing order contains information about the type
and amount of change in the concerned period and, optionally, a comment. The opera-
tor can validate or reject the request via GUI as shown in Figure 2.
Fig. 2. Balancing order card
In case the order is generated automatically, an xml file containing all relevant in-
formation is posted to the file server. The coordination platform downloads the file
from the server, parses it (extracts relevant information) and then creates notification
for the receiver. The xml file is formatted according to the ENTSO-E1 standard.
An UML sequence diagram of communication between interested parties is shown
in Figure 3.
sd Sequence diagram
«Logical Actor» «Logical Actor» «Logical Actor» «Logical Actor»
GEN OPERATOR 400/220 TSO OPERATOR TSO RDC OPERATOR GEN OPERATOR 110
(from Actors) (from Actors) (from Actors) (from Actors)
par
[1] Dispatch order()
Answer to the
request
(accept/reject)
[2]
Dispatch order()
Dispatch order()
Answer to the request
(accept/reject)
Answer to the request
(accept/reject)
[3]
Dispatch order (in case of
emergency or jeopardized grid
security)
Notification about taken Answer to the request()
actions()
Fig. 3. Balancing order sequence
1
xmlns=”urn:entsoe.eu:wgedi:errp:activativatondocument:5:0”
2.2 Availability and readiness
Generation units or regional operators as parts of a TSO can inform the TSO operator
about availability of generation units in certain periods of time due to planned or un-
planned outages (e.g. maintenance). It is done using the coordination platform’s pre-
defined form. TSO only acknowledges that the notification is received.
2.3 Critical information exchange
A user of the platform can inform other user(s) about an event that occurred on the
grid or warn them about a potentially problematic situation. The user who is provid-
ing the information should include the type and the name of element concerned, the
type of event/warning and its description.
Types of elements identified:
Line
Transformer
Generator
Busbar
Coupler
Substation
Events identified:
Tripping
Power shortfall
Types of warnings:
Overload due to unexpected high load flow
Overload due to unexpected disconnection of other element
Unexpected high flows
N-1 violation
Low voltage level
High voltage level
Shortage of power reserves
High wind generation
Bad weather conditions
Activation of exceptional contingencies
Disturbance of control system infrastructure (e.g. IT, building)
The receiving party only acknowledges the receipt of that the notification is re-
ceived.
2.4 Defence plan
TSO uses predefined form in the coordination platform to inform the generation units
about new frequency set point values.
3 Conclusion
In this paper a coordination platform for handling emergencies and restoration in
power grid was presented. Coordination platform allows operators to communicate
quickly, easily and reliably in critical situation. Since the purpose of the platform is to
help during the emergencies, it is planned for it to be further developed to support
situations when the grid split or part of the grid goes to the blackout.
Acknowledgement
The research presented in this paper is partly financed by the European Union (H2020
TRINITY project, Pr. No: 863874) and partly by the Ministry of Science Technologi-
cal Development of Republic of Serbia.
References
1. Dalal, G., Gilboa E, Mannor S.: Proceedings of The 33rd International Conference on Ma-
chine Learning, PMLR 48:2197-2206 (2016).
2. J. R. Roncero, "Integration is key to Smart Grid management," CIRED Seminar 2008:
SmartGrids for Distribution, 2008, pp. 1-4, doi: 10.1049/ic:20080430
3. OperatorFabric, https://opfab.github.io/, last accessed May 07, 2021.
4. Nguyen, Q., Baker, O., “Applying Spring Security Framework and OAuth2 To Protect
Microservice Architecture API”. Journal of Software vol. 14 (2019)