Collapse All Expand All

Version: 10.2.1c and 10.2.1c SP3

Resource Center Home

Decide which feature classes to include in your network. Below are the feature classes we recommend you include in your geodatabase. These feature classes are from the Minerville sample geodatabase. You may use different feature class names and include additional feature classes. Throughout this documentation, we will refer to the feature classes as named below.

 

FdrMgrNonTraceable

The FDRMGRNONTRACEABLE model name may be assigned to a feature class or to an attribute field. If it is assigned at the feature class level, the entire class will be omitted from Feeder Manager traces.

You may also create a Feeder Manager NonTraceable Indicator field to which the model name is assigned. Below is required data type and domain for this field. You may change the name of the field, but the FDRMGRNONTRACEABLE field model name assigned later must have the EXACT spelling.

Field	Data Type	Domain
Feeder Manager NonTraceable Indicator	long integer	FdrMgrNonTraceable

The user will be able to select Traceable or NonTraceable for individual features.

For a detailed explanation of FDRMGRNONTRACEABLE, view the appendix help topic: Appendix > Bitgate Fields > Electric Tracing - Edges.

  

Conductors

Conductors consist of primary and secondary wire as well as other current-carrying lines such as bus and transmission lines. These feature classes must participate in your geometric network as simple edges or complex edges. If you have edges in your network that you don't want Feeder Manager to trace (but want to trace them for other purposes--such as bus in a substation that is upstream of the circuit breaker), include these feature classes in your network and use the model name FDRMGRNONTRACEABLE as an object class model name or field model name to disable edge feature classes from the trace. If you want Feeder Manager to trace with respect to conductor phasing, you must create a PhaseDesignation field for the edge features in your network. The PhaseDesignation field should be assigned a domain.

Below is a list of required fields for this feature class. You may change the names of the fields, but the field model names assigned later must have the EXACT spelling. Ensure the domains are assigned as shown.

Field	Data Type	Domain
FeederID	long integer or string/text (same as Circuit Source)
FeederID2	long integer or string/text
FeederInfo	long integer (precision = 10)
ElectricTraceWeight	long integer (precision = 10)
PhaseDesignation	long integer	On the Properties Subtypes tab, assign the appropriate domain for each subtype: Phase Designation, Single Phase, Two Phase, or Three Phase.
OperatingVoltage	any data type, domain required	OperatingVoltage
FdrMgrNonTraceable (optional)	long integer or string/text	FdrMgrNonTraceable
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID or ParentCircuitSourceGUID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceID	long integer	Data type = 32-bit integer Default value = null
Add either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceGUID	GUID	Default value = null
FacilityID	text (length=20)	Default value = null

 

Switchable Devices

Switches can interrupt the flow of electricity in a circuit. You can include non-mechanical open points in this category as well because a switch that is normally open appears the same to the tracing algorithms as an open point. Modeling an open point as a switch allows you to close it out in the field and reflect that change by changing the normal open status fields. You can have one or more feature classes that store switchable devices but each must be assigned the model name of SWITCH. In your model, the switch classes must be a simple junction, and must have fields assigned the following model names. If you want to use the out-of-the-box autoupdaters to maintain the trace weights, the fields carrying the NORMALPOSITION_A, NORMALPOSITION _B, or NORMALPOSITION _C model name should have a domain assigned.

Below is a list of required fields for this feature class. You may change the names of the fields, but the field model names assigned later must have the EXACT spelling. Ensure the domains are assigned as shown.

Field	Data Type	Domain
FeederID	long integer or string/text (same as Circuit Source)
FeederID2	long integer or string/text
FeederInfo	long integer (precision = 10)
ElectricTraceWeight	long integer (precision = 10)
PhaseDesignation	long integer	On the Properties Subtypes tab, assign the appropriate domain for each subtype: Phase Designation, Single Phase, Two Phase, or Three Phase.
NormalPosition_A	long integer	NormalStatus
NormalPosition_B	long integer	NormalStatus
NormalPosition_C	long integer	NormalStatus
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID or Parent CircuitSourceGUID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and Subsource fields should be added to all junction classes eligible to represent subsidiary or ultimate sources.
ParentCircuitSourceID	long integer	Data type = 32-bit integer Default value = null
Add either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceGUID	GUID	Default value = null
CircuitSourceID	long integer	Data type = 32-bit integer Default value = null
Subsource	short integer	Yes/No domain Data type = 16-bit integer Default value = null
FacilityID	text (length=20)	Default value = null

 

Protective Devices

