A relay is tested using preliminary, manufacturer, or default settings to maintain progress. Pickup, timing, and trip outputs may all pass, but the result is not traceably linked to the protected feeder, approved settings revision, CT/VT ratios, active setting group, or required trip logic. Final settings may then be loaded later without confirming that the installed configuration is the one that was actually tested.
A relay can pass every injected test point and still protect the system incorrectly. Wrong pickup values, time delays, curves, CT/VT ratios, setting-group selection, or output logic can cause unwanted trips, failure to trip, or loss of coordination with upstream and downstream protection. Secondary injection verifies relay response. It does not approve the protection philosophy, coordination study, or engineering calculations.
Before final test acceptance, the relay and feeder identity are unambiguous, the approved settings file has a controlled revision, CT/VT ratios match the design, the intended setting group is active, and the required trip logic has been verified. The test report is linked to that exact settings revision, while a final relay readback or download confirms what remains installed after testing. Any later settings change is reviewed for impact and retested where required. Settings approval remains with the Protection Engineer or A/E. CxA verifies approval status, configuration traceability, evidence, and readiness.
Introduce a settings-to-test hold point: no final protection-test acceptance or energisation readiness until the approved revision is loaded, the active group and trip logic are verified, and the final readback and test report refer to the same device and configuration. Manufacturer or default settings may support limited non-energised checks only when the scope is explicitly recorded as preliminary. Those checks must not be presented as final protection testing or evidence of energisation readiness.
05 · FIELD TAKEAWAYA relay can pass the test and still protect the wrong system. The result becomes meaningful only when the tested settings are approved, installed, and traceable.
This note describes a recurring industry pattern using combined and simplified examples. It does not represent a particular client or project.