MiCOM IEC 61850 Integration with SCADA Systems: Practical Engineering, Data Mapping, Reporting, Controls and Commissioning

Table Of Contents
  1. 1. Introduction
  2. 2. IEC 61850 SCADA Architecture
  3. 3. MiCOM Relay as an IEC 61850 Server
  4. 4. MMS Communication Between MiCOM and SCADA
  5. 5. Understanding the MiCOM IEC 61850 Data Model
  6. 6. Functional Constraints: ST, MX, CO and Other Categories
  7. 7. SCADA Point List Engineering
  8. 8. Quality, Timestamp and Measurement Scaling
  9. 9. IEC 61850 Reporting: Sending Data to SCADA
  10. 10. Remote Control of MiCOM Relays Through SCADA
  11. 11. SCL Files in MiCOM SCADA Integration
  12. 12. Practical Example: Integrating a MiCOM Feeder Relay with SICAM PAS
  13. 13. Time Synchronization and Event Handling
  14. 14. Ethernet Network Design for MiCOM SCADA Integration
  15. 15. Cybersecurity Considerations
  16. 16. Commissioning and Testing of MiCOM IEC 61850 SCADA Integration
  17. 17. Common MiCOM IEC 61850 SCADA Integration Problems
  18. 18. Practical Commissioning Checklist
  19. 19. Conclusion
  20. 20. Practical MiCOM and IEC 61850 Training by Elec-Engg

1. Introduction

IEC 61850 has become an important communication standard for modern substation automation systems. It provides a standardized data model and communication services that allow protection relays, bay control units, meters, station controllers and SCADA systems to exchange information.

MiCOM protection relays can be integrated into IEC 61850-based SCADA architectures to provide:

  • Protection indications and alarm information.
  • Measured electrical quantities.
  • Circuit-breaker and disconnector status.
  • Protection operation and disturbance information.
  • Remote control commands, where supported.
  • Event reporting and time-stamped indications.
  • Communication with station-level systems such as SICAM PAS.

The integration process involves more than establishing an Ethernet connection. Engineers must understand the relay’s IEC 61850 data model, configure the required communication services, map data points into the SCADA database, configure reporting and controls, and verify the complete communication path during commissioning.

This article explains the practical engineering process for integrating MiCOM relays into IEC 61850 SCADA systems.

Important: IEC 61850 capabilities vary between MiCOM models, order codes, communication hardware, firmware versions and software releases. Always check the relevant technical manual, MICS, PICS, PIXIT, ICD file and release documentation before designing the integration.

2. IEC 61850 SCADA Architecture

An IEC 61850 substation automation system normally consists of three functional levels.

2.1 Process level

The process level includes equipment directly associated with the primary electrical system, such as:

  • Current transformers (CTs).
  • Voltage transformers (VTs).
  • Circuit breakers.
  • Disconnectors and earthing switches.
  • Merging units, where process bus technology is implemented.
  • Intelligent sensors and process interfaces.

Protection relays receive electrical measurements and binary signals from the process level. Depending on the architecture, these signals may be connected through conventional copper wiring or communicated using IEC 61850 services.

2.2 Bay level

The bay level contains protection and control devices responsible for individual feeders, transformers, busbars, generators and other electrical assets.

MiCOM relays can perform protection and control functions and exchange information with other IEDs and the station-level system.

Examples of information provided by a feeder protection relay include:

  • Phase overcurrent protection operation.
  • Earth-fault protection operation.
  • Circuit-breaker position.
  • Protection trip indication.
  • Protection alarm status.
  • Phase current measurements.
  • Voltage and frequency measurements, where available.
  • Relay self-supervision alarms.

2.3 Station level

The station level contains the SCADA and substation automation equipment.

Typical components include:

  • Station controller.
  • SCADA server.
  • HMI workstation.
  • Engineering workstation.
  • Gateway to the control centre.
  • Event and alarm management systems.
  • Time synchronization equipment.

A station-level system such as Siemens SICAM PAS can communicate with supported MiCOM relays through IEC 61850 MMS.

IEC 61850 : The Standard for Modern Substation Automation

linkedin.com

3. MiCOM Relay as an IEC 61850 Server

In a typical IEC 61850 SCADA architecture, a MiCOM relay operates as an IEC 61850 server.

The SCADA system or station controller operates as an IEC 61850 client.

The server makes its supported data model available to the client. The client establishes communication, discovers the available logical devices and logical nodes, reads data and subscribes to reports where supported.

