CMDB vs Asset Records

Lloyd_Codon · ‎09-05-2023

Hi everyone. I'm working on Asset Management side and I have this scenario, where my assets serial always changing because the CMDB team is updating the serials in their CMDB table base on(RITM Request to update Serial). Because of that, I have lot of records, serials with mismatch in their Asset Tag, Delivery Date, PO, Location etc.. Since I don't have view on RITM (Requests to Update CI Attributes), I know many more serials will get updated in the future like when replacement or refresh on data center happen. Hope somebody share some good practices related on this matter Asset or CMDB side. Thank you.

Prabu Velayutha · ‎09-05-2023

Hi @Lloyd_Codon

There is Asset CI field mapping configuration, you can remove the serial number from the mapping to make sure respective CI updates are not impacting the asset fields.

It is important to define the process while manually importing Bulk CIs in to CMDB.

If it is external data source integration make use of Identification and Reconciliation engine IRE APIs before transforming the data to the CMDB tables that will take care of duplicate CIs.

There should be a CMDB custodian or Configuration Manager who should review the bulk data approve the import, verify if the CIs already exist with the same serial number and reconcile with the existing record instead of creating new record, if you using IRE API it will take care otherwise you need to have Unique Identifiers like Serial number or Name or FQDN to check if the record exist like setup Colace in the transform map to update existing records.

Also if there are duplicate serial numbers in the manual import those needs to be corrected and the teams loading the data should be educated regarding the quality of data and its importance. Revert if you have any questions.

If my response helps to solve your issue. Kindly mark it as helpful & Accept the Solution.

View solution in original post

Prabu Velayutha · ‎09-05-2023

Hi @Lloyd_Codon

There is Asset CI field mapping configuration, you can remove the serial number from the mapping to make sure respective CI updates are not impacting the asset fields.

It is important to define the process while manually importing Bulk CIs in to CMDB.

If it is external data source integration make use of Identification and Reconciliation engine IRE APIs before transforming the data to the CMDB tables that will take care of duplicate CIs.

There should be a CMDB custodian or Configuration Manager who should review the bulk data approve the import, verify if the CIs already exist with the same serial number and reconcile with the existing record instead of creating new record, if you using IRE API it will take care otherwise you need to have Unique Identifiers like Serial number or Name or FQDN to check if the record exist like setup Colace in the transform map to update existing records.

Also if there are duplicate serial numbers in the manual import those needs to be corrected and the teams loading the data should be educated regarding the quality of data and its importance. Revert if you have any questions.

If my response helps to solve your issue. Kindly mark it as helpful & Accept the Solution.

Lloyd_Codon · ‎09-06-2023

Hi Prabu. Thank you for this info.

Prabu Velayutha · ‎09-07-2023

No problem! happy to help and share what I know.

Rahul Priyadars · ‎09-05-2023

may i know what Kind of CIs are in this scope where Serial No is Changed - Server , Laptop etc.

Is Host Name is still same and Serial No of Devices is changed and accordingly updated in CI Record?

What is the functional scenario where above Use Case is Coming?

** Serial No is important Key for Hardware CLass ci for Identification process which control the Updates / Create of a Given CI.

Regards

RP