MiCOM IEC 61850 ICD, CID, IID and SCD Files Explained: Complete Guide to SCL Engineering, File Structure, Configuration and Practical Substation Integration

Table Of Contents
  1. 1. Introduction
  2. 2. What Is SCL in IEC 61850?
  3. 3. Understanding the Main IEC 61850 SCL File Types
  4. 4. ICD vs CID vs IID vs SCD vs SSD
  5. 5. Internal Structure of an SCL File
  6. 6. How SCL Describes GOOSE Communication
  7. 7. How SCL Describes MMS Reporting
  8. 8. Practical SCL Engineering Workflow for MiCOM Relays
  9. 9. MiCOM S1 Agile and IEC 61850 SCL Engineering
  10. 10. Common SCL Configuration Problems
  11. 11. Validating SCL Files
  12. 12. Practical Commissioning Checklist for MiCOM IEC 61850 SCL Projects
  13. 13. Best Practices for Managing SCL Files
  14. 14. Conclusion
  15. 15. Practical MiCOM and IEC 61850 Training by Elec-Engg

1. Introduction

IEC 61850 communication in MiCOM protection relays involves more than configuring IP addresses and enabling communication services. For successful integration into a substation automation system (SAS), engineers must understand how IEC 61850 configuration files describe IED capabilities, logical devices, logical nodes, datasets, report control blocks, GOOSE messages and communication parameters.

These configuration files are based on the Substation Configuration Language (SCL), defined in IEC 61850-6. SCL provides a standardized XML-based format for exchanging engineering information between protection relays, bay controllers, merging units, SCADA systems and substation configuration tools.

The most important SCL file types are:

  • ICD: IED Capability Description
  • CID: Configured IED Description
  • IID: Instantiated IED Description
  • SCD: Substation Configuration Description
  • SSD: System Specification Description

Understanding these files is essential when integrating MiCOM protection relays into multi-vendor IEC 61850 networks.

This article explains their purposes, differences, internal structure and practical use in substation engineering.

2. What Is SCL in IEC 61850?

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

It describes the communication and functional configuration of IEC 61850-compliant substation devices and systems.

SCL allows engineering tools from different manufacturers to exchange structured information about:

  • IEDs and their access points
  • Logical devices and logical nodes
  • Data objects and datasets
  • MMS reporting configuration
  • GOOSE publishing and subscription
  • Communication networks and addressing
  • Substation topology and primary equipment
  • External signal references and inter-IED connections

Instead of manually recreating every communication parameter in different engineering applications, SCL files allow compatible tools to exchange a standardized representation of the system configuration.

Why is SCL important for MiCOM relays?

Consider a substation containing:

  • MiCOM P143 feeder protection relays
  • MiCOM P443 distance protection relays
  • Transformer protection IEDs
  • Bay control units
  • A station-level SCADA system
  • An Ethernet communication network

The devices may come from different manufacturers, but they must exchange information using a common IEC 61850 data model and communication architecture.

SCL provides the engineering framework for describing these devices and their communication relationships.

It is important to understand that SCL is a configuration exchange format. An SCL file is not, by itself, relay firmware or a complete protection settings file.

3. Understanding the Main IEC 61850 SCL File Types

Each SCL file type represents a different stage or scope of the engineering process.

3.1 ICD – IED Capability Description

IED capability

An ICD file describes the IEC 61850 capabilities of an IED as provided by its manufacturer.

It normally contains information about the supported IEC 61850 data model and communication capabilities.

For a MiCOM relay, the ICD file may describe:

  • Supported logical devices
  • Logical nodes
  • Data objects and attributes
  • Available datasets or dataset capabilities
  • MMS services and reporting capabilities
  • GOOSE publishing capabilities, where supported
  • Communication access points
  • Supported control models and functions

The ICD file is typically used as an input to the system engineering process.

Example:

An engineer is integrating a MiCOM feeder protection relay into an IEC 61850 substation.

The engineer obtains the applicable ICD file from the relay manufacturer or an approved engineering package and imports it into a compatible IEC 61850 system configuration tool.

The tool uses this description to understand the relay’s declared IEC 61850 model and available capabilities.

Important: An ICD file does not necessarily represent the final configuration of the relay installed in the substation. It describes its declared capabilities, not every configuration choice made during engineering.

3.2 CID – Configured IED Description

IED configuration

A CID file describes the configured IEC 61850 representation of a particular IED.

