F_CIRCUITCOMPONENT

To avoid a severe drop in performance, this table should NOT be an ArcFM table. It should be created as an Esri table.

The ObjectID field is automatically created (by Esri) when you create the table.

Since this table is considered a Fiber Manager application table, users and admins should not edit attributes nor records directly within this table. All circuit changes should be performed through the Fiber Manager interface.

This table must be versioned for an SDE database. Consult Esri's documentation for more information about versioning tables.

In ArcGIS applications, there are four numeric data types: Short Integer, Long Integer, Float, and Double. The choices reflect a balance between minimizing storage space while still allowing enough range and precision for the field to be useful. For example, because lengths typically have decimals, these fields are assigned either Float or Double.

In the table below, any field set to integer does need to be either a Short or Long Integer, as these fields cannot contain decimals. So, the decision comes down to the minimum and maximum values you need for the field:

• Short Integer Storable Range: -32,768 to 32,767

• Long Integer Storable Range: -2,147,483,648 to 2,147,483,647

So, as an example, would you ever have more than 32,767 patch panels on a single rack? No. So, the RackPosition field could be a Short Integer. Conversely, foot or meter stamps along a cable could easily exceed 32,767. So, CableMarking fields should be a Long Integer. Our integer recommendations err on the side of more range and usefulness, but your company could decide to change a Long Integer to a Short Integer (or a Double down to a Float) if you knew the maximum values would never exceed the types’ upper threshold.