- Introduction
- 1. Understanding the MiCOM-to-SCADA Communication Architecture
- 2. Understanding IEC 61850 Data References
- 3. Identifying the Required SCADA Signals
- 4. Understanding Functional Constraints in SCADA Mapping
- 5. Understanding Data Types and Common Data Classes
- 6. Quality Information: Why SCADA Must Check More Than the Value
- 7. Timestamp Handling in IEC 61850 SCADA Integration
- 8. Creating MMS Datasets for SCADA Reporting
- 9. Practical Example: Mapping a MiCOM Feeder Relay to SCADA
- 10. SCADA Control and Breaker Operation
- 11. Using SCL Files During SCADA Integration
- 12. Troubleshooting MiCOM IEC 61850 SCADA Integration
- 13. Best Practices for MiCOM IEC 61850 SCADA Engineering
- 14. Commissioning Checklist
- 15. Conclusion
- Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Introduction
IEC 61850 enables MiCOM protection relays to exchange protection, control, measurement and status information with Substation Automation Systems (SAS), SCADA platforms and station-level controllers. However, establishing communication between a MiCOM relay and a SCADA system is only one part of the integration process.
A successful integration also requires correct data-point mapping, logical node identification, functional constraint selection, quality and timestamp handling, dataset configuration, report control configuration and verification of the information received by the SCADA system.
For protection and commissioning engineers, understanding how to map IEC 61850 information into a SCADA database is essential. Incorrect mapping can result in missing indications, incorrect measurements, misleading alarms or control points that do not operate as expected.
This article explains the practical engineering workflow for integrating MiCOM relays with IEC 61850-based SCADA systems.
Important: IEC 61850 capabilities differ between MiCOM relay families, models, order codes, communication hardware and firmware versions. Always verify the supported data model and services using the relevant technical manual, MICS, PICS, PIXIT, ICD file and firmware documentation.
1. Understanding the MiCOM-to-SCADA Communication Architecture
In a typical IEC 61850 substation, MiCOM protection relays operate as Intelligent Electronic Devices (IEDs). The station-level SCADA system acts as an IEC 61850 client.
The communication architecture generally includes:
- MiCOM protection relays as IEC 61850 servers.
- SCADA or SAS software as IEC 61850 clients.
- Ethernet switches connecting the IEDs and station-level equipment.
- MMS communication for monitoring, reporting and supported control services.
- GOOSE communication for fast peer-to-peer exchange between IEDs.
- Engineering tools for configuring IEDs and the overall substation system.
A simplified communication path is:
MiCOM relay → Ethernet network → IEC 61850 MMS client → SCADA database → HMI
The relay exposes its supported information model through IEC 61850. The SCADA client discovers or imports this model and associates selected data objects with its internal database points.
GOOSE is a separate communication mechanism. It is generally used for fast exchange of signals between IEDs rather than ordinary SCADA reporting.
2. Understanding IEC 61850 Data References
An IEC 61850 data reference identifies an item within an IED’s standardized information model.
A typical reference can contain:
- IED name
- Logical Device (LD)
- Logical Node (LN)
- Data Object (DO)
- Data Attribute (DA)
For example, consider a hypothetical feeder relay with the following reference:
MICOM_P143LD0/PTOC1.Op.general
This can be interpreted as:
| Element | Meaning |
|---|---|
| MICOM_P143 | IED name |
| LD0 | Logical Device |
| PTOC1 | First overcurrent protection logical node |
| Op | Operation data object |
| general | General operation indication |
This is an illustrative reference. The actual logical device names, logical node instances and data attributes must be taken from the specific relay’s IEC 61850 data model.
A data reference should never be assumed to exist simply because it is defined in the IEC 61850 standard. The relay must actually implement and expose the relevant logical node and data object.
3. Identifying the Required SCADA Signals
Before configuring the IEC 61850 client, the engineering team should prepare a SCADA signal list.
The signal list defines which information must be transferred from the protection relay to the station-level system.
Typical signal categories include:
3.1 Protection indications
Examples include:
- Phase overcurrent protection operated.
- Earth fault protection operated.
- Directional overcurrent protection operated.
- Distance protection operated.
- Differential protection operated.
- Protection start indication.
- Protection trip indication.
- Auto-reclose operation.
- Protection function blocked.
The corresponding logical nodes depend on the protection functions implemented by the relay.
Examples of standardized logical node classes include:
| Logical node | Typical function |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIR | Directional protection |
| PDIS | Distance protection |
| PDIF | Differential protection |
| RREC | Automatic reclosing |
| PTRC | Protection trip conditioning |
The actual implementation and data-object availability must be checked in the relay documentation.
3.2 Circuit breaker indications
SCADA operators commonly require:
- Circuit breaker open.
- Circuit breaker closed.
- Intermediate or invalid position, where available.
- Breaker failure indication.
- Spring charged.
- Local/remote selection.
- Breaker trip circuit supervision.
- Breaker operation counter.
IEC 61850 logical nodes commonly associated with switching equipment include:
- XCBR – Circuit breaker.
- CSWI – Switch controller.
- CILO – Interlocking.
- GGIO – Generic process I/O.
Not every MiCOM relay exposes all these nodes or all their data objects.
3.3 Measurements
Typical measurements include:
- Phase currents.
- Residual or earth fault current.
- Phase-to-phase voltages.
- Phase-to-neutral voltages.
- Active power.
- Reactive power.
- Apparent power.
- Power factor.
- Frequency.
- Energy measurements, where supported.
The MMXU logical node is commonly used for electrical measurements.
However, engineers must verify the available measurement objects, scaling, units and functional constraints in the actual relay model.
3.4 Device and communication status
SCADA may also require:
- Relay healthy indication.
- Internal device alarm.
- Communication failure.
- Protection function unavailable.
- Maintenance or test mode indication.
- Time synchronization status, where exposed.
These points are important because a missing protection indication is not necessarily evidence that the protection function has not operated. It may also indicate a communication or data-quality problem.
4. Understanding Functional Constraints in SCADA Mapping
Functional Constraints (FCs) identify the purpose of a data attribute within the IEC 61850 information model.
Selecting the correct functional constraint is essential when configuring the SCADA client.
Common functional constraints include:
| Functional constraint | Purpose | Typical application |
|---|---|---|
| ST | Status information | Breaker position, protection status |
| MX | Measured values | Current, voltage, power |
| CO | Control | Supported switching commands |
| SP | Setpoint | Setpoint-related information |
| CF | Configuration | Configuration parameters |
| DC | Description | Descriptive information |
| SG | Setting group | Setting group information |
| SE | Setting group editing | Setting group editing services |
| BR | Buffered reporting | Buffered report information |
| RP | Unbuffered reporting | Unbuffered report information |
For example, a breaker position indication is normally accessed as status information, while phase current is accessed as a measured value.
A control command is not simply another status point. It uses the appropriate control model and services supported by the IED.
Practical engineering rule: Do not select an IEC 61850 data reference based only on its name. Confirm its functional constraint, data type, control model and reporting behavior.
5. Understanding Data Types and Common Data Classes
IEC 61850 uses standardized data structures known as Common Data Classes (CDCs).
A CDC defines the structure and attributes of a particular category of information.
Examples include:
| CDC | General application |
|---|---|
| SPS | Single-point status |
| DPS | Double-point status |
| INS | Integer status |
| ENS | Enumerated status |
| MV | Measured value |
| WYE | Three-phase measurement structure |
| DEL | Phase-to-phase measurement structure |
| ACD | Directional protection activation information |
| ACT | Protection operation information |
| SPC | Single-point control |
| DPC | Double-point control |
For example, a protection operation indication may be represented using an appropriate protection-related CDC, while a phase current may be represented using a measurement CDC.
The SCADA client must correctly interpret the structure and attributes of the selected CDC.
This becomes especially important when integrating devices from different manufacturers. Two relays may implement the same standardized logical node but expose different supported data objects or optional attributes.
6. Quality Information: Why SCADA Must Check More Than the Value
One of the most important aspects of IEC 61850 integration is the quality attribute, commonly represented by q.
A measurement or status value should not always be interpreted as valid simply because the SCADA system receives a numerical or Boolean value.
Quality information provides additional context about the reliability and validity of the data.
Depending on the data object and implementation, quality can indicate conditions such as:
- Validity.
- Old data.
- Inconsistent data.
- Inaccurate data.
- Substituted data.
- Test condition.
- Operator-blocked information.
- Failure-related conditions.
For example, assume SCADA receives a phase current of 450 A.
If the quality indicates that the value is invalid or questionable, the operator should not treat 450 A as a reliable live measurement.
Similarly, a breaker position indication may retain a value even when the communication path or underlying data source is no longer reliable.
Recommended SCADA engineering practice
For important protection and switching indications:
- Map the actual data value.
- Map its associated quality information where available.
- Configure the SCADA database to recognize invalid or questionable quality.
- Display communication and data-quality problems clearly.
- Avoid treating invalid data as a normal zero or healthy state.
Quality supervision is particularly important for protection alarms, breaker positions, interlocking-related information and critical measurements.
7. Timestamp Handling in IEC 61850 SCADA Integration
IEC 61850 data objects can include timestamp information, commonly represented by the attribute t.
A timestamp helps the SCADA system determine when an event or value was recorded by the source device.
This is important when several protection relays operate during the same power system disturbance.
For example:
- A feeder protection relay detects a fault.
- A transformer protection relay receives an associated signal.
- A breaker opens.
- A busbar protection scheme records its operation.
Accurate timestamps help engineers reconstruct the sequence of events.
7.1 Device timestamp versus SCADA reception time
These are two different concepts:
Device timestamp: The time associated with the data at the source IED.
SCADA reception time: The time at which the SCADA system receives or processes the information.
If the SCADA system uses only reception time, communication delays can distort the apparent sequence of events.
For disturbance analysis, source timestamps should be used where supported and correctly synchronized.
7.2 Time synchronization
MiCOM relay time synchronization capabilities depend on the specific model and configuration.
Possible synchronization arrangements in substations include:
- SNTP.
- PTP, where supported.
- IRIG-B, where supported.
- Other device-specific time synchronization methods.
The engineering team must confirm which synchronization methods are supported by the relay and the overall station architecture.
A time synchronization test should include verification of:
- Time source availability.
- Relay synchronization status.
- Time zone and UTC handling.
- Timestamp consistency between IEDs.
- Event sequence accuracy.
8. Creating MMS Datasets for SCADA Reporting
MMS reporting is commonly used to transfer selected IEC 61850 information from MiCOM relays to SCADA clients.
Rather than continuously reading every available data object, the engineering configuration can use datasets and report control blocks.
A dataset defines the collection of data attributes to be included in a report.
For example, a feeder relay dataset might contain:
| Signal | Example data reference |
|---|---|
| Phase overcurrent operation | PTOC1.Op |
| Earth fault operation | PTOC2.Op |
| Breaker position | XCBR1.Pos |
| Phase current | MMXU1.A |
| Phase voltage | MMXU1.PhV |
| Relay health | Device-specific status object |
These are conceptual examples. The exact references and attributes must be verified against the IED’s implemented model.
8.1 Report Control Blocks
IEC 61850 defines two commonly used report control block types:
Buffered Report Control Block (BRCB)
Buffered reporting can retain events during temporary communication interruptions, subject to the device’s buffer capacity and implementation.
When the client reconnects, the relay may be able to deliver buffered events.
Unbuffered Report Control Block (URCB)
Unbuffered reporting does not provide the same persistent event buffering behavior as BRCB. Events generated while the client is disconnected may not be available after reconnection.
The exact supported reporting services, reservation behavior and configuration limitations must be checked for the particular MiCOM relay.
8.2 Important report parameters
Depending on implementation, report configuration may involve:
- Dataset reference.
- Report ID.
- Buffered or unbuffered reporting.
- Integrity period.
- General interrogation.
- Data-change reporting.
- Quality-change reporting.
- Data-update reporting.
- Optional fields.
- Trigger options.
- Client association and report reservation.
The purpose is to ensure that the SCADA system receives the required information efficiently and reliably.
9. Practical Example: Mapping a MiCOM Feeder Relay to SCADA
Consider a feeder protection panel using a MiCOM relay with IEC 61850 communication.
The station-level SCADA system requires the following information:
- Phase overcurrent trip.
- Earth fault trip.
- Circuit breaker open/closed status.
- Phase currents.
- Phase voltages.
- Relay health.
- Communication status.
The engineering process can be divided into several stages.
Step 1 – Confirm the IED capability
Before starting the configuration, verify:
- Exact relay model.
- Order code.
- Communication hardware.
- Firmware version.
- IEC 61850 edition and supported services.
- Supported logical nodes.
- Available datasets and report control blocks.
Obtain the correct ICD file or other supported engineering description.
Step 2 – Configure the IED identity
Assign the required IED name and communication parameters according to the substation engineering design.
For example:
| Parameter | Example |
|---|---|
| IED name | MICOM_FEEDER_01 |
| IP address | 192.168.10.21 |
| Subnet mask | 255.255.255.0 |
| Gateway | According to network design |
| Ethernet interface | Configured relay communication port |
These values are illustrative only.
The IED name used in the system configuration must match the intended device identity and the corresponding SCADA configuration.
Step 3 – Identify the required data objects
Use the relay’s IEC 61850 model to locate the relevant protection, switching, measurement and device-status information.
Do not assume that every signal has a direct one-to-one relationship with a familiar relay front-panel indication.
Some information may require additional mapping or may not be exposed through IEC 61850 in the selected firmware.
Step 4 – Configure datasets and reports
Create or select suitable datasets containing the required SCADA information.
Configure the corresponding report control blocks according to the relay’s supported capabilities and the SCADA client’s requirements.
Step 5 – Configure the SCADA database
The SCADA engineer imports or configures the data references and associates them with internal point names.
A sample mapping table is shown below.
| SCADA tag | IEC 61850 information | Type |
|---|---|---|
| FEEDER01_OC_TRIP | PTOC1.Op | Protection status |
| FEEDER01_EF_TRIP | PTOC2.Op | Protection status |
| FEEDER01_CB_POS | XCBR1.Pos | Breaker position |
| FEEDER01_IA | MMXU1.A | Measurement |
| FEEDER01_VA | MMXU1.PhV | Measurement |
| FEEDER01_RELAY_HEALTH | Supported device-health object | Status |
The table is illustrative. The actual references, CDCs and attributes must be taken from the relay’s IEC 61850 model.
Step 6 – Verify the communication
Confirm that the SCADA client can:
- Establish an MMS association.
- Discover or access the required data model.
- Read selected data objects.
- Enable the required reports.
- Receive status changes.
- Receive measurements.
- Interpret quality and timestamps correctly.
Step 7 – Perform functional testing
Operate the relevant protection or test functions under an approved test procedure.
Verify that the correct SCADA point changes state and that the associated timestamp and quality information are handled correctly.
10. SCADA Control and Breaker Operation
In some installations, SCADA is also required to operate circuit breakers through the IEC 61850 control services supported by the relay.
A typical control path is:
SCADA operator → IEC 61850 client → MMS control service → MiCOM relay → breaker control circuit
Depending on the implementation, the control model may include:
- Direct control.
- Select Before Operate (SBO).
- Enhanced security control models.
- Status and command termination information.
The relay’s supported control model must be verified before engineering the SCADA command.
Important control checks
Before commissioning remote breaker control, verify:
- The correct breaker is selected.
- Local/remote selection permits remote operation.
- Interlocking conditions are satisfied.
- The relay’s control model is configured correctly.
- Command termination and feedback are received.
- Breaker position feedback agrees with the actual equipment.
- Failed or rejected commands are correctly reported.
A successful communication test does not prove that the breaker control scheme is correctly engineered.
Remote control testing must follow the approved site safety and switching procedures.
11. Using SCL Files During SCADA Integration
Substation Configuration Language (SCL) is used to describe IEC 61850 system and IED configurations.
Relevant file types include:
| File | Purpose |
|---|---|
| ICD | IED Capability Description |
| CID | Configured IED Description |
| IID | Instantiated IED Description |
| SCD | Substation Configuration Description |
| SSD | System Specification Description |
In a typical system engineering workflow:
- Obtain the correct MiCOM IED capability description.
- Import the IED into the system engineering tool.
- Configure the substation and communication structure.
- Define datasets and report control blocks as supported.
- Configure GOOSE communication where required.
- Generate or update the relevant system configuration files.
- Apply the device-specific configuration using the supported engineering process.
- Configure the SCADA client using the validated model and communication settings.
S1 Agile and system-level IEC 61850 engineering tools have different roles. The exact workflow depends on the MiCOM product generation and the engineering tools supported by the project.
An SCL file should not be considered proof that the physical relay has been configured successfully. The generated configuration must be applied, validated and tested against the actual device.
12. Troubleshooting MiCOM IEC 61850 SCADA Integration
The following table summarizes common integration problems.
| Problem | Possible cause | Recommended checks |
|---|---|---|
| SCADA cannot connect to relay | IP or network problem | Check IP settings, VLANs, routing and firewall rules |
| MMS association fails | Client/server configuration mismatch | Check server access point, connection settings and supported services |
| Data object cannot be found | Incorrect reference | Check the actual IED data model |
| Measurement is unavailable | Unsupported object or wrong FC | Verify the measurement model and functional constraint |
| Reports are not received | Incorrect report configuration | Check dataset, report control block and client configuration |
| Events are missing after disconnection | URCB or buffering limitation | Check whether BRCB is supported and configured |
| Incorrect breaker indication | Wrong data mapping or feedback wiring | Compare relay status, IEC 61850 value and physical position |
| Invalid quality | Source data or supervision issue | Investigate quality flags and underlying device conditions |
| Incorrect event sequence | Time synchronization problem | Check device time, synchronization and UTC handling |
| Remote command rejected | Control model or interlocking issue | Check control configuration, local/remote state and interlocks |
Wireshark analysis
Wireshark can help engineers investigate MMS communication.
Useful display filters include:
tcp.port == 102
To identify TCP retransmissions:
tcp.analysis.retransmission
To identify TCP reset packets:
tcp.flags.reset == 1
For GOOSE traffic:
goose
Or:
eth.type == 0x88b8
MMS normally uses TCP port 102. GOOSE uses Ethernet multicast and does not rely on TCP/IP.
Packet analysis should be combined with relay diagnostics, SCADA logs and engineering configuration checks.
13. Best Practices for MiCOM IEC 61850 SCADA Engineering
The following practices help reduce integration errors:
- Prepare a complete signal list before engineering begins.
- Use the correct ICD and device model for the installed relay.
- Keep IED names consistent across SCL files, network configuration and SCADA databases.
- Verify every data reference against the actual IED model.
- Check functional constraints and CDCs.
- Map quality and timestamp information for important signals.
- Configure datasets and reporting according to actual operational requirements.
- Test report recovery behavior after communication interruptions.
- Verify control models and interlocking before remote operation.
- Maintain a controlled record of SCL files and configuration revisions.
- Perform end-to-end testing between the physical relay and the SCADA HMI.
- Record the relay firmware, configuration version and communication settings in commissioning documentation.
14. Commissioning Checklist
Use the following checklist during MiCOM IEC 61850 SCADA commissioning.
IED and network configuration
- Confirm relay model, order code and firmware.
- Confirm IEC 61850 capability and supported services.
- Verify IED name and IP address.
- Check Ethernet link and network connectivity.
- Confirm the correct SCL and device configuration files.
Data model and SCADA mapping
- Verify logical device and logical node references.
- Confirm data objects and data attributes.
- Check functional constraints.
- Confirm CDC and data types.
- Verify measurement scaling and engineering units.
- Map quality and timestamp information where available.
MMS communication and reporting
- Establish MMS association.
- Verify data-model access.
- Configure datasets.
- Configure report control blocks.
- Test general interrogation.
- Test status and measurement updates.
- Verify event behavior after communication interruption.
Functional testing
- Test protection indications.
- Test breaker position indications.
- Verify relay health and alarm points.
- Check event timestamps.
- Test remote control where applicable and authorized.
- Confirm correct operation on the SCADA HMI.
- Save final configuration and test records.
15. Conclusion
IEC 61850 integration of MiCOM protection relays with SCADA systems requires more than establishing Ethernet connectivity and an MMS association. Engineers must understand the IED information model, logical node references, data objects, functional constraints, common data classes, quality attributes, timestamps, datasets and report control blocks.
A properly engineered SCADA interface provides reliable protection indications, measurements, breaker status, alarms and supported control functions. It also makes fault analysis and substation operation more effective.
For commissioning engineers, the most important principle is to verify the complete data path—from the actual relay function to its IEC 61850 data object, through MMS reporting, into the SCADA database and finally onto the operator’s HMI.
Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Elec-Engg provides practical training for engineers working with MiCOM protection relays, IEC 61850 communication, protection and control systems, and substation automation.
Training subjects include:
- MiCOM relay configuration and engineering.
- IEC 61850 architecture and data modeling.
- MMS communication, datasets and reporting.
- GOOSE configuration and testing.
- ICD, CID and SCD file engineering.
- SCADA integration and troubleshooting.
- Practical commissioning and communication testing.
Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Visit Elec-Engg to explore practical power system protection and substation automation training.
