Isolation trace taking out entire subnetwork

[SamDeLore]

Hi all,

We've run into some strange results when performing isolation traces. 

A bit about our UN: 

• Water Utility (Hierarchical/Mesh/Source)
• UN 5, Pro 2.9.10, Enterprise 10.9.1 (latest patches)

The issue seems to trigger when a directional device within a loop is isolated by an Isolation trace. It looks like the system correctly recognises that the upstream of a device is without flow and therefore should extend the isolation downstream of that device. Now because the downstream has another path back to the controller, the isolation is reaching the controller and then taking out the entire supply zone (at least that's how I'm interpreting this result)

In reality, because the downstream side has another path back to the controller, flow should actually be able to reach the southern loop even with the isolation in place to the north. 

Things I've tried so far:

• Removing the directional device (Gives correct result)
• Making the directional device a controller (not a good solution and didn't work anyway)
• Deploying into enterprise 11.1 with a version 6 UN (Same issue)

CC: @RudyProsser 

[Cash_Eddy]

Hi Sam,

I looked at your data and noticed that there was not a Utility Network present with a network topology, only an asset package. Has the AP been applied to a staged UN?

Cash Eddy

Axim Geospatial LLC

[SamDeLore]

Hi Cash,

My bad, I've updated the attachment, a bit of late night asset package hackery going on..🙄

[RobertKrisher]

This is not the expected behavior; I'd recommend you work with support to log an issue for this.

[SamDeLore]

Thanks @RobertKrisher,

We'll proceed to escalate the issue to support.

[MikeMillerGIS]

Can you verify that you are using a source and not a sink based hierarchical network.

[SamDeLore]

Hi Mike,

Yes, Source based.

[SamDeLore]

Some additional information.

When run in ArcGIS Pro 2.9.1, 2.9.5 & 3.0.3 the trace works,

When run in 2.9.10 & 3.1.3 the issue above appears

[SamDeLore · Accepted solution]

Reviving this thread.

The original issue was solved with ArcGIS Server 10.9.1 Utility Network and Data Management Patch 6

• BUG-000162360 - Performing an isolation trace with a directional device near the isolated section returns incorrect trace results.

It appears this bug has been re-introduced at some stage, I'm working with Pro 3.3.1, Enterprise 11.3 & UN 7, below is a comparison of the same trace. The start point is after a non-return valve which is taking out the entire subnetwork in an isolation trace

The right is Pro 3.3.1 (UN originally created in 2.9.5), Enterprise 10.9.1 (patch 6 applied) & UN 5.

The left is Pro 3.3.1, Enterprise 11.3, UN 7

If I move the trace start point further downstream of the directional device with another isolating feature between the start point and the directional valve, the trace runs correctly

I'll raise through our local support in addition to this post but just wanted to share more broadly

[jtmathwig]

I'm not sure if my experience is exactly this issue, but it certainly seems similar with our Gas UN. We cannot figure out if there is a data issue, UN configuration issue, or an ESRI bug. 

Working with UN3 with Enterprise 10.8 in Pro 2.5 (but also with UN6 in Enterprise 11.1 and Pro 3.1.7), isolation traces would not select all required valves and take out large areas. In some cases, moving the start point (seemingly arbitrarily) down a line can return correct results, as Sam has noted above.

Additionally, tracing on the high-pressure side vs the low-pressure side of a regulator gives undesirable results in a system isolation trace. Putting a start point on the high-pressure side never identifies a downstream valve and either stops at the regulators (UN3) or takes out the entire network downstream (UN6). A trace on the low-pressure side seems to work fine.

Any further help is much appreciated!