Appendix 10.8.1 – Configuration Guide

Welcome and FAQs
Abandon Model Names and Settings
- Gas Abandon
- Water Abandon
- Electric Abandon
Application Metrics
ArcCatalog Data Types
Standalone Applications
ArcFM System Tables
- How to Assign Permissions to System Tables
Autoupdaters
- Attribute Autoupdaters
- Special Autoupdaters
- Relationship Autoupdaters
- Feeder Manager Autoupdaters
  - ArcFM Feeder Cache Maintenance Autoupdater
- Abandon Autoupdaters
- Combo Autoupdaters
- Minerville Autoupdaters
- Server Autoupdater Blocklist
Bitgate Fields
- Gas Tracing - Junctions
- Gas Tracing - Edges
- Water Tracing - Junctions
- Water Tracing - Edges
- Electric Tracing - Junctions
- Electric Tracing - Edges
- FeederInfo
Cable Pulling Calculations
- Cable Clearance
- Pulling Configuration
- Weight Correction Factor
- Effective Coefficient of Friction
- Bends
- Initial or Reelback Tension
- Pulling Tensions
- Sidewall Bearing Pressure
- Maximum Allowable Pulling Tension with a Pulling Eye
- Maximum Allowable Pulling Tension with a Basket Weave Grip
- Cable Pulling Tables
Class Model Names
Designer NonCreatable Features
Edit Tasks
Electric Distribution Data Model Overview
- Structures Overview
- Circuit Segments Overview
- Devices Overview
  - Electric Device
  - Misc Network Feature
  - Open Point
  - Overcurrent Protective Device
  - Dynamic Protective Device
  - Fuse
  - Power Factor Correcting Equipment
  - Street Light
  - Switch
  - Transformer Bank
  - Transformer
  - Voltage Regulator
  - Device Control
    - Network Protector
    - Relay Control
    - Recloser Control
    - Reclose Sequence
    - Recloser Electronic Control
    - Recloser Hydraulic Control
    - Sectionalizer Control
    - Sectionalizer Electronic Control
    - Sectionalizer Hydraulic Control
  - Device Object
  - Unit Object
- Customer and Service Overview
Interpretation of FeederSourceInfo Values
Fiber Manager Data Architecture Overview
- Fiber Optic Cable
- Patch Location
- Splice Point
- Device Point
- Splitter Location
- Fiber Slack Loop
- Fiber Fault
- Transition Point
- Fiber Structure
- F_FIBERCONNECTIONOBJECT
- F_CIRCUIT
- F_CIRCUITCOMPONENT
- Additional Information
Fiber Tracing Types
Field Model Names
- Electric Field Model Names
- Gas Field Model Names
- Water Field Model Names
- Domain Independent Field Model Names
- Designer Field Model Names
- Network Adapter Field Model Names
- Responder Field Model Names
- Fiber Manager Field Model Names
Gas Distribution Data Model Overview
- Devices and Facilities Overview
- Pipes and Maintenance Overview
- Cathodic Protection Overview
Geodatabase Replication Versions
How Design Optimization Works
- How Design Optimization Works: Methodology and Algorithms
- Transformer Selection Example
How Electric Tracing Works
- Data Considerations
- Impact of Conductor Phase Designation
- Transformers and Continuity of Phases Between Primary and Secondary
- Electric Trace Options
- How Phase Constraints Are Interpreted
How Gas Tracing Works
- Valve Isolation
- Cathodic Protection System
- Squeeze Off
- Gas Pressure System
- Gas System
- Gas Trace Options
How Water Tracing Works
- Water Valve Isolation
- Water Cathodic Protection System
- Water Pressure System
- Water System
Login Connection Strings
- Data Considerations
  - Process Framework
- Select License
Remove All Refreshes While Placing Template
Secondary Circuit Analysis Calculations
- Load Flow Calculation
- Fault Calculation
- Motor Starting Calculation
- Secondary Circuit Analysis Tables
Splits
Tips for Creating a Map Document
Validation Rules
XML
XML Style Sheets
Glossary
- A
- B
- C
- D
- E
- F
- G
- I
- K
- L
- M
- N
- O
- P
- Q
- R
- S
- T
- U
- V
- W
- X
- Z

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.

Attributes:

Field Name	Field Type	Description
ActualSize	text	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.
Availability	text	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.
DuctID	text	Stores a unique identifier for a duct. Conduit Manager can be configured to use this field with the DUCTID model name assigned.
DuctSize	text	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.
Material	text	Indicates the type of material a conduit is made of. Conduit Manager uses this field with the DUCTMATERIAL model name assigned.

Show QR code for this page

QR Code is a registered trademark of DENSO WAVE INCORPORATED in Japan and other countries.

Was this helpful?

Contact Information

Legal Information

Change your cookie settings