Inside a modern substation, intelligent electronic devices no longer trade trip signals over dedicated copper wires. They publish them as GOOSE messages on the station Ethernet. GOOSE, short for Generic Object Oriented Substation Event, is the part of IEC 61850 built for speed: it moves a breaker trip or an interlock status from one relay to another in milliseconds, fast enough to replace hardwired protection signaling. This guide explains what a GOOSE message actually is, why it deliberately skips the normal networking stack, and how it differs from the slower client-server traffic that IEC 61850 uses for everyday SCADA data.
GOOSE Message in one line: An IEC 61850 GOOSE message is a fast, publish-subscribe, layer-2 Ethernet multicast that carries time-critical status between substation IEDs - most importantly protection trips and interlocking signals. It is published to a multicast group address rather than sent to one recipient over TCP/IP, which lets any subscribed device receive it within a few milliseconds without connection setup or acknowledgments.
A GOOSE message is a raw Ethernet frame. It carries its own EtherType and rides directly on the data-link layer, with no IP header, no TCP, and no ports. That is a deliberate design choice. TCP/IP adds connection setup, sequencing, and acknowledgment handshakes that each cost time, and for a protection trip a few extra milliseconds can matter. By publishing at layer 2, a device can put the message on the wire the instant an event occurs and let the switching fabric fan it out immediately.
The model is publish-subscribe rather than request-response. A publishing IED does not address the message to a specific relay; it sends it to a multicast group, and every device configured to subscribe to that group receives it. One published trip can therefore reach several downstream relays at once. There is no client asking for the data and no server replying - the publisher simply announces the event, and interested subscribers act on it. This decoupling is what lets a single protection event ripple through interlocking logic across many devices without any of them polling each other.
Because GOOSE is a multicast that any subscribed device receives, station engineers isolate and prioritize it so it does not flood the network or get delayed behind ordinary traffic. GOOSE frames typically carry an IEEE 802.1Q VLAN tag, which does two jobs at once: the VLAN identifier confines the multicast to a defined segment of the network so it is not broadcast everywhere, and the priority field marks the frame as high priority so managed switches forward it ahead of best-effort data.
This is why substation LAN design and GOOSE reliability are inseparable. Managed switches with multicast filtering and priority queuing keep trip messages moving quickly and prevent a storm of GOOSE traffic from reaching devices that have no interest in it. Get the VLAN and priority configuration wrong and a trip can arrive late, or the network can be swamped by multicast that should have been contained. In practice, commissioning a GOOSE scheme means configuring the publishers, the subscribers, and the switches together as one system.
IEC 61850 actually defines two very different communication styles, and it helps to keep them apart. GOOSE is the fast, peer-to-peer, event-driven multicast used for protection and interlocking between IEDs. MMS, the Manufacturing Message Specification, is the slower client-server channel that a SCADA master or gateway uses to poll measurements, read status, browse the data model, and issue commands. MMS runs over TCP/IP with connections and confirmations; GOOSE runs on layer 2 with none. One is built for millisecond trips inside the substation, the other for orderly supervisory data exchange.
For a control room or a cloud platform, that split has a practical consequence. GOOSE lives on the substation station bus and generally stays there - it is not something a cloud SCADA system subscribes to directly across a wide-area link, because layer-2 multicast does not route and because its timing guarantees only hold on the local fabric. Instead, a substation gateway speaks MMS to the IEDs, or maps the relevant points to a protocol such as IEC 60870-5-104, and forwards the resulting values upstream. A cloud SCADA platform such as Merobix then monitors those forwarded measurements, breaker states, and event records for trends, alarms, and reporting, while the millisecond protection decisions themselves stay where they belong: on GOOSE, inside the station.
GOOSE carries time-critical protection signals, and TCP/IP adds connection setup, sequencing, and acknowledgment steps that each cost time. By running as a raw layer-2 Ethernet multicast, a device can publish a trip the instant an event happens and let switches fan it out in a few milliseconds. The reliability that TCP would normally provide is achieved instead through rapid retransmission of the GOOSE message.
GOOSE is fast, peer-to-peer, event-driven layer-2 multicast used for protection trips and interlocking between IEDs. MMS is client-server traffic over TCP/IP that a SCADA master or gateway uses to poll measurements, read status, and send commands. GOOSE is for millisecond events inside the substation; MMS is for orderly supervisory data exchange.
Not directly, because GOOSE is layer-2 multicast that does not route across a wide-area link and whose timing guarantees only hold on the local station network. A substation gateway instead speaks MMS to the IEDs or maps the relevant points to a routable protocol and forwards them upstream. A cloud platform then monitors those forwarded values and events rather than the raw GOOSE traffic.
Primary references from the standards bodies and regulators that define this topic:
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.