Remove a subnetwork controller

There are cases in which the terminal on a device or junction object no longer needs to be set as a subnetwork controller. You can remove this assignment in the Modify Subnetwork Controller pane or through Python scripting. Additionally, if the asset group and asset type need to be retired from serving as subnetwork controllers, there are specific configuration steps to follow.

Requirement

An existing subnetwork controller is present.

Remove the subnetwork controller assignment using the Modify Subnetwork Controller pane

To remove the subnetwork controller assignment, complete the following steps:

1. Click the Utility Network tab.
2. In the Subnetwork group, click Modify Controller .
3. In the Modify Subnetwork Controller pane, choose one of the following to add a selected feature to the pane:
   • Click the Select a feature tool and select a feature on the map from the device feature class.
   • Click the Add Selected tool to add a selected row from the junction object or device attribute table.

   The Modify Subnetwork Controller pane is populated with the selected feature you want to remove as a subnetwork controller.

4. For the Terminal parameter, select the terminal from the drop-down menu to remove as a subnetwork controller.
5. Click the delete button next to the Terminal parameter.
6. Click Apply.

The terminal is removed as a subnetwork controller. Validate the network topology so this terminal is no longer treated as a subnetwork controller by analytic operations. Run the Update Subnetwork tool to update and remove the Subnetwork Name for features in the subnetwork. Export the subnetwork with the Set export acknowledged check box checked to remove the row in the Subnetworks table corresponding to the terminal. When working with an enterprise geodatabase, this must be performed against the default version.

Retire a subnetwork controller asset group and asset type

Subnetwork controllers are set on specific network features from an asset group and asset type that are considered valid to serve as controllers. When a decision is made to stop using certain features for subnetwork controllers in the network, there is a defined set of steps to follow. Since existing subnetwork controllers cannot be reclassified by editing the asset group and asset type attributes, these features must be removed as controllers in the network along with several configuration steps.

Complete the following steps to discontinue use of a specific type of subnetwork controller for a network:

1. Use the Modify Subnetwork Controller pane to remove the subnetwork controller.
2. Use the Set Subnetwork Definition tool to remove the asset group and asset type from the subnetwork definition as a valid subnetwork controller.
3. Use the Set Network Category tool to remove the Subnetwork Controller network category from the asset group and asset type.

   Note:

   This step requires steps 1 and 2 to be completed.

   The process of retiring the asset group and asset type from being a valid subnetwork controller is complete.

   If there is a transitional period in which not all controllers can be removed, you can perform step 2 to remove the asset group and asset type from the subnetwork definition as a valid subnetwork controller. This will allow remaining subnetwork controllers to function but prevent any new controllers from being set using the retired asset group and asset type. After all subnetwork controllers for the asset group and asset type are removed from the network, the final step of removing the Subnetwork Controller network category assignment can be completed.

Use Python scripting to remove the subnetwork controller assignment

Editors can use Python scripting to perform edit operations which include removing the subnetwork controller assignment from a device or junction object. To do this, you must first import arcpy and start an edit operation to run the DisableSubnetworkController function.