Essentials to Expanded Model

[Joshua_Moreno]

I have started digitizing data from scratch based on circuit maps into the Essentials Model but after many discussions with our Electrical team, it seems that the Expanded model is what we will need to use. How would I go about migrating the data from the essentials model asset package to the expanded model asset package? Data Loading tools, migration workspace?

Anything I have to know before doing so? Will be using the configurations table to edit the expanded model to only keep distribution and rename/remove certain items we don't need.

Thank you!

[RobertKrisher]

The essentials data model is designed to be able to import configuration from the expanded model (using the tools outlined in this article). Depending on your needs, you may be able to just import the things you need instead of needing to re-migrate your data.

If you do need to migrate your data, you can either use the data loading tools directly or use the Create Simple Data Mapping / Create Migration Workspace tools to help set up the mappings for you.

[Joshua_Moreno]

Hi Robert, the link to the article for importing configuration from expanded to essentials seems to be a calculation question on how to update via related tables. May have been an incorrect link? If you can send the correct one, that would be greatly appreciated!

I think  this workflow may be best for our use case. Thank you!

[RobertKrisher]

Oops! Too many links! The tools in question are the Create and Apply Network Copy workbook from the Utility Data Management Support toolbox. This is the link to the article that describes them. I'll also update the link in the original post for posterity.

[Joshua_Moreno]

Awesome, thank you so much! I did find the Transfer Utility Network Data that allows for the merging of data from an asset package to another asset package within the Utility Data Management Tools 3.5. Do you know what this would essentially do? It only provides two parameters for the source and target asset packages and no mapping.

[RobertKrisher]

@Joshua_Moreno that tool is designed to merge two asset packages with the exact same schema into a single asset package.

[Joshua_Moreno]

Hi Robert, how would I use the data loading tools directly to migrate my current data in the essentials asset package to the expanded? I tried using the simple data mapping and migration workspace but kept getting errors regarding the need of additional information for my schema but if I do add the subtypes to the target subtype it then populates that asset group to only have the subtype I provide. Unless I am missing something where I can accurately choose or map the subtypes - example: my essentials model has single and three phase transformers and I am mapping that to the medium voltage transformer in the expanded but for the subtype I only have the option to select one subtype (asset type) and when I tried loading it, it populates the selected subtype to all my transformers.

[RobertKrisher]

In the simple data mapping spreadsheet, you need to create separate mappings for each of the asset groups and asset types in your model. This will allow you to properly identify (through a definition query) each asset type in your source model and map it to its corresponding asset type in the target model.

[Joshua_Moreno]

Hi Robert, when running the create simple data mapping tool this is my result in the Data Mappings sheet. Are you saying to add asset types to this from source to target? 

[RobertKrisher · Accepted solution]

Instead of using the asset group field to create the definition queries for your mappings, use the asset type field. You will find it much easier to do your mappings this way.