Select to view content in your preferred language

Only the same number of water devices is getting selected each time i run the trace.

692
7
Jump to solution
04-15-2024 04:48 AM
Angiex__1
Occasional Contributor

I have created three subnetwork controllers, for the water system, pressure and for the isolation. No matter what i did the trace is only selecting 712 devices every time i run the trace.

scenario 1

Angiex__1_0-1713181600321.png

 

scenario 2

Angiex__1_1-1713181696976.png

 

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

A subnetwork trace for a pressure subnetwork should only include features that belong to that pressure zone, if it is including additional features than you have not correctly defined the subnetwork in your utility network or the data in the utility network is incorrect. If you haven't already, you should read the articles we wrote about modeling water subnetworks using the utility network, as they answer most of these questions and provide examples (for this thread, and several of the other threads of questions you have on here). The questions you just asked are part of the quality assurance process (article three below).

View solution in original post

0 Kudos
7 Replies
RobertKrisher
Esri Regular Contributor

If you are using the standard model, you likely either haven't populated any of the fields that are associated with the condition barriers in those tiers (valve status, CP Only, etc) or you haven't defined the rest of the subnetworks in your system. If you only create one pressure zone for your system, you should only expect to see one pressure zone for your system.

0 Kudos
Angiex__1
Occasional Contributor

@RobertKrisher So the valve status or the CP has to be populated after migrating from the GN? and I have created a subnetwork for system and pressure, where i kept system as a main subnetwork and the pressure tier is inside the system tier.

0 Kudos
RobertKrisher
Esri Regular Contributor

Because you only created a single pressure zone in the entire system then by your very definition all the features in the system must belong to that one pressure zone (although by your screenshot I can see there are quite a few features that don't belong to any subnetwork). The subnetwork will stop when it encounters a barrier (closed valve for pressure) or when it encounters another subnetwork controller.

0 Kudos
Angiex__1
Occasional Contributor

@RobertKrisher So by creating 3 or more pressure zones the trace picking up only a certain specific number of features can be minimized?

0 Kudos
RobertKrisher
Esri Regular Contributor

Define your pressure zones using the devices that regulate the pressure for those zones (typically pumps and pressure-reducing valves in a water distribution system) and you should have the correct number of features in each zone. You should check with an engineer or someone with an operational understanding of the specific system you are modeling if you are unsure you are seeing the correct results.

0 Kudos
Angiex__1
Occasional Contributor

@RobertKrisher what does a correct number of features in each zone mean? like should the trace only have to run inside the zone? I was given the GN data and asked to migrate to UN replicating the exact trace, that's where I am stuck in the tracing. In the UN it has subnetwork areas whereas in the GN I was given only two main sources and 6 other overhead sources.

0 Kudos
RobertKrisher
Esri Regular Contributor

A subnetwork trace for a pressure subnetwork should only include features that belong to that pressure zone, if it is including additional features than you have not correctly defined the subnetwork in your utility network or the data in the utility network is incorrect. If you haven't already, you should read the articles we wrote about modeling water subnetworks using the utility network, as they answer most of these questions and provide examples (for this thread, and several of the other threads of questions you have on here). The questions you just asked are part of the quality assurance process (article three below).

0 Kudos