A simplified communication arrangement is:

MiCOM protection relay → Ethernet network → IEC 61850 station controller → SCADA/HMI

The relay may provide information through several IEC 61850 services:

ServiceMain purpose
MMSClient-server communication
ReportingEvent and data transmission
GOOSEFast peer-to-peer event communication
Control servicesRemote operation of supported equipment
Time synchronizationSynchronization of events and device clocks
File servicesAccess to supported files and records

Not every MiCOM relay supports every service. The actual implementation must be confirmed using the documentation for the specific device.

4. MMS Communication Between MiCOM and SCADA

Manufacturing Message Specification (MMS) is commonly used for client-server communication in IEC 61850 systems.

Through MMS, the SCADA client can:

  • Establish an association with the relay.
  • Discover the relay’s data model.
  • Read measurements and indications.
  • Access supported status information.
  • Configure or enable supported reports.
  • Send control requests where permitted.
  • Receive events and updates.

MMS communication normally uses TCP port 102.

4.1 Establishing an MMS association

The general communication sequence is:

  1. The SCADA client identifies the relay’s IP address.
  2. The client establishes a TCP connection.
  3. The MMS association is initiated.
  4. The relay accepts or rejects the association according to its configuration and access rules.
  5. The client discovers the available IEC 61850 data model.
  6. The client reads the required data or configures supported reporting services.

A successful TCP connection does not necessarily mean that IEC 61850 communication is fully operational. The MMS association and application-level services must also be verified.

4.2 Data model discovery

A SCADA client should discover the actual data model exposed by the MiCOM relay rather than assuming that all standard IEC 61850 objects are implemented.

The client may browse:

  • Server.
  • Logical devices.
  • Logical nodes.
  • Data objects.
  • Data attributes.
  • Functional constraints.

For example, a relay might expose a protection logical node containing a trip-related data object. The exact reference depends on the relay’s implementation and configuration.

5. Understanding the MiCOM IEC 61850 Data Model

Correct SCADA integration requires an understanding of the IEC 61850 object hierarchy.

The general structure is:

IED → Logical Device → Logical Node → Data Object → Data Attribute

5.1 Intelligent Electronic Device

An IED represents the intelligent device communicating on the IEC 61850 network.

For example, a MiCOM feeder protection relay may have an IED name such as:

FEEDER_01

This name is part of the engineering configuration and must be consistent with the system-level design.

5.2 Logical Device

A logical device groups related functions within an IED.

A relay may contain logical devices associated with protection, measurement, control or other functional groups.

The actual logical device names are implementation-specific.

5.3 Logical Node

A logical node represents a defined functional element.

Examples of commonly encountered IEC 61850 logical node classes include:

Logical nodeGeneral function
PTOCTime-overcurrent protection
PIOCInstantaneous overcurrent protection
PDISDistance protection
PDIFDifferential protection
PTRCProtection trip conditioning
MMXUMeasurement functions
XCBRCircuit-breaker function
CSWISwitch control
GGIOGeneric process I/O
LPHDPhysical device information
LLN0Logical device common functions

These are standard logical node classes. Their presence and data objects in a specific MiCOM relay must be confirmed from its actual data model.

5.4 Data objects

A logical node contains data objects representing particular information.

For example, an XCBR logical node may contain a position data object.

The position object can represent the circuit-breaker state.

5.5 Data attributes

Data objects contain attributes describing their values and associated information.

For example, a position data object may include:

  • stVal: Status value.
  • q: Quality.
  • t: Timestamp.

This distinction is important when creating SCADA point lists. Mapping only the status value without considering quality and timestamp can result in incomplete event and alarm handling.

6. Functional Constraints: ST, MX, CO and Other Categories

Functional constraints identify the type of information represented by an IEC 61850 data attribute.

Some commonly encountered functional constraints are:

Functional constraintMeaningTypical use
STStatus informationBreaker position, protection status
MXMeasurement informationCurrent, voltage, power
COControl informationOperate commands
SPSetpoint informationSupported setpoint values
CFConfiguration informationConfiguration-related attributes
DCDescription informationDescriptive information
SGSetting group informationSetting group parameters
SESetting group editingSupported setting configuration

For SCADA integration, ST and MX are particularly important.

ST is generally used for status indications, while MX is used for measurements.

CO is relevant to control operations.

