Scribd
Upload
104 views2 pages

Bad Habit of Using GGIO Logical Nodes

The document summarizes a study analyzing the use of GGIO logical nodes in IEC 61850 configuration files. The study analyzed 124 unique configuration files and found 316 device instances with 219 GOOSE messages and 836 report control blocks configured. The study concluded that utilities must understand that using GGIOs loses advantages of IEC 61850, application profiles should minimize GGIO usage, utilities must validate function implementation, and GGIOs must include project documentation.

Uploaded by

Alejandro B.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
104 views2 pages

Bad Habit of Using GGIO Logical Nodes

The document summarizes a study analyzing the use of GGIO logical nodes in IEC 61850 configuration files. The study analyzed 124 unique configuration files and found 316 device instances with 219 GOOSE messages and 836 report control blocks configured. The study concluded that utilities must understand that using GGIOs loses advantages of IEC 61850, application profiles should minimize GGIO usage, utilities must validate function implementation, and GGIOs must include project documentation.

Uploaded by

Alejandro B.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Tech Papers

Bad habit of using GGIO logical nodes


Alexander Golovin, Alexey Anoshin

There are quite a few people saying that GGIO is a bad thing. Having a good semantic model provided by
IEC 61850, it’s pretty silly to get rid of semantics by means of GGIO. However, it happens a lot due to
several reasons. We tried to investigate how relevant the problem is, and what are primary factors for that.

As an input for our analysis we have used 124 unique SCL files, including ICDs for individual IEDs as well
as SCD files for complete projects. There were 316 IED instances with 57 unique IED types. Finally, these
IEDs produced 219 GOOSE messages and had 836 Report control blocks configured.

Methodology
The data has been carefully collected and filtered out in order to get rid of duplicates, influencing final
investigation results. In order to process the data, including filtering and final analysis, we have used the
core of our IEC 61850 Telegram messenger bot with additional Python-based scripts providing the required
information.

We have analyzed 124 unique SCL files, including ICDs for individual IEDs as well as SCD files for
complete projects.

The overall database of SCL files at the beginning of the investigation have counted over 500+ files, so
careful filtering has been required in order to get rid of duplicates and different instances of the same
projects. The filtering has been performed in several stages. First, md5 hash has been calculated for each
file, so that files with repeating hash have been removed. Second, files have been validated against SCL-
schema (depending on the determined edition, respective schema has been used), so that only valid files
passed. Finally, SCL files’ header has been analyzed in order to exclude different versions of the same
project. Additionally, unique IED-type filtering has been applied in order to collect the data for IED-types
only.

We intentionally did not want to give preference to any kind of project, vendor or IED type, so we have
made completely “blind” analysis.

Conclusions
As previous parts of this paper were long enough, we do need to outline some conclusions to settle in our
minds:

· Utilities MUST understand that they are accepting blind systems with those GGIOs, loosing half of
the advantages of IEC 61850 compared to outdated communication protocols.
· Clear application profiles shall minimize the amount of GGIOs used in projects.
· Utilities must have means to check function implementation in accordance with the defined profile.
· While GGIOs are used, they must be well documented and include project specific descriptions.

Keeping this in mind, we will take the shortest path to the worldwide IEC 61850 understanding and
acceptance.

Author Author
Company: TEKVEL Ltd. Company: TEKVEL Ltd.
Position: Technical director Position: Executive Director
Alexander Golovin Alexey Anoshin

You might also like