How to make correctness 90 percent in CMDB dashboard as part of CMDB discovery?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello Everyone,
We have setup discovery for our project and everything in initial state
As part of CMDB health dashboard , our target is to keep the Correctness percentage as 90 %
Now in our system , correctness showing as -10% , what are all the recommended orphan rules we can apply for all CI classes ?
For example : for computer class , i applied orphan rules as
Operation status : non operational , ip address is no empty , most recent discovery before last 60 days
What are all the recommended steps to perform this ?? please suggest
Regards,
Shabbir Shaik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
20m ago
Hi @shabbir5
As a BPC, I can understand the pain. What you’re looking for is the ideal outcome and output, but what’s missing is the root understanding of the issue. Your current score is at –10%, which means there are gaps on the process side as well as the data side. There may be little to no governance, and anyone might be updating anything in the CMDB, which leads to these issues."
Also, I would suggest going to Now Create and getting the CMDB process workshop and process guide. There you will find many more useful tricks and topics.
https://learning.servicenow.com/nowcreate
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
6m ago
Hi @shabbir5 ,
An orphan CI is a configuration item in the CMDB that no longer has a valid technical or business relationship — meaning it’s not discovered, not referenced, or no longer connected to anything in the ecosystem, and therefore represents stale or inaccurate data.
A simple example is:
If a switch CI is removed or retired but its switch port CIs are still present, those ports become orphans, because their parent CI no longer exists.
You can also refer to this post for additional clarity:
https://www.servicenow.com/community/itsm-forum/orphan-ci-s-using-orphan-rule-in-cmdb-health/m-p/512...
When we talk about Correctness in CMDB Health, remember it doesn’t only look at orphan CIs — it also includes:
Stale CIs (not updated or discovered in a defined period)
Duplicate CIs (same asset discovered multiple times with conflicting records)
Orphan CIs (validity broken due to missing relationships)
So, to reach your target score, don’t focus only on orphan rules —
you should also review and tune your stale CI detection and duplicate CI handling.
Improving these additional two KPIs will help you close the gap and get that extra 10% uplift in correctness.
Regards,
Pratiksha
