Conduit Manager and Physical Conductors
Using ConductorInfo to Model Physical Conductors
The main conductor entity can exist in the Line or EdgeObject table. Conduit Manager lets a conductor that occupies a duct be non-spatial and stored in the EdgeObject Table. In either case, spatial or non-spatial, the conductor belongs to the E:Conductor network category, and participates in network connectivity.
When using conductor info records, the main conductor, one that belongs to the E:Conductor category, does not carry any conductor attributes, such as Size and Material. The main conductor uses UN containment associations for non-spatial conductor units, such as units in the E:Conductor Info network category, to show the conductor attributes. The Conductor Info row shows the Size and Material attributes of the single physical conductor that it represents, and the PhasesNormal attribute value to indicate the named electrical phase to which it belongs (if it is a phase conductor). If the Conductor Info row represents a neutral conductor, then it will have PhasesNormal = None and IsNeutral = True. Using the conductor info supports a separate detailed accounting of each physical conductor present, including the ability to represent multiple conductors of different types that are connected in parallel for a single phase or for the neutral.
Required Configuration
-
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.
Conductor Info and Physical Conductors
If not using Conductor Info to model physical conductors, the main conductor entity itself (a row in the Line or the EdgeObject table) shows attributes for physical conductor properties, such as Size and Material, and apply to each of the physical conductors that may be present, including both phase and neutral conductors.
Required Configuration
-
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.
Conductor Connectivity
A spatial or non-spatial conductor participates in the network topology of the electric domain network in the UN. It is interpreted as a path that electric power can flow on one or more of the electric phases A, B, and C. For a spatial conductor, that path has a polyline shape that can be seen in the map display. A non-spatial conductor path, such as a conductor going through a duct in Conduit Manager, is an abstract connection between two junctions in the network model, where the duct may be spatial or non-spatial.
Devices can be directly connected to a conductor with spatial coincidence with either of its 2 endpoints, such as in the case of two-terminal switchable devices, or at any point along the length of the conductor with or without the mediation of a special tap feature, such as transformers that can use a tap feature while capacitors do not need one. Details on how conductors are connected to various types of electric equipment in these various ways are given in the individual section for each equipment type.