topic Re: Inconsistent trace results in ArcGIS Utility Network Questions

Inconsistent trace results

Jens_Dalsgaard — Wed, 23 Nov 2022 14:53:49 GMT

I experience inexplicable and inconsistent downstream trace results. I have really tried myself understanding what is going on - I do not get it though.

From a high voltage substation (HV/MV) I set a trace start flag on the secondary winding on one of the transformers and request a downstream trace - se screen dump below:

As the trace is set to continue into low voltage (target tier), of course I would expect the trace to do so. In the below screen dump, you see that it does not continue into the low voltage mesh (blue lines):

And zooming into a medium voltage substation (MV/LV) it is clear that the trace stops at the MV/LV transformer - se screen shot below:

Really strange, cause I have successfully run an update subnetworks on the low voltage mesh, so I know that the trace from this transformer and downstream should work.

Now, moving the trace start point (from the HV/MV transformer secondary) to just outside this substation and running the exact same trace I reach this inconsistent result that you see below - the trace continuing through the MV/LV transformer and into the low voltage mesh as configured in the GP:

Enlighten me please, Esri (or someone else). I cannot see me doing anything wrong here - I might though. Or UN might have a bug?

One thing is for sure - you have a puzzled user.

Re: Inconsistent trace results

GIS_Solutions — Wed, 23 Nov 2022 16:49:25 GMT

Are you using the asset pack made by esri electric foundation?

Can you add a screenshot of the all tier and terminal configuration?

Re: Inconsistent trace results

Jens_Dalsgaard — Wed, 23 Nov 2022 19:07:40 GMT

We're using the UNC data model from the Utility Network Community. John Alsup / Mike Miller know it.

I will send information about tiers and terminals tomorrow.

Re: Inconsistent trace results

Jens_Dalsgaard — Thu, 24 Nov 2022 05:31:43 GMT

Please find the requested information enclosed.

Re: Inconsistent trace results

Jens_Dalsgaard — Thu, 24 Nov 2022 06:21:17 GMT

By the way - allow me to mention that performing a similar downstream trace from the HV/MV transformer in a migration from a different source using the exact same asset package template the trace propagates nicely into the low voltage mesh.

Hence, I doubt it has anything to do with the schema / data model configuration.

Re: Inconsistent trace results

MikeMillerGIS — Sat, 26 Nov 2022 11:45:19 GMT

Jens,

This appears to be BUG-000148077 - Downstream trace does not traverse all adjacent subnetworks across tiers.

Re: Inconsistent trace results

Jens_Dalsgaard — Sat, 26 Nov 2022 16:57:29 GMT

OK, thanks for the feedback, Mike.

Where may I read more on this bug, and what is the priority / time-frame on fixing it?

Re: Inconsistent trace results

MikeMillerGIS — Tue, 29 Nov 2022 11:59:39 GMT

It does not appear this bug is exported to the our web system. Best option would be to log a support incident and get yourself added to this issue. The more users affected increases it priority.

Re: Inconsistent trace results

Jens_Dalsgaard — Wed, 30 Nov 2022 10:16:52 GMT

Will do so through the Elvia Premium Support (as it is related to / documented on Elvia UN data).

Thanks for feedback, Mike.

Re: Inconsistent trace results

emin-saka — Mon, 27 Mar 2023 06:22:44 GMT

Hi, @Jens_Dalsgaard

I got the good news from the esri UN team. This bug (BUG-000148077) will be fixed in the next version 3.2

Thanks for your concern and support, @Remi_Myers

Re: Inconsistent trace results

emin-saka — Wed, 06 Dec 2023 10:12:59 GMT

Hi all,

I am happy to inform you that the BUG-000148077 was fixed with the new version of ArcGIS Enterprise/Pro (11.2 / ArcGIS Pro 3.2)

BUG-000148077 : "The downstream trace across tiers does not reach the target tier in some cases."

Re: Inconsistent trace results

Jens_Dalsgaard — Mon, 11 Dec 2023 12:22:55 GMT

Given the fact that the consolidation version for Utility Network is ArcGIS Pro 3.1 could you inform me please on when we may expect a 3.1 patch with this fix.