Description

A focused course, tailored for you

CMDB Governance That Survives Discovery Drift

A practitioner course for ITSM professionals who need CI data their change and audit processes can actually rely on.

Your CMDB discovery runs clean. Your health score still drops. The problem isn't the discovery tool, it's the governance layer: who owns each CI class, which source wins when two discovery methods conflict, and what the escalation path is when accuracy slips below the threshold your change team relies on.

$199 one-time

Tailored to your situation. Access within 24 hours. 30-day money-back.

Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.

Why this course

CI data quality is the foundation every downstream ITSM process depends on. Change risk scoring pulls from CI relationships. Service catalog entries map to CI hierarchies. Incident routing uses CI class and tier. When the CMDB drifts, all of these processes degrade quietly, and the failure only surfaces at the worst moment: a major change window where the impact analysis is wrong, or an audit where you cannot demonstrate CI accuracy to an ISO 20000 assessor. Most CMDB teams try to solve drift by running discovery more frequently or adding normalization rules. Neither works long-term without an underlying governance framework that defines ownership, source-of-truth hierarchy, and correction SLAs.

What you walk away with

Define a CI classification policy that sets clear scope, minimum viable CI attributes, and lifecycle stages your team will actually maintain.
Build a discovery reconciliation ruleset that resolves source conflicts by CI class, preventing discovery drift from overwriting authoritative manual records.
Establish a CI ownership and accountability model with named owners, correction SLAs, and an escalation path for stale or unverifiable records.
Connect CMDB relationship accuracy to change risk scoring so your CAB has reliable affected-CI data for every change request.
Design a CMDB health reporting framework that tracks the metrics your audit and operations stakeholders need, not just the percentage your discovery tool reports.
Produce a governance operating model with a quarterly review cadence, a governance board charter, and a continuous improvement loop that prevents drift from returning.

The 12 modules

Module 1. The CI Classification Problem

Most CMDB health problems start with an undefined scope boundary: what belongs in the CMDB, at what level of detail, and maintained by whom. This module works through the CI classification policy document, defining CI classes, minimum viable attribute sets, and the scope boundary that prevents the CMDB from becoming an unmanageable dumping ground. You produce a draft CI classification policy your team can ratify and enforce.

Module 2. Discovery Architecture and Source Authority

When two discovery sources disagree on the same CI, which one wins? Without a defined source-of-truth hierarchy, discovery tools silently overwrite authoritative data, creating drift that is invisible until it causes a downstream failure. This module maps your discovery landscape, defines source authority by CI class, and produces the source hierarchy document that governs reconciliation decisions across your environment.

Module 3. Building the Reconciliation Ruleset

Reconciliation rules translate source authority decisions into the logic that runs during every discovery cycle. This module walks through designing reconciliation rules by attribute: which fields are discovery-authoritative, which are manually maintained and protected, and which require human review when sources conflict. You produce a reconciliation ruleset specification document and a testing protocol that validates rule behavior before deployment.

Module 4. CI Ownership and the Accountability Matrix

Data that nobody owns degrades. This module designs the CI ownership model: how CI classes map to owner roles, what correction SLAs are realistic, and what the escalation path is when a CI goes stale or its owner leaves. You produce a CI ownership RACI matrix and a stale-record escalation procedure your operations and change teams will accept as authoritative.

Module 5. CMDB Health Metrics That Support Change Risk

Raw CI accuracy percentage is not the metric your change advisory board cares about. They care whether CIs connected to this week's change requests have verified relationships and accurate attributes. This module reframes CMDB health metrics around operational use cases, produces a health reporting template segmented by change-impact tier, and defines the accuracy threshold below which change risk scoring becomes unreliable.

Module 6. Integrating CMDB with Change Risk Scoring

The change management process depends on CMDB relationship data to calculate affected services, estimate blast radius, and assign risk tier. This module documents the data dependencies between CMDB and change management, identifies the CI attributes and relationship types that feed risk scoring, and produces an integration specification that makes the connection between CI accuracy and change approval quality explicit for your CAB.

Module 7. CI Lifecycle Governance Policy

A CI that discovery added three years ago and nobody has touched since is not a verified record, it is a liability. This module designs the CI lifecycle policy: how CIs move through planned, active, retired, and decommissioned states, who authorizes each transition, and what the retirement process looks like when a physical asset is removed from service. You produce a lifecycle policy document and a retirement workflow your change and asset teams can follow.

Module 8. Service Model Alignment and the Business Service Map

The service catalog and the CMDB should tell the same story about how services are composed from CIs. This module aligns your CI hierarchy with your service catalog structure, identifies gaps where service catalog entries have no corresponding CI relationships, and produces a business service map that gives operations and management teams a reliable picture of service dependencies.

Module 9. Auditing the CMDB for ISO 20000 and ITIL Maturity

ISO 20000 and ITIL maturity assessments examine configuration management as a core process. Assessors ask to see CI scope documentation, evidence of regular accuracy reviews, and records showing how configuration discrepancies are detected and corrected. This module maps CMDB governance artefacts to ISO 20000 clause 8.5 and ITIL 4 configuration management practice requirements, producing an evidence pack you can present to an external assessor.

