Project Name
Turned a Drifting CMDB Into Reliable Configuration Data on ServiceNow for a Retail Enterprise
Our client is a large retail and eCommerce enterprise running a hybrid, multi-cloud IT estate that underpins its customer-facing digital services. The organisation had a ServiceNow CMDB in place, but the configuration data had diverged from reality over time: decommissioned servers still marked active, duplicate records returning conflicting answers to simple asset queries, and broken relationships making impact analysis unreliable at the moment it was needed most.
Because the data could not be trusted, teams had built workarounds that bypassed the CMDB entirely, and a system nobody uses quietly becomes shelfware regardless of what it cost to implement. The engagement was not a clean-up exercise, but it was a governance rebuild, starting from the operating model and working out to the automation that keeps the data honest.
A CMDB that existed on paper but had drifted so far from reality that the processes depending on it had stopped trusting it entirely.
- A CMDB No One Trusted: The CMDB was filled with inaccurate data, causing teams to bypass it entirely and undermining the value of the platform.
- Ghost CIs and Stale Records: Decommissioned servers and outdated assets remained active in the CMDB, making inventory and asset counts unreliable.
- Duplicate Configuration Items: The same assets existed under multiple records, creating conflicting data with no automated deduplication or reconciliation.
- Broken CI Relationships: Application dependencies and infrastructure relationships were outdated or incorrect, making impact analysis unreliable during incidents and changes.
- Set-and-Forget Discovery: Discovery jobs deteriorated over time as credentials expired, IP ranges changed, and MID servers went unmanaged, resulting in incomplete and outdated data.
- No Clear Ownership: No team owned CMDB data quality, allowing conflicts between sources to accumulate without accountability.
- Trying to Track Everything: Attempting to model the entire estate introduced unnecessary complexity, making the CMDB harder to maintain instead of more valuable.
- Fragmented Sources with No Authority: Multiple tools maintained conflicting asset records, with no authoritative source to reconcile discrepancies or ensure consistent data.
Ksolves, an AI-first ServiceNow consulting services company, rebuilt the CMDB on out-of-the-box ServiceNow, fixing the operating model first and then automating the data so it stays clean on its own. The governing principle was governance before tooling: CMDB drift is an accountability problem before it is a data problem, and no amount of discovery automation prevents drift from returning if ownership is unclear and scope is unmanaged.
- Service-Centric Scope with CSDM: Scoped the CMDB to critical business services and modelled them using CSDM, creating a focused, maintainable database that supports service delivery instead of tracking every asset.
- Ownership and Governance Board: Established service ownership, a governance board, and a clear roadmap, embedding accountability and preventing future CMDB drift.
- IRE as the Gatekeeper: Routed every data source through the Identification and Reconciliation Engine, eliminating duplicates and enforcing authoritative data ownership across all integrations.
- Targeted Discovery and MID Server Health: Optimised discovery schedules, maintained MID servers, and managed credentials proactively to ensure accurate, up-to-date asset data.
- Automated Dependency Mapping via Service Mapping: Used Service Mapping to maintain accurate application and infrastructure relationships, improving incident response and change impact analysis.
- Service Graph Connectors for Third-Party Data: Integrated endpoint and cloud data through Service Graph Connectors, ensuring every import follows IRE identification and reconciliation rules.
- CMDB Health KPIs and Automated Remediation: Configured health dashboards, staleness rules, and automated remediation tasks, turning CMDB maintenance into a continuous process.
- Data Certification for Non-Discoverable Attributes: Scheduled regular certification for business-owned attributes that cannot be validated automatically, keeping critical data accurate.
- CMDB Data Manager for Lifecycle Governance: Automated the retirement, archiving, and deletion of obsolete CIs, ensuring the CMDB continuously reflects the current environment.
Technology Stack
| Category | Technology |
|---|---|
| Core Platform | ServiceNow CMDB on the Now Platform |
| Data Integrity | Identification and Reconciliation Engine (IRE) |
| Discovery | ServiceNow Discovery with MID Servers |
| Relationships | ServiceNow Service Mapping |
| Third-Party Ingestion | Service Graph Connectors with IntegrationHub ETL |
| Service Modelling | Common Service Data Model (CSDM) |
| Health | CMDB Health Dashboard and KPIs |
| Certification | Data Certification |
| Lifecycle | CMDB Data Manager |
| Workspace | CMDB Workspace |
From a database no one trusted, and everyone worked around, to a living system of record that incident, change, and problem management can all stand on with confidence.
- A CMDB People Trust and Use: Accurate, up-to-date records restored confidence in the CMDB, making it the trusted foundation for IT operations instead of a system that teams bypass.
- Duplicates Eliminated at the Source: IRE and authoritative data rules prevent duplicate CIs and ensure consistent, reliable asset information across all data sources.
- Reliable Impact Analysis: Accurate CI relationships enable dependable change impact analysis and incident response based on the actual service landscape.
- Continuously Updated Discovery: Optimised discovery schedules, healthy MID servers, and managed credentials keep CMDB data current and eliminate stale records.
- Clear Ownership and Accountability: Service ownership and governance ensure ongoing data quality, preventing CMDB drift from returning.
- Continuous CMDB Health Management: Health KPIs and automated remediation tasks maintain data quality continuously, replacing periodic clean-up exercises.
- Automated Lifecycle Management: CMDB Data Manager retires stale and orphaned CIs automatically, keeping the database accurate and uncluttered.
- Stronger ITSM Outcomes: Trusted configuration data improves incident, change, and problem management, enabling faster decisions and more reliable IT operations.
Ksolves transformed an unreliable CMDB into a trusted system of record by combining strong governance with ServiceNow best practices. Through clear ownership, automated discovery, intelligent reconciliation, and continuous health monitoring, the organisation established accurate, dependable configuration data that strengthens incident, change, and problem management while remaining scalable as the IT estate evolves.
Does Your CMDB Feel More Like a Digital Junk Drawer than a Source of Truth?
