topic Re: How to manage connectivity - Circuits in ArcGIS Utility Network Questions

How to manage connectivity - Circuits

Joshua_Moreno — Thu, 04 Dec 2025 20:00:57 GMT

We have a couple of pad mounted switch gears in which two circuits enter and exit. In my traces, I would want to show this separation, I ran a connected trace and it resulted in the opposite.

Below are screenshots as to what I want to be returned on the trace. From the circuit source, A5, I would want the trace to hit the switch and only select switches 3 and 1 in the diagram on the left. Entering from the circuit source at 3 and exiting at 1, going downstream to a transformer. Would this be fixed with terminals or is it a matter of how it is digitized/types of devices?

The switches are just cabinet buses connecting the switches/fuses within a fuse bank.

Re: How to manage connectivity - Circuits

MikeMillerGIS — Thu, 04 Dec 2025 20:08:45 GMT

Did you include the condition barrier to stop at open switches in your trace?

Re: How to manage connectivity - Circuits

Joshua_Moreno — Thu, 04 Dec 2025 20:21:57 GMT

Well, that was an easy fix that I completely overlooked. Thank you!

Re: How to manage connectivity - Circuits

gis_KIWI4 — Thu, 04 Dec 2025 20:26:35 GMT

Just to add to that - the basic connectivity trace picks all topologically connected network including open switches.

Re: How to manage connectivity - Circuits

Joshua_Moreno — Thu, 04 Dec 2025 21:04:12 GMT

Ahh gotcha, how can I see what the conditions or parameters of the out the box trace configurations are?

Re: How to manage connectivity - Circuits

gis_KIWI4 — Thu, 04 Dec 2025 21:41:31 GMT

The Connected Trace has no Condition Barriers by default this behavior is different when you select the downstream/upstream trace. When you select these traces the condition barriers are inherited from the subnetwork definition.

Connected Trace

Upstream/Downstream

Re: How to manage connectivity - Circuits

RobertKrisher — Fri, 05 Dec 2025 02:59:37 GMT

Also, the connectivity trace ignores terminal directions and subnetwork controllers.

Re: How to manage connectivity - Circuits

Joshua_Moreno — Fri, 05 Dec 2025 05:05:25 GMT

Hi Robert! A couple of questions regarding this, I'm trying to run a subnetwork trace but within this switch gear, switch 1 is connected from the circuit source of circuit 1 but switch 3 isn't connected from the circuit source just the switch itself but should be apart of the same circuit logically (which is what I want to achieve), thus it is getting selected as connected from the 2nd subnetwork that also runs into the switch. Would this be another trace barrier case or something else?

Lastly, I can't seem to populate the subnetwork name into my electric line features as I want to create subnet lines. I've set the circuit breaker as the subnetwork controller (line side terminal, unable to select bus side if that is what is needed?). And have also followed the proper steps of validating topology and updating subnetwork but it is not propagating the subnetwork name from the controller name into my electric lines.

Loaded questions but I do appreciate the help as always! Thank you!

Re: How to manage connectivity - Circuits

MikeMillerGIS — Fri, 05 Dec 2025 12:33:34 GMT

It is very hard to trouble shoot, could you provide a sample database that we could look at?

Do you have propagation set on the subnetwork? Did you set the propagated network attribute?

Re: How to manage connectivity - Circuits

RobertKrisher — Fri, 05 Dec 2025 20:38:26 GMT

@Joshua_Moreno if the subnetwork name isn't getting past the controller, then the phasing of your controller or lines are likely not populated or they don't match (i.e. your controller is C phase but the line is B phase). I agree with @MikeMillerGIS that without seeing your configuration with a small bit of data we can only guess about what is happening.

Re: How to manage connectivity - Circuits

Joshua_Moreno — Fri, 05 Dec 2025 21:16:20 GMT

Should I export my UN and delete data to provide a subset?

Re: How to manage connectivity - Circuits

Joshua_Moreno — Fri, 05 Dec 2025 22:12:37 GMT

What I just noticed is that the phase energized field is not staying as phases ABC and always reverting back to de-energized at the subnet controller/circuit breaker even when I save edits, validate topology, and update subnetwork. Once the subnetwork gets updated, it reverts back to de-energized. Can this be a cause of this issue?

Re: How to manage connectivity - Circuits

RobertKrisher — Sat, 06 Dec 2025 22:45:38 GMT

@Joshua_Moreno There are three fields that are configured when using propagation, and the phases energized field store the results of the phasing that was calculated by the system. Phases energized is a symptom of the problem; the cause is that the field used for E:Phases Propagated (phasechange) is not populated.

Here's a screenshot of the standard subnetwork definition for propagation:

Here's a screenshot of the network attribute assignment for E:Phases Propagated.

If you populate the phasechange field of all your features with the phasing value, instead of the phases energized field, then your subnetworks should start tracing. If you aren't 100% confident in your phasing, you may want to remove the propagators from your subnetwork so you can work through some of the simpler data issues first before you worry about having your phasing 100% accurate.

Re: How to manage connectivity - Circuits

Joshua_Moreno — Mon, 08 Dec 2025 17:07:36 GMT

Well, this was exactly my issue. Thank you for this information as I completely overlooked it.