Printable checklist availableDownload the formatted A4 checklist with status boxes, evidence fields, project details and approval record.
Download PDF checklist A4 PDF · 2 pages
Use this plan to define ownership and evidence across the complete protection chain. Device-level tests are inputs; the final acceptance criterion is correct system behaviour.
Required records
- Approved protection philosophy, trip matrix and single-line diagram.
- CT/VT or LPIT ratios, polarity and terminal references.
- SCD/CID/IID files, settings exports, firmware inventory and network architecture.
- DC schematics, breaker mechanism data and interlocking cause-and-effect.
Hold point A — measurement chain
- Verify primary polarity, phase identity, ratio and grounding.
- Confirm sampled-value dataset, scaling, quality flags and phase mapping.
- Prove loss-of-signal and invalid-quality responses.
Hold point B — communications and time
- Verify GOOSE publisher/subscriber references, VLAN and supervision.
- Test network redundancy transitions and alarm behaviour.
- Record time source, profile, lock state and loss-of-sync response.
Hold point C — IED logic and outputs
- Inject representative internal and external faults.
- Verify pickup, direction, zone selection, blocking and breaker failure.
- Trace every trip from logical node to physical or GOOSE output.
Hold point D — trip circuit and breaker
- Prove trip-coil continuity, trip-circuit supervision and DC polarity.
- Measure relay output, coil energisation, auxiliary-contact change and main-contact response separately.
- Verify local/remote authority and every maintenance isolation position.
Close-out
Store signed results with settings hashes, SCL revision, firmware, test connections and deviations. Any late design or configuration change must trigger a defined regression-test scope.