---
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


---

# Software model relationship to software installation

# Software model relationship to software installation {#ariaid-title1}

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

Associating each software installation with a software model lets you perform audit
reporting of licensable and non-licensable software.

## Overview {#swmodel-swinstall-rel__section_et3_5n1_ltb}

Software models are automatically created for licensable and non-licensable products if the following system properties are enabled:

* com.snc.samp.automaticsmrcreation: for licensable products
* com.snc.samp.automaticsmcreation: for non-licensable products
{#swmodel-swinstall-rel__ul_dnh_vn1_ltb}

If the system properties are enabled and a discovery model match exists, even if the match is
generic, a software model will not be created. If the system properties are not enabled, the
software model is just matched to a discovery model; no software models are created.

A match is made to the most specific software model. If no specific software model exists for
the discovery model, then the match is made to the most generic software model.

During the matching process, if a matching software model is found, but it has an install
condition on it then it's not considered to be a match. In such a scenario, a software model is
automatically created without an install condition.

For each normalized publisher and normalized product pair in the Software Discovery Model
(cmdb_sam_sw_discovery_model) table, the scheduled job, SAM -- Discovery Model to Software Model matching, gets all software models with matching publisher and
product. If the software model has no install condition, subscription condition, or DB option,
the system gets matching discovery models with normalized publisher, normalized product,
normalized edition, and normalized version values. Once a match is found, the software model
reference is put on the software model column in the Software Discovery Model
\[cmdb_sam_sw_discovery_model\] table.

## Manually set software model {#swmodel-swinstall-rel__section_dvk_141_ltb}

If you choose to match on a more generic software model than what the scheduled job
SAM -- Discovery Model to Software Model matching sets, you can manually
set the desired software model in the form view on the Software Discovery Model
(cmdb_sam_sw_discovery_model) table. The Automatically matched column becomes unchecked.

If a software model is set and the Automatically matched column's value is false, the
scheduled job will not override the software model value on subsequent executions.

## Sample matches {#swmodel-swinstall-rel__section_oyg_xq1_ltb}

The following are some sample scenarios of software model and discovery model matches.  
{#swmodel-swinstall-rel__table_akz_pyf_ltb__entry__3}

| Discovery model | Software models | Matches with |
|-|-|-|
| SQL Server 2019 Enterprise | * SQL Server 2019 Enterprise * SQL Server 2019 {#swmodel-swinstall-rel__ul_hb1_vyf_ltb} | SQL Server 2019 Enterprise software model |
| SQL Server 2019 Enterprise | * SQL Server 2019 Enterprise with install conditions * SQL Server 2019 (Edition is anything) {#swmodel-swinstall-rel__ul_ugw_khp_4tb} | SQL Server 2019 software model​​ |
| SQL Server 2019 | SQL Server 2019 with install conditions (Edition is anything)​ | No match found. If the system property is enabled, a new software model will be created: SQL Server Enterprise (Version is anything)​. |
[ ]

{#swmodel-swinstall-rel__table_akz_pyf_ltb}