Utility Network Technical FAQ

Document created by BBaldwin-esristaff Employee on Mar 26, 2019Last modified by mmiller-esristaff on Mar 27, 2019
Version 10Show Document
  • View in full screen mode

The goal of this document is to keep a running, updated list of the common technical questions that users are asking related to Esri's utility network. Please feel free to post questions to the bottom of the blog post and we will work on incorporating these answers into the updated post.

 

There are already of wealth of resources available through the ArcGIS Pro help documentation and other sources. Please ensure your questions are not already answered on this site: What is a utility network?

 

  • Can any device be choosen as a subnetwork controller? 
    • For a partitioned network, a device with directional terminals is required, for a hierarchical network, devices with directional or bi-directional terminals is required.  The device requires the Subnetwork Controller Category and also be defined as a controller in the subnetwork definition.(revised 3/27/2019)
    • Revision history:
      • First Posted: 3/26/2019
      • Revised: 3/27/2019
  • Is there a way to create multiple connectivity associations at a time?
    • Connectivity associations can be built into the migration framework using Data Interoperability or the FME workbenches.  The Import Associations geoprocessing tool can be used to load associations in bulk from a CSV file after the network has been created and features loaded.
    • Revision history:
      • First Posted: 3/26/2019
      • Revised: 3/27/2019
  • Where are group and pre-set templates stored?
    • These templates are stored in the map inside an ArcGIS Pro Project.  The maps can be exported to Mapx and shared to other projects.  At this time, there is no process to export the templates to a file themself.
    • Revision history:
      • First Posted: 3/26/2019
      • Revised: 3/27/2019
  • If I need to make an update to the 'service territory' feature, what do I do?
    • You cannot expand the extent of an existing Utility Network.  The easiest process is to export the Utility Network to an Asset Package.  In the Asset Package, expand or adjust the extent.  Create a brand new EGDB, stage a new Utility Network and apply the asset package.  Then republish your services.  If you use the same name or overwrite your services, this should not affect any downstream maps.
    • Note: This will not bring any versioning information or history, so that information will be lost.  
    • Revision history:
      • First Posted: 3/26/2019
      • Revised: 3/27/2019
  • What domain values should be used? Should everything use unique domain codes?
    • As a field may be used for different values across the asset group, it is best practice to not use the same code for different descriptions. 
      • Example: 
        • Layer: Water Network Device
        • Asset Groups: Valve and Hydrant:
        • Valid values for Valves
          • 1: Open
          • 2: Closed
        • Valid values for Hydrants
          • 3: In Service
          • 4: Out of Service
        • We could use the same code, of 1 for hydrants and use the description of In Service, but when we run a query or perform a trace and are looking to stop of open Valves, we would have to add a second part to that configure to ensure we are stopping at open valve and not open hydrants.  By ensure codes are unique, we can ensure we are only stopping or returning open devices, not other devices that happen to share the same code, but the descirption is completely different.
    • Revision history:
      • First Posted: 3/26/2019
      • Revised: 3/27/2019
  • I would like to support the utility network in my application, how should I interact with the layers.
    • You will need to be able to interact with services.  Your software will interact with either a Feature Service(for read and write) or layers in a Map Service(Read only).
    • We recommend you support a web map as the interface into those services.  The industry solution templates ship with a Network Viewer.  This network viewer is very similar and look and feel to the Editor maps we provide.  The difference is it is not using Subtype layers.  For each subtype in a subtype layer, a web map layer is used with an definition expression by subtype.  
    • If you cannot use a web map and need to interact with a service, in the Utility Network solution template includes a simple network publishing map.  This map replaces the subtype layers with group layers with definition expressions per layer.  This is designed for a Map Service and cannot be published as a Feature Service.  You software can interact with the individual layers of this service, similar to the layers in a Feature Service.
    • If you want to use the Utility Network feature service, you will have to take advantage of the Query Data Elements capabilities of the feature service to interact with the schema of that data
    • Revision history:
      • First Posted: 3/26/2019
  • Is there any way to validate the schema of the Asset Package without having to create an EGDB and apply it?
  • Parking Lot: Please ask your questions in the comments and we will add them here and work on answers
    • Can I change an Asset Group in the utility network?
    • Can I change an Asset Type in the utility network?
    • Can I add or remove fields in the utility network?
    • How do you(Esri) design and develop the models?  Do you work in the asset package, do you work in scripts, do you work in the utility network?
    • If I add an asset group in the Asset Package, what are my steps to ensure the schema is valid?
2 people found this helpful

Attachments

    Outcomes