Create a subnetwork

A subnetwork represents a topological subset within a tier where all the connected features are defined by the same subnetwork controllers. To create a subnetwork, a subnetwork controller is set, the network topology is validated, and the subnetwork is updated.

Subnetwork controllers allow you to specify the origin and name of a subnetwork. The network topology must be validated to incorporate new subnetwork controllers. The subnetwork must also be updated to apply the subnetwork name to any connected features, create a row in the Subnetworks table, and, if applicable, generate a feature in the SubnetLine class, and update a subnetwork system diagram.


The following requirements must be met before you can create a subnetwork:

  • The network topology must be enabled.
  • The name of the subnetwork must be unique in the utility network.
  • The name of the subnetwork controller must be unique in the tier.
  • The feature must meet the prerequisites to be set as a subnetwork controller.

Create a subnetwork in the network

This is an overview of the workflow associated with creating a subnetwork.

  1. Set a subnetwork controller by specifying a terminal as a subnetwork controller.

    A new row is written into the Subnetworks table and the Is Dirty attribute is marked as true to specify it is dirty.

  2. Validate the network topology so it can identify the new subnetwork controller.
  3. Update the subnetwork to refresh subnetwork information and generate any corresponding subnetwork system diagrams.

    The Is Dirty attribute is updated to false for the row in the Subnetworks table to specify that the subnetwork is clean, and a row is added in the SubnetLine class if the Aggregated Lines for SubnetLine Feature Class or Summaries parameter is configured in the Subnetwork Trace Configuration for the tier. If a diagram template was specified when setting the subnetwork definition, a new subnetwork system diagram is generated.

A subnetwork is created.