Hi Experts,
I have a couple of questions in terms of Best practices for CMDB data.
1. We are using the network and server data for RU billing purposes every month. One challenge we are facing here is how to validate to RU. As you see, the auto-discovery is in place and the agreement is to find all the devices that are active and scanned by discovery in the last 30 days and validate and bill them. But, I see there is a lot of mismatch in the data when it is validated by the client and data available in CMDB. fixes are done reactively by the respective team which results in temporary fixes and again data is mismatched when it is validated by clients.
After my investigation, in a lot of differences in scheduled jobs, and no best practices are followed and running in a siloed manner, which loses the trust in the data , which results in multiple references of the same data, which defeats the purpose of CMDB. How to fix these data and how to make these validate same across both parties. Do I need to bring in some dates in the agreement, that the client needs to check the data in between dates ( since CMDb data will be changing)?
2. How to handle these CMDB data mismatches as best practices and avoid the ongoing issues
Kindly share your thoughts and expertise pls.
Regards,
Paul
Regards,
PaulSylo
Kindly mark "helpful", if this helps, or Mark as "Accepted " if it solves your issues !
