Should a CI be changed when the hardware asset is updated?

[Dan74]

Afternoon, 

Can someone advise on the following please?

I have a scenario that Ci names are being used continuously, even when the asset underneath it is retired and is replaced, is the normal? 

For example

Ci - Switch A 

Asset - 12345

Asset 1234 is replaced with Asset 5678 and the Ci remains Switch A.  Is this the correct practice.  The replacements assets are for lifecycle events or faulty kit etc.

Thank you in advance for your assistance

Dan

[Ashok Sasidhara · Accepted solution]

The CI associated with the asset should not be changed. When an asset is getting replaced, the state and substate of that asset should be updated accordingly (i.e. Ideally something like 'In stock' and 'Pending Repair' OR 'Retired' and 'Pending disposal'). The status of the corresponding CI should also get synced accordingly (E.g. CI should become non-operational when asset is retired). The new asset should have a separate CI associated with it. Refer the following URL to read about Asset-CI synchronization:

https://www.servicenow.com/docs/bundle/xanadu-it-service-management/page/product/asset-management/co...

[Guido Bernuetz]

I agree with the previous reply. When  an asset is replaced, it has a new serial number and maybe a new model.

These are core attributes also for the CI and must be in sync between Asset and CI.

Of course it is challenge to replace a CI which have a lot of relations. The new device may have the same relations.

So, new Asset => new CI !

[Dan74]

@Guido Bernuetz @Ashok Sasidhara Thanks both for the sanity check.