Question about B_Subnetwork* tables

[MobiusSnake]

Hi all,

I'm adding a few new types to an electrical UN, using the model in the Electric Utility Network Foundation as a starting point.  I want them to participate in connectivity traces, but I'd like to exclude them from upstream and downstream traces; although they'll be connected to features that are part of subnetworks, I don't need them to participate in the subnetwork.

I thought if I excluded these new types from the B_Subnetwork* tables, this would result in what I wanted.  Unfortunately running the Update Subnetwork tool on test data raised an error when it hit these new types.

Based on some testing, I think I can achieve what I want by adding these types to the B_Subnetwork* tables and using a network attribute or network category to exclude them from upstream/downstream traces, but I'd prefer to exclude them from my subnetworks entirely.  Is there a way to have these assets connected to my regular assets, having them participate in connectivity traces, while excluding them from the subnetworks?

Thanks!

[MikeMillerGIS · Accepted solution]

You could set them as barriers in the subnetwork trace and then select Do Not Include barriers.  But they will stop the trace, so if they are inline, they will stop the subnetwork from traversing through the item.  Also, if they have a terminal configuration, they will be returned regardless of include barriers.  I really do not think there is a way to achieve what you are looking for.

[BillBott]

Do you really need subnetworks?  Of course, without subnetworks you would lose the ability to run a subnetwork, upstream and downstream traces and many other features and characteristics of subnetworked features. However, these could be replicated by other means if you really wanted to. 

Guess it depends on how much work you wanted to do and/or the business value tradeoff. 🙂