Reservoir as Subnetwork Controller in Water Pressure and System Tiers?

[PeterKing]

As we move through setting up each of our pressure zones in the UN v.7, we have determined that there is a pressure zone which is fed directly from a Reservoir. It appears that Storage/Reservoir is not a valid Subnetwork controller for the System or Pressure Tier.

I would like to ask if there are any considerations or drawbacks to adding Storage/Reservoir as a valid device on the Pressure and System Tiers using the Set Subnetwork Definition tool.

Thanks!

[RobertKrisher · Accepted solution]

A feature can only be a subnetwork controller for a single tier, so if you make it a controller for the pressure tier then it won't be considered as a source of water if you run a trace on the system tier.

[PeterKing]

Thanks for your reply Robert!

Is there a reason that Reservoirs were omitted as valid Subnetwork Controllers for the Pressure or System Tiers in the UN model? 

[PierreloupDucroix]

You van add reservoir as a valid subnet controller for system / pressure but as soon as you modify a reservoir to turn it into a controller for a pressure subnet you won't be able to use it for another tier.

What we did is we added a new assetgroup and assettype in the the waterJunctionObject table and parameter it so it can be included in a reservoir and can be controller for the system tier.

This way the "system object" controls this syryem tier and the reservoir can still control another tier

[RobertKrisher]

Intakes are configured to be able to be used as subnetwork controllers in the system tier of the model, they just aren't configured to be controllers of the pressure tier of the model. For the reasons that Pierreloup and myself listed.