- Introduction
- 1. Why Time Synchronization Is Important in Protection Systems
- 2. Understanding Time Synchronization Architecture
- 3. SNTP Time Synchronization
- 4. PTP – Precision Time Protocol
- 5. IRIG-B Time Synchronization
- 6. Comparison of SNTP, PTP and IRIG-B
- 7. UTC, Local Time and Time Zones
- 8. IEC 61850 Timestamps and Quality Information
- 9. Practical Example: Synchronizing MiCOM Relays Using SNTP
- 10. Practical Example: Investigating an Incorrect Event Sequence
- 11. Troubleshooting Time Synchronization in MiCOM Relays
- 12. Time Synchronization Commissioning Checklist
- 13. Best Practices for Substation Time Synchronization
- 14. Conclusion
- Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Introduction
Accurate time synchronization is an essential requirement in modern digital substations. Protection relays, bay control units, disturbance recorders, SCADA servers and other Intelligent Electronic Devices (IEDs) must maintain a consistent time reference to ensure that events recorded by different devices can be correctly correlated.
In a MiCOM-based substation, time synchronization is particularly important for:
- Sequence of Events (SOE) analysis.
- Protection event records.
- Fault and disturbance investigation.
- Circuit breaker operation analysis.
- IEC 61850 MMS reporting.
- GOOSE event correlation.
- SCADA alarm management.
- Comparison of records from multiple protection relays.
IEC 61850 supports the exchange of time-related information, but the actual time synchronization method depends on the relay hardware, firmware and project architecture.
Common technologies used in substation time synchronization include SNTP, PTP and IRIG-B.
This article explains these technologies, their applications in MiCOM protection relays, practical engineering considerations and commissioning procedures.
Important: Not every MiCOM relay supports every synchronization method. Always verify the exact model, order code, communication hardware, firmware and supported synchronization interfaces using the manufacturer’s documentation.
1. Why Time Synchronization Is Important in Protection Systems
Consider a substation with several protection relays connected to the same electrical network.
A fault occurs on an outgoing feeder. Several devices may record related events:
- The feeder relay detects an overcurrent condition.
- The protection function issues a trip command.
- The circuit breaker opens.
- The upstream relay records a change in current.
- The station SCADA system receives the protection indication.
- A disturbance recorder captures the fault waveform.
If the clocks of these devices are not synchronized, their event records may show inconsistent times.
This makes it difficult to determine:
- Which protection function operated first.
- Whether the breaker opened within the expected time.
- Whether the upstream protection operated as backup.
- Whether a communication delay affected the event sequence.
- How the fault developed across the substation.
Accurate synchronization allows engineers to compare records using a common time reference.
2. Understanding Time Synchronization Architecture
A typical substation time synchronization architecture contains a central time source that distributes time information to connected devices.
A simplified arrangement is:
GNSS / GPS ANTENNA
|
MASTER CLOCK
|
-------------------------
| | |
SNTP PTP IRIG-B
| | |
Ethernet Ethernet Dedicated
| | Interface
| | |
MiCOM MiCOM Protection
Relay 1 Relay 2 Devices
| | |
-------- SUBSTATION -----
TIME REFERENCE
The diagram represents possible synchronization paths. An actual installation may use only one method or a combination of technologies.
Main components
| Component | Function |
|---|---|
| GNSS antenna | Receives satellite timing information |
| Master clock | Generates and distributes the reference time |
| SNTP server | Provides time over an IP network |
| PTP grandmaster | Distributes precision time using PTP |
| Ethernet switch | Carries synchronization messages |
| IRIG-B distribution equipment | Distributes a timing signal over dedicated connections |
| MiCOM relay | Synchronizes its internal clock using supported methods |
The master clock should be selected and configured according to the required accuracy and the synchronization capabilities of the connected devices.
3. SNTP Time Synchronization
SNTP stands for Simple Network Time Protocol.
It is a simplified form of Network Time Protocol used to synchronize clocks over IP networks.
SNTP is commonly used in industrial automation and substation systems where millisecond-level synchronization may be sufficient.
3.1 How SNTP works
The SNTP client periodically communicates with an SNTP server to obtain time information.
A simplified communication process is:
- The relay is configured with the IP address of an SNTP server.
- The relay sends a time request.
- The server responds with time information.
- The relay adjusts its internal clock.
- The process repeats according to the configured synchronization interval.
3.2 SNTP configuration parameters
Depending on the relay implementation, configuration may include:
- SNTP enable/disable.
- Primary time server IP address.
- Secondary time server IP address.
- Synchronization interval.
- UTC configuration.
- Time zone settings.
- Synchronization status.
An illustrative configuration is:
| Parameter | Example |
|---|---|
| SNTP server | 192.168.10.100 |
| Secondary server | 192.168.10.101 |
| Time reference | UTC |
| Synchronization method | SNTP |
| Network | Station Ethernet |
These values are examples only and must be adapted to the actual substation network.
3.3 Advantages of SNTP
- Uses an existing Ethernet network.
- Relatively simple configuration.
- Suitable for many monitoring and event-recording applications.
- Does not require a dedicated timing cable to every relay.
3.4 Limitations of SNTP
SNTP generally provides lower timing accuracy than properly engineered precision time synchronization systems.
Accuracy depends on factors such as:
- Network delay.
- Network congestion.
- Server performance.
- Client implementation.
- Synchronization interval.
- Device clock characteristics.
For applications requiring high-precision time synchronization, engineers should evaluate PTP or a suitable dedicated timing interface.
4. PTP – Precision Time Protocol
PTP stands for Precision Time Protocol.
It is defined by IEEE 1588 and is designed to provide accurate time synchronization over packet-based networks.
PTP can achieve substantially better synchronization accuracy than ordinary SNTP when the complete system is correctly engineered.
It is particularly relevant in applications involving:
- High-precision event recording.
- Sampled Values.
- Process bus architectures.
- Time-critical measurement systems.
- Coordinated protection and monitoring.
4.1 PTP architecture
A typical PTP network includes:
- Grandmaster clock.
- Boundary clocks.
- Transparent clocks.
- Ordinary clocks.
- Ethernet network infrastructure.
Grandmaster clock: Provides the primary time reference.
Boundary clock: Receives time from an upstream PTP clock and distributes it to downstream devices.
Transparent clock: Measures the time a PTP message spends passing through network equipment and accounts for this delay.
Ordinary clock: A device that participates in PTP as a time source or time receiver.
4.2 PTP message exchange
PTP uses timing messages to calculate clock offset and network delay.
Important message types include:
- Sync.
- Follow_Up.
- Delay_Req.
- Delay_Resp.
- Announce.
The exact message sequence depends on the selected PTP profile and implementation.
The synchronization process allows a receiving device to estimate the difference between its local clock and the reference clock.
4.3 PTP profiles
Different PTP profiles are designed for different application requirements.
In power utility automation, IEC/IEEE 61850-9-3 defines a PTP profile for power utility automation.
Engineers must verify that the grandmaster, network switches and receiving IEDs support compatible PTP profiles.
Do not assume that two devices supporting IEEE 1588 automatically interoperate with identical performance. Profile, transport, delay mechanism and configuration compatibility matter.
4.4 PTP configuration considerations for MiCOM relays
Before using PTP, verify:
- Whether the relay supports PTP.
- Supported IEEE 1588 version.
- Supported PTP profile.
- Supported transport mechanism.
- Ethernet interface requirements.
- Grandmaster compatibility.
- Switch compatibility.
- Required synchronization accuracy.
PTP should not be presented as a universal feature of all MiCOM protection relays.
5. IRIG-B Time Synchronization
IRIG-B is a standardized time-code format commonly used in electrical substations and protection systems.
It can distribute time information through a dedicated timing connection.
IRIG-B is often used with:
- Protection relays.
- Disturbance recorders.
- Digital fault recorders.
- Sequence-of-events systems.
- Other substation monitoring equipment.
5.1 How IRIG-B works
A master clock generates an IRIG-B time-code signal.
The signal is distributed to connected devices through suitable cables and interfaces.
The receiving relay decodes the time information and updates its internal clock.
5.2 IRIG-B signal formats
IRIG-B has different signal formats and implementations.
Common distinctions include:
- Modulated IRIG-B.
- Unmodulated IRIG-B.
- DCLS signal.
- AM signal.
- With or without additional time information, depending on implementation.
The receiving relay must support the selected signal type and electrical interface.
5.3 Advantages of IRIG-B
- Dedicated time distribution.
- Widely used in protection and disturbance recording systems.
- Does not depend on normal Ethernet traffic.
- Can provide accurate synchronization when properly implemented.
5.4 Limitations of IRIG-B
- Requires dedicated wiring and distribution equipment.
- Signal type must match the receiving device.
- Cable and interface limitations must be considered.
- Installation and maintenance can become more complex in large substations.
6. Comparison of SNTP, PTP and IRIG-B
| Characteristic | SNTP | PTP | IRIG-B |
|---|---|---|---|
| Communication medium | Ethernet/IP | Ethernet | Dedicated timing connection |
| Main standard | RFC 4330 | IEEE 1588 | IRIG Standard 200-04 |
| Typical application | General clock synchronization | Precision network synchronization | Dedicated substation timing |
| Network dependency | Yes | Yes | No normal IP dependency |
| Timing accuracy | Generally lower | Potentially very high | Depends on signal and implementation |
| Network switch requirements | Standard IP network | Compatible PTP network | Not applicable to timing signal path |
| Configuration complexity | Relatively low | Higher | Moderate |
| MiCOM availability | Model-dependent | Model-dependent | Model-dependent |
There is no universal rule that one method is always best. The selection should be based on application requirements, device capabilities, network design and required synchronization accuracy.
7. UTC, Local Time and Time Zones
One of the most common sources of confusion in substation time synchronization is the difference between UTC and local time.
UTC is the international time reference used by many power system automation applications.
Local time includes the time-zone offset and may also include daylight-saving adjustments in some countries.
For example:
- UTC: 08:00
- Local time: 12:00
- Offset: UTC+4
The actual time-zone configuration must reflect the project location and operating requirements.
7.1 Why UTC is important
Using UTC as a common reference makes it easier to compare event records from different locations and devices.
A protection relay in one country and a disturbance recorder in another can use the same UTC reference even if their local clocks display different times.
7.2 Engineering considerations
Check:
- UTC versus local-time configuration.
- Time-zone offset.
- Daylight-saving handling.
- Timestamp interpretation in SCADA.
- Event-recording format.
- Time synchronization status.
A relay can be accurately synchronized but still display an apparently incorrect time if the time-zone configuration is misunderstood.
8. IEC 61850 Timestamps and Quality Information
IEC 61850 data objects may include a timestamp attribute identified as t.
The timestamp provides time-related information associated with the value or event.
Quality information is commonly represented by q.
These attributes are important when SCADA systems receive data through MMS reports or when engineers analyze event information.
8.1 Timestamp components
IEC 61850 timestamps can contain:
- Date.
- Time.
- Fractional seconds.
- Time-quality information.
The timestamp structure also carries information relevant to synchronization quality.
8.2 Time-quality information
Time-quality information can indicate conditions such as:
- Whether the time is synchronized.
- Whether the time is reliable.
- Whether clock failure has occurred.
- Whether the time accuracy is known or specified.
The precise interpretation should follow the relevant IEC 61850 data type and device implementation.
8.3 Why timestamp quality matters
Suppose a MiCOM relay reports a breaker opening event at 10:15:32.250.
If the time source is unreliable, the displayed timestamp may not be sufficiently accurate for detailed sequence-of-events analysis.
SCADA engineers should therefore consider both the timestamp and its associated quality information where exposed.
9. Practical Example: Synchronizing MiCOM Relays Using SNTP
Consider a substation with four MiCOM protection relays connected to a station Ethernet network.
The project uses a central SNTP server.
Network arrangement
| Device | IP address |
|---|---|
| SNTP server | 192.168.10.100 |
| MiCOM Feeder Relay 1 | 192.168.10.21 |
| MiCOM Feeder Relay 2 | 192.168.10.22 |
| MiCOM Transformer Relay | 192.168.10.23 |
| MiCOM Busbar Relay | 192.168.10.24 |
All IP addresses are illustrative.
Step 1 – Check relay support
Confirm that each relay supports SNTP and identify the correct configuration procedure.
Do not assume that all four relays use identical menus or parameter names.
Step 2 – Configure the time server
Enter the approved SNTP server address in each relay.
If supported, configure a secondary time server.
Step 3 – Check network connectivity
Confirm that the relay can communicate with the SNTP server.
Check the relevant network path, routing and any access-control rules.
Step 4 – Verify synchronization
Use the relay’s diagnostic or status information to check whether synchronization has been established.
Step 5 – Compare relay clocks
Compare the clocks of all connected devices against the master reference.
Step 6 – Verify event timestamps
Generate suitable test events under an approved test procedure and compare their recorded timestamps.
The objective is to verify that the relays use a consistent time reference and that their event records can be correctly correlated.
10. Practical Example: Investigating an Incorrect Event Sequence
Assume a feeder protection relay and an upstream transformer protection relay record the following events:
| Device | Event | Recorded time |
|---|---|---|
| Feeder relay | Overcurrent start | 14:20:15.120 |
| Feeder relay | Trip command | 14:20:15.180 |
| Feeder relay | Breaker open | 14:20:15.260 |
| Transformer relay | Current disturbance | 14:20:15.100 |
At first glance, the transformer relay appears to have recorded a disturbance before the feeder relay detected the fault.
However, this does not necessarily mean the transformer protection system operated first.
Possible causes include:
- Different clock offsets.
- Incorrect synchronization.
- Different timestamp sources.
- Event-processing delays.
- SCADA reception timestamps being confused with source timestamps.
- Incorrect time-zone configuration.
The engineer should verify the clock status and timestamp quality of each device before drawing conclusions about the protection sequence.
11. Troubleshooting Time Synchronization in MiCOM Relays
| Problem | Possible cause | Recommended checks |
|---|---|---|
| Relay clock is incorrect | Wrong time source or configuration | Check server address and synchronization settings |
| Relay is not synchronized | Network or interface problem | Check communication path and relay diagnostics |
| Different relays show different times | Different sources or clock offsets | Compare synchronization source and UTC settings |
| Event timestamps are inconsistent | Clock accuracy or timestamp configuration | Check time quality and synchronization status |
| SNTP synchronization fails | Server unavailable or network blocked | Check IP connectivity and network access rules |
| PTP synchronization fails | Profile or configuration mismatch | Check grandmaster, profile and switch compatibility |
| IRIG-B signal is not detected | Wrong signal type or wiring | Check signal format, polarity and interface |
| Time changes unexpectedly | Multiple time sources or configuration conflict | Review synchronization architecture |
| SCADA displays an incorrect time | Time-zone or timestamp conversion issue | Check UTC and local-time handling |
Useful engineering checks
For Ethernet-based synchronization, inspect:
- Network connectivity.
- IP configuration.
- Firewall and access-control rules.
- Time-server availability.
- PTP message reception, where applicable.
- Switch configuration.
- Relay synchronization diagnostics.
For IRIG-B, inspect:
- Master clock output.
- Signal type.
- Cable continuity.
- Connector condition.
- Signal level and waveform.
- Relay input configuration.
12. Time Synchronization Commissioning Checklist
Master clock
- Confirm the master clock installation.
- Verify GNSS antenna and satellite reception, if used.
- Check the selected time reference.
- Confirm UTC configuration.
- Verify available synchronization outputs.
- Record master clock status.
MiCOM relay configuration
- Confirm relay model and firmware.
- Verify supported synchronization methods.
- Configure the correct time source.
- Check primary and secondary servers, where applicable.
- Confirm the correct signal type for IRIG-B, if used.
- Verify synchronization status.
Network synchronization
- Check network connectivity.
- Verify SNTP server availability.
- Check PTP profile compatibility, if used.
- Verify switch support and configuration.
- Confirm that network policies allow the required traffic.
Functional testing
- Compare relay clocks against the master reference.
- Generate test events.
- Compare event timestamps between IEDs.
- Check time-quality information.
- Verify SCADA timestamp interpretation.
- Record synchronization accuracy and test results.
13. Best Practices for Substation Time Synchronization
For reliable time synchronization in MiCOM-based substations:
- Define the required timing accuracy before selecting the technology.
- Use a common and properly maintained time reference.
- Verify the capabilities of every installed IED.
- Keep UTC and local-time configuration consistent.
- Avoid conflicting or unintended time sources.
- Monitor synchronization status.
- Verify timestamp quality where available.
- Test event correlation between different devices.
- Document master clock settings and network architecture.
- Include time synchronization checks in periodic maintenance.
For high-accuracy applications, the complete timing chain must be evaluated. A high-precision grandmaster alone does not guarantee high accuracy at every receiving relay.
14. Conclusion
Time synchronization is a fundamental requirement for reliable protection event recording and disturbance analysis in digital substations.
SNTP provides a practical network-based synchronization method, PTP offers precision synchronization for supported systems, and IRIG-B provides dedicated time distribution through a separate interface.
For MiCOM protection relays, the correct solution depends on the specific relay model, hardware, firmware and project requirements.
Commissioning engineers should verify not only that the relay displays the correct time but also that its event timestamps are consistent, synchronized and suitable for protection sequence analysis.
Accurate time synchronization makes it possible to reconstruct fault events, compare protection operations and investigate substation disturbances with greater confidence.
Practical MiCOM Protection and IEC 61850 Training by Dr Saeed Roostaee – Elec-Engg
Elec-Engg provides practical training for protection, commissioning and substation automation engineers.
Relevant training topics include:
- MiCOM protection relay configuration.
- IEC 61850 communication and engineering.
- MMS and GOOSE communication.
- SNTP and substation time synchronization.
- IEC 61850 timestamps and quality information.
- SCL configuration and system integration.
- Protection event analysis and troubleshooting.
- Practical commissioning procedures.
Training is available through video courses, structured self-paced training, face-to-face courses and customized in-house programs.
Visit Elec-Engg for practical power system protection and substation automation training.
