🎓 Lesson 4
D2
IEC 61850 GOOSE Timing Analysis Lab
GOOSE timing analysis is how we check that critical safety messages between protective relays and controllers in power substations arrive fast and reliably—like a heartbeat for the grid.
🎯 Learning Objectives
- ✓ Calculate end-to-end GOOSE transmission delay including stack processing, network propagation, and switch forwarding latency
- ✓ Analyze jitter and time dispersion across multiple GOOSE datasets to assess conformance with IEC 61850-5 Class T1/T2 timing requirements
- ✓ Design a GOOSE dataset configuration (GoCB settings) that satisfies both worst-case latency budget and redundancy constraints for a 132 kV substation automation system
- ✓ Explain the impact of VLAN prioritization, QoS mapping, and store-and-forward vs. cut-through switching on GOOSE timing performance
- ✓ Apply packet capture and timestamping techniques using IEC 61850-compliant test tools (e.g., Omicron CMC 356, Keysight IxNetwork) to validate measured GOOSE timing against specification
📖 Why This Matters
In mining and bulk material handling operations, integrated SCADA systems increasingly rely on IEC 61850 GOOSE messaging to coordinate blast initiation sequences, conveyor interlocks, and emergency shutdowns across distributed substations. A 12 ms GOOSE delay may be acceptable for feeder protection—but catastrophic if it delays a blast-permit signal during simultaneous multi-face detonation. This lab teaches you not just *that* GOOSE works—but *how fast and consistently* it must work to keep people, equipment, and production safe.
📘 Core Principles
GOOSE timing depends on three interdependent layers: (1) Application layer: GOOSE message structure, dataset size, and GoCB configuration (T0, MaxTime, MinTime); (2) Network layer: Ethernet frame overhead, VLAN tagging, priority tagging (IEEE 802.1Q), and physical medium (copper/fiber); (3) Device layer: IED firmware processing time (pre- and post-GOOSE stack), hardware timestamping accuracy, and switch behavior (buffer depth, queue scheduling, cut-through latency). Determinism is achieved not by speed alone—but by bounded worst-case delay (WCD), where jitter ≤ 10 μs and total end-to-end delay < 3 ms is required for Class T1 (sub-cycle) applications per IEC 61850-5 Annex A. Mining substations often operate at Class T2 (≤ 10 ms), but blast-safety-critical paths demand T1 rigor.
📐 End-to-End GOOSE Delay Budget
The total worst-case end-to-end delay (T_E2E) is the sum of fixed and variable components across all nodes in the path. It must be validated against the GOOSE control block’s MaxTime parameter and application safety requirement.
Total GOOSE End-to-End Delay (T_E2E)
T_E2E = ΣT_processing + ΣT_switch + T_propagation + T_jitter_maxCalculates worst-case deterministic delay from GOOSE publisher to subscriber, inclusive of all device and network contributions.
Variables:
| Symbol | Name | Unit | Description |
|---|---|---|---|
| T_processing | Device processing latency | μs | Time taken by IED firmware to generate (publisher) or consume (subscriber) GOOSE PDU |
| T_switch | Switch forwarding latency | μs | Per-switch cut-through or store-and-forward delay; vendor-specified, typically 0.8–3.5 μs for industrial Ethernet switches |
| T_propagation | Physical layer propagation delay | μs | Signal travel time across cable: ~0.4 μs/m for UTP, ~0.15 μs/m for single-mode fiber |
| T_jitter_max | Peak-to-peak jitter contribution | μs | Maximum expected variation due to queuing, buffer contention, or clock drift across path |
Typical Ranges:
Class T1 (sub-cycle): ≤ 3000 μs
Mining substation (T2): ≤ 10000 μs
💡 Worked Example
Problem: A GOOSE message originates from a SEL-487B relay (processing latency = 120 μs), traverses two managed industrial switches (cut-through latency = 1.2 μs each, queue jitter = ±0.8 μs), travels 85 m over Cat6a copper (propagation = 0.4 μs/m), and terminates at a Siemens SIPROTEC 5 IED (processing = 180 μs). MaxTime = 4 ms. Calculate T_E2E and verify compliance.
1.
Step 1: Compute fixed propagation: 85 m × 0.4 μs/m = 34 μs
2.
Step 2: Sum device processing: 120 μs + 180 μs = 300 μs
3.
Step 3: Sum switch latencies: 2 × 1.2 μs = 2.4 μs
4.
Step 4: Add worst-case jitter: 2 × 0.8 μs = 1.6 μs (conservative peak-to-peak)
5.
Step 5: Total T_E2E = 34 + 300 + 2.4 + 1.6 = 338 μs = 0.338 ms — well below 4 ms MaxTime
Answer:
The result is 0.338 ms, which falls within the safe range of < 4.0 ms and provides >90% timing margin for future traffic growth or firmware updates.
🏗️ Real-World Application
At BHP’s South Flank iron ore operation (Pilbara, WA), a GOOSE-based interlock was deployed between the primary crusher station (ABB REL670) and the rail load-out PLC to prevent conveyor startup during blast vibration windows. Initial commissioning showed 7.2 ms jitter due to untagged background NTP and SNMP traffic on the same VLAN. Remediation included strict 802.1Q priority tagging (PCP=6), dedicated GOOSE VLAN, and switch egress shaping—reducing jitter to <1.1 μs and achieving consistent 2.8 ± 0.3 ms delivery. This enabled integration into the site’s automated blast sequencing SCADA module without compromising SIL-2 integrity per IEC 61508.