Operational Asset Replacement
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 08:26 PM
We have noticed that during asset replacements, new assets are overriding existing ones. This issue is causing problems during asset audits as the details of old assets are being overwritten by the new ones, and it is also affecting the financial components.
Our Asset are auto sync via discovery CI.
Asset manager complaining that the discovery process should create a new asset record when the CI's serial number does not match the existing serial number.
Can someone please clarify the process for replacing old computers, workstations, servers, and switches in conjunction with CI management?
We are using the same "name" for the new device when it replace (mdb_ci.name) , but they have different serial numbers and other attributes based new device type.
I have reviewed below but still could not work this out yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-15-2024 11:00 PM
If replacing assets means you are really replacing one with the other and it has the same name, than indeed your asset manager is correct. You should use the serial number to create assets (if exists, update, if not, create).
I am not sure what you are struggling with, because you are mentioning how you are doing it now and how you should be doing it. You have provided your own solution.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 12:19 AM
The issue is that the system updates the existing CI and overdue the existing asset records with new details, including the serial number, instead of creating a new CI and new asset. This happening due to same device name use in new device name.
During the asset replacement should we retired existing CI prior?or any other method to be followed ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2024 03:28 AM
The new device should indicate its own attributes only. It is not recommended to use the same Name. The old asset should either go back to stock awaiting disposal or go for repair based on the scenario and the processes which you have defined. It is important that the 'State' and 'Substate' fields of both the old and new assets automatically get updated to indicate appropriate values as part of the replacement process.
Are you using HAM pro? Then you should look at the OOB asset lifecycle flows and make modified copies of those flows to address your requirements. The 'State' and 'Substate' updates happen automatically as part of these flows. Refer the following links about a couple of lifecycle flows which involve asset replacement:
