Home Orlando Software Asset Management Software Asset Management Software Asset Management Software Asset Management references Software model fields

Software model fields

Software Model form and related list field descriptions.

Software Model form


Field	Description
Display name	Name of the model. The system property glide.cmdb_model.display_name.shorten controls how software model display names are generated. Users with the admin role can configure this property. The default format is publisher + product + version + edition + platform + language. If the Platform or Language fields aren't set to Anything, the values are appended.
Publisher	Publisher of the software. You can use the lookup list provided. Note: Publisher is a reference to the company [core_company] table. Only companies that you are using internally are shown.
Product	Software product name. The same lookup list provided on the Software Discovery Models form. You can create a custom product from the lookup list, if desired. Note: If the relationship between the software publisher [samp_sw_publisher] and company [core_company] tables is not correct, products for that publisher may not be shown. If the publisher and product do not exist, you can Add a custom software product.
Discovery map	Set of conditions that determines which software discovery models get mapped to the software models. Purchased rights are only applied to software discovery models that meet the condition. This matching is important for reconciliation. Discovery models with predefined suites are indicated in the Suite defined field. A value of Yes indicates that the discovery model is a suite parent. You can use the discovery maps provided, or you can choose to specify the condition information directly instead. A user with the sam_admin role can choose to create a custom discovery map. When you select a discovery map, you may encounter a message: `Many underlying software models will be created. These might be part of suite components, downgrade rights or next version. Please validate on completion`. The message appears only if there are greater than or equal to 50 suite components for the software model and if any of the following conditions are met: A software model does not exist for any suite component A software model does not exist for any downgrade right A software model does not exist for the next version Note: If you change the discovery map in an existing software model, a warning message appears. The warning message informs you that the downgrade rights on the software model and on the related entitlements also change. For example, if you change the discovery map on a software model from DMAP1 to DMAP2, and save the software model, then all the downgrade rights associated with DMAP1 are removed from the software model and the downgrade rights associated with DMAP2 are populated. However, if the value in the Agreement type field in the Software Entitlement form layout is Generic, the downgrade rights for that entitlement don't change. If the discovery map has a lifecycle definition defined, those settings are automatically populated in the Software Model Lifecycles related list. You can verify which discovery models get mapped to the software model by clicking the Show Matching Discovery Models related link. If the Publisher and Product fields are empty, the values are automatically populated according to the discovery map.
Version condition	Condition qualifier for the Version field. starts with is is anything The default is is anything.
Edition condition	Condition qualifier for the Edition field. starts with is is anything The default is is anything.
Platform	Platform of the software product to use when searching for the normalized discovery model. The default is Anything for Windows, Mac, UNIX.
Language	Language of the software product to use when searching for the normalized discovery model, which is populated once it has been normalized or added manually. The default is Anything.
License under management	Option that indicates you want to manage licenses for that software. If you clear the option, your software model won't be included in your reconciliation results. The value is set to true by default. It is also set to true for any software models that have been upgraded. If you upgrade and have software models with this option selected, you can do a bulk update and clear the License Under Management option from any software models you don’t want to include in your reconciliation results. When you run reconciliation again, only the software models with the option still selected will display in your results.
Software install condition	Only software installations that meet this software discovery map condition are counted during reconciliation. If needed, specify a subset of software installations that should be counted during reconciliation.
Product classification	The official United Nations Standard Products and Services Code (UNSPSC) classification.
Product type	Product type values include: Child, Driver, Licensable, Not Licensable, Patch, and Unknown. Note: The reconciliation process only considers software products that are licensable.
Version	Version of the software product. Required if the version condition value is [starts with] or [is-].
Edition	Edition of the software product to use when searching for the normalized discovery model. Required if the edition condition value is [starts with] or [is].

General tab


