Select to view content in your preferred language

Looking for Life Cycle Status Domain Definitions

173
2
Jump to solution
07-09-2025 12:30 PM
KevinBoes
Emerging Contributor

My organization manages sewer and stormwater utility data and added a life cycle status field several years ago to track an asset's status from proposal through abandonment. More recently, we have been preparing metadata for this dataset and are trying to codify definitions for the values in that domain (values in attached photo). With the exception of one value, the values in our domain seem to be the same as the out-of-the-box life cycle status domain prior to its split into life cycle status and construction status in the utility network model.

Despite our best efforts, we cannot locate documentation outlining when certain values should be used. For instance, under what circumstances should an asset be labeled as 'temporary' rather than 'to be retired'? Where might we be able to find such documentation, if it exists?

0 Kudos
1 Solution

Accepted Solutions
PatrickGCowan
Esri Contributor

Here's a breakdown of the standard lifecycle status codes you included, along with suggested meanings:

Code Description Suggested Meaning
0UnknownStatus is not defined or not yet assigned.
1ProposedAsset is planned but not yet approved or constructed.
2ApprovedAsset has been reviewed and approved for construction or installation.
4Under ConstructionAsset is currently being built or installed.
8In ServiceAsset is active and operational.
16To Be RetiredAsset is still in use but scheduled for decommissioning or removal.
32AbandonedAsset is no longer in use and has been formally removed from service.
64InactiveAsset is not currently in use but may be reactivated in the future.
 

Note: The value 65 (Temporary) does not appear in the original Esri schema and is most likely a custom addition. It also presents a potential conflict: since the domain uses bitwise values, 65 is the combination of 64 (Inactive) and 1 (Proposed). If “Temporary” is intended to be a distinct, standalone status—not a combination of other states—it would be more appropriate to assign it a unique bitwise value such as 128, which is the next available power of two.

View solution in original post

0 Kudos
2 Replies
PatrickGCowan
Esri Contributor

Here's a breakdown of the standard lifecycle status codes you included, along with suggested meanings:

Code Description Suggested Meaning
0UnknownStatus is not defined or not yet assigned.
1ProposedAsset is planned but not yet approved or constructed.
2ApprovedAsset has been reviewed and approved for construction or installation.
4Under ConstructionAsset is currently being built or installed.
8In ServiceAsset is active and operational.
16To Be RetiredAsset is still in use but scheduled for decommissioning or removal.
32AbandonedAsset is no longer in use and has been formally removed from service.
64InactiveAsset is not currently in use but may be reactivated in the future.
 

Note: The value 65 (Temporary) does not appear in the original Esri schema and is most likely a custom addition. It also presents a potential conflict: since the domain uses bitwise values, 65 is the combination of 64 (Inactive) and 1 (Proposed). If “Temporary” is intended to be a distinct, standalone status—not a combination of other states—it would be more appropriate to assign it a unique bitwise value such as 128, which is the next available power of two.

0 Kudos
KevinBoes
Emerging Contributor

This is exactly what we were looking for! Thank you for your help!

0 Kudos