Sewer Utility Network Foundation

[egcon27]

Hello!

I'm working on building a prototype utility network using the Essentials Sewer Utility Network Foundation. So far, it's going well, and there's a lot of documentation available. Here's what I've done so far:

• Simple data mapping
• Migration workspace
• Load data using workspace
• Asset package to GDB
• Enable network topology
• Working on network errors

As I go through this process, I have some random questions.

1. Has anyone noticed that the Sewer Utility Network Essentials package is missing some things? I found documentation stating what should be included with the solution package, like instructions, workflow examples, and another map to support editing. The solution I downloaded seems to missing a lot of this…I downloaded it in June 2025 and using ArcPro 3.5.1

Introducing Utility Network Foundations

What is included in a Utility Network Foundation?

Each Utility Network Foundation includes:

• Instructions
• An Asset Package containing schema for components that typically make up the domain network and rules to define network behavior
• A map to publish the utility network service for the domain network
• A map to support editing
• Workflow examples
• Sample data

1. I noticed the required network attribute field "Operable" doesn't have the coded domain set up? The videos I watched looks like it should be. Im wondering if there is a reason for this? Or possibly a mistake in the preconfigured model.
2. I'm wondering about the map included in the foundation package. The table of contents has clean lines connecting everything. Is this just a display setting? When I created my utility network and added it to a map, I don't see these lines. Should I be seeing them with a proper UN setup. See attached.
3. Lastly, I'm wondering how I can create sub-networks. I've seen some things suggesting I can use an ancillary role field to automate this setup. I know there's a tool to modify the subnetwork controller, but I'm interested in using my ancillary role field somehow. Is there any good documentation on this if possible?

Thanks!

[RobertKrisher · Accepted solution]

Every link I reference below is contained on the Wastewater utility network reading list.

The article you reference was originally published in 2018 (last updated in 2023). Most of what is outlined is still available in the Utility Network Foundations, but the way it is delivered is changed. I'll reach out to someone from Solutions for more comment, and see if they can update the article to avoid future confusion.

1 - The operable field does have a domain configured, but only for certain subtypes. As an example, system valves are operable but relief valves aren't. You can verify this by using the subtypes pane in ArcGIS Pro or by referring to the data dictionary.

2 - I'm not sure what you mean by clean lines? If you just add the utility network to a map it won't contain any symbology, but you can repoint the layers in the provided map to your migrated data if you want to use that symbology. If you want to configure your own map, with your own symbology, there's a tutorial for that: https://learn.arcgis.com/en/projects/configure-a-map-for-arcgis-utility-network/

3 - Because your system is gravity fed, you should be able to use Digitized Direction tracing to do upstream/downstream tracing without loading subnetwork controllers (relevant article). I'd recommend you use the Modify Subnetwork Controller tool to manually create your subnetworks the first time before you attempt to automate this. Especially since the first time you create your subnetwork you may run into connectivity issues (relevant tutorial for creating subnetworks, subnetwork errors, and quality assurance). If you're implementing a foundation you could automatically create any sinks in your network as subnetwork controllers by migrating them into the C_Subnetworks table in your asset package. This will only work for asset types that are configured to be subnetwork controllers (treatment plant, directional manhole controllers, etc).

[egcon27]

Thank you @RobertKrisher ! I'll definitely use the links you provided. I sometimes get lost in the documentation rabbit hole.  

1- Just to clarify, does the operable field serve any specific purpose for the subtypes it is not set for? Should this field be populated for the Utility Network (UN) even if the subtypes are not operable? Since the Sewer Device Feature class has the operable field as a network attribute, wouldn't it be best to set up the domain so that these subtypes are marked as "operable = No"? Is it acceptable for this field to be null?

2- this is what i was referring to as "clean lines" (not sure what to call it). Wasn't sure if this was UN thing.

[RobertKrisher · Accepted solution]

1 - Operable is a network attribute for the device class, so any features that have a value populated will have their value used during analysis. Technically a cleanout isn't operable, but if you set it as Operable=No, and do a trace finding the first upstream inoperable device in your network, then it can be returned. Most attributes like this are either nullable or have an unknown or not applicable value.

2 - Based on the screenshot it looks like you are referring to the subtype group layers. If you click Add Data > Subtype Group Layer and select a class that has subtypes then it will add a special group layer that looks like that to your map. This is not exclusive to the utility network, but it is heavily relied upon by many utility network customers. If you follow the tutorial for configuring a map that I linked, you will learn about subtype group layeres.

[egcon27]

This is helpful thanks!