Duct Definition

The DuctDefinition object class has fields that describe selected characteristics of a duct, such as size or material. The table below provides some common examples, and you can add more fields for your business rules. In other words, adding fields to this table is how you add fields to the ArcFM Conduit Configuration dialog:

IMPORTANT: No data should be saved in the DuctDefinition table itself. The table should have the fields (and can have associated domains), but no data. As end users populate data using the ArcFM Conduit Configuration dialog, their edits are saved in a single binary large object (BLOB) attribute field of the ConduitSystem feature class called Configuration.

Subtypes: Duct Bank, Trench. The use of subtypes is optional. The Subtype attribute can be removed if subtypes aren't used in the model.

Model Names: DUCT

IMPORTANT: If you are implementing GlobalIDs to support Esri Replication, be aware that the DuctDefinition object class does NOT support a GlobalID field. The Visibility property on this field must be set to No to avoid errors.


Field Name

Field Type




Actual size of the duct. Conduit Manager can use this field (it's not required) to store the actual size of the duct when placing ducts within ducts. It requires that the ACTUALDUCTSIZE model name be assigned.



The Conduit Manager Availability Indicator functionality uses this field to indicate whether a duct is available for conduit placement. It uses the DUCTAVAILABILITY model name on this field.



Stores a unique identifier for a duct. Conduit Manager can be configured to use this field with the DUCTID model name assigned.



Size of the duct. Conduit Manager uses this field to provide the ability to place ducts within ducts. Underground Facility Manager also uses this field. It requires that the DUCTSIZE model name be assigned.



Indicates the type of material a conduit is made of. Conduit Manager uses this field with the DUCTMATERIAL model name assigned.

QR code for this page

Was this helpful?