Secondary injection test procedure: which relay functions and settings define the test scope?

Verify secondary injection before acceptance.

Evaluate secondary injection test procedure against the approved procedure, matching asset state, verified connections, instrument settings and raw repeat data before accepting or escalating the result.

For this protection and instrument-transformer circuit, identify settings, current or voltage path, logic, timing and trip output in the same record as the reading, because each can alter the interpretation of secondary injection test procedure. Treat relay secondary injection as comparable only when the asset state, test point and time basis for secondary injection test procedure match. For secondary injection test procedure, check scope and edition status on the IEC 60255-1 relay common requirements before freezing the procedure.

A deviation involving secondary injection test procedure should be escalated only after the secondary injection test procedure setup is verified and the observation remains repeatable. Retain the instrument identification, raw measurement, repeated result and disposition for secondary injection test procedure so the decision remains reviewable. For secondary injection test procedure equipment scope, check Wrindu’s relay protection testing range page before selecting a model.

Verify isolation and secondary-circuit boundaries

The purpose of this step is to connect verify isolation secondary-circuit boundaries with the specific decision that secondary injection test procedure must support. Within verify isolation secondary-circuit boundaries, the scope is proving relay logic and document scope, so the record must distinguish the observed quantity, the comparison source and the condition of the test object.

The minimum technical record for verify isolation secondary-circuit boundaries should preserve settings, current or voltage path, logic, timing and trip output together with the unedited result. Treat protection logic test as comparable only when the asset state, test point and time basis for verify isolation secondary-circuit boundaries match. For verify isolation secondary-circuit boundaries, check scope and edition status on the IEC 60255-24 COMTRADE format before freezing the procedure.

Preserve both the first and repeated records for verify isolation secondary-circuit boundaries; overwriting either result would weaken the audit trail for secondary injection test procedure. Retain the instrument identification, raw measurement, repeated result and disposition for verify isolation secondary-circuit boundaries so the decision remains reviewable.

How should test cases represent the enabled logic?

Verify test cases represent enabled against the test basis.

Evaluate test cases represent enabled against the approved procedure, matching asset state, verified connections, instrument settings and raw repeat data before accepting or escalating the result.

For this protection and instrument-transformer circuit, identify settings, current or voltage path, logic, timing and trip output in the same record as the reading, because each can alter the interpretation of test cases represent enabled. Treat trip output verification as comparable only when the asset state, test point and time basis for test cases represent enabled match. For test cases represent enabled, check scope and edition status on the IEC 60255-187-1 differential protection before freezing the procedure.

Preserve both the first and repeated records for test cases represent enabled; overwriting either result would weaken the audit trail for secondary injection test procedure. Retain the instrument identification, raw measurement, repeated result and disposition for test cases represent enabled so the decision remains reviewable. For test cases represent enabled equipment scope, check Wrindu’s microcomputer protection relay tester page before selecting a model.

Capture pickup, timing and output evidence

Keep capture pickup timing output visible in the secondary injection test procedure record instead of hiding it inside a corrected or filtered result. Within capture pickup timing output, the scope is proving relay logic and document scope, so the record must distinguish the observed quantity, the comparison source and the condition of the test object.

Reconstructing capture pickup timing output requires a time-stamped record of settings, current or voltage path, logic, timing and trip output for the tested protection and instrument-transformer circuit. Treat relay secondary injection as comparable only when the asset state, test point and time basis for capture pickup timing output match. For capture pickup timing output, check scope and edition status on the IEC TS 60255-216-1 digital protection interfaces before freezing the procedure.

If the evidence for capture pickup timing output remains incomplete, limit the stated conclusion for secondary injection test procedure and schedule a controlled repeat or a complementary method. Retain the instrument identification, raw measurement, repeated result and disposition for capture pickup timing output so the decision remains reviewable.

Check binary inputs, outputs and trip interfaces

The decision on check binary inputs outputs should be made at a defined hold point in the secondary injection test procedure workflow. Within check binary inputs outputs, the scope is proving relay logic and document scope, so the record must distinguish the observed quantity, the comparison source and the condition of the test object.

Reconstructing check binary inputs outputs requires a time-stamped record of settings, current or voltage path, logic, timing and trip output for the tested protection and instrument-transformer circuit. Treat protection logic test as comparable only when the asset state, test point and time basis for check binary inputs outputs match. For check binary inputs outputs, check scope and edition status on the IEC PAS 61850-90-28 GOOSE and SV validation before freezing the procedure.

The final record should explain why evidence about check binary inputs outputs was accepted, repeated or escalated within the secondary injection test procedure scope. Retain the instrument identification, raw measurement, repeated result and disposition for check binary inputs outputs so the decision remains reviewable.

Distinguish relay proof from primary-circuit proof

Resolve distinguish relay proof primary-circuit before using the secondary injection test procedure result for acceptance, maintenance planning or equipment selection. Within distinguish relay proof primary-circuit, the scope is proving relay logic and document scope, so the record must distinguish the observed quantity, the comparison source and the condition of the test object.

For this protection and instrument-transformer circuit, identify settings, current or voltage path, logic, timing and trip output in the same record as the reading, because each can alter the interpretation of distinguish relay proof primary-circuit. Treat trip output verification as comparable only when the asset state, test point and time basis for distinguish relay proof primary-circuit match. For distinguish relay proof primary-circuit, check scope and edition status on the IEC 60255-26 electromagnetic compatibility before freezing the procedure.

If the evidence for distinguish relay proof primary-circuit remains incomplete, limit the stated conclusion for secondary injection test procedure and schedule a controlled repeat or a complementary method. Retain the instrument identification, raw measurement, repeated result and disposition for distinguish relay proof primary-circuit so the decision remains reviewable. For distinguish relay proof primary-circuit equipment scope, check Wrindu’s relay commissioning test plan page before selecting a model.

When do missing settings invalidate the test?

Set a hold point for missing settings invalidate test.

Evaluate missing settings invalidate test against the approved procedure, matching asset state, verified connections, instrument settings and raw repeat data before accepting or escalating the result.

Use the same basis for settings, current or voltage path, logic, timing and trip output whenever missing settings invalidate test is trended across crews, instruments or outage dates. Treat relay secondary injection as comparable only when the asset state, test point and time basis for missing settings invalidate test match.

If the evidence for missing settings invalidate test remains incomplete, limit the stated conclusion for secondary injection test procedure and schedule a controlled repeat or a complementary method. Retain the instrument identification, raw measurement, repeated result and disposition for missing settings invalidate test so the decision remains reviewable.

Prepare a reproducible secondary-injection record

The purpose of this step is to connect prepare reproducible secondary-injection record with the specific decision that secondary injection test procedure must support. Within prepare reproducible secondary-injection record, the scope is proving relay logic and document scope, so the record must distinguish the observed quantity, the comparison source and the condition of the test object.

The minimum technical record for prepare reproducible secondary-injection record should preserve settings, current or voltage path, logic, timing and trip output together with the unedited result. Treat protection logic test as comparable only when the asset state, test point and time basis for prepare reproducible secondary-injection record match.

When setup correction removes the change in prepare reproducible secondary-injection record, report a test-condition issue rather than an unsupported secondary injection test procedure asset finding. Retain the instrument identification, raw measurement, repeated result and disposition for prepare reproducible secondary-injection record so the decision remains reviewable.