CMDB CI status fields - install_status vs life_cycle_stage

bpolo · ‎07-26-2023

We are currently implementing Vulnerability Response, and we noticed that OOB functionality in VR checks the status of a Configuration Item using the life_cycle_stage field. We do not have this field populated on our CIs. We use the install_status field to check the status of a CI. Please could someone explain the difference between these two fields, and when should which field be used. Is it best to start using the life_cycle_stage field rather than the install_status field? Or do they have different purposes?

Any help would be much appreciated. Thanks!

Ashok Sasidhara · ‎07-26-2023

Install status is one among the many different status fields present for CI classes in ServiceNow. There are others also like hardware status (applicable only for hardware CIs), operational status etc. Life cycle stage and Life cycle status are the new CSDM aligned fields aimed to ensure a consistent format for indicating CI status (by replacing the multiple legacy status fields) across all CI classes. Life Cycle Mapping [life_cycle_mapping] table shows how the various legacy status fields are mapped to Life cycle stage and Life cycle status values. You can find more details about this in the following URL:

https://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/configuration-managem...

View solution in original post

davidnavelgas · ‎04-17-2024

Hi,

We're going to start a new proyect and we are in the analysis phase. We have to work with non-it CI, like vehicles. For that we're going to use the CI class model Vehicle (cmdb_ci_vehicle) and we are thinking about how to manage the lifecycle of these items. OOB, ServiceNow has the fields install_status and operational_status and with the new features of CSDM, it includes LifeCycle Stage and LifeCycle Stage Status. The recommended practice is to use these new fields and we don't have any legacy status that we have to mapping. On the other hand, we have to do a simple app and it makes sense to use the classic fields. What approach do you recommend to us? If you used the classic fields, what do you believe make sense?

Thanks in advance.

Cheers.

David

Manu_h · ‎04-18-2024

This topic seems to be interesting to me.

Has anyone have and answer?

Best regards

Ashok Sasidhara · ‎04-18-2024

It is recommended to use new fields. Since you said that it is a new project and hence assuming that you don't have any existing data related to the items in your scope, you need not even have to bother about migrating from legacy to new fields. So you can directly start using the new fields.

Also on a separate note, you should explore 'Enterprise asset management' product if you have a use case to manage Vehicles & similar items as Assets also apart from managing them as CIs.

davidnavelgas · ‎04-18-2024

Hi,

Thanks for your answer.

For this first phase of the project we won't use Asset Management but it could be possible that we have to use in the future.

Cheers.

David