Collapse All Expand All

Version: 10.2.1c and 10.2.1c SP3

Resource Center Home

In order to correctly calculate voltage level information for the features in your network, Feeder Manager 2.0 requires two particular domains that work in conjunction with one another and with your operating voltage field (which requires these two domains, and which you'll create in a future step).

• FdrMgrVoltageCode domain
• Operating Voltage domain 

Both domains must have these properties:

Field Type: Long Integer
Domain Type: Coded Values
Split policy: Duplicate
Merge policy: Default Value

In order to understand the relationship between these two domains, as well as their collective impact on how Feeder Manager 2.0 interprets your data, it is necessary to include information about the operating voltage field throughout this material. That's despite the fact that you've yet to reach the point in the configuration process where you actually create that field.

 

Operating Voltage Domain

The purpose of this domain is to translate the encoded contents of the operating voltage field into a human-readable string. Later, you'll assign this domain to the operating voltage field. Name it whatever you like.

You must first create an Operating Voltage domain (this domain is called Electric Line Voltage in the Minerville sample data). Below is an example of how you might set up this domain. The codes and values will be specific to your utility. The Description field holds the values that users will see in the dropdown menu.

 

 

FdrMgrVoltageCode Domain

The purpose of this domain is to translate the encoded contents of the operating voltage field contents into machine-readable integers that can be consumed by Feeder Manager 2.0.

Feeder Manager tracing only takes FdrMgrVoltageCode values into account when found on conductors attached to a transformer.

This domain is unlike other domains. Feeder Manager 2.0 requires this domain, but it is NOT assigned to a field. While the OperatingVoltage field utilizes this domain, it is NOT assigned to it.

It is vital that this domain be called FdrMgrVoltageCode EXACTLY. Use the same spelling and capitalization.

For any coded value that exists in your Operating Voltage domain (as it's called in our example) you must have a corresponding value in the FdrMgrVoltageCode domain. The description for each code in the domain must be an integer from 0 to 127, to be assigned to the code in order of increasing voltage.

Feeder Manager 2.0 uses the integer values to store the voltage levels within the Trace Weight field and uses those levels to determine continuity of electrical phases when tracing through a transformer feature.

If you configured your operating voltage domain as was shown in the example above, your FdrMgrVoltageCode domain that might look like this:

 

 

More details

A key component of transformers is that they can tap one or more of the available phases of a primary to provide service voltage. To correctly determine the status of the secondary and service wire when a single phase transformer taps a three-phase line, Feeder Manager uses the phase assignment of the transformer and voltage level attributes on conductor features to control tracing through the transformer.

If the voltage level of the arriving conductor is the same as that for another conductor connected at that junction, then Feeder Manager 2.0 treats the same-voltage wire as a primary and will continue to trace it regardless of the phasing of the transformer. If, on the other hand, the voltage level of a wire is different than that of the arriving conductor, then it is considered to be a wire that goes through the transformer. Feeder Manager will only trace those wires that go through the transformer when it is tracing for the phase(s) assigned to the transformer.

This means that conductors require a field with the model name OPERATINGVOLTAGE. Minerville uses subsets of the Master Operating Voltage domain to assign a code representing the voltage. However, Feeder Manager 2.0 requires that an additional domain called FdrMgrVoltageCode be defined but NOT assigned to this operating voltage field. The FdrMgrVoltageCode domain is logically independent of the other voltage domains (in the Minerville database these include Electric Line Voltage and Electric Device Operating Voltage, both subsets of the Master Operating Voltage domain). The "assignment" of the FdrMgrVoltageCode domain to the field with model name OPERATINGVOLTAGE happens in the Feeder Manager software and isn't established through ArcCatalog.

In spite of its logical independence from other voltage domains, the FdrMgrVoltageCode domain shares "code" values with these domains. In Minerville, the Master Operating Voltage domain stores a series of integer Code values, each of which represents one of the possible operating voltages that could be assigned to a conductor. To each such Code value, the domain assigns a textual Description value (e.g. 4.2kV wye). Both the nominal and operating voltage domains that are assigned to the appropriate fields of devices and conductors all contain the same integer code for each voltage. These domains are assigned to data to support entry and validation by mapping the values of the operating and nominal voltage field onto strings that make sense to people.

The job of the FdrMgrVoltageCode domain is to map the values in the domain to distinct integers from 0 to 127, inclusive. The description for each code in the domain must be an integer from 0 to 127, and should be (for full tracing functionality) assigned to the code in order of increasing voltage (i.e., higher voltages map onto higher integers). Feeder Manager 2.0 uses the integer values to store the voltage levels in the bits of the weight field to support tracing.

 

 

---

Send Comment to ArcFMdocumentation@schneider-electric.com