Data Model Changes

After you import the asset package, the data model can be adjusted to align with an existing Fiber Manager 10.x model, or to otherwise meet specific business requirements. See Data Migration Best Practices for more information.

Note that many changes to the Fiber Manager XI data model will result in necessary software configuration changes, thus increasing the implementation effort.

Here are some examples of how data model changes can impact configuration.

• Including custom fields, tables, or relationships for non-fiber objects, such as buildings or towers, have little or no impact on the implementation effort.

• Adds, updates, and deletes of fields, tables, or relationships for fiber objects, such as cables or patch locations, have a small impact on the implementation effort.

  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 Objects topic.

• Adds, updates, and deletes of fields, tables, or relationships for fiber connectivity, such as circuits and connections, have a larger impact on the implementation effort.

  Example: The Connection table is the default table for fiber strand connections at splice points and patch panels. You can change the table used for connections, but then you must map every required field in that table to the fields expected by Fiber Manager. For more information, see the Connections topic.