- 1. Introduction
- 2. What Is MMS in IEC 61850?
- 3. MMS Communication Architecture
- 4. MMS Client and Server
- 5. IP Address and Network Configuration
- 6. Establishing an MMS Association
- 7. IEC 61850 Data Model Browsing
- 8. Important MMS Services
- 9. Functional Constraints in MMS
- 10. Data Quality and Timestamp
- 11. MMS Reporting
- 12. MMS Controls in MiCOM Relays
- 13. MMS Integration with Siemens SICAM PAS
- 14. Configuring MMS Using MiCOM Engineering Tools
- 15. MMS Communication Testing with Wireshark
- 16. Common MMS Communication Problems
- 17. MMS Commissioning Checklist
- 18. MMS Security Considerations
- 19. Practical Engineering Recommendations
- 20. Conclusion
- 21. Practical MiCOM and IEC 61850 Training by Elec-Engg
1. Introduction
Manufactured by Schneider Electric, MiCOM protection relays are widely used in electrical substations for feeder protection, transformer protection, distance protection, line differential protection and other power system applications.
Many MiCOM relay models support IEC 61850 communication, allowing protection devices to exchange information with substation automation systems, SCADA platforms and other intelligent electronic devices (IEDs).
One of the main communication services defined by IEC 61850 is Manufacturing Message Specification (MMS).
MMS enables an external client, such as a SCADA system or substation controller, to access information provided by an IED. This includes protection indications, measurements, alarms, equipment status and supported control services.
For engineers working with MiCOM relays, understanding MMS configuration is essential for successful integration with systems such as Siemens SICAM PAS and other IEC 61850-compatible automation platforms.
This article explains MMS architecture, client-server communication, logical device browsing, data access, reporting, control services, configuration and practical troubleshooting.
The exact MMS capabilities depend on the MiCOM model, order code, communication hardware, firmware and IEC 61850 implementation. Always verify the supported services in the relevant documentation and device-specific MICS, PICS, PIXIT and ICD files.
2. What Is MMS in IEC 61850?
MMS is an application-layer communication protocol used by IEC 61850 for communication between clients and servers.
In a typical substation:
- The protection relay operates as an MMS server.
- The station controller or SCADA system operates as an MMS client.
- The client establishes a communication association with the relay.
- The client accesses the relay’s IEC 61850 data model.
- The relay provides supported data and services.
For example, a MiCOM feeder relay can provide the following information to a SCADA system:
- Phase overcurrent protection operation.
- Earth fault protection operation.
- Circuit breaker status.
- Phase current measurements.
- Voltage measurements, where available.
- Protection alarms.
- Disturbance and event-related information, where supported.
The MMS client can read data, subscribe to reports and execute supported control services.
3. MMS Communication Architecture
MMS communication in IEC 61850 generally uses the following protocol architecture:
+----------------------------------+
| SCADA / Station Controller |
| |
| IEC 61850 MMS Client |
+----------------+-----------------+
|
|
Ethernet Network
|
|
+----------------v-----------------+
| MiCOM Protection Relay |
| |
| IEC 61850 MMS Server |
| |
| Logical Devices |
| Logical Nodes |
| Data Objects |
| Data Attributes |
+----------------------------------+
The SCADA system requests information from the relay, and the relay responds according to its supported IEC 61850 services.
Unlike GOOSE, MMS uses a client-server communication model and is carried over TCP/IP.
3.1 Protocol Stack
A simplified MMS communication stack is:
| Layer | Protocol or function |
|---|---|
| Application | IEC 61850 MMS services |
| Presentation | ISO presentation services |
| Session | ISO session services |
| Transport | TCP |
| Network | IP |
| Data Link | Ethernet |
| Physical | Copper or fibre Ethernet |
MMS commonly uses TCP port 102.
This is an important parameter when checking firewall rules and network communication.
4. MMS Client and Server
4.1 MMS Server
The MMS server is normally the protection relay.
It makes the IEC 61850 data model available to external clients.
Its functions may include:
- Providing device information.
- Exposing logical devices.
- Providing logical node information.
- Providing data objects and attributes.
- Responding to read requests.
- Supporting reporting.
- Supporting control services where implemented.
A MiCOM relay’s available services must be checked against the exact device documentation.
4.2 MMS Client
The MMS client is typically a station controller, SCADA system or IEC 61850 engineering tool.
Examples include:
- Siemens SICAM PAS.
- Other IEC 61850-compatible substation automation systems.
- SCADA platforms with IEC 61850 client functionality.
- IEC 61850 testing and diagnostic tools.
The client establishes an association with the relay and accesses its data model.
5. IP Address and Network Configuration
Before establishing MMS communication, the relay and client must be correctly configured on the Ethernet network.
Consider the following illustrative example:
| Device | IP address | Subnet mask |
|---|---|---|
| MiCOM Relay 1 | 192.168.10.11 | 255.255.255.0 |
| MiCOM Relay 2 | 192.168.10.12 | 255.255.255.0 |
| SICAM PAS | 192.168.10.100 | 255.255.255.0 |
| Engineering PC | 192.168.10.200 | 255.255.255.0 |
These addresses are examples only.
Check the following parameters:
- IP address.
- Subnet mask.
- Default gateway, where required.
- Ethernet interface selection.
- Network routing.
- TCP port 102 accessibility.
- Firewall rules.
- Switch port configuration.
A successful ping test confirms basic IP reachability, but it does not prove that MMS communication is operational.
6. Establishing an MMS Association
Before accessing the relay data model, the client must establish an MMS communication association.
The process generally involves several stages:
- Establish the TCP connection.
- Exchange the required ISO transport and session information.
- Establish the presentation and ACSE association.
- Negotiate the MMS application communication.
- Access the supported IEC 61850 services.
The association allows the client and server to exchange MMS requests and responses.
6.1 Common Communication Parameters
Important parameters include:
- Relay IP address.
- Server identity.
- TCP port.
- IED name.
- Logical device references.
- Supported MMS services.
- Client association configuration.
The exact configuration requirements depend on the MMS client and MiCOM implementation.
7. IEC 61850 Data Model Browsing
After establishing communication, the client can browse the available data model.
The IEC 61850 hierarchy is:
IED
└── Logical Device
└── Logical Node
└── Data Object
└── Data Attribute
For example, a feeder protection relay may expose information similar to:
IED1
└── PROT
├── PTOC1
│ └── Op
│ └── general
│
├── PIOC1
│ └── Op
│
└── PTRC1
└── Tr
└── general
This is an illustrative structure, not a guaranteed MiCOM data model.
7.1 Logical Device Browsing
A logical device groups related logical nodes.
The client can discover the logical devices exposed by the server using supported MMS model-discovery services.
7.2 Logical Node Browsing
Logical nodes represent functions or information categories.
Examples include:
| Logical node | Description |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIS | Distance protection |
| PDIF | Differential protection |
| PTRC | Protection trip conditioning |
| MMXU | Measurement information |
| XCBR | Circuit breaker information |
| CSWI | Switch control |
| GGIO | Generic process I/O |
The actual availability and naming of logical nodes depend on the relay.
7.3 Data Object Browsing
A data object provides a specific item of information within a logical node.
For example, a protection operation logical node may contain operation status information.
7.4 Data Attribute Browsing
Data attributes provide the detailed values associated with data objects.
Examples include:
stVal: Status value.q: Quality.t: Timestamp.mag: Magnitude of a measured value.
Not all data objects have the same attributes.
8. Important MMS Services
IEC 61850 uses MMS services to provide data access and communication functionality.
Some important services are described below.
8.1 GetNameList
This service allows the client to discover names of objects within the server.
It is useful for browsing:
- Logical devices.
- Logical nodes.
- Data objects.
- Data attributes.
- Other supported model objects.
8.2 GetVariableAccessAttributes
This service allows the client to obtain information about a variable or data structure.
It helps the client understand the structure and type of the information available from the server.
8.3 Read
The Read service allows the client to retrieve a data value from the server.
For example, the client may read the breaker position.
Illustrative reference:
IED1CTRL/XCBR1.Pos.stVal
The exact reference depends on the IED data model.
8.4 Write
The Write service allows a client to modify supported writable data.
Not every data attribute is writable.
Writing settings or changing device configuration should not be assumed to be possible through ordinary MMS data access.
8.5 GetVariableAccessAttributes and Read
These services are often used together during data model discovery and point mapping.
The client first discovers the object structure and then reads the required values.
9. Functional Constraints in MMS
Functional Constraints (FCs) identify the purpose of data attributes.
Important examples include:
| FC | Meaning |
|---|---|
| ST | Status |
| MX | Measurement |
| CO | Control |
| SP | Setpoint |
| CF | Configuration |
| DC | Description |
| SG | Setting group |
| SE | Setting |
| SV | Substitution |
| BL | Blocking |
For example:
- Breaker position is generally status information.
- Phase current is measurement information.
- A supported switch command is control information.
Functional constraints are important when engineering SCADA points and interpreting the data model.
10. Data Quality and Timestamp
A reliable IEC 61850 integration must consider more than the data value itself.
Two important attributes are quality (q) and timestamp (t).
10.1 Quality – q
Quality information indicates the validity and reliability of a data value.
It may include information about:
- Validity.
- Source.
- Test status.
- Operator blocking.
- Other quality details.
For example, a measurement may have a numerical value but be marked invalid.
The SCADA system should process the quality information rather than treating every received number as valid.
10.2 Timestamp – t
The timestamp provides time information associated with the data.
It is important for:
- Event recording.
- Sequence-of-events analysis.
- Alarm investigation.
- Fault analysis.
- Correlation between multiple IEDs.
Correct timestamp interpretation requires suitable time synchronization and correct time-zone handling in the wider system.
11. MMS Reporting
MMS reporting is one of the most important services in IEC 61850 substation automation.
Instead of continuously polling every data point, a client can configure reporting to receive relevant changes and periodic updates.
A report can contain:
- Data values.
- Quality.
- Timestamp.
- Reason for inclusion.
- Dataset reference.
- Sequence information, where configured.
11.1 Dataset
A dataset is a collection of selected data attributes.
For example:
DS_FEEDER_SCADA
├── PTOC1.Op.general
├── PTRC1.Tr.general
├── XCBR1.Pos.stVal
└── MMXU1.A.phsA.cVal.mag.f
These are illustrative references and must be confirmed in the specific relay data model.
11.2 Report Control Block
A Report Control Block (RCB) defines the reporting behavior.
There are two main types:
- URCB: Unbuffered Report Control Block.
- BRCB: Buffered Report Control Block.
URCB is used for unbuffered reporting. It does not provide the persistent event-retention behavior of BRCB.
BRCB supports event buffering, allowing reports to be recovered after temporary client disconnection within the available buffer and implementation limits.
11.3 Report Trigger Conditions
Common trigger options include:
- Data change.
- Quality change.
- Data update.
- Integrity period.
- General interrogation.
The supported options depend on the server implementation.
12. MMS Controls in MiCOM Relays
IEC 61850 can support control services through MMS.
These services allow an authorized client to operate supported equipment through the IED.
For example, a SCADA operator may request circuit breaker opening or closing.
Common control models include:
- Direct control.
- Select Before Operate (SBO).
- Select Before Operate with enhanced security, where supported.
12.1 Direct Control
In direct control, the client sends a control request without a separate selection operation.
The IED evaluates the request and responds according to its control model and configured interlocking conditions.
12.2 Select Before Operate
In SBO control, the client first selects the control object and then issues the operation.
The selection process helps prevent unintended operations and supports control coordination.
12.3 Control Verification
During commissioning, verify:
- Control model.
- Select and operate behavior.
- Command termination.
- Interlocking.
- Local/remote status.
- Position feedback.
- Command timeout.
- Control authority.
Control services and their detailed behavior must be verified against the particular MiCOM model and application.
13. MMS Integration with Siemens SICAM PAS
A common application is integration of MiCOM protection relays with Siemens SICAM PAS.
In this architecture:
- MiCOM relay operates as the MMS server.
- SICAM PAS operates as the MMS client.
- Ethernet provides the communication network.
- MMS provides data access and reporting.
13.1 Integration Architecture
+--------------------------+
| SICAM PAS |
| |
| IEC 61850 MMS Client |
| |
| SCADA Data Processing |
+------------+-------------+
|
|
Ethernet Network
|
+-----+------+
| |
+------v------+ +---v----------+
| MiCOM Relay | | MiCOM Relay |
| Feeder 1 | | Feeder 2 |
| MMS Server | | MMS Server |
+-------------+ +--------------+
13.2 Typical Engineering Workflow
- Configure the MiCOM relay communication parameters.
- Confirm the relay IP address.
- Obtain the appropriate ICD file.
- Import the IED description into the system engineering project.
- Configure the IED name and communication access point.
- Identify the required logical nodes and data objects.
- Configure the SCADA data points.
- Configure datasets and report control blocks where supported.
- Establish communication with the relay.
- Verify indications and measurements.
- Test reports and controls where applicable.
- Complete the integration and commissioning documentation.
The precise SICAM PAS workflow depends on its software version and the selected IEC 61850 interface.
14. Configuring MMS Using MiCOM Engineering Tools
S1 Agile is used for engineering supported MiCOM relays.
Depending on the relay family and firmware, it can be used for device configuration and access to supported communication settings.
Typical engineering activities include:
- Device identification.
- Communication configuration.
- Protection setting configuration.
- Review of available IEC 61850 information.
- Device-specific configuration and diagnostics.
System-level IEC 61850 engineering may require a separate system configuration tool.
Do not assume that S1 Agile provides every system-level SCL engineering function or supports identical IEC 61850 configuration workflows across all MiCOM products.
Before engineering, check the exact relay model, firmware, communication module and software compatibility.
15. MMS Communication Testing with Wireshark
Wireshark is an important tool for troubleshooting IEC 61850 MMS communication.
It allows engineers to examine TCP connections and MMS traffic.
Useful display filters include:
MMS communication:
tcp.port == 102
TCP retransmissions:
tcp.analysis.retransmission
TCP reset packets:
tcp.flags.reset == 1
Traffic from a particular relay:
ip.addr == 192.168.10.11
15.1 What Should Be Checked?
During packet analysis, examine:
- TCP connection establishment.
- Port 102 communication.
- Association establishment.
- MMS request and response messages.
- Data model discovery.
- Read requests.
- Report messages.
- Control requests, where applicable.
- Communication interruptions.
A successful TCP connection does not prove that the MMS association or IEC 61850 services are operating correctly.
16. Common MMS Communication Problems
| Problem | Possible cause | Recommended check |
|---|---|---|
| TCP connection fails | Incorrect IP or network issue | Check IP address, routing and port 102 |
| MMS association fails | Protocol or association configuration mismatch | Review client and server configuration |
| Data model cannot be browsed | Incorrect IED description or unsupported service | Check the ICD and server capabilities |
| Some signals are missing | Incorrect logical node or data reference | Verify the actual data model |
| Measurements are incorrect | Incorrect scaling or data interpretation | Check data type, units and scaling |
| Reports are not received | RCB not enabled or incorrectly configured | Check dataset and report configuration |
| Events are missing after disconnection | Unbuffered reporting or buffer limitations | Check URCB/BRCB selection |
| Controls fail | Incorrect control model or interlocking | Verify control configuration and authority |
| Timestamps are incorrect | Time synchronization issue | Check SNTP, PTP or other supported time source |
17. MMS Commissioning Checklist
Before placing a MiCOM relay into service, use a structured testing procedure.
Communication Configuration
- Verify relay IP address.
- Verify subnet mask and gateway.
- Check Ethernet connection.
- Confirm network reachability.
- Check TCP port 102.
- Verify firewall and network policies.
MMS Association
- Establish the MMS association.
- Confirm client-server communication.
- Check supported MMS services.
- Verify server identification.
Data Model
- Browse logical devices.
- Browse logical nodes.
- Identify required data objects.
- Verify data attributes.
- Check functional constraints.
- Verify quality and timestamp.
Reporting
- Verify datasets.
- Check report control blocks.
- Test data-change reporting.
- Test quality-change reporting.
- Test integrity reporting where supported.
- Test general interrogation.
- Test buffered reporting and recovery where applicable.
Controls
- Verify supported control models.
- Check local/remote status.
- Verify interlocking.
- Test control feedback.
- Confirm safe operation under the approved commissioning procedure.
18. MMS Security Considerations
MMS communication is an important part of the substation network and must be protected.
Recommended practices include:
- Separate protection and control networks from office networks.
- Restrict access to engineering workstations.
- Use appropriate firewall rules.
- Limit access to TCP port 102.
- Protect relay configuration files.
- Maintain configuration backups.
- Monitor network communication.
- Apply appropriate authentication and authorization.
- Follow applicable IEC 62351 guidance and organizational cybersecurity policies.
Do not assume that standard MMS communication is automatically encrypted or protected by strong authentication. Security capabilities depend on the device, protocol implementation and configured security architecture.
19. Practical Engineering Recommendations
For reliable MiCOM MMS integration:
- Confirm the exact IEC 61850 capabilities of the relay.
- Use the correct ICD file.
- Maintain consistent IED names.
- Check the logical device and logical node structure.
- Select only required data points.
- Understand functional constraints.
- Configure report control blocks carefully.
- Choose URCB or BRCB according to the application.
- Verify quality and timestamp handling.
- Test controls separately from monitoring.
- Use Wireshark for communication diagnostics.
- Document the complete SCADA point mapping.
Successful integration requires both correct protocol configuration and correct application-level engineering.
20. Conclusion
MMS is a fundamental communication service in IEC 61850-based substations.
For MiCOM protection relays, it enables SCADA systems and station controllers to access protection indications, measurements, equipment status, reports and supported control functions.
Engineers must understand the client-server architecture, data model browsing, MMS services, datasets, report control blocks, functional constraints and communication testing.
When correctly configured, MMS provides a structured method of integrating MiCOM protection relays with modern substation automation systems.
However, successful implementation always depends on the actual capabilities of the relay, the MMS client and the complete communication architecture.
21. Practical MiCOM and IEC 61850 Training by Elec-Engg
Elec-Engg provides practical training in power system protection, MiCOM protection relays, IEC 61850 communication and substation automation.
Our training covers:
- MiCOM protection relay configuration.
- IEC 61850 architecture and data models.
- MMS client-server communication.
- MMS reporting and control.
- GOOSE publisher and subscriber engineering.
- ICD, CID, IID and SCD files.
- URCB and BRCB configuration.
- SICAM PAS integration.
- Wireshark communication analysis.
- Practical testing and commissioning.
Training formats:
- Pre-recorded video courses.
- Structured self-paced training.
- Face-to-face training.
- Customized in-house training for companies and utilities.
Practical courses by Dr Saeed Roostaee / Elec-Engg
Website: https://elec-engg.com/
