OOTB State for inactive hardware CIs and their corresponding assets

Alok Kr Gupta
Tera Contributor

an hour ago

Hello everyone, 

 

I have a small query on inactive devices, for devices which are not seen by a discovery source for >60 days, what state should be updated for both at CMDB and AMDB to  retain record with a clear stale state ?

 

I could think of marking CI's Operational status as Non-operational but it does not changes the asset's state & substate. Even marking Lost may create ambiguity. 

 

Please share your thoughts/ insights if anyone has solved this without use of a custom attribute.  

0 Helpfuls
  • 73 Views
2 REPLIES 2

vaishali231
Kilo Sage

an hour ago

Hey @Alok Kr Gupta 

I wouldn't recommend automatically changing the Asset state based only on Discovery inactivity.

Discovery indicates whether a CI has been seen, not whether the physical asset has been lost, retired, or disposed of. A device may simply be powered off, disconnected from the network, or excluded from the Discovery schedule.

A common approach is to:

  1. Update the CI Operational Status to Non-operational (or use a custom "Stale/Not Seen" status) after the defined threshold (e.g., 60 days).
  2. Retain the current Asset State/Substate until the asset has been validated through your asset management or decommissioning process.
  3. Use the Last Discovered/Last Seen date to drive reports, notifications, or review tasks for asset owners.

This keeps the CMDB indicating that the CI is stale while avoiding incorrect asset lifecycle transitions such as Lost or Retired without confirmation

 

*************************************************************************************************************************************

If this response helps, please mark it as Accept as Solution and Helpful.

Doing so helps others in the community and encourages me to keep contributing.

Regards

Vaishali Singh

Servicenow Developer
Linkedin - https://www.linkedin.com/in/vaishali-singh-2273361bb



0 Helpfuls

Alok Kr Gupta
Tera Contributor
In response to vaishali231

an hour ago

Hey @vaishali231 , thanks for the response. 

 

I also thought of updating CI state as Non-operational and generate a task for the concerned  domain team to verify if the CI is still active or not. However, until the investigation if I simply keep the asset as in-use, then it will create an ambiguity. Also, when exporting a report, one needs to compare both the tables separately which defeats the purpose of single version of truth for asset and CI

0 Helpfuls