Skip To Content

Update subnetworks

Subnetworks are updated to ensure attributes, features, and connectivity are current and valid in a network. Updating a subnetwork also exposes inconsistences in a subnetwork, such as invalid features, disjointed or inconsistent subnetworks, and incorrect numbers of subnetwork controllers. The Update Subnetwork tool is used to update subnetworks that are marked as dirty from edits made, marking them as valid.

Subnetworks are marked as dirty when they're created and from validating the network topology after subnetwork features are edited. When a subnetwork is updated with no errors, it's marked as clean. This is tracked by the Is dirty attribute in the Subnetworks table. See Dirty subnetworks to learn more.

Subnetwork properties inspected and updated during update subnetwork

When a subnetwork is updated, there are certain properties and requirements that are checked. Some of these properties are set in the subnetwork definition for the tier. When a subnetwork is updated, there are also certain attributes are also updated for network features.

The following subsections include information about the properties that are inspected when a subnetwork is updated. If error features are generated from updating subnetworks, see Error feature management for details about specific error features and suggestions on how to resolve these; reference the section specific to update subnetwork.

Dive-in:
The Update Subnetwork tool performs attribute edits in place. This means that the Update Subnetwork process bypasses eventing and will not prompt the evaluation of attribute rules. See Evaluate attribute rules for more information.

Valid lines and devices

As specified in the subnetwork definition, certain asset groups and asset types for each feature class are defined as valid lines and valid devices for each tier in a domain network. Features that violate the subnetwork definition are discovered when updating the subnetwork by inspecting the attributes of traversable features in the subnetwork. If invalid features are discovered when updating a subnetwork, an error is reported and error features are created.

Subnetwork name attribute

The subnetwork name is an attribute set on device features that are defined as subnetwork controllers. The Update Subnetwork tool is used to update the subnetwork name attribute for features that are traversable from the subnetwork controllers. This process ensures that the subnetwork name is consistent for subnetwork features.

Inconsistent subnetworks—When a subnetwork has multiple subnetwork controllers that are traversable and the Subnetwork Name attribute does not match, the subnetwork is considered inconsistent. For example, in a mesh network with five subnetwork controllers; four of the subnetwork sources have the correct subnetwork name, while the fifth has a different name. If inconsistent subnetworks are discovered when updating subnetworks, an error is returned in the Update Subnetwork tool and error features are generated. The specific subnetwork names found to be inconsistent are returned and can be inspected using the Modify Subnetwork Controller pane and the Subnetworks table. Additionally, point error features are created for the subnetwork controllers that have inconsistent subnetwork names.

Disjoint subnetworks—For partitioned domain networks, subnetworks with controllers that have the same subnetwork name and are not traversable are considered disjoint subnetworks. When updating subnetworks, error features will be generated for disjoint subnetworks if the subnetwork definition does not allow for this. This setting is defined within the subnetwork definition for the tier. Check the network properties to review the Tiers subsection of the specific domain network.

Boundary features that connect multiple subnetworks are updated during the update subnetwork process. These are device features that are on the boundary of two different subnetworks; an open switch between two circuits or a closed valve between two zones. The Subnetwork name attribute for boundary features is updated to reflect the subnetworks it participates in by concatenating the subnetwork names separated by two colons, for example, subnetwork1::subnetwork2. If any of the neighboring subnetworks are found to be inconsistent, a warning is returned during the update process listing the conflicting subnetwork names. To determine how to resolve the warning, neighboring subnetworks mentioned can be inspected using the Modify Subnetwork Controller pane and the Subnetworks table. Once the neighboring subnetworks are edited, the update subnetwork process can be executed again.

To learn more, see Subnetworks and Subnetwork name attribute.

Is connected attribute

Every line and point feature participating in the line, device, and junction feature classes has an attribute named Is connected. This attribute helps identify isolated features by maintaining information about the line or point's connectivity to subnetwork controllers. The Is connected attribute is updated when a subnetwork is updated. Because the Update Subnetwork tool only affects features in the subnetwork, the tool only updates the Is connected attribute from False or Unknown to True for those features it affects. To learn more, read about the Is connected attribute.

Summaries, propagation, and attribute substitution

Summaries that are configured in the subnetwork trace configuration of the subnetwork definition are updated during the update subnetwork process. When updating a subnetwork, the tool writes the results of the summaries into the SubnetLine feature class for the summary attributes. Also, if propagators or substitution is configured, they are considered when a subnetwork is updated.

Review the following for more details: Summaries, Attribute propagation, and Attribute substitution.