Circuit Header Migration
Circuit header migration requires population of the Circuits table with a row for each circuit in the network, including a circuit name and identifiers for the network object acting as header. Specifically, the following fields at a minimum must be populated in the Circuits table for each circuit:
|
Field |
Type |
Description |
|---|---|---|
|
circuitname |
String |
Model name of the circuit |
|
fibercircuitheaderclass |
String |
Name of the header feature class |
|
fibercircuitheaderglobalid |
GlobalID |
Unique identifier of the header object |
|
runstatus |
Short Integer |
Records the result of the most recent bulk healing tool run. |
For migrations from 10.x, copy all the data rows from the 10.x Circuits table to the XI Circuits table. This process can be done with the Append geoprocessing tool. Make sure to choose the “Preserve GlobalIDs” option to prevent assignment of new Global IDs to migrated circuit headers.
For migrations from other data sources, select an identifying asset (a port, or a fiber strand) along the route of each circuit that can be traced to identify the other connected facilities for the circuit. These connections become the circuit headers in Fiber Manager XI. Record the corresponding name, any other (optional) circuit details, the GlobalID, and the object's identifying class model name in the circuit table.