One of the most frequent requests we’ve received from organizations that implemented a Utility Network Foundation was to rethink how we represented the lifecycle of an asset and give organizations more flexibility around how that status determines if a feature participates in a network or not. At the March 2026 ArcGIS Solutions release, we did just that.
For those unfamiliar, Utility Network Foundations accelerate the implementation of an ArcGIS Utility Network by providing you with an industry-specific configuration to help you get up and running faster. Utility Network Foundations are part of Esri’s collection of ArcGIS Solutions. These Foundations are available at no additional cost to ArcGIS users and are fully supported by Esri.
In March 2026 we released new versions of our Utility Network Foundations for District Energy, Electric, Gas, Sewer, Stormwater, and Water that incorporate the enhancements described below. We plan to update the Communications Utility Network Foundation in the fall of 2026 with these same capabilities, as well as add support for the Telecom Domain Network (TDN).
Why did we make the change?
We received consistent feedback that the previous field names that were used in most Foundations, Lifecycle Status and Construction Status, overlapped with terms utilities already used in asset management. The names didn’t clearly communicate their roles, which made it harder to align utility network editing with an organization’s existing lifecycle terminology.
To address this, we clarified the intent of each field. Lifecycle Status is now Asset State and remains the field used by the Foundations to support network behavior (i.e. the values used in traces and subnetworks). Construction Status is now Asset Lifecycle Status and is intended for an organization’s business lifecycle terminology. Since it’s no longer a network attribute, it’s easier to customize.
We also added a geoprocessing tool to the Utility Data Management Support (UDMS) toolbox that can create an attribute rule to keep the two fields in sync, allowing editors to work with familiar lifecycle terms while the system maintains the Asset State needed for expected network behavior.
What Changed?
Utility Network Foundations released at or after March 2026 will now include these changes.
1. The Lifecycle Status field is now named Asset State
- It has a new name
- Domain values remain the same as in previous versions
- The field remains a network attribute (in-line for performance)
While the name of this field has been changed to reduce confusion, the intended use of this field remains the same: to determine what features are included in a subnetwork or returned in a trace. This happens because the subnetwork definition and trace configurations included in the Utility Network Foundations specify that an asset state of “In Service” or “Planned Removal” is part of a subnetwork or trace, while a value of “Out of Service” or “Proposed” is not.
Here are some practical examples of how the Lifecycle Status field can be used.
- A water utility can set Asset State to Out of Service for assets that are retired/abandoned so they’re excluded from traces and subnetwork management.
- An electric utility wants to flag equipment for future replacement. They can set the Asset State to Planned Removal so that the users know equipment is planned to be removed but still is actively part of the network.
It is important to keep in mind that this field and its provided domains control a large part of the configuration and if modifications are made to this domain during implementation, knowledge of how network attributes are used is required. Modifying these values can have downstream impacts that the user may not be aware of.
2. The Construction Status field is now named Asset Lifecycle Status
- It has a new name
- Domain values remain the same as in previous versions
- Field is no longer a network attribute
- Customization of values is encouraged
This renamed field gives utilities a place to include their organization’s unique asset lifecycle statuses in their utility network implementation. The use of this field is completely optional. If an organization chooses to use this field, they can add to or modify the provided domain values to fit their business needs.
Here is an example of how a water utility might leverage this field.
- A water utility designs a new valve in their system and sets its Asset Lifecycle Status to Design. As the project progresses, the status moves to Approved, then Under Construction, and finally Construction Complete.
Note: Asset Lifecycle Status does not change trace/subnetwork behavior by itself; it only drives network behavior if you choose to sync it to Asset State (for example, using the UDMS attribute-rule tool described below).
3. Domains are simplified and subnetworks are more clearly defined
Another significant change from previous versions is that bitwise combinations for domain values on the Asset State network attribute are no longer required. Previously, the Utility Network Foundations had a domain structure where combined values lived at the root level, subtype domains repeated subsets of those values, and bitwise combinations were used inside traces and tiers.
Many users told us this was confusing as it required organizations to have a more advanced understanding of the schema, so we simplified it. The Foundations now rely on clear, explicit values. If your organization already uses bitwise combinations of values (where a single value represents multiple flags), you can continue with that approach, but the Foundations now ship with a simpler configuration that does not require it.
Going forward, Utility Network Foundations will only use a single domain with a compact set of values. The included trace and tier configuration will reference those values directly rather than relying on bitwise combinations.
4. Keeping fields in sync with attribute rules.
Organizations now have the option to use the Asset Lifecycle Status field to drive updates to the Asset State field. To do this the Utility Data Management Support (UDMS) toolbox now includes a geoprocessing tool that creates an attribute rule tailored to your data and calculates the correct Asset State value from the matching Asset Lifecycle Status value.
For example, a large gas utility may have dozens of different asset lifecycle values it uses to track an asset’s state at a granular level (out of service, in warehouse, under construction, etc). An attribute rule can synchronize each of those values with the proper Asset State value automatically.
While editors continue working with lifecycle terms that reflect real-world conditions, such as “Installed Not Energized” or “Abandoned in Place”, the tool ensures that the underlying Asset State is set for the expected network functionality. This automated approach removes the need for editors to understand internal network logic and helps administrators avoid mismatched or invalid status combinations.
Timeline and adoption guidance
The March 2026 ArcGIS Solutions release included these updates for all the Utility Network Foundations, except for Communications, which will be updated at the next release.
Frequently Asked Questions
Q: Am I required to adopt the new schema?
A: No. If your existing implementation functions well, you can keep it as-is.
Q: Do I have to stop using bitwise values?
A: No, they’re simply no longer required. Use them if they work for your organization, but it will be up to each user or organization to implement them.
Q: Do these changes affect Field Maps?
A: Yes, and it’s an improvement. If you use the geoprocessing tool to generate an attribute rule to sync your Asset State and Asset Lifecycle Status fields, editors can select the Asset Lifecycle Status value and the system sets Asset State behind the scenes. This change simplifies field editing and reduces errors.
Q: Can I customize Asset Lifecycle Status values?
A: Yes. Because Asset Lifecycle Status (formerly Construction Status) is no longer a network attribute, you can customize values to match your organization’s terminology and workflows.
Q: What if I need help migrating to the new structure?
A: Contact your Esri account team or join the Utility Network community to ask questions and share best practices.
Closing thoughts
These updates are all about making the Utility Network Foundations easier to understand and easier to work with, without disrupting systems that are already running smoothly. They provide a cleaner structure for new deployments, give organizations more flexibility where it matters, and reduce friction caused by terminology or configuration patterns that did not always align with organizational workflows.
We’re grateful for the feedback that made these changes, and we hope they make your future implementations simpler and more intuitive.
Commenting is not enabled for this article.