https://community.esri.com/t5/arcgis-utility-network-questions/modifying-the-lifecycle-status-domain-values-in/m-p/1324447#M2785 <P>We designed the lifecycle status to only have values that impact tracing.&nbsp; Each of the status we have use a bit in the network index, changing the domain, would increase the number of bits and potentially cause it to no longer be stored inline, impacting performance of tracing and update subnetwork.&nbsp; That is why we added a second status attribute, we called it construction status.&nbsp; This gives more status options, but does not increase the number of bits used for typical tracing.&nbsp;&nbsp;</P><P>So I would ask, how is In Service -Warranty different from In Service.&nbsp; I would probably add a construction status for Warranty and not change lifecycle status.</P> Thu, 31 Aug 2023 17:00:53 GMT JohnAlsup 2023-08-31T17:00:53Z https://community.esri.com/t5/arcgis-utility-network-questions/modifying-the-lifecycle-status-domain-values-in/m-p/1324405#M2784 <P>Hello-&nbsp;</P><P>I am interested in best practice information pertaining to modifications made to the lifecycle status domains.&nbsp;</P><P>A client I am working with is interested in adding "In Service- Warranty" to the domain. No problem... only thing I am concerned about is the tracing behavior set at the subnet level. This would cause a trace to fail when encountering a feature != In service and To be retired. How could I modify the lifecycle status domain/bitwise configuration to take this into account?&nbsp;</P><P>Thanks!</P> Thu, 31 Aug 2023 15:43:28 GMT https://community.esri.com/t5/arcgis-utility-network-questions/modifying-the-lifecycle-status-domain-values-in/m-p/1324405#M2784 TSmith 2023-08-31T15:43:28Z https://community.esri.com/t5/arcgis-utility-network-questions/modifying-the-lifecycle-status-domain-values-in/m-p/1324447#M2785 <P>We designed the lifecycle status to only have values that impact tracing.&nbsp; Each of the status we have use a bit in the network index, changing the domain, would increase the number of bits and potentially cause it to no longer be stored inline, impacting performance of tracing and update subnetwork.&nbsp; That is why we added a second status attribute, we called it construction status.&nbsp; This gives more status options, but does not increase the number of bits used for typical tracing.&nbsp;&nbsp;</P><P>So I would ask, how is In Service -Warranty different from In Service.&nbsp; I would probably add a construction status for Warranty and not change lifecycle status.</P> Thu, 31 Aug 2023 17:00:53 GMT https://community.esri.com/t5/arcgis-utility-network-questions/modifying-the-lifecycle-status-domain-values-in/m-p/1324447#M2785 JohnAlsup 2023-08-31T17:00:53Z