Digital Protection End-to-End Commissioning

A digital protection scheme can pass individual device tests and still fail as a system. The commissioning boundary must therefore extend from the physical measurement source to the final breaker trip path. The evidence should answer one question: will the correct breaker open, within the required time, for the intended fault and no other condition?

Define the functional chain

Primary current or voltage is converted by a conventional CT/VT or low-power instrument transformer.
A merging unit or sensor interface applies ratio, scaling, phase mapping and quality attributes.
Sampled Values are published with the required dataset, network priority and time reference.
The IED subscribes, evaluates protection algorithms and applies logic and interlocks.
A trip is issued through hardwired output or GOOSE.
Trip I/O, lockout logic and the DC circuit energise the correct trip coil.
The mechanism moves and breaker auxiliary contacts return the final state.

Control configuration before injection

Freeze the approved SCL baseline and relay settings. Record IED name, logical-node references, MAC addresses, APPIDs, VLAN IDs, priorities, sampling rates, CT/VT ratios, time source and redundancy mode. Compare configured subscriptions with the issued architecture. A network capture is useful evidence, but it must be tied to the approved data model.

Test measurement integrity

Inject phase-by-phase and confirm magnitude, angle, phase order, polarity, frequency and quality at the subscribing IED. Include zero and low-level checks, loss of one stream, invalid quality, time-sync degradation and recovery. Where conventional transformers feed a stand-alone merging unit, verify the analog wiring and the digital mapping as two separate error opportunities.

Prove logic and selectivity

Use stable states for pickup and dropout, then dynamic sequences for operate time, directional polarisation, memory voltage, differential restraint and autoreclose logic. Include close-to-threshold cases and realistic pre-fault loading. For blocking or permissive schemes, prove both successful communication and the designed fail-state when a message is delayed, lost or marked invalid.

Measure the complete trip time

Record at least four timestamps: injected-fault inception, protection-element operation, trip output/GOOSE transition and breaker contact separation. This separates algorithm time, communication/logic time, output/DC time and mechanical time. A single end-to-end number is useful operationally but insufficient for diagnosis.

Negative testing

Commissioning must show that the scheme does not trip for load, inrush, external faults, incorrect quality, maintenance mode or loss of a nonessential network path. Validate substitute and test modes, GOOSE supervision, alarm routing, redundancy changeover and restoration after configuration download or reboot.

Handover evidence

The final pack should include the approved SCD/CID/IID files, relay-setting checksum, firmware versions, network topology, time-sync status, injection files, packet evidence where relevant, event records, trip times, deviations and final as-left configuration. Treat any manual change made during testing as a controlled configuration change.

Official sources and revision control

Technical review date: 16 August 2026. Standards and product capabilities can change; confirm the project-specific edition, firmware, options and ordered configuration before engineering or procurement.

End-to-End Digital Protection Commissioning: Sensor to Trip Coil