Available with Standard or Advanced license.
When you publish or consume a service that contains a utility network and related network feature classes, some conditions and restrictions apply. These are dependent on the layers that are present in the map view, how the map service is configured, and where the service will be consumed.
The following are general guidelines for sharing utility network data from an enterprise geodatabase:
- The Utility Network service and Network Diagram service are available when publishing the utility network layer.
- Map layers 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.
License:
The active portal account must be licensed with the ArcGIS Utility Network user type extension to create, publish, and work with a utility network.
See Utility network services to learn more.
Publish a utility network layer
There are conditions and restrictions for sharing utility network and related feature classes as web layers. Analyzer errors are received when these rules are broken to prevent publishing. Additional analyzer warnings alert you if your intention is to consume services using ArcGIS Pro.
When the utility network layer is present in the active map view, the applicable conditions and restrictions for sharing are as follows:
- The published feature service automatically includes the Utility Network and Network Diagram child services to support trace analysis and network diagrams.
- The map layers for the published feature service do not support configurations such as definition queries and hidden fields set using the Visible field property—analyzer errors will be returned if these exist.
- The map must contain all of the utility network layers if the intent is to consume in ArcGIS Pro.
- An analyzer warning will be returned if a subset of utility network layers is provided. This is to warn about issues that will arise when consuming services in ArcGIS Pro that were published with a subset of utility network layers.
- Web layers must reference data from registered data sources; ensure that Reference registered data is checked under Data on the General tab of the Share As Web Layer pane.
- Include Feature for Layer Type to have access to the utility network layer, the ability to make edits on the default branch version, or the ability to enable the version management capability.
- Web layer properties for feature access must include the Only allow true curve updates by true curve clients option.
- All network layers must be registered as branch versioned.
- Version Management is an optional supported capability. Review Share branch versioned data to understand the conditions enforced by analyzers for branch versioned datasets.
Publish utility network feature classes without a utility network layer
When sharing network feature classes without the utility network layer, the restrictions are lessened. In this case, you can configure the active map view to include a subset of layers use definition queries, make a subset of fields visible, and so on. This allows an organization to share the services and maps with users who require access to a subset of utility network classes.
When the utility network layer is not present in the active map view, the application conditions and restrictions for sharing are as follows:
- The published feature service will not include the Utility Network or Network Diagram child services—performing trace analysis or working with network diagrams will not be supported.
- The map layers being published can support definition queries and hidden fields set using the Visible field property.
- This feature service will behave in the same way as any other feature service. Any edits will still apply utility network behavior behind the service (such as dirty area creation), but dirty areas and errors will not be visible on the map.
- The version management capability is optionally supported.
Workflow examples
To understand these conditions for working with services and the utility network, consider the following workflow examples based on an electric utility with electric distribution and electric transmission data. The example utility network in these workflows contains two domain networks for electric distribution and electric transmission and a structure network.
GIS editor workflows
A GIS editor working on electric distribution is performing maintenance edits on distribution data. That editor needs to see dirty areas and errors created by edits. The editor will use a feature service created with all the data and the utility network layer. The ArcGIS Pro project created for this user contains only the electric distribution domain network, the structure network, and the utility network layer.
Similarly, a GIS editor working on electric transmission is also performing maintenance edits on transmission data. That editor needs to see dirty areas and errors created by edits. The editor will use a feature service created with all the data and the utility network layer. The ArcGIS Pro project created for this user contains only the electric transmission domain network, the structure network, and the utility network layer.
GIS analyst workflows
A GIS analyst working on electric distribution needs to perform tracing, other analysis, and map production. The analyst uses a feature service created with all the data and the utility network layer. The ArcGIS Pro project for this analyst contains only the electric distribution domain network, the structure network, and the utility network layer.
Similarly, a GIS analyst working on electric transmission also needs to perform tracing, other analysis, and map production. The analyst uses a feature service created with all the data and the utility network layer. The ArcGIS Pro project for this analyst contains only the electric transmission domain network, the structure network, and the utility network layer.
An analyst working on both electric distribution and electric transmission will work with an ArcGIS Proproject containing the electric distribution domain network, the electric transmission domain network, the structure network, and the utility network layer.
In these three GIS analysis workflows, the GIS analyst needs permission to the whole feature service.
Web access workflows
Some casual users will use web maps configured for specific tasks and workflows. These web maps will be configured to have a reduced set of layers, possibly definition queries on some layers, and a reduced set of visible fields. When a user only needs to view or query data, the web map can use a feature service without a utility network layer.
If the user needs tracing or network diagrams, the web map will need to use a feature service that includes the utility network service and network diagram service.
Field editor workflows
Field editors use mobile devices to perform limited edits for workflows such as inventory inspection. These field editors typically use either Esri mobile apps or runtime apps created by Esri partners. Usually web maps are configured for these apps, but some partner runtime apps may use a different approach. Web maps configured for field editing can have a subset of layers from a utility network with definition queries on layers and a subset of fields made visible.
For simple editing workflows such as inspecting poles and equipment, the web map can use a feature service without the utility network layer, as it will not be necessary in this workflow to display dirty areas or errors.
More complex field editing workflows may require tracing or network diagrams. The web map for these more advanced workflows will require a feature service with the utility network service and the network diagram service.