- Introduction
- 1. Understanding MiCOM Configuration Files
- 2. Configuration Files and Engineering Software
- 3. Why Configuration Backup Is Important
- 4. Creating a MiCOM Relay Configuration Backup
- 5. Configuration Version Management
- 6. Firmware Management in MiCOM Relays
- 7. IEC 61850 Configuration and SCL File Management
- 8. Managing IEC 61850 Datasets and Control Blocks
- 9. Restoring a MiCOM Relay Configuration
- 10. Replacing a Defective MiCOM Relay
- 11. Practical Example: Replacing a MiCOM Feeder Relay Connected to SICAM PAS
- 12. Common Configuration and Firmware Problems
- Problem 1: Engineering software cannot open the project
- Problem 2: Project does not match the relay
- Problem 3: IEC 61850 data objects are missing
- Problem 4: SICAM PAS cannot establish MMS communication
- Problem 5: GOOSE communication fails after relay replacement
- Problem 6: Firmware update causes unexpected behavior
- 13. Best Practices for MiCOM Configuration Management
- 14. MiCOM Configuration Management Commissioning Checklist
- 15. Training on MiCOM Relays and IEC 61850 Engineering
- Conclusion
Introduction
Reliable configuration management is essential when engineering, commissioning, maintaining, or replacing MiCOM protection relays. A protection relay configuration contains much more than conventional protection settings. Depending on the relay model and installed communication options, it may also include communication parameters, IEC 61850 data models, datasets, report control blocks, GOOSE configuration, input/output assignments, programmable logic, disturbance recording settings, and other device-specific parameters.
Incorrect configuration handling can result in communication failures, missing SCADA indications, incorrect GOOSE subscriptions, unexpected protection behavior, or differences between the original and replacement relay.
For engineers working with MiCOM P40 Agile protection relays, understanding configuration files, firmware compatibility, backup procedures, restoration, and device replacement is therefore an important part of protection and substation automation engineering.
This article explains the main configuration-management concepts and provides practical recommendations for maintaining MiCOM relay projects.
1. Understanding MiCOM Configuration Files
A MiCOM protection relay configuration is the collection of engineering parameters required to operate the device correctly.
Depending on the relay family, configuration software, firmware, and communication hardware, these parameters may include:
- Protection function settings.
- System and measurement parameters.
- Binary input and output assignments.
- Programmable logic and control functions.
- Communication parameters.
- IEC 61850 logical device and logical node configuration.
- IEC 61850 datasets and report control blocks.
- GOOSE publisher and subscriber configuration.
- Disturbance recorder settings.
- Event and fault-recording parameters.
- User access and security settings.
Not every MiCOM relay supports all these features. The available configuration items depend on the specific relay model, order code, firmware version, and installed communication options.
A configuration file should therefore always be associated with the exact device model and applicable software version.
2. Configuration Files and Engineering Software
MiCOM relays have been engineered using different software tools across product generations.
For many MiCOM P40 Agile devices, S1 Agile is used for device configuration and engineering. Other MiCOM generations may use different tools and project formats.
The engineer should distinguish between:
- The engineering project stored on the computer.
- The configuration downloaded into the relay.
- The relay’s operational settings and records.
- IEC 61850 SCL files used for device or system integration.
- Firmware and device software packages.
These items are related, but they are not interchangeable.
For example, an SCD file describing the substation IEC 61850 system is not necessarily a complete backup of every protection setting inside a MiCOM relay.
Similarly, saving an engineering project does not automatically prove that the relay contains exactly the same configuration.
A proper backup procedure must identify which configuration elements are included and which require separate export or documentation.
3. Why Configuration Backup Is Important
Configuration backup is required throughout the relay lifecycle.
Typical situations include:
- Before changing protection settings.
- Before modifying IEC 61850 communication parameters.
- Before upgrading firmware.
- Before replacing a communication module.
- Before carrying out maintenance.
- Before replacing a defective relay.
- After successful commissioning.
- Before applying a new project revision.
- When transferring engineering responsibility to another team.
Without a reliable backup, engineers may lose important information about the original relay configuration.
A useful backup should contain the engineering project, relevant device configuration files, protection settings, communication parameters, applicable SCL files, and documentation describing the installed hardware and firmware.
4. Creating a MiCOM Relay Configuration Backup
The exact procedure depends on the device and S1 Agile software release. However, the following workflow provides a practical engineering approach.
Step 1: Identify the relay
Before connecting to the relay, record:
- Relay model and product designation.
- Complete order code.
- Serial number.
- Hardware version, where available.
- Firmware version.
- Communication interface and installed options.
- IEC 61850 support and edition, where applicable.
- Existing project identification.
This information helps prevent the use of an incompatible project or configuration.
Step 2: Connect to the device
Depending on the relay model and available interfaces, connection may be established through a supported front communication port or rear communication interface.
Confirm:
- Correct communication cable.
- Correct interface selection.
- Communication settings.
- Device availability.
- Access permissions.
- Compatibility between the engineering software and relay firmware.
Do not assume that every MiCOM model uses the same connection method.
Step 3: Retrieve the existing configuration
Where supported, use the engineering software to retrieve or upload the configuration from the relay.
The objective is to obtain the actual device configuration rather than relying only on an old project saved on another engineer’s computer.
Compare the retrieved configuration with the available project.
If differences exist, investigate them before making changes.
Step 4: Save the project
Save the retrieved configuration in a clearly identified project folder.
A useful naming convention is:
Substation_Bay_RelayModel_SerialNumber_Date_Revision
For example:
NorthSubstation_Feeder01_P443_SN123456_20261120_REV01
The example is illustrative; use the actual relay model and identification information from the project.
Step 5: Export supporting information
Where the software and device support it, separately save relevant information such as:
- Protection settings.
- Communication parameters.
- IEC 61850 configuration.
- SCL files.
- Programmable logic configuration.
- Disturbance and event records.
- Hardware and firmware identification.
- Configuration comparison reports.
Step 6: Verify the backup
A backup is not complete merely because a file has been saved.
Check that:
- The project opens successfully.
- The correct relay is identified.
- The expected configuration sections are present.
- The exported files are readable.
- The backup is stored in a controlled location.
- The project revision and date are recorded.
Where possible, maintain a second copy in an approved backup location.
5. Configuration Version Management
Version management helps engineers understand how a relay configuration has changed over time.
For example, a feeder relay may have several revisions:
| Revision | Description |
|---|---|
| REV00 | Original project received from the manufacturer |
| REV01 | Initial protection settings |
| REV02 | Changes following commissioning tests |
| REV03 | IEC 61850 communication modifications |
| REV04 | Approved operational update |
Each revision should have a clear description.
Avoid filenames such as:
- Final project.
- Final project new.
- Final project latest.
- Final project latest 2.
These names create confusion when several engineers work on the same installation.
A better approach is to use a structured revision system and maintain a change log.
Recommended change log
| Item | Example |
|---|---|
| Relay | Feeder protection relay |
| Revision | REV03 |
| Date | 20 November 2026 |
| Modified by | Responsible engineer |
| Changes | Updated GOOSE subscription |
| Approval | Approved engineering revision |
| Test status | Functional test completed |
The change log should identify the specific parameters or functions modified, not simply state that the project was updated.
6. Firmware Management in MiCOM Relays
Firmware is the embedded software running inside the protection relay.
It controls device operation and implements protection, measurement, communication, monitoring, and other supported functions.
Firmware compatibility is particularly important when working with IEC 61850.
Different firmware releases may introduce:
- New protection features.
- Changes to communication behavior.
- Additional IEC 61850 logical nodes or data objects.
- Changes to supported datasets or control blocks.
- Bug fixes.
- Improvements to device stability.
- Changes to engineering software compatibility.
- Security-related updates.
However, the availability of a feature in the IEC 61850 standard does not mean that every MiCOM firmware release implements it.
Always consult the relevant manufacturer documentation.
6.1 Identify the installed firmware
Before performing any firmware-related activity, record the firmware version currently installed in the relay.
The identification procedure depends on the model and available interfaces.
Use the appropriate device menu, engineering software, or manufacturer-approved identification procedure.
Record the firmware version in the project documentation.
6.2 Check firmware compatibility
Before updating firmware, verify compatibility with:
- Exact relay model.
- Order code.
- Hardware revision.
- Communication module.
- Existing configuration.
- Engineering software release.
- Applicable firmware package.
- IEC 61850 implementation.
- Approved project requirements.
A firmware package intended for another relay variant must not be used simply because the product names appear similar.
6.3 Firmware update precautions
Firmware upgrades should be performed only under an approved maintenance procedure.
Before upgrading:
- Obtain the correct manufacturer firmware package.
- Verify the package against the intended relay.
- Save the current configuration.
- Record the existing firmware version.
- Review manufacturer upgrade instructions.
- Confirm the consequences for configuration retention.
- Confirm the availability of a recovery procedure.
- Obtain the required operational approval.
After upgrading, verify device operation and configuration compatibility.
Do not assume that a firmware upgrade preserves every setting, communication parameter, or IEC 61850 configuration item.
7. IEC 61850 Configuration and SCL File Management
IEC 61850 introduces an additional configuration-management requirement.
MiCOM relays supporting IEC 61850 may use configuration information represented through Substation Configuration Language (SCL).
SCL is an XML-based language defined by IEC 61850-6.
Common SCL file types include:
| File | Full name | Main purpose |
|---|---|---|
| ICD | IED Capability Description | Describes the capabilities of an IED |
| CID | Configured IED Description | Describes a configured IED |
| IID | Instantiated IED Description | Describes an instantiated IED |
| SCD | Substation Configuration Description | Describes the substation IEC 61850 configuration |
| SSD | System Specification Description | Describes system-level functional requirements |
These files have different purposes and should be managed carefully.
7.1 ICD files
An ICD file typically describes the IEC 61850 capabilities of an IED.
It may contain information about:
- Logical devices.
- Logical nodes.
- Data objects.
- Communication capabilities.
- Supported services.
- Data types.
- Available control blocks.
The actual contents depend on the device implementation and manufacturer-provided description.
An ICD file should correspond to the intended relay model and relevant firmware or device release.
7.2 CID files
A CID file represents a configured IED description.
It may contain configuration information for the device’s IEC 61850 communication and data model.
The exact configuration and device-loading workflow depends on the relay and engineering software.
7.3 IID files
An IID file is used to describe an instantiated IED within an engineering workflow.
It can support the exchange of IED-specific configuration information between engineering tools.
7.4 SCD files
An SCD file describes the IEC 61850 substation configuration.
It can include information about multiple IEDs, communication networks, datasets, GOOSE control blocks, report control blocks, and other system-level engineering elements.
A change to an SCD file may affect several IEDs, not just one MiCOM relay.
For this reason, system-level changes must be coordinated with the responsible IEC 61850 engineering team.
7.5 S1 Agile and SCL engineering
S1 Agile is primarily used for supported MiCOM device engineering.
The ability to import, export, or modify particular SCL file types depends on the software version, relay model, and implemented workflow.
Full station-level SCL engineering may require a separate IEC 61850 system configuration tool.
Do not assume that S1 Agile alone provides every system-level SCL engineering function.
8. Managing IEC 61850 Datasets and Control Blocks
IEC 61850 configuration files may contain datasets and associated control blocks.
These are important when integrating MiCOM relays with SCADA systems and other IEDs.
8.1 Datasets
A dataset defines a collection of IEC 61850 data attributes.
For example, a feeder protection relay may provide data related to:
- Phase overcurrent protection.
- Earth-fault protection.
- Breaker position.
- Protection trip status.
- Current measurements.
- Voltage measurements.
- Relay health.
The actual data objects and attributes depend on the relay implementation.
When modifying a dataset, verify that the receiving system expects the same data structure.
8.2 Report control blocks
Report control blocks are used to transfer selected data to IEC 61850 clients through MMS reporting services.
Two commonly encountered types are:
- URCB: Unbuffered Report Control Block.
- BRCB: Buffered Report Control Block.
A buffered report control block can support the retention and later delivery of reports according to its implementation and configuration.
An unbuffered report control block does not provide the same persistent buffering behavior.
The supported report features, client associations, and reservation behavior must be verified for the exact relay.
8.3 GOOSE control blocks
GOOSE control blocks are used to publish datasets through Ethernet multicast messaging.
When managing GOOSE configuration, check:
- Publisher IED.
- Subscriber IED.
- Dataset definition.
- GOOSE control block.
- Destination multicast address.
- VLAN configuration.
- Application identifier.
- Configuration revision.
- External references.
- Subscriber mapping.
The ConfRev value identifies the configuration revision associated with the GOOSE control block and its dataset. It is not the firmware version of the relay.
Any modification to the relevant GOOSE configuration should be followed by appropriate verification and functional testing.
9. Restoring a MiCOM Relay Configuration
Restoring a configuration means transferring an approved configuration into a device.
The procedure depends on the relay model and engineering software.
Before restoring a project, verify:
- Exact relay model.
- Order code.
- Hardware compatibility.
- Firmware compatibility.
- Communication interface.
- Project revision.
- Configuration source.
- Protection setting approval.
- IEC 61850 compatibility.
A project created for one device variant must not automatically be assumed suitable for another.
Recommended restoration workflow
Step 1 – Identify the target relay
Record its model, order code, serial number, firmware, and hardware information.
Step 2 – Verify the source project
Open the intended project and check its identification and revision.
Step 3 – Compare configurations
Where supported, compare the project with the existing relay configuration.
Investigate differences before downloading anything.
Step 4 – Review protection settings
Confirm that protection settings are correct for the target installation.
Pay particular attention to:
- CT ratios.
- VT ratios.
- Rated frequency.
- Protection pickup values.
- Time delays.
- Directional settings.
- Differential protection parameters.
- Breaker failure settings.
- Trip matrix.
- Binary input and output assignments.
Step 5 – Review IEC 61850 configuration
Check the IED identity, logical device references, datasets, report control blocks, GOOSE configuration, and communication parameters where supported.
Step 6 – Download using the approved procedure
Use the manufacturer-supported engineering workflow.
Some changes may require a device restart or additional commissioning steps. Follow the relevant instructions.
Step 7 – Verify the relay
After restoration, verify the settings, communications, indications, and protection functions.
A successful download alone is not proof of correct operation.
10. Replacing a Defective MiCOM Relay
Replacing a defective relay is one of the most important applications of configuration backup and version management.
Although a replacement relay may have the same product designation, it is essential to confirm that its hardware, order code, firmware, and communication options are compatible with the original device.
10.1 Information to collect from the original relay
Before removing the defective relay, collect as much information as possible:
- Model and order code.
- Serial number.
- Firmware version.
- Protection settings.
- Binary input and output assignments.
- Programmable logic.
- Communication settings.
- IEC 61850 configuration.
- SCL files.
- GOOSE publisher and subscriber information.
- SCADA data mapping.
- Disturbance records and event information, where required.
If the original relay is completely inaccessible, use the latest approved project and available commissioning documentation.
10.2 Verify the replacement relay
Check that the replacement unit has the required:
- Protection functions.
- Hardware configuration.
- Input and output arrangement.
- Communication interfaces.
- IEC 61850 options.
- Firmware compatibility.
- Auxiliary supply requirements.
- CT and VT input characteristics.
A similar model name does not guarantee identical hardware or functionality.
10.3 Transfer the configuration
Use the approved engineering software and manufacturer procedure to transfer the configuration.
If the replacement relay uses a different hardware or firmware revision, check whether project conversion or engineering modifications are necessary.
Do not force an incompatible project into the replacement device.
10.4 Verify the IEC 61850 identity
An important consideration is the IEC 61850 IED identity.
The replacement device must be consistent with the station engineering configuration.
Check:
- IED name.
- Logical device references.
- IP address.
- Subnet mask.
- Gateway, if applicable.
- Communication services.
- MMS client-server configuration.
- GOOSE publisher identity.
- GOOSE subscriber references.
- Report control blocks.
- SCADA communication mapping.
If the IED name or communication identity changes, the system-level SCL configuration may also require modification.
10.5 Test communication after replacement
Perform appropriate tests for every communication service used by the installation.
For MMS, verify that the SCADA or gateway client can establish communication and access the expected data.
For GOOSE, verify that the intended subscribers receive and correctly process the published messages.
Where sampled values are implemented, verify the relevant process-bus configuration and subscription behavior.
Do not assume that the communication system will automatically recognize a replacement relay simply because it has the same model designation.
11. Practical Example: Replacing a MiCOM Feeder Relay Connected to SICAM PAS
Consider a substation with a MiCOM feeder protection relay connected to Siemens SICAM PAS.
The relay communicates through IEC 61850 MMS and also publishes a GOOSE signal used by another IED for an interlocking application.
The original relay becomes defective and must be replaced.
Original configuration
The original relay has:
- A defined IED name.
- A configured IP address.
- IEC 61850 MMS communication.
- A dataset containing protection and breaker information.
- A report control block used by SICAM PAS.
- A GOOSE publisher transmitting a protection-related signal.
- An approved protection settings revision.
Replacement procedure
1. Identify the original configuration
Retrieve the latest approved engineering project and SCL files.
Confirm the original relay model, firmware, communication parameters, and configuration revision.
2. Inspect the replacement relay
Verify its hardware, order code, firmware, communication options, and IEC 61850 capabilities.
3. Transfer the approved settings
Apply the approved protection settings and device configuration using the supported engineering procedure.
4. Verify MMS communication
Check that SICAM PAS can communicate with the replacement relay.
Verify the required data objects, reports, quality attributes, timestamps, and indications.
5. Verify GOOSE publishing
Confirm that the replacement relay publishes the expected GOOSE dataset.
Check the destination multicast address, VLAN settings, APPID, dataset, and configuration revision where applicable.
6. Verify the subscriber
Confirm that the receiving IED recognizes the GOOSE message and processes the intended signal.
7. Perform functional testing
Test the complete signal path, including the relay logic, communication network, receiving IED, and intended application.
8. Update documentation
Record the replacement relay’s serial number, firmware, project revision, test results, and approved configuration.
This example demonstrates why device replacement must be treated as an engineering and commissioning activity rather than simply a hardware exchange.
12. Common Configuration and Firmware Problems
Problem 1: Engineering software cannot open the project
Possible causes:
- Incompatible software release.
- Missing device package.
- Unsupported project format.
- Damaged project file.
- Incompatible operating environment.
Recommended actions:
- Verify the engineering software version.
- Confirm that the required device support package is installed.
- Obtain the original project from a reliable source.
- Check the manufacturer’s compatibility information.
Problem 2: Project does not match the relay
Possible causes:
- Incorrect relay model.
- Different order code.
- Different hardware revision.
- Incompatible firmware.
- Different communication options.
Recommended actions:
- Identify the exact relay.
- Review the project device identification.
- Check the supported project conversion procedure.
- Avoid downloading an unverified project.
Problem 3: IEC 61850 data objects are missing
Possible causes:
- Different firmware implementation.
- Different relay model.
- Incorrect ICD or CID file.
- Different logical device configuration.
- Unsupported logical nodes or data objects.
- Incorrect SCL engineering workflow.
Recommended actions:
- Verify the device’s actual IEC 61850 data model.
- Compare the relevant manufacturer documentation.
- Confirm the correct SCL file.
- Check the system configuration tool and engineering revision.
Problem 4: SICAM PAS cannot establish MMS communication
Possible causes:
- Incorrect IP configuration.
- Incorrect IED name or addressing.
- Network routing problems.
- MMS service not enabled or not supported as expected.
- Incorrect client configuration.
- Firewall or network security restrictions.
Recommended actions:
- Verify network connectivity.
- Check the relay IP parameters.
- Confirm that TCP port 102 is permitted where MMS over TCP is used.
- Verify the client configuration and device data model.
- Inspect the network traffic with Wireshark.
A successful TCP connection to port 102 does not, by itself, prove that MMS application communication is correctly configured.
Problem 5: GOOSE communication fails after relay replacement
Possible causes:
- Incorrect GOOSE publisher configuration.
- Incorrect subscriber external references.
- Dataset mismatch.
- Wrong multicast address.
- VLAN configuration mismatch.
- Incorrect APPID.
- Configuration revision mismatch.
- Unsupported or incorrectly configured GOOSE services.
Recommended actions:
- Compare the publisher and subscriber configuration.
- Inspect the GOOSE packets using Wireshark.
- Check the dataset and relevant configuration revision.
- Verify the subscriber’s external references and signal mapping.
- Perform end-to-end functional testing.
Useful Wireshark display filters include:
goose
eth.type == 0x88b8
Problem 6: Firmware update causes unexpected behavior
Possible causes:
- Incompatible firmware package.
- Incomplete upgrade.
- Configuration conversion issue.
- Changed feature implementation.
- Communication configuration not retained as expected.
Recommended actions:
- Verify the installed firmware.
- Review manufacturer release notes.
- Compare the device configuration with the approved backup.
- Check protection and communication functions.
- Follow the manufacturer’s recovery procedure if necessary.
13. Best Practices for MiCOM Configuration Management
For industrial substations, configuration management should be part of the formal engineering process.
Recommended practices include:
- Maintain one approved master project for each relay.
- Keep separate copies of original and modified configurations.
- Record the exact relay model and order code.
- Record firmware and hardware versions.
- Use structured revision numbering.
- Maintain a change log for every modification.
- Back up configuration before firmware upgrades.
- Store SCL files with their corresponding engineering revision.
- Keep protection settings and IEC 61850 configuration under coordinated revision control.
- Verify replacement devices before transferring configurations.
- Test MMS and GOOSE communication after relevant changes.
- Maintain approved copies in a controlled backup location.
- Document commissioning results.
- Restrict configuration changes to authorized personnel.
- Follow site-specific operational safety and change-control procedures.
14. MiCOM Configuration Management Commissioning Checklist
Use the following checklist when preparing a relay backup, restoring a project, upgrading firmware, or replacing a device.
Device identification
- Relay model and order code recorded.
- Serial number recorded.
- Hardware version checked.
- Firmware version recorded.
- Communication options verified.
Configuration backup
- Existing configuration retrieved where supported.
- Engineering project saved.
- Protection settings exported or documented.
- Communication parameters recorded.
- IEC 61850 configuration backed up.
- Relevant SCL files archived.
- Backup revision documented.
Firmware management
- Firmware compatibility verified.
- Manufacturer release notes reviewed.
- Approved firmware package obtained.
- Backup completed before upgrade.
- Post-upgrade configuration verified.
IEC 61850 verification
- IED name checked.
- IP parameters checked.
- Logical device and logical node references reviewed.
- Dataset configuration checked.
- Report control blocks verified.
- GOOSE publisher configuration checked.
- GOOSE subscriber mapping verified.
- MMS communication tested.
- GOOSE communication tested where applicable.
Final commissioning
- Protection settings independently checked.
- Binary input and output assignments verified.
- Trip and close circuits tested as applicable.
- SCADA indications verified.
- Communication alarms checked.
- Functional tests completed.
- Final project revision saved.
- Commissioning documentation updated.
15. Training on MiCOM Relays and IEC 61850 Engineering
Understanding configuration files, firmware compatibility, and device replacement is essential for protection and commissioning engineers.
Elec-Engg provides practical training in power system protection, MiCOM relays, IEC 61850 communication, and substation automation.
Training topics include:
- MiCOM protection relay configuration.
- S1 Agile engineering.
- Protection settings and device management.
- IEC 61850 MMS communication.
- GOOSE configuration and testing.
- ICD, CID, IID, and SCD file interpretation.
- Integration with SICAM PAS and SCADA systems.
- Network diagnostics using Wireshark.
- Relay testing and commissioning.
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
Visit Elec-Engg for available power system protection and substation automation training.
Conclusion
Configuration and firmware management are essential parts of the MiCOM relay lifecycle. A reliable engineering process requires accurate device identification, verified backups, controlled project revisions, firmware compatibility checks, and systematic restoration procedures.
IEC 61850 adds another layer of complexity because device configuration must remain consistent with the wider substation communication system.
When replacing a relay or modifying its configuration, engineers must verify both protection functionality and communication interoperability. A successful project download is only one step; the final configuration must be tested under the actual installation conditions.
