A subnetwork represents a topological subpart 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, generate a feature in the SubnetLine class, and, if applicable, generate a subnetwork system diagram.
The following requirements must be met before you can create a subnetwork:
Create a subnetwork in the network
This is an overview of the workflow associated with creating a subnetwork.
- 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.
- Validate the network topology so it can identify the new subnetwork controller.
- 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 and a feature is created in the SubnetLine class. If a diagram template was specified when setting the subnetwork definition, a new subnetwork system diagram is generated.
A subnetwork is created.