Create Domains

There are three domains that may be set up to work with Feeder Manager. These domains provide the coded values for various functionality within Feeder Manager. The FdrMgrVoltageCode domain is required. Set up the Phase Designation, Single Phase, Two Phase, and Three Phase domains if you wish to maintain information on phases. Use the FdrMgrNonTraceable domain if you want to identify specific edge features as non-traceable.

Phase Designation Domain

If you want to use phasing, you must create the Phase Designation domain. Phasing allows you to maintain information on individual phases of a conductor or device.

Coded Values:

Code

Description

7

ABC

6

AB

5

AC

4

A

3

BC

2

B

1

C

Single Phase Domain

This domain provides phasing for single-phase conductors and devices. Phasing allows you to maintain information on individual phases of a conductor or device.

Coded Values:

Code

Description

4

A

2

B

1

C

Two Phase Domain

This domain provides phasing for two-phase conductors and devices. Phasing allows you to maintain information on individual phases of a conductor or device.

Coded Values:

Code

Description

6

AB

5

AC

3

BC

Three Phase Domain

This domain provides phasing for three-phase conductors and devices. Phasing allows you to maintain information on individual phases of a conductor or device.

Coded Values:

Code

Description

7

ABC

FdrMgrNonTraceable Domain

If you created a FdrMgrNonTraceable field on one or more edge feature classes, you may also wish to create a domain to be applied to fields carrying the FDRFieldiMGRNONTRACEABLE field model name (this model name will be assigned in the next step). This will make the field contents easier to interpret, and will enforce a restricted range of values for that field.

Properties:

  • Field Type: Compatible with fields with model name FDRMGRNONTRACEABLE

  • Domain Type: Coded Values

  • Split policy: Duplicate

  • Merge policy: Default Value

Coded Values:

Code

Description

0

Traceable

1

NonTraceable

FdrMgrVoltageCode Domain

The FdrMgrVoltageCode domain is unlike any other domain. It converts the values found in a field with the OPERATINGVOLTAGE field model name. These values are integers from 0 to 127. FdrMgrVoltageCode converts them as a seven-bit sequence within the MMElectricTraceWeight integer field. Feeder Manager requires this domain be created, but it is NOT assigned to a field. While the OperatingVoltage field utilizes this domain, the domain is NOT assigned to the field.

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, so that 0 would be the description for 2.4. Feeder Manager uses the integer values to store the voltage levels within the Trace Weight field and the voltage levels to determine continuity of electrical phases when tracing through a transformer feature.

Properties:

  • Field Type: Compatible with fields assigned the OPERATINGVOLTAGE model name

  • Domain Type: Coded Values

  • Split policy: Duplicate Value

  • Merge policy: Default Value

For detailed information about creating voltage code domains visit the Voltage Code domains section.

NormalStatus Domain

This domain will be assigned in a later step to the NormalPostion_A, NormalPosition_B, and NormalPosition_C fields for Circuit Source features.

Properties:

  • Field Type: Long Integer

  • Domain Type: Coded Values

  • Split policy: Duplicate

  • Merge policy: Default value

Coded Values:

Code

Description

0

Open

1

Closed

2

Not Applicable

Optional:

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

Yes/No Domain

Properties:

  • Field Type: Short Integer

  • Domain Type: Coded Values

  • Split policy: Duplicate

  • Merge policy: Default value

Coded Values:

Code

Description

0

No

1

Yes

Optional:

Create the following domain if you want to display the Total RatedkVA for an electric trace. The ArcFM Electric Trace Options includes an option to display kVA by phase for a trace. To access this option, in ArcMap click the Options button on the ArcFM Electric Traces toolbar and select the Electric Traces tab:

With this option checked, the Rated kVA dialog is shown after each trace. This displays the sum of the rated kVA (by phase) for all transformer units returned by the trace. If transformer units are not present, the rated kVA is calculated from the kVA values of the transformers. If configured incorrectly, the values in this box will all be 0.0.

To display Rated kVA for a trace, you will need to create the following domain. This domain holds the possible RatedkVA values in your network. The following table shows an example of how this domain may be created. Your domain will probably have more values.

Transformer Unit kVA

Properties:

  • Field Type: Long Integer

  • Domain Type: Coded Values

  • Split policy: Duplicate

  • Merge policy: Default value

Coded Values:

Code

Description

10

10 kva

15

15 kva

25

25 kva

38

37.5 kva

50

50 kva

75

75 kva

100

100 kva

Voltage Code Domains

This step is necessary only if you want Feeder Manager to recognize the Operating Voltages of your network features. However, if you have a multi-tiered network and are using the ArcFM FeederSubsource Level autoupdater, you must set up the voltage code domains.

  • The OPERATINGVOLTAGE field model name is required on the OperatingVoltage field and the field must be a Long Integer.        

  • The Operating Voltage field (designated by the OPERATINGVOLTAGE field model name) Requires two domains:

    • The first domain is created by the user, specific to the utility and the operating voltages that they work with. This domain is assigned to the operating voltage field. It can be named whatever you like. It must be a Long Integer coded value domain. For documentation purposes, we will call this domain Operating Voltage domain.                

    • The second domain is the FdrMgrVoltageCode domain. It must have the exact spelling and capitalization as shown. It must be set up with corresponding values to the Operating Voltage domain (see example below). It must also be a Long Integer coded value domain.

The following sections focus on setting up these two domains.

Operating Voltage Domain

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 the user will see in the dropdown menu.

FdrMgrVoltageCode Domain

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

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

For any coded value that exists in your first domain (Operating Voltage domain in our example) you must have a corresponding value in the FdrMgrVoltageCode domain. The description field in this domain MUST contain an integer between 0 and 127. So we would have a FdrMgrVoltageCode domain that might look like this:

Operating Voltage

Code

Description

120

2.4 LG/4.6 LL kV Grounded Y

160

7.2 LG kV Grounded Y Single Phase

210

7.2 LG/12.5 LL kV Grounded Y

230

7.62 LG/13.2 LL kV Grounded Y

270

8.0 LG/13.8 LL kV Grounded Y

340

14.4 LG/24.9 LL kV Line-to-Neutral

    FdrMgrVoltageCode

Code

Description

120

24

160

32

210

32

230

46

270

54

340

68

NOTE: Schneider Electric recommends creating the descriptions in the FdrMgrVoltageCode domain so that increasing voltages map to increasing description values in the Operating Voltage domain. If Responder is implemented, this step is required.If Network Adapter is implemented, it requires that any equivalent voltages map to the same value in the Description field. For example, 160 means "7.2 kv grounded Y single phase" and 210 means "7.2 kv grounded Y two phase", making 160 and 210 physically the same. Therefore, they should both map to the same value (e.g., 160/32 and 210/32).

Operating Voltage

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 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 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 uses the integer values to store the voltage levels in the bits of the weight field to support tracing.

QR code for this page

Was this helpful?