A healthy CMDB is not just about having some data — it’s about having the right data for the right class of Configuration Items (CIs) at the right time.
In this post, I want to explore a powerful but often under-leveraged concept in ServiceNow CMDB Health — Required and Recommended fields — and how these parameters play a pivotal role in determining CMDB Completeness.
🔍 What is CMDB Completeness?
Completeness is one of the 3 pillars of CMDB Health (alongside Correctness and Compliance). It answers a fundamental question:
“Is enough useful information present in a CI to make it operationally valuable?”
ServiceNow provides the CMDB Health Dashboard to visualize and track the completeness of CIs based on rules defined at the CI class level.
📌 Required vs. Recommended Fields: What’s the Difference?
ServiceNow allows you to configure Health Completeness Policies using two field types:
✅ Required Fields
- Mandatory for completeness calculation
- If missing, the CI is flagged as incomplete
- Drives data quality for critical fields like:
- Name
- Serial Number
- IP Address
💡 Recommended Fields
- Not mandatory but suggested for better context
- Examples:
- Environment
- Location
- Business Service
- Support Group
- Change Group
#ITOM #CMDB
✔️ If this solves your issue, please mark it as Correct.
✔️ If you found it helpful, please mark it as Helpful.
—
Shubham Jain
