Using Responder
Responder Multifeeds
Version: 10.2.1c and 10.2.1c SP3 |
| Responder Overview > Manage Incidents > Incident Management - General Information > Responder Multifeeds |
While Responder does support multifeeds, there are scenarios in which multifeeds are not supported. The following diagram will be used to explain the ways in which multifeeds are not fully supported:
If a fault is placed at the fuse or a downstream device, Responder is unable to populate the FeederID and Substation fields because it cannot determine which feeder - F1, F2, or F3 - has the fault. In this situation, the fields are left blank. One way to access this information is via a comma-delimited list, available in Responder Line Display.
If a fault is placed at SP1, SP2, or SP3, the Prediction Engine considers the next upstream device, which in this case is T1. If the fault is determined to be further upstream than T1, the Prediction Engine moves to the next upstream device, which is the fuse. The Prediction Engine can create a fault on the fuse, but not on anything upstream because it would have to guess at which upstream path to choose.
If a problem is reported with T1 and a crew determines that T1 is not at fault, you can move the fault to the next unconfirmed, upstream device. If Responder encounters a split when moving to the next upstream device, Responder is unable to determine which feeder is at fault.
In a multifeed situation, if you create a fault at switch S1, then it will be auto-confirmed because multiple feedpaths exist both upstream and downstream of a device.
If there is a fault on the fuse or any downstream device , it will not be auto-confirmed because at least one side of the device has only one feedpath.
