Collapse All Expand All

Version: 10.2.1c and 10.2.1c SP3

Resource Center Home

The CircuitSource object class stores information about the source of a circuit. Assign the following model names to the CircuitSource object class. The field names shown are from the Minerville data model. Your field names may be different but model names must be exact. You also need to add a value to the first three fields only. Feeder Manager maintains the FeederSourceInfo field automatically. Each value in the FeederID field must be unique.

Object Model Name: CIRCUITSOURCE

Field Model Names:

Field	Field Model Name
FeederID*	FEEDERID
FeederName	FEEDERNAME
SubstationID	SUBSTATIONID
FeederSourceInfo	FEEDERSOURCEINFO

*When populating the CircuitSource table, remember that each value in the FeederID field must be unique. This field should have a NOT NULL constraint applied as well. Further, we strongly recommend that you set a unique constraint on the field (in both the CircuitSource table and the CircuitSourceID table). Oracle and SqlServer both have the ability to set a unique constraint. If you set the constraint, uses cannot make the mistake of assigning duplicate FeederIDs to different feeders, which is not supported.

ArcFM automatically maintains this field when the appropriate model name is assigned. The Appendix contains a page that interprets the values stored in this field.

Autoupdaters:

Event	Autoupdater
On Feature Update	ArcFM Internal FeederID Update

 

Create Circuit Source Relationships

Feeder Manager requires a separate relationship class for each feature class in the network that may possibly contain features serving in the role of a circuit source (i.e., a source of power for the electric distribution network and a starting point for Feeder Manager’s tracing actions). See Create a relationship class.

Feeder Manager will only trace circuits that are represented by a matched pair consisting of one CircuitSource object and one junction feature. Many utilities use Circuit Breakers exclusively as the source of a circuit but some also use Reclosers as the source point for a circuit. Also, Circuit Breakers may exist in a distribution system and not be the source of a circuit. For these reasons, having an object that is related to the appropriate feature classes provides the flexibility necessary to model all the possible conditions. Feeder Manager will build the list of Feeders by starting with the records in the Circuit Source object and determining the attributes of the feeders. It then traverses all defined relationships to associated features to establish starting points for tracing the network.

The relationship cardinality does not require each circuit source object to have a related feature, but each circuit source object that does have a related feature can have no more than one.

Feeder Manager will traverse the relationships defined for the Circuit Source object class to acquire the starting location on the geometric network for circuit tracing. You can define relationships between Circuit Source and multiple classes (including ones that don't represent the start of a circuit). Feeder Manager will check the following three conditions before traversing the relationship:

If all three conditions are satisfied, then Feeder Manager treats the associated feature class as a starting feature for a circuit trace.

Things to ensure for correct behavior:

 

FeederSourceInfo

This field is used to flag feeders that participate in multifeeds, or that contain features belonging to loops, or both. Two bits of the FeederSourceInfo’s 32-bit integer value are used for this purpose. (Note: Other bits of the integer are used for purposes internal to Feeder Manager, so one cannot count on FeederSourceInfo values being restricted to 0 – 3.) The FeederSourceInfo integer is interpreted as follows:

 

 

 

---

Send Comment to ArcFMdocumentation@schneider-electric.com