What does it mean by Generic Object Oriented Substation Events (GOOSE) via IEC 61850?

[Anonymous user]

IEC 61850 defines an abstract object model for substations and methods to access these objects on a network. The abstract object model represents the SAS functionality in terms of logical nodes (LN) within the logical devices that are allocated to the IEDs as the physical devices. The actual communication between IEDs is handled via common IEC 61850 protocols such as SV, MMS and GOOSE.

-Ankit Acharya

Healthcare Segment KAM

[Anonymous user · Accepted solution]

Hello @Anonymous user, 

Thanks for sharing this information.🙂

Any reference documentation or link to reference documentation or presentation to be shared?

[Yann_BV]

One big difference between IEC61850 and other protocols is the GOOSE (other stuff like SV and IEC61969 add on)...

GOOSE is a multicast message then send to ALL (I do not know other protocol with this feature), 

By itself, it is very fast as send at link layer without TCP repeat, high througput with 150 digital DataPoint with quality per frame (or less when it is measurement), and reliable (as repeated cyclically like any PLC).

Every IED can receive simultaneously a new change... also well adapted for distributed automation (immediate advise to all protections that get in emergency mode for example, or control uniqueness, load shedding, electric network reconfiguration...)

This open a change of mind for redundancy, for function backuping, and especially for distributed automation (and with possibly review IEC61499).

Another change of mind is the control (possible and powerfull in standard IEC 61850 mms) ... using GOOSE it is no more a message with later aknowledgment, but IED put a goose state asking in fact to execute action on other IEDs (ex inter-trip, backup protect)... others can send their own goose back with pseudo state telling running or acknowledgment... (not working with protection but with BCU or PLC)

Somewhere the DDB (Dynamic Data Base) is not into one device, but the DDB is on the whole Ethernet network (any IED reconnecting get all "critical" states in order to trigger immediatly its own PLC).