Field	Description
Short description	A brief description of the model.
Status	The status of the model. The options are In Production, Retired, and Sold.
Cost	The cost of a single unit of the software.
Owner	The person responsible for the model.
Next version	Reference to another software model of the same manufacturer which represents the next version of the product. The next version is defined on the discovery map and is part of the content service. The next version is populated on the software model in either of the two ways: When you create a software model or update the discovery map on a software model, a business rule is triggered when you click Save. The next version is populated if the discovery map has a next version defined for it. If the content service has the next version specified for the associated discovery map on an existing software model, the next version is populated when the schedule job, SAM- Create downgrades/upgrades for a software entitlement runs. However, if you entered a value in the Next version field, that value is not overridden. If a software model for the next version does not exist, a software model is automatically created. If the newly created software model consists of downgrade rights and child components, these components are automatically created. When the new software model for the next version is created or if one exists, the license entitlements from the current software model are moved over and associated with the software model for the next version.
Certified	Option to indicate that the software model is approved for use.
Blacklisted	Option for blacklisting the software model. Blacklisting identifies software that you should not install in your environment (inappropriate software, or software with vulnerabilities, for example). If the removal candidates don't exist, a scheduled job runs nightly that creates removal candidates for blacklisted software.

Suite Components tab


Field	Description
Allow automated content update	Option allowing ServiceNow to automatically send updated suite definitions to your instance through weekly content updates.
Inference percent	The percentage of suite components that must be present on a system to count as a suite. Used for suite management. Software installations on the same device and assigned to same user that meets the inference percent could be considered a suite. For example, if the inference percent for a suite of five products is set to 60% and three software installs on the same device, or assigned to the same user, are discovered, all three installations are considered a suite.
Suite child	The child product or products of the suite. For example, Microsoft Word and Microsoft Excel are child products of Microsoft Office.
Mandatory	Requirement of a suite component. A suite component can be Optional, Always Mandatory, or Mandatory Group. Set to Always Mandatory if the software must be installed to count the model as a suite.
Suite relationship assumed	Relationship that indicates that multiple software models exist for one or more of the suite components. Therefore, the relationship between suite parent and suite component was assumed. Review the created suite components to ensure the relationship is correct.

Suite Parents tab


	Description
Suite parent	The parent suites to which the software is assigned. For example, the parent suite for several common Microsoft products is a version of Microsoft Office.
Mandatory	Requirement of a suite component. A suite component can be Optional, Always Mandatory, or Mandatory Group. Set to Always Mandatory if the software must be installed to count the model as a suite.
Suite relationship assumed	Relationship that indicates that multiple software models exist for one or more of the suite components, therefore the relationship between suite parent and suite component was assumed. Review the created suite components to ensure the relationship is correct.

Product Catalog tab


Field	Description
Catalog Item	Information about the model as it appears in the product catalog and service catalog. Information only appears if the model has been published to the product catalog.
Description	Description of the software model as it appears in the product catalog.
Picture	Image of the software logo can be added. This logo appears in the service catalog if the software model is published.

Software Model Lifecycle related list


Field	Description
Software model	Name of software model.
Lifecycle type	Lifecycle type values include: Internal Publisher
Lifecycle phase	Lifecycle phase values include: Pre Release General Availability Date the software became generally available to the market. Upgrade Only shown when the Lifecycle type field is Internal. End of Life Date the software was no longer supported by the publisher. End of Support End of Extended Support
Source	Source of the lifecycle model. If the record is created manually, it's set to Internal. If it's created automatically, the field is set to ServiceNow.
Description	Description of the software model lifecycle.
Phase start date	Date the lifecycle phase starts.
Phase end date	Date the lifecycle phase ends.
Risk	The risk level to an organization with regards to the lifecycle phase. For example, the risk for the end of support phase for a publisher maybe moderate or the end of life phase maybe high. Risk type values include: Very High High Moderate Low None

Override License Cost related list

Table 1.
Field	Description
Software Model	The software model that the software entitlement belongs to.
Metric Group	The metric group the software entitlement belongs to.
License Metric	The license metric specified for the software entitlement.
License Cost	Cost of the license.
License & Maintenance Cost	Cost of the license combined with cost of the maintenance license. Note: Specify a license cost or a license and maintenance cost, to override the true-up cost during reconciliation. If no values are specified in the License Cost or License & Maintenance Costfields, the software entitlement cost is used for true-up cost calculations. Note: For SaaS licenses, only the license cost applies. The license & maintenance cost does not apply.

Metric Attributes related list


Field	Description
Software model	Software model associated with the metric attributes.
Metric group	Grouping for the software metric. If you have optional publisher packs installed that the software applies to, those options are shown. Otherwise, the metric group value is Common.
License metric	The license metric that the software license is counted against when reconciliation is run (per user, per device, for example).
Description	Attribute type description that is based on the license metric value.
Attribute	Attribute type for reconciling entitlement license metrics. Maximum active OSEs per server Maximum installs per OSE Maximum installs per right: For Per User, Per Device, Per Named User, and Per Named Device Maximum processors per right Minimum users per processor Minimum cores per processor Minimum cores per server
Attribute value	Value of the attribute (integer).
Attribute value is unlimited	Option for setting the attribute as unlimited.

