ServiceNow Australia Release – CMDB and CSDM Enhancements

John Zhang1

ServiceNow’s Australia release (GA May 5, 2026) introduces significant enhancements to the Configuration Management Database (CMDB), with a strong focus on AI-driven automation, Dynamic Identification and Reconciliation Engine (IRE), data quality, service context, Service Graph Workspace, and improved CMDB administration. The release continues the broader evolution of ServiceNow from a CI-centric CMDB toward a more automated, service-centric, and CSDM-aligned platform.

1. Major CMDB Enhancements

Service Graph Workspace / CMDB Workspace

One of the most significant changes is the evolution of the CMDB user experience through Service Graph Workspace, bundled with the CMDB Workspace store application.

It provides a centralized experience for:

CMDB data
Companies
Locations
Users
Configuration Items (CIs)
CI relationships
Data quality
Foundation data

A key improvement is context-based navigation and search. Users can search and explore CMDB information through business-oriented contexts mapped to CI classes instead of needing to understand the underlying CMDB class hierarchy.

This represents a shift from navigating technically through structures such as:

cmdb_ci → cmdb_ci_server → cmdb_ci_linux_server toward a more business- and context-oriented CMDB experience.

Organizations upgrading to Australia should also evaluate existing CMDB Workspace customizations and determine which should be replaced with the new Service Graph Workspace capabilities.

2. Dynamic Identification and Reconciliation Engine (Dynamic IRE)

Dynamic IRE is one of the most important CMDB enhancements highlighted in the Australia release.

Traditionally, organizations often need to maintain: Data Source → Payload → Identification Rule → CI Matching → Reconciliation. Dynamic IRE reduces the dependency on manually created identification rules and is designed to improve CI identification across multiple data sources.

The expected benefits include:

Less manually maintained IRE configuration
Improved CI identification
Reduced duplicate CI creation
Reduced CMDB administration
Better handling of CI identification across multiple sources

The Australia documentation identifies Dynamic IRE as being scoped to cmdb_ci_hardware and its descendants.

Recommended architecture assessment

Before broadly adopting Dynamic IRE, CMDB architects should review:

Identification rules
CI identifiers
Lookup identifiers
Data source configurations
Transform Maps
IntegrationHub ETL mappings
Import Sets
Service Graph Connectors
Custom scripts used for CI identification
Existing duplicate CI populations

The objective should be to determine which existing custom identification configurations can be simplified or retired rather than simply introducing Dynamic IRE alongside unnecessary legacy configurations.

3. AI-Assisted CMDB Remediation and Deduplication

Australia expands AI assistance for CMDB remediation, particularly around duplicate CIs.

De-duplication Task Resolution Assistant

The new De-duplication Task Resolution Assistant uses AI to help CMDB administrators resolve duplicate CI tasks. The AI can preselect remediation choices, such as identifying which CI should become the authoritative or "main" CI, while providing reasoning before the administrator commits the change.

Automated de-duplication tasks

Australia also introduces improvements including:

Automatic generation of de-duplication tasks for lookup and related tables during IRE identification
Remediation of duplicate related items in lookup tables
AI-assisted remediation options
The ability to disable related-table workflows during remediation when duplicate CI merges are blocked by business rules or errors

A typical remediation process can therefore move from:

Duplicate CIs → Manual analysis → Manual selection → Manual remediation toward:

Duplicate CIs → AI-assisted analysis → Recommended authoritative CI → Administrator approval → Remediation

For example, multiple records such as:

Server A
Server A1
Server-A
server01.company.com

can be analyzed to determine whether they represent the same physical or logical CI.

AI should, however, assist rather than bypass CMDB governance. The CMDB administrator or data steward should remain responsible for approving significant remediation decisions.

4. CMDB Success Advisor

CMDB Success Advisor provides dashboards, recommendations, and remediation guidance designed to help organizations achieve target outcomes across:

Data Foundations
Hardware Asset Management (HAM)
Software Asset Management (SAM)
Principal CI classes
Hardware assets
Software installations