Module 10. Stakeholder Alignment for CI Standards

Change management, asset management, and operations all have opinions about what the CMDB should contain and how it should be maintained, and those opinions often conflict. This module designs a stakeholder alignment workshop pattern: how to surface competing requirements, negotiate CI scope and quality standards, and produce a written agreement that change, asset, and operations teams will honor. You produce a workshop facilitation guide and a standards agreement template.

Module 11. Scripted Controls and Platform Automation for CI Quality

Manual governance processes break down under volume. This module designs platform automation that enforces CI governance at ingestion: attribute validation on CI creation, automated routing of relationship discrepancies for human review, and scheduled reports that flag CIs breaching correction SLAs before they become a health metric problem. You produce automation specifications your platform team can implement without requiring discovery tool changes.

Module 12. The CMDB Governance Operating Model

A governance framework without an operating model reverts to drift within six months. This module designs the repeating operating cadence: the quarterly CMDB governance review agenda, the governance board charter defining who has authority over scope and policy changes, the monthly health review feeding change management reporting, and the continuous improvement cycle that captures lessons from discovery conflicts and near-miss change failures. You produce a governance charter your organization can ratify and run.

How this addresses your situation

Specific modules that map to what you said you are dealing with.

Discovery completed clean but CI accuracy dropped: Module 3 (reconciliation ruleset) and Module 2 (source authority).

Change team reporting that risk scoring is pulling wrong affected CIs: Module 5 and Module 6.

ISO 20000 audit approaching, need to demonstrate configuration management process: Module 9.

CI owner left the team and records are going stale with no correction process: Module 4.

What you get with this course

12 written modules covering the full CMDB governance lifecycle from CI classification through quarterly operating model.
Downloadable templates: CI classification policy, reconciliation ruleset specification, CI ownership RACI matrix, health reporting template, lifecycle policy, stakeholder standards agreement, governance board charter.
Worked examples for each module using realistic ITSM scenarios across infrastructure, application, and business service CI classes.
The hand-built implementation playbook: a sequenced action plan mapped to your specific governance gaps, delivered alongside course access.

What you will have in hand by Day 1, Week 1, Month 1

Course access provisioned within 24 hours of purchase.

Hand-built implementation playbook delivered alongside course access.

Before and after

Before

CMDB accuracy drops each quarter despite successful discovery runs. Change management pulls CI data that does not match operational reality. Audit evidence for configuration management is thin or inconsistent. No clear owner when a CI goes stale.

After

A governance framework with defined CI ownership, a reconciliation ruleset that resolves source conflicts by CI class, CMDB health metrics tied to change risk thresholds, and a quarterly operating model that catches drift before it becomes a downstream problem.

What happens if you do not address this

Without a governance layer, discovery drift continues regardless of how often you run discovery. The downstream costs accumulate in change risk misjudgments, incident routing errors, and audit findings that configuration management is not operating as a controlled process. Each quarter the gap between CMDB data and operational reality widens, and the effort to close it compounds.

Who it is for

ITSM practitioners, CMDB administrators, and IT governance leads who own the quality and reliability of CI data across a medium-to-large environment. You are accountable for CMDB health metrics, CI lifecycle policy, and the governance process that keeps discovery data aligned with operational reality. You may sit in an IT operations team, a platform governance function, or an enterprise architecture practice with ITSM responsibility.

Who this is NOT for. Infrastructure engineers who only interact with the CMDB as consumers. Teams running a single lightweight ITSM tool with no discovery integration. Organizations that have not yet implemented a formal CI lifecycle process.

How it arrives

Text-based course in the Art of Service learning environment, plus downloadable templates and worked examples for every module, plus the hand-built implementation playbook delivered alongside course access.

Time investment. Each module is designed for a 60-90 minute focused session. Most practitioners work through the course over two to three weeks alongside their regular responsibilities.

Why $199 is the right number

Generic ITIL certification courses cover configuration management at a process level but do not produce the governance artefacts your team needs to operate: the reconciliation ruleset, ownership matrix, health reporting template. Consulting engagements can produce these artefacts but typically cost many times more and take weeks to schedule. This course delivers practitioner-level governance artefacts you build for your own environment, at the pace you set.

FAQ

Does this course require a specific discovery tool or ITSM platform?

No. The governance principles and artefacts covered are platform-agnostic. The reconciliation ruleset and ownership models apply across major ITSM and discovery platforms. Platform-specific configuration examples are noted where relevant, but the course does not depend on any single tool.

How is the implementation playbook different from the course modules?

The course modules teach the governance framework and produce templates you complete for your environment. The implementation playbook is hand-built by Gerard after your purchase, sequencing the actions specific to your governance gaps and environment context. It is a one-to-one artefact, not a generic checklist.

Can I use this to prepare for an ISO 20000 audit?

Yes. Module 9 maps CMDB governance artefacts directly to ISO 20000 clause 8.5 and produces an evidence pack structured for external assessors. The templates from earlier modules feed into this evidence pack.

30-day money-back guarantee. If after a week of working through the materials this is not what you needed, reply to the receipt email and a full refund is processed. No questions, no forms.

Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.