Summary Highlights
- Start with the approved 87B/50BF functions, active revision, bus topology, CT allocation and exact test endpoints.
- Select internal/external bus-fault, zone/status, BF initiation/reset/timing and retrip/backup cases for the installed architecture.
- Distinguish synthetic relay-input testing, an included physical CT path and an authorized output or breaker trip-path test.
- Record operated and blocked outputs, current/position assumptions, communication dependencies and any untested paths.
- Close the work with recorded restoration, unresolved defects and engineering actions; a trip LED or self-test is not whole-scheme proof.
Article Details
Breaker-failure and busbar protection maintenance should establish how the selected scheme behaved under identified test conditions. It should not end with a statement that the relay powered up or that every future fault will clear. The useful result identifies the tested zones, inputs, logic, timing references and actual output endpoints, together with the paths that remained blocked or outside scope.
Define the installed functions and the evidence boundary
Begin with the approved one-line and protection drawings, CT allocation, relay model and firmware, active settings and logic revision, trip matrix and relevant operating states. Separate 87B bus differential logic from 50BF initiation and failed-clearing supervision. Check-zone, dynamic zone selection, retrip, dead-zone, communications and additional bay functions are included only when present and selected for the work.
| Test boundary | Evidence it can provide | What it does not automatically prove |
|---|---|---|
| Known signals injected at identified relay inputs | Selected measurement, characteristic, zone logic, pickup/reset and timing response | Primary CT behaviour or wiring outside the injection points |
| A defined primary or physical CT measurement path | Response of the included sensor, wiring and relay input path | Fault-level saturation performance or every unused core, tap and topology |
| An authorized output or installed trip-path test | The observed contact, interposing relay, coil or breaker response up to the recorded endpoint | Successful interruption of actual fault current or untested parallel/remote paths |
| Internal self-supervision and event review | Condition of the portions actually monitored and the recorded sequence | Health of every external circuit, correct trip destinations or future fault clearing |
A contact-output test and a breaker operation test are not interchangeable. ENTSO-E reports both approaches among operators. The scope must say which was authorized and observed, rather than calling either one an unrestricted end-to-end test.
Establish the safe condition and preserve the settings found
Only qualified personnel should prepare and perform the work under an approved isolation and test plan. An energized CT secondary must not be opened; rated 1 A or 5 A is not a touch-safe designation. The plan must control unintended trips, affected live circuits, test equipment, access and any temporary loss of protection. This article gives no secondary switching or terminal connection procedure.
Record the settings and logic found before changes, including their identifier and approval status. Compare them with the actual CT assignments, coupler arrangement, status inputs, BFI sources and trip destinations. A mismatch is an engineering finding, not an instruction to load a generic setting file. Preserve the as-found evidence and identify who approves any proposed change before application.
Review visible condition and available alarms: supply, internal supervision, current circuits, position discrepancy, time synchronisation, communications and input/output modules where applicable. An alarm-free display does not establish the health of unmonitored external paths. Disturbance records and previous unexplained starts can help select cases, but are not substitutes for the agreed tests.
Use a scenario matrix for the bus differential function
| Selected case | Conditions and interpretation | Result and limit to record |
|---|---|---|
| Internal-zone operating case | Apply the approved signal set and zone membership for the selected function | Operating quantity, zone decision and authorized outputs; only the applied case is demonstrated |
| External/through-current stability case | Use the model-appropriate restraint and security conditions, including agreed CT-error or waveform simulations | Stability for the applied magnitude, waveform and topology; no claim to reproduce every primary CT saturation event |
| Check-zone supervision, where installed | Examine selective/check-zone combinations and applicable transfer/coupler exceptions | Actual permissive/blocking behaviour; no blanket check-zone immunity to CT or configuration faults |
| Changing or inconsistent status, where relevant | Use the approved transition, invalid-state and last-valid/blocking policy | Zone assignment, alarm and affected outputs; synthetic status inputs alone do not prove primary contacts moved |
| End-zone or coupler overlap case, where included | Identify CT/CB locations, available sources and intended local/remote destinations | Observed selective or deliberately nonselective sequence and untested remote paths |
The test set and method must suit the architecture. A low-impedance numerical characteristic test is not a substitute for the CT and circuit checks required by a high-impedance design. Conversely, a generic high-impedance circuit recipe must not be applied to separately measured numerical inputs. Criteria and acceptance tolerances come from the approved engineering documents and applicable device instructions.
A differential result needs the input reference, polarity, ratio/scaling, phase relationship and zone assignment. If a result is unexpected, distinguish a wrong signal or reference from a logic, wiring or device issue before changing settings. Reversed polarity, a missing input and an incorrect status can produce similar symptoms without the same cause.
Test BFI, supervision, reset and timing as separate conditions
Identify the authorized sources of breaker failure initiate and the selected phase/common-start logic. Then distinguish initiation, timer start, current or position supervision, reset and final output. The SEL utility paper shows that timer-start and output-supervision arrangements vary. A BF test should therefore follow the installed logic rather than assume that every timer starts from the same two-input gate.
Select cases that cover normal clearing/reset, sustained failed clearing and any applicable low-current or position-supervised branch. Include unauthorized or spurious-start rejection where required by the design. The applied current, waveform and simulated position must be recorded. A model-specific subsidence-current algorithm or dropout response is not assumed from a steady-current test.
| Timing event | Reference to record | Limit |
|---|---|---|
| BFI or timer start | The actual signal or logic transition used as the start reference | BFI arrival and timer start may differ |
| Retrip output, if provided | The selected contact or message and its observed change | A command does not prove that the same breaker interrupted current |
| Backup/intertrip output | The selected destinations, output state and operating endpoint | Blocked or simulated destinations remain outside physical-chain evidence |
| Current reset or breaker indication | The measured detector response or identified auxiliary state | An auxiliary status is not a measurement of arc extinction; reset may depend on waveform |
| Final clearing evidence, if separately available | The identified current interruption and participating breaker records | Relay operating time alone is not total fault-clearing time |
The engineering delay must allow normal interruption and detector behaviour while meeting the coordinated backup and stability requirements. There is no universal millisecond or cycle value for this article. Comparing a test with a setting is useful only when both use the same start, stop and supervision references.
Keep retrip and backup destinations distinct
Where retrip is configured, identify the same-breaker circuit, coil or output that it uses. For backup tripping, identify the sources that must be removed, the local breaker selection and any remote intertrip or reclosing restrictions. The stages may use different supervision and timers. Retrip is not mandatory in every design, and backup destinations are not determined by a list of physically adjacent breakers.
For each authorized output test, record what actually operated and what was inhibited. A relay LED, software bit or simulated contact is evidence at that endpoint only. If the work includes a coil or breaker operation, document the included path and response; do not claim that a no-load operation demonstrates fault interruption. Remote reception and final interruption require their own authorized evidence.
Include physical CT, binary and communication paths only as scoped
CT polarity, ratios, cores, secondary continuity, earthing arrangement and zone allocation must be assessed through the applicable safe method. A relay-input injection can verify logic while bypassing much of the installed CT circuit. A primary-current test covers the actual path used, but its current and waveform may not reproduce the primary fault conditions used in the design study. Neither test automatically covers every feeder, core or operating state.
Status inputs require particular care because an auxiliary indication can disagree with the primary apparatus. The ENTSO-E report includes a case where a disconnector mechanism indicated a completed movement while one pole did not move. Tests of simulated binary states should therefore be labelled as such; inspection or functional checks of the physical indication path are separate parts of the agreed scope.
For a scheme using GOOSE, sampled values or remote trip channels, identify the participating publishers, subscribers, input/output mappings and the actual test or blocked state relevant to the work. Check the selected data and signal paths under the approved method. A successful message, link alarm or laboratory simulation alone does not prove the full physical clearing chain or protocol conformance.
Time synchronisation and recorder references affect event comparison. Preserve known clock offsets, missing records and resolution limits instead of treating every event timestamp as directly comparable. A digital-secondary communication failure can remove measurement, initiation or output paths depending on the architecture; an available Ethernet link does not prove every required application path is healthy.
Restore, document and close the engineering findings
Before return to service, the authorized team must verify the required restoration of outputs, test/blocked modes, temporary logic, settings, communications and protection availability. Record the restoration checks and any limitations or defects still open. Completing an injection sequence is not permission to energise equipment or a declaration that every protection path is ready.
A useful report names the zone and bay, relay model/firmware, as-found and final approved revision, actual bus state, CT/input references, test equipment and relevant traceability, applied cases, acceptance basis, measured timing endpoints, observed outputs, blocked or untested destinations, event files and clock limitations. Add the defect, required action, responsible party and retest status. These are example engineering fields, not a claim of a statutory report form or work already performed.
For example, a hypothetical record may state: selective zone A and check-zone combination tested with a specified synthetic input set; backup contact observed; remote trip and physical breaker operation excluded by the authorised scope; settings unchanged; identified output blocks restored and documented. This supports a precise result without turning partial testing into whole-chain proof.
Maintenance frequency and the required scenarios depend on the equipment, approved programme, condition, consequences of failure and changes to the installation. ENTSO-E found several different operator strategies. Its dated survey is not a universal legal interval or a replacement deadline. Changes to feeders, CT allocation, coupler logic, firmware or communication mapping should trigger an assessment of whether the previous test evidence still applies.
Technical references: ENTSO-E busbar differential protection recommendations (4 December 2019, sections 4–7 and questionnaire 8) distinguish topology, test scope and operator maintenance approaches. The SEL and utility breaker-failure case study (2025, printed pages 2–4 and 12–15) explains differing initiation, reset, backup and digital-path dependencies. Use these as engineering context alongside the approved station scheme and applicable device instructions.
Related Blog Posts
- What Are Breaker Failure Protection and Busbar Protection Relays? What Do They Do, How Do They Work and Why Are They Used?
- What Tests and Maintenance Are Required for Overcurrent and Earth Fault Protection Relays?
- Distance Protection Relay Testing and Maintenance
- Transformer Differential Protection Relay Testing and Maintenance
Related Services
Frequently Asked Questions
Why is maintenance required on breaker failure and busbar protection relays?
Maintenance provides recorded evidence that selected busbar and breaker-failure functions behaved as required in the tested states. It can identify mismatches introduced by settings, wiring, status, equipment or topology changes. The report must identify tested and excluded paths; a healthy display, self-test or a single trip output is not whole-scheme proof. Frequency and scope follow the applicable equipment and approved programme, not one universal interval.
Which tests are performed on these relays?
The agreed scope can include settings and logic review, internal/external differential cases, applicable check-zone and status combinations, BF initiation/reset/timing, retrip and backup destinations, CT/binary paths, communications and output tests. It must suit the installed architecture. Synthetic input tests, physical CT-path checks and actual breaker trip tests provide different evidence and must be labelled separately.
What does the busbar differential test verify?
It demonstrates the selected differential characteristic, zone decision and security behaviour for the applied signals, topology and settings. Include internal operating cases and the agreed external/through-current stability cases. Record magnitude, waveform, polarity/scaling, zone assignment and outputs. It does not guarantee every future fault will clear or prove primary CT saturation behaviour and trip paths that were bypassed or excluded.
Why is the check zone test important?
Where a check zone is installed, testing establishes how it supervises the selective zones for the approved combinations and any topology exceptions. The expected permissive, block or alarm must match the actual design. Some architectures do not use the same check-zone arrangement. Agreement in a test is not a guarantee against CT, wiring, common-input or configuration errors.
Why is dynamic zone selection tested separately?
In a scheme that uses dynamic selection, current membership and trip destinations can change with the bus arrangement. Test the applicable stable, transition and inconsistent-status cases against the approved policy. Simulated binary states verify only the included input/logic path; they do not prove that all primary disconnector or breaker contacts physically moved. Fixed-zone architectures need their own relevant checks.
What does the breaker failure test verify?
It verifies the configured BFI source, timer-start conditions, current and/or position supervision, reset, timing and designated outputs in the selected scenarios. Include the agreed normal-clearing and sustained-failure cases and any relevant low-current branch. Record start and stop references. A breaker can open its contacts without interrupting current, so position indication and measured current must not be treated as the same evidence.
Why should retrip and backup trip be tested separately?
Retrip addresses the same breaker through its selected output or trip circuit; backup tripping removes the remaining sources through other designated destinations. Their supervision, timing and physical paths may differ, and retrip is not present in every scheme. Separate results show what each stage actually operated. A command or blocked-output simulation does not prove coil operation, remote reception or successful fault interruption.
Why is CT checking very critical in busbar protection?
The relay combines currents from several circuits, so polarity, ratio/scaling, missing inputs or wrong zone allocation can create false differential quantities. The safe test method must identify which cores, wiring and measurement points are included. An energized CT secondary must not be opened, and 1 A or 5 A ratings do not make it touch-safe. Relay-input testing alone does not establish the complete physical CT path or fault saturation performance.
Why is the trip circuit test indispensable?
The selected output must reach its intended endpoint, rather than merely appear as a trip LED or internal bit. The approved scope may end at a relay contact or terminal block, or include an installed coil and breaker operation. State that endpoint, actual operated paths and any inhibited or remote destinations. A no-load breaker operation still does not demonstrate interruption of real fault current.
Why is record keeping important in these systems?
Records connect the result to the actual revision, bus state, CT assignment, applied scenarios and observed endpoints. Keep event files, clock limitations, blocked or untested paths, defects, actions, retest status and restoration evidence. Later topology, setting or equipment changes can invalidate earlier assumptions. A clear record supports engineering follow-up without claiming complete future reliability from one visit.