Legacy UN data migration workflows

[Adam_CanopyMapping]

Hey there everyone,

My company is in the process of training me to understand UN and the migration of Geographic Network data to the UN standard. I was hoping to hear from others who have done similar work. I'm just trying to imagine the possible time frame, scope of work and the general workflow of the process. 

Additionally can the migration process be streamlined with model builder, python or similar tools?

[PatrickGCowan · Accepted solution]

There is a new migration tutorial that has been released that walks through a migration using some new tooling. The tutorial is based off migrating from a known model (GN based) to the essentials model. The tutorial for the Sewer industry has been released. Other industries will follow, but they will all use the same workflow, so the concepts are the same.

Sewer migration tutorial: Sewer Data Migration Tutorial 

Over the past year a lot of work has been put into new tools to make the migration process easier, and these tutorials go through using these new tools.

[gis_KIWI4]

@Adam_CanopyMapping  - There are many ways of migrating to the UN and multiple tools you could use.
The way I think about this is the end goal is to accommodate your GN data into the UN framework (schema and rules). 

The process is broadly broken into 2 pieces - Configuring the UN and Loading the Data

GN has no limitation on the number of feature classes whereas UN expects you to fit your data in predefined feature classes (Electric Line, Device, Etc). So in the GN you may have had different layers for Transformers, Fuses, Switches but in UN they will need to sit under Electric Device Layer. 

UN also builds up on the GN by providing additional capability like associations, subnetworks, connectivity rules just to name a few and these things need to set up according to your business requirements.

Some of the common migration patterns you will see around the industry are - 

1) Use the foundational Model and follow the migration tutorials. You will create create an asset package and then stage the utility network (Data Loading Tools include customized spreadsheets and geoprocessing tools). The have different versions of the Foundational Model including an essentials model. 
https://www.esri.com/arcgis-blog/products/arcgis-solutions/data-management/arcgis-solutions-introduc...

2) Creating your own Utility Network. A step by step guide here - https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/configure-a-utility-network.htm At the end of this process you will end up with mobile geodatabase with a fully configured Utility Network. You can the create mappings between GN and UN to load data. (We did this because we though the foundational model was overkill for what we were trying to achieve. We also used FME to do all the data loading) 

3) If it works for your business needs, the easiest option is to grab a Utility Network/Asset Package from a peer utility that have already done the hard work and load your data into it. Appreciate that all utilities are different but it won't hurt to explore this option.

A few pointers from our migration journey - 

Understand the fundamental of UN (schema, rules, functionality). That will build the foundation for your journey. 

Keep things simple when you start building out the UN

Reach out to this awesome community for any help

[RobertKrisher]

There is a dedicated learning series to migrating data to the utility network that includes links to many articles, tutorials, videos, and other important information that can help you on your learning journey. And I strongly second what @gis_KIWI4 said, reach out to this community whenever you have questions.