---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-asset-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Model categories

# Model categories {#ariaid-title1}

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

Model categories define the relationships between enterprise model classes, enterprise asset classes, and Configuration Management Database (CMDB) CI classes in Enterprise Asset Management. Model categories connect every enterprise asset to the correct model class, asset class, and CI class.

## Overview of model categories {#model-hierarchy__section_l2l_1df_3jc}

When you create an enterprise model, you assign it to a model category. The assignment determines:

* The model class for the model record
* The asset class for assets created from that model
* The CI class for the corresponding CMDB CI record
{#model-hierarchy__ul_dn2_ydf_3jc}  

Model category assignments follow these rules:

* Multiple model categories can share the same model class or asset class.
* A CI class can be assigned to only one model category, and this assignment is optional.
{#model-hierarchy__ul_jtq_n2f_3jc}

## Model category functions {#model-hierarchy__section_ukd_y2f_3jc}

Beyond routing records into the correct classes, model categories serve three purposes:

1. Asset and CI record creation: EAM uses the model category to place assets in the correct asset class and create linked CI records in the correct CI class.
2. Bi-directional asset-CI synchronization: The model category mapping keeps asset and CI records in sync. Changes to state, location, or assignment are reflected in both records.
3. Discovery and identification rules: Model categories use configured CMDB IRE rules to define asset unique identifiers. These identifiers determine how the system recognizes assets when data arrives from Discovery or Procurement.
{#model-hierarchy__ol_ozm_y2f_3jc}

## Parent and child model categories {#model-hierarchy__section_mpq_fgf_3jc}

Model categories are organized in a two-tier hierarchy. Parent model categories represent the nine top-level industry domains. Child model categories sit
beneath a parent and carry the actual class mappings assigned to model records.

For the complete list of available model categories and their corresponding CMDB CI class, asset class, and model class, see [Enterprise model categories and corresponding classes](https://servicenow-prod.fluidtopics.net/G2drqI_Cug6~kd2MsnGY4A "Enterprise model categories and their corresponding Configuration Management Database (CMDB) configuration item (CI), asset, and model classes.").  
Important:  
Use only the existing top-level parent model categories.

## Creating custom model categories {#model-hierarchy__section_i2j_vhf_3jc}

If none of the existing child model categories meet your needs, you can create a custom child category under an existing parent. When creating a child category, you specify the parent model category, model class, asset class,
and optionally a CI class. For details, see [Create model categories](https://servicenow-prod.fluidtopics.net/APhT13AlXrwrALmmTvEwfQ "You can create model categories for the Enterprise Asset Management application.")  
Important:  
Custom model categories must be children of one of the nine seeded parent categories. Creating new top-tier parent categories is not supported.