It can contain the configuration needed to describe the device’s communication and application model, including:

  • IED name and access point
  • Logical devices and logical nodes
  • Configured datasets
  • Report control blocks
  • GOOSE control blocks
  • Communication parameters
  • External signal references, where applicable

For example, a MiCOM relay may be configured to publish a GOOSE message containing breaker status and protection trip information.

The CID representation can describe the relevant dataset, GOOSE control block and communication parameters for that configured IED.

The actual process of transferring and activating this configuration depends on the relay model, firmware and supported engineering tools.

3.3 IID – Instantiated IED Description

An IID file represents an instantiated IED within a system engineering workflow.

It describes a specific IED instance and its relevant configuration information for integration into a wider system.

It is particularly useful in engineering processes where the IED configuration is developed separately from the complete substation configuration.

For example:

  1. A protection engineer prepares the configuration of a MiCOM relay.
  2. The IED instance is represented in an IID file.
  3. The system engineer incorporates that IED description into the overall substation engineering project.
  4. The integrated configuration is checked against the rest of the system.

The precise use of IID files depends on the engineering toolchain and the SCL engineering process being followed.

3.4 SCD – Substation Configuration Description

Complete substation project

An SCD file describes the IEC 61850 configuration of the substation as a whole.

It can include multiple IEDs, their communication networks, datasets, reporting configurations, GOOSE connections and relevant substation information.

An SCD file may contain information about:

  • All participating IEDs
  • Their logical devices and logical nodes
  • Communication subnetworks
  • IP addresses and other communication parameters
  • GOOSE publishers and subscribers
  • Dataset definitions
  • Report control blocks
  • External references between IEDs
  • Substation and primary equipment structure

For a multi-vendor substation, the SCD file is particularly important because it provides a common engineering description of the IEC 61850 system.

Example:

A substation contains MiCOM protection relays, Siemens bay controllers and a station-level SCADA system.

The SCD file can describe the IEDs and their communication relationships, allowing the system engineer to coordinate GOOSE and MMS integration across the different devices.

3.5 SSD – System Specification Description

An SSD file describes the system or substation specification.

It is generally associated with an earlier engineering stage, before the complete IED configuration has been developed.

It can describe:

  • Substation structure
  • Voltage levels and bays
  • Primary equipment
  • Functional requirements
  • Logical nodes associated with substation functions
  • Relationships between primary equipment and automation functions

An SSD file can be used as an input to the wider IEC 61850 engineering process.

4. ICD vs CID vs IID vs SCD vs SSD

The following table summarizes the main differences.

File typeFull nameMain purpose
ICDIED Capability DescriptionDescribes an IED’s declared capabilities
CIDConfigured IED DescriptionDescribes a configured IED
IIDInstantiated IED DescriptionRepresents an instantiated IED in system engineering
SCDSubstation Configuration DescriptionDescribes the overall substation IEC 61850 configuration
SSDSystem Specification DescriptionDescribes the substation or system specification

A simplified engineering sequence is:

  1. Define the substation requirements.
  2. Develop the system specification, where SSD is used.
  3. Obtain the ICD files for the selected IEDs.
  4. Instantiate and configure the IEDs.
  5. Develop datasets, reports and GOOSE communication.
  6. Integrate the IED descriptions into the substation project.
  7. Validate and generate the relevant device configuration files.
  8. Commission and verify the system.

The exact sequence is not universal. Some projects use different engineering workflows, and not every toolchain uses all five file types.

5. Internal Structure of an SCL File

SCL files use XML syntax.

An SCL document contains structured elements that describe different parts of the substation automation system.

Some of the most important elements are:

XML elementPurpose
SCLRoot element of the SCL document
HeaderProject and configuration metadata
SubstationSubstation structure and primary equipment
IEDIntelligent Electronic Device
AccessPointCommunication access point of an IED
ServerIEC 61850 server model
LDeviceLogical device
LN0Logical node zero
LNLogical node
DataSetCollection of data references
FCDAFunctional constrained data attribute reference
ReportControlMMS report control block
GSEControlGOOSE control block
InputsExternal signal inputs
ExtRefExternal reference to data from another IED
CommunicationCommunication network description
SubNetworkCommunication subnet
ConnectedAPConnection of an IED access point to a network
GSEGOOSE communication addressing information
AddressCommunication address information
PParameter within an address or communication description

5.1 IED element

The IED element represents an intelligent electronic device.

