Conductors

A conductor in the ArcFM Utility Network (UN) is a topological path that represents the physical connectors between two endpoints. In the ArcFM network model, there can be a branch from points along the path that connect to other network entities. The path corresponding to the conductor may or may not have a geographic shape. If it has a geographic shape, then it is represented by an object in the Line feature class of the Electric Domain network of the UN. If the conductor does not have a shape, such as a conductor stored in ducts, it is a non-spatial conductor and is represented by a row in the EdgeObject table of the electric domain network of the UN. In both spatial and non-spatial cases, the conductor participates in the network topology.

IMPORTANT: Conductor entities cannot have terminals in the Conductor Info rows and do not participate directly in UN network topology. They are not connected to anything, and they must refer to the conductor entity that contains them (which does participate directly in the network model) for information about their position in the electric network topology.

Requirements

A conductor feature Asset Group Asset Type must belong to the E:Has Conductor Info category to have conductor info records.
Conductor Info rows must belong to the E:Conductor Info network category (based on their Asset Group and Asset Type).
The main conductor entity that contains Conductor Info records must belong to the E:Has Conductor Info network category to signal that it is using the a model to capture conductor properties separately for each physical conductor.
Each main conductor entity in the E:Conductor and E:Has Conductor Info network category should contain its own E:Conductor Info objects exclusively. No E:Conductor Info object should be contained by more than one E:Conductor feature.
Conductor Info rows do not participate in UN topology because the conductor info records in EdgeObjects do not show connectivity.
A conductor entity type signals that it is not using conductor info records by its non-membership in the E:Has Conductor Info network category.
Neutral Type, Neutral Size, and Neutral Material attributes must exist on the Conductor Line feature classes and EdgeObject table if you want to model this neutral information separately from the conductor size/material.

Exception to this rule where Junction-to-Junction connectivity is used:

Join the tap transformer to its tap junction.
Connect the internal connections of a vault to the edge connector of a non-spatial conductor in Conduit Manager.

We recommend adding a Network Category, such as E:Connector Conductor, to note a conductor that represents devices as in-line.

For more information, see the Editor XI Conduit Manager Data Model topic.

Impact on ArcFM

Coincident Geometry vs. Junction-to-Junction Connectivity — The UN allows spatial features to use junction-to-junction connectivity instead of a geographic coincident. The ArcFM UN electric model strongly discourages the use of Junction-to-Junction connectivity to connect two features that have point geometry because it does not work well with ADMS and some ArcFM applications. See Conductor Network Categories for more information.