The availability and access permissions of each functional constraint depend on the particular data object and IED implementation.

7. SCADA Point List Engineering

One of the most important activities in an IEC 61850 integration project is preparing the SCADA point list.

The point list defines which information must be collected from the protection relay and how it will be presented to the operator.

A properly prepared point list should include:

  • Point name.
  • Equipment or feeder identification.
  • IEC 61850 reference.
  • Functional constraint.
  • Data type.
  • Engineering unit.
  • Scaling factor.
  • Alarm classification.
  • Event priority.
  • Normal state.
  • Quality handling.
  • Timestamp handling.
  • Control permissions, where applicable.

7.1 Typical MiCOM feeder SCADA points

The following table shows a conceptual point list. It is not a universal MiCOM data model; actual references must be obtained from the relay’s ICD file or online data model.

SCADA pointInformationTypical category
Feeder CB OpenBreaker open statusST
Feeder CB ClosedBreaker closed statusST
Protection TripProtection trip indicationST
Phase OC OperatedOvercurrent operationST
Earth Fault OperatedEarth-fault operationST
Relay HealthyDevice health indicationST
Local/RemoteControl authority indicationST
Phase A CurrentPhase A currentMX
Phase B CurrentPhase B currentMX
Phase C CurrentPhase C currentMX
Three-phase VoltageVoltage measurementMX
Active PowerActive power measurementMX
Reactive PowerReactive power measurementMX
FrequencySystem frequencyMX

A point list should be checked against the actual relay configuration. For example, a protection element may exist in the relay’s software but not be enabled or mapped to the required IEC 61850 data object.

7.2 Protection indications

Protection indications are particularly important for control-room operators.

Examples include:

  • Phase overcurrent start.
  • Phase overcurrent trip.
  • Earth-fault start.
  • Earth-fault trip.
  • Distance zone operation.
  • Differential protection operation.
  • Breaker failure initiation.
  • Protection general alarm.

Engineers must distinguish between a protection start signal and a protection trip signal. These represent different operational conditions and should not be mapped to the same SCADA point unless the project specification explicitly requires such aggregation.

8. Quality, Timestamp and Measurement Scaling

A reliable SCADA system must handle more than the raw value of a data attribute.

IEC 61850 provides quality and timestamp information that should be considered during integration.

8.1 Quality attribute q

The quality attribute provides information about the validity and reliability of a data value.

It may indicate conditions such as:

  • Validity.
  • Test condition.
  • Operator blocking.
  • Substituted value.
  • Old or questionable information.
  • Failure-related conditions.

The SCADA system should not automatically treat every received value as valid.

For example, a measurement may still contain a numerical value while its quality indicates that it is invalid or questionable.

8.2 Timestamp attribute t

The timestamp indicates when the associated information was generated or updated, according to the device’s implementation and time synchronization arrangement.

This is important for:

  • Sequence-of-events analysis.
  • Protection operation investigation.
  • Alarm chronology.
  • Fault analysis.
  • Control-room event records.

A SCADA system should preserve the source timestamp where supported rather than replacing every event time with the time at which the SCADA server received the message.

8.3 Measurement scaling and units

Measurements may be represented through IEC 61850 common data classes and associated attributes.

Engineers must check:

  • Engineering units.
  • Multiplier.
  • Scaling.
  • Data type.
  • Range.
  • Invalid or unavailable values.

For example, a current value might be represented in amperes or in scaled units, depending on the relay’s data model.

Incorrect scaling can lead to serious operational errors. A current displayed as 500 A instead of 5 A, for example, could mislead an operator and affect alarm thresholds.

Always verify the relay’s documented measurement representation and the SCADA driver’s interpretation.

9. IEC 61850 Reporting: Sending Data to SCADA

Reading individual values continuously is not always the most efficient approach.

IEC 61850 reporting allows an IED to transmit selected information to a client when configured conditions are met.

Reporting is commonly used for:

  • Protection indications.
  • Breaker status changes.
  • Alarm updates.
  • Measurement changes.
  • Event notifications.
  • General interrogation or integrity updates, where supported.

9.1 Datasets

A dataset is a collection of data attributes selected for a particular communication purpose.

For example, a feeder protection dataset may contain:

  • Circuit-breaker position.
  • Protection trip indication.
  • Relay health status.
  • Phase current measurements.
  • Earth-fault operation.

The dataset should be designed around the SCADA requirements rather than including every available relay data object.

9.2 Report Control Blocks

