Migrate existing data into a utility network

There are three approaches to create and configure a utility network which are considered best practice: using the Utility Network Migration Wizard, the Migration toolset, or the Utility Network Foundations. The migration wizard and toolset are built around the Migrate To Utility Network tool, and are ideal for organizations seeking a straightforward path to create a generic utility network that inherits their existing schema and workflows. This approach is best suited to those with modest requirements who prefer to gradually enhance network capabilities over time. In contrast, the Utility Network Foundations provide industry-specific data models that align with Esri best practices, for customers aiming to maximize their investment in the utility network and use advanced capabilities such as associations, nonspatial objects, and network diagrams. This approach delivers a comprehensive framework tailored to specific industry needs.

This topic is focused on the process to create a utility network, which supports basic editing and tracing workflows using the Utility Network Migration Wizard or Migrate To Utility Network tool in the Migration toolset.

Utility network migration workflow

The Migrate To Utility Network tool creates a mobile geodatabase containing a utility network based on the existing source feature classes you provide. You can also access and work with the migrate tool using the Utility Network Migration Wizard to simplify mapping of existing data to utility network classes. Designed with existing geometric network users in mind, these tools facilitate access to the network management capabilities of the utility network for those whose current requirements are limited in scope. They allow you to preserve and map the existing schema for each class, assign domains for the creation of asset types, and optionally specify which asset types can be used to define the source or sink in the network as subnetwork controllers. Once the utility network is created, the Analyze Network Data tool can be used to identify errors or data quality issues and prescribe the editing operations that are required to address the problems. This tool creates an output that can be modified and used by the Apply Error Resolutions tool to automate the resolution of common error types in your network.

Data mapping and merging of fields

The Migrate To Utility Network tool and wizard allow you to create a utility network based on your existing data with minimal impact to your schema. It is important to understand how mapping is performed to migrate data into the fixed schema of the utility network.

When configuring the migrate tool, you decide how multiple source classes will be mapped to the feature classes that make up the utility network schema. By default, the Source Class name is assigned as an Asset Group label for the class in the output. With multiple feature classes being combined, it is unavoidable that fields available with some classes will not be present on others. You can maintain the existing schema for the each class by migrating and merging the fields in the output class.

For example, consider a scenario in which a water pump and a system valve feature class are mapped to the Water Device class with 10 fields each. By default, the fields from each class will be merged in the output to create a Water Device class with 20 attribute fields. Any fields with the same name and data type will be combined into a single field in the output class.

If the source classes contain subtypes, the migrate operation will automatically merge the associated domain values to the best of its ability. Should an issue occur during this process, a warning is returned.

Defining asset types

Every feature in a utility network is classified using a combination of its class, asset group, and asset type. The asset type represents the minor classification of utility network classes and plays an important role in defining the behaviors of features in a utility network, the most common being the establishment of rules that govern connectivity between features in the network.

Note:

The utility network created using the wizard and geoprocessing tool allows every device and junction asset type to connect with every other line asset type, providing similar topological capabilities as a geometric network.

Asset types can be defined using a field with a subtype or coded value domain. The descriptions from the subtype and domain are used as the description for the asset type. Codes are automatically generated, starting at 1 except in cases where you are using a subtype field with subtype codes between 1 and 1023 (inclusive). In this case, the original subtype codes are preserved. If the source data does not contain subtypes, any field with a coded value domain can be used to specify the asset types to be created. For example, if you populate the asset type field with the Valve Type field for the Control Valve Asset Group and Structure Type field for the Network Structure Asset Group, the coded value domain would be used to specify asset types, which allows us to configure rules and behaviors specific to each in the network. When no field is specified for the Asset Type, a single asset type corresponding with the Asset Group's name is created.

Configuring subnetworks

Subnetwork controllers define the origin of a subnetwork. They are used to define how a resource flows through a network and are set at the terminal level on features from the Device feature class and Junction Object table.

When mapping source data to asset groups and asset types in the output, you can specify whether the asset types for the feature class may act as a controller by checking the Is Controller check box. Selecting this option applies the Subnetwork Controller network category to each asset type of the specified asset group, assigns the appropriate terminal configuration, and adds a single tier to the output utility network with a basic subnetwork definition outlined below:

• Tier Name—Based on the domain network name
• Tier Rank—1
• Support Disjoint Subnetworks—True
• Update Subnetwork Policy—Do not manage Status. Do not update structure or domain network containers. Do not use eventing.
• Valid Subnetwork Controllers—All asset types configured as subnetwork controllers
• Valid Devices—All device layers
• Valid Junctions—All junction layers
• Valid Lines—All line layers
• Aggregated Lines for SubnetLine—None
• Trace Configuration—Do not include structures, containers, or content. Disabled devices are barriers.

If source data mapped to the Device class participates in a geometric network, includes an Ancillary Role field with the values Source or Sink, and the Is Controller parameter value is set, the rows with a value are added to the controllers.csv file created in the folder specified in the Output Location parameter. This file is created in the same location as the output mobile geodatabase and contains the information needed to enable the features as subnetwork controllers using Import Subnetwork Controllers tool to create a single system-wide subnetwork.

