Thinking Beyond Client-Server: How IEC 61850 Organizes and Moves Data

Ask ten automation people which protocol IEC 61850 is, and you’ll get ten answers. None of them wrong.

It isn’t one protocol. It’s one data model with three very different delivery trucks parked out back, and you pick the truck based on what the freight must do.

  • Manufacturing Message Specification (MMS): A traditional client-server messaging protocol used for SCADA, HMIs and configuration tools
  • Generic Object Oriented Substation Event (GOOSE): A high-speed, multicast messaging protocol that strips away the TCP/IP stack to deliver critical device-to-device commands
  • Sampled Values: A high-rate waveform data stream used to broadcast digitized voltage and current measurements from merging units

Get that straight and the rest of IEC 61850 stops being mysterious.

Everything Has an Address, and the Address Explains Itself

IEC 61850 organizes data in a strict hierarchy. Each layer narrows things down, and the full path tells you exactly what you’re looking at without a decoder ring.

  • Physical Device. The actual hardware. Nameplate, IP address, mounting screws.
  • Server. The communications entity living inside that hardware. It owns the address space clients browse.
  • Logical Device. A functional grouping within the server. One relay might present separate logical devices for protection, for control, for metering and for disturbance records. This matters enormously when a gateway or RTU is fronting a whole row of legacy equipment, because it can present each piece as its own logical device.
  • Logical Node. The smallest standardized unit of function. A circuit breaker. An overcurrent element. A measurement unit. A current transformer.
  • Data Object and Data Attribute. The information itself, plus its quality flag and its timestamp.

Logical nodes are where the real magic sits, and they’re named from a fixed vocabulary. A circuit breaker is XCBR. A three-phase measurement unit is MMXU. A time overcurrent protection function is PTOC.

Those names mean the same thing in an SEL relay, a GE relay, an ABB relay and a Siemens relay. That’s the multi-vendor problem solved at the root instead of papered over with translation tables.

Nobody Actually Reads Values One at a Time
Individual reads are the least interesting thing an IEC 61850 server does. If that’s all you’re using, you bought a Ferrari to haul mulch.

The real work runs through datasets. A dataset is just an ordered list of data attributes gathered from anywhere in the model, defined once, given a name and referenced from then on.

By itself, a dataset does nothing at all. It’s inert. It becomes useful when you attach it to a control block that decides how it gets delivered:

  • Report control blocks push the dataset to a client over MMS — on change, on a timer or when asked.
  • Log control blocks write it into a journal on the device that a client can go query later.
  • GOOSE control blocks multicast it as a GOOSE message.
  • Sampled Value control blocks publish it as a Sampled Value stream.

Same dataset. Four completely different destinies.

Buffered vs. Unbuffered Reporting

This distinction is small in the spec and enormous in the field.

An unbuffered report goes out if a client is listening. If the link is down, the event evaporates. Nobody ever knows it happened.

A buffered report queues events on the device while the client is gone and delivers the backlog when it reconnects. Your SCADA link drops for four minutes, comes back and the event sequence is intact.

If the data has any forensic, regulatory or “why did the plant trip at 3 a.m.” value, you want it buffered. I’ve watched people learn this lesson the expensive way.

Reporting is also configurable down to the trigger — data change, quality change, data update, integrity period — and every report carries a sequence number so the client can spot a gap. That’s a genuinely better event mechanism than the change-of-state polling most of our industrial protocols still lean on.

The Three Mappings: Choosing the Right Delivery Truck

Now let’s look closer at how those three delivery trucks actually operate.

MMS: The Client/Server One

MMS is the Manufacturing Message Specification, ISO 9506. It’s ancient. It came out of the MAP and TOP work back in the 1980s, when the industry was convinced one universal manufacturing protocol was right around the corner.

That never happened. But MMS had one property the IEC 61850 authors needed badly: it can carry arbitrary named object structures instead of fixed message layouts. MMS is what your HMI, your gateway and your engineering tools use. Connecting to a server, browsing the address space, reading and writing, control operations with select-before-operate, subscribing to reports, pulling logs, transferring files — that’s how a COMTRADE disturbance record gets off a relay.

It’s also the only one of the three that’s confirmed, connection-oriented and routable straight out of the box. That’s why it’s the mapping that leaves the substation heading toward the control center.

GOOSE: The One That Killed the Copper

GOOSE stands for Generic Object Oriented Substation Event, which is a mouthful that tells you nothing.

Here’s what it actually is: a publisher multicasts a dataset directly onto Ethernet. No IP. No TCP. No transport layer whatsoever. Subscribers filter on the multicast MAC address and an application ID and grab what they care about.

Stripping all that away is what makes it fast enough to carry a protection trip. It’s also why there’s no connection, no acknowledgment and no retry in any normal sense.

So how is it reliable? Repetition.

A publisher retransmits the same message continuously. When nothing is happening, it repeats slowly, every second or two, just idling along. The instant a value in the dataset changes, the publisher fires a burst of messages, then stretches the interval back out until it settles into the slow rhythm again.

The side effect is beautiful. Because the message never stops arriving, a subscriber knows the link is healthy. If the messages stop showing up on schedule, something is broken and the system knows immediately.

Think about what that replaced. A hardwired trip circuit sits there silently doing nothing until the day it’s needed, and if a technician nicked that conductor during a panel modification in 2019, you find out during a fault. GOOSE proves itself alive every second of every day.

Sampled Values: The Firehose

Sampled Values does for measurement what GOOSE did for tripping.

Instead of running current and voltage secondaries as analog signals from the switchyard all the way into the relay room, a merging unit sitting at the equipment digitizes the waveform right there and multicasts the samples.

The rates will get your attention. Protection typically runs 80 samples per cycle — 4,000 per second at 50 Hz, 4,800 at 60 Hz. Metering and power quality climb to 256 samples per cycle.

Every sample carries a count and a synchronization flag, and every publisher has to be locked to a common time reference. This is the one place in IEC 61850 where precise time sync stops being a nice-to-have. Two merging units feeding a differential scheme have to sample the identical instant. Miss that and the protection sees a difference that doesn’t exist, and acts on it.

Client/Server vs. Publisher/Subscriber

If you take one thing away, take this.
With MMS, a client reaches out, establishes communications with a server, and the two exchange information. Someone asked, someone answered.

With GOOSE and Sampled Values, information is thrown onto the network and whoever was configured to want it picks it up. Nobody asked. Nobody answered.

Those are answers to different questions. A SCADA system collecting trend data from a relay has nothing in common with a relay screaming at another relay that a breaker needs to open in the next four milliseconds.

IEC 61850 didn’t choose between them. It shipped both.

What This Means When You Need the Data

For most factory floor engineers, the interesting piece is the MMS side. Your PLC doesn’t need Sampled Values and it has no business subscribing to protection GOOSE. It needs breaker position, volts, amps, power and a handful of alarms. That means accessing the data through an IEC 61850 client connection on the network and mapping it directly into your control system.

And if the IED’s SCL file is available, importing it wipes out an enormous pile of manual data entry, because the device’s model comes along for the ride.

Need a hand? Call the RTA Enginerds at 800-249-1612 or email solutions@rtautomation.com.