Modifying the Lifecycle Status Domain Values in the UN

[TSmith]

Hello- 

I am interested in best practice information pertaining to modifications made to the lifecycle status domains. 

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? 

Thanks!

[JohnAlsup · Accepted solution]

We designed the lifecycle status to only have values that impact tracing.  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.  That is why we added a second status attribute, we called it construction status.  This gives more status options, but does not increase the number of bits used for typical tracing.  

So I would ask, how is In Service -Warranty different from In Service.  I would probably add a construction status for Warranty and not change lifecycle status.