0016 Elements

0016 Elements

Migration Path

• PON_ELEM_TYPE_DEFS -> ElementType
• PON_ELEM_CAT_DEFS -> ElementCategory
• PON_ELEM_MAT_DEFS -> ElementMaterial
• PON_ELEM_DEFS -> Element
• PON_ELEMENT_CHILD -> ElementLink
• PARAMTRS -> ElementType, ElementCategory, ElementMaterial (Custom ancillary logic, see below)
• ASSET_ELEM_DEFS -> Element

Data Considerations

• Duplicates
  • PON_ELEM_DEFS_GD – duplicates not migrated
  • ASSET_ELEM_DEFS_GD – duplicates not migrated
• Null Data Replacement - See SQL
• NOTE: In BrM 7.x Element Type, Category and Material are required. If this data is NULL in BrM 6.x, it will default to a value of “Other” in BrM 7.x. If this is not your desired result, please make sure to clean up the NULL data in the BrM 6.x elements before migrating to BrM 7.x.

Other Notes

• The element migration migrates element data for Bridge, Tunnel, and Sign.
• Note that this is one of the more complex migrations for several reasons. All custom types, categories, and materials had to be migrated into BrM 7.x and duplicate names are not allowed. For non-bridge assets, the BrM 6.7.1 data model stored the type and category data as parameter data instead of lookup table values. This data had to be massage into a table called ASSET_ELEM_TYPE_DEFS in the TRANSFORMED database to assign IDs to be migrated to unique type-category pairs in BrM 7.x.
• Existing custom type, category, and material values were appended _x to ensure uniqueness of names during the migration.
• Remaining NULL name values were assigned the ID of the same row.
• There is custom logic for element tables that do not have the columns MODELING_ONLY or ACTIVE.