Software model fields

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.

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 Core UI.

Condition qualifiers for the Version field.- starts with - is - is anything

This field is automatically set to is anything.

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:

• A software model doesn’t exist for any suite component
• A software model doesn’t exist for any downgrade rights
• A software model doesn’t 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.

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 License operations > Licensing > Software models. 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.

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

Note: The next version is populated only after the SAM- Create downgrades/upgrades for a software entitlement scheduled job runs weekly.

However, if you entered a value in the Next version field, that value isn’t overridden.

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.

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:

• Add Filter Condition: Enables you to specify all the conditions that a software installation must meet to be included in reconciliation.
• Add "OR" Clause: Enables you to specify any of the conditions that a software installation can meet to be included in reconciliation.

In the Software Asset Workspace, you can add multiple software install conditions to a single software model using the following options:

• or: Enables you to specify any of the conditions that a software installation can meet to be included in reconciliation.
• and: Enables you to specify all the conditions that a software installation must meet to be included in reconciliation.
• + New condition set: Enables you to specify additional sets of conditions that a software installation can meet to be included in reconciliation.

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:

• Add Filter Condition: Enables you to specify all the conditions that a subscription must meet to be included in reconciliation.
• Add "OR" Clause: Enables you to specify any of the conditions that a subscription can meet to be included in reconciliation.

In the Software Asset Workspace, you can add multiple subscription conditions to a single software model using the following options:

• or: Enables you to specify any of the conditions that a subscription can meet to be included in reconciliation.
• and: Enables you to specify all the conditions that a subscription must meet to be included in reconciliation.
• + New condition set: Enables you to specify additional sets of conditions that a subscription can meet to be included in reconciliation.

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.

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:

• The Publisher is Oracle.
• The Product is DB Server.

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:

• Add Filter Condition: Enables you to specify all the conditions that a database option or management pack must meet to be included in reconciliation.
• Add "OR" Clause: Enables you to specify any of the conditions that a database option or management pack can meet to be included in the reconciliation.

In the Software Asset Workspace, you can add multiple database option conditions to a single software model using the following options:

• or: Enables you to specify any of the conditions that a database option or management pack can meet to be included in the reconciliation.
• and: Enables you to specify all the conditions that a database option or management pack must meet to be included in reconciliation.
• + New condition set: Enables you to specify additional sets of conditions that a database option or management pack can meet to be included in reconciliation.

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

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.

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:- Very High - High - Moderate - Low - None

Life-cycle phase values include:- Pre Release: Date when the software was pre-released. - General Availability: Date when the software became generally available to the market. - Upgrade

Note: Only shown when the Lifecycle type field is Internal.

• End of Support: Date by which the software will not be enhanced by the publisher.

This value corresponds to the Mainstream Support end date for Microsoft according to its Fixed Lifecycle Policy.

• End of Extended Support: Date by which the publisher will no longer provide any support or updates to the software.

This value corresponds to the Extended Support end date for Microsoft according to its Fixed Lifecycle Policy.

• End of Life: Date by which the software will no longer be manufactured by the publisher.

Note: This value isn't applicable for Microsoft because it follows the fixed lifecycle policy providing mainstream support and extended support. For more information, see Fixed Lifecycle Policy.

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.

Agreement type that is set on the software entitlement.- Common: Generic, Enterprise License Agreement (ELA) - IBM: Generic, Enterprise License Agreement (ELA), International Program License Agreement (IPLA), IBM Customer Agreement (ICA), Unlimited Level Agreement (ULA) - Microsoft: Generic, Enterprise License Agreement (ELA) - Oracle: Generic, Unlimited Level Agreement (ULA) - VMware: Generic, Enterprise License Agreement (ELA), Enterprise Purchasing Program (EPP), Volume Purchasing Program (VPP)

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.

Type of CAL that is associated with the client access record.- User CAL: Licenses each user that accesses the associated server, regardless of the number of devices that each user is using to access the server.

• Device CAL: Licenses each device that accesses the specified server, regardless of the number of users that are using each device to access the server.

• User/Device CAL: Licenses each user or device that accesses the associated server.

Note: If you are using a Citrix software model, the User/Device CAL type is based on the user/device licenses that are assigned to your users or shared devices.

• Reserved Hourly Average Sensor: This metric counts the number of unique active endpoints per clock-hour and averages them over a rolling 28-day period. The count of Reserved Hourly Average Sensor Licenses resets at the start of each clock-hour.
• Sensor Subscription: This metric calculates license usage by averaging endpoint counts over four consecutive weeks. Weekly endpoint counts are based on the total number of endpoints consumed in the previous seven days.

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.

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 (

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

Life-cycle phase values include:- Pre Release: Date the software was pre-released. - General Availability: Date the software became generally available to the market. - Upgrade

Note: Only shown when the Lifecycle type field is Internal.

• End of Life: Date by which the software will no longer be manufactured by the publisher.

Note: This value isn't applicable for Microsoft because it follows the fixed life-cycle policy providing mainstream support and extended support. For more information, see Fixed Lifecycle Policy.

• End of Support: Date by which the software will not be enhanced by the publisher.

This value corresponds to the Mainstream Support end date for Microsoft according to its Fixed Lifecycle Policy.

• End of Extended Support: Date by which the publisher will no longer provide any support or updates to the software.

This value corresponds to the Extended Support end date for Microsoft according to its Fixed Lifecycle Policy.