https://community.esri.com/t5/arcgis-utility-network-questions/modeling-proposed-features-in-the-utility-network/m-p/1671931#M6119 <P>You can add the proposed features to the utility network classes and snap them, but use the Lifecycle Network attribute to set them as Out of Service.&nbsp; The trace will treat them as a barrier and stop traversing at that location.&nbsp; The subnetwork definition has a setting to include/exclude barrier features in the definition.&nbsp;&nbsp;</P> Wed, 10 Dec 2025 12:30:33 GMT MikeMillerGIS 2025-12-10T12:30:33Z https://community.esri.com/t5/arcgis-utility-network-questions/modeling-proposed-features-in-the-utility-network/m-p/1668572#M6040 <P>Hey All,&nbsp;</P><P>Had a question pertaining to proposed assets in a Water Distribution UN. I am working with a client that currently digitizes proposed water mains and services as "pulled-back" from active mains. In some cases, their configuration has created topology errors due to gaps in feature connectivity or junctions missing.&nbsp;</P><P>I wanted to see what the community's experience has been with this, as to how to manage these transient asset states during a migration, to minimize the amount of cleanup required post-migration. I had theorized that perhaps a snapping operation could be ran during the migration on any proposed features (e.g, prior to loading data into the asset package and converting to a UN) but wanted to see if there is a better method to tackle this. We are excluding abandoned assets in this migration, as there are far too many and the only alternative we had found was faking z-values to remedy most of the stacked point issues.</P><P>&nbsp;</P><P>Thanks for any input!</P> Tue, 25 Nov 2025 18:49:08 GMT https://community.esri.com/t5/arcgis-utility-network-questions/modeling-proposed-features-in-the-utility-network/m-p/1668572#M6040 TSmith 2025-11-25T18:49:08Z https://community.esri.com/t5/arcgis-utility-network-questions/modeling-proposed-features-in-the-utility-network/m-p/1671931#M6119 <P>You can add the proposed features to the utility network classes and snap them, but use the Lifecycle Network attribute to set them as Out of Service.&nbsp; The trace will treat them as a barrier and stop traversing at that location.&nbsp; The subnetwork definition has a setting to include/exclude barrier features in the definition.&nbsp;&nbsp;</P> Wed, 10 Dec 2025 12:30:33 GMT https://community.esri.com/t5/arcgis-utility-network-questions/modeling-proposed-features-in-the-utility-network/m-p/1671931#M6119 MikeMillerGIS 2025-12-10T12:30:33Z