'Normally Open' Subnetwork Controller - Electric UN

[AndrewBerg1]

ArcGIS Enterprise 11.1, Pro 3.1.4, UN Version 6

We have a situation where a subnetwork (electric) can be backed from another substation. It is normally fed from a normally closed circuit breaker, and the other end of the subnetwork is connected to a normally open circuit breaker in a different substation. (see image)

The problem, though, is that if I configure the normally open circuit breaker as a subnetwork controller, it tries to push its subnetwork down the line and runs into the other (real) subnetwork causing it to throw an error, even though it is open.

We would like the normally open circuit breaker to be its own subnetwork so that it can be exported to an ADMS system. 

Thanks

[EstherSmith_Dev]

You can configure your tier definition to only allow "Normally Closed" device status to build the subnetwork, and anything else as subnetwork tier barrier. Then your backup CB 22 will stop rebuilding  subnetwork 11 as it becomes a barrier right at its downstream terminal. When you export subnetwork 22 for ADMS etc, the JSON will include only the CB 22 and nothing else.

[AndrewBerg1]

Is this all configured in the Set Subnetwork Definition GP tool? Do I uncheck the 'Include Barrier Features', as a "Normally Open" device is considered a barrier feature in our network?

 

[SahilBhouraskar]

-

[RobertKrisher]

Setting a condition barrier will not solve the problem because the subnetwork controller begins at the terminal, and unchecking the 'include barriers' will cause your tie switches to no longer be considered part of their network (which is bad).

The current workarounds for this issue are to either disconnect the line connected to the breaker or set the phasing of the device to be de-energized. If you log a case with support on this issue, they can get you attached to the bug/enhancement associated with this behavior.