topic Re: Isolation trace taking out entire subnetwork in ArcGIS Utility Network Questions

Isolation trace taking out entire subnetwork

SamDeLore — Sun, 22 Oct 2023 21:25:28 GMT

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

Re: Isolation trace taking out entire subnetwork

Cash_Eddy — Thu, 19 Oct 2023 14:20:20 GMT

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

Re: Isolation trace taking out entire subnetwork

RobertKrisher — Thu, 19 Oct 2023 14:47:19 GMT

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

Re: Isolation trace taking out entire subnetwork

MikeMillerGIS — Thu, 19 Oct 2023 17:57:04 GMT

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

Re: Isolation trace taking out entire subnetwork

SamDeLore — Fri, 20 Oct 2023 00:12:57 GMT

Hi Mike,

Yes, Source based.

Re: Isolation trace taking out entire subnetwork

SamDeLore — Fri, 20 Oct 2023 00:14:37 GMT

Hi Cash,

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

Re: Isolation trace taking out entire subnetwork

SamDeLore — Fri, 20 Oct 2023 00:15:33 GMT

Thanks @RobertKrisher,

We'll proceed to escalate the issue to support.

Re: Isolation trace taking out entire subnetwork

SamDeLore — Fri, 20 Oct 2023 03:48:56 GMT

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

Re: Isolation trace taking out entire subnetwork

SamDeLore — Wed, 18 Sep 2024 23:57:41 GMT

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

Re: Isolation trace taking out entire subnetwork

jtmathwig — Tue, 17 Dec 2024 14:56:30 GMT

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!

Re: Isolation trace taking out entire subnetwork

RobertKrisher — Tue, 17 Dec 2024 15:06:24 GMT

@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.

Re: Isolation trace taking out entire subnetwork

jtmathwig — Tue, 17 Dec 2024 15:14:16 GMT

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.

Re: Isolation trace taking out entire subnetwork

SamDeLore — Tue, 17 Dec 2024 21:28:48 GMT

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 ?

Re: Isolation trace taking out entire subnetwork

RobertKrisher — Wed, 18 Dec 2024 17:17:49 GMT

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.

Re: Isolation trace taking out entire subnetwork

Becky_Brown — Wed, 18 Dec 2024 22:03:04 GMT

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!

Re: Isolation trace taking out entire subnetwork

SamDeLore — Wed, 18 Dec 2024 22:27:30 GMT

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 😕