goose messaging determining its potential in a real case · 2019-08-15 · red elÉctrica de...

May, 24th 2013 Carlos Rodríguez del Castillo – [email protected] Prague

Goose Messaging

Determining its potential in a real case

IEC 61850 Europe 2013 Conference by Phoenix Forums

mailto:[email protected]

May, 24th 2013 – IEC 61850 2013 Europe Conference, Prague

Index

1. Starting point

2. The LAN

3. Interoperability

4. Impact on protection logics

5. Monitoring, diagnosis and testing

6. Next steps and conclusions


RED ELÉCTRICA DE ESPAÑA

3 / 20

Starting point

q Nueva Tintaya and Socabaya 220 kV double bus bar substations

q Multivendor IEC 61850 station bus solution

m Up to twelve (12) different IED models/manufacturers interconnected

q No PRP in protection IEDs. PRP in telecontrol IEDs.

q Two independent Protective System for each bay

q Two independent Differential Bus Bar Protection IEDs

q Use of Goose as much as possible

q Use of MMS for telecontrol functions

q Traffic control over the network



4 / 20

Goose definition adoptions

q Each Goose message has a different AppID value

q Each Goose message has a different multicast address

q Each Goose message has a defined semantic GoID value

m GO_PP1_PS1: Goose message from Primary Protection Bay #1 to Secondary Protection Bat #1

m GO_PI1_PPBAxPSBA: Goose message from Breaker Protection Bay #1 to Bus Bar Protection IEDs

q Specific drawing schemes for each IED defining:

m Goose messages published by the IED

m Information received by Goose from other IEDs

m Link of IEC 61850 data reference with settings names and logic scheme inputs



5 / 20

LAN

q Protective System A and B will have independent LANs

q Trunk link between LANs for Supporting Functions in each bay

q Telecontrol between bay level and station level with PRP

q All communication between bays go through station level

q Traffic to be isolated in a per-LAN and per-bay basis

m Traffic inside a bay will not go out of the bay

m Traffic inside a Protective System will not go out to the other

Protective System (in the same bay)

q Use of VLAN to effectively route the Goose communication



6 / 20

LAN: Use of VLAN

q VLAN 1 for TCP/IP traffic including MMS and NO Goose

q Goose messaging classified by intercommunication meaning

m VLAN 2: Goose messaging between IEDs in the same Protective System

m VLAN 3: Goose messaging between IEDs in the same bay, different

Protective System

m VLAN 4: Goose messaging from bay IEDs to Bus Bar Protection IEDs

m VLAN 5: Goose messaging from Bus Bar Protection IEDs to bay IEDs

m VLAN 6, 7: Goose messaging between IEDs in HV/MV transformer bays



7 / 20

VLAN 1: General VLAN



8 / 20

VLAN 2: Intra Protective System Interchange



9 / 20

VLAN 3: Inter Bay Protective System Interchange



10 / 20

VLAN 4: From Bays to Bus Bar Protection IEDs



11 / 20

VLAN 5: From Bus Bar Protection IEDs to Bays



12 / 20

Interoperability

q Once configured, Goose interchange shows no interoperability problems

q Switches and VLAN concept works as expected

q The difficult issue is to come to a final configuration

m Each IED configuration tool works really different

m Feedback to each IED configuration tool with other IEDs CID file

m Difficulty to handle IED CID files changes: in some tools you have to re-do all the subscriptions of the IED because one IED CID file has changed

m Some tools do not work with CID files. Impossible to import the CID file of the IED to be configured, so you cannot create the subscriptions in a third-party tool

q We expect to improve with edition 2



13 / 20

Impact on protection logics

q Use of subscribe information in the protection logic has shown some issues:

m It is important to know how the logics are executed

m Subscribed information is read whenever is available plus some delay

m Subscribed information from different IEDs but generated at the same instant can be available in different logic cycles

m Could cause problems if some logic function depends on several information that comes from different sources

q Found potential problems when publishing Goose messages

m Sometimes, a change in the dataset is delayed until T1 time because of a previous change in the dataset. Is this an implementation issue?

m Current solution: Defines T1 as 1 millisecond

q No connection between IEC 61850 semantic and PLC variables



Configuration and Documentation

q Use of ATLAN tool to graphically define GOOSE interchange and their configuration

m Drawings showing GOOSE functionality

m GOOSE configuration carried out using built-in cid file editor

m Automatic cid and scd file generation from system design information

q Project documentation

m Seamless integration of physical and logical signals

m GOOSE documentation showing published info

m LAN and IED Communication parameters extracted from GOOSE configuration

m GOOSE subscription reports

14 / 20



15 / 20

Monitoring, diagnosis and testing

q Each subscription from an IED to a Goose message is monitored and sent to the telecontrol functions (via ACSI report service)

q Specific graphic pages have been developed in HMI functions

m At bay level At station level

q Diagnosis: Subscription problems are easily detected



16 / 20

Monitoring, diagnosis and testing

q IEDs manage Goose subscription status but with no semantic

q It is expected to improve with edition 2 LGOS logical node

q For testing

m Use of a relay test set for simulating Goose and IEDs

m Use of a relay test set to test switch VLAN configuration

m Use of a relay test set to generate event recorders of Goose specific data during functional test

m Use of special hand devices and Wire Shark to sniff Goose messages in the LAN

q For Functional Testing of a bay, Goose messages at bay level are transparent: you could do the tests in the same way as before



17 / 20

Conclusions

q The standardized way of defining Goose subscriptions in SCL must be a reality in tool implementations (system and IED tools)

q Isolating Goose messages reduce the impact on the traffic network

q Complying with total clearance time of a fault during FAT, but more exhaustive tests needs to be done

q Once Nueva Tintaya substation was configured, Socabaya took only two days

q Documentation process is simplified with ATLAN tool

q Goose messages help you know in real time when your system is unavailable (clear advantage versus wired systems)



18 / 20

Conclusions

q The wiring has been reduced in approximately 15%

61850 Bay cabinet Conventional bay cabinet

Conventional Diff Line Protection

61850 Diff Line Protection



19 / 20

Next steps

q Think about process bus for inputs/outputs and sampled values

q Advance in the Engineer Process definition for the future

q Study more in detail transfer times of Goose messages

q Study the reliability of the solution

q Move to edition 2, whenever it is available

q Advanced in the testing procedure

q Creation of troubleshooting guides for maintenance people

q Training courses for engineering and maintenance people

q Creation of a documentation set to be reused in other projects

q Try to automate the complete process



20 / 20

Thank you for your attention !!

Carlos Rodríguez del Castillo - [email protected]

mailto:[email protected]

goose messaging determining its potential in a real case · 2019-08-15 · red elÉctrica de...

Documents