Utility Network Foundation Roadmap

802
4
Jump to solution
07-04-2019 05:09 AM
AnthonyRyanEQL
Occasional Contributor III

Is there any documentation/diagram on the roadmap for the utility network foundation? The reason for asking is - there was significant changes to structure/container down to AT, new related tables for crossarms, etc.

i can see some more significant changes to these related tables in the future to make them more useful (eg. Further normalisation, completing capabilities - adding ElectricLine/Crossarm relationship) and also to see what new capability to strip out to make the model less complicated (eg. Remove cablemountdetail table, remove phasesummer, phasewinter, etc.)

thanks

0 Kudos
1 Solution

Accepted Solutions
MikeMillerGIS
Esri Regular Contributor

Great questions. The next few releases are focusing on the following

1:  Extending the sample data to include subnetworks for all tiers and feeder feed feeders in the distribution tier.  This will help us round out the rules and ensure we have the categories and other properties set appropriately.

2:  Providing the ability to rename key components.  We are close to finishing a new exciting capability in the asset package to rename items during application.  This could be to simply rename an asset group to a new asset group and all UN properties are shifted to the new name or provide a localization like experience where the model can be converted to another language.

3:  Allow deploying a subset of the asset package.  The first release will be focused on reducing fields, code values in domains and a few other things, but we want to keep extending it to provide the ability to remove Asset Groups someday.  

4:  Adding new tables and classes for inspections and other activities.  

5:  Adding to the list of workflows.  

We do not plan to change the Asset Group and Asset Types like with did in version 3, but there will be changes as we keep driving the model and gathering feedback from the community.

Thank you for your feedback so far and please keep sharing it with us.

View solution in original post

4 Replies
MikeMillerGIS
Esri Regular Contributor

Great questions. The next few releases are focusing on the following

1:  Extending the sample data to include subnetworks for all tiers and feeder feed feeders in the distribution tier.  This will help us round out the rules and ensure we have the categories and other properties set appropriately.

2:  Providing the ability to rename key components.  We are close to finishing a new exciting capability in the asset package to rename items during application.  This could be to simply rename an asset group to a new asset group and all UN properties are shifted to the new name or provide a localization like experience where the model can be converted to another language.

3:  Allow deploying a subset of the asset package.  The first release will be focused on reducing fields, code values in domains and a few other things, but we want to keep extending it to provide the ability to remove Asset Groups someday.  

4:  Adding new tables and classes for inspections and other activities.  

5:  Adding to the list of workflows.  

We do not plan to change the Asset Group and Asset Types like with did in version 3, but there will be changes as we keep driving the model and gathering feedback from the community.

Thank you for your feedback so far and please keep sharing it with us.

AnthonyRyanEQL
Occasional Contributor III

Michael,

Excellent news on the enhancements.

Are you able to elaborate on Item 1? Trying to understanding if there are any implications if an utility decides to implement their own asset group/asset type configuration. I’m not familiar with the concept of ‘feeder feed feeders’ in the distribution tier.

Also,

Item 4 - Additional tables/classes for inspections, etc. I assume this will be similar to the WireData, etc. and can be implemented whenever the utility decides as its not truely part of the UNF.

Thanks

0 Kudos
MikeMillerGIS
Esri Regular Contributor

Just keep track of your additions. Also, you do not have to update once you settle on a starting point. You can extend your version with our changes if you need them. The models are going to change just like software does and as the software it sits on top of does.

Feeder feed feeder: This would be using a step down transformer as controller for a subnetwork.

Correct on item 4

AnthonyRyanEQL
Occasional Contributor III

Thanks again

0 Kudos