Home / Technical Articles / Protocols applied for time synchronization in a digital substation automation

Time Synchronization

Substation automation is a mission-critical task and electric power utilities must synchronize across large-scale distributed power grid switches in a substation to enable smooth power transfer and maintain power supply integrity.

Protocols applied for time synchronization in a digital substation automation
Protocols applied for time synchronization in a digital substation automation (photo credit: Siemens)

Precise time synchronization is therefore required to ensure that substation devices have accurate clocks for system control and data acquisition, etc. Time synchronization is especially important for time stamping of sampled values (IEC61850-9-2) of current, and voltage values require accurate clocks inside the merging units.

Time synchronization is used to precisely synchronize internal (time) clocks in IEDs, merge units (MUs), protection/control units, Ethernet switches and wherever processes need to be synchronized in substation automation. It helps to achieve accurate control and precise global analysis of network response and when, where and why any faults have occurred.

In substation automation, the following applications require time synchronization:

  1. Transmission of Ethernet protocols like GOOSE and MMS
  2. Real-time data acquisition from IEDs, RTUs and MUs
  3. Real-time process control of equipment like protection relays
  4. Fault recording for fault and performance analysis

Generally there are two kinds of time synchronization in substation automation: direct time synchronization and synchronization over LAN.


  1. Protocols Applied for Time Synchronization
    1. For Direct Time Synchronization
        1. GPS
        2. IRIG-B
      1. 1PPS
    2. For Time Synchronization over LAN
      1. SNTP
      2. IEEE 1588 PTP
  2. What is the Benefit of IEEE 1588 v2?
  3. How does IEEE 1588 PTP Work?
  4. How to Apply Time Synchronization in Substation Automation

1. Protocols Applied for Time Synchronization

Normally the internal clock within network devices will be synchronized according to a synchronization time server that is connected to a GPS (Global Positioning Satellite) or a redundant satellite. Depending on the substation network application, synchronization time for events and faults can range from sub-microseconds to milliseconds.

Factors effecting time synchronization accuracy depend on the protocol, traffic load, communication media and cable distance of the network.

IEDs can be synchronized using either a dedicated timing system based on standalone cabling and signal repeaters, or a network timing system shared with other automation applications and normally based on Ethernet cables and switches.

Dedicated timing systems often use one pulse per second (1-PPS) to provide an accurate timing reference at the start of each second, or the IRIG-B time code for time and date information. GPS (or GNSS) receivers convert the time information received from GNSS into a 1-PPS signal and the IRIG-B time code, which are then used to synchronize all the IEDs in a substation.

An example of a dedicated timing network that operates independent of the substation communication network is shown in Figure 1. When the 1-PPS signal travels from the GPS receiver to the device, a propagation delay is introduced.

Separate timing and communication networks
Figure 1 – Separate timing and communication networks

During commissioning, this delay must be measured and compensated.

Substation applications, such as SCADA or disturbance recorders, requiring timing accuracy in the millisecond range, can use a network time protocol (NTP) system operating over an existing Ethernet communication network, as illustrated in Figure 2.

Combined timing and communications
Figure 2 – Combined timing and communications

However, most substation applications require timing accuracies in microseconds and consequently NTP is not suitable.

Go back to contents ↑

1.1 For Direct Time Synchronization

Traditionally direct time synchronization with the end device can be realized via dedicated wiring with fiber, coax or twisted pair cables to transport the timing signals. Normally only one time server device is required for a time synchronization task. Because the port number in the time server device for direct synchronization is restricted, only a limited number of the devices can be synchronized.

Direct time synchronization is normally implemented for the IEDs at bay and process level in substation automation.

Standard protocols for direct time synchronization in substation automation are GPS, IRIG-B and 1PPS.

Go back to contents ↑

1.1.1 GPS

GPS stands for Global Positioning Satellite. The GPS system is highly redundant and can be used for direct time synchronization or as a time source for other time protocols. An antenna for each IED or switch is required for direct time synchronization with a GPS.

The UPS system is capable of delivering timing accuracies of within ten nanoseconds of coordinated universal time (UTC).

Go back to contents ↑

1.1.2 IRIG-B

IRIG-B stands for Inter-range instrumentation group time codes B and is the industry standard for GPS time synchronization. IRIG-B can be applied in a substation for power quality and system stability monitoring, sequence of events recording and accurate time stamping for revenue billing (1 ms).

IRIG-B time code can only be transmitted via dedicated twisted pair or coax cable and it is not a low-cost solution for time synchronization.

IRIG-B needs an external time source. The accuracy of time sampled values depends on availability and quality of time synchronization can be in the microsecond range (typ. 100 ps).

Go back to contents ↑

1.1.3 1PPS

1PPS stands for one pulse per second. It is a high-precision time pulse from precision clocks like a GPS receiver that very precisely indicates the start of a second. 1PPS is sent to every user over separate lines and entails an enormous additional wiring effort.

The accuracy of time synchronization of 1 PPS can be in the micro-second range (typ. 1 ps).

Go back to contents ↑

1.2 For Time Synchronization over LAN

Time Synchronization over a LAN (Local Area Networks) synchronizes devices via an Ethernet network and can enlarge the number of devices driven through one Ethernet cable. It reduces the cabling infrastructure and cost by transporting all time synchronization information together with data communications over the same Ethernet communication medium.

Normal standard protocols are SNTP for synchronizing IEDs at station level and IEEE 1588 PTP for synchronizing IEDs at bay and process level.

Go back to contents ↑

1.2.1 SNTP

SNTP stands for Simple Network Time Protocol. It is basically NTP but lacks some internal algorithms that are not needed for all types of servers. It is widely distributed in LANs or on the Internet. SNTP allows accuracy of time synchronization into the millisecond range (typical 1-10 ms).

SNTP is suitable for a station bus but does not achieve the accuracy required by a process bus with GOOSE and SV messages.

Go back to contents ↑

1.2.3 IEEE 1588 PTP

PTP stands for Precision Time Protocol and is a future-proof standard Ethernet protocol described in the standards IEEE 1588 and IEC61588 for time synchronization.

It is a cost-efficient solution and can be applied on the basis of the existing Ethernet network in a substation. IEEE 1588 applies master/slave time synchronization mechanisms and sup-ports hardware time stamps.

IEEE 1588 has two versions and they are not directly compatible. IEEE 1588 v2 is required mostly for IEC61850-9-2 Process Buses or IEEE C37.118-2005 Synchrophasors in sub-station automation and can be converted to IRIG- B.

Distributed clocks in end devices can be synchronized with IEEE 1588 v2 in the sub-microsecond range (type 30-50 ns).

Go back to contents ↑

2. What is the Benefit of IEEE 1588 v2?

IEEE 1588 is used for time critical applications such as Substation automation and offers many benefits for utility vendors:

High Availability Solutions

IEEE 1588 v2 use Best Master Clock Selection Algorithm (BMC). The master clock in a substation can receive time synchronization messages from other potential master clocks. All clocks can operate using the same information and therefore arrive at consistent results. Fast resynchronization can be achieved when system changes occur.

At the same time, IEEE 1588 v2 prevents error accumulation in cascaded topologies, supports fault tolerance and enhances the flexibility of the system.

Low Cost Solutions

IEEE 1588 v2 can use an existing Ethernet network and reduce cabling costs. Its unicast message has shorter frame sizes in order to reduce the bandwidth consumed by the network traffic messaging and requires minimum processor performance.

It is easy to implement in IEDs, multicast Ethernet and other multicast capable networks with low cost and simple maintenance.

High Precision Solution

IEEE 1588 v2 synchronizes clocks with differing precision and resolution. It achieves network clock synchronization accuracy in the sub-microsecond range.

Go back to contents ↑

3. How does IEEE 1588 PTP Work?

IEEE 1588 PTP has two versions, PTPv1 (IEEE 1588-2002) supports ordinary clock (OC) and boundary clock (BC) mechanisms; PTPv2 (IEEE 1588-2008) supports ordinary clock (0C), boundary clock (BC) and transparent clock (TC) mechanisms.

Figure 3 – PTPv1-BC

In version one for boundary clock mechanisms, a radio clock or a GPS receiver controls a ground master clock (GM). The ground master clock determines the time base for the system and synchronizes the respective slave clock (BC in the transmission switch or OC in the end device) directly connected to it in each step.

In the slave clock, one port serves as a PTP slave port to an upstream master clock, and the other ports serve as PTP clock masters to downstream PTP clocks.

At first, the time difference between the master and the slave is corrected (offset). Then the delay time between slave and master is measured by delay request and delay response. In the end, the time in the slave or end device is synchronized according to delay time and offset.

Best PTP synchronization performance can be achieved by minimizing the number of nodes between the grand GM (grand master) device and the OC (ordinary clock) slave IED device.

In version two for transparent clock mechanisms, transparent clocks correct the “residence time” of the network device like an Ethernet Switch.

The residence time is the time delay incurred by a packet passing through the Ethernet switch and can be calculated by the time stamp between egress and ingress.

Figure 4 – PTPv2-BC

This residence time is accumulated in a correction field to realize time synchronization.

Since transparent clocks are stateless they have no impact on the reconfiguration time of ring topology networks for example. Each switch in the path appears to be a “wire” which does not skew the time calculation for packets passing through them.

This avoids the accumulation of jitter and thus reduced accuracy when using many cascaded switches.

Residence time
Figure 5 – Residence time

The IEEE 1588-2008 standard supports two types of transparent clocks, namely: End-to-End (E2E) and Peer-to-Peer (P2P).

  • End-to-End TCs only measure the time taken for a PTP event message (those that get time stamped) to transit the bridge and provide this information to the receiving clocks in the correction field.
  • Peer-to-Peer TCs use the peer delay mechanism and measure the port-to-port propagation delay time between two directly connected ports sharing the same communication technology. The peer delay mechanism is independent of the state of a port (master or slave). It operates separately in both directions of the link.

Go back to contents ↑

4. How to Apply Time Synchronization in Substation Automation

Time synchronization for a station bus and a process bus has different requirements. Figure 6 shows one example of how to realize time synchronization with different time protocols in substation automation. As shown in the figure, precise time is provided by a GPS to a time server unit as a precise time source for communication devices like switches or IEDs.

Normally a redundant time source from another time satellite can be applied to enhance system reliability.

Time synchronization in substation automation
Figure 6 – Time synchronization in substation automation

Star topology is very common for time synchronization in a station bus and a process bus. Normally time synchronizations for IEDs at bay and process level are implemented separately. However, a common precise time source can be applied.

SNTP is implemented to synchronize the switches and other remote devices, monitoring PC and control system at station level. According to the accuracy requirement in a substation, time synchronization with IEEE 1588 PIPv2 TC mode is applied for the IEDs at bay and process level with IEEE 1588 switches from process level.

Because there are no IP packets in a process bus, transmission protocol IEEE 802.3 is used for PTP messages. IRIG-B and 1PPS require separate cable and synchronize the IED5(e.g. IED-1 and IED-5) at bay and process level.

In order to achieve high availability of time synchronization, some point-to-point communication (e.g. IED-1 to IED-7) between IEDs and MUs can be applied without any communication switch.

As the future-proof time synchronization protocol, IEEE 1588 improves the reliability of the substation network.

Go back to contents ↑


  1. Time Synchronization for Transmission Substations Using GPS and IEEE 1588 by Peter A Crossley, Member, IEEE, Hao Guo, Student Member, IEEE, and Zhao Ma, Senior Member, CSEE
  2. Hirschmann, White Paper – Data communication in substation communication (SAS)
  3. IEC 61850 Communication Networks and Systems in Substations, IEC standard in ten main parts, 2002
  4. Hirschmann, White Paper Precision Clock Synchronization – The Standard IEEE 1588. Rev. 2.01 Andreas Dreher, Dirk Mohl, Markus Seehofer
  5. IEC 61850-90-4 Technical report: Network Engineering Guidelines, 2012
  6. Hirschmann Service and Support

Premium Membership

Premium membership gives you an access to specialized technical articles and extra premium content (electrical guides and software).
Get Premium Now ⚡

About Author


Edvard Csanyi

Electrical engineer, programmer and founder of EEP. Highly specialized for design of LV/MV switchgears and LV high power busbar trunking (<6300A) in power substations, commercial buildings and industry fascilities. Professional in AutoCAD programming. Present on

One Comment

  1. Eng. neama awad
    Aug 22, 2018

    Hi Edvard :

    i`m wheely grateful for your great web site & your contribution in giving a very useful post that providing a basic knowledge for undertraining engineers , my friend we have in iraq a 400kv super grid substation , it has a SCS system type Alstom ds Agile , the hardware network is completed , but the data base of substation not installed yet, can you start posting about basic of making a data base for such control system ,also we have in other substation SCS system type microscada Siemens sicam pas have similar principles, we need to know how to prepare data base for such substation , what the required resources , what the prices of software ..etc. .


Leave a Comment

Tell us what you're thinking... we care about your opinion!

Premium Membership

Get access to premium electrical guides, technical articles and much more!