Client Access related list

Table 2.
Field	Description
Name	Unique name for the client access record.
Software model	Software model for the client access record.
Database instance	Oracle database instance. Note: Only shown for Oracle Named User Plus license metric.
Total device count	Number of unique devices allowed to access the product.
Total user count	Number of unique users allowed to access the product.
Total user/device count	Number of user/device licenses that are accessed a user or a shared device. Note: Only shown when Citrix is specified.

Downgrade Rights related list


Field	Description
Parent software model	Parent (or the topmost hierarchy) of the software model.
Software model	Software model associated with the downgrade rights. Based on the parent software model that you select, the related software models appear in the list. For example, if you select Microsoft SQL Server 2012 Standard as the parent software model, only Microsoft-related software models appear in the list.
Source	Source of the downgrade rights. If the record is created manually, it's set to Internal. If it's created automatically, the field is set to ServiceNow.
Active	Option that indicates if the downgrade rights on the software model are active or not. If needed, you can deactivate the downgrade rights. Only the active downgrade rights appear in the field. To see all the downgrade rights, remove the Active condition from the filter. If you deactivate a downgrade right on a software model, the change is propagated to the related software entitlement downgrade rights, irrespective of the source of the downgrade right. You cannot deactivate the downgrade right on a software model and keep the downgrade right activated on the software entitlement. To deactivate a downgrade right, double-click the field to display the toggle button, select false, and click the Save icon (). false: deactivates the downgrade right on the software model and on the related software entitlements. true: reactivates the downgrade right on the software model and on the related software entitlements.

Previous topic

Next topic

Release version

Software model fields

Software Model form and related list field descriptions.

Software Model form


Field	Description
Display name	Name of the model. The system property glide.cmdb_model.display_name.shorten controls how software model display names are generated. Users with the admin role can configure this property. The default format is publisher + product + version + edition + platform + language. If the Platform or Language fields aren't set to Anything, the values are appended.
Publisher	Publisher of the software. You can use the lookup list provided. Note: Publisher is a reference to the company [core_company] table. Only companies that you are using internally are shown.
Product	Software product name. The same lookup list provided on the Software Discovery Models form. You can create a custom product from the lookup list, if desired. Note: If the relationship between the software publisher [samp_sw_publisher] and company [core_company] tables is not correct, products for that publisher may not be shown. If the publisher and product do not exist, you can Add a custom software product.
Discovery map	Set of conditions that determines which software discovery models get mapped to the software models. Purchased rights are only applied to software discovery models that meet the condition. This matching is important for reconciliation. Discovery models with predefined suites are indicated in the Suite defined field. A value of Yes indicates that the discovery model is a suite parent. You can use the discovery maps provided, or you can choose to specify the condition information directly instead. A user with the sam_admin role can choose to create a custom discovery map. When you select a discovery map, you may encounter a message: `Many underlying software models will be created. These might be part of suite components, downgrade rights or next version. Please validate on completion`. The message appears only if there are greater than or equal to 50 suite components for the software model and if any of the following conditions are met: A software model does not exist for any suite component A software model does not exist for any downgrade right A software model does not exist for the next version Note: If you change the discovery map in an existing software model, a warning message appears. The warning message informs you that the downgrade rights on the software model and on the related entitlements also change. For example, if you change the discovery map on a software model from DMAP1 to DMAP2, and save the software model, then all the downgrade rights associated with DMAP1 are removed from the software model and the downgrade rights associated with DMAP2 are populated. However, if the value in the Agreement type field in the Software Entitlement form layout is Generic, the downgrade rights for that entitlement don't change. If the discovery map has a lifecycle definition defined, those settings are automatically populated in the Software Model Lifecycles related list. You can verify which discovery models get mapped to the software model by clicking the Show Matching Discovery Models related link. If the Publisher and Product fields are empty, the values are automatically populated according to the discovery map.
Version condition	Condition qualifier for the Version field. starts with is is anything The default is is anything.
Edition condition	Condition qualifier for the Edition field. starts with is is anything The default is is anything.
Platform	Platform of the software product to use when searching for the normalized discovery model. The default is Anything for Windows, Mac, UNIX.
Language	Language of the software product to use when searching for the normalized discovery model, which is populated once it has been normalized or added manually. The default is Anything.
License under management	Option that indicates you want to manage licenses for that software. If you clear the option, your software model won't be included in your reconciliation results. The value is set to true by default. It is also set to true for any software models that have been upgraded. If you upgrade and have software models with this option selected, you can do a bulk update and clear the License Under Management option from any software models you don’t want to include in your reconciliation results. When you run reconciliation again, only the software models with the option still selected will display in your results.
Software install condition	Only software installations that meet this software discovery map condition are counted during reconciliation. If needed, specify a subset of software installations that should be counted during reconciliation.
Product classification	The official United Nations Standard Products and Services Code (UNSPSC) classification.
Product type	Product type values include: Child, Driver, Licensable, Not Licensable, Patch, and Unknown. Note: The reconciliation process only considers software products that are licensable.
Version	Version of the software product. Required if the version condition value is [starts with] or [is-].
Edition	Edition of the software product to use when searching for the normalized discovery model. Required if the edition condition value is [starts with] or [is].

