Conductor Network Categories

The AssetGroup and AssetType values for conductor features in both the Line feature class and the EdgeObject table in the Electric Domain network should be qualified with respect to the following Network Categories:

Network Category Name	Applicable tables	Description
E:Conductor	Line EdgeObject	Denotes a main conductor entity that participates in network topology and represents up to three phases and a neutral, where each one may have one or more physical conductors in parallel.
E:Busbar	Line	Denotes a conductor entity that participates in network topology and connects equipment within a substation, a switch cabinet, or any other context where busbar equipment needs to be represented as a conductive path in the electric model. E:Busbar and E:Conductor are mutually exclusive categories.
E:Connector Conductor	Line	Used to denote conductors that connect spatial features instead of using junction-to-junction connectivity.
E:Overhead	Line EdgeObject	Used to denote conductors installed on overhead poles.
E:Underground	Line EdgeObject	Used to denote underground cables.
E:Submersible	Line EdgeObject	Used to denote conductors designed for underwater environments.
E:Has Conductor Info	Line EdgeObject	Used to denote an object that has conductor info records.
E:Conductor Info	EdgeObject	Used to represent conductor info records.

Setting Conductor Attributes when NOT using Conductor Info

The following schema applies to both the Line feature class and the EdgeObject table in the electric domain network, for all types that represent a balanced conductor. This applies to a feature or object type that belongs to the E: Conductor network category only and does not belong to the E:Has Conductor Info network category.

Name	Data Type	Description	Sample Data
PhasesNormal	Short or Long Integer	A domain coded value bound to an in-line network attribute. Used to control phase propagation in electric subnetworks and feed in to electric tracing behavior.	1 = C 2 = B 3 = BC 4 = A 5 = AC 6 = AB 7 = ABC 0 = None
ConductorSize	Short or Long Integer	Domain lookup code for the nominal diameter of the conductive material for the phase conductors.	1 = “1/0” 113 = “1000 kCM”
ConductorMaterial	Short or Long Integer	Domain lookup code for the conductive material for the phase conductors.	18 = “ACSR” 23 = “AA” 29 = “Aluweld”
NeutralType	Short or Long Integer	Domain lookup code describing the neutral conductor.	0 = “None” 1 = “Present” 3 = “Concentric”
NeutralSize	Short or Long Integer	Domain lookup code for the nominal diameter of the conductive material for the neutral conductor.	1 = “1/0” 113 = “1000 kCM”
NeutralMaterial	Short or Long Integer	Domain lookup code for the conductive material for the neutral conductor.	18 = “ACSR” 23 = “AA” 29 = “Aluweld”

Setting Conductor Attributes with ConductorInfo

The following schema applies to both the Line feature class and the EdgeObject table in the electric domain network, for all types that represent an unbalanced conductor. This applies to a feature or object type that belongs to both the E:Conductor and the E:Has Conductor Info network category. The PhasesNormal attribute is needed to feed in to the phase propagation in the electric network model. The value must reflect all phases found in the ConductorInfo rows, from the PhasesNormal value that is held by the conductor.

Name	Data Type	Description	Sample Data
PhasesNormal	Short or Long Integer	Domain coded value. Bound to an in-line Network Attribute. Used to control phase propagation in electric subnetworks and to inform electric tracing behavior. The PhasesNormal value of an unbalanced conductor should be automatically maintained, from an AutoUpdater as an example, as the union of the PhasesNormal values for all of the ConductorInfo rows that it contains.	1 = C 2 = B 3 = BC 4 = A 5 = AC 6 = AB 7 = ABC 0 = None

Name

Data Type

Description

Sample Data

PhasesNormal

Short or Long Integer

Domain coded value. Bound to an in-line Network Attribute. Used to control phase propagation in electric subnetworks and to inform electric tracing behavior. The PhasesNormal value of an unbalanced conductor should be automatically maintained, from an AutoUpdater as an example, as the union of the PhasesNormal values for all of the ConductorInfo rows that it contains.

1 = C

2 = B

3 = BC

4 = A

5 = AC

6 = AB

7 = ABC

0 = None

ConductorInfo Attributes

The following schema applies to the EdgeObject table in the electric domain network. This is where the ConductorInfo units that belong to a topological conductor feature, or object, are stored. Each row has these attributes populated:

Name	Data Type	Description	Sample Data
PhasesNormal	Short or Long Integer	Domain coded value. Specifies the electrical phase carried by the physical conductor that this ConductorInfo row represents.	1 = C 2 = B 3 = BC 4 = A 5 = AC 6 = AB 7 = ABC 0 = None
ConductorSize	Short or Long Integer	Domain lookup code for the nominal diameter of the conductive material.	1 = “1/0” 113 = “1000 kCM”
ConductorMaterial	Short or Long Integer	Domain lookup code for the conductive material.	18 = “ACSR” 23 = “AA” 29 = “Aluweld”
IsNeutral	Short or Long Integer	Domain lookup code to indicate whether this is a neutral conductor.	0 = “No” 1 = “Yes”

Network Junction

Network Junction features must exist as you try to connect conductors that belong to different Asset Group and Asset Types. In this example, an electric junction feature of a medium voltage connection point is used when connecting a medium voltage overhead conductor to a medium voltage busbar.

During customer implementations, these electric junctions are used for the client to manage UN connectivity. Samples are included in the ArcFM UN Asset Packages and the EUNF Sample Data.

Recommended Configurations

We recommend UN rules are set so one Network Junction feature type serves as the connection between two conductors of different types.

Product Limitations

The ArcFM UN will not place restrictions on these electric junctions. When Designer XI pushes a design to the UN, the product tries to select the correct electric junction feature type using UN connectivity rules. You can use an Autoupdater for this functionality. See the OOTB Autoupdaters topic for more information. If more than one electric junction can be used by evaluating the UN connectivity rules, an error will be returned to the designer. If the UN connectivity rules cannot be applied, an UNKNOWN Electric Junction will be added.