Using Export Asset Package after first successful Utility Network

BrandoCrozier

We have created our first successful iteration of a Utility Network for an Electric Utility using an existing Asset Package. This is our first iteration; only one Subnetwork (circuit). Our plan is to do new iterations with more subnetworks. We had to add a bunch of rules, Asset Types, and even one Subnetwork Controller type to the Asset Package. As we prepare for the next iteration we want to avoid redoing that work.

Should we use the Export Asset Package tool, take that Asset Package, then start our next iteration that will include the successful subnetwork and our next subnetwork on our list?

If not, can you please explain why this is a bad idea. Or, suggest another way to avoid re-adding all the information into the original Asset Package with each iteration?

GIS_kiwi4

@BrandoCrozier - Exporting the Asset Package from your working UN and using that as the baseline is not only valid but is recommended. There are many advantages to doing this - additive changes, Asset package version management etc. 

Just make sure to select the "include data" option when exporting the asset package. 

 

Load Data when applying the asset package.

 

Edit - Upon reading your question clearly I see that you are wanting to add AssetTypes and Rules. 
I would like to point out these can be added to existing UN without exporting to Asset Package.
for example adding an AssetType is adding a new coded value to the field and then optionally adding connectivity rules.

In fact, most changes can be made directly to the UN apart from a few operations like Removing Terminals. 

But a good practice when it comes to development work is to Export to Asset Package -> make Changes ->Apply Asset Package.