It identifies an IED and contains its access points and server model.

A substation configuration can contain multiple IED elements, each representing a different protection relay, bay controller or other IEC 61850 device.

5.2 AccessPoint element

An IED can have one or more access points.

An access point represents a communication interface through which the IED connects to the IEC 61850 system.

The actual interfaces and their functions depend on the device hardware and configuration.

5.3 Server and LDevice elements

The Server element describes the IEC 61850 server model of an IED.

Within the server, logical devices are represented by LDevice elements.

A logical device contains logical nodes that represent functions and information within the IED.

5.4 LN0 and LN elements

LN0 represents the zero logical node of a logical device.

It commonly contains configuration information such as datasets and control blocks.

LN elements represent other logical nodes, such as:

  • PTOC – Time Overcurrent Protection
  • PDIS – Distance Protection
  • PDIF – Differential Protection
  • PTRC – Protection Trip Conditioning
  • XCBR – Circuit Breaker
  • MMXU – Measurement

The availability of these logical nodes depends on the particular relay’s IEC 61850 implementation.

5.5 DataSet and FCDA elements

A dataset is a collection of IEC 61850 data references.

The DataSet element defines the dataset, while FCDA elements identify the data attributes included in it.

For example, a dataset may contain:

  • Protection trip indication
  • Circuit breaker position
  • Overcurrent protection operation
  • Phase current measurements
  • Alarm indications

The dataset can be used by MMS reporting or GOOSE communication, depending on the configuration and implementation.

5.6 ReportControl element

The ReportControl element describes an MMS report control block.

It defines how selected data is reported to an IEC 61850 client.

Important report control parameters can include:

  • Buffered or unbuffered reporting
  • Dataset association
  • Report ID
  • Trigger options
  • Integrity period
  • Buffer time
  • Optional fields

The exact supported reporting features must be checked against the IED’s capabilities.

5.7 GSEControl element

The GSEControl element describes a GOOSE control block.

It identifies the dataset used for GOOSE publishing and includes relevant control information.

The corresponding communication parameters are described in the SCL communication section.

5.8 ExtRef element

The ExtRef element describes an external reference to information originating from another IED.

It is particularly important when configuring GOOSE subscriptions and mapping external signals into an IED’s application model.

For example, a MiCOM relay may receive a GOOSE signal representing the circuit breaker status of another bay.

The external reference helps describe the relationship between the incoming information and the subscribing IED.

6. How SCL Describes GOOSE Communication

GOOSE communication is one of the most important applications of IEC 61850 in protection and substation automation.

Unlike conventional MMS client-server communication, GOOSE uses Ethernet multicast messages for fast event-based communication.

SCL describes the publisher’s GOOSE control block and dataset, as well as the subscriber’s external references and communication relationships.

6.1 GOOSE publisher configuration

The publisher IED is responsible for transmitting GOOSE messages.

The engineering process includes:

  1. Selecting the required signals.
  2. Creating a dataset.
  3. Associating the dataset with a GOOSE control block.
  4. Configuring the communication parameters.
  5. Defining the relevant multicast addressing and VLAN information.
  6. Generating or exporting the applicable IED configuration.

A MiCOM relay can act as a GOOSE publisher only when the specific model and configuration support the required service.

6.2 GOOSE subscriber configuration

The subscriber receives GOOSE messages published by another IED.

The engineering process includes:

  1. Identifying the publisher.
  2. Selecting the required GOOSE dataset signals.
  3. Creating the external references.
  4. Mapping incoming information to the appropriate application inputs.
  5. Configuring the subscribing IED.
  6. Testing the received signals and their application behavior.

6.3 Example: GOOSE breaker interlocking

Consider two adjacent feeder bays.

The first feeder relay publishes its circuit breaker status through GOOSE.

The second feeder relay subscribes to this information and uses it as part of its interlocking logic.

Conceptual GOOSE communication

MiCOM Feeder Relay 1

GOOSE publisher

Circuit breaker position

Ethernet multicast GOOSE message

MiCOM Feeder Relay 2

GOOSE subscriber

External reference → interlocking logic

The SCL configuration describes the publisher’s dataset and GOOSE control block, the subscriber’s external reference and the communication information required to establish the relationship.

The actual logic, signal mapping and response must also be configured and tested in the relay’s supported engineering environment.

7. How SCL Describes MMS Reporting

MMS is used for communication between IEC 61850 servers and clients.

