---
sourceDocument: Australia Asset Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-asset-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Asset Management

ft:clusterId :

    - itam

bundleId :

    - itam

workflow :

    - Technology


---

# Software Component Model table

# Software Component Model table {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Software Component Model table

TheSoftware Component Model \[cmdbsoftwarecomponentmodel\]table in ServiceNow stores records of software component models used across various industries and solutions on the platform.
It extends theSystem Component Model \[cmdbswcomponentmodel\]table from the Data Foundation Model application.
Show full answer Show less  
Records in this table are automatically created when a discovery model is normalized with a version set or manually normalized. A scheduled script generates these models based on the system property **com.snc.sam.softwarecomponent.choice.versionlevel** , which controls the version granularity. Available version levels are **MAJOR** , **FULL** , **BOTH** (default), and **NONE**, and must be set in lowercase.

When both FULL and MAJOR versions exist, two records are created; if only MAJOR exists, only one record is created. Manual creation of software component model records is also supported, with or without referencing the Software Product table depending on whether Software Asset Management applications are installed.

## Upgrade Information

Upgrading to the Zurich release or later triggers a one-time scheduled job, **SAM - Generate software component model**, which generates component model records for all existing normalized discovery models. Thereafter, a business rule automatically creates new records whenever a new discovery model is normalized.

Note that the Software Discovery Model table is available only if Basic or Professional Software Asset Management applications are active in your instance.

## Discovery Model Considerations

* **System property changes:** Existing software component models retain their original settings when system property preferences change; only new models adopt updated settings.
* **Model deletion/modification:** Deleting or modifying a software component model does not trigger automatic recreation from the discovery model.
* **Manual re-normalization:** When discovery models are manually normalized with new values, existing component models remain unchanged. A new component model is created only if one does not already exist for those values.  
The Software Component Model \[cmdb_software_component_model\] table stores component model records that serves industries and use cases across different solutions on the ServiceNow Platform.

## Overview of Software Component Model table {#software-component-model-table__section_vyz_2r1_phc}

The Software Component Model table extends from the System Component Model \[cmdb_sw_component_model\] table that resides in the Data Foundation Model (sn_cmdb_foundation) application. The Software Component Model table can consist
of various entities.  
A software component model record is automatically created whenever a discovery model meets either of the following conditions:

* Is normalized with a normalized version set.
* Is manually normalized with a normalized version set.
{#software-component-model-table__ul_bdx_zhl_qhc}  
A script runs to generate software component models from the normalized discovery models. This script uses the system property, com.snc.sam.software_component.choice.version_level, to determine the granularity of the normalized version. You can configure this system property to set the version level options, which include the following versions:

* MAJOR
* FULL
* BOTH
* NONE

{#software-component-model-table__ul_cdx_zhl_qhc}  
Note:  
The system property is configured to the BOTH version by default. You can modify this setting by selecting any of the other available options. When entering values, ensure they are in lowercase format. As an example, to set the system property to NONE, enter "none" in the value field.

Two records are created in the Software Model Component table when a FULL version and a MAJOR version exist for the normalized discovery model. However, only one record is created if only the MAJOR version exists.

You can also manually create a software component model record in the Software Component Model \[cmdb_software_component_model\] table. If you have the Basic Software Asset Management or the Software Asset Management Professional application while creating the record, you can reference the Software Product \[samp_sw_product\] table. If you are not using the Software Asset Management application, you need to type in the
software product name.

## Upgrade information {#software-component-model-table__section_bv3_gr1_phc}

When you upgrade to Zurich release and later releases, the scheduled job, SAM - Generate software component model does a one time run to generate component model records for all existing normalized discovery
models which are then stored in the Software Component Model table.  
After the upgrade, every time a new discovery model is normalized, the business rule, Create software component model that runs on the Software discovery model \[cmdb_sam_sw_discovery_model\] table gets triggered and automatically creates new software component model records for the new normalized discovery models.  
Note:  
The Software Discovery Model table is available if you have Basic Software Asset Management or the Software Asset Management Professional application running on your ServiceNow instance.

## Discovery model considerations {#software-component-model-table__section_dch_35p_phc}

The following are some considerations to keep in mind for discovery models:

* System property changes: When a system property preference changes, the existing software component models retain their original settings. Only newly created version models adopt the updated system property.
* Model deletion or modification: If you delete or modify a software component model, the system won't recreate it from the original discovery model.
* Manual re-normalization: When a discovery model is manually normalized with new values, the existing software component model remains as is. The system creates a new software component model only if one does not already exist.
{#software-component-model-table__ul_tpd_l5p_phc}