Conduit Manager Data Migration 10.x to XI

Data migration is an important part of your upgrade to Editor XI and Conduit Manager XI. The tables provided below identify the feature classes and fields in the 10.x Series application and where they should be mapped in the XI Series application. Use these tables to scope and plan your data migration. With the exception of the Conduit Blob field, all of the Conduit Manager 10.x fields have an equivalent field in the Conduit Manager XI data model. Your company likely added other fields to your data model, and these fields vary by company. Thus, they are not represented in the tables below. Most likely, there is a logical field in the Conduit Manager XI data model to accept your additional fields. Work with your implementation team to determine the best fit.

Non-UFM Implementation

The 10.x Conduit Manager data model’s Conduit feature class includes a blob field with the DuctBankConfiguration field model name. The field contains the layout and attributes of conduits’ ducts. To migrate this data, we first need to unpack that information from the blob field if you did not implement Underground Facilities Manager (UFM). Two developer samples exist to help with this process. We recommend making use of the Create Vault Boundaries developer sample first, followed by the Create Duct Ends from Blob developer sample second. To download these developer samples, refer to the Conduit Manager Data Migration 10.x to XI article on myArcFM.

Create Vault Boundaries Developer Sample

The Create Vault Boundaries developer sample, written for use in ArcMap, creates polygons around the selected Underground Structure points. It is implemented in ConduitDataConversionAddin.sln. This sample defaults the size of the Vault Boundary to 10 x 10 and the wall height to 10. The following data configuration is required:

• A point feature class with the ManholeFeatureSnap model name assigned

• A polygon feature class with the VaultBoundary model name assigned: VaultBoundary is a new object class model name created for this developer sample. The VaultBoundary feature class requires the following fields:

  • FacilityId — this is a text field with the FacilityId field model name assigned.

  • WallHeight — this is a float field with the WallHeight field model name assigned.

Create Duct Ends from Blob Developer Sample

The Create Duct Ends from Blob developer sample, written for use in ArcMap, iterates over Conduits connected to the selected Underground Structures. It uses information stored in the Conduit feature’s blob field to create three different types of features that are used to populate UN data in the Editor XI data model:

• One Duct Bank End feature is created where the conduit intersects the Vault Boundary polygon.

• One Duct End feature is created for each duct definition stored in the Conduit’s blob field. The Duct End features are created on the edge (wall) of the Vault Boundary.

• One Underground Connection Point is created at the same location as each Duct End feature for each duct that is associated to a cable.

It is implemented in ConduitDataConversionAddin.sln. It requires the following data configuration:

• A point feature class with the ManholeFeatureSnap model name assigned

• An edge feature class with the ULS model name assigned

• A polygon feature class with the VaultBoundary model name assigned — VaultBoundary is a new object class model name created for this developer sample. We recommend the dataset to which this feature class belongs have a Z coordinate system defined. The VaultBoundary feature class requires the following fields:

  • FacilityId — this is a text field with the FacilityId field model name assigned.
  • WallHeight — this is a float field with the WallHeight field model name assigned.

• A point feature class with the DuctBankEnd model name assigned — this feature class’s coordinates must have Z values. The DuctBankEnd feature class requires the following field:

  • ConduitObjectID — this is a long integer field with the ConduitIdentifier field model name assigned.

• A point feature class with the DuctEnd model name assigned — this feature class’s coordinates must include Z values. The DuctEnd feature class requires the following fields:

  • ConduitObjectId — this is a long integer field with the ConduitIdentifier field model name assigned.
  • Diameter — this is a text field with the DuctSize model name assigned.
  • DuctCrossSectionShape — this is a short integer field with the DuctCrossSectionShape model name assigned.
  • DuctId — this is a text field with the DuctName model name assigned.
  • IsAvailable — this is a short integer field with the DuctAvailability model name assigned.
  • IsOccupied — this is a short integer field with the DuctOccupied model name assigned.
  • Material — this is a text field with the DuctMaterial model name assigned.

