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 

[RobertKrisher]

@jtmathwig You should contact support for those issues. There is at least one known bug with isolation traces where placing the start location and barrier on the same line, which can produce incorrect results.

[jtmathwig]

We do have an open case, so hopefully we can get some traction soon. It's just been quite a headache for our emergency shutdown tracing, etc. as we try to figure this out!

Thank you.

[SamDeLore]

Hi @jtmathwig ,

It does sound like you're experiencing similar issues. The common denominators in my experience are isolating directional devices & loops in the network, which are pretty common in pressure networks.

We are subscribed to BUG-000170999 that was updated on 9/26/2024 to "In Product Plan", so fingers crossed there's a patch coming soon.

@RobertKrisher do you know when we might see a UN patch for 11.3 ?

[RobertKrisher]

Not off the top of my head, although since you're working in an Enterprise environment what you're really hoping for is an 11.3 patch. Reach out to your account manager about this issue and they should be able to go through proper channels to come up with an estimated window.

[Becky_Brown]

We are seeing the same problem as @SamDeLore in our environment: Enterprise 11.1 / UN v6 / ArcGIS Pro 3.4 (also 3.1.7 and 3.3.2). The first two images show the starting point south of a System Meter and two PRVs. The isolation trace results take out a large portion of our northeastern service area.

The next two images show the isolation trace run with the starting point north of the System Meter and PRVs. The trace results are correct here. 

There are several areas in they system that are responding this way. We've verified the Is Connected field, Lifecycle Statuses, also disconnected and reconnected the assets, and ran Update Subnetwork. This workflow has been repeated ad nauseam with the same results. 

The Esri technical consultant I'm working with on the tracing pointed me to this blog. It appears that the original bug has crept back into the newer versions. Additionally, I tried to find BUG-000162360 to subscribe to it for updates but cannot find it as someone else mentioned. Does anyone have a direct link?

Any help is appreciated! 

[SamDeLore]

Hi @Becky_Brown ,

We're tracking this issue against BUG-000170999, I don't have a link to anything though sorry, it's all contained to our MyEsri page. Here's a screenshot of the detail, note the workaround isn't really a workaround 😕