A Report Control Block (RCB) defines how a server sends reports to a client.

Two common types are:

Unbuffered Report Control Block (URCB)

  • Used for unbuffered reporting.
  • Reports are generally not persistently retained for later delivery if the client is disconnected.
  • Suitable for applications where temporary loss of reports can be recovered through other mechanisms.

Buffered Report Control Block (BRCB)

  • Supports buffering of reports according to the implementation.
  • Can help preserve event information during temporary client communication interruptions.
  • Useful for event-oriented applications where recovery after reconnection is required.

Actual buffering capacity, reservation behavior, entry handling and supported report options depend on the relay.

9.3 Report configuration parameters

Typical reporting parameters include:

  • Dataset reference.
  • Report Control Block name.
  • Buffering mode.
  • Integrity period.
  • General interrogation.
  • Data-change trigger.
  • Quality-change trigger.
  • Data-update trigger.
  • Optional fields.
  • Client association or reservation settings, where supported.

The exact options available in a MiCOM relay must be checked against its implementation documentation.

9.4 Integrity reporting

Integrity reporting allows the IED to send a periodic update of selected data.

This can help the SCADA system refresh its database and identify differences between the current relay state and the SCADA representation.

9.5 General interrogation

General interrogation (GI) is used to request a general update of the relevant report data.

It is particularly useful after establishing communication or recovering from a communication interruption, where supported by the server and client.

10. Remote Control of MiCOM Relays Through SCADA

Remote control is one of the most sensitive aspects of protection and control integration.

Depending on the relay model and supported IEC 61850 control services, the SCADA system may be able to operate a circuit breaker or another controllable object.

Typical operations include:

  • Circuit-breaker close.
  • Circuit-breaker open.
  • Disconnector operation, where supported.
  • Earthing switch operation, where supported.
  • Setting group selection, where supported and authorized.

Control engineering must be treated separately from ordinary status monitoring.

10.1 Direct control

In a direct-control model, the client sends an operate command without a separate select phase.

The IED processes the request according to the supported control model and configured conditions.

10.2 Select Before Operate (SBO)

In Select Before Operate, the client first selects the control object and then sends the operate command.

The selection phase allows the server to check whether the object can be selected for operation.

The operate phase follows if the selection is accepted and remains valid.

SBO can provide additional protection against unintended operations, but it does not replace electrical and operational interlocking.

10.3 Control model verification

IEC 61850 defines several control models, but support is implementation-dependent.

Engineers must verify:

  • Which control models the MiCOM relay supports.
  • Whether direct control is available.
  • Whether SBO is available.
  • Whether enhanced security is supported.
  • How command termination is reported.
  • Whether interlocking checks are implemented.
  • Whether local/remote authority is enforced.
  • Whether command timeout and cancellation are supported.

10.4 Local and remote authority

A relay may have a local/remote selector or another authority mechanism.

The SCADA system must respect the relay’s actual control authority state.

For example, a breaker may be electrically healthy and operationally available, but remote control may be blocked because the device is in local mode.

10.5 Interlocking and operational safety

Remote operation should be permitted only when all required operating conditions are satisfied.

Examples include:

  • Breaker position.
  • Disconnector position.
  • Earthing switch position.
  • Protection lockout status.
  • Busbar configuration.
  • Electrical and mechanical interlocking.
  • Local/remote selector position.
  • Operational authorization.

The control system must provide clear feedback for accepted, rejected, completed or failed commands.

Never assume that a command was successfully executed simply because the SCADA client transmitted it. The final status and command termination must be verified.

11. SCL Files in MiCOM SCADA Integration

Substation Configuration Language (SCL) is an XML-based language defined by IEC 61850-6.

SCL files support the engineering and exchange of substation automation configuration information.

The main SCL file types include:

FileFull nameMain purpose
ICDIED Capability DescriptionDescribes IED capabilities
CIDConfigured IED DescriptionDescribes the configured IED
IIDInstantiated IED DescriptionDescribes an instantiated IED
SCDSubstation Configuration DescriptionDescribes the substation system configuration
SSDSystem Specification DescriptionDescribes system requirements and functions

11.1 ICD file

The ICD file describes the capabilities of an IED, including its supported logical nodes and relevant communication configuration information.

It is useful during the initial engineering and system integration stages.

11.2 CID file

A CID file represents a configured IED description intended for the device.

It may include the relevant communication and configuration information required by the IED.

