Electric Tracing - Edges

For any edge feature class that belongs to the electrical network, the bits of the MMElectricTraceWeight field are interpreted as follows in the Minerville sample database:

Bit

Description

31

Reserved

30 - 28

Indicate the presence or absence of a conductor for each phase and depend on the field model name PhaseDesignation. For any traceable features (see bit 12 below), Feeder Manager then uses the value in the field with field model name PHASEDESIGNATION to set these bits. The value of 1 indicates the presence of a conductor on a phase; a 0 indicates the absence of a conductor on the phase.

27 - 13

Reserved

12

Specifies a line (edge) that should not be traced and depends on the class model name FDRMGRNONTRACEABLE and the field model name FDRMGRNONTRACEABLE. If Feeder Manager finds the class model name FDRMGRNONTRACEABLE, then no features in this feature class are traced. If Feeder Manager finds the field model name FDRMGRNONTRACEABLE, then only those features with a code of 0 are traced. The BusBar feature class, for example, may contain some busbar features that should not be traced, such as those found in substations.

The FdrMgrNonTraceable field is intended to signify that power does not flow through a given edge feature—not that Feeder Manager should leave it entirely alone and not update its FeederID, FeederID2 and FeederInfo fields. A common application of the FdrMgrNonTraceable field is to isolate a feeder of one voltage level from a higher voltage feeder immediately upstream of it, so that they will be treated as two separate feeders by Feeder Manager (and not as a single large multifeed feeder). This is accomplished by identifying a conductor feature that provides the sole connection between the two feeders, and designating that conductor as FdrMgrNonTraceable.

Feeder Manager is designed to maintain a NULL-valued FeederID for FdrMgrNonTraceable edge features. That's why user-entered FeederID values for such features are liable to be overwritten with NULL by Feeder Manager. It's the same thing that would happen if the features happened to have PhaseDesignation = NULL (assuming that Feeder Manager has been configured to use conductor phase designation). The features are understood to be de-energized, and that means that their FeederID is NULL.

The Trace A Feeder tool does not, however, actively reset the FeederID to NULL for a FdrMgrNonTraceable feature, in the event that its FeederID field has been manually altered. This happens generally with any de-energized feature, of which FdrMgrNonTraceable is just one special case. That's because the Trace A Feeder tool is not designed to search for and correct FeederID values for any de-energized features beyond the scope of the feeder it has been asked to trace. The Trace All Feeders tool is the one to use in order to assure that all de-energized features are correctly initialized as such by Feeder Manager (by setting their FeederID values to NULL).

Note that there is a analagous bit that works with junction features (Bit 17).

11

Reserved

10 - 4

These bits are set to indicate the operating voltage of the edge feature and depend on the OPERATINGVOLTAGE field model name and the Feeder Manager FDRMGRVOLTAGECODE domain.

3 - 0

Reserved

QR code for this page

Was this helpful?