Requirements

The following requirements must be met to migrate data to a utility network using the wizard or tool:

• All data for the source and stand-alone classes must be geodatabase classes.

• For the Include related classes and Include attachments parameters, all relationships and attachments must use a Global ID primary key. Attribute relationships are not supported.

• For the mapping components, it is important to understand how the utility network manages networks in a traditional domain network to properly define the subnetwork controller type and tier definition. To learn more, see Types of subnetwork controllers and Tier definition. Understanding utility network feature classification will also help you define the proper mapping for asset group and asset types in the target classes.

Use the wizard to migrate data into a utility network

The Utility Network Migration Wizard guides you through the workflow associated with migrating existing data into a utility network and can help to simplify the mapping of existing data to asset groups and asset types in the output utility network.

Complete the following steps to create a utility network from existing data:

1. In the Catalog pane, right-click an existing geometric network referencing the data you want to migrate into a utility network.
2. Click To Utility Network to open the Utility Network Migration Wizard.

   Note:

   You can also access the wizard from the ribbon or Quick Access Toolbar by adding the To Utility Network command. If the wizard is not started from an existing geometric network, you can manually add domain networks and perform class mapping using existing source geodatabase feature classes.

3. On the Domain Networks page, fill in the following:
   1. Provide Name text for the domain network that will be created.
   2. For Controller Type, specify how network resources flow in the domain network.

      The default is Source.

   3. For Tier Definition, specify the definition that will be used for the domain network.

      The default is Partitioned.

   4. Optionally, use the Add Geometric Network or Add Domain Network buttons to create additional domain networks as necessary.
   5. Click Next.
4. On the Geodatabase Options page, specify information for the output geodatabase and utility network.
   1. For Service Territory Feature Class, define the operational area for your utility.
   2. For Output Folder, navigate to an existing folder that contains the output mobile geodatabase and utility network.
   3. Provide a name for the mobile geodatabase in Output Geodatabase Name.

      The default is MigrationDatabase.

   4. Provide a name for the feature dataset that will be created in Feature Dataset Name.

      The default is UtilityNetwork.

   5. Provide a name for the utility network that will be created in Utility Network Name.

      The default is Network.

   6. For Utility Network Version, specify the version that will be created.

      The default is Current. This creates the latest version of the utility network compatible with the current ArcGIS Pro release.

   7. To migrate fields and merge the schema from source feature classes into the output utility network classes, leave the Migrate fields check box checked.
   8. To maintain relationship classes and copy related tables for source data that is migrated into the utility network and stand-alone classes, check the Include related classes check box.

      This is unchecked by default.

   9. To include file attachments for source data that is migrated into the utility network and stand-alone classes, check the Include attachments check box.

      This is unchecked by default.

   10. To load data to the output utility network and geodatabase, leave the Load data check box checked.
   11. Click Next.
5. On the Utility Network Mapping page, configure the mapping of classes from the source dataset to the proper target class, asset group, and asset type in the output utility network.

   If you started the wizard using an existing geometric network, any feature classes associated with the network are displayed under the Source Class field, with Target Class and Asset Group specified.

   1. Use the Add Feature Class button to import additional feature classes to participate in the utility network.
   2. Specify or update Target Class as needed using the drop-down menu provided to map to the correct domain network class.
   3. For feature classes mapped to a device in the target class, check the Is Controller check box to specify whether it can act as a source or sink and serve as subnetwork controllers in your domain network.
   4. Click Next.
6. On the Standalone Class Mapping page, migrate feature classes into the output mobile geodatabase that do not participate in the utility network.
   1. Click the Add Class button to import additional feature classes or tables.
   2. Click Next.
7. On the Migration Summary page, review the geodatabase options and mapping configured for the migration.
   1. Optionally, use the navigation buttons at the bottom of the pane to navigate to previous pages and make any changes required.
   2. Click Finish.

A mobile geodatabase is created containing a utility network and stand-alone classes based on the existing source feature classes you provided.

Once the utility network is created, the Analyze Network Data tool can be used to identify errors or data quality issues and prescribe the editing operations that are required to address the problems. This tool creates an output that can be modified and used by the Apply Error Resolutions tool to automate the resolution of common error types in your network.

Use the Migrate To Utility Network tool to create a utility network

To use the Migrate To Utility Network tool to create a utility network, 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 Migrate To Utility Network.

   The Migrate To Utility Network tool opens in the Geoprocessing pane.

3. Specify a polygon feature class for the Service Territory Feature Class parameter.

   This feature class represents the geographical extent covered by the domain network. It is used to restrict edits so that features are not created outside of a network area. The utility network's extent (editing area) is the extent of the combined polygons.

   If no existing service territory feature class exists, a service territory polygon layer can be created with the map's spatial reference when source data is in an active map by using the Create command to the right of the drop-down menu.

