Asset Type unavailable in Set Subnetwork Definition Tool

[Yeaton]

Hello,  

I am configuring a sewer utility network foundation essentials model.  I successfully completed the data migration but need to augment the model with a "Connections" asset group as is available in the expanded version of the sewer UN.  So, I added a connection asset-type within the sewer device asset group and added connectivity rules, which all went well.  I believe the next step is to include the new asset type as a valid device in using the "Set Subnetwork Definition" tool.  Unfortunately this new asset type isn't available in the tool's drop down menu. Are there additional steps to incorporate this new asset type into the UN schema that i missed?

[VenkataKondepati]

Yes. There’s one extra step.

Asset types only appear in Set Subnetwork Definition if they’re assigned the correct network category. Adding the asset type and connectivity rules isn’t enough.

You can try below.

1. Assign the same network category used by existing subnetwork devices to your new asset type.

2. Run Validate Network Topology.

3. Reopen Set Subnetwork Definition.

Subnetworks are driven by network categories, not just asset groups/types.

[Yeaton]

Thanks VenkatKondepati!

Best Regards,

Aaron Y.

[RobertKrisher · Accepted solution]

The only time a network category is required for an asset type to show up in Set Subnetwork Definition is when you want to make something a subnetwork controller (in which case there are several criteria).

Adding an asset type and setting the subnetwork definition both require the network topology to be disabled, so you do not need to validate the network topology for the new asset type to appear. You can find more information about these kinds of constraints on the Utility network management tasks page.

The most likely issue was that the tool hadn't refreshed. If you closed and reopened the tool you should have seen the new asset type (if you were running against SDE). If you were running against a service then you would have had schema locking turned off, which means in order to see any schema changes you would have needed to restart the service.