Operationalization means using CMDB data in processes and automation, not just documentation.

Making IPC processes use CI references drives adoption and measurable impact.

Compliance covers policy violations and cardinality constraints; missing fields are completeness.

CMDB Workspace centralizes health tiles, tasks, and actions across ingest/govern/insight pillars.

A design review ensures attributes are few, useful, governed, and at the right inheritance level.

Use OOTB classes to maintain compatibility with products and reduce technical debt.

Retirement policies automate and govern lifecycle changes consistently across classes.

CCB needs decision?makers for model design and alignment to strategy; Tier?1/auditors are consumers not core decision?makers.

A single hardware asset can back different CI instances as its operational role changes across time.

Coverage compares discovered/in?scope items vs. what’s in the CMDB.

Use compliance policies and Data Manager to enforce and remediate ownership data.

Schema & dependency maps make relationships visible for validation; calendars/SLM don’t.

Quarantine and retire?then?delete patterns prevent data loss and enable review.

Compliance validates value policies and formats beyond presence.

Tie operational outcomes (failed changes) to health improvements to show value.

Certification policies schedule attestations of specific fields for assigned owners.

Separating Admin and Process Owner roles helps governance and prevents conflicts.

Use authoritative de?provision events/last?seen timestamps rather than indirect signals.

Display names are mutable and ambiguous; prefer stable identifiers and combinations.

A design document governs class/attribute/relationship decisions and is the basis for health policies.

Timeliness checks how recently CIs were updated/discovered vs. expectations.

Constrain choices and enforce via compliance to prevent drift.

Query Builder models graph queries over CIs and relationships, returning full sets and paths.

Unified Map/dependency views visualize relationships for impact and troubleshooting.

OM/Change and SAM leverage CMDB relationships and utilization data for outcomes.

NLQ interprets plain English against saved queries for easier insights.

Dependency view maps upstream/downstream paths for impact analysis.

Playbooks in the Foundations Dashboard provide step?by?step remediation tied to indicators.

Graph queries control direction and types to capture full paths; text contains/Excel joins are not graph traversal.

Coverage is about discovered/expected vs. present; show time?series improvements.

Store Service Graph Connectors deliver tested, IRE?aligned integrations for major systems like Intune/SCCM.

Put common attributes at the correct parent so children (e.g., Linux/Windows servers, Docker hosts) inherit without duplication.

Identification & Reconciliation Engine uses identifiers and precedence to merge multi?source data into a single trusted CI.

CMDB 360/multi?source views expose provenance and quality, useful regardless of Discovery licensing.

Prefer standard relationship semantics; if missing, add one well?governed type used consistently across classes.

Support/Managed?by groups are non?discoverable CMDB attributes referenced to foundational data for routing and reporting.

Applications (cmdb_ci_appl) represent deployed code instances (e.g., DB instances) used operationally in IPC.

CI Class Manager reclassification enforces constraints and preserves relationships/history safely.

Business Application is non?operational portfolio; Application Service is the logical deployed service instance used in IPC.

Place attributes at the highest appropriate parent to leverage inheritance; avoid duplicating on children.

Completeness focuses on key non?discoverable operational attributes tied to routing and lifecycle.

IH ETL supports sequencing, transformations, and creation of foundational references before CI loads.

Identifiers and precedence enable safe multi?source reconciliation instead of siloing sources.

Identifiers combine with IRE reconciliation to prevent duplicates; timing and load balancing do not resolve identity.

Govern non?discoverables through Data Manager/certification rather than unreliable automation or manual free?text.

Extending OOTB classes preserves inheritance and upgradeability, reducing technical debt compared to parallel bases or ad?hoc custom fields.

SG Connectors and Discovery patterns can populate software/package relationships; manual updates don’t scale.

Tag?based mapping leverages consistent cloud tags as seeds for service entry points and ownership.

ACC collects utilization and rich endpoint config not feasible agentlessly, enabling SAM/ops use cases.

Retirement policies govern end?of?life via controlled rules instead of blind deletes.

Keys and foundational references enable deterministic joins between discovered and manual data.

Validate and set class consistently in transforms to avoid unintended subclasses or base class pollution.

Import Sets suit simple/one?time loads; IH ETL suits orchestrated recurring pipelines.

Use stable identifiers (e.g., serial) rather than mutable display attributes.

Service Mapping (top?down) builds Application Services from entry points through dependencies.

Core metrics include Completeness, Correctness, Compliance, Coverage, Duplication, and Timeliness.

CMDB Health measures completeness/correctness/compliance per class with required attribute checks.

Identity rules and the dedupe tools address duplicates; scan frequency and autofill do not.

A RACI mapping clarifies ownership and stewardship for CMDB quality and lifecycle.

The Configuration Manager leads CMDB strategy/policy; other roles consume CMDB data.