In a substation, a MiCOM relay may provide data to a station-level SCADA system or an IEC 61850 gateway.

SCL can describe:

  • Logical nodes and data objects
  • Datasets
  • Report control blocks
  • Buffered reporting
  • Unbuffered reporting
  • Report trigger options
  • Client-server communication relationships

Example: Feeder protection reporting

A MiCOM feeder relay may provide the following information to the SCADA system:

  • Phase current measurements
  • Circuit breaker position
  • Overcurrent protection start
  • Overcurrent protection trip
  • Earth fault protection operation
  • Relay alarms
  • Device health information

The engineer creates an appropriate dataset and configures a report control block where supported.

The SCADA client can then use the configured reporting services to receive relevant information.

The precise data references, reporting behavior and supported services depend on the relay implementation.

8. Practical SCL Engineering Workflow for MiCOM Relays

The following workflow illustrates how a MiCOM relay can be integrated into a multi-IED IEC 61850 substation.

The exact procedure depends on the relay model, firmware, communication hardware and engineering tools.

Step 1: Identify the MiCOM relay model

Before starting the engineering process, identify:

  • Exact relay model
  • Hardware and order code
  • Communication interface
  • Firmware version
  • IEC 61850 edition
  • Supported logical nodes
  • MMS services
  • GOOSE publishing and subscription capabilities

Do not assume that every MiCOM P40 Agile relay supports the same IEC 61850 functions.

Step 2: Obtain the correct ICD file

Obtain the ICD file applicable to the exact relay implementation.

Check that the file corresponds to the relevant model and firmware or supported product configuration.

An incompatible ICD file can cause engineering problems later in the project.

Step 3: Import the ICD into a system configuration tool

Import the ICD into an IEC 61850-compatible system configurator.

The tool should be able to interpret the IED’s declared data model and capabilities.

The system engineer can then create the IED instance within the substation project.

Step 4: Configure the IED name and access point

Assign a unique IED name and configure the appropriate access point.

For example:

  • IED name: FEEDER_01
  • Access point: S1
  • Logical device: PROT

These are illustrative names, not mandatory MiCOM naming conventions.

IED names must be consistent throughout the engineering project.

Step 5: Configure logical nodes and datasets

Select the required data objects and attributes.

For example, a feeder protection dataset might include:

  • Circuit breaker position
  • Protection trip indication
  • Overcurrent protection operation
  • Earth fault protection operation
  • Current measurements

Create separate datasets for different applications when appropriate.

Avoid adding unnecessary data to GOOSE datasets, particularly where message performance and network loading are important.

Step 6: Configure MMS report control blocks

Configure the required report control blocks.

Typical engineering parameters include:

  • Report ID
  • Dataset
  • Buffered or unbuffered reporting
  • Trigger options
  • Integrity period
  • Buffer time

Confirm that the report control block configuration is supported by the relay and the intended SCADA client.

Step 7: Configure GOOSE publishing

For each GOOSE publisher:

  1. Select the dataset.
  2. Create or configure the GOOSE control block.
  3. Set the required communication parameters.
  4. Configure the multicast MAC address.
  5. Configure VLAN ID and priority where applicable.
  6. Check the transmission behavior and supervision requirements.

The Ethernet switch configuration must be consistent with the intended GOOSE network design.

Step 8: Configure GOOSE subscriptions

For each subscriber:

  1. Identify the required publisher.
  2. Select the published signal.
  3. Create the appropriate external reference.
  4. Map the signal into the relay’s supported input or application logic.
  5. Check the dataset and configuration revision.
  6. Verify the subscription and signal behavior.

A GOOSE subscription is not complete merely because the publisher and subscriber are visible in the same SCD file. The actual application mapping and relay support must also be verified.

Step 9: Configure the communication network

The SCL communication section describes the relevant network connections.

Typical parameters include:

  • Subnetwork name
  • IED access point
  • IP address
  • Subnet mask
  • Gateway, where applicable
  • GOOSE multicast MAC address
  • VLAN ID
  • VLAN priority

For example, a project may use the following illustrative network arrangement:

DeviceIP address
MiCOM Feeder 01192.168.10.11
MiCOM Feeder 02192.168.10.12
Station gateway192.168.10.100
Engineering workstation192.168.10.200

These are example addresses only. The actual network plan must follow the substation’s approved IP addressing scheme.

Step 10: Generate and validate the SCL files