Protective Devices provide overcurrent protection and can interrupt the flow of electricity in a circuit. You can have one or more feature classes that represent protective devices but each must be assigned the model name of FDRMGRPROTECTIVE to designate it as a member of this category. Please note that Feeder Manager makes no distinction between the categories of Switchable and Protective Devices. The autoupdaters provided with Feeder Manager use the FDRMGRPROTECTIVE model name to maintain the value in the trace weight field. The design of Feeder Manager anticipates that future applications (especially outage management) will need to determine from the trace weight alone whether a device is protective or not, i.e., whether it is designed to open automatically in response to a fault. Assign a domain to the fields with model names NORMALPOSITION_A, NORMALPOSITION _B, and NORMALPOSITION_C.

Below is a list of required fields for this feature class. You may change the names of the fields, but the field model names assigned later must have the EXACT spelling. Ensure the domains are assigned as shown.

Field	Data Type	Domain
FeederID	long integer or string/text (same as Circuit Source)
FeederID2	long integer or string/text
FeederInfo	long integer (precision = 10)
ElectricTraceWeight	long integer (precision = 10)
PhaseDesignation	long integer	On the Properties Subtypes tab, assign the appropriate domain for each subtype: Phase Designation, Single Phase, Two Phase, or Three Phase.
NormalPosition_A	long integer	NormalStatus
NormalPosition_B	long integer	NormalStatus
NormalPosition_C	long integer	NormalStatus
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID or ParentCircuitSourceGUID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and Subsource fields should be added to all junction classes eligible to represent subsidiary or ultimate sources.
ParentCircuitSourceID	long integer	Data type = 32-bit integer Default value = null
Add either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceGUID	GUID	Default value = null
CircuitSourceID	long integer	Data type = 32-bit integer Default value = null
Subsource	short integer	Yes/No domain Data type = 16-bit integer Default value = null
FacilityID	text (length=20)	Default value = null

 

Transformers

Transformers are devices that transform the voltage level in a circuit. Transformers must be a junction feature class in your geometric network. You can include Step Transformers in this category as well. This feature class must be assigned the class model name of TRANSFORMER. The Phase Designation field should store the phase or phases that the transformer is tapping and have a domain assigned to it. This enables Feeder Manager to determine which phase of a three-phase conductor a single-phase transformer is tapping.

Below is a list of required fields for this feature class. You may change the names of the fields, but the field model names assigned later must have the EXACT spelling. Ensure the domains are assigned as shown.

Field	Data Type	Domain
FeederID	long integer or string/text (same as Circuit Source)
FeederID2	long integer or string/text
FeederInfo	long integer (precision = 10)
ElectricTraceWeight	long integer (precision = 10)
PhaseDesignation	long integer	On the Properties Subtypes tab, assign the appropriate domain for each subtype: Phase Designation, Single Phase, Two Phase, or Three Phase.
Optional: Create the following field if you want to display the Total RatedkVA for an electric trace. This functionality also requires the TransformerUnit object class.
RatedkVA	Long integer	Transformer Unit kVA
Optional: Create the following field if you want secondary conductors downstream of a transformer to inherit the transformer's LowSideVoltage value. If this value doesn't exist (and the functionality is configured), the downstream secondary conductors inherit the OperatingVoltage value from the transformer.
LowSideVoltage	long integer
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID or ParentCircuitSourceGUID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and Subsource fields should be added to all junction classes eligible to represent subsidiary or ultimate sources.
ParentCircuitSourceID	long integer	Data type = 32-bit integer Default value = null
Add either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceGUID	GUID	Default value = null
CircuitSourceID	long integer	Data type = 32-bit integer Default value = null
Subsource	short integer	Yes/No domain Data type = 16-bit integer Default value = null
FacilityID	text (length=20)	Default value = null

Optional:

The following object class is required ONLY if you are using a multi-tiered network and Extended Feeder Manager.

CircuitSourceID Object Class

This table stores data about the multi-tiered network.

Field	Data Type	Domain
FeederLevel	Long integer
FeederName	text (length=48)
ObjectID	Object ID
ParentCircuitSourceID	Long integer	No domain Data type = 32-bit integer Default value = null
Add either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceGUID	GUID	Default value = null
RelatedFeatureClassName	text (length=48)
RelatedObjectID	long integer

  

Optional:

The following object class is required if you wish to view the Total RatedkVA for an electric trace. This object may have additional fields in your geodatabase. The RatedKVA field is the only one necessary to display RatedKVA for an electric trace. This functionality also requires a field on the Transformer feature class.

TransformerUnit Object Class

Field	Data Type	Domain
RatedkVA	Long integer	Transformer Unit KVA

 

 

 

---

Send Comment to ArcFMdocumentation@schneider-electric.com