How does Utility Network Management handle existing associations when editing network data?

JürgenBiendara

Hello,

I am trying to figure out how Utility Network Management handles existing associations when editing network data, especially when splitting associated objects. Please see the following example based on Electric Foundation V2 Solution:

A cable is associated with three conduits (Image 1). The cable is split in two places, which automatically adjusts the associations.

• After the first split: Image 2
• After the second split: Image 3

The new containment associations seem to be computed due to geometric intersections, among other things. I have the following questions about this:

• How does the Utility Network determine the adjusted associations after each of the two splits.
• Which parameters have influence on it and (how) can these parameters be influenced?
• Is it possible to configure the Utility Network in such a way that when a device is placed on a cable, the cable is automatically split at this position?
• Does a more detailed documentation exist on this topic, describing (besides containment associations) the effects on other association types?

Many thanks for the help.
Jürgen

Image 3.jpg

Image 2.jpg

Image 1.jpg

settings.required.txt.zip

linuxDS.png

Clip_1262.jpg

Screenshot 2024-08-20 at 7.13.39 AM.png

SHAFAA Logo SQ.jpeg

KoryKramer_0-1724163049638.png

JohnAlsup

Hi Jurgen.  In the Utility Network Foundation, by default we set all split policy's to the Utility Network default setting, which is DO_NOT_SPLIT.  DO_NOT_SPLIT has the following behaviour: The container's content will not be split if the container feature is split. If a parallel content line feature is found, the content will be contained by both sections of the container feature. If the content line is not parallel, the content will be contained by the container feature that is closest to it. This is the default.

You can change the split policy by running the SetAssociationRole gp tool and changing the split policy the the specific asset type.  This will require the UN network topology to be disabled.  You can also change it in the Asset Package before apply by editing the table B_ASSOCIATIONROLE, changing the splitpolicy column for the desired asset types.