CMDB Certification Frequency
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
We are looking to revamp our CMDB certification tasks and are curious how often other business are sending out tasks to their Owners across the CIs.
Currently we operate on a monthly basis for Servers and Business Apps and find it too overwhelming for our end users to manage. We are also curious if others see a need to send out certification tasks for network gear (routers, firewalls, switches, etc.) or does your company do an annual sync up with the Class Owner?
Would love any input/feedback on what you found works for your company.
- Labels:
-
Data Health Tools
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Greetings @vsomm. I know there is a lot of flexibility in how frequent you can generate data certification and attestation tasks within CMDB Workspace. I don't think there is a one-size-fits-most solution and entirely depends on the business requirements / desired outcomes.
It would be worth exploring your data for the table(s) being certified to better understand metrics such as :
- How many new records are being created month-over-month
- How many records are being offboarded month-over-month
- For existing records, how often is information changing month-over-month
- How many fields are being certified as-is with no changes?
- How many fields are being changed (you can compare original value versus certified value)
- How many fields are being failed?
If you find that the table data you are certifying isn't changing a lot month-over-month, then it doesn't make sense to have certification campaigns so frequent. If you are finding there are a lot of changes but not enough resources available to perform the certifications, then that would be a great example of a risk to escalate to leadership. Finally, if you ARE finding there are a lot of changes to the table data month-over-month, that indicates to me, there is a problem upstream with the intake process that the correct information isn't being captured at the time of record creation. Apologies for the long non-answer but I thought it was a good question and wanted to chime in. Interested in what others have to share.
