Improve CMDB Health

Last Updated: January 7, 2026 Estimated Reading Time: 8 minutes

Overview

A healthy CMDB is the foundation of effective IT operations. This guide provides a systematic approach to improving your CMDB health scores, from quick wins to long-term strategies.

Before You Begin

Understand Your Baseline

Before making improvements, assess your current state:

1. Check Overall Health Score: View your CMDB's aggregate health score in the Health Dashboard
2. Identify Problem Areas: Review the health distribution to see how many CIs fall into each range
3. Prioritize by Impact: Focus on critical and high-criticality CIs first
4. Review Top Issues: Use the "Top Issues" widget to see the most common problems

Set Realistic Goals

| Current Score | 30-Day Goal | 90-Day Goal | |---------------|-------------|-------------| | Below 50% | 55-60% | 65-70% | | 50-64% | 65-70% | 75-80% | | 65-74% | 75-80% | 80-85% | | 75%+ | 80-85% | Maintain/optimize |

Quick Wins (1-4 Hours)

These high-impact, low-effort improvements can boost your health score by 5-10 points within a day.

Step 1: Fix Orphaned CIs

Problem: CIs with no relationships are likely incomplete or abandoned.

Solution:

1. Go to CI Health Workspace
2. Filter by Health Score: 0-49 (Critical/Poor)
3. Look for CIs with "No relationships" issue
4. For each orphaned CI:
   • If legitimate: Add missing relationships (owner, hosts, depends on)
   • If retired: Mark as decommissioned or delete
   • If duplicate: Merge with correct CI in ServiceNow

Example: A server with no applications should either have apps added or be marked as retired.

Expected Impact: +3-5 health points per 100 orphaned CIs fixed

Step 2: Fill Missing Required Fields

Problem: Incomplete data reduces health scores and limits usefulness.

Solution:

1. Filter CI Health Workspace by "Missing required fields" issue
2. Group by CI class to identify patterns
3. Bulk update common fields:
   • Owner/Support Group: Assign to appropriate teams
   • Environment: Set to Production, Development, or Test.
   • Business Criticality: Mark as Critical, High, Medium, or Low
   • IP Address (servers): Add from discovery tools
   • Location: Set datacenter or region

Bulk Update Process:

1. Select multiple CIs with same missing field
2. Use ServiceNow bulk edit or import tools
3. Sync cmdbx to reflect changes
4. Verify health score improvement

Expected Impact: +2-4 health points per field completed

Step 3: Update Stale Records

Problem: CIs not updated in 90+ days may have outdated information.

Solution:

1. Filter by "Data freshness" issue in CI Health Workspace
2. Sort by last updated date (oldest first)
3. Review each stale CI:
   • Verify current state: Is it still operational?
   • Update key fields: Status, version, owner, location
   • Add update notes: Document what was verified
   • Set next review date: Schedule quarterly checks

Pro Tip: Use ServiceNow's Discovery tool to auto-update server and network device data.

Expected Impact: +2-3 health points per 100 CIs updated

Step 4: Set Operational Status

Problem: CIs with "Unknown" or blank status reduce health scores.

Solution:

1. Filter by operational status: "Unknown" or blank
2. Determine correct status for each CI:
   • Operational: Currently in use
   • Non-Operational: Retired, decommissioned, or disposed
   • Maintenance: Temporarily offline for updates
   • Awaiting Installation: Purchased but not deployed
3. Update status in ServiceNow
4. For non-operational CIs: Consider archiving or removing

Expected Impact: +1-2 health points per 100 CIs updated

Medium Effort (1-2 Weeks)

These improvements require more planning but deliver sustained health score gains.

Step 5: CSDM Restructuring

Problem: Services not following CSDM standards fail compliance checks.

Solution:

1. Open CSDM Workbench
2. Review flagged non-compliant services
3. Common fixes:
   • Business Services: Should contain Application Services, not directly run on servers
   • Application Services: Should run on infrastructure (servers, databases)
   • Technical Services: Should group infrastructure components
4. Use visual service modeling to restructure
5. Validate against CSDM rules before saving
6. Write back to ServiceNow

Example CSDM-Compliant Structure:

Business Service: Online Banking
├── Application Service: Web Application
│   ├── Runs On: Web Server 1
│   ├── Runs On: Web Server 2
│   └── Depends On: Database Service
└── Application Service: Database Service
    ├── Runs On: DB Server 1
    └── Runs On: DB Server 2

Expected Impact: +5-10 health points for restructured services

Step 6: Relationship Cleanup

Problem: Invalid, duplicate, or circular relationships reduce health scores.

Solution:

1. Go to Dependency Map
2. Enable "Highlight Issues" mode
3. Look for:
   • Circular dependencies: A → B → C → A
   • Invalid relationships: Application "runs on" Application
   • Duplicate relationships: Multiple identical connections
4. Use Blast Radius to verify impact before removing
5. Remove invalid relationships in ServiceNow
6. Sync cmdbx and verify fix

Common Invalid Patterns:

• Application → Application (should be "depends on", not "runs on")
• Server → Server (should be "connects to" for network)
• Business Service → Hardware (should go through Application Service)

Expected Impact: +3-5 health points per 50 relationships fixed

Step 7: AI-Powered Bulk Remediation

Problem: Manual fixes do not scale for large CMDBs.

Solution:

1. Filter the CI Health Workspace to the target CIs (for example, all servers with health less than 60%)
2. Click "AI Remediation" button
3. Review generated improvement plan:
   • Prioritized list of issues
   • Suggested fixes for each CI
   • Bulk update scripts (CSV or API)
4. Validate recommendations
5. Execute bulk updates in ServiceNow
6. Sync and verify health improvements

AI Remediation Features:

• Pattern detection across similar CIs
• Root cause analysis for systemic issues
• Automated script generation for bulk fixes
• Rollback recommendations if issues arise

Expected Impact: +10-20 health points for large-scale fixes

Long-Term Strategy (Ongoing)

Maintain and continuously improve CMDB health with these processes.

Step 8: Automated Discovery

Setup ServiceNow Discovery:

1. Configure discovery schedules for:
   • Servers (weekly)
   • Network devices (daily)
   • Applications (bi-weekly)
2. Map discovery data to CI fields
3. Enable auto-update for stale records
4. Monitor discovery failures and fix

Benefits:

• Automatically updates IP addresses, OS versions, installed software
• Keeps data fresh without manual effort
• Reduces stale record issues

Step 9: Process Integration

Embed CMDB updates into existing workflows:

Change Management:

• Require CMDB updates before change approval
• Verify affected CIs using Blast Radius
• Update CI data during change implementation

Incident Management:

• Link incidents to CIs
• Update CI status when failures occur
• Review CI health after major incidents

Onboarding:

• Create CIs with complete data from day one
• Use templates for common CI types
• Assign owners before deployment

Step 10: Quarterly Health Audits

Establish a Review Cadence:

Monthly:

• Review health score trends
• Address new critical issues (< 25% health)
• Update top 20 worst-performing CIs

Quarterly:

• Full CMDB audit for critical CIs
• CSDM compliance review
• Relationship validation
• Retire decommissioned CIs
• Train team on new cmdbx features

Annually:

• Comprehensive data quality assessment
• Review and adjust health goals
• Update CMDB governance policies
• Stakeholder reporting on improvements

How to Measure Success

Key Metrics to Track

1. Overall Health Score: Target 75%+ for mature CMDBs
2. Critical CI Health: All critical CIs should be 80%+
3. Issue Reduction: Track count of each issue type over time
4. Time to Resolve: How quickly new issues are addressed
5. User Adoption: Team engagement with cmdbx tools

Monthly Health Report Template

Present to stakeholders:

• Current overall health score (with trend)
• CIs improved this month (count and %)
• Top 5 improvements made
• Remaining critical issues
• Next month's focus areas

Common Pitfalls to Avoid

1. Perfectionism: Do not aim for 100% health. Focus on critical CIs first.
2. Ignoring Root Causes: Fix systemic issues, not just symptoms
3. No Governance: Improvements decay without ongoing processes
4. Lack of Ownership: Assign CMDB stewardship to specific teams
5. Tool Over Process: cmdbx shows problems; your team must fix them

Related Articles

• How Health Scores Work - How cmdbx calculates scores
• CSDM Compliance - How to reach CSDM compliance
• Best Practices - CMDB hygiene best practices
• Health Dashboard - How to use the health dashboard

Need Help?

Contact [email protected] or use the AI Assistant for personalized improvement recommendations.