Subnetwork Management
Hi everyone,
I am currently in the early process of deleting and updating subnetworks in our utility network. When reviewing this documentation, I run into problems at the last step. Using the water system shown below, I have removed all subnetwork controllers. Then I validate the extent and get no errors and no dirty areas display within the error inspector. Then I update the subnetwork using the find subnetwork pane or geoprocessing tool successfully. When I run the export subnetwork too, the tier parameter says that there are no clean subnetworks discovered.
Can anyone give me some guidance on how to setup a system and pressure subnetwork on the below water system? Generally speaking, the pink line pumps water from a river to a treatment plant and the pumps to distribution. Does there need to be an asset that serves as a subnetwork controller at the beginning of the pink line to represent the supply (river)? If I set the pumps at the plant as subnetwork controllers for a pressure subnetwork, all assets are assigned to the system subnetwork. Wouldn't you think that everything after the pumps would be the pressure subnetwork?
Overall, what assets do you use as subnetwork controllers within a water utility network? For example, the esri default Naperville water data uses a water treatment plant as the controller for the system subnetwork. For us, the treatment plant is an area that contains several assets which could control a subnetwork. How do you handle wells that feed a treatment plant? What about bodies of water that serve as a source for a system?
I've gone through most of the content within this documentation, but have had a difficult time applying it to our utility network. Any help regarding subnetwork management would be greatly appreciated!
@shildebrand - I am not very experienced with water networks but I will try answering this from a Subnetwork Management lens.
Can anyone give me some guidance on how to setup a system and pressure subnetwork on the below water system? Generally speaking, the pink line pumps water from a river to a treatment plant and the pumps to distribution. Does there need to be an asset that serves as a subnetwork controller at the beginning of the pink line to represent the supply (river)? If I set the pumps at the plant as subnetwork controllers for a pressure subnetwork, all assets are assigned to the system subnetwork. Wouldn't you think that everything after the pumps would be the pressure subnetwork?
The water network is generally modelled as a Hierarchical Network so you can have a device that is part or more than one subnetwork from different tiers.
Every subnetwork needs a starting point which is the subnetwork controller. So yes, you would expect a subnetwork controller to be present at the start of the pink line.
I am currently in the early process of deleting and updating subnetworks in our utility network. When reviewing this documentation, I run into problems at the last step. Using the water system shown below, I have removed all subnetwork controllers. Then I validate the extent and get no errors and no dirty areas display within the error inspector. Then I update the subnetwork using the find subnetwork pane or geoprocessing tool successfully. When I run the export subnetwork too, the tier parameter says that there are no clean subnetworks discovered.
This would imply that there are no subnetworks to export.
Could you check the Subnetworks Table to see if there any records in there?
what Assets do you use as subnetwork controllers within a water utility network? For example, the esri default Naperville water data uses a water treatment plant as the controller for the system subnetwork. For us, the treatment plant is an area that contains several assets which could control a subnetwork. How do you handle wells that feed a treatment plant? What about bodies of water that serve as a source for a system?
This will vary based on organizational requirements. It will completely depend on how you decide to configure your Utility Network. Any device or JunctionObject can be set as a subnetwork controller.
If you have assets within the Treatment Plant, perhaps one of the valves or pumps could be a subnetwork controller.
Hope this helps.
Are you able to break your problem statement down into specifics scenarios and we can try working through that.
The behavior of not seeing returning dirty areas is expected.
Regarding the Subnetworks, it still a bit odd that your IsDirty flag is set to True.
I would suggest running the Update Subnetwork Tool again to see if that changes.
I reckon the Export Subnetwork Tool expects "Clean" subnetworks to be exported and that is where your issue is.
Below is an example from our Electrical Utility Network.
Before we start.
Step One - Modify Controller and remove subnetwork Controller (Don't delete the feature, I have seen that done before)
Step Two - Validate Topology. At This Point, IsDeleted = True and IsDirty = True
Step Three - Update Subnetwork using the geoprocessing tool. This will change the IsDirty = False and IsDeleted will remain True
Step Four - Use "Export Subnetwork" tool
This should remove the line from the Subnetworks Table.
Thank you for your help. Is is possible that the "Is Dirty" field is the same as the "Status" field? Regardless, both are set to true, so that probably isn't the issue. Below is a snip of what happens when trying to run the export subnetwork tool. Do you know if the entire utility network database (which includes multiple subnetworks that don't work or are useless to us) needs to be "clean"? Or does the subnetwork that you are attempting to delete just need to be "clean"? We will probably need to get some help from Esri technical support regarding this or from some other outside resource.
