Modelling one way check valves along subnetwork boundaries in water network

[KJ_GIS]

ERROR 001890: Invalid subnetwork connectivity, multiple subnetwork controllers with different subnetwork names found.

Hi, I'm looking for best practices on handling check valves along pressure zone boundaries.  These check valves are flow valves with terminal connections defined.  I'm receiving above error because a subnetwork controller with a different subnetwork name is reachable from an adjacent subnetwork controller, via a one-way check valve along the pressure zone boundary.  I was able to set the pink subnetwork below by changing the check valve's normal status to closed, but probably not ideal?  I've got a lot of these situations so looking for the best way to handle. 

in the picture above the red arrow is the controller for the pink subnetwork and the blue arrow is one of the controllers of the blue subnetwork.   

Thank you,

[MikeMillerGIS · Accepted solution]

I assume not all check valves are pressure zone boundaries?  You might have to set up a Network Attribute or a new type of Asset Type that is PZ Boundary Check Valve and use that as a condition barrier for the PZ's.

[KJ_GIS]

Hi Mike, thanks for the advice.  I went with your suggestion of setting up a new asset type for PZB Check Valve since yeah, not all the check valves are at pressure zone boundaries.   Seems to be working for updating subnetworks.   Thank you.