General tab


Field	Description
Short description	A brief description of the model.
Status	The status of the model. The options are In Production, Retired, and Sold.
Cost	The cost of a single unit of the software.
Owner	The person responsible for the model.
Next version	Reference to another software model of the same manufacturer which represents the next version of the product. The next version is defined on the discovery map and is part of the content service. The next version is populated on the software model in either of the two ways: When you create a software model or update the discovery map on a software model, a business rule is triggered when you click Save. The next version is populated if the discovery map has a next version defined for it. If the content service has the next version specified for the associated discovery map on an existing software model, the next version is populated when the schedule job, SAM- Create downgrades/upgrades for a software entitlement runs. However, if you entered a value in the Next version field, that value is not overridden. If a software model for the next version does not exist, a software model is automatically created. If the newly created software model consists of downgrade rights and child components, these components are automatically created. When the new software model for the next version is created or if one exists, the license entitlements from the current software model are moved over and associated with the software model for the next version.
Certified	Option to indicate that the software model is approved for use.
Blacklisted	Option for blacklisting the software model. Blacklisting identifies software that you should not install in your environment (inappropriate software, or software with vulnerabilities, for example). If the removal candidates don't exist, a scheduled job runs nightly that creates removal candidates for blacklisted software.

Suite Components tab


Field	Description
Allow automated content update	Option allowing ServiceNow to automatically send updated suite definitions to your instance through weekly content updates.
Inference percent	The percentage of suite components that must be present on a system to count as a suite. Used for suite management. Software installations on the same device and assigned to same user that meets the inference percent could be considered a suite. For example, if the inference percent for a suite of five products is set to 60% and three software installs on the same device, or assigned to the same user, are discovered, all three installations are considered a suite.
Suite child	The child product or products of the suite. For example, Microsoft Word and Microsoft Excel are child products of Microsoft Office.
Mandatory	Requirement of a suite component. A suite component can be Optional, Always Mandatory, or Mandatory Group. Set to Always Mandatory if the software must be installed to count the model as a suite.
Suite relationship assumed	Relationship that indicates that multiple software models exist for one or more of the suite components. Therefore, the relationship between suite parent and suite component was assumed. Review the created suite components to ensure the relationship is correct.

Suite Parents tab


	Description
Suite parent	The parent suites to which the software is assigned. For example, the parent suite for several common Microsoft products is a version of Microsoft Office.
Mandatory	Requirement of a suite component. A suite component can be Optional, Always Mandatory, or Mandatory Group. Set to Always Mandatory if the software must be installed to count the model as a suite.
Suite relationship assumed	Relationship that indicates that multiple software models exist for one or more of the suite components, therefore the relationship between suite parent and suite component was assumed. Review the created suite components to ensure the relationship is correct.

Product Catalog tab


Field	Description
Catalog Item	Information about the model as it appears in the product catalog and service catalog. Information only appears if the model has been published to the product catalog.
Description	Description of the software model as it appears in the product catalog.
Picture	Image of the software logo can be added. This logo appears in the service catalog if the software model is published.

Software Model Lifecycle related list


