How to manage connectivity - Circuits

[Joshua_Moreno]

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.

[MikeMillerGIS · Accepted solution]

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

[Joshua_Moreno]

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

[gis_KIWI4]

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

[Joshua_Moreno]

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

[gis_KIWI4]

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

[RobertKrisher]

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

[Joshua_Moreno]

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!

[MikeMillerGIS]

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?

[RobertKrisher]

@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.