What Is MMS in IEC 61850?

Back to Blog

The Client-Server Backbone

IEC 61850 defines abstract services - read this data, write that setting, enable this report, operate that breaker - and MMS is the concrete protocol those services are mapped onto for client-server communication. MMS is an older ISO standard (ISO 9506) that IEC 61850 adopted rather than inventing a new one, layering the substation object model on top of MMS's generic device-and-variable model. It rides on TCP/IP over the station Ethernet, so it is routable, reliable, and connection-oriented, which is exactly what routine SCADA polling and reporting need.

Through MMS a client can browse an IED's data model, read and write data attributes, enable a report control block and receive spontaneous reports, issue select-before-operate or direct control commands, and read and change settings. It is the everyday workhorse of the substation network - if a SCADA system or gateway is pulling status and measurements or writing setpoints to an IEC 61850 device, that traffic is almost certainly MMS.

Why MMS Is Not the Whole Story

MMS is reliable but not fast enough for protection-grade signaling, so IEC 61850 pairs it with two connectionless services. Trips and interlocks that must arrive in milliseconds go over GOOSE, published on Layer 2 with no TCP handshake. Digitized current and voltage streams go over Sampled Values. MMS handles everything that can tolerate TCP latency - reports, control, configuration - while GOOSE and SV handle the time-critical peer-to-peer traffic.

For a cloud or enterprise SCADA layer, MMS is usually the point of contact, because a station gateway terminates the fast Layer 2 services and exposes their results as MMS-reportable data. Understanding that split - reliable MMS for routine data, connectionless services for speed - is central to the IEC 61850 standard and to any integration design against it.

Datasets and Report Control Blocks in Practice

MMS reporting is built from two configured objects. A dataset is a named list of data attributes - the points you care about, grouped. A report control block (RCB) watches a dataset and sends a report to the connected client when a trigger fires: a data change, a quality change, an integrity period expiring, or a general interrogation the client requests to get a full baseline. The client enables the RCB after connecting, and from then on data arrives spontaneously - which is why 61850 clients do not poll the way older SCADA protocols do.

The distinction that matters operationally is buffered versus unbuffered. A buffered RCB queues events inside the IED while no client is connected and delivers the backlog on reconnection, so a communications outage does not erase the event record. An unbuffered RCB simply drops whatever happened while nobody was listening. For anything feeding an event log, alarm system, or historian, buffered reporting is the one you want, and proving the buffer behavior after a long outage belongs in the commissioning tests.

Control Models: Direct Operate and Select-Before-Operate

IEC 61850 defines four control models that MMS carries: direct operate with normal security, select-before-operate (SBO) with normal security, and enhanced-security versions of both. Select-before-operate makes the client reserve the control point and receive confirmation before issuing the operate - a two-step pattern that guards against a mistaken or duplicated command reaching a breaker in one hop. The enhanced-security variants add supervision of the command's outcome, so the client learns whether the equipment actually responded rather than only whether the message was accepted.

Which model applies to a given point is fixed in the IED's configuration, not chosen at runtime - the client must speak the model the device expects. For anything that moves primary equipment, the control model is part of the operational safety design: the choice, the interlocks around it, and who is authorized to command what from where are matters for the site's operating procedures and qualified operations personnel, with the protocol simply enforcing the sequence.

Getting MMS Data Out to the Wider SCADA World

MMS is a substation protocol, and the wider enterprise usually does not speak it. The standard pattern is a station gateway acting as the MMS client: it browses the IEDs, enables their report control blocks, and republishes the data northbound in whatever the upstream system expects. The main engineering task in that gateway is name mapping - IEC 61850 addresses are long hierarchical paths through logical devices, logical nodes, and data objects, and they must be mapped onto the flatter tag model of the receiving system without losing the semantics.

Utility masters commonly take that northbound feed as IEC 60870-5-104 or DNP3 - the pattern for the former is covered in connecting IEC 60870 to a cloud SCADA. And because the gateway sits at the station bus boundary where the fast Layer 2 services terminate, the northbound feed can carry the results of GOOSE-driven events too - as reportable data changes rather than as raw multicast frames.

Troubleshooting an MMS Association

MMS connections fail in layers, and the fastest diagnosis walks up them. First TCP: the client must reach the IED on port 102, the ISO-transport-over-TCP port, so a firewall rule or routing gap shows up as a plain connection failure. Above TCP sit the OSI upper layers, and mismatched selectors or application titles between client and server configurations produce the classic symptom of a TCP connection that establishes followed by an association that refuses. Both ends' configured addressing must agree exactly.

Once associated, the common traps are reporting-related. A report control block can be owned by only one client at a time, so a second client - a test laptop, a redundant master - fails to enable the RCB the primary already holds; devices expose multiple RCB instances for exactly this reason, and each client needs its own assignment. After long outages, check buffered RCBs for overflow indications, which mean the event backlog exceeded the buffer and something was lost. And where IEC 62351 security features are deployed on the station network, certificate and authentication failures add one more layer to check, per the site's security configuration.

Frequently Asked Questions