Set or modify the subnetwork definition

A subnetwork represents a topological subpart within a domain network and tier where features have traversability to the same subnetwork controllers. Subnetworks are used to drive analytics and visualize a network through rendering, labeling, and map generation.

Some of the properties for subnetworks are assigned when the domain network they reside in is created. These properties are for all subnetworks in the domain network. You can set additional properties for subnetworks at the tier level using the Set Subnetwork Definition geoprocessing tool. You can review the domain network and tier properties using the Network Properties tab.

For more details about the components set for a subnetwork at the tier level, see Subnetwork definition.

Requirements

To set subnetwork definitions, the following requirements must be met:

• The network topology must be disabled.
• A tier in the specified domain network must exist.
• When working with an enterprise geodatabase, ensure the following:
  • The Input Utility Network parameter must be from a database connection established as the database utility network owner.
  • The connected ArcGIS Enterprise portal account must be the portal utility network owner.

Set the subnetwork definition for a tier

To set the subnetwork definition for the specified tier, complete the following steps:

1. On the Analysis tab, in the Geoprocessing group, click Tools to open the Geoprocessing pane.
2. In the Geoprocessing pane, search for and select Set Subnetwork Definition.
3. For the Input Utility Network parameter, choose a utility network.
4. For the Domain Network parameter, choose the domain network.
5. For the Tier Name parameter, choose a tier.
6. Optionally, check Support Disjoint Subnetwork.

   The option for disjoint subnetworks is only available for tiers in domain networks that have a partitioned tier definition.

   • Checked—The tier can support disjoint subnetworks.
   • Unchecked (Default)—The tier does not support disjoint subnetworks.
7. For Subnetwork Diagram Templates, specify the diagram templates you want the network diagrams to be based on, if you want the system to automatically create subnetwork system diagrams for each subnetwork of that tier.
8. Expand the Valid Features and Objects section to set the following options:
   1. For the Valid Devices parameter, check all the asset types that can participate in these subnetworks.
   2. For the Valid Device Subnetwork Controllers parameter, specify the asset types from the device class that can be set as subnetwork controllers.
      The asset group and asset types listed must have the system network category of subnetwork controller assigned. Values listed are from the asset group and asset types provided for Valid Devices.
   3. For the Valid Lines parameter, check all the asset types that can participate in these subnetworks.
   4. For Aggregated Lines For SubnetLine Feature Class, specify the lines whose geometry will be aggregated to create the subnet lines among the valid lines.
   5. For the Valid Junctions parameter, check all the asset types that can participate in these subnetworks.
   6. For the Valid Junction Objects parameter, check all the asset types that can participate in these subnetworks.
   7. For the Valid Junction Object Subnetwork Controllers parameter, specify the asset types from the junction object class that can be set as subnetwork controllers.

      The asset group and asset types listed must have the system network category of subnetwork controller assigned. Values listed are from the asset group and asset types provided for Valid Junction Objects.

   8. For the Valid Edge Objects parameter, check all the asset types that can participate in these subnetworks.

   If the topology definition for the input domain network is set to hierarchical, these parameters present a subset of the valid features and objects defined for the parent tier (highest parent tier).

   Note:

   Certain parameters require a minimum Utility Network Version. Refer to the Set Subnetwork Definition tool.

9. Optionally, expand the Subnetwork Trace Configuration section to set any desired conditions.

   These autopopulate settings in the Trace geoprocessing tool for subnetwork traces. They are also used by the Update Subnetwork tool to determine which features define the subnetwork and are updated. Finally, the Export Subnetwork tool uses these settings to determine what information to export.

   • Include Containers—Specifies whether containers will be included.
   • Include Content—Specifies whether content of containers will be included.
   • Include Structures—Specifies whether structures will be included.
   • Include Barrier Features—Specifies whether barriers will be included.
   • Validate Locatability—Specifies whether an error will be returned if unlocatable junction or edge objects are encountered.
   • Summaries—Calculates and stores function information about a subnetwork in the SubnetLine feature class.
   • Condition Barriers—Defines a feature or object that will stop an operation based on network attributes and categories.
   • Function Barriers—Defines a feature or object that will stop an operation based on a function.
   • Apply Traversability To—Defines the traversability scope to enforce. Apply traversability to only junctions, only edges, or both junctions and edges.
   • Propagators—Uses propagated network attributes to control what network features are considered. A Substitution function is available. This parameter is only available Python.

   See Subnetwork trace configuration for more details and the Set Subnetwork Definition tool to explore each parameter.
10. Expand the Update Subnetwork Policy section to set the following options:
    1. Optionally, check the Manage IsDirty check box.

       This option determines whether the IsDirty attribute in the Subnetworks table is managed by the update subnetwork operation. This also impacts the consistency of network diagrams and the methods used to remove deleted controllers from the Subnetworks table. When this option is checked, the IsDirty attribute is managed by the update subnetwork operation and updated in the Subnetworks table and SubnetLine feature class. This option is only visible for tiers that have subnetwork controllers defined and is checked by default. When there are no subnetwork controllers defined for a tier, this option is disabled.

       Note:

       If the tier is configured to not manage the Is dirty attribute, the update subnetwork operation can be used in the default version to delete rows from the Subnetworks table in the default version where the Is deleted attribute is set to true.

    2. Optionally, check the Update Structure Network Containers check box.

       This option determines whether structure network containers have their supported subnetwork name attribute updated when running update subnetwork. This option is checked by default.

    3. Optionally, check the Update Domain Network Containers check box.

       This option determines whether domain network containers have their supported subnetwork name attribute updated when running update subnetwork. This option is checked by default.

    4. For Edit Mode for Default Version and Edit Mode for Named Version, choose from the following to determine how the operation performs attribute edits:

       Note:

       Edit Mode for Default Version also applies to file and mobile geodatabases.

       • Without Eventing—This is the default for both the default and named versions as well as when working in a single-user deployment. When using this edit mode in an enterprise deployment, geodatabase contracts are not honored during update subnetwork. This means that events do not trigger updates to editor tracking, attribute rules, or related objects when features are updated. This also means that changes made to features without events do not write geodatabase history for later review. This approach is taken to optimize the performance of update subnetwork.
         • When using this edit mode in the default version or a single-user deployment, the subnetwork name and propagated values are updated for all features and objects in the subnetwork.
         • When using this edit mode in named versions, the subnetwork name and propagated values are updated only for features edited by the user in the version.
       • With Eventing—This option enables users to trigger geodatabase behavior when updating subnetworks in the default and named version as well as when working in a single-user deployment. With this edit mode, cursor updates are used to update the subnetwork name and propagated values for all features traversed by the operation.

         Using With Eventing respects all geodatabase contracts. This means that attribute rules fire and have their validation status reset, editor tracking is updated, related objects are updated when applicable, and changes are recorded as actual edits in the history of the geodatabase. This edit mode should be considered for users who require attribute rules to fire during the update subnetwork operation.

         Caution:

         This option may adversely impact performance and should not be used with larger subnetworks when a large number of attribute rules or related objects such as feature-linked annotation classes, are present in your data.

    Note:

    Parameters in this section require a minimum Utility Network Version. Refer to the Set Subnetwork Definition tool for more information.

11. Click Run.

The subnetwork properties are defined for the tier. To view the subnetwork properties, open the utility network's layer properties and view the Network Properties tab. To establish subnetworks within the tier, see Create a subnetwork.