The capability is accessible through Service Graph Workspace and is intended to proactively identify data-quality gaps and improvement opportunities.

For a CMDB governance program, it can support a continuous improvement cycle:

CMDB Success Advisor → Identify Gaps → Prioritize → Remediate → Measure Improvement

This is preferable to treating CMDB data quality as a one-time cleanup exercise.

5. Enhanced CI Creation and Lookup Identifiers

Australia enhances manual CI creation by supporting lookup identifiers and mandatory attributes.

This helps improve:

CI identification
Data consistency
IRE processing
Manual CI creation
Prevention of duplicate records

Organizations should review existing manual CI creation processes and determine whether users can be moved toward standardized lookup identifiers and governed CI creation practices.

6. CMDB Query Builder V2

Australia expands CMDB Query Builder V2 execution-mode support and improves performance for complex CMDB queries.

Benefits include:

More query structures
Improved query performance
Better handling of complex CMDB queries

Some limitations remain, including gaps involving certain related-list conditions, NOT/filter combinations, some Service Mapping relationships, and OR conditions unless enabled through the appropriate property.

7. CMDB 360 and Multisource Data

CMDB 360 provides multisource data visibility and reporting capabilities.

It replaces the removed Multisource Report Builder and provides a more integrated approach to viewing data from multiple sources within the CMDB workspace experience.

This is particularly important for organizations that receive CI information from multiple discovery tools, integrations, asset systems, and other data sources.

8. Domain Separation Enhancements

Australia expands CMDB domain separation support to additional tables, including:

cmdb_key_value
cmdb_print_queue_instance
cmdb_software_instance
samp_client_access
samp_oracle_options

These changes improve data isolation for organizations operating CMDB environments with domain separation requirements.

9. CMDB Security and Access Changes

Australia introduces several security and access-related changes.

Role changes

The elevated-role requirements are adjusted so that:

sn_cmdb_admin receives capabilities that previously required higher administrative roles.
sn_cmdb_editor receives capabilities that previously required itil.

Granular read-only protection

A new platform-wide read_only_option field provides more granular read-only protection, including options such as:

strict_read_only
client_script_modifiable

These capabilities also affect CMDB tables and provide stronger protection against unintended modification while maintaining backward compatibility.

Upgrade consideration

Organizations should also consider potential longer upgrade times associated with the new composite index on cmdb_ci.

10. CSDM Enhancements and Direction

The Australia release continues ServiceNow's broader investment in CSDM-aligned service modeling and Foundation data management. The strategic direction is to strengthen relationships between:

Business Applications → Application Services → Technical Services → Technology → Infrastructure CIs

This supports the broader objective of moving from a primarily CI-centric CMDB toward a service-centric CMDB.

CSDM 5.0

The source material identifies CSDM 5.0 as a broader data-model evolution rather than a feature uniquely introduced by the Australia release. CSDM 5.0 material referenced in the source includes areas such as:

Additional CSDM domain concepts
AI-related CI classes such as AI Function and AI Application
SBOM tracking
Operational Technology (OT) classes

Therefore, CSDM 5.0 should be treated as part of the broader CSDM evolution rather than automatically classified as an Australia-specific release feature.

11. AI-Assisted CSDM Service Delivery Map

The Australia roadmap includes AI-oriented capabilities for generating a CSDM Service Delivery Map.

Conceptually, the platform can increasingly assist with identifying and visualizing relationships such as:

Business Application
↓
Application Service
↓
Technical Service / Technology
↓
Infrastructure CIs

This capability supports the CSDM objective of connecting technical infrastructure to the business and services that depend upon it.

For CSDM architects, the strategic value is significant: the CMDB becomes less focused on simply answering "What CIs do we have?" and increasingly capable of answering:

What business application does this CI support?
What application service does it belong to?
What technical service supports that application service?
What business service depends on it?
Who owns the service?
What relationships exist across the service model?

12. Service Mapping and ITOM Enhancements

Australia also continues the evolution of ITOM and Service Mapping capabilities.

AI-powered Service Mapping

Automated agents can assist with generating service maps from machine-learning candidates and linking Business Applications to discovered Application Services.

This can reduce:

Manual service-map creation
Manual relationship maintenance
Service-mapping administration

Service Mapping MCP Tools

Service Mapping also introduces Model Context Protocol (MCP) capabilities that enable conversational and dynamic querying of:

Live service topologies
CI relationships
Service-mapping data
Service dependencies

This creates opportunities for external AI platforms and conversational interfaces to interact with ServiceNow service-topology information.

13. What CMDB/CSDM Architects Should Do for an Australia Upgrade

For organizations preparing for the Australia release, CMDB/CSDM work should be organized into six major workstreams.

Workstream 1 — IRE

Review:

Existing identification rules
Dynamic IRE opportunities
Data-source/native keys
CI identifiers
Lookup identifiers
Duplicate CI population
Custom identification scripts

The objective is to simplify the identification architecture and reduce unnecessary customization.

Workstream 2 — CMDB Data Quality

Establish a baseline for:

Completeness
Correctness
Compliance
Relationships
Duplicate CIs
Stale CIs
Orphan CIs

Use CMDB Success Advisor and other data-quality capabilities to establish a continuous improvement process.

Workstream 3 — CSDM

Review:

Business Applications
Application Services
Service Offerings
Technical Services
Business Services
Technology Management
Service Owners
Service relationships

Ensure that the CMDB is aligned with the organization's CSDM service model

.

Workstream 4 — Service Graph Workspace

Evaluate:

Existing CMDB Workspace customizations
Administrator experience
Data-owner experience
Context-based navigation
Foundation data management

Determine which legacy customizations can be retired in favor of ServiceNow's newer workspace capabilities.

Workstream 5 — AI and Now Assist

Evaluate opportunities for:

Duplicate CI remediation
CMDB troubleshooting
Data-quality recommendations
De-duplication task resolution
Text-to-action capabilities
CSDM Service Delivery Map generation
AI-assisted Service Mapping

Workstream 6 — CMDB/CSDM Governance

Establish clear accountability across:

Data Owner → Data Steward → CMDB Administrator → CSDM Architect → Platform Governance

Define measurable KPIs and establish an ongoing governance process rather than treating CMDB remediation as a one-time project.

14. Top CMDB/CSDM Features to Highlight

For an Australia Release CMDB/CSDM presentation or architect interview, the following capabilities are the most important to highlight:

Dynamic IRE
Service Graph Workspace / CMDB Workspace enhancements
CMDB Success Advisor
Now Assist for CMDB remediation
Automated de-duplication task generation
De-duplication Task Resolution Assistant
Enhanced CI creation and lookup identifiers
CMDB 360 / multisource data management
Enhanced CMDB Query Builder V2
Enhanced Foundation data management
AI-assisted CSDM Service Delivery Map generation
AI-powered Service Mapping
Service Mapping MCP capabilities
Expanded domain separation
Granular read-only security controls

15. Overall Strategic Impact

The Australia release represents an important step in the evolution of ServiceNow CMDB.

The strategic direction can be summarized as:

Traditional CMDB

Collect CIs → Maintain Identification Rules → Manage Relationships → Perform Manual Cleanup

↓

Australia-era CMDB

Automated Identification → AI-Assisted Remediation → Continuous Data Quality → Service Context → CSDM-Aligned Service Modeling → AI-Assisted Service Mapping

The most important architectural change is therefore not simply the introduction of individual features. It is the movement toward a more automated, intelligent, service-centric CMDB, where Dynamic IRE reduces manual identification configuration, AI assists with remediation, Service Graph Workspace provides business/context-oriented access, CMDB Success Advisor drives continuous data-quality improvement, and CSDM/service mapping capabilities connect infrastructure data to business services.

For a CMDB/CSDM architect, the Australia upgrade should therefore be approached as an opportunity to simplify the existing CMDB architecture, reduce technical debt and customization, improve data quality, strengthen CSDM alignment, and take advantage of AI-driven automation rather than simply upgrading the platform version.