Utility Network Sharing, Publishing, and Administration
This domain tests publishing a utility network as a feature service, enabling the Utility Network capability, sharing it securely, and administering versions, topology, and service performance. The exam focuses on deployment dependencies and ongoing maintenance tasks.
Publishing and sharing rules
- Publish from ArcGIS Pro as a web layer to a federated ArcGIS Enterprise portal and server. The enterprise geodatabase must be registered as a data store.
- The service must be a feature service with the Utility Network capability enabled. Without that capability, utility network tools such as tracing and subnetwork operations do not work through the service.
- Branch versioning is required. Editors connect through the service and work in versions; reconcile and post to the default version.
- Share the service and web map to portal groups and grant appropriate permissions. Viewers need query access; editors need edit access and version access.
- Schema changes must be applied consistently. After adding asset groups, asset types, or rules, re-enable and validate network topology and confirm the published service reflects the schema.
Administration tasks
- Monitor dirty areas, errors, and exceptions. Schedule validation and Update Subnetwork during low-use periods.
- Manage versions: reconcile, post, delete old versions, and compress the geodatabase. Rebuild indexes and update statistics for performance.
- Use Rebuild Network Topology when topology is corrupted, and verify service logs when traces fail.
Worked example
A team publishes a utility network but tracing fails in the web map. The service is a feature service and the data store is registered, but the Utility Network capability was not enabled. The fix is to enable the capability and republish or restart the service as appropriate. The reasoning is that tracing depends on the utility network service capability, not just on feature access.
Traps that cost marks
- Publishing to a non-federated server or from an unregistered data store.
- Using a file geodatabase, which cannot support a utility network service.
- Forgetting to enable the Utility Network capability and then blaming the trace configuration.
- Letting versions accumulate or failing to compress, causing administrative and performance problems.
- Changing the schema without validating topology or confirming the service is synchronized.