Life Cycle Stage for devices where user is on longer leave

[EikeK]

Is there a recommended combination of life cycle stages for devices that are operational but not actively in use because the user is on an extended leave of absence (e.g., parental leave, sabbatical), yet still has the device at home?

We need a way to distinguish these devices from others that are actively in use, as the costs differ between the two.

Unfortunately, I can’t find a suitable option among the Life Cycle Stages—to the best of my knowledge, it’s not permitted to add new stages either.

We are thinking about adding a checkbox to identify those devices in our reporting but would like to use ootb capabilities where possible. 

Thanks

[Phil Scherry]

I was thinking there were some states in the hardware asset management that might make sense in this scenario.  I'm sorry, but I forgot what status they map to on the CI side.  https://www.servicenow.com/docs/r/it-asset-management/asset-management/t_SettingAssetStatesAndSubsta...

State = In Stock with a substate of 'Reserved' or 'On hold'

State = In transit with a substate of 'Reserved'

State = In use with a substate of 'Pending fulfillment'

[EikeK]

Thank you.

In use - Pending fullfilment sounds like the closest one, but not the perfect solution.
With setting to In Stock we would need to select a stockroom and as soon as the asset is moved to a reserved state we lose the assigned to information.

[Mathew Hillyard]

Hi @EikeK 

Consider tracking this via the User information rather than the asset. There is presumably some way of working out the user is on long-term leave - if not, this should really be tracked at the User level rather than spread the information around every module/table that needs to know about this.

Then just join the User table to your target table (which I assume already has a relationship to a user - e.g. Owned by or Assigned to) via a Database View and report away 🙂

I hope this helps!
Mat

[EikeK]

Hi Mat,

I didnt think of going that direction but I like the idea.
We will look into that.

Thanks