What is the Best Practice process for redeploying personal computer assets?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2023 01:50 PM
Hello community!
We are trying to define our best practice processes for redeploying personal computer assets that have been returned by an exiting staff. Should the department that bought the PC hold on to it until the next new hire arrives, or should it be returned to IT, or should it be returned to logistics/supply chain? What is the best practice you recommend?
I would greatly appreciate any direction you can give me.
Best regards,
Jeff
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2023 07:21 PM
Hi @Jeff Welton1 ,
We have a OOTB Flow, please refer to this doc : https://docs.servicenow.com/bundle/vancouver-it-asset-management/page/product/hardware-asset-managem...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2023 11:54 PM
It usually depends on the end of life of the 'Model' of PC which was returned by the user. If the returned model is approaching end of life soon (in a few months or so), it might be better to mark it as Retired and then ready to be disposed as per the organization's disposal process. If the returned model is not reaching end of life any time soon, it would be better to return it to the stockroom so that it can be redeployed to another user later (Assuming it is in a good working condition). But in both cases, typically the first step might be to return it to the ITAM support team so that they can take the necessary actions (E.g. data back up, data wiping, reimaging, repair if applicable etc.) depending on whether it is going to be retired or redeployed.
Ideally the organization should define the process around PC refresh considering end of life dates, redeployment criteria, retirement and disposal processes etc. Based on the defined criteria, create a new flow by reusing the hardware asset refresh flow mentioned in the following URL and modifying it as per your process and requirements: