Digital substations require time synchronization accurate to better than 1 microsecond. Sampled Values, GOOSE, sequence-of-events recording, traveling-wave fault location, and synchrophasor measurements all rely on precise time across the entire substation network.
Standard IEEE 1588v2 (PTP) is powerful but too flexible — it has dozens of options and many possible configurations. To get interoperable, reliable, sub-microsecond timing in a substation, the industry needed a stricter, narrower specification: a PTP profile for power utility automation.
That profile is IEC/IEEE 61850-9-3 — the official PTP Power Profile, published jointly by the IEC and IEEE in 2016. It defines exactly which PTP options, parameters, and accuracy targets must be supported by every clock, transparent clock, boundary clock, and link in a substation network.
This guide explains every requirement in the standard — verified directly against IEC/IEEE 61850-9-3:2016 Edition 1.0.
Table of Contents
1. Why a PTP Profile Is Needed
IEEE 1588v2 (PTP) is a flexible toolkit. It supports multiple transports (Ethernet, UDP/IPv4, UDP/IPv6), several delay measurement mechanisms (end-to-end vs peer-to-peer), 1-step or 2-step synchronization, ordinary/boundary/transparent clock types, and a long list of optional features.
For utility automation, you cannot afford this much flexibility. Two PTP-capable clocks from different vendors might both be “IEEE 1588 compliant” yet fail to interoperate because they chose different options. Worse, the resulting synchronization accuracy might be too poor for Sampled Values or PMU applications.
IEC/IEEE 61850-9-3 fixes this by defining a single, narrow profile that:
- Uses Layer 2 Ethernet only (no UDP/IP)
- Uses peer-to-peer (P2P) delay measurement only
- Targets ≤1 µs network time inaccuracy across the substation
- Integrates with PRP and HSR redundancy (IEC 62439-3)
- Specifies clear inaccuracy budgets for every clock in the path
Every IED in a digital substation that supports PTP for time sync should implement this profile.
2. Scope and Standards Stack
| Standard | Role |
|---|---|
| IEC 61588:2009 ¦ IEEE Std 1588-2008 | The base PTP standard. Defines all PTP concepts, message types, BMCA, and mechanisms. |
| IEC/IEEE 61850-9-3 | The Power Profile. Restricts and customizes IEEE 1588 for utility automation. |
| IEC 61850-5 | Defines synchronization classes T0 to T5 (the accuracy classes that PTP must support) |
| IEC 61869-9 | Sampled Values requirements that drive the strictest sync classes |
| IEC 62439-3 | PRP and HSR redundancy — Annex A and B handle PTP doubly-attached clocks |
| IEC TR 61850-90-4 | Network engineering guidelines for substation networks |
The Power Profile applies Layer 2 Ethernet transport per IEEE 1588:2008 Annex F and peer-to-peer delay measurement per Annex J.4 — with restricted values.
3. Profile Identification
Every PTP profile has unique identification values that allow clocks to confirm which profile they’re operating under. For IEC/IEEE 61850-9-3:
| Field | Value |
|---|---|
| profileName | IEC/IEEE 61850-9-3 “Precision time protocol profile for power utility automation” |
| profileVersion | 1.0 |
| profileIdentifier | 00-0C-CD-00-01-xy |
| organizationName | IEC Technical Committee 57 Working Group 10 |
The xy in the profile identifier is significant. The first nibble (x) encodes redundancy support:
| x value | Meaning |
|---|---|
| 0 | Singly-attached clock (no redundancy) |
| 1 | PRP redundancy |
| 2 | HSR redundancy |
| 3 | Both PRP and HSR (configurable) |
The second nibble (y) is the minor revision (0 for profileVersion 1.0).
So a PRP-capable PTP clock conforming to this profile reports profile identifier 00-0C-CD-00-01-10.
4. Clock Types in the Power Profile
The profile uses standard PTP clock types but with specific capabilities and constraints:
Ordinary Clocks (OC)
Single-port clocks that participate in PTP but don’t relay messages. Three sub-types:
| Sub-type | Definition |
|---|---|
| Slave-only | defaultDS.slaveOnly = true — no port can be in MASTER state. Used in IEDs that only consume time. |
| Grandmaster-capable | defaultDS.slaveOnly = false — port can become master if BMCA elects it. |
| Grandmaster-only | clockClass = 6 (synchronized) or 7 (holdover) — no port can be in SLAVE state. Used in dedicated time sources with GPS. |
Transparent Clocks (TC)
Forward PTP messages and add a correction field for the residence time inside the switch. Their ports don’t have PTP states. In substations, most managed Ethernet switches operate as TCs to keep accuracy budgets manageable.
Boundary Clocks (BC)
Multi-port clocks that re-generate PTP timing. One port can be in SLAVE state (upper subdomain), other ports in MASTER state (lower subdomain). BCs allow extending PTP across larger networks but add more time error than TCs.
Boundary clocks filter messages between subdomains — they propagate management messages and selected TLVs like ALTERNATE_TIME_OFFSET_INDICATOR (ATOI), but not event messages.
5. Time Inaccuracy Targets
The profile defines a strict statistical definition of “time inaccuracy”:
Time inaccuracy: time error not exceeded by 99.7% of measurements, evaluated over a series of 1000 measurements (about 20 minutes) in steady state.
Assuming a Gaussian distribution, this corresponds to three sigma (3σ = 99.7%) — no more than 3 measurements outside the specified interval out of 1000 total.
Three Levels of Time Inaccuracy
The profile distinguishes three concepts:
| Concept | Definition |
|---|---|
| Reference time inaccuracy (εRF) | Between TAI/UTC and the input of the grandmaster (e.g., GPS receiver inaccuracy) |
| Network time inaccuracy (εN) | Between the grandmaster’s reference signal and the input of a slave clock |
| Total time inaccuracy (εT) | εRF + εN — between TAI/UTC and the input of the slave clock |
Steady-State Definition
“Steady state” means:
- 30 seconds after a single master starts sending sync messages
- 16 seconds after a change of master
- No change to environmental temperature
- The clock has been energized for at least 30 minutes (for temperature-controlled oscillators)
6. Network Time Inaccuracy Budget
The profile targets network time inaccuracy better than ±1 µs after the time signal crosses approximately 15 TCs or 3 BCs.
This is the design rule. It means:
- If your substation network has more than 15 transparent clocks in series, you risk exceeding 1 µs
- If you use boundary clocks, you must stay under 3 in series
- Mixed topologies (TCs + BCs) require careful budget calculation
The 1 µs target meets the requirements of:
- IEC 61850-5 Class T5 (1 µs for substation automation)
- IEC 61869-9 Sampled Values for protection
For classes that need 4 µs or worse (T0 to T3), more network elements can be tolerated.
7. Grandmaster Requirements
The grandmaster is the time source. Its accuracy directly impacts everything downstream.
Grandmaster Time Inaccuracy
A grandmaster-capable clock shall have a time inaccuracy ≤ 250 ns between its applied time reference signal (GPS, IRIG-B) and the produced sync messages.
This corresponds to IEEE 1588:2008 clockAccuracy value 22H.
Grandmaster Holdover
A grandmaster shall remain within the 250 ns time inaccuracy for a holdover time of at least 5 seconds after losing its time reference signal, given it was in steady state.
If the time reference signal is lost for longer than 5 seconds, the clock’s accuracy will drift.
Grandmaster Clock Quality During Reference Loss
The grandmaster shall adjust its clockClass according to IEEE 1588 Table 5:
clockClass | Condition |
|---|---|
| 6 | Synchronized to time reference signal, in steady state |
| 7 | In holdover (within 5 s of losing reference) |
| 52 | Time error exceeds 250 ns (after losing reference) |
| 187 | Time error exceeds 1 µs |
| 6 | After recovering reference signal and reaching steady state |
The clockClass advertises the quality of the grandmaster to all downstream clocks. Other clocks use the Best Master Clock Algorithm (BMCA) to select the best available grandmaster, so a degrading clockClass may cause an alternate grandmaster to take over.
Grandmaster Traceable Flags
PTP messages carry timeTraceable and frequencyTraceable flags. A grandmaster:
- With GPS time reference sets
timeTraceable = true - With only 1PPS frequency reference sets
frequencyTraceable = true
These flags are not considered by the BMCA. To prioritize a time-traceable source over a frequency-traceable one in the same time domain, configure Priority1.
8. Transparent Clock (TC) Requirements
A TC shall introduce less than 50 ns of device time inaccuracy, measured between sync messages at any ingress port and the produced sync messages at any egress port, given it is in steady state.
This includes:
- Time errors in measuring residence delay
- Peer delay measurement at ingress port
- Responding to peer delay measurement on egress port(s)
A TC should forward Sync messages even if not yet in steady state — this avoids unnecessary delay during startup.
💡 Design implication: With 50 ns per TC, you can chain ~15 TCs and still stay under 1 µs.
9. Boundary Clock (BC) Requirements
A BC shall introduce less than 200 ns of device time inaccuracy between the port in SLAVE state and any port in MASTER state, given it is in steady state.
This is 4× more than a TC — which is why the budget allows only 3 BCs vs 15 TCs.
BC as Free-Running Grandmaster
If a BC has no port in SLAVE state and no time reference signal, it operates as a free-running master per IEEE 1588:2008 J.4.4.1.
BC as Master in Holdover
A BC shall remain within the 250 ns time inaccuracy for a holdover time of at least 5 seconds after losing its time reference signal or PTP synchronization, given it was in steady state.
A BC should send Announce and Sync messages even if not yet in steady state.
10. Media Converter Requirements
Media converters (e.g., fibre-to-copper) introduce a delay considered in the peer-to-peer measurement. This delay can have significant jitter and might differ in each direction (asymmetry).
The profile has two rules:
| Media converter type | Requirement |
|---|---|
| IEC 61588-supporting (treated as TC or BC) | Subject to TC requirements (50 ns) or BC requirements (200 ns) |
| Non-IEC 61588-supporting (transparent to PTP) | Jitter < 50 ns and asymmetry < 25 ns |
If you mix-and-match fibre and copper in a substation, make sure the media converters meet at least the second criterion.
11. Link Requirements
Links (fibre or copper) present a predictable and nearly constant propagation delay (~5 µs/km). This delay’s average is regularly measured by peer-to-peer delay measurement.
The key concern is asymmetry — when the forward propagation delay differs from the reverse delay. This cannot be measured by PTP; it must be known by network engineering and compensated.
The profile requires:
- Links shall present a propagation asymmetry of less than 25 ns, OR
- Links shall have a known propagation asymmetry with asymmetry variation < 25 ns
⚠️ Note: Radio links are explicitly excluded from this profile. Only wired Ethernet (fibre or copper) is supported.
12. PRP and HSR Redundancy Integration
This is where IEC/IEEE 61850-9-3 stands out from generic IEEE 1588 — it natively handles the doubly-attached clocks of PRP and HSR networks.
Singly-Attached Clocks
For clocks with one PTP port, the profile uses the default Best Master Clock Algorithm of IEEE 1588:2008 (Sections 9.3.2, 9.3.3, 9.3.4).
Doubly-Attached Clocks (PRP/HSR)
For clocks with paired ports (one in each PRP LAN, or two in an HSR ring), the profile extends the BMCA according to IEC 62439-3:2016, Annex A.
This extension handles:
- Election of master when both ports receive Announce messages from the same grandmaster via different paths
- Selection of best path when announce messages arrive from different masters on different LANs
- Failover when one LAN of a PRP network fails
Each redundancy mode has its own profile identifier (see Section 3) — x=1 for PRP, x=2 for HSR, x=3 for both configurable.
RedBox Operating Modes
The profile defines several RedBox PTP modes (declared in the PICS):
| Mode | Description |
|---|---|
| RedBox as TC (DATC) | Doubly-Attached TC — transparently forwards PTP between attached LAN and ring |
| RedBox as Stateless TC (SLTC) | Stateless TC variant |
| RedBox as Three-way BC (TWBC) | BC with three logical ports (LAN A, LAN B, attached side) |
| RedBox as DAC BC (DABC) | Doubly-Attached Clock BC |
For PRP/HSR architecture details, see: PRP, HSR, RedBox and QuadBox Explained
13. Default PTP Attribute Settings
The profile mandates specific default settings for every conforming clock:
| PTP Attribute | Default Value | Range |
|---|---|---|
defaultDS.domainNumber | 0 | 0–255 (93 recommended to avoid conflict) |
portDS.logAnnounceInterval | 0 (1 Announce/s) | 0 |
portDS.logSyncInterval | 0 (1 Sync/s) | 0 |
portDS.logMinPdelay_ReqInterval | 0 (1 Pdelay_Req/s) | 0 |
portDS.announceReceiptTimeout | 3 | 3 |
defaultDS.priority1 | 128 (255 for slave-only) | 0–255 |
defaultDS.priority2 | 128 (255 for slave-only) | 0–255 |
defaultDS.slaveOnly | False | True, False |
transparentClockDefaultDS.primaryDomain | 0 | 0–255 |
| Allan deviation sample period | 1.0 s | 1.0 s |
Time Domain 93 Recommendation
Domain 0 is the IEEE 1588 default. To prevent conflict with other PTP distributions that may already occupy domain 0 on the same network, the profile recommends domain 93 for substation PTP.
If you have both a substation-internal PTP and an external PTP (e.g., for IT systems), use different domains.
14. Network Engineering Calculation
For a network engineer to verify a substation design will meet the 1 µs target, the profile provides an explicit formula.
Total Time Inaccuracy Formula
| Symbol | Meaning |
|---|---|
| εT | Total time inaccuracy at the slave |
| εRF | Reference time inaccuracy (e.g., GPS = ~30 ns typical) |
| εGM | Grandmaster time inaccuracy (≤ 250 ns per profile) |
| εTC | TC time inaccuracy (≤ 50 ns per profile) |
| εBC | BC time inaccuracy (≤ 200 ns per profile) |
| εMC | Media converter time inaccuracy (varies) |
| NTC | Number of TCs in series on the longest path |
| NBC | Number of BCs in series on the longest path |
| NMC | Number of media converters in the longest path |
Worked Example
Consider a substation slave reached through:
- 1 grandmaster (GPS-locked)
- 12 transparent clocks
- 1 boundary clock
- No media converters
Calculation:
| Element | Contribution |
|---|---|
| εRF (GPS) | 30 ns |
| εGM | 250 ns |
| 12 × εTC | 600 ns |
| 1 × εBC | 200 ns |
| Total εT | 1080 ns (1.08 µs) |
This exceeds the 1 µs target. Either reduce the BC count, replace BC with TC, or use a more accurate grandmaster.
Network Engineering Recommendations
The profile advises:
- Select network elements knowing their specific contribution to time inaccuracy
- Estimate network time inaccuracy for all slave clocks during design phase
- Use stricter-specification network elements in more demanding applications or larger networks
- Configure Priority1 to prefer time-traceable grandmasters over frequency-traceable ones in the same time domain
- Set all clocks participating in PTP time distribution to the same time domain
Commissioning Verification
The network commissioner should:
- Check the time inaccuracy of installed components against specifications
- Verify the topology (e.g., using the management mechanism)
- Perform a calibration for network time inaccuracy of all slave clocks (e.g., using their 1PPS output)
This is why the profile recommends equipping clocks with a 1PPS output for testing purposes.
15. Management Mechanisms
The profile requires clocks to support at least one of three management mechanisms:
| Option | Standard | What It Provides |
|---|---|---|
| SNMP MIB | IEC 62439-3:2016, Annex E | Standard SNMP access to PTP attributes |
| IEC 61850 Clock Objects | IEC TR 61850-90-4:2013, Sections 19.3 and 19.4 | IEC 61850-native management |
| Manufacturer-specific | Vendor-defined | Fixed values or proprietary management |
Most substation IEDs support either the IEC 61850 Clock Objects (for integration with the rest of the IEC 61850 system) or the manufacturer’s own mechanism.
16. PICS — Protocol Implementation Conformance
Every conforming clock must declare its capabilities in a Protocol Implementation Conformance Statement (PICS). The profile defines a standard PICS table with the following key entries:
| Capability | Description |
|---|---|
| CLOCK_TYPE_OC | Clock is an Ordinary Clock |
| CLOCK_TYPE_TC | Clock is a Transparent Clock |
| CLOCK_TYPE_BC | Clock is a Boundary Clock |
| NR_PORTS | Total number of clock ports |
| PORTS_STEP | 1-step / 2-step / both supported on egress |
| SLAVE_ONLY | All ports are slave-only |
| TIME_TRACEABLE | Connectable to external time reference (e.g., GPS) |
| FREQ_TRACEABLE | Connectable to external frequency reference |
| DAC | Doubly-Attached Clock (PRP/HSR) |
| PORTS_PAIRED | Identifies the paired ports for redundancy |
| REDBOX_DATC | RedBox as Doubly-Attached TC |
| REDBOX_SLTC | RedBox as Stateless TC |
| REDBOX_TWBC | RedBox as Three-way BC |
| REDBOX_DABC | RedBox as DAC BC |
| MIB_SNMP | Supports SNMP MIB management |
| MIB_61850 | Supports IEC TR 61850-90-4 Clock Objects |
| ATOI | Supports ALTERNATE_TIME_OFFSET_INDICATOR TLV |
| PPS | Has a 1PPS output |
| ACCURACY | Design value of clockAccuracy (nanoseconds) |
| DEVIATION | Design value of Allan deviation (nanoseconds) |
| HOLDOVER | Expected length of clockClass 7 holdover (seconds) |
Every IEC/IEEE 61850-9-3 clock data sheet should publish this PICS table — it tells the engineer exactly what the clock can do and how it fits in a network design.
17. Common Misconceptions
“PTP and IEEE 1588 are the same as the Power Profile”
False. PTP (IEEE 1588) is the base standard. The Power Profile (IEC/IEEE 61850-9-3) is a narrow subset with stricter requirements. A clock that is “IEEE 1588 compliant” is not necessarily Power Profile compliant. Always specify IEC/IEEE 61850-9-3 explicitly in your tender, not just “IEEE 1588” or “PTP”.
“Layer 2 PTP and UDP PTP are interchangeable”
False. The Power Profile uses Layer 2 only (IEEE 1588 Annex F). UDP-based PTP (Annex D) is not part of the profile. Clocks supporting only UDP PTP cannot be used in a Power Profile network.
“Peer-to-peer and end-to-end delay measurement are both supported”
False. The profile uses peer-to-peer (P2P) delay measurement exclusively (Annex J.4). End-to-end mechanism is not supported. This means every switch in the path must be a PTP-aware (TC or BC) — non-PTP switches will break the timing chain.
“Grandmaster holdover is unlimited”
False. The profile guarantees holdover for at least 5 seconds. Beyond that, accuracy degrades and the clockClass changes to indicate reduced quality. For longer holdover, you need a higher-grade oscillator (TCXO/OCXO) — verify the vendor’s published holdover specification.
“PTP fixes itself automatically if the grandmaster fails”
Partially true. If multiple grandmaster-capable clocks exist on the network, the BMCA will elect a new grandmaster. But the new grandmaster’s accuracy depends on its own time source. If only one GPS-locked grandmaster exists, its failure means everyone enters holdover — and only for 5 seconds before quality degrades.
“All managed switches support PTP”
False. Many enterprise managed switches do not have hardware PTP support. Even those that do may not meet the 50 ns TC time inaccuracy required by the profile. Always verify the switch is certified for IEC/IEEE 61850-9-3 (or at least IEEE 1588v2 with Power Profile support) before specifying it for a digital substation.
Summary
The IEC/IEEE 61850-9-3 PTP Power Profile is the only PTP profile officially designed for power utility automation. It targets sub-microsecond time synchronization across the substation network — the level required by Sampled Values, GOOSE, and high-accuracy protection applications.
The key things to remember:
- The profile uses Layer 2 Ethernet (no UDP/IP)
- Uses peer-to-peer (P2P) delay measurement only
- Target: network time inaccuracy < 1 µs across the substation
- Budget: ~15 TCs OR 3 BCs in series
- Grandmaster: ≤ 250 ns inaccuracy, ≥ 5 s holdover
- Transparent Clock: ≤ 50 ns device inaccuracy
- Boundary Clock: ≤ 200 ns device inaccuracy
- Link asymmetry: < 25 ns (or known and compensated)
- Default Sync/Announce interval: 1 Hz (logInterval = 0)
- Integrates natively with PRP and HSR redundancy (via IEC 62439-3 Annex A)
- Profile identifier
00-0C-CD-00-01-xydistinguishes singly-attached (x=0), PRP (x=1), HSR (x=2), or both (x=3) - Time domain 93 is recommended to avoid conflict with domain 0
- Always specify IEC/IEEE 61850-9-3 in tenders — not just “IEEE 1588” or “PTP”