{
  "language": "en",
  "interfaceLanguage": "en",
  "url": "https://voltformer.com/articles/breaker-failure-50bf-timing-mv-intertrip-coordination",
  "id": "oct2026-breaker-failure-50bf-timing-mv-intertrip-coordination",
  "slug": "breaker-failure-50bf-timing-mv-intertrip-coordination",
  "date": "2026-10-07",
  "title": "MV Breaker Failure 50BF: Build the Timer and Intertrip Budget",
  "summary": "Coordinate breaker-failure initiation, current-detector reset and backup clearing for an MV bus with multiple sources without copying a universal timer.",
  "tags": [
    "Breaker failure",
    "50BF timing",
    "MV intertrip",
    "Current-detector reset"
  ],
  "author": "Voltformer Engineering",
  "category": "Protection & Control",
  "readTime": "6 min read",
  "contentMarkdown": "### 1. Define the failed interruption\n\nBreaker-failure protection asks whether the selected breaker has removed its current contribution after a legitimate trip command. It is not just an extra overcurrent delay. On an MV bus supplied by two incomers and a closed coupler, opening only the upstream breaker of the failed feeder may leave another source feeding the fault. Define the isolation set from the single-line diagram for every permitted topology. The [SEL breaker-failure paper](https://cdn.selinc.com/assets/Literature/Publications/Technical%20Papers/6262_AdvancesBreaker-failure_HA_20060905_Web.pdf?v=20160510-233021) discusses initiation, reset and backup tripping. Use the [feeder-setting guide](/articles/mv-feeder-protection-settings-50-51-67-79-iec-60255) for ordinary grading; this guide concerns failed interruption and its escalation.\n\n### 2. Obtain the timing boundaries\n\nRecord the initiating protection functions, trip-output delay, interposing relays, breaker maximum interrupting time under the specified duty, current-detector reset, auxiliary-contact timing and timer tolerance. Obtain minimum fault current through the failed breaker for each source configuration and CT performance at maximum current. Specify where the timer starts: an internal protection bit and an external trip contact do not have the same delay. Use the actual relay manual, not a setting name from another model. The [SEL-311C sheet](https://selinc.com/api/download/10134/) illustrates that detector timing is a device-specific specification. Do not apply that timing automatically to a different IED.\n\n### 3. Illustrative local timing budget\n\nAssume the timer starts when the protection trip command asserts. Allow 5 ms for the output/interface, 60 ms for breaker interruption, 15 ms for detector reset and 20 ms engineering margin. The resulting illustrative timer is 100 ms.\n\n$$\n5 + 60 + 15 + 20 = 100\n$$\n\nIf failure persists, suppose backup logic and communication take 10 ms and the backup breaker interrupts in 70 ms. Clearing after initiation is then 180 ms.\n\n$$\n100 + 10 + 70 = 180\n$$\n\nFault detection before initiation is excluded and must be added for total fault duration. These assumed values are not recommended settings. Check thermal duty, arc-energy assessment, process consequences and any stability constraint against the complete timeline, including worst-case tolerances.\n\n### 4. Match the logic to the initiating trip\n\n| Initiating condition | Evidence of failed opening | Review requirement |\n|---|---|---|\n| Fault trip with current | Current persists after the allowance | Pickup and reset suit minimum fault |\n| Non-electrical trip with little current | Contact/status logic as designed | Current-only detection may be insufficient |\n| Retrip stage | Original breaker receives another command | Independent coil/path availability |\n| Backup intertrip | All fault-feeding sources isolated | Topology-dependent trip matrix |\n\nThe [SEL-352 data sheet](https://selinc.com/api/download/3056/) identifies different schemes for fault and other conditions. Auxiliary contacts provide useful position evidence but are not interchangeable with measured interruption. A pole can fail to interrupt even when a mechanism contact changes state. Conversely, retained contact status can falsely suggest failure after current has ceased.\n\n### 5. Coordinate every source and restore selectively\n\nDefine which incomer, coupler, generator or remote breaker receives backup tripping with each bus configuration. Include reverse power flow and embedded generation; the normal power-flow arrow is not the fault-source map. Prevent automatic reclose or transfer from immediately re-energizing the failed isolation zone. Document lockout, reset authority and the conditions for restoration. A retrip can improve clearing for some control-path faults, but sending it down the same failed coil cannot cure that coil's failure. The final timer must allow successful primary interruption while meeting the project backup-clearing requirement.\n\n### 6. Commission the failure rather than only the timer\n\nWith an approved isolated test setup, demonstrate successful opening resets the scheme before escalation. Simulate persistent current and verify retrip, backup destinations and lockout. Separately test missing initiation, stuck auxiliary status, low-current initiating trips and communication loss. The [SEL paper](https://cdn.selinc.com/assets/Literature/Publications/Technical%20Papers/6262_AdvancesBreaker-failure_HA_20060905_Web.pdf?v=20160510-233021) explains why CT subsidence current can delay a detector's reset after primary interruption; include the manufacturer's relevant test method. Capture initiation, current detector, timer, outputs and backup response together. For Ethernet intertrip, apply the [GOOSE failure-supervision workflow](/articles/iec-61850-goose-prp-hsr-failover-trip-supervision). Retain as-built logic and topology cases alongside the setting file.\n\n### 7. Setting-review questions\n\n#### Can a fixed timer serve every MV breaker?\n\nOnly if project evidence supports all included breakers and operating cases. A familiar value is not that evidence.\n\n#### Is an open auxiliary contact enough to declare success?\n\nNot for every failure mode. Use the designed combination of current and position evidence.\n\n#### Should 50BF start on every trip command?\n\nDefine the initiating set deliberately. Maintenance commands, nonfault trips and protection trips may require different supervision and authorization logic.\n\n### 8. Primary references\n\n- [SEL-352](https://selinc.com/api/download/3056/)\n- [SEL-311C](https://selinc.com/api/download/10134/)\n- [SEL — Breaker-Failure](https://cdn.selinc.com/assets/Literature/Publications/Technical%20Papers/6262_AdvancesBreaker-failure_HA_20060905_Web.pdf?v=20160510-233021)",
  "contentLanguage": "en",
  "sources": [
    {
      "name": "SEL-352",
      "url": "https://selinc.com/api/download/3056/"
    },
    {
      "name": "SEL-311C",
      "url": "https://selinc.com/api/download/10134/"
    },
    {
      "name": "SEL — Breaker-Failure",
      "url": "https://cdn.selinc.com/assets/Literature/Publications/Technical%20Papers/6262_AdvancesBreaker-failure_HA_20060905_Web.pdf?v=20160510-233021"
    }
  ]
}