Conduit Manager

Conduit Manager functionality requires three elements: conduit features, the conductors and cables (such as fiber optic cables) placed within them, and the annotation describing their arrangement. Conduit Manager uses the model name ULS (underground linear structure) to represent conduits and the model name ULSMember to represent conductors and cables that may be placed in them.

The conduit cross section contains the Contents List describing the conductors and cables within ducts (or trenches). Administrators can configure the database to retrieve different field values and other text to create the Contents List. You can use an expression string, a field, or the ObjectID (default). You can also change the annotation expression.

This section describes the steps necessary to configure a geodatabase to use Conduit Manager. Configuration is separated into two parts: 1) the minimum configuration which allows the user to associate conductors and cables with conduit and place cross section annotation; 2) additional configuration that allows the use of a variety of optional functionality affecting annotation, duct size, headings and more.

The basic steps for configuring Conduit Manager assume your geodatabase has minimal general ArcFM configuration (ArcFM configuration is required). So some of the steps in this topic may be partially completed (some model names may be already created, etc.) in your geodatabase. It's a good idea, however, to ensure everything is configured correctly before moving to the next step.

Once these steps are complete your geodatabase has been configured and you may create maps with your underground conduit system features. Conduit tracing requires additional configuration. However, a license for Conduit Manager is NOT required to perform conduit traces. Below is a list of optional functionality that is available in Conduit Manager and requires additional configuration.

  • Underground Facility Manager (UFM): This tool allows the user to manage the underground distribution network using manholes. This includes creating, editing and viewing manhole and duct bank configurations.

  • Phase Designation: This functionality allows the user to place different phases of a conductor in different positions (ducts) within a conduit.

  • Conductor Information: For banked conductors, you may create a related Conductor Information object class that maintains information about each unit of the bank. Conductor Information requires that Phase Designation be configured as well.

  • Duct Size Options: Users may place subducts within ducts providing the conduit carries a field with the field model name DUCTSIZE.

  • Annotation Options: Conduit Manager provides various ways to display a conduit's annotation. To utilize the annotation options, you must also configure Conduit Information. There are two methods to configure annotation.

  • Duct Bank/Conduit Size Options: A conduit (duct bank) has a default size of 40 by 40 map units. You may modify the dimensions of a conduit by adding two fields to the conduit feature class.

  • Duct ID Options: You can add a field that stores a utility-assigned identifier for the Duct. The field must have the field model name DUCTID assigned.

  • Availability Indicator: This functionality allows you to designate a duct's availability using an Available field.

  • Heading Options: You can place a heading as part of the cross-section annotation feature. It includes the material and size of the duct.

  • Lasso Tool: This tool provides an easy way to relate a group of conductors with a conduit feature. This section also describes how to configure lasso annotation.

QR code for this page

Was this helpful?