Unusual Valve Configuration - How to Model for Subnets and tracing

JCGuarneri

We have a one-off situation at the boundary of two pressure zones in our system. There's a segment of pipe that apparently had a pretty shallow bury, and the solution to prevent freezing was a small bypass left open (see below). This allows a trickle flow of high pressure to come through from high pressure to low so the water is always moving and doesn't have a chance to freeze.

Right now, I just have the valve closed to allow the pressure subnetworks to work properly. Ideally, I would like to be able to meet the following criteria:

• Show valve as open
• Establish pressure zone change
• Return as a valve that needs to be closed on Isolation traces

Any suggestions for this? I know I could set a new class of subnetwork controller, but that seems heavy handed and I'm not sure if that would interfere with the isolation return. If only the engineers had spec'd a check valve...

 

 

 

 

RobertKrisher

Hmm, I don't see any great options for this other than what you're doing. 

The best idea I could come up with would be to assign a network category to let this be treated as a barrier on your pressure tier, but not on your system tier. This handles the inconsistent subnetwork name problem but means that your isolation trace will treat this like a closed valve if you do your isolation trace on your pressure tier. You could get the correct result if you ran your isolation trace against the system tier, but that will be slower than running a trace on your system tier since it must analyze more features and paths to sources (identifying all the possible paths to water sources, instead of just to the pressure controllers).