After completing the system engineering, validate the configuration.

Check:

  • XML syntax
  • SCL schema compatibility
  • IED names
  • Access points
  • Logical node references
  • Dataset references
  • Report control blocks
  • GOOSE control blocks
  • External references
  • Communication addresses
  • Configuration revisions

The system configuration tool may export an SCD and device-specific CID or other supported SCL files.

Step 11: Transfer the configuration to the MiCOM relay

Use the engineering procedure and software supported by the specific MiCOM relay.

MiCOM S1 Agile is used for engineering and managing supported MiCOM products, but the availability of IEC 61850 SCL import, export and configuration functions varies by model and software version.

Some projects require a separate IEC 61850 system configurator for system-level SCL engineering.

Do not assume that an SCD file can be downloaded directly into every MiCOM relay. The actual device configuration and transfer process must follow the manufacturer’s instructions.

Step 12: Perform commissioning tests

After the configuration is applied, verify the actual communication behavior.

For MMS:

  • Establish communication with the relay.
  • Read the required data objects.
  • Verify reporting.
  • Test controls where applicable.
  • Check report buffer behavior if buffered reporting is used.

For GOOSE:

  • Verify publisher transmission.
  • Verify subscriber reception.
  • Check signal mapping.
  • Test the application logic.
  • Confirm VLAN and multicast addressing.
  • Verify communication supervision and failure behavior.

Use suitable IEC 61850 client tools and network analysis tools such as Wireshark where appropriate.

9. MiCOM S1 Agile and IEC 61850 SCL Engineering

MiCOM S1 Agile is an engineering environment used with supported MiCOM protection relays.

Depending on the relay and software version, it can support functions such as:

  • Relay configuration
  • Protection settings
  • Disturbance and event retrieval
  • Device communication
  • Supported IEC 61850-related engineering functions

However, engineers should distinguish between two different activities:

Relay engineering

This includes protection settings, programmable logic, relay-specific configuration and device-level commissioning.

System-level IEC 61850 engineering

This includes the overall substation configuration, SCL file management, inter-IED GOOSE relationships, communication network design and integration of multiple manufacturers’ devices.

A separate IEC 61850 system configuration tool may be required for some or all system-level tasks.

Always confirm the exact supported workflow in the documentation for the MiCOM model and engineering software version being used.

10. Common SCL Configuration Problems

SCL errors can affect communication, commissioning and system integration.

The following are common problems encountered during IEC 61850 engineering.

ProblemPossible causeRecommended check
ICD import failureIncorrect or unsupported SCL versionCheck file edition and schema
IED not recognizedIncorrect IED name or structureCheck IED and access point definitions
Missing logical nodeUnsupported or absent data modelCheck the relay’s MICS and ICD
Dataset errorInvalid data referenceCheck FCDA references
MMS reporting failureIncorrect report configurationCheck dataset and report control block
GOOSE not receivedIncorrect subscription or network settingsCheck publisher, subscriber and network
GOOSE configuration mismatchInconsistent configuration revisionCheck ConfRev and dataset consistency
Wrong signal receivedIncorrect external reference mappingCheck ExtRef and application mapping
Communication failureIncorrect IP or network configurationCheck addressing and connectivity
GOOSE packet not visibleVLAN or multicast filtering issueCheck switches and packet capture
SCL validation failureXML or schema errorValidate against the applicable SCL schema

10.1 Configuration revision mismatch

GOOSE control blocks include a configuration revision value, commonly represented by ConfRev.

The value is associated with changes to the relevant GOOSE configuration, particularly the dataset and control block configuration.

If the publisher and subscriber configurations are inconsistent, the subscriber may not process the message as intended.

The engineer should verify that both sides have compatible configuration and that the relay implementation handles configuration changes as specified by the manufacturer.

ConfRev is not the relay firmware revision.

10.2 Incorrect external references

A subscriber may fail to use an incoming GOOSE signal because the external reference is missing, incorrect or mapped to the wrong application input.

Check the publisher’s data reference, subscriber’s ExtRef and the actual relay logic mapping.

10.3 Incorrect VLAN and multicast configuration

GOOSE uses Ethernet multicast communication.

Incorrect multicast addressing, VLAN configuration or switch filtering can prevent the subscriber from receiving the message.

Verify the relay configuration and the Ethernet network configuration together.

10.4 Incompatible SCL versions

Different engineering tools and devices may support different IEC 61850 editions or SCL schema versions.

