Support Extended Feeder Manager

Extended Feeder Manager uses the same framework as Feeder Manager and extends the functionality to help a utility manager to identify distinct voltage levels within an electric network. Extended Feeder Manager allows the utility manager to define a set of intermediate feeder sources within electric circuits at points downstream of the ultimate power sources recognized by Feeder Manager.

If you have configured your geodatabase to use Extended Feeder Manager (EFM) you will need to perform the following steps to ensure Responder supports EFM. The following steps ensure that the FeederID field is properly populated. This value is necessary for EFM to function properly.

Ensure that you have performed all upgrade steps necessary for your current release. These steps are outlined on the What's New page for each release.
Use ArcCatalog to add the SubstationID field to the CircuitSourceID table. This field should have a data type of Text (length=20) and allow NULL values.
If it doesn't already exist, add the SUBSTATIONID field model name to the Electric Field Model Name domain.
Use the ArcFM Properties Manager to assign the SUBSTATIONID field model name to the SubstationID field on the CircuitSourceID table.
Populate the SubstationID field with an ID that indicates the substation that feeds a feeder at a particular voltage level. The substation could be a subsource or an ultimate source.

How does Extended Feeder Manager work?

In the following diagram, you see that without Extended Feeder Manager, only one circuit source is allowed. If an outage is placed on the fuse, Responder will trace to the circuit source to obtain the FeederID and Substation.

In the next diagram, you see that Extended Feeder Manager allows for multiple subsources. If an outage is placed on the fuse under Feeder 1, Responder will trace to Feeder 1 to obtain FeederID and Substation. If an outage is placed on the fuse under Feeder 2, Responder will trace to Feeder 2 to obtain FeederID and Substation.

The FeederID field will be left blank if Responder encounters a tracing problem due to bad data, or when a multifeed is detected.