11.3 IID file

An IID file describes an instantiated IED configuration for use within an engineering workflow.

11.4 SCD file

The SCD file represents the wider substation automation configuration.

It can include information about multiple IEDs, communication networks, datasets, GOOSE subscriptions and other system-level configuration elements.

11.5 SSD file

The SSD file describes system-level functional requirements and substation-related specifications.

11.6 System engineering and device engineering

The system-level IEC 61850 configuration process and the device-level relay engineering process are related but not identical.

A system configurator may be used to engineer the overall substation configuration, while a MiCOM engineering tool is used for supported relay configuration and device-specific settings.

S1 Agile is used for supported MiCOM device engineering. It should not be assumed to provide universal system-level SCL engineering or unrestricted compatibility with every SCL file generated by another vendor’s tool.

Before exchanging configuration files, check the supported SCL version, schema, edition, namespaces and device-specific implementation.

12. Practical Example: Integrating a MiCOM Feeder Relay with SICAM PAS

Consider a substation with several outgoing feeders. Each feeder is protected by a MiCOM relay.

The objective is to collect protection status, breaker information and measurements in Siemens SICAM PAS and display them on the station HMI.

12.1 System architecture

The basic arrangement is:

  • MiCOM feeder protection relay.
  • Ethernet communication network.
  • Station communication infrastructure.
  • SICAM PAS.
  • Operator HMI.

12.2 Step 1: Check relay compatibility

Before starting configuration, identify:

  • Exact MiCOM model.
  • Complete order code.
  • Communication hardware.
  • Firmware version.
  • IEC 61850 edition.
  • Supported MMS services.
  • Available logical nodes.
  • Supported report services.
  • Supported control models.

Obtain the applicable ICD file and device documentation.

12.3 Step 2: Configure network parameters

Configure the relay’s communication parameters according to the project network plan.

Typical parameters include:

  • IP address.
  • Subnet mask.
  • Default gateway, if required.
  • Ethernet port assignment.
  • IED name.
  • Network access restrictions.

For example:

DeviceIP address
Feeder Relay 1192.168.10.11
Feeder Relay 2192.168.10.12
SICAM PAS192.168.10.100
Engineering PC192.168.10.200

These addresses are illustrative only. The actual values must follow the approved network design.

12.4 Step 3: Identify required data points

Prepare the SCADA point list.

For Feeder 1, the required data may include:

  • Breaker open/closed status.
  • Protection trip.
  • Overcurrent operation.
  • Earth-fault operation.
  • Relay healthy.
  • Phase currents.
  • Active power.
  • Reactive power.
  • Frequency.

Check each required point against the actual relay data model.

12.5 Step 4: Configure datasets and reports

Where supported, create or select appropriate datasets for the required SCADA information.

Configure the relevant Report Control Blocks.

Select suitable trigger options and integrity periods according to the application requirements.

Ensure that the SCADA client can establish the required association and receive the reports.

12.6 Step 5: Configure SICAM PAS

In the station-level engineering environment:

  1. Add the MiCOM relay to the project.
  2. Configure the communication parameters.
  3. Import or use the supported device description information.
  4. Establish the IEC 61850 connection.
  5. Browse the available data model.
  6. Select the required data points.
  7. Map them into the station database.
  8. Configure report handling.
  9. Configure alarm and event properties.
  10. Configure remote controls if permitted by the project.

The exact workflow depends on the SICAM PAS release and the supported IEC 61850 engineering interfaces.

12.7 Step 6: Configure HMI presentation

The operator HMI should present information clearly.

For example:

  • Breaker status should use clear open and closed indications.
  • Protection trips should be identified as alarms.
  • Relay communication failure should be clearly indicated.
  • Measurements should show the correct engineering units.
  • Events should display reliable timestamps.
  • Remote control should show command status and final feedback.

12.8 Step 7: Verify the complete communication path

The final test must confirm that the information displayed on the HMI corresponds to the actual relay state.

A correct relay data model alone does not guarantee correct SCADA operation. The complete path must be tested from the relay to the station controller and HMI.

13. Time Synchronization and Event Handling

Time synchronization is essential for reliable sequence-of-events analysis.

When multiple protection relays and station-level devices record events, their clocks must be sufficiently synchronized for the required application.

Depending on device capabilities and system architecture, time synchronization may use:

  • SNTP.
  • PTP.
  • IRIG-B.
  • Other supported synchronization methods.

