Latest Contributions by Jens_Dalsgaard

‎02-12-2024

For domestic PV production I would recommend maintaining such information in a separate customer / meter management system. And then, having service points and meter connections registered in UN, integrate the information from this third party system into GIS. This master data management approach removes double efforts managing this information in several systems. With such approach you may also benefit from other information from the third-party customer management / MDM system (meter type, consumption, planned replacement of meters, critical customers, ...)

‎01-18-2024

A quick question. I have a schema and a corresponding D_Configuration (XYZ) working as intended. Now I add e.g. an extra attribute (ABC) to one of the feature classes in the asset package template and migrate data thereto. What would happen if after adding this attribute ABC I apply the asset package with the D_Configuration XYZ without updating this D_Configuration with this new attribute ABC? Will attribute ABC be filtered out and not be applied to the utility network, or not? Best regards

‎12-11-2023

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.

‎11-21-2023

Nice with a workaround @CashEddy Still the ArcGIS Pro is a primary interface and should be improved on this topic.

‎11-15-2023

Thanks for the feedback. My intentions were backed.

‎11-15-2023

Reading here (https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/an-overview-of-attribute-domains.htm) it appears that the field to which a domain is assigned can be of many data types. So is it shear imagination when I believe I've Esri heard recommend using data type Integer to obtain best possible performance?

‎08-07-2023

Preparing for such 'condensed presentations of what we’re doing related to UN' it would be nice to have an indication of how much time we may expect available for such 🙂 So, once you know please update this post. Best regards Jens Dalsgaard / Volue

‎05-12-2023

Many of the double-feeding scenarios are in nature temporary and hence dealing with the requirements described above in a - let's call it - static way as suggested here doesn't seem right. Following dialogue at IMGIS and internal dialogue I think we're more inclined to creating custom functionality to support business needs here. But, thanks for the input, Mike.

‎05-11-2023

Allow me to refer you to a LinkedIn post that I made earlier: https://www.linkedin.com/posts/jensdalsgaard_dso-digitaltwin-gis-activity-7008701841232265216-rfSa?utm_source=share&utm_medium=member_desktop Scandinavian utilities have what many utilities out there are still working towards: A digital twin of the grid and and an implemented master data management strategy where grid documentation from ArcGIS Utility Network feed the ERP, the ADMS, grid calculations, etc. No duplicates. In the comments to the post I offer my input to a definition of digital twins in context of electric utility. Good luck with your thesis.

‎03-30-2023

During delta migrations we would like to disable editor tracking so that the fields from the source on who created / updated when may be written and persisted in UN. With editor tracking enabled, whatever we write will be immediately overwritten ty logged in user and date/time of write. Does anything prevent disabling editor tracking on a utility network dataset.

‎03-17-2023

Interesting. We have massive UN data in a very high quality working with e.g., Norway's largest electric utility. Being European based and hence working with three phase, balanced grids, some differences thus exist between these data sets I assume. Yet, learning from each other benefits all. Please allow me to link some LinkedIn posts I have made recently (my profile holds many more): https://www.linkedin.com/posts/jensdalsgaard_businessprocessautomation-dso-activity-7003639611885289473-UuIO?utm_source=share&utm_medium=member_android https://www.linkedin.com/posts/jensdalsgaard_arcgis-activity-7006184208238792704-gTXX?utm_source=share&utm_medium=member_android https://www.linkedin.com/posts/jensdalsgaard_dso-digitaltwin-gis-activity-7008701841232265216-rfSa?utm_source=share&utm_medium=member_android https://www.linkedin.com/posts/jensdalsgaard_arcgis-utilitynetwork-digitaltwin-activity-7011256984913985536-qDGY?utm_source=share&utm_medium=member_android https://www.linkedin.com/posts/jensdalsgaard_saas-dso-digitaltwin-activity-7013795739466113024-qJkS?utm_source=share&utm_medium=member_android Would like to learn some more about what you guys are doing / aiming at. Best regards Jens Dalsgaard

‎03-17-2023

Hi @RichardKoch I agree with the GIS not being and ADMS / OMS framework rather a repository for as-built grid documentation and normal switching position. Yet, offering a more flexible subnetwork mgmt approach of (erroneously) multi-fed parts of the grid would also support better debugging - where is the missing tie-point. I had brief talk with R Krisher yesterday, and based on this, I believe we will create functionality aiming at supporting the debugging of missing tie points. Because this is needed. Also, despite ADMS / OMS offering the live switching status handling (and more) I do see a potential for using GIS for handling live switching statuses of the extensive low-voltage grid as we see many utilities having their ADMS / OMS handle medium / high voltage only. For this we are looking into creating products delivering what subnetwork management functionality does not support.

‎03-13-2023

Utility Network supports subnetworks fed from multiple subnetwork controllers [SNC's] assuming these all have the same subnetwork name assigned. In case of multiple SNC's feeding the same area, features being part of such subnetwork will have an attribute listing all the SNC controller names feeding the area. Yet, if if more SNC's feed the same area, and these SNC's have differing subnetwork names the subnetwork (line feature) is not generated - and error is generated only. When this happens, a user will need to debug the cause. That is, most likely find the switching device that should have been opened to serve as a tie point. This task would be quite a lot easier, if the user had the subnetwork line feature to look at in the map. Assuming that ArcGIS does all the needed tracing to find the inconsistent SNC subnetwork names, it would be really nice, if UN actually returned the feature representing the illegal subnetwork line. Why not return a subnetwork line feature flagged as "Illegally fed from multiple SNC's with inconsistent subnetwork names." Such improvement would offer a lot of value also during daily operation. Esri tends to show examples where a portion of the grid is temporarily de-energized (opening a switching device) to then be energized again (closing another switching device (a in effect often feeding from other substation). That is not how any DSO would do. You would not de-energize the grid, rather feed it from both sides temporarily to then shortly after to open a switch to once again make feeding 'correct'. It would be very useful to show the temporarily multi-fed part of the grid in a special color making everyone aware that a temporary situation exists.

‎02-28-2023

OK, so even we wanted to add to parents we couldn't. well, that clears any concerns 😉 Not possible. Does that go for devices only?

‎02-28-2023

The assembly b is not optional. Yet, allowing ALSO associating device c directly to assembly a (whilst also associating device c to assembly b being associated to assembly a) serves a specific purpose. You're right - it is not really circular in nature; More parallel association chains. So Esri, would this be problematic?

Online Status	Offline
Date Last Visited	‎03-09-2026 11:50 AM

My Ideas

Latest Contributions by Jens_Dalsgaard

Re: Electric Utility Network - Domestic Solar PV System

D_Configuration and schema changes

Re: Inconsistent trace results

Re: Scroll bar on Network Properties in Utility Management Extenstion

Re: Does field type matter performance wise when assigning domains

Does field type matter performance wise when assigning domains

Re: UNC gathering in September

Re: Handling multi-fed subnetworks with differing Subnetwork names

Re: Utility network and Digital Twin

Disable Editor Tracking on a Utility Network

Re: Handling multi-fed subnetworks with differing Subnetwork names

Re: Handling multi-fed subnetworks with differing Subnetwork names

Handling multi-fed subnetworks with differing Subnetwork names

Re: Will circular associations be problematic?

Re: Will circular associations be problematic?

Re: How to use Error Inspector's Zoom To and Pan T...

Re: Electric Radial Partitioned Tier Source– Why A...

Re: Distance trace - how to?

Re: Choosing the right model for your stakeholders...

Re: Migration from Geometric to Utility network re...

European Utility Network Community (UNC)