Modify a subnetwork

A subnetwork represents a topological subpart within a tier where all the connected features are defined by the same subnetwork controller or controllers.

Modifications to a subnetwork include the following:

• Changing the name of the subnetwork
• Adding a new subnetwork controller to the subnetwork
• Removing an existing subnetwork controller from the subnetwork

To learn more, see Concepts and operations.

Change the name of a subnetwork

To change the name of a subnetwork, the Subnetwork Name must be updated on the subnetwork controller or controllers defining the subnetwork. The subnetwork is updated to apply the new name to connected features. To accomplish this, a network topology must be enabled.

1. Open the Subnetworks table and sort it by Subnetwork Name to identify all the subnetwork controllers associated with the subnetwork you want to modify.
2. Modify the Subnetwork Name for all associated subnetwork controllers in the Modify Subnetwork Controller pane.

   The subnetwork becomes dirty. In the Subnetworks table, this step sets the Is Deleted attribute to true for the row referencing the previous subnetwork name. A new row or rows are written for the renamed subnetwork controller or controllers.

3. Validate the network topology so it recognizes the changes.
4. Save your edits.
5. Update the subnetwork to reflect the new name on connected features. If trace configurations were specified for the subnetwork definition, or through the Update Subnetwork tool, only traversable connected features will receive the new name.
The name of the subnetwork is updated.

Add another subnetwork controller to a subnetwork

Additional subnetwork controllers can be added to subnetworks with a mesh or radial topology type.

The feature of the terminal selected to be a subnetwork controller must have an asset type with the Subnetwork controller network category assigned.

To perform the steps below, the network topology must be enabled.

1. Set a terminal on a feature as a subnetwork controller. Ensure the subnetwork name you provide matches the subnetwork it is being added to. This feature must be connected (or will be connected) to the subnetwork being modified for it to be associated with that subnetwork.
2. Validate the network topology to incorporate the change.
3. Save your edits.
4. Update the subnetwork to update the corresponding diagram (if one exists).
An additional subnetwork controller is added to the subnetwork.

Remove a subnetwork controller from a subnetwork

You can remove a subnetwork controller by deleting the subnetwork controller setting from the terminal set as a subnetwork controller and then exporting the information to remove the record from the Subnetworks table.

You can remove controllers from subnetworks as long as other controllers are still connected to the subnetwork. If they are not, an error is returned when the subnetwork is updated.

To perform the steps below, the network topology must be enabled.

1. Remove an upstream or downstream terminal from assignment as a subnetwork controller. To view all upstream or downstream terminals associated with a subnetwork controller, open the Subnetworks table and sort by Subnetwork Name.
2. Validate the network topology to incorporate the change.
3. Save your edits.
4. Update the subnetwork to update any corresponding diagrams.
5. Export the subnetwork with the Set export acknowledged check box checked to remove corresponding records.

   This removes the corresponding row in the Subnetworks table and the SubnetLine class and updates the corresponding diagram by removing the subnetwork controller.

The subnetwork controller is removed from the subnetwork.