Field	Description
Software model	Name of software model.
Lifecycle type	Lifecycle type values include: Internal Publisher
Lifecycle phase	Lifecycle phase values include: Pre Release General Availability Date the software became generally available to the market. Upgrade Only shown when the Lifecycle type field is Internal. End of Life Date the software was no longer supported by the publisher. End of Support End of Extended Support
Source	Source of the lifecycle model. If the record is created manually, it's set to Internal. If it's created automatically, the field is set to ServiceNow.
Description	Description of the software model lifecycle.
Phase start date	Date the lifecycle phase starts.
Phase end date	Date the lifecycle phase ends.
Risk	The risk level to an organization with regards to the lifecycle phase. For example, the risk for the end of support phase for a publisher maybe moderate or the end of life phase maybe high. Risk type values include: Very High High Moderate Low None

Override License Cost related list

Table 1.
Field	Description
Software Model	The software model that the software entitlement belongs to.
Metric Group	The metric group the software entitlement belongs to.
License Metric	The license metric specified for the software entitlement.
License Cost	Cost of the license.
License & Maintenance Cost	Cost of the license combined with cost of the maintenance license. Note: Specify a license cost or a license and maintenance cost, to override the true-up cost during reconciliation. If no values are specified in the License Cost or License & Maintenance Costfields, the software entitlement cost is used for true-up cost calculations. Note: For SaaS licenses, only the license cost applies. The license & maintenance cost does not apply.

Metric Attributes related list


Field	Description
Software model	Software model associated with the metric attributes.
Metric group	Grouping for the software metric. If you have optional publisher packs installed that the software applies to, those options are shown. Otherwise, the metric group value is Common.
License metric	The license metric that the software license is counted against when reconciliation is run (per user, per device, for example).
Description	Attribute type description that is based on the license metric value.
Attribute	Attribute type for reconciling entitlement license metrics. Maximum active OSEs per server Maximum installs per OSE Maximum installs per right: For Per User, Per Device, Per Named User, and Per Named Device Maximum processors per right Minimum users per processor Minimum cores per processor Minimum cores per server
Attribute value	Value of the attribute (integer).
Attribute value is unlimited	Option for setting the attribute as unlimited.

Client Access related list

Table 2.
Field	Description
Name	Unique name for the client access record.
Software model	Software model for the client access record.
Database instance	Oracle database instance. Note: Only shown for Oracle Named User Plus license metric.
Total device count	Number of unique devices allowed to access the product.
Total user count	Number of unique users allowed to access the product.
Total user/device count	Number of user/device licenses that are accessed a user or a shared device. Note: Only shown when Citrix is specified.

Downgrade Rights related list


Field	Description
Parent software model	Parent (or the topmost hierarchy) of the software model.
Software model	Software model associated with the downgrade rights. Based on the parent software model that you select, the related software models appear in the list. For example, if you select Microsoft SQL Server 2012 Standard as the parent software model, only Microsoft-related software models appear in the list.
Source	Source of the downgrade rights. If the record is created manually, it's set to Internal. If it's created automatically, the field is set to ServiceNow.
Active	Option that indicates if the downgrade rights on the software model are active or not. If needed, you can deactivate the downgrade rights. Only the active downgrade rights appear in the field. To see all the downgrade rights, remove the Active condition from the filter. If you deactivate a downgrade right on a software model, the change is propagated to the related software entitlement downgrade rights, irrespective of the source of the downgrade right. You cannot deactivate the downgrade right on a software model and keep the downgrade right activated on the software entitlement. To deactivate a downgrade right, double-click the field to display the toggle button, select false, and click the Save icon (). false: deactivates the downgrade right on the software model and on the related software entitlements. true: reactivates the downgrade right on the software model and on the related software entitlements.

How search works:

Topics are ranked in search results by how closely they match your search terms

Software model fields

Software model fields

Software Model form

General tab

Suite Components tab

Suite Parents tab

Product Catalog tab

Software Model Lifecycle related list

Override License Cost related list

Metric Attributes related list

Client Access related list

Downgrade Rights related list

On this page

Software model fields

Software model fields

Software Model form

General tab

Suite Components tab

Suite Parents tab

Product Catalog tab

Software Model Lifecycle related list

Override License Cost related list

Metric Attributes related list

Client Access related list

Downgrade Rights related list

Log in to personalize your search results and subscribe to topics