Understanding Health Scores

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

Overview

Every Configuration Item (CI) in cmdbx receives a health score from 0-100. This score helps you prioritize CMDB improvements and track data quality over time.

Health Score Ranges

| Range | Status | Color | Action Needed | |-------|--------|-------|---------------| | 90-100 | Excellent | Green | No action needed | | 75-89 | Good | 🔵 Blue | Minor improvements recommended | | 50-74 | Fair | 🟡 Yellow | Should be addressed soon | | 25-49 | Poor | 🟠 Orange | Requires attention | | 0-24 | Critical | 🔴 Red | Immediate action needed |

How Health Scores Are Calculated

Health scores are calculated from 6 weighted components:

1. Data Completeness (25% weight)

Measures how many required fields are filled for the CI's class.

Example: A server with missing IP address, OS version, or owner will score lower.

Required fields vary by CI class:

  • Servers: Name, IP Address, OS, Environment, Owner
  • Applications: Name, Owner, Business Criticality, Environment
  • Databases: Name, Version, Owner, Host Server
  • Services: Name, Description, Owner, Status

How to improve:

  • Fill in missing required fields in ServiceNow
  • Use bulk update tools for common patterns
  • Set defaults for new CIs

2. Relationship Health (25% weight)

Evaluates the quality and validity of CI relationships.

Example: An application with no "Runs on" relationship to a server is likely incomplete.

Common relationship issues:

  • Orphaned CIs: No relationships at all
  • Missing upstream: Application without hosting server
  • Missing downstream: Server without applications or services
  • Invalid relationships: Connections that don't make sense (app "runs on" app)
  • Circular dependencies: A depends on B, B depends on A

How to improve:

  • Connect orphaned CIs to their dependencies
  • Remove invalid or duplicate relationships
  • Use CSDM Workbench to model services correctly
  • Ensure relationships follow CSDM patterns

3. Data Freshness (15% weight)

Checks when the CI was last updated.

Freshness thresholds:

  • < 30 days: Fresh (100% score)
  • 30-90 days: Aging (75% score)
  • 90-180 days: Stale (50% score)
  • > 180 days: Very stale (25% score)

Example: A server not updated in 6 months may have outdated information.

How to improve:

  • Update CI records during change windows
  • Set up automated discovery tools (ServiceNow Discovery)
  • Review and update stale CIs quarterly
  • Enable auto-update workflows in ServiceNow

4. CSDM Compliance (15% weight)

Validates whether CI relationships follow ServiceNow Common Service Data Model standards.

CSDM rules enforced (30+ rules):

  • Business Applications must "Contain" Application Services
  • Application Services must "Run on" servers or infrastructure
  • Business Services can't directly "Run on" hardware
  • Proper use of "Depends on", "Contains", "Runs on", "Connects to"

Example: A Business Application should "Contain" Application Services, not individual servers.

How to improve:

  • Use the CSDM Workbench to model services correctly
  • Review CSDM relationship rules documentation
  • Restructure non-compliant service hierarchies
  • Run CSDM validation reports

5. Operational Status (10% weight)

Considers the operational state and criticality of the CI.

Status values:

  • Operational: Active and in use (100%)
  • Non-Operational: Retired or decommissioned (50%)
  • Maintenance: Temporarily offline (75%)
  • Unknown/Blank: Unclear status (25%)

Example: A CI marked as "In Maintenance" for 12 months may actually be retired.

How to improve:

  • Update operational status regularly
  • Retire decommissioned CIs instead of leaving them inactive
  • Mark production CIs with appropriate criticality
  • Clean up "Unknown" status CIs

6. Business Criticality (10% weight)

Factors in the business impact if the CI fails.

Criticality levels:

  • Critical: Mission-critical systems (weight: 1.5x)
  • High: Important systems (weight: 1.25x)
  • Medium: Standard systems (weight: 1.0x)
  • Low: Non-essential systems (weight: 0.75x)

Example: Critical production CIs should have higher data quality than dev/test systems.

How to improve:

  • Set appropriate criticality levels for all CIs
  • Ensure critical CIs have complete data (100% fields filled)
  • Prioritize improvements for business-critical systems
  • Review criticality during change management

