- 1. Introduction
- 2. System Architecture
- 3. Understanding the MMS Client-Server Relationship
- 4. Network Configuration
- 5. MiCOM IEC 61850 Data Model
- 6. ICD and SCL File Preparation
- 7. Data Mapping in SICAM PAS
- 8. Collecting Measurements
- 9. Status Indications and Alarms
- 10. MMS Reporting and Dataset Configuration
- 11. Remote Control Through SICAM PAS
- 12. GOOSE Communication: SICAM PAS and MiCOM Relays
- 13. Time Synchronization
- 14. Redundancy and Network Availability
- 15. Practical Example: Integrating a MiCOM Feeder Relay
- 16. Testing and Commissioning
- 17. Wireshark Analysis for MiCOM and SICAM PAS
- 18. Common Integration Problems and Troubleshooting
- 19. Cybersecurity Considerations
- 20. Engineering Recommendations
- 21. Conclusion
- 22. Practical IEC 61850 and SICAM PAS Training by Elec-Engg
1. Introduction
Integrating MiCOM protection relays with Siemens SICAM PAS is a common engineering task in substations where protection, control, monitoring and SCADA functions must operate as one coordinated system.
MiCOM relays can provide protection functions, measurements, alarms, status indications and control capabilities. SICAM PAS collects and processes this information and makes it available to higher-level systems, such as a control centre, HMI or substation automation network.
When IEC 61850 is used, communication between MiCOM relays and SICAM PAS is generally based on the IEC 61850 MMS client-server model.
This article explains the engineering principles and practical workflow for integrating MiCOM protection relays with Siemens SICAM PAS, including:
- IEC 61850 system architecture
- MMS client-server communication
- MiCOM relay data model and logical nodes
- ICD and SCL files
- Data point mapping
- Measurements, indications and alarms
- Report control blocks and datasets
- Remote control engineering
- GOOSE communication
- Time synchronization and redundancy
- Testing, commissioning and troubleshooting
The procedures and capabilities described here are subject to the installed SICAM PAS version, communication options, MiCOM relay model, firmware and IEC 61850 implementation.
2. System Architecture
A typical SICAM PAS and MiCOM integration consists of three main levels:
- Protection and control level
- Substation automation and SCADA level
- Control centre level
At the protection level, MiCOM relays measure electrical quantities, detect faults and execute protection and control functions.
At the automation level, SICAM PAS communicates with the relays, collects information, manages data points and provides communication interfaces to other systems.
At the control centre level, operational information is transferred to a remote SCADA or control centre using an appropriate communication protocol.
A simplified architecture is:
CONTROL CENTRE
|
IEC 60870-5-104 / DNP3
|
SICAM PAS
IEC 61850 MMS Client
|
Ethernet Network
|
+----------+----------+
| | |
MiCOM MiCOM MiCOM
Relay 1 Relay 2 Relay 3
MMS Server MMS Server MMS Server
| | |
Feeder Transformer Busbar
Protection Protection Protection
In this architecture:
- MiCOM relays normally operate as IEC 61850 servers.
- SICAM PAS normally operates as an IEC 61850 client.
- SICAM PAS establishes communication associations with the relays.
- The relays provide their IEC 61850 data model and supported services.
- SICAM PAS collects data and transfers selected information to other systems.
The actual architecture may differ depending on the project design and the communication capabilities of each device.
3. Understanding the MMS Client-Server Relationship
IEC 61850 MMS is the primary communication mechanism used for transferring monitoring and control information between SICAM PAS and compatible MiCOM relays.
The client-server relationship is important.
MiCOM relay – IEC 61850 server
The relay provides information such as:
- Protection operation indications
- Circuit breaker status
- Disconnector status, where available
- Current and voltage measurements
- Active and reactive power
- Frequency
- Protection alarms
- Relay health and self-supervision
- Supported control objects
SICAM PAS – IEC 61850 client
SICAM PAS can perform supported client functions such as:
- Establishing an MMS association
- Reading data objects
- Receiving reports
- Reading measurements
- Monitoring status indications
- Sending supported control commands
- Collecting quality and timestamp information
MMS communication normally uses TCP port 102.
A successful network connection does not automatically mean that IEC 61850 communication is correctly configured. The client and server must also agree on the data model, services, control behaviour and communication parameters.
4. Network Configuration
Before configuring IEC 61850 communication, the Ethernet network must be designed and configured correctly.
Each MiCOM relay and the SICAM PAS communication interface must have suitable network settings.
Typical parameters include:
| Parameter | Example |
|---|---|
| SICAM PAS IP address | 192.168.10.10 |
| MiCOM Relay 1 IP | 192.168.10.21 |
| MiCOM Relay 2 IP | 192.168.10.22 |
| MiCOM Relay 3 IP | 192.168.10.23 |
| Subnet mask | 255.255.255.0 |
| Gateway | According to network design |
| MMS TCP port | 102 |
These addresses are illustrative only.
4.1 IP Address Planning
A structured IP address plan helps prevent communication problems.
For example:
- SICAM PAS communication interfaces should use reserved addresses.
- Each relay should have a unique IP address.
- Engineering workstations should use an approved network configuration.
- Protection and automation networks should follow the project’s cybersecurity design.
4.2 Network Connectivity Tests
Before proceeding with IEC 61850 configuration, check:
- Physical Ethernet connections.
- Correct switch port configuration.
- IP address and subnet settings.
- VLAN assignment, if applicable.
- Routing and firewall rules.
- Network accessibility between SICAM PAS and each relay.
A ping test may confirm basic IP connectivity, but it does not prove that the MMS service is operating correctly.
5. MiCOM IEC 61850 Data Model
The SICAM PAS configuration must correspond to the data model implemented by the MiCOM relay.
IEC 61850 organizes information through a hierarchical structure:
IED
|
+-- Logical Device (LD)
|
+-- Logical Node (LN)
|
+-- Data Object (DO)
|
+-- Data Attribute (DA)
For example, a MiCOM feeder protection relay may provide data associated with logical nodes such as:
| Logical Node | Typical function |
|---|---|
| PTOC | Time overcurrent protection |
| PIOC | Instantaneous overcurrent protection |
| PDIS | Distance protection |
| PDIF | Differential protection |
| MMXU | Measurements |
| XCBR | Circuit breaker |
| CSWI | Switching control |
| PTRC | Protection trip conditioning |
| GGIO | General-purpose input/output |
These are standard logical-node examples. Their presence, naming, data objects and implementation must be checked against the actual MiCOM model and its IEC 61850 documentation.
For example, a protection operation indication may be represented by a protection logical node with an appropriate data object and status attribute.
A current measurement may be represented through an MMXU logical node.
A circuit breaker position may be available through an XCBR logical node.
The actual object references must be taken from the relay’s implemented data model rather than assumed from the standard.
6. ICD and SCL File Preparation
SCL stands for Substation Configuration Language. It is an XML-based language defined in IEC 61850-6.
SCL files describe IED capabilities, communication parameters, data models and system-level engineering information.
The most relevant file types are:
| File | Meaning | Purpose |
|---|---|---|
| ICD | IED Capability Description | Describes the IED’s capabilities |
| CID | Configured IED Description | Describes a configured IED instance |
| IID | Instantiated IED Description | Describes an instantiated IED |
| SCD | Substation Configuration Description | Describes the substation system configuration |
| SSD | System Specification Description | Describes system-level requirements |
6.1 Exporting or Obtaining the MiCOM Description
For the selected MiCOM relay:
- Identify the exact relay model and order code.
- Check the installed firmware version.
- Confirm IEC 61850 support and edition.
- Obtain the appropriate ICD or other supported SCL description.
- Check the logical devices and logical nodes.
- Review the supported data objects and communication services.
The availability and method of obtaining SCL files depend on the MiCOM model and engineering software version.
6.2 Importing the Device into the System Configuration
The system-level engineering environment must support the required SCL import and validation functions.
A typical workflow is:
- Create or open the substation project.
- Import the MiCOM device description.
- Assign the correct IED name.
- Configure the communication access point.
- Check the IP address and network parameters.
- Review the logical device structure.
- Verify the available data objects.
- Validate the resulting system configuration.
SICAM PAS is used for automation and communication engineering. The exact SCL import, device integration and configuration workflow depends on the SICAM PAS version and the associated engineering tools.
Do not assume that every MiCOM configuration file or every SCL service can be edited directly in SICAM PAS.
7. Data Mapping in SICAM PAS
Data mapping is one of the most important stages of the integration process.
The engineer must select which information from the MiCOM relay is required by SICAM PAS and determine how it should be represented in the automation system.
Typical data categories include:
- Single-point indications
- Double-point indications
- Measurements
- Protection alarms
- Equipment status
- Counter values
- Control commands
- Device health information
7.1 Example: Feeder Protection Data
Consider a feeder protected by a MiCOM overcurrent relay.
The SICAM PAS system may need to collect the following information:
| Information | Description | Typical IEC 61850 source |
|---|---|---|
| Phase overcurrent trip | Protection operation | Relevant protection LN |
| Earth fault trip | Earth fault operation | Relevant protection LN |
| Circuit breaker position | Open/closed status | XCBR |
| Phase current | Current measurement | MMXU |
| Voltage | Voltage measurement | MMXU |
| Frequency | System frequency | MMXU |
| Relay alarm | Device alarm | Implemented status or alarm object |
| Relay healthy | Device supervision | Implemented health indication |
The table provides functional examples. The exact logical node and data-object references depend on the device implementation.
7.2 Creating a Data Point List
Before configuring SICAM PAS, prepare a structured point list.
A practical point list should include:
| Field | Example |
|---|---|
| Equipment name | Feeder 01 |
| IED name | MiCOM_FEEDER_01 |
| Logical device | LD0 |
| Logical node | MMXU |
| Data object | A |
| Data attribute | Appropriate measurement attribute |
| Data type | According to implementation |
| Functional constraint | MX |
| SCADA description | Feeder phase current |
| Engineering unit | A |
| Alarm priority | According to project philosophy |
This documentation helps maintain consistency between relay engineering, SICAM PAS configuration and control-centre database engineering.
8. Collecting Measurements
SICAM PAS can collect supported electrical measurements from MiCOM relays using IEC 61850 MMS.
Typical measurements include:
- Phase currents
- Phase-to-phase voltages
- Phase-to-neutral voltages
- Active power
- Reactive power
- Apparent power
- Power factor
- Frequency
- Energy values, where available
Measurements are commonly represented through logical nodes such as MMXU, depending on the relay’s implementation.
8.1 Measurement Data Quality
Measurement values should not be considered independently of their quality information.
IEC 61850 uses the quality attribute q to indicate the status and validity of a data value.
Relevant quality conditions may include:
- Validity
- Old data
- Inconsistent data
- Failure
- Substituted value
- Test condition
- Operator-blocked condition
The SICAM PAS engineering should preserve or correctly process the quality information according to the project requirements.
For example, a current measurement with invalid quality should not be treated as a normal valid measurement by the SCADA application.
8.2 Engineering Units and Scaling
Check the measurement scaling and engineering units carefully.
Incorrect scaling can lead to misleading control-room displays.
For example:
- Current may be represented in amperes or kiloamperes.
- Voltage may be represented in volts or kilovolts.
- Power may be represented in watts, kilowatts or megawatts.
Confirm the scaling, multiplier, unit and data type using the relay’s documentation and the actual data model.
9. Status Indications and Alarms
Protection and equipment status information is essential for substation operation.
Typical indications include:
- Overcurrent protection start
- Overcurrent protection trip
- Earth fault protection trip
- Distance protection operation
- Differential protection operation
- Circuit breaker open
- Circuit breaker closed
- Protection blocked
- Relay alarm
- Communication failure
- Device self-supervision alarm
The actual availability and representation of these indications vary between MiCOM relay types.
9.1 Protection Indications
Protection indications should be mapped carefully.
For example, distinguish between:
- Protection start
- Protection trip
- Trip output activation
- Circuit breaker opening
- Protection function blocked
These conditions are not necessarily identical.
A protection start does not always mean that the relay has issued a trip command. Similarly, a trip command does not prove that the circuit breaker has successfully opened.
The SICAM PAS database should preserve these functional distinctions.
9.2 Alarm Processing
An alarm list should define:
- Alarm description
- Source IED
- Logical node and data reference
- Alarm priority
- Normal state
- Abnormal state
- Acknowledgement requirements
- Event timestamp
- Quality handling
This is especially important when many protection relays are connected to the same SICAM PAS system.
10. MMS Reporting and Dataset Configuration
IEC 61850 reporting is an efficient method of transferring information from protection relays to SICAM PAS.
Instead of continuously reading every data point, the client can receive reports when configured data changes or when other reporting conditions occur.
The main reporting components are:
- Dataset
- Report Control Block
- Buffered Report Control Block (BRCB)
- Unbuffered Report Control Block (URCB)
- Integrity period
- General interrogation
- Trigger options
10.1 Dataset
A dataset contains selected IEC 61850 data attributes.
For example, a feeder dataset may contain:
- Circuit breaker position
- Protection trip indication
- Phase current
- Earth fault current
- Relay alarm
- Device health indication
The dataset content must be supported by the relay and configured according to the intended reporting application.
10.2 Report Control Blocks
A Report Control Block determines how the server reports dataset changes to the client.
Two common types are:
URCB – Unbuffered Report Control Block
Unbuffered reporting provides reports without the persistent event buffering characteristic of a BRCB. Events that occur while the client is disconnected may not be available later through that report mechanism.
BRCB – Buffered Report Control Block
Buffered reporting can retain event information during communication interruptions, subject to the device’s buffer capacity and implementation.
When the client reconnects, buffered events may be delivered according to the supported reporting and recovery behaviour.
10.3 Report Configuration Checks
During engineering, verify:
- The required dataset exists.
- The report control block is available.
- The client can enable the report.
- The required trigger options are supported.
- The integrity period is appropriate.
- Buffering behaviour is understood.
- Quality and timestamps are included where required.
- The report remains operational after communication recovery.
Not every MiCOM relay supports every reporting option or the same number of report control blocks.
11. Remote Control Through SICAM PAS
SICAM PAS may provide remote control of supported equipment through IEC 61850 MMS.
Typical applications include:
- Circuit breaker opening
- Circuit breaker closing
- Disconnector operation, where supported
- Reset commands
- Other permitted control functions
The actual control capability depends on the MiCOM relay, its control model, configuration, interlocking logic and project requirements.
11.1 IEC 61850 Control Models
IEC 61850 defines different control models, including:
- Direct control
- Select Before Operate (SBO)
- Enhanced security variants, where implemented
The control model determines how the client requests and executes an operation.
For SBO, the client first selects the control object and then issues the operate command within the applicable conditions.
11.2 Practical Circuit Breaker Control Example
Consider a feeder circuit breaker controlled through a MiCOM relay.
The general engineering sequence is:
- SICAM PAS receives the circuit breaker status.
- The operator requests an opening or closing operation.
- SICAM PAS sends the appropriate control request.
- The MiCOM relay processes the request.
- The relay checks configured control conditions and interlocking.
- The relay issues the appropriate output command if permitted.
- The circuit breaker operates.
- The relay updates its position indication.
- SICAM PAS receives the updated status.
The feedback status must be checked independently. A successful control request does not guarantee that the circuit breaker has physically changed position.
11.3 Control Commissioning
During testing, verify:
- Correct control object reference
- Correct control model
- Select and operate behaviour, where applicable
- Command termination
- Interlocking conditions
- Local/remote selection
- Command timeout
- Circuit breaker position feedback
- Event and alarm generation
Never test closing commands on live equipment without an approved switching procedure and appropriate operational authorization.
12. GOOSE Communication: SICAM PAS and MiCOM Relays
GOOSE is another important IEC 61850 communication service.
However, it is important to distinguish GOOSE communication from MMS-based SCADA integration.
MMS is normally used between SICAM PAS and MiCOM relays for monitoring, reporting and supported control functions.
GOOSE is primarily used for fast peer-to-peer communication between IEDs.
Typical applications include:
- Interlocking
- Breaker failure initiation
- Protection blocking
- Busbar protection signals
- Transfer trip
- Trip and permissive signals
12.1 Relay-to-Relay GOOSE
For example, two MiCOM relays may exchange a GOOSE signal.
MiCOM Relay A
GOOSE Publisher
|
| Ethernet Multicast
|
MiCOM Relay B
GOOSE Subscriber
This communication can operate independently of the SICAM PAS MMS data collection path.
12.2 GOOSE Monitoring Through SICAM PAS
Whether SICAM PAS can directly subscribe to, process or expose a particular GOOSE signal depends on the installed system architecture and supported functions.
Do not assume that SICAM PAS automatically subscribes to every GOOSE message exchanged between MiCOM relays.
Where the project requires GOOSE-based interlocking or protection logic, verify the intended publisher, subscriber and processing devices.
GOOSE configuration should be validated through the relevant SCL engineering process and tested at the actual IED level.
13. Time Synchronization
Correct time synchronization is essential for event analysis and disturbance investigation.
MiCOM relays and SICAM PAS should use a consistent time reference according to the substation time synchronization design.
Possible methods include:
- SNTP
- PTP, where supported
- IRIG-B, where supported
- Other device-specific time synchronization methods
The selected method depends on the relay model, communication hardware, firmware and system architecture.
13.1 Importance of Accurate Timestamps
Accurate timestamps help engineers:
- Reconstruct fault sequences
- Compare protection operations
- Analyze breaker operation times
- Investigate communication failures
- Correlate events from different IEDs
IEC 61850 data may include timestamp information through the t attribute.
The time quality should also be considered. A timestamp should not automatically be treated as accurate simply because it is present.
13.2 Time Synchronization Checks
During commissioning:
- Check the time source.
- Confirm the relay synchronization configuration.
- Verify SICAM PAS time settings.
- Compare event timestamps from different devices.
- Check time quality indications where available.
- Verify behaviour after loss and recovery of the time source.
14. Redundancy and Network Availability
Substation communication networks should be designed to provide the required availability.
Depending on the project, redundancy may be implemented through:
- Redundant Ethernet switches
- Redundant communication paths
- Redundant SICAM PAS architecture
- PRP
- HSR
- Network recovery mechanisms
PRP and HSR are defined in IEC 62439-3.
However, support for these mechanisms must be checked for each relay, communication module and network device.
A redundant network does not automatically make the entire SCADA system redundant. The engineering must also consider server availability, client reconnection, communication recovery and database consistency.
15. Practical Example: Integrating a MiCOM Feeder Relay
Consider a substation with one MiCOM feeder protection relay connected to SICAM PAS.
The required functions are:
- Phase current monitoring
- Earth fault current monitoring
- Circuit breaker position
- Overcurrent protection trip indication
- Earth fault protection trip indication
- Relay alarm
- Remote circuit breaker opening and closing, where supported
Step 1: Prepare the Device Information
Collect:
- MiCOM relay model
- Order code
- Firmware version
- IEC 61850 capability information
- Relay IP address
- ICD or other applicable SCL file
- Data model documentation
Step 2: Configure Network Communication
Assign the relay and SICAM PAS communication interface their approved IP addresses.
Check physical connectivity, subnet settings and network access.
Step 3: Configure the IED Description
Use the supported engineering tools to integrate the MiCOM device description into the system configuration.
Confirm the IED name, access point, logical devices and available logical nodes.
Step 4: Identify the Required Data
Prepare the point list for:
- Measurements
- Protection indications
- Circuit breaker status
- Device alarms
- Control objects
Use the actual data references from the relay documentation and configured model.
Step 5: Configure MMS Reporting
Configure the required datasets and report control blocks, where supported.
Ensure SICAM PAS can establish the association and receive the required reports.
Step 6: Configure Control Functions
Configure only the control objects and control models supported by the relay.
Check local/remote selection, interlocking and feedback indications.
Step 7: Test the Integration
Perform communication, measurement, status, alarm and control tests.
Confirm that the data received by SICAM PAS corresponds to the actual relay state.
Step 8: Complete Documentation
Record:
- IED names
- IP addresses
- Data references
- Dataset configuration
- Report control blocks
- Control models
- Time synchronization settings
- Test results
- Outstanding limitations
16. Testing and Commissioning
A complete integration test should cover the communication network, IEC 61850 services and actual application behaviour.
16.1 Communication Tests
- Verify Ethernet connectivity.
- Check IP addressing.
- Confirm MMS TCP port 102 accessibility.
- Establish the MMS association.
- Check device identification and data model access.
- Confirm communication recovery after interruption.
16.2 Measurement Tests
- Compare relay measurements with SICAM PAS values.
- Verify engineering units.
- Check scaling and multiplier.
- Confirm quality information.
- Verify timestamps.
16.3 Indication Tests
- Operate or simulate the relevant protection functions using approved procedures.
- Verify protection start indications.
- Verify trip indications.
- Check circuit breaker status.
- Confirm alarm generation.
- Check event timestamps.
16.4 Reporting Tests
- Verify dataset configuration.
- Enable the required reports.
- Test data-change reporting.
- Test integrity reporting where configured.
- Check general interrogation.
- Test BRCB recovery behaviour where supported.
16.5 Control Tests
- Check the correct control object.
- Verify the control model.
- Test select and operate where applicable.
- Confirm interlocking.
- Verify command termination.
- Confirm actual equipment feedback.
17. Wireshark Analysis for MiCOM and SICAM PAS
Wireshark is useful for investigating IEC 61850 communication problems.
Typical display filters include:
| Filter | Purpose |
|---|---|
tcp.port == 102 | MMS communication |
goose | GOOSE messages |
eth.type == 0x88b8 | GOOSE Ethernet frames |
tcp.analysis.retransmission | TCP retransmissions |
tcp.flags.reset == 1 | TCP reset packets |
For MMS communication, engineers can inspect:
- TCP connection establishment
- MMS association requests
- Association responses
- Read requests
- Report transmission
- Control requests
- Connection termination
For GOOSE communication, engineers can inspect:
- Publisher MAC address
- Multicast destination address
- APPID
- VLAN information
stNumsqNumtimeAllowedToLiveconfRev
Wireshark can help identify communication problems, but protocol capture alone does not prove that the application logic or protection scheme operates correctly.
18. Common Integration Problems and Troubleshooting
| Problem | Possible cause | Recommended check |
|---|---|---|
| SICAM PAS cannot connect to relay | IP or network problem | Check addressing, routing and switches |
| MMS association fails | Service or configuration mismatch | Check relay capability and client configuration |
| Data points are missing | Incorrect data references | Compare with the relay data model |
| Measurements are incorrect | Scaling or unit mismatch | Check measurement attributes and engineering units |
| Reports are not received | Report configuration problem | Check datasets and report control blocks |
| Events are lost during disconnection | Unbuffered reporting or buffer limitations | Check URCB/BRCB behaviour |
| Control command is rejected | Control model or interlocking issue | Check control configuration and operating conditions |
| Breaker status does not change | Feedback or wiring problem | Check relay input and breaker auxiliary contacts |
| Timestamps are inconsistent | Time synchronization issue | Check time source and quality |
| GOOSE signal is missing | Publisher/subscriber configuration issue | Check SCL, multicast and network configuration |
| Communication is intermittent | Network or device issue | Check switch logs, packet captures and device diagnostics |
19. Cybersecurity Considerations
The integration of MiCOM relays with SICAM PAS should follow the project’s cybersecurity requirements.
Important practices include:
- Separate protection and corporate networks.
- Restrict access to engineering interfaces.
- Use approved firewall rules.
- Control remote access.
- Apply suitable user permissions.
- Protect engineering workstations.
- Maintain backups of relay and system configurations.
- Monitor communication failures and unauthorized access.
- Follow applicable IEC 62351 and organizational cybersecurity requirements.
IEC 61850 communication should not be considered secure merely because it operates within a private substation network.
Security features and protocol protection mechanisms must be checked against the actual device and system implementation.
20. Engineering Recommendations
For successful MiCOM and SICAM PAS integration, engineers should follow these recommendations:
- Verify the exact MiCOM model and IEC 61850 capability before starting.
- Obtain the correct device documentation and SCL files.
- Prepare the IP address plan before configuring devices.
- Establish the complete data point list.
- Use actual logical-node and data-object references.
- Configure datasets and reports according to the required SCADA functions.
- Test measurement scaling and data quality.
- Configure controls only after reviewing interlocking and control models.
- Keep relay-to-relay GOOSE applications separate from MMS-based SCADA integration.
- Verify time synchronization across the system.
- Test communication recovery and redundancy.
- Maintain complete engineering records and commissioning reports.
21. Conclusion
Integrating MiCOM protection relays with Siemens SICAM PAS using IEC 61850 requires more than establishing an Ethernet connection.
The engineer must understand the relay’s IEC 61850 data model, MMS communication services, logical nodes, datasets, report control blocks, control models and system-level configuration.
Correct data mapping is particularly important because protection indications, measurements, alarms and equipment status must be transferred to SICAM PAS with the correct meaning, quality and timestamp.
GOOSE communication should also be understood as a separate peer-to-peer mechanism that is commonly used for fast communication between IEDs rather than as a replacement for MMS-based SCADA integration.
A properly engineered system provides reliable protection monitoring, substation automation, operational visibility and integration with higher-level SCADA systems.
22. Practical IEC 61850 and SICAM PAS Training by Elec-Engg
Elec-Engg provides practical training in power system protection, IEC 61850 communication and substation automation engineering.
Our training covers:
- IEC 61850 fundamentals and architecture
- MMS communication and reporting
- GOOSE configuration and testing
- Logical nodes and data objects
- ICD, CID, IID and SCD files
- MiCOM protection relay configuration
- Siemens SICAM PAS engineering
- SCADA data mapping and integration
- Wireshark communication analysis
- Substation automation testing and commissioning
Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.
The focus is on practical engineering applications, configuration procedures, communication analysis and real substation automation problems.
Practical courses by Dr Saeed Roostaee / Elec-Engg.
Website: https://elec-engg.com/