The selected method must be compatible with the relay hardware and firmware.

13.1 Why synchronization matters

Consider a feeder fault that causes several events:

  1. Overcurrent protection starts.
  2. Protection issues a trip.
  3. Circuit breaker opens.
  4. Breaker failure logic may initiate if the breaker does not clear the fault.
  5. The SCADA system receives alarm and status updates.

If device clocks are not synchronized, the event sequence may appear incorrect.

13.2 Event timestamp handling

Engineers should verify:

  • Relay time source.
  • Time synchronization status.
  • Time zone and UTC handling.
  • Timestamp quality.
  • SCADA timestamp interpretation.
  • Event buffering and recovery behavior.
  • HMI event ordering.

The source timestamp should be preserved where the application and communication implementation support it.

14. Ethernet Network Design for MiCOM SCADA Integration

IEC 61850 integration depends on reliable network engineering.

Important design considerations include:

  • Managed Ethernet switches.
  • VLAN separation.
  • Network redundancy, where required.
  • Port security.
  • IP address management.
  • Multicast management for GOOSE traffic.
  • Network monitoring.
  • Bandwidth planning.
  • Physical network segregation.

14.1 MMS traffic

MMS generally uses TCP/IP communication and TCP port 102.

Network engineers should check that the required communication path is available between the MiCOM relay and the station controller.

14.2 GOOSE traffic

GOOSE is Ethernet-based multicast communication and uses EtherType 0x88B8.

It is not carried over TCP/IP.

GOOSE may be used for fast interlocking or protection-related communication between IEDs, while MMS is normally used for SCADA monitoring and control.

14.3 VLAN configuration

VLANs can be used to separate communication traffic and improve network organization.

For example, the network design may distinguish:

  • Protection and control traffic.
  • SCADA communication.
  • Engineering access.
  • Network management.

The actual arrangement should follow the substation network design and cybersecurity policy.

15. Cybersecurity Considerations

Protection relays are important components of critical electrical infrastructure.

Their communication interfaces must be protected against unauthorized access and misuse.

Recommended measures include:

  • Restricting access to authorized engineering workstations.
  • Using strong and controlled credentials where supported.
  • Disabling unused services.
  • Applying network segmentation.
  • Limiting remote access.
  • Monitoring network activity.
  • Maintaining configuration backups.
  • Controlling firmware and software updates.
  • Documenting configuration changes.
  • Applying approved cybersecurity procedures.

IEC 62351 defines security-related measures for power system communication protocols. However, the presence of IEC 61850 communication does not automatically mean that a MiCOM relay implements every IEC 62351 security feature.

Check the exact device documentation and approved cybersecurity requirements.

16. Commissioning and Testing of MiCOM IEC 61850 SCADA Integration

Commissioning should cover both communication and application behavior.

A successful network ping is not sufficient evidence of correct IEC 61850 integration.

16.1 Communication tests

Verify:

  • Correct IP configuration.
  • Ethernet link status.
  • TCP connectivity.
  • MMS association.
  • Data model discovery.
  • Correct IED naming.
  • Correct logical device and logical node references.

16.2 Status indication tests

Test the relevant status points.

Examples:

  • Circuit breaker open.
  • Circuit breaker closed.
  • Protection start.
  • Protection trip.
  • Relay healthy.
  • Local/remote indication.

Confirm that each state is correctly displayed on the SCADA HMI.

16.3 Measurement tests

Compare the relay measurements with the SCADA values.

Check:

  • Phase currents.
  • Voltages.
  • Active power.
  • Reactive power.
  • Frequency.
  • Engineering units.
  • Scaling.
  • Quality.

Where practical, use an approved secondary injection or test arrangement to verify the complete measurement chain.

16.4 Reporting tests

Verify:

  • Report enablement.
  • Dataset references.
  • Data-change reporting.
  • Integrity reporting.
  • General interrogation, where supported.
  • Quality-change handling.
  • Buffered report behavior, where supported.
  • Recovery after communication interruption.

16.5 Control tests

Remote control tests must be performed under an approved commissioning procedure.

Verify:

  • Local/remote authority.
  • Interlocking conditions.
  • Select operation, where applicable.
  • Operate command.
  • Command termination.
  • Final breaker position.
  • Rejection and timeout behavior.

Never perform an actual breaker operation without appropriate authorization and safety precautions.

16.6 Network troubleshooting with Wireshark

