Latest Contributions by DamienPyne

‎02-23-2026

I had to go digging to confirm. Yes we have eventing off. This was not an option with UNM v3 which is where we started. Its one of those options and enhancements we did not go to when we uplifted to v6.

‎02-22-2026

I guess its similar to a load shift. You have subnetwork 1 and subnetwork 2. To update the changes of the shift where SN1 is now part of the old SN1, you need to update both SN1 and SN2. If you only update SN2, then there is a section not yet updated. Same theory here. You have a section of network not part of that update (ie your deenergised features), and the IsConnected will clear the SN value and flag these as isconnected = False. Ie they are isolated network objects.

‎02-19-2026

We have seen this, and raised to Esri. We had been advised this is "as expected". Our workflow advises the user to use the subnetwork line to review for the update. You should see these features IsConnected value updated, and when you run IsConnected the subnetwork should then update to unknown.

‎02-05-2026

We came from 2 different companies with 2 different levels of granularity and maturity. One with minimal detail (a line for the conduit, and arrangement but not maintained, and missing relationships from the conduit to the trench and to the cable), and the other with a rich dataset of maintained cross section detail. We also took advantage to 3D enable our utility network. Our end state is the trench modelled at z=0, and conduits and cables at depth (assumed at standard depths for migration, continual improvement through integrated design to correct over time). For the source data with minimal associations we utilised the unknown conduit as a holding feature. It seems like a similar model to what @PierreloupDucroix mentioned.

‎01-27-2026

When we developed our model we had a deep conversation with our Esri rep about this. We also have a very granular Low Voltage model in our network , adding additional asset types to this scenario. Based on this we created a virtual object called "Feeder Start Point". Outside of a distribution transformer, these are our only subnetwork controllers. This allowed and overcame the issue or directional and non-directional/bi-directional breakers, etc.

‎03-23-2025

The summary tool for Pro 3.1 does not remove duplicates data correctly and therefore is reporting a count higher that the total errors in the database. Refer Reporting topology errors - Esri Community At the moment this is not an option while we are using pro3.1. If/when we upgrade to 3.3 or 3.5 (this is probably our target) this tool would be an option.

‎03-20-2025

Thanks, that looks like a useful approach. In terms of migration, I have a foot in each camp. We had previously gone live with un3 on 10.8.1 but due to other factors we are doing a new migration to 11.1 un6. For migration I have all the tooling in the database, but also looking to the future post new go live of how a general user can filter and search for targeted errors where they will only have Pro. Let me take your suggestion to one of the team and confirm this will work and provide the requested approach.

‎03-20-2025

Thanks David. I'm really chasing where there can be >1 error type. Something like E25 and E9 both present (but i dont know what is there I just want all the errors of each type that I can filter to). So E25 = 2 power 25 + E9 = 2 power 9 = 33,554,432 + 512 = 33,554,944 Where there is only one error present its fine. Any ideas?

‎03-20-2025

With the topology errors being stored as bitwise values in the dirty areas layer, how can I filter to just specific errors? This needs to be in ArcGIS Pro. For the migration of our data I can report from a database level, but for the general users who will not have database access (and in our production environments we have heavily restricted database access) they need to be able to find through Pro. I did try building some definition queries on the DAs layer, but this only works were there is a single error. For example with Error 25, this works fine for E25. ERRORTYPE = POWER(CAST(2 AS BIGINT),25) How do users filter to specific errors when bitwise is not supported in def queries? We are currently using Ent11.1, ArcGIS Pro 3.1, UNv6.

‎03-12-2025

@MikeMillerGIS yes looks like its better in 3.3. Is that something you are looking to correct for 3.1?

‎03-12-2025

I will let you know when I have some 3.3 with the tool. This is the quick def query view of the data. I am expecting about 8000 errors so hopefully 3.3 provides an aligned output.

‎03-12-2025

Possible to share let me get back to you, and yes I can hook up a 3.3 with the tool and review.

‎03-12-2025

Thanks Mike, but what about specific examples like E29 where this should not have 2 feature classes driving the results and therefore increasing the number? And the fact this particular error is showing 25K errors while the network property value is 11K in total for points or 15K in total for all errors? This is an important item as for this error type has never been high (under 1000 on our original go live on UNv3) and is now significantly higher (25K). I am trying to determine the correct reporting and focus of the issue.

‎03-11-2025

Hi I'm hoping @MikeMillerGIS you can assist here in understanding the output from the "Summerize Utility Network Errors Tool" within UtilityDataManagementSupport toolbox, vs looking at the errors themselves. At the moment our migration partner is using your tool for reporting which is creating some concerns about volumes. I have downloaded the toolbox from GitHub - Esri/Utility-Data-Management-Support-Tools at 3.1, but I dont see aligned numbers. We are in the middle of a remigration of data (long story not worth the discussion) and when I use the toolbox for topology error counts there are ~25K errors for Error29 alone reported (item1) but in the network properties there is only ~11K point errors in total (item2), and using SQL at the database supports the network properties, and specifically for error29 only reports 7,904 errors (item3). Can you please assist in understanding why there are such large numbers reported in the toolbox report. Thanks Damien

‎02-27-2025

Hi Dani We created our own data model with one structure network, and an electric and communication domain network. Our comms is just the bearer network (not all the individual fibres). We have had no issues with both electric and communication equipment on the same poles, or in the same trench and conduit systems. Damien

Online Status	Offline
Date Last Visited	‎03-22-2026 01:43 PM

My Ideas

Latest Contributions by DamienPyne

Re: Update subnetwork and de-energized equipment

Re: Update subnetwork and de-energized equipment

Re: Update subnetwork and de-energized equipment

Re: Conduit Configuration vs Circuit/Feeder Maps

Re: Circuit Breaker - Subnetwork Controller vs Non-Subnetwork Controller

Re: Displaying and filtering topology error codes in ArcGIS Pro

Re: Displaying and filtering topology error codes in ArcGIS Pro

Re: Displaying and filtering topology error codes in ArcGIS Pro

Displaying and filtering topology error codes in ArcGIS Pro

Re: Reporting topology errors

Re: Reporting topology errors

Re: Reporting topology errors

Re: Reporting topology errors

Reporting topology errors

Re: Comms Utility Network with Electric UN

Re: Update subnetwork and de-energized equipment

Re: Conduit Configuration vs Circuit/Feeder Maps

Re: Circuit Breaker - Subnetwork Controller vs Non...

Re: Comms Utility Network with Electric UN

Re: Contingent values changes the subtype selected

APAC Utilities Community of Practice