Regardingh Combined domain network of Water and electric utility in a single Enterprise SQL database

[PragatiSingh]

we are moving to arcgis utility network for our electric and water geometric network data to Postgres enterprise database. How we separate the two domain networks within the postgres instance? Do we need to create separate databases within the instance

[RobertKrisher]

@PierreloupDucroix How would you configure the trace to stop at the first pole? Poles are part of the structure network, so they can't be used as barriers. I suppose you could trace to the first fitting or valve and see if it has a pole associated with it.

For performance purposes I would think carefully about whether I wanted to turn on the update structure/domain container during update subnetwork. Do you really want to put the system, pressure tier, etc from your water network on your poles? Not only is it of limited value, but it will also make update subnetwork take longer to run (since it has to update all the poles in the network).

[PierreloupDucroix]

Thank you for your advice; it was just an idea, as we're only in the pre-project phase.

I could configure the poles to only be part of the first tier to reduce update time. Another solution would be to use attribute rules instead, to retrieve the IDs of the nearest poles in the water network elements. In this case, there would be no requirement for a unified UN.

[RobertKrisher]

I like the idea of using Arcade to identify the nearest pole on-demand, you'll just need to make sure that your water editors have read-only access to the electric layers.

If you combine both networks, then editors will need to have full read/write access to both datasets, and both editors will need to be careful with how they edit data. You'll also get some annoying scenarios like removing a pole as part of an electric design will cause a conflict with a water version because the water user added an association to that pole to a feature in their version.

[PierreloupDucroix]

Having a shared infrastructure will certainly encourage these scenarios, just as they might occur in a telecommunications/electricity network for poles or trenches...

In my case, the same team will handle both water and electricity management, as it's a relatively small organization.