Wireshark can help engineers investigate communication problems.

Useful display filters include:

FilterPurpose
tcp.port == 102MMS-related TCP traffic
tcp.analysis.retransmissionTCP retransmissions
tcp.flags.reset == 1TCP reset packets
gooseGOOSE packets
eth.type == 0x88b8GOOSE EtherType

For MMS problems, examine connection establishment, association requests, responses and application-level communication.

For GOOSE problems, examine multicast traffic, destination MAC address, APPID, dataset configuration, stNum, sqNum, timeAllowedToLive and configuration revision (ConfRev).

A packet capture should be taken at an appropriate network point. A switch configuration that prevents the monitoring port from seeing the relevant traffic may lead to misleading conclusions.

17. Common MiCOM IEC 61850 SCADA Integration Problems

ProblemPossible causeRecommended investigation
Relay cannot connectIncorrect IP or network configurationCheck addressing, VLAN and physical link
TCP connection failsPort blocked or service unavailableCheck TCP port 102 and relay settings
MMS association rejectedClient or server configuration mismatchCheck association and access configuration
Required data point missingObject not supported or not enabledBrowse the actual relay data model
Wrong measurementScaling or unit mismatchVerify measurement representation
Status does not updateReport configuration problemCheck dataset, RCB and trigger options
Events appear in wrong orderClock synchronization issueCheck time source and timestamps
Reports stop after interruptionReport recovery or buffering issueCheck URCB/BRCB behavior and client configuration
Control command rejectedAuthority, interlocking or control modelCheck control permissions and command sequence
HMI shows communication alarmAssociation or report communication failureCheck client-server connection and event handling

18. Practical Commissioning Checklist

The following checklist can be used during an IEC 61850 SCADA integration project.

Device and documentation

  • Confirm exact MiCOM model and order code.
  • Confirm firmware and communication hardware.
  • Obtain the applicable ICD file.
  • Review MICS, PICS and PIXIT documentation.
  • Confirm IEC 61850 edition and supported services.

Network configuration

  • Confirm IP address and subnet mask.
  • Confirm IED name.
  • Check Ethernet connectivity.
  • Check VLAN and switch configuration.
  • Confirm MMS communication path.

Data engineering

  • Discover the actual data model.
  • Confirm logical device and logical node references.
  • Prepare the SCADA point list.
  • Verify functional constraints.
  • Verify data types and engineering units.
  • Check quality and timestamp handling.

Reporting

  • Verify datasets.
  • Verify Report Control Blocks.
  • Configure required report triggers.
  • Test integrity reporting.
  • Test general interrogation where supported.
  • Verify buffering and recovery behavior where supported.

Control

  • Verify supported control models.
  • Verify local/remote authority.
  • Check interlocking conditions.
  • Test command selection and operation where applicable.
  • Confirm command termination and final status.

Final commissioning

  • Test protection indications.
  • Compare measurements with relay values.
  • Test alarm and event timestamps.
  • Test communication recovery.
  • Verify HMI presentation.
  • Save configuration backups.
  • Prepare commissioning records.

19. Conclusion

Integrating MiCOM protection relays into IEC 61850 SCADA systems requires a coordinated approach involving relay engineering, IEC 61850 data modeling, MMS communication, reporting, control services, network configuration and commissioning.

The most important engineering tasks are:

  1. Understanding the actual IEC 61850 data model supported by the relay.
  2. Preparing an accurate SCADA point list.
  3. Configuring datasets and reporting services.
  4. Mapping quality, timestamps and measurements correctly.
  5. Implementing remote controls with appropriate authority and interlocking.
  6. Verifying the complete communication path during commissioning.

A reliable integration is achieved only when the relay, communication network, station controller and HMI operate together correctly.

20. Practical MiCOM and IEC 61850 Training by Elec-Engg

Elec-Engg provides practical training in power system protection, MiCOM protection relays and substation automation.

Training topics include:

  • MiCOM protection relay configuration and engineering.
  • IEC 61850 fundamentals and data modeling.
  • MMS client-server communication.
  • GOOSE configuration and testing.
  • IEC 61850 SCL engineering.
  • MiCOM integration with Siemens SICAM PAS.
  • SCADA point mapping and reporting.
  • IEC 61850 troubleshooting using Wireshark.
  • Practical protection and commissioning procedures.

Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.

Practical courses by Dr Saeed Roostaee / Elec-Engg

Website: https://elec-engg.com/

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top