<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Coordination Platform for Handling Emergencies and Restoration of Power Grid</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Dušan Popadić</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marko Batić</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute Mihajlo Pupin, University of Belgrade</institution>
          ,
          <addr-line>Belgrade</addr-line>
          ,
          <country country="RS">Serbia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>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. 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 efficiently.</p>
      </abstract>
      <kwd-group>
        <kwd>Power grid</kwd>
        <kwd>Coordination</kwd>
        <kwd>Transmission service operator</kwd>
        <kwd>Generation unit</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        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 [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. 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
separate use cases and their sub-cases:



      </p>
      <sec id="sec-1-1">
        <title>Dispatch order</title>
        <p>o Balancing order
o Availability and readiness</p>
      </sec>
      <sec id="sec-1-2">
        <title>Critical information exchange</title>
        <p>o Event
o Warning</p>
      </sec>
      <sec id="sec-1-3">
        <title>Defence plan coordination These use cases shall be integrated as a part of the Coordination platform developed in the TRINITY project framework. An overview of actors and use cases can be seen in Figure 1.</title>
        <p>Market
Enterprise
Operation
Station
«Logical Actor»
GEN GROUP OPERATOR
(from
Actors)
«Logical Actor»
GEN OPERATOR
(from</p>
        <p>Actors)
«Logical Actor»
GEN OPERATOR
400/220
(from
Actors)
«Logical Actor»
GEN OPERATOR 110
(from
Actors)
«Logical Actor»
TSO OPERATOR
(from
Actors)
«Logical Actor»
ADJACENT TSO
OPERATOR
(from
Actors)
«Primary Use Case»
HLUC4.19 - UC 1 Balancing</p>
        <p>Order</p>
        <p>Emergency Information Exchange (UC 4.19)
«Primary Use Case»
HLUC 4.19 - UC 3 Defence Plan</p>
        <p>Preparation
«Primary Use Case»
HLUC4.19 - UC 2 Critical
Information Exchange
«Logical Actor»
TSO RDC OPERATOR
(from
Actors)
«Logical Actor»
RSC OPERATOR
(from
Actors)
«Logical Actor»
DSO OPERATOR
(from
Actors)</p>
      </sec>
      <sec id="sec-1-4">
        <title>Overview of use cases</title>
        <p>2</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Solution</title>
      <p>
        The Coordination platform is based on the OperatorFabric [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] which supports sending
notifications to users in form of cards. The platform is web based application for
reliable and secure communication and coordination that utilize the OAuth2 protocol [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]
for authorization and thus ensure that only authorized people can access this sensitive
process.
2.1
      </p>
      <sec id="sec-2-1">
        <title>Balancing order</title>
        <p>TSO operator can use the coordination platform to create and sent balancing (di
spatch) order s to generation units or balancing service providers with , for instance, a
request to increase or decrease the power production. Balancing order s can be issued
manually through the platform using a predefined form or automatically by a third
party soft ware used by TSO. A Balancing order contain s information about the type
and amount of change in the concerned period and, optionally, a comment. The
operator can validate or reject the request via GUI as shown in Figure 2.</p>
        <sec id="sec-2-1-1">
          <title>Balancing order card</title>
          <p>In case the order is generated automatically, an xml file containing all relevant
information 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.</p>
          <p>An UML sequence diagram of communication between interested parties is shown
in Figure 3.</p>
          <p>sd Sequence diagram</p>
          <p>
            «Logical Actor»
GEN OPERATOR 400/220
(from Actors)
par
[
            <xref ref-type="bibr" rid="ref1">1</xref>
            ]
[
            <xref ref-type="bibr" rid="ref2">2</xref>
            ]
[
            <xref ref-type="bibr" rid="ref3">3</xref>
            ]
          </p>
          <p>Dispatch order()
Answer to the</p>
          <p>request
(accept/reject)
«Logical Actor»
TSO OPERATOR
(from Actors)
«Logical Actor»
TSO RDC OPERATOR
(from Actors)
«Logical Actor»
GEN OPERATOR 110</p>
          <p>(from Actors)
Dispatch order()
Answer to the request</p>
          <p>(accept/reject)
Notification about taken
actions()</p>
          <p>Dispatch order()
Answer to the request</p>
          <p>(accept/reject)</p>
          <p>Dispatch order (in case of
emergency or jeopardized grid</p>
          <p>security)
Answer to the request()
1 xmlns=”urn:entsoe.eu:wgedi:errp:activativatondocument:5:0”</p>
        </sec>
        <sec id="sec-2-1-2">
          <title>Line</title>
        </sec>
        <sec id="sec-2-1-3">
          <title>Transformer</title>
        </sec>
        <sec id="sec-2-1-4">
          <title>Generator</title>
        </sec>
        <sec id="sec-2-1-5">
          <title>Busbar</title>
        </sec>
        <sec id="sec-2-1-6">
          <title>Coupler</title>
        </sec>
        <sec id="sec-2-1-7">
          <title>Substation</title>
        </sec>
        <sec id="sec-2-1-8">
          <title>Tripping</title>
        </sec>
        <sec id="sec-2-1-9">
          <title>Power shortfall</title>
        </sec>
        <sec id="sec-2-1-10">
          <title>Events identified:</title>
          <p>Types of warnings:


















2.2</p>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>Availability and readiness</title>
        <p>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
unplanned outages (e.g. maintenance). It is done using the coordination platform’s
predefined form. TSO only acknowledges that the notification is received.
2.3</p>
      </sec>
      <sec id="sec-2-3">
        <title>Critical information exchange</title>
        <p>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
providing the information should include the type and the name of element concerned, the
type of event/warning and its description.</p>
        <sec id="sec-2-3-1">
          <title>Types of elements identified:</title>
          <p></p>
        </sec>
        <sec id="sec-2-3-2">
          <title>Overload due to unexpected high load flow</title>
        </sec>
        <sec id="sec-2-3-3">
          <title>Overload due to unexpected disconnection of other element</title>
        </sec>
        <sec id="sec-2-3-4">
          <title>Unexpected high flows</title>
        </sec>
        <sec id="sec-2-3-5">
          <title>N-1 violation</title>
        </sec>
        <sec id="sec-2-3-6">
          <title>Low voltage level</title>
        </sec>
        <sec id="sec-2-3-7">
          <title>High voltage level</title>
        </sec>
        <sec id="sec-2-3-8">
          <title>Shortage of power reserves</title>
        </sec>
        <sec id="sec-2-3-9">
          <title>High wind generation</title>
        </sec>
        <sec id="sec-2-3-10">
          <title>Bad weather conditions</title>
        </sec>
        <sec id="sec-2-3-11">
          <title>Activation of exceptional contingencies Disturbance of control system infrastructure (e.g. IT, building)</title>
          <p>The receiving party only acknowledges the receipt of that the notification is
received.</p>
        </sec>
      </sec>
      <sec id="sec-2-4">
        <title>Defence plan</title>
        <p>TSO uses predefined form in the coordination platform to inform the generation units
about new frequency set point values.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>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.</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgement</title>
      <p>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
Technological Development of Republic of Serbia.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Dalal</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gilboa</surname>
            <given-names>E</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mannor</surname>
            <given-names>S.</given-names>
          </string-name>
          :
          <source>Proceedings of The 33rd International Conference on Machine Learning</source>
          , PMLR
          <volume>48</volume>
          :
          <fpage>2197</fpage>
          -
          <lpage>2206</lpage>
          (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>J. R.</given-names>
            <surname>Roncero</surname>
          </string-name>
          ,
          <article-title>"Integration is key to Smart Grid management,"</article-title>
          <source>CIRED Seminar</source>
          <year>2008</year>
          :
          <article-title>SmartGrids for Distribution</article-title>
          ,
          <year>2008</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>4</lpage>
          , doi: 10.1049/ic:20080430
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. OperatorFabric, https://opfab.github.io/,
          <source>last accessed May 07</source>
          ,
          <year>2021</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Baker</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          , “
          <article-title>Applying Spring Security Framework and OAuth2 To Protect Microservice Architecture API”</article-title>
          .
          <source>Journal of Software</source>
          vol.
          <volume>14</volume>
          (
          <year>2019</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>