CSDM 5.0 is the current version of ServiceNow's CMDB data model standard. Getting your CMDB ready for AI agents means fixing the CSDM data those agents read, one stage at a time: Foundation, Crawl, Walk, Run, Fly. As of 22 October 2026, ServiceNow ties its control tower, Event Management and its Triage and Categorize AI agent to CMDB data, so a wrong configuration item becomes a wrong agent action. CSDM work belongs in an instance-first AI readiness plan, alongside the data model prerequisites for Now Assist.
- ServiceNow published the CSDM 5 white paper in May 2025; it adds a seventh domain and relabels Application Service as Service Instance.
- ServiceNow's product page says Super Intelligence Control Tower (previously AI Control Tower) "exists within your CMDB".
- The CSDM Data Foundations dashboard shows key CSDM indicators on one tab per stage, Foundation through Fly.
What changed from CSDM 4.0 to CSDM 5.0?
CSDM 5.0 adds a seventh domain, Ideation & Strategy, renames the Manage Technical Services domain to Service Delivery, and changes three labels, including Application Service to Service Instance. ServiceNow's white paper launch post calls the release "an incremental and expanded version from the CSDM 4 model".
The white paper's list of CSDM 5.0 changes covers the Ideation & Strategy domain, SBOM, the System Component Model, Value Stream, Teams, life cycle stage and stage status, a DevOps change data model, the new Service Instance and AI CI classes, and the table label changes. The seven CSDM data domains are Foundation, Ideation & Strategy, Design & Planning, Build & Integration, Service Delivery, Service Consumption and Manage Portfolio. Ideation & Strategy capabilities belong to Strategic Portfolio Management (SPM). Build & Integration tables hold no operational CIs, and Design & Planning records are outside the direct targets of Incident, Problem and Change.
For teams comparing CSDM 5 vs CSDM 4, the relabels change the names admins see on existing records. ServiceNow's CSDM domain docs now describe the Service Instance table as the one "called application service before CSDM v5". The table names stay the same:
| CSDM 4 label | CSDM 5 label | Table |
|---|---|---|
| Application Service | Service Instance | cmdb_ci_service_auto |
| Technical Service | Technology Management Service | cmdb_ci_service_technical |
| Technical Service Offering | Technology Management Service Offering (Technology management offering in ServiceNow docs) | service_offering |
The child tables of cmdb_ci_service_auto keep the Application Service name and are grouped by how they are populated: Service Mapping, tag-based, calculated and query-based. The Technology Management Service label landed with the Yokohama family release. The new version also marks the single Business Process reference on Business Application as legacy.
Do you have to use the new CSDM 5 Service Instance classes?
The model adds five new Service Instance classes for data, network, connection, operational process and facility services. They shipped in CMDB CI Class Models 1.64.0 in November 2024. The CSDM white paper says they have no user interface, sit outside Event Impact Analysis, and carry "no expectation for use of Service Instances unless local requirements necessitate said use".
ServiceNow staff add a firmer condition for mapped services. A ServiceNow Yokohama article on Service Instance says: "If you need Service Configuration Item Associations, do not migrate to the new classes yet." Event Management builds service maps from those associations (svc_ci_assoc) together with CI relationships (cmdb_rel_ci), so keep the existing Application Service subclasses wherever Event Management depends on them.
Which ServiceNow AI agents and features depend on CMDB and CSDM data?
ServiceNow states a CMDB dependency for Super Intelligence Control Tower, AI Passport, Event Management and AIOps, the ITSM Triage agent, change risk assessment and the ServiceNow Otto (formerly Now Assist) agentic workflows for CMDB. ServiceNow's own docs show incident summarization and similar-incident matching working from text fields, and the L1 IT Service Desk AI Specialist page names no CMDB input.
ServiceNow's CSDM landing page makes the general case: its products are CSDM-aware and expect CMDB data organized according to CSDM guidelines. The table below lists where ServiceNow names the dependency for each AI capability, and where it names none.
| ServiceNow AI capability | What it reads from the CMDB/CSDM | ServiceNow source |
|---|---|---|
| Super Intelligence Control Tower | AI assets as CIs, with the control tower anchored by the CMDB and Context Engine | Knowledge 2026 control tower release and the control tower product page |
| AI Passport (expected Q4 2026) | Agent identity grounded in the CMDB, GRC policies and workflow approvals | AI Passport announcement |
| Event Management CI binding | CIs matched to incoming alerts; an alert with no CI match stays unlinked | CI binding for alerts |
| Event Management impact | CMDB relationships and service associations (cmdb_rel_ci, svc_ci_assoc) | Alert impact calculation |
| AIOps analyze alert impact workflow | Application services mapped to business and technical services through Service Portfolio data | AIOps agentic workflows |
| ITSM Triage and categorize agent | Service, service offering and CI, which it assigns on the incident | Triage and categorize use case |
| Change risk assessment | Affected CIs, impacted services and service offerings on the change request | Otto for ITSM skills |
| ServiceNow Otto for CMDB | Upstream services and CIs, through the Assess CMDB Impact agentic workflow | Otto for CMDB release notes |
| Incident summarization | No CMDB dependency stated: inputs are description, short description, work notes, comments and email | Incident summarization inputs |
| Similar incidents (Predictive Intelligence) | No CMDB dependency stated: similarity uses the Short description and Description fields | Predictive Intelligence for Incident |
| L1 IT Service Desk AI Specialist | No CMDB dependency stated on its docs page | L1 IT Service Desk AI Specialist |
The split sets the cleanup order. Summarization and similar-incident matching work without CMDB input. The Triage agent, change risk and Event Management write or calculate from CI and service data, so their output inherits every gap in it.
Event Management shows how much CI status matters. ServiceNow's impact docs say alerts on CIs in maintenance are excluded from impact calculation, and an alert with no matching CI stays unlinked until more information arrives. ServiceNow sources differ on alert analysis scope. The Now Assist for ITOM docs say it supports tag-based, rule-based and Log Analytics alert groups and analyzes other alert types at the parent alert level, while the ServiceNow Otto for ITOM release notes add automated and mixed alert groups. Gartner's February 2025 AI-ready data research sets the stakes for AI data in general, predicting that "through 2026, organizations will abandon 60% of AI projects unsupported by AI-ready data."
What does the Triage agent fix show?
The Triage agent fix is ServiceNow's own documented case of a CMDB gap turning into a wrong agent action. The August 2026 ServiceNow Otto for ITSM store releases (17.0.5, 16.0.6 and 15.1.4) fixed a case where the agent "could assign an irrelevant, caller-owned device" as the configuration item "when the matched service offering had no related configuration items of its own".
The trigger sat in CMDB data: a service offering with no related CIs. The agent turned it into a wrong field value on an incident. Relating CIs to every service offering closes that gap, and offerings are Walk-stage and Run-stage work in CSDM. Echelon's guide to governing AI agents in ServiceNow treats duplicate CIs and broken CI-to-service links as CMDB integrity checks.
Where do Super Intelligence Control Tower and Context Engine get their context?
ServiceNow's Knowledge 2026 release describes the expanded control tower as "anchored by the ServiceNow CMDB and Context Engine". The control tower product page tells customers to "Enrich each AI asset as a configuration item with lineage, ownership, and relationships." Context Engine applies a semantic layer that, per ServiceNow's data foundation announcement, "integrates CMDB, workflow data, analytics insights, and third-party systems".
ServiceNow told reporters ahead of Knowledge 2026 that it uses the control tower internally to manage over 1,600 AI assets, The Register reported.
The control tower took a new name in October 2026. ServiceNow's AI Passport announcement uses Super Intelligence Control Tower, and CIO.com reports the new name as part of the same announcement. ServiceNow docs and Community articles still say AI Control Tower as of 22 October 2026, so search both names when you look for setup steps. The same announcement says AI Passport, shadow AI detection and AI Cost Management "are expected to be available in Q4 2026."
How does CSDM 5 model AI agents, models and MCP services in the CMDB?
ServiceNow's AI inventory model stores deployed AI as CIs: AI Function (cmdb_ci_function_ai), AI Application (cmdb_ci_appl_ai_application) and MCP Function (cmdb_ci_function_mcp), with AI Model Deployment (cmdb_ci_ai_model_deployment) still in development. ServiceNow staff guidance groups these CIs into Service Instances, and AI digital assets such as models, datasets and prompts sit in the Build & Integration domain.
AI Function and AI Application shipped in CMDB CI Class Models 1.68.0 in January 2025, with AI Application extending cmdb_ci_appl. A ServiceNow staff blog on the AI inventory data model says: "AI CIs are populated into a Service Instance via Tags, CMDB Groups, or direct membership." The same blog links the AI System product model to Business Application through sn_apm_ws_ba_product_model_map.
On 22 July 2026 ServiceNow published formal guidance on AI in CSDM. It discusses new entities: Cancelled and Deployable life cycle statuses, a new Digital System CMDB class and a re-introduced DevOps Package class. The attached AICT with CSDM v1 paper says a Digital System "supersedes and encapsulates the traditional Business Application". That position comes from the July 2026 guidance paper and sits outside the 2025 white paper.
The same paper says CMDB and Service Graph Connector discovery will populate AI service instances, AI applications, AI agents and AI MCP services, and it calls CMDB and CSDM the "semantic layer" that gives AI agents "structured, authoritative knowledge". The June 2026 control tower release added three generally available Service Graph Connector integrations for AI discovery (Databricks, Snowflake and Hugging Face), and its Q1 2026 recap says AI assets get an initial risk classification as they enter the CMDB.
In what order should I clean up CMDB data before turning on agents?
Clean up CMDB data in ServiceNow's five CSDM stages: Foundation, Crawl, Walk, Run, Fly. The white paper keeps this order from CSDM 4 and adds AI agents to the reason Foundation comes first. The white paper's adoption section says: "Many of the reporting, workflow and AI agent asks of data within a CMDB are dependent upon referential data".
- Fix Foundation: clean Company, Business Unit, Department, Location, Groups, Users, CMDB Group, Product Models and Contracts, and map legacy status values to life cycle before activating
com.snc.cmdb.csdm.activation. - Reconcile Crawl: get the white paper's four Crawl-stage tables right (business application, application service, application, server/host; the Zurich Crawl docs call application service Mapped Application Service), with IRE identification rules blocking duplicate CIs.
- Relate Walk: build Technology Management Services, their offerings and Dynamic CI Groups, and relate CIs to every offering the Triage and Categorize AI agent can match.
- Map Run: model the Business Service Portfolio, Business Services and Business Service Offerings, the Service Portfolio data the AIOps analyze alert impact workflow uses.
- Complete Fly: add Business Capability, Information Object and Request Catalog, and ServiceNow's staged implementation docs allow Information Object before Fly.
Ownership and life cycle status cut across every stage. The Brazil CMDB release notes describe an app_service_owner role that grants create, read, update and delete access to Service Instance records. Version 4.1.0 of the Data Foundations Dashboards added a report of CIs where Operational Status and Lifecycle Stage differ, and the Zurich CMDB release notes removed Design as an Operational status value.
Ingestion is where duplicates start. IRE lets only authoritative sources write CI attributes and prevents duplicates by uniquely identifying each CI. Service Graph Connectors use IRE to identify and classify data before it is loaded into the CMDB. On a new instance, the same logic applies from day one, which Echelon covers in standing up a new ServiceNow instance. If the Triage agent is your first agentic workflow, Echelon's framework for an AI POC on ServiceNow uses L1 triage as its worked example.
How do you measure CMDB AI readiness in ServiceNow?
ServiceNow ships several tools that measure or improve CMDB and CSDM readiness, including the CMDB and CSDM Data Foundations Dashboards, CMDB Health, CMDB success advisor, the summarize CMDB readiness skill in ServiceNow Otto for CMDB, and CMDB Data Manager. ServiceNow's AI Readiness Evaluation app assesses catalogs, cases and knowledge articles, and its published pages leave out the CMDB.
| Tool | What it measures or does | Where it lives |
|---|---|---|
| CSDM Data Foundations dashboard | Key CSDM indicators on Foundation, Crawl, Walk, Run and Fly tabs | Plugin com.snc.cmdb.getwell, activated by default in base systems |
| CMDB Health | Health KPIs, including correctness rules for duplicate, orphan and stale CIs | CMDB Workspace; CMDB Health dashboard jobs are disabled by default |
| CMDB success advisor | Data Foundations, Hardware Asset Management and Software Asset Management outcomes | Scoped application, Store app since November 2025 |
| Summarize CMDB readiness skill | AI summary of the success advisor HAM and Data Foundations dashboards, with remediation suggestions | ServiceNow Otto for CMDB, configured in AI Admin Hub (formerly Now Assist Admin Console) |
| CMDB Data Manager | Policy-driven Delete, Retire, Archive, Attestation, Delete CMDB Related Entry and Certification of CIs | CMDB Workspace |
The Data Foundations dashboards are the fastest start. A ServiceNow staff article says the app is "automatically entitled on all sub-prod instances", and data appears only after the scheduled job runs. The dashboards' store release notes mention CSDM 3.0 alignment and no CSDM 5 update, and version 4.5.0 (September 2026) split the large jobs into one job per metric.
The summarize CMDB readiness skill requires CMDB success advisor to be installed and active, and the skill setup page states: "The skill uses the Now LLM Service to generate the summary." AI Admin Hub took its new name in an August 2026 release, per the Now Assist Suite release notes. CMDB success advisor 3.2.0 (October 2026) adds de-duplication and stale-CI remediation agents, and its HAM outcome needs a HAM Pro entitlement, per the success advisor store release notes.
CMDB Health's Correctness KPI applies identification, orphan CI and stale CI rules, the same duplicate and stale CI problems the success advisor agents remediate. CMDB 360 retains per-source history of proposed CI attribute values, which shows which discovery source wrote a disputed value. ServiceNow's data foundation announcement adds Autonomous Data Governance, expected in 2H 2026, which "continuously monitors the data estate and automatically flags quality violations".
ServiceNow's AI Readiness Evaluation automates data-quality assessment across service catalogs, cases and knowledge articles. Catalog data is its own AI prerequisite, covered in Echelon's guide to making a ServiceNow catalog ready for AI agents. For CMDB readiness, use the dashboards in the table above.
How do you move from CSDM 4.0 to CSDM 5.0 safely?
ServiceNow publishes no dedicated CSDM 4.0 to 5.0 migration guide or tool. The white paper gives a generic five-step table-to-table method, ServiceNow staff say to keep Application Service subclasses if you rely on service associations, and the CSDM plugin needs life cycle mapping before activation.
The white paper's migration section (p.58) runs five steps: back up, attribute mapping, identify table dependencies, refactor attributes, and data migration. Attribute mapping sorts each field into Best Practice, Keep, Refactor or Do Not Need (DNN), and the paper flags customizations populated on less than 10% of CIs as candidates to drop. Step 3 uses a dependency fix script by Austin Buono of ServiceNow Customer Outcomes. The paper warns that custom or out-of-box attributes outside the target table hierarchy lose their data, which is why the backup comes first. Archive or delete stale CIs with CMDB Data Manager policies before the migration, so fewer records move.
Three checks keep a 4.0 to 5.0 move safe:
- Keep Application Service subclasses where you need
svc_ci_assoc, per the Yokohama Service Instance guidance. - Edit and activate inactive life cycle mapping records before you activate life cycle migration.
- Rerun the metric collection jobs behind the Data Foundations dashboard tabs after each class change and compare the Crawl and Walk results.
Does bad CMDB data cost more Assists?
No ServiceNow documentation or staff post links CMDB quality to Assist consumption. ServiceNow's assist calculation docs say total assists equal the number of actions multiplied by the assist ratio, and ServiceNow staff price each agentic workflow run in tiers by the number of tools it calls: 25, 50 or 150 assists.
The ServiceNow staff best-practice article on assists sets the tiers at 0–4 tools (Small, 25 assists), 5–8 tools (Medium, 50) and 9–20 tools (Large, 150). Skills inside an agentic workflow are billed as part of the run. The same article says "fewer tools mean less LLM context, faster execution, and lower assist consumption."
ServiceNow's April 2026 packaging announcement put AI, data, security and governance into every ServiceNow offering. The staff article adds that a simple skill such as case summarization involves few actions and consumes one assist.
Inference (ServiceNow documents none of this): an agent that makes extra tool calls to work around a missing or duplicate CI can move a run into a higher tier. The claim that agents on a fractured CMDB retry and loop comes from one non-staff Community author. AI Admin Hub usage alerts on assist consumption are the place to watch for it, alongside how Assists are metered at renewal.
What does Armis change for CMDB population?
ServiceNow completed its Armis acquisition on 20 April 2026 for "approximately $7.75 billion in cash", per ServiceNow's close announcement. The close release routes Armis signals to Context Engine and AI Control Tower (renamed Super Intelligence Control Tower in October 2026) and does not mention the CMDB.
Armis assets reach the CMDB through the Store app Service Graph Connector For Armis, built by Armis Inc. The Armis close announcement says Armis is "integrated with the ServiceNow AI Platform today and remains available as a standalone solution". Forrester noted that Armis Centrix already offered CMDB integrations before the deal. Service Graph Connectors load data through IRE, which ServiceNow says is how connectors identify and classify data before it's loaded into the CMDB. Check IRE identification rules for every class the Armis connector writes to, including OT classes, before you switch it on.
What changed in Zurich, Australia and Brazil for CMDB and CSDM?
Zurich (GA 10 September 2025) removed Design as a CSDM Operational status value. Australia (GA 5 May 2026) listed CMDB success advisor (a Store app since November 2025) and Dynamic IRE as new, and extended IRE de-duplication tasks to lookup and related tables. Brazil has been in early availability since 24 September 2026; ServiceNow lists GA as Q4 2026.
Check the Zurich to Australia CMDB notes for CMDB changes, and Echelon's upgrade guide for features enabled by default.
- Australia removed the Multisource Report Builder and points teams to CMDB 360, per the Australia CMDB notes.
- ServiceNow staff say Dynamic IRE was introduced in Australia and back-ported to Zurich patch 11, and the Brazil CMDB release notes say Brazil enables it by default on zBooted instances.
- Brazil deprecates Service Graph Workspace in favor of CMDB Workspace, per the Brazil CMDB release notes.
Frequently asked questions.
Is CSDM the same as the CMDB?
CSDM and the CMDB are different things. The CMDB is the ServiceNow database that holds configuration items and their relationships. CSDM is the data model standard that says which classes, relationships and domains those records belong in. In CSDM vs CMDB terms, the ServiceNow CMDB holds the data, and CSDM defines its shape so AI agents and other products can read it.
Is there a CSDM 5.1 or a CSDM 6?
No ServiceNow source names a CSDM 5.1 or a CSDM 6 as of 22 October 2026. "CSDM 5.1" appears only as a commenter's wish, and "CSDM 6" only in community comments, one of them a commenter's account of a Knowledge 2025 session. Download the current CSDM 5 whitepaper from ServiceNow's white paper launch post, published in May 2025.
What are the seven CSDM 5 domains?
The seven domains are Foundation, Ideation & Strategy, Design & Planning, Build & Integration, Service Delivery, Service Consumption and Manage Portfolio. Ideation & Strategy is new in this version, and Service Delivery is the renamed Manage Technical Services domain. ServiceNow's CSDM alignment docs describe each domain as a group of related entities.
How do I access the CSDM Data Foundations dashboard?
The CSDM Data Foundations dashboard comes from the Store app CMDB and CSDM Data Foundations Dashboards, plugin com.snc.cmdb.getwell, activated by default in base systems. Open it from CMDB Workspace. Data appears only after the scheduled job runs. Install or update it from the ServiceNow Store listing; version 4.5.0 shipped in September 2026.
Why did Application Service become Service Instance?
ServiceNow relabeled cmdb_ci_service_auto to Service Instance with Yokohama and CSDM 5 so Service Instance can cover data, network, connection, operational process and facility services as well as applications. The Application Service child tables keep their names by population method. ServiceNow's docs page on service instances (application services) lists its creation methods, including Dynamic CI Group, tag-based and Service Mapping discovery.
Is AI Control Tower the same product as Super Intelligence Control Tower?
Super Intelligence Control Tower is the name ServiceNow uses for AI Control Tower in its 15 October 2026 AI Passport announcement, as CIO.com reported the same day. Docs and Community articles still use AI Control Tower. ServiceNow's May 2026 NVIDIA release says the control tower "governs the actions the agent takes" in Project Arc (generally available as Arc since 21 October 2026), the desktop agent covered in what ServiceNow Arc is.
Which CMDB AI agents does ServiceNow Otto for CMDB include?
ServiceNow Otto for CMDB includes the Assess CMDB Impact agentic workflow, which identifies upstream services and CIs, and the CMDB Governance agentic workflow for administrators and service owners. It can also diagnose failed Service Graph Connector import sets and resolve de-duplication tasks with the Manage duplicate CIs skill. Install it from the ServiceNow Store, per the Otto for CMDB release notes.
Echelon builds, tests and deploys work inside ServiceNow instances, and its engineering team describes platform context as emergent rather than documented. Echelon's IT Process Graph maps how work moves across systems and can show every process step a planned change would touch, giving its agents context on how each instance is configured and used.
To see Echelon build in your own instance, book a scoping call.
