Software model fields
Software Model form and related list field descriptions.
After you fill a software entitlement with the correct PPN, a software model is automatically created. The tabs on the Software Model form, such as Suite Components, Suite Parents, Software Product Lifecycles, Metric Attributes, Downgrade Rights, Product Lifecycles for all Versions, and so on, are populated automatically. However, you can manually add or update the software model details based on your requirements.
Details tab
This list shows the details of a software model such as the status of the model, product details, licensing, conditions, and product catalog information.
| 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. |
| Status | Status of the model. The options are In Production, Retired, and Sold. |
| Product Details section | |
| 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’re 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 isn’t correct, products for that publisher may not be shown. If the publisher and product don’t exist, you can Add a custom software product in Software Asset Management classic. |
| Version condition | Condition qualifiers for the Version field.
This field is automatically set to is anything. |
| Version | Version of the software product. |
| Edition condition | Condition qualifiers for the Edition field.
|
| Edition | Edition of the software product to use when searching for the normalized discovery model. |
| Discovery map | A set of conditions that determine 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:
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. You can verify which discovery models get mapped to the software model by selecting the Show Matching Discovery Models related link in Software Asset Management classic. View the same results in the Software Asset Workspace, by navigating to . Select a software model and then select the Matching Discovery Models related list. If the Publisher and Product fields are empty, the values are automatically populated according to the discovery map. |
| 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:
However, if you entered a value in the Next version field, that value isn’t overridden. |
| Product classification | The official United Nations Standard Products and Services Code (UNSPSC) classification. From this release, product classifications have been enhanced with a comprehensive set of UNSPSC codes available via the Content Service library. Updates to the UNSPSC codes will also be available via the bi-weekly Content Service library update. |
| Software Licensing section | |
| 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. |
| License under management | Option to manage licenses for the specified software. If you clear this option, your software model won't be included in your reconciliation results. This option is selected by default. It’s also selected 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 that 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. |
| Owner | Person responsible for the model. |
| Unit of consumption | Unit of measure for the software units that can be consumed. |
| Conditions section | |
| Condition name | Name of the condition that you want to define for the software model. |
| Software install condition | Condition to account for only specific software installations during reconciliation. Installs that do not meet the required software install conditions will be included in the reconciliation process. However,
these installs are likely to be flagged as unlicensed unless there is another software model that meets the required software install conditions. For example, if you have purchased Microsoft
Visual Studio and set up software installation conditions for using Visual Studio only to consume licenses in your non-production environment. You need to create separate software install conditions for each component model under Visual Studio. Note:
If you clear the License under management option, the software installations that meet the specified software install conditions are excluded from reconciliation instead. In the Software Asset Management classic application, you can add multiple software install conditions to a single software model using the following options:
In the Software Asset Workspace, you can add multiple software install conditions to a single software model using the following options:
|
| Subscription condition Note: This field appears only on subscription-based software models, including hybrid software models that contain both software subscriptions and on-premise software
installations. |
Condition to account for only groups of subscriptions during reconciliation. Only the subscriptions that meet the specified subscription conditions are included in reconciliation. For example, you can set a
subscription condition to reconcile subscriptions from only a specific geographic location or business department. Note: If you clear the License under management option, the subscriptions that
meet the specified software conditions are excluded from reconciliation instead. In the Software Asset Management classic application, you can add multiple subscription conditions to a single software model using the following options:
In the Software Asset Workspace, you can add multiple subscription conditions to a single software model using the following options:
Warning:
You can’t add subscription conditions to out-of-the-box software models. You must create a software model to define subscription conditions for the associated subscription software. |
| General section | |
| Short description | Brief description of the model. |
| Platform | Platform of the software product to use when searching for the normalized discovery model. The default is Anything for Windows, macOS, UNIX. |
| Language | Language of the software product to use when searching for the normalized discovery model, which is populated after it has been normalized or added manually. This field is automatically set to Anything. |
| Asset tracking strategy | Option to override the way assets are tracked for the model. |
| Asset tracking unit | Unit of measure for asset. |
| Cost | Cost of a single unit of the software. |
| Certified |
Option to indicate if the product associated to this software model is approved or unapproved by TRM. When a enterprise architect adds a product to the TRM library, the product is flagged as either approved or unapproved. When a software model is created for an approved product, this check box is automatically selected. If you create a software model for an unapproved product, the software model is designated as restricted. During the reconciliation process, any software installations associated with unapproved products are identified as removal candidates. If you activate the Application Portfolio Management - TRM (com.snc.apm_trm) plugin for software models that exist, this check box may or may not be selected depending on whether the product is approved. |
| Restricted software | Option for restricting software. Restricted software identifies software that you shouldn’t 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 restricted software. |
| License all installs accessed by clients Note: This field appears only on software models that are associated with client access records, except for Oracle DB Server software models. |
Option to license the configuration items (CIs) that the software is installed on, based on conditions that you specify on the software model, such as software install conditions. If any of the associated client
access records are unlicensed due to insufficient rights, all CIs remain unlicensed. If you disable this option, only the CIs that have been added to your client access records are licensed. See Add a software client access record in Software Asset Management classic for detailed instructions on how to add CIs to your client access records. If you enable this option after you have already added CIs to your client access records, those CIs are deleted from your records and then subsequently licensed based on the conditions that you specify on the software model. |
| Database option Note: This field appears only on Oracle Database software models. |
Oracle database option or management pack. Each option or pack requires a separate software model. The database option is an identifier for software models. This field is shown when creating software models that meet the following conditions:
|
| Database option condition Note: This field appears only on Oracle Database software models that are associated with a database option or management pack, as specified in the Database option field. |
Condition to account for only the subsets of Oracle Database options or management packs during reconciliation. Only the database options or management packs that meet the specified database option conditions are included in the
reconciliation. Note: If you clear the License under management option, the database options or management packs that meet the specified database option conditions are excluded from
reconciliation instead. In the Software Asset Management classic application, you can add multiple database option conditions to a single software model using the following options:
In the Software Asset Workspace, you can add multiple database option conditions to a single software model using the following options:
|
| Apply to subscriptions | Option to apply this software model to only subscription-based software suites. If you don’t enable this option, you can apply this software model to only software suites with installed software. |
| Auto-generate client access for allocations. Note:
This field appears only on Oracle Database Server software models. Important:
To use this option, you must request the Data Collection for Oracle Global Licensing and Advisory Services (GLAS) application from the ServiceNow Store. For details, see Request Data Collection for Oracle Global Licensing and Advisory Services (GLAS). |
Option to automatically generate and manage client access records for Oracle Database Server. If you enable this option, the Software Asset Management application generates and manages client access records based on your latest Oracle Database Server Named User Plus entitlements, the users, and devices that the associated rights are allocated to, and the Oracle database instances that are supported by these users and devices. The Software Asset Management application generates a separate client access record for each supported database instance. If you disable this option after the Software Asset Management application has automatically generated client access records for Oracle Database Server, those client access records are no longer managed and updated automatically. You must manage and update those client access records manually to keep them accurate and upto date. If you enable this option and already have existing client access records for Oracle Database Server, all automatically generated client access records are managed and updated automatically again. However, you must continue to manage and update all manually generated client access records. |
| Product Catalog section | |
| 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 that can be added. This logo appears in the service catalog if the software model is published. |
| Activity section | |
| Work notes | Notes about the work order task that are visible to all users within your organization. |
Suite Components tab
This list shows the software suite component details. Software components are the suite children of a software suite parent. For more information, see Software Asset Management software suites.
| Field | Description |
|---|---|
| Suite child | 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 that the relationship is correct. |
| Suite Content Usage section | |
| Inference Option: Number and Percent |
Number: Specifies the number of components installed for the suite. Specify a number lesser than or equal to the number of components.
Note: For any new software models being created with
suite components, the Number option is selected by default. Percent: Specifies what percentage of the components must be installed for the suite.
Note: For existing software models with suite components that were using the inference percent, the
Percent option is selected by default. However, you can choose to use the Number option. If the system property Use component licenses to optimize compliance when suite licenses run out is set to true, Inference percent specifies a threshold to determine whether the suite or component licensing is optimal. |
| Allow automated content update | Option to enable automatic content changes to software models. |
Suite Parents tab
This list shows the software suite parent details. For more information, see Software Asset Management software suites.
| Description | |
|---|---|
| Suite parent | Parent suites to which the software is assigned. For example, the parent suite for several common Microsoft products is a version of Microsoft Office. |
| Suite child | 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. |
Software Product Lifecycles
This list shows the life cycle information of a software product. For more information on life cycles, see Product life cycles.
| Field | Description |
|---|---|
| Publisher | Name of publisher. |
| Product | Name of the software product. |
| Version | Licensable version of the software |
| Edition | Edition of the software. |
| Full Version | The granular licensable version of the software. |
| Phase start date | Date when the life-cycle phase starts. |
| Lifecycle type | The product life cycle type values include:
|
| Risk | The risk level to an organization with regards to the life-cycle phase. For example, the risk for the end of support phase for a publisher maybe moderate or the end of life phase may be high. Risk type values include:
|
| Lifecycle phase | Life-cycle phase values include:
|
| Active | Indicates if the life cycle is to be considered or not while evaluating the risk of the software. Note: By default, only active life cycles are displayed. |
| Source | Source of the life cycle. If the record is created manually, this field is set to Internal. If the record is created automatically, this field is set to ServiceNow. |
| Description | Description of the software product life cycle. |
Software Entitlements tab
This list shows the entitlement terms of your software license. For more information, see the Software entitlements section in Software models and Software entitlements.
| Field | Description |
|---|---|
| Display name | Automatically generated name based on the software model display name. |
| License metric | License metric for the license group that the software license is counted against when reconciliation is run. The options for license metric change based on the Metric group field. For more information, see Software license metrics. |
| Metric group | Metric group based on the Software Model field. Each metric group has a set of license metrics that are specific to the software publisher. |
| License type | The type determines whether the rights grant full access to the software or if they’re being upgraded from a previous version of the software. The following are the various license types:
|
| Active rights | Number of rights granted for this entitlement. |
| Purchased rights | Number of rights purchased for this entitlement. |
| Total cost | Total cost of the entitlement calculated from the unit cost. |
Override License Costs tab
This list shows the override license cost information for your software entitlements.
| Field | Description |
|---|---|
| Software Model | Software model that the software entitlement belongs to. |
| Metric Group | Metric group that the software entitlement belongs to. |
| License Metric | 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. 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 Cost fields, 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. |
| The following fields appear when the value selected in the License Metric field is Employee. | |
| Active | Indicates whether the license cost is to be considered for true-up cost calculations. |
| Lower limit | Minimum number of employees that the licenses are required for. |
| Upper limit | Maximum number of employees that the licenses are required for. |
SAP Engine Usages tab
This list shows the license usage for SAP Engines.
| Field | Description |
|---|---|
| Name | Name of the license usage record. Select a name to open the record to view detailed information such as the associated software model and SAP client. |
| Count | Number of unique users or devices that are granted access to the SAP Engine product. |
| Type | Type of CAL that is associated with the license usage record.
|
| Usage | Total memory usage of the SAP Engine product in gigabytes (GB). |
| Cost Center | Cost center of the users or devices that are granted access to the SAP Engine product. |
| Department | Business department of the users or devices that are granted access to the SAP Engine product. |
| Location | Geographic location of the users or devices that are granted access to the SAP Engine product. |
| Company | Company of the users or devices that are granted access to the SAP Engine product. |
Software Model Results tab
This list shows the software model results associated with the license metric results.
| Field | Description |
|---|---|
| Status | Status of the software model. Possible values are Compliant or Not Compliant. Select the Status field to open the corresponding Software Model Results record, where you can view more in-depth information about the software model result. See View software model results for detailed descriptions of each field on the Software Model Results form. |
| Agreement type | Agreement type that is set on the software entitlement.
Note: If the agreement type is Enterprise Level Agreement or Unlimited Level Agreement, the Status is Compliant even if there are unlicensed installations or unlicensed
subscriptions. |
| Unlicensed installs | Number of unlicensed software installations that are not covered by any entitlements. |
| True-up cost | Estimated cost of remediating unlicensed installations based on the lowest number of rights needed (rights needed times average price per right from entitlements). The lowest cost from Purchase Rights remediation options. |
| Over-licensed amount | Estimated cost of rights not being used. The sum of the Over Licensed amount from the True-up value costs. |
| Potential savings |
Cost saved by optimizing unused licenses. |
| Group | Group specified on which to run reconciliation. Values include:
|
| Subgroup | Subgroup specified on which to run reconciliation. Values include:
|
Metric Attributes tab
This list shows the metric attributes information of a software model.
| 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. For more information on each attribute type, see Software model metric attributes. |
| Attribute value | Value of the attribute (integer). |
| Attribute value is unlimited | Option for setting the attribute as unlimited. |
Vendor Catalog Items tab
This list shows you the details of the software models associated with a vendor. For more information, see Vendor catalog items.
| Field | Description |
|---|---|
| Name | Name of the catalog item. |
| Product ID | Item identification number assigned by your organization. |
| Short Description | Brief description of the item. |
| Vendor Price | The price at which the item is available in the vendor catalog. If the vendor offers a discount, the vendor price reflects the discounted price. |
| Rank tier | Overall ranking for this vendor's products and services. |
Client Access tab
This list shows a client access record details of the users or devices that are accessing a particular version of your server software using a client access license (CAL).
| Field | Description |
|---|---|
| Name | Name of the client access record. Select a name to open the corresponding client access record, where you can view more in-depth information about the record, such as the users or devices that the associated client access licenses (CALs) are assigned to and the configuration items (CIs) that the associated server software is installed on. See Add a software client access record in Software Asset Management classic for more information on client access records in the Software Asset Management classic application. See Create a software client access record in workspace for more information on client access records in the Software Asset Workspace. |
| Count | Number of unique users or devices that are granted access to the associated server. Note: If you are using a Citrix software model and User/Device CAL type, the Count field is based on the number of user/device licenses that are assigned to your users or shared
devices. |
| Type | Type of CAL that is associated with the client access record.
Note: The Reserved Hourly Average Sensor and Sensor Subscription license metrics are applicable only for CrowdStrike and are available with Yokohama Patch 1, Software Asset Management - SaaS License Management (sn_sam_saas_int) 15.0.8, and Software Asset Management (sn_itam_samp) 2.1.0 version onwards. If you are on any version for Yokohama below Patch 1, refer KB1801232. |
| Cost Center | Cost center of the users or devices that are granted access to the associated server. |
| Department | Business department of the users or devices that are granted access to the associated server. |
| Location | Geographic location of the users or devices that are granted access to the associated server. |
| Company | Company of the users or devices that are granted access to the associated server. |
Software Subscriptions tab
This list shows the available subscriptions for a software application.
| Field | Description |
|---|---|
| Display name | Software publisher and product for the subscription. |
| User principal name | User's email address for the subscription. |
| Software model | Software model for the subscription. |
| Last activity | Last date when this subscription was last used. |
| Inactive days | Number of days for which a user's subscription has been inactive. This field is visible on the Software Subscriptions form when the Last activity field is not empty. Inactive days are calculated using the value in the Last activity field. |
| Subscription profile | Profile that is associated with the subscription identifier. |
Downgrade Rights tab
This list shows the downgrade rights information of a software model. For more information, see Downgrade Rights.
| 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 then select the Save icon (
|
Matching Discovery Models tab
This list shows the discovery maps that match the software publisher and product fields of the software model.
| Field | Description |
|---|---|
| Display name | Name of the discovery model. This value is generated automatically using the discovered publisher, discovered product, and discovered version. |
| Normalization status | Status of the normalization process:
|
| Publisher | Normalized publisher of the software. |
| Product | Normalized product name of the software. |
| Version | Normalized version of the software product. |
| Edition | Normalized edition of the software. |
Product Lifecycles for all Versions tab
This list shows the life cycle for all versions of the software product.
| Field | Description |
|---|---|
| Publisher | Name of the publisher. |
| Product | Name of the software product. |
| Version | Licensable version of the software. |
| Full version | Granular licensable version of the software. |
| Edition | Edition of the software. |
| Lifecycle phase | Life-cycle phase values include:
|
| Lifecycle type | The product life cycle type values include:
|
| Source | Source of the life cycle. If the record is created manually, this field set to Internal. If the record is created automatically, the field is set to ServiceNow. |
| Description | Description of the software product life cycle. |
| Phase start date | Date when the life-cycle phase starts. |
| Risk | Risk level to an organization with regards to the life-cycle 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:
|
| Active | Option to indicate if the life cycle is to be considered or not while evaluating the risk of the software. Note: By default, only active life cycles are displayed. |
Group Allocations tab
This list shows the user groups allocated to the software model.
| Field | Description |
|---|---|
| Assignment Group | Name of the user group assigned to this software entitlement. Software licenses are allocated to all the members of this assignment group based on the availability of unallocated licenses for the software entitlement. |
| Status | Current status of the group allocation to the software model. Possible values are:
|
| Active | Indicates if the user group allocation to the software entitlement is active. Possible values are:
|
| License metric | User-based license metric for user allocation to the software entitlement. License metric values include:
|
| Group Members | Number of users available in the assignment group. |
| Software model | Field value is automatically set to the selected software model. |
| Allocated Quantity | Number of users from the assignment group allocated to the software entitlement. |
| Entitlement condition | Entitlement condition defined to apply the group user allocation on the filtered software entitlements. |