Hierarchical Water Subnetwork

[AmberY]

Hi, 

We were in the midst of building subnetwork and understand that "Hierarchical networks only allow features to belong to more than one subnetwork as long as those networks belong to different tiers".

But during the process of building subnetwork, it turns out that the asset of water line is belong to more than one subnetwork. Is this a glitch or if there is something we didnt aware of? 

Run subnetwork tracing of this system subnetwork A, B, C, D respectively all return the same coverage area. 

Appreciate all the thoughts. Thanks so much!

[RobertKrisher]

There are a few edge cases to this rule. Firstly, a feature can belong to many subnetworks without an error if the feature acts as a barrier between multiple subnetworks. Think of a closed valve between two pressure zones.

Another less common situation is when a feature is in an area fed by two different subnetworks, but the subnetwork controllers themselves aren't connected. This can happen if you have something like a pressure zone that is fed by different water systems, but the valves in the area prevent water from one system from entering the other system.

From the screenshot it looks like you are not using one of the utility network foundations, so it's for me to speculate what could be going on in your situation since I don't know how your data is configured.

[AmberY]

Hello @RobertKrisher ,

The Water System Tier is configured with these parameters.

And we have only build system subnetwork for now and have little clue on why the subnetwork behave these way. As in some region, the subnetwork is overlapping but in other region, the subnetwork hit error 29 for overlapping. 

First case seem not applicable to our case as i can see that the water line and other non-barrier feature are belong to 5 system subnetwork even it is not a barrier. For case two, I am not sure how to verify if this is the case, appreciate if you could share some thoughts on this. For context, we only performed "Assign Terminal Connections" for terminal devices and directly build the subnetwork due to certain reason.

Thanks so much!