• A point feature class with the UndergroundConnectionPoint model name assigned — this feature class’s coordinates must include Z values. The UndergroundConnectionPoint feature class requires the following field:

  • ConduitObjectId — this is a long integer field with the ConduitIdentifier field model name assigned.

UFM Implementation

Customers may have implemented the UFM data model with Conduit Manager 10.x. To migrate this data, features in the Duct feature class (UFMDUCT class model name) need to be moved from their locations on UFMWall features to the edge of the UFMFloor features. This is required because the Editor XI data model doesn't contain UFMWall features. In the Editor XI data model, walls are modeled as the edges of Vault polygons. We recommend using the Create Duct Ends for UFM Ducts developer sample to help with this migration. To download this developer sample, refer to the Conduit Manager Data Migration 10.x to XI article on myArcFM.

Create Duct Ends for UFM Ducts Developer Sample

The Create Duct Ends for UFM Ducts developer sample, written for use in ArcMap, iterates over UFMWalls and ConduitSystem features related to the selected Underground Structures. The sample uses information from the ConduitSystem features and the UFMDucts on the UFMWalls to create three different types of features that are used to populate UN data in the Editor XI data model:

• One Duct Bank End point is created where the conduit intersects the boundary of the UFMWall and UFMFloor.

• One Duct End point feature is created for each UFMDuct on the UFMWall. The Duct End features are created on the boundary of the UFMWall and UFMFloor.

• One Underground Connection Point feature is created at the same location as each Duct end feature that is related to a cable.

It is implemented in ConduitDataConversionAddin.sln. The sample requires the following data configuration:

• A point feature class with the ManholeFeatureSnap model name assigned

• An edge feature class with the ULS model name assigned

• A polygon feature class with the UFMFloor model name assigned — we recommend adding the following field to this feature class:

  • ConvertedDate — this is a date field with the ConvertedDate field model name assigned. This field is used by the sample to track which walls have already been processed. The code checks this field before processing a wall to avoid creating duplicate DuctBankEnds, DuctEnds, and UndergroundConnectionPoints in the event that the user runs the tool on the same Underground Structure more than once.

The sample requires a dataset with Z coordinates defined containing DuctBankEnd, DuctEnd, and UndergroundConnectionPoint feature classes. It also requires:

• A point feature class with the DuctBankEnd model name assigned. This feature class’s coordinates must have Z values. The DuctBankEnd feature class requires the following field:

  • ConduitObjectID — this is a long integer field with the ConduitIdentifier field model name assigned.

• A point feature class with the DuctEnd model name assigned. This feature class’s coordinates must include Z values. The DuctEnd feature class requires the following fields:

  • ConduitObjectId — this is a long integer field with the ConduitIdentifier field model name assigned.

  • Diameter — this is a text field with the DuctSize model name assigned.

  • DuctCrossSectionShape — this is a short integer field with the DuctCrossSectionShape model name assigned.

  • DuctId — this is a text field with the DuctName model name assigned.

  • IsAvailable — this is a short integer field with the DuctAvailability model name assigned.

  • IsOccupied — this is a short integer field with the DuctOccupied model name assigned.

  • Material — this is a text field with the DuctMaterial model name assigned.

• A point feature class with the UndergroundConnectionPoint model name assigned — this feature class’s coordinates must include Z values. The UndergroundConnectionPoint feature class requires the following field:

  • ConduitObjectId — this is a long integer field with the ConduitIdentifier field model name assigned.

It may be helpful to visualize the UFM data model for Conduit Manager 10.x compared to the Editor XI data model for Conduit Manager. Below is an image of features representing the UFM data model for Conduit Manager 10.x.

Below is an image of features representing the Editor XI data model.

Below are tables mapping the 10.x feature classes and fields to their equivalent XI asset groups, asset types, and fields.

Note: Walls in the 10.x model are modeled in the XI as edges of vault polygons. You can calculate wallHeight from a UFMWall that’s connected to the UFMFloor.