Data Model Changes

After you import the asset package, advanced users can make changes to the Fiber Manager XI data model to meet specific business needs.

Here is some information to consider first.

• Adds, updates, and deletes of fields, tables, or relationships such as an Inside Building or Marker object, have a small impact on the time to implement the project.

  Example: The strand table contains all the fiber strands in your network. This table must have a field showing the global ID of the parent buffer tube. If the name of the field in your data is different from the Fiber Manager XI data model, you must configure the parent global ID field to point to the correct field. For more information, see the Fiber Manager Configure Your Fiber Objects topic.

• Adds, updates, and deletes of fields, tables, or relationships such as objects used in the Utility Network (UN), circuits, and connections have a large impact on the time to implement the project.

  Example: The Connection table is the default table for fiber object connections at splice points and patch panels. You can change the table used but, you MUST go through the process to map every required field listed for that table. For more information, see the Fiber Manager Connections topic.

Service Territory

The asset package includes the Service Territory layer and it must span the operational and geographical area of your fiber optic system. It represents the territory where the network topology is maintained and where Fiber Manager XI editing tools are available.

• The Service Territory defines the spatial reference for the UN feature classes. If you want to add to, update, or edit the Service Territory, these changes must be done before you create the UN. Once this spatial reference has been defined and the UN has been created, it cannot be changed.

• This feature layer polygon is used to create the UN geographical extent. It must have at least one feature that outlines the service area boundary, plus a reasonable buffer.

• In the map properties, make sure you choose a projected coordinate system for your map that is appropriate for your service location. You can confirm the selected system in your map properties.

  

  See Geographic vs. Projected Coordinate Systems for more information about these map properties.

• Some ArcFM tools require the ability to assign negative Z values for below grade elevations. This spatial reference must contain a vertical coordinate system with a direction of positive up and a resolution that defines a minimum Z value with negative values.

• The feature layer is copied into the new feature dataset as M and Z-enabled, editor tracking enabled, and global IDs added if they are not present.