4. For the Output Folder parameter, specify the output path and folder for the mobile geodatabase that will contain the utility network dataset.
5. For the Utility Network Version parameter, specify the version of the utility network to be created.
   • Current—Creates the latest utility network version compatible with the current version of ArcGIS Pro. This is the default.
   • 7—Creates a utility network version 7.
   • 6—Creates a utility network version 6.
   • 5—Creates a utility network version 5.
6. For the Feature Dataset Name parameter, specify a name for the utility network's feature dataset.

   The default is UtilityNetwork.

7. For the Output Name parameter, specify the name for the mobile geodatabase that will contain the utility network.

   The default is MigrationDatabase.

8. For the Load Data parameter, specify whether data or schema only will be loaded from the source classes to the output utility network.
   • Checked—Data from the source classes will be loaded to the output utility network and stand-alone classes. This is the default.
   • Unchecked—Schema only will be updated in the output utility network. Data will not be loaded.
9. For the Merge fields to utility network classes parameter, choose an option from the drop-down menu to specify whether fields from the source classes will be merged and combined in the output utility network classes.
   • Checked—Fields in the source classes will be combined with the fields in the output utility network. This is the default.
   • Unchecked—Fields in the source classes will not be added to the output utility network classes.
10. For the Include related classes parameter, specify whether to copy classes related to the input source and stand-alone classes.

    Classes related to a related class are not copied.

    • Checked—Classes related to the source and stand-alone classes are included in the migration to the output utility network.
    • Unchecked—Classes related to the source and stand-alone classes are not included in the migration to the output utility network. This is the default.
11. For the Include attachments parameter, specify whether to create an attachment table and migrate attachments from the source.
    • Checked—An attachment table is created in the output and attachments are migrated.
    • Unchecked—Attachments are not migrated to the output geodatabase. This is the default.
12. In the Mapping section, for the Domain Networks parameter components, complete the following for each domain network that will be created:
    1. For Name, specify the name of the domain network. This describes the resource the domain network manages and will prefix all network classes added to the domain network.
    2. For Subnetwork Controller Type, specify the subnetwork controller type that will be used to determine how the network resource flows through all subnetworks of the domain network. Specify whether resources originate from a point in your network (Source), or flow toward a point in your network (Sink).
    3. For Tier Definition, specify the tier definition type for the domain network, either Partitioned or Hierarchical.

       A tier definition denotes the organization of the tiers relative to the rest of the network.

13. In the Mapping section, for the Utility Network Mapping parameter components, specify the input feature classes and mapping details as follows:
    1. For Source Class, specify the source feature classes to be migrated to the output utility network.

       The Catalog view can be used to select multiple feature classes for input to the component using drag and drop.

    2. For Target Class, specify the output class in the domain network to which the source class should be mapped.

       This is determined by the geometry type of the features in the source. Keep the following in mind:

       • Domain network classes contain the network features through which your delivered resource flows while Structure domain network classes support these features.
       • Point features are typically devices or junctions.
       • Line features are domain or structure network lines.
       • Polygon features can be assigned as structure boundaries.

    3. For Asset Group, specify the name of the asset group that will be created for the source class in the target domain network.

       By default, this is assigned the name of the Source Class.

14. Optionally, for Asset Type, specify the subtype field or a field containing a coded value domain that will be used to define the asset types in the Target Class section.

    If Asset Type is empty, or the provided field does not contain a coded value domain, a single asset group is created using the name of the asset group.

15. For Is Controller, specify the asset types that can act as sources or sinks and serve as subnetwork controllers in your domain network.

    If checked, the specified asset group and asset types are assigned the Subnetwork Controller network category and are eligible to define the origin of a subnetwork. If the source feature class participates in a geometric network and contains an Ancillary Role field with the values of Source or Sink, these are used to determine which features of the asset type can serve as subnetwork controllers in the utility network. These features are output to a Controllers.csv file for later import into the output utility network. When no Ancillary Role field is present, subnetwork controllers can be set manually for the specified features in the output utility network.

16. For the Input Standalone Classes parameter, specify any feature classes that do not participate in the utility network that you want to copy and include in the output mobile geodatabase.
17. Click Run.

A mobile geodatabase is created containing a utility network and stand-alone classes based on the existing source feature classes you provided.

The Migrate to Utility Network tool completes and creates the following outputs:

• An output mobile geodatabase is created containing classes and a utility network dataset using the mappings and configuration settings applied.
• An output controllers.csv file is created in the output folder containing feature information for any sources or sinks identified in your source data with an Ancillary Role field. This can be used by the Import Subnetwork Controllers tool to set the sources or sinks in your network as subnetwork controllers.
• A group layer containing subtype group layers for each class controlled by the utility network is created in the output folder. This can be used to visualize your new schema in a map.
• A data loading workspace is created in the output folder that can be used to migrate your data again as needed. This is used when you want to run the data migration again using the same configuration, without the requirement of creating a new mobile geodatabase.

Once the utility network is created, the Analyze Network Data tool can be used to identify errors or data quality issues and prescribe the editing operations that are required to address the problems. This tool creates an output that can be modified and used by the Apply Error Resolutions tool to automate the resolution of common error types in your network.