A file created by one tool may not be accepted by another tool without an appropriate conversion or compatibility process.

Always check the supported SCL version and edition before exchanging configuration files.

11. Validating SCL Files

SCL validation is an important part of IEC 61850 engineering.

A configuration file should be checked before it is used for commissioning.

Validation should include several levels.

1. XML validation

Check that the XML structure is syntactically correct.

2. SCL schema validation

Check that the file follows the applicable IEC 61850-6 SCL schema.

3. Engineering consistency validation

Check references between IEDs, datasets, logical nodes, control blocks and communication elements.

4. Device capability validation

Check that the configuration uses functions and data models supported by the target MiCOM relay.

5. Communication validation

Check IP addressing, GOOSE multicast parameters, VLAN settings and network design.

6. Functional validation

Verify that the configured signals produce the intended protection and automation behavior.

Passing an XML or schema validation does not guarantee that a relay will accept the configuration or that the substation application will operate correctly. Device compatibility and functional commissioning are separate requirements.

12. Practical Commissioning Checklist for MiCOM IEC 61850 SCL Projects

Use this checklist when preparing or reviewing a MiCOM IEC 61850 integration project.

  • Confirm the exact MiCOM relay model and hardware.
  • Confirm firmware and IEC 61850 edition.
  • Obtain the correct ICD file.
  • Check the relay’s PICS and MICS documentation.
  • Import the ICD into a compatible engineering tool.
  • Assign unique IED names.
  • Verify access points and logical devices.
  • Check the required logical nodes and data objects.
  • Configure datasets.
  • Configure MMS report control blocks.
  • Configure GOOSE control blocks.
  • Configure subscriber external references.
  • Verify GOOSE dataset and configuration revisions.
  • Check IP addresses and network parameters.
  • Verify VLAN and multicast settings.
  • Validate the SCL files.
  • Confirm compatibility with the target relay.
  • Transfer configuration using the approved procedure.
  • Test MMS communication and reporting.
  • Test GOOSE publishing and subscription.
  • Test signal mapping and application logic.
  • Capture and analyze network traffic where necessary.
  • Archive the final approved SCL files and configuration records.

13. Best Practices for Managing SCL Files

For large substation projects, SCL file management should be treated as part of the engineering quality process.

Recommended practices include:

Maintain controlled file versions. Keep a record of every approved ICD, CID, IID and SCD file used during engineering.

Use unique IED names. Avoid duplicate IED names and inconsistent naming between engineering tools.

Keep a clear configuration baseline. Archive the approved configuration before making changes.

Check vendor compatibility. Confirm the compatibility of the IED model, firmware, SCL edition and engineering tools.

Document GOOSE relationships. Maintain a signal matrix showing each publisher, subscriber, dataset, signal and application mapping.

Coordinate protection and SAS engineers. GOOSE communication can affect protection and interlocking functions, so configuration changes must be reviewed by the relevant engineering teams.

Test after every significant change. A modification to a dataset, GOOSE control block or external reference may affect communication and application behavior.

14. Conclusion

ICD, CID, IID, SCD and SSD files are fundamental elements of IEC 61850 engineering.

For MiCOM protection relays, these files help engineers describe device capabilities, configure IEDs, integrate communication services and coordinate protection and substation automation functions.

The most important distinction is that the ICD describes declared IED capabilities, the CID describes a configured IED, the IID represents an instantiated IED within an engineering workflow, and the SCD describes the overall substation configuration.

A sound understanding of SCL is essential for engineers working with MMS reporting, GOOSE communication, multi-vendor integration and IEC 61850 commissioning.

The engineer must also remember that SCL file compatibility does not automatically guarantee device compatibility. The exact relay model, firmware, supported services, engineering tools and manufacturer’s configuration procedures must always be considered.

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

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

Our training covers the engineering principles and practical applications of IEC 61850, including:

  • IEC 61850 architecture and communication services
  • MMS client-server communication
  • GOOSE publishing and subscription
  • Logical nodes and data objects
  • Datasets and report control blocks
  • ICD, CID, IID and SCD files
  • SCL engineering and system integration
  • MiCOM relay configuration and communication
  • IEC 61850 testing and troubleshooting
  • Practical integration of protection relays into substation automation systems

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

Visit Elec-Engg to explore practical training by Dr Saeed Roostaee in power system protection and substation automation.

Leave a Comment

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

Scroll to Top