> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/configure-ios/communication-protocol-ios/iec-61850-8-1-mms.md).

# IEC 61850-8-1 MMS

## Introduction to IEC 61850‑8‑1 MMS <a href="#introductiontoiec6185081mms" id="introductiontoiec6185081mms"></a>

IEC 61850‑8‑1 MMS (Manufacturing Message Specification) is the standard mechanism for supervisory control, monitoring, reporting, and configuration in digital substations. It enables SCADA systems, HMIs, and engineering tools to interact with protection and automation IEDs over reliable TCP/IP‑based client/server communication. MMS supports retrieval of status information, analog measurements, settings parameters, file transfers, and execution of control commands such as breaker operations. MMS messages are mapped over TCP/IP and provide structured access to the IEC 61850 object model. They are used extensively in SCADA communication, monitoring, maintenance, engineering access, and any application where reliable, request‑response communication is required.

## Protocol characteristics <a href="#protocolcharacteristics" id="protocolcharacteristics"></a>

* **Client/Server Architecture**\
  MMS operates using a centralized client/server model, where an IED exposes its data model through an MMS server, and one or more clients (SCADA, HMI, engineering tools) retrieve information or issue commands. There is no multicast: all messages are request‑response exchanges performed over TCP/IP sessions.
* **Request‑Driven Data Access**\
  Instead of event‑driven multicasts, MMS data exchange occurs when the client issues explicit Read, Write, or Control requests. This includes reading measurements, statuses, and configuration values; writing settings; or performing Select‑Before‑Operate (SBO) sequences.
* **Data Model**\
  MMS exposes IEC 61850 Logical Devices, Logical Nodes, Data Objects, and Data Attributes. These include status variables, measurement values, quality information, settings, control points, and system information. All values follow the IEC 61850‑7‑3 and ‑7‑4 object model definitions.
* **Report Control Blocks & Datasets**\
  Event‑driven communication in MMS uses Report Control Blocks (RCBs) associated with datasets. RCBs define how event conditions such as data change, quality change, or periodic integrity trigger the transmission of a Report message from the server IED to the MMS client. Buffered and unbuffered reporting modes are supported, depending on the RCB type.
* **Transport Mechanism**\
  MMS is transmitted over TCP/IP, typically using the OSI session and presentation mappings defined in IEC 61850‑8‑1. Because MMS relies on TCP for reliability, it is suited for supervisory and engineering applications rather than sub‑millisecond protection signaling.
* **Reliability & Responsiveness**\
  MMS ensures reliable communication through TCP acknowledgement, sequence handling, and optional buffering in RCBs. Latency depends on network conditions and client request frequency, typically ranging from a few milliseconds to several hundred milliseconds, appropriate for SCADA communication and IED control operations.
* **Security Model (Protocol‑agnostic)**\
  IEC 61850‑8‑1 MMS does not inherently provide encryption or authentication. Deployments typically rely on external mechanisms such as TLS (IEC 62351‑4), VPNs, access control lists, and network segmentation. Security services are implemented outside the MMS protocol.

## How the protocol works <a href="#howtheprotocolworks" id="howtheprotocolworks"></a>

* **Dataset & Report Control Block configuration**\
  Engineering tools generate SCL files that define the datasets and Report Control Blocks used for MMS reporting. These include the set of data attributes monitored for changes, the buffering behavior, trigger options (data change, quality change, data update, periodic integrity), optional fields, and configuration revision handling. IEDs load this information during initialization to determine how they generate MMS Reports.
* **Data access & client requests**\
  SCADA systems and engineering tools initiate communication by connecting to the MMS server on the IED. Operations include reading data values, writing configuration settings, browsing the IED’s data model, retrieving file records, or issuing commands using SBO or direct‑operate control models. All data access is explicitly triggered by the client.
* **Report generation**\
  When a client enables an RCB, the IED monitors the dataset for conditions such as data change or quality change. When a trigger occurs, the IED assembles a Report message and sends it to the client. If the RCB is buffered, reports are queued until successfully acknowledged by the client.
* **Reception & subscription**\
  MMS clients subscribe to Reports by enabling one or more RCBs on the server IED. Once enabled, the client receives Report messages whenever trigger conditions are met. Unlike GOOSE, the communication is connection‑oriented and unicast.
* **Application processing**\
  MMS is used to feed SCADA displays, operator controls, alarm handling, HMI updates, settings management, and engineering access. Control commands (e.g., breaker open/close) are executed using the SBO or direct operate models and follow strict command validation and timeout rules defined by IEC 61850.

## Example applications <a href="#exampleapplications" id="exampleapplications"></a>

* **SCADA Monitoring & Control**\
  MMS provides all real‑time information needed by SCADA systems, including breaker statuses, alarms, analog measurements, and operator‑initiated control actions such as opening or closing switchgear.
* **Engineering Access & Configuration**\
  MMS enables engineers to read and write settings, inspect Logical Node parameters, download event logs, retrieve disturbance records, and perform device diagnostics.
* **Event‑Driven Reporting**\
  Using RCBs, IEDs push event notifications to SCADA systems when data changes occur, instead of requiring polling. This includes alarm generation, operational status changes, and periodic integrity reports.
* **Maintenance & File Transfer**\
  MMS includes file services that allow retrieving COMTRADE disturbance records, fault logs, or diagnostic files for maintenance and analysis.
* **HMI & Operator Interfaces**\
  Operator workstations rely on MMS to display status indications, alarm summaries, event lists, breaker positions, and to execute human‑initiated control commands safely and reliably.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/configure-ios/communication-protocol-ios/iec-61850-8-1-mms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
