ArcFM Desktop > ArcFM > Feeder Manager > Feeder Manager Step 6: Assign Model Names |
Feeder Manager is configured, like other ArcFM components, by assigning model names and autoupdaters to network features. Assign model names to features with this in mind: you should never apply more than one of the class model names SWITCH, FDRMGRPROTECTIVE, or TRANSFORMER (used by the built-in weight autoupdater only) to any feature class in your electric distribution network. For example, if your network has a feature class that contains both manual switches and fuses, create two separate feature classes so that you can apply the model name SWITCH to one and FDRMGRPROTECTIVE to the other. In addition, the SWITCH and TRANSFORMER class model names may NOT be applied to any feature class that may contain circuit source features. Put another way, assign any class that may contain circuit source features the model name FDRMGRPROTECTIVE. For accurate KVA ratings, you should apply the TRANSFORMERUNIT model to only the TransformerUnit object class.
This step requires that you assign model names and field model names to your feature classes through the ArcFM Properties Manager. It is easiest to assign all of the model names and field model names for a feature class rather than assigning all of the model names then all of the field model names.
If you want to use the ArcFM Electric Trace Options menu in ArcMap to choose whether a feature class participates in protective device traces, assign the PROTECTIVE model name to that feature class.
The Appendix contains more information about the various "Protective" model names. View the topic titled "FAQ: What is the difference between the various "Protective" model names?"
If you have created a FdrMgrNonTraceable field for any feature classes or subtypes, you must assign the FDRMGRNONTRACEABLE field model name to the FdrMgrNonTraceable field.
Object Model names: SPLITTARGET
ELECTRICNETWORKEDGE: You must assign this model name to any edge features in your electric network that will participate in the ArcFM Electric Next Upstream Protective Device and Isolation Protective Device traces.
FEEDERSECONDARY: Assign this model name if you want secondary conductors downstream of a transformer to inherit the transformer's LowSideVoltage or OperatingVoltage value.
Field Model names:
Field Field Model Name Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
OperatingVoltage
OPERATINGVOLTAGE
PhaseDesignation
PHASEDESIGNATION
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.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No<
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = NoThings to ensure for correct behavior:
- FdrMgrNonTraceable is not set on features that you want to be traced
- If you wish feeder manager to respect conductor phasing then a phase designation field is required for the edge, and the field must be driven by the phase designation domain (see previous step for instructions on setting up this domain)
- Feeder Manager uses the voltage levels to determine continuity of phases when tracing though a transformer feature.
Object Model names: SPLITTARGET
ELECTRICNETWORKEDGE: You must assign this model name to any edge features in your electric network that will participate in the ArcFM Electric Next Upstream Protective Device and Isolation Protective Device traces.
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
OperatingVoltage
OPERATINGVOLTAGE
PhaseDesignation
PHASEDESIGNATION
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
You will need to assign the NormalStatus domain to the NormalPosition fields.
Right-click the Switch feature class and select Properties.
Click the Fields tab and select the NormalPosition_A field.
In the Field Properties window, set the Domain field to Normal Status.
Repeat steps 2 and 3 for NormalPosition_B and NormalPosition_C.
Object Model name: SWITCH
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
NormalPosition_A
NORMALPOSITION_A
NormalPosition_B
NORMALPOSITION_B
NormalPosition_C
NORMALPOSITION_C
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and SubSource fields should be aded to all junction classes eligible to represent subsidiary sources.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGlobalID
Global ID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGUID
GUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either only CircuitSourceID or both CircuitSoureGlobalID and CircuitSourceGUID, but not all three. If all three are added, the feature will not work with the manager.
CircuitSourceID
CIRCUITSOURCEID
Field Info Tab:
Reset After Create = Yes
SubSource
SUBSOURCE
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = NoThings to ensure for correct behavior:
- Must exist as a simple junction edge and must split any complex edge
If your feature class acts as a source, you will need to assign the DYNAMICPROTECTIVEDEVICE model name. If it is not a source, do NOT assign the DYNAMICPROTECTIVEDEVICE model name.
Right-click the feature class and select Properties.
Click the Fields tab and select the NormalPosition_A field.
In the Field Properties window, set the Domain field to Normal Status.
Repeat steps 2 and 3 for NormalPosition_B and NormalPosition_C.
Object Model names: FDRMGRPROTECTIVE and DYNAMICPROTECTIVEDEVICE (assign both model names to dynamic protective devices). The exception to this is Fuses. Fuses should be assigned the FDRMGRPROTECTIVE model name only.
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
NormalPosition_A
NORMALPOSITION_A
NormalPosition_B
NORMALPOSITION_B
NormalPosition_C
NORMALPOSITION_C
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and SubSource fields should be aded to all junction classes eligible to represent subsidiary sources.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGlobalID
Global ID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGUID
GUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either only CircuitSourceID or both CircuitSoureGlobalID and CircuitSourceGUID, but not all three. If all three are added, the feature will not work with the manager.
CircuitSourceID
CIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesSubSource
SUBSOURCE
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model names: TRANSFORMER
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
Optional: Assign the following field model name 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
LOWSIDEVOLTAGE
Optional: Assign the following field model name if you want to display the Total RatedkVA for an electric trace. This functionality also requires model names on the TransformerUnit object.
RatedkVA
RATEDKVA
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and SubSource fields should be aded to all junction classes eligible to represent subsidiary sources.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGlobalID
Global ID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGUID
GUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either only CircuitSourceID or both CircuitSoureGlobalID and CircuitSourceGUID, but not all three. If all three are added, the feature will not work with the manager.
CircuitSourceID
CIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesSubSource
SUBSOURCE
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = No
You may tap one or more of the available phases of a primary to provide service voltage. Feeder Manager uses the phase assignment of the transformer and voltage level attributes on conductor features to control tracing through the transformer. This allows Feeder Manager to correctly determine the status of the secondary and service wire when a single phase transformer taps a three phase line.
Configure this class if you want your default junction features to carry an automatically updated FeederID. If you haven't yet created your geometric network, this feature class won't be available. You will need to configure it after creating the geometric network. This will be discussed later.
Object Model names: None
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable =No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model names: None
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model Name: none
Field Model Names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Reset After Create = Yes
Add either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
You will need to assign the NormalStatus domain to the NormalPosition fields.
Right-click the feature class and select Properties.
Click the Fields tab and select the NormalPosition_A field.
In the Field Properties window, set the Domain field to Normal Status.
Repeat steps 2 and 3 for NormalPosition_B and NormalPosition_C.
Object Model names: SWITCH
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
NormalPosition_A
NORMALPOSITION_A
NormalPosition_B
NORMALPOSITION_B
NormalPosition_C
NORMALPOSITION_C
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and SubSource fields should be aded to all junction classes eligible to represent subsidiary sources.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGlobalID
Global ID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGUID
GUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either only CircuitSourceID or both CircuitSoureGlobalID and CircuitSourceGUID, but not all three. If all three are added, the feature will not work with the manager.
CircuitSourceID
CIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesSubSource
SUBSOURCE
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model names: None
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model names: TRANSFORMER
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
Optional: The following fields are required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network. The CircuitSourceID and SubSource fields should be aded to all junction classes eligible to represent subsidiary sources.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGlobalID
Global ID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesCircuitSourceGUID
GUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either only CircuitSourceID or both CircuitSoureGlobalID and CircuitSourceGUID, but not all three. If all three are added, the feature will not work with the manager.
CircuitSourceID
CIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesSubSource
SUBSOURCE
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model names: FDRMGRLOADPOINT
Note for Responder Users: The FDRMGRLOADPOINT model name may be assigned differently depending on your data model. Refer to the Responder documentation for information about assigning this model name. It is strongly recommended that you assign this model name during the initial Feeder Manager configuration to avoid the need to re-initialize trace weights during Responder configuration.
Note for All Other Users: The FDRMGRLOADPOINT model name isn't currently used, but will be required for future Feeder Manager functionality. It is strongly recommended that you assign it during the initial Feeder Manager configuration to avoid the need to re-initialize trace weights at a later time.
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
ServiceCurrentRating
SERVICECURRENTRATING
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model names: None
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
Object Model names: None
Field Model names:
Field
Field Model Name
Properties FeederID
FEEDERID
Field Info Tab:
Reset After Create = Yes
FeederID2
FEEDERID2
Field Info Tab:
Reset After Create = Yes
FeederInfo
FEEDERINFO
Field Info Tab:
Editable = No
Reset After Create = YesElectricTraceWeight
MMELECTRICTRACEWEIGHT
Field Info Tab:
Reset After Create = Yes
PhaseDesignation
PHASEDESIGNATION
RatedKVA
RATEDKVA
Optional: The following field is required only if you have a multi-tiered network. The ParentCircuitSourceID field should exist on every feature class that participates in the multi-tiered network.
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesAdd either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
Field Info Tab:
Visible = Yes
Editable = No
Reset After Create = YesFacilityID
FACILITYID
Field Info Tab:
Visible = Yes
Editable = Yes
Reset After Create = No
The following object class is required ONLY if you are using a multi-tiered network and Extended Feeder Manager.
Object Model names: CIRCUITSOURCEID
Field Model names:
Field
Field Model Name
FeederLevel
FEEDERLEVEL
FeederName
FEEDERNAME
ObjectID
CIRCUITSOURCEID
ParentCircuitSourceGUID
PARENTCIRCUITSOURCEGUID
Add either ParentCircuitSourceGUID or ParentCircuitSourceID, but not both. If both are added, the feature will not work with the manager.
ParentCircuitSourceID
PARENTCIRCUITSOURCEID
RelatedFeatureClassName
RELATEDFEATURECLASSNAME
RelatedObjectID
RELATEDOBJECTID
The following object class is required if you wish to view the Total RatedkVA for an electric Trace. A field model name on the Transformer class is required as well.
Object Model names: TRANSFORMERUNIT
Field Model names:
Field
Field Model Name
RatedkVA
RATEDKVA