Viewing Health Scores

Dashboard View

The Health Dashboard shows:

  • Overall CMDB health score (average of all CIs)
  • Health distribution (count of CIs in each range)
  • Health trend (12-week historical chart)
  • Top issues (most common problems across CIs)

CI Health Workspace View

When browsing CIs:

  • Each CI displays its health score as a colored badge
  • Click a CI to see detailed health breakdown
  • Filter by health range using the status cards
  • Sort by health score to find worst offenders

Individual CI View

Click any CI to see:

  • Overall health score (large number)
  • Breakdown by component (6 components with percentages)
  • Specific issues identified (missing fields, stale data, etc.)
  • AI-generated remediation recommendations
  • Health history over time (trend chart)

Improving Health Scores

Quick Wins (30 minutes)

Focus on these high-impact, low-effort improvements:

  1. Fix orphaned CIs: Add missing relationships (owners, servers, services)
  2. Fill missing fields: Update IP addresses, environments, criticality
  3. Update stale records: Review CIs not updated in 90+ days
  4. Set operational status: Mark CIs as Operational, Retired, or Maintenance

Medium Effort (1-2 days)

Tackle these for sustained improvement:

  1. CSDM restructuring: Use CSDM Workbench to model services correctly
  2. Relationship cleanup: Remove invalid or duplicate relationships
  3. Bulk updates: Use AI Remediation to generate improvement plans
  4. Criticality review: Ensure all production CIs have appropriate criticality

Long-Term (Ongoing)

Implement these processes for continuous improvement:

  1. Automated discovery: Set up ServiceNow Discovery to keep data fresh
  2. Process integration: Update CMDB during change/incident workflows
  3. Quarterly audits: Review and improve health scores regularly
  4. Onboarding process: Ensure new CIs are created with complete data

Use the AI Remediation feature in the CI Health Workspace to generate bulk improvement plans. It analyzes all filtered CIs and provides prioritized recommendations.

Frequently Asked Questions

Q: Why did my health score drop?

A: Health scores can drop if:

  • Data becomes stale (not updated in 90+ days)
  • Relationships are removed or invalidated
  • Required fields are cleared
  • Sync brought in new CIs with missing data
  • CSDM compliance issues are detected

Check the health trend chart to see when the drop occurred, then review recent changes.

Q: How often are health scores recalculated?

A: Health scores are recalculated:

  • Automatically during daily sync (default)
  • Manually via "Recalculate Health" button in CI Health Workspace
  • After changes in CSDM Workbench
  • On-demand via CI Health Workspace

Q: What's a "good" overall CMDB health score?

A: Target scores by maturity:

| Score | Assessment | Recommendation | |-------|------------|----------------| | 80%+ | Excellent | World-class CMDB hygiene, maintain current processes | | 70-79% | Good | Above average, focus on incremental improvements | | 60-69% | Fair | Room for improvement, prioritize top issues | | 50-59% | Poor | Needs attention, implement improvement plan | | < 50% | Critical | Urgent action required, dedicate resources |

Q: Can I customize health scoring weights?

A: Not currently. Health scoring uses industry best practices and ServiceNow CSDM standards. If you have specific needs, contact [email protected] to discuss custom scoring.

Q: Why do some CIs have N/A scores?

A: CIs may show N/A if:

  • Recently created (not yet scored)
  • Missing critical data for scoring
  • CI class not supported for health scoring
  • Sync in progress

Wait for next sync or manually trigger recalculation.

Q: How does health scoring compare to ServiceNow's built-in scoring?

A: cmdbx health scoring is more comprehensive:

| Feature | cmdbx | ServiceNow CMDB Health | |---------|-------|------------------------| | Data completeness | Yes | Yes | | Relationship health | Yes | Limited | | CSDM compliance | Yes | No | | Data freshness | Yes | No | | AI recommendations | Yes | No | | Trend analysis | Yes | Limited |

Related Articles

Need Help?

Contact [email protected] or use the AI Assistant to ask questions about your health scores.