---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# CMDB schema model

# CMDB schema model {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

The CMDB schema model is a series of connected tables that contain all the assets and business services controlled by a company and its configurations.
Related ServiceNow® Store apps and reference information:

* [CMDB tables descriptions](https://www.servicenow.com/docs/1GLrH0vZKHQqi0lHfIjuTw "List of tables in the CMDB in a base system with its name, label, and a description of the type of information that is stored in the table."): Descriptions of key CMDB tables in the base system.
* [CMDB CI Class Models](https://www.servicenow.com/docs/darqAyORPOpoURCcjTGVXA "The CMDB contains base-system classes that store data about configuration items (CIs). The CMDB CI Class Models ServiceNow Store app adds class models that extend the CMDB class hierarchy, including class descriptions, identification rules, identifier entries, and dependent relationships if applicable."): A ServiceNow Store app that adds class models that extend the base CMDB class hierarchy. This includes class descriptions, identification rules, identifier entries, and dependent relationships if applicable. You can then use the added classes as any other CMDB base class.
* [Populating the CMDB](https://www.servicenow.com/docs/RFEkBbd3mAJUu78e4wYSRA "You can populate the CMDB by using Discovery, by using the IntegrationHub ETL or Import Sets to import and integrate data from a third-party source, by integrating with an external CMDB, or by manually creating CIs."): Information about the various options for populating the CMDB.
* [Discovery patterns](https://www.servicenow.com/docs/access?context=c_MappingPatternsCustomization&version=australia&pubname=australia-it-operations-management&ft:locale=en-US): A ServiceNow Store app that provides a library of Discovery patterns for discovering specific devices and applications in the industry.
* [Getting started with Service Graph Connectors](https://www.servicenow.com/docs/llR5whccV6~8Oi~Q_e8~xQ "Service Graph Connectors, including API Service Graph Connectors, are predefined integrations that ingest third-party data and API data into the Configuration Management Database (CMDB) from various domains, such as security, servers, software or monitoring, Internet of Things (IoT), and cloud."): ServiceNow Store apps that provide pre-defined integrations for importing and integrating common third-party data into CMDB classes. Also includes the [IntegrationHub ETL](https://www.servicenow.com/docs/_zqPaqbG5vaxHRfrZ6bq7Q "Use the IntegrationHub ETL store app to create and manage ETL transform maps, which integrate third-party data into the CMDB or into non-CMDB tables without compromising the integrity of data. IntegrationHub ETL provides a simplified user interface that guides you through the integration process end-to-end, including a test integration run of sample data.") wizard for creating new ETL transform maps.
{#c_ConfigurationManagementDatabase__ul_lhp_xgx_wpb}

CMDB tables contain information about computers and devices on the network, software contracts and licenses, business services, and so on. The IT desk can use the CMDB to better understand their network users' equipment, and the
relationships between them. The CMDB can also be referenced by other processes within the system.

Applications such as Asset Management and Contract Management, operate in conjunction with the CMDB. Asset Management and Software Asset Management link to CMDB all assets, hardware, software, assets in stock, as well as records for manufacturers and vendors. The Contract Management application contains information about contracts, including
leases, service contracts, purchase orders, warranties, and software licenses. The Configuration Management Database (CMDB) application has a focus on operation.

For more background information about the CMDB, see the ServiceNow Community post at [CMDB 101- What is a configuration management database and why do you need one?](https://community.servicenow.com/community?id=community_blog&sys_id=e913125fdbd9d7404837f3231f9619de).

## Key class categories {#c_ConfigurationManagementDatabase__section_plq_xzk_4hc}

The following items are class categories that are typically key in organizations. You can for example, use this list as a general guideline for designating classes as Principal Class so you can track health and pay attention to the most important classes in your CMDB:

* Servers (physical and virtual): Classes that are typically well-understood, relatively stable, and which form the backbone of most infrastructure.
* Databases: Classes of high business impact, critical for incident triage, and relatively straightforward to discover and maintain.
* Network devices (core infrastructure): Classes such as routers, switches, firewalls, and load balancers---hardware that connects everything. If setting as Principal Class, then as a general guideline, prioritize core and critical devices over access switches.
* Application servers.
* Storage.

{#c_ConfigurationManagementDatabase__ul_mnz_c1l_4hc}For more information, see [Principal Class](https://www.servicenow.com/docs/ENE4G2KZHXZ4qUyd2nyztg "A Principal Class is a designation for those CMDB classes that are most critical for foundational data health and governance in the organization. Those classes are then prioritized for tracking, health, certification, lifecycle management, and class list views.").

## Key CMDB classes {#c_ConfigurationManagementDatabase__section_ilb_vcl_wz}

Key classes in the CMDB:

* The Base Configuration Item \[cmdb\] class, which is the core CMDB table for non IT CIs (descending classes are non IT CIs).
* The core Configuration Item \[cmdb_ci\] class, which stores the basic attributes of all the CIs. The sn_cmdb_admin, sn_cmdb_editor, asset, admin, or itil user role is required to access this table (descending classes are IT CIs).
* The CI Relationship \[cmdb_rel_ci\] class, which defines all relationships between CIs.

{#c_ConfigurationManagementDatabase__ul_p5k_mkr_bp}

The Configuration Item class is extended to other classes, such as Database \[cmdb_ci_database\] and Computer \[cmdb_ci_computer\]. The Computer class is extended to the Server \[cmdb_ci_server\] class, which is extended to the UNIX Server \[cmdb_ci_unix_server\] class, and so on.  
Note:  
The Base Configuration Item \[cmdb\] class uses the table per partition extension model, which has different behaviors for replicating and deriving information than other extended tables. See [Table extension and classes](https://www.servicenow.com/docs/access?context=table-extension-and-classes&version=australia&pubname=australia-platform-administration&ft:locale=en-US).  
You can use the schema map to view more details of tables and their relationships:

1. Navigate to System DefinitionTables \& Columns.
2. Select a table and then select Schema Map.
{#c_ConfigurationManagementDatabase__ol_z3w_tkr_bp}  
Note:  
CIs not extended from the Configuration Item \[cmdb_ci\] table, are not displayed in Dependency Views maps and in CI relation formatters.

## CI attributes {#c_ConfigurationManagementDatabase__section_nv4_ycl_wz}

Attributes apply to all the CIs in a classification. To change attribute values for a CI, edit
the appropriate CI. To add a unique attribute to a class, extend the class table and create a
new classification for that CI.

The position of a CI in a classification hierarchy is determined by the attributes it shares
with the CIs below it. Each time a CI has a single different attribute from its parent, the
classification hierarchy branches.

For example, servers have different attributes from computers, which include workstations and
laptops. Linux servers and UNIX servers have different attributes from
the parent server classification and from each other, so they occupy separate branches in the
hierarchy.

*[\>]: and then