I asked our SMEs if they want anything from the EUNF v2.2 model renamed. They came back with a list of renaming almost every AG and AT. Will we regret that later? Does it make more work downstream and later in migration?
Solved! Go to Solution.
It makes your life easier to communicate with other utilities or contractors if everyone uses the same terminology, but every utility has unique naming standards. If you do need to rename things use the D_Rename table to manage the rename, so it handles updating all the rules and configuration. Read this blog if you are unfamiliar with this process. You'll still need to adjust any existing maps or applications you've configured that reference specific asset groups or asset types by name.
Once you've deployed a utility network you cannot rename asset groups or asset types, so if you've already deployed and want to make this change, you'll need to go back to an asset package and deploy a new database and services. For a list of what you can/cannot change, and when, refer to the Utility Network Management Tasks page of the online help.
It makes your life easier to communicate with other utilities or contractors if everyone uses the same terminology, but every utility has unique naming standards. If you do need to rename things use the D_Rename table to manage the rename, so it handles updating all the rules and configuration. Read this blog if you are unfamiliar with this process. You'll still need to adjust any existing maps or applications you've configured that reference specific asset groups or asset types by name.
Once you've deployed a utility network you cannot rename asset groups or asset types, so if you've already deployed and want to make this change, you'll need to go back to an asset package and deploy a new database and services. For a list of what you can/cannot change, and when, refer to the Utility Network Management Tasks page of the online help.
Something to keep in mind is when you change an Asset Group or an Asset Type in the EUNF model is there are downstream actions that you will need to take. Probably the largest of those tasks is updating the rules which can get overwhelming. Robert mentions using the rename table which is a good idea because then you don't need to make the downstream changes.
Don't be afraid to change the model, it is not one size fits all and is very flexible. Making the downstream changes can get overwhelming but it is a one-time effort - your users will be using the system for a while and having what they need will drive value beyond the time spent configuring.
If you use the D_Rename option in the Apply Asset Package, as Robert pointed out, you don't have to deal with updating the rules or subnetwork definition. The process takes care of all that for you. If you manually rename, then yes, you will have to deal with changing the rules, subnetwork definition, network categories, etc.