When modifications are made to a subnetwork in a utility network, it becomes known as a dirty subnetwork. A dirty subnetwork indicates pieces of information are incomplete or out of date. Edits range from applying the subnetwork name to newly connected features, to updating an associated subnetwork system diagram. This is tracked by the Is dirty attribute in the Subnetworks table. Subnetworks are marked as dirty when initially created by adding a subnetwork controller, and can also be introduced by the validation of dirty areas. During validation, subnetworks that the features belong to are marked as dirty.
A dirty subnetwork may cause analytic events to yield unexpected results. Updating a subnetwork takes the edits made for subnetworks flagged as dirty and updates relevant subnetworks with this information. This process marks the subnetwork as clean by setting the Is dirty attribute to false in the Subnetworks table.
The following table lists various edits that can be performed on a utility network that affect the state of subnetworks or subnetwork components.
- Edits—Description of edits performed
- Results from edits—List of changes in subnetwork
- Results from Update Subnetwork—List of changes from executing Update Subnetwork
Results from edits to subnetwork and Update Subnetwork
|Edits||Results from edits||Results from Update Subnetwork|
Create a subnetwork
| || |
Create a subnetwork controller
Connect a feature
Delete a feature
Subnetwork name change
Subnetwork controller modification
Feature attribute modification
Delete a subnetwork
To completely delete a subnetwork, removing all records, the diagram, and SubnetLine feature, the Export Subnetwork tool is used.
Remove a subnetwork controller
To delete the row from the Subnetworks table, use the Export Subnetwork tool.
Details of the results are as follows:
- Subnetwork is dirty—A new row with the subnetwork name is written into the Subnetworks table with the Is dirty attribute marked as true.
- All subnetwork are dirty—All rows with the same subnetwork name in the Subnetworks table have the Is dirty attribute marked as true.
- SubnetLine is dirty—The associated row in the SubnetLine class attribute table is marked as dirty.
- Subnetwork system diagram is dirty—The associated subnetwork system diagram is marked as dirty.
- Subnetwork controller is dirty—The row associated with the subnetwork controller in the Subnetworks table is marked as dirty.
- All subnetwork controllers are deleted—The Is Deleted attribute is marked as true for all subnetwork controllers associated with the subnetwork.
- Subnetwork controller is deleted—The Is Deleted attribute is marked as true for the associated subnetwork controller.
- SubnetLine is deleted—The Is Deleted attribute is marked as true for the associated row in the attribute table of the SubnetLine.
- Subnetwork system diagram is deleted—The Is Deleted attribute is marked as true for the associated subnetwork system diagram.
Details of the updates are as follows:
- Subnetwork is clean—The associated row in the Subnetworks table has the Is dirty attribute marked as false.
- All Subnetworks are clean—All rows with the same subnetwork name in the Subnetwork Name attribute have the Is dirty attribute marked as false.
- SubnetLine is clean—The associated feature in the SubnetLine class is no longer marked as dirty.
- Subnetwork system diagram is clean—The associated subnetwork system diagram is no longer marked as dirty.
- Subnetwork controller is clean—The row associated with the subnetwork controller in the Subnetworks table is no longer marked as dirty.
- New SubnetLine feature—A new row is created in the SubnetLine table.
- New subnetwork system diagram—A new subnetwork system diagram is created.
- Summaries—Summaries are written to an attribute in the SubnetLine class.
- New diagram name—The subnetwork system diagram with the old name is deleted and a subnetwork system diagram is generated with the new name.
- Old subnetwork name removed—The row or rows with the old subnetwork name are removed.