| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nDisplay name\n\n | \n\nName 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.\n\n If the **Platform** or **Language** fields aren't set to **Anything**, the values are appended.\n\n |
| \n\nStatus\n\n | \n\nStatus of the model. The options are **In Production**, **Retired**, and **Sold**.\n\n |
| \n\nProduct Details section\n\n | |
| \n\nPublisher\n\n | \n\nPublisher 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.\n\n |
| \n\nProduct\n\n | \n\nSoftware 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.\n\n If the publisher and product don’t exist, you can [Add a custom software product in Software Asset Management Core UI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/t_AddACustomProduct.md).\n\n |
| \n\nVersion condition\n\n | \n\nCondition qualifiers for the **Version** field.- **starts with**\n- **is**\n- **is anything**\n\nThis field is automatically set to **is anything**.\n\n |
| \n\nVersion\n\n | \n\nVersion of the software product.\n\n |
| \n\nEdition condition\n\n | \n\nCondition qualifiers for the **Edition** field.- **starts with**\n- **is**\n- **is anything**\n\n |
| \n\nEdition\n\n | \n\nEdition of the software product to use when searching for the normalized discovery model.\n\n |
| \n\nDiscovery map\n\n | \n\nA 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.\n\nYou 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.\n\nWhen 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:\n\n- A software model doesn’t exist for any suite component\n- A software model doesn’t exist for any downgrade rights\n- A software model doesn’t exist for the next version\n\n **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.\n\n 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.\n\nIf the **Publisher** and **Product** fields are empty, the values are automatically populated according to the discovery map.\n\n |
| \n\nNext version\n\n | \n\nReference 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:\n\n- 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.\n- 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.\n\n**Note:** The next version is populated only after the **SAM- Create downgrades/upgrades for a software entitlement** scheduled job runs weekly.\n\n\n However, if you entered a value in the **Next version** field, that value isn’t overridden.\n\n |
| \n\nProduct classification\n\n | \n\nThe 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.\n\n |
| \n\nSoftware Licensing section\n\n | |
| \n\nProduct type\n\n | \n\nProduct type values include: **Child**, **Driver**, **Licensable**, **Not Licensable**, **Patch**, and **Unknown**.**Note:** The reconciliation process only considers software products that are licensable.\n\n |
| \n\nLicense under management\n\n | \n\nOption 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.\n\nIf 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.\n\n |
| \n\nOwner\n\n | \n\nPerson responsible for the model.\n\n |
| \n\nUnit of consumption\n\n | \n\nUnit of measure for the software units that can be consumed.\n\n |
| \n\nConditions section\n\n | |
| \n\nCondition name\n\n | \n\nName of the condition that you want to define for the software model.\n\n |
| \n\nSoftware install condition\n\n | \n\nCondition 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.\n\n In the Software Asset Management classic application, you can add multiple software install conditions to a single software model using the following options:\n\n- **Add Filter Condition**: Enables you to specify all the conditions that a software installation must meet to be included in reconciliation.\n- **Add \"OR\" Clause**: Enables you to specify any of the conditions that a software installation can meet to be included in reconciliation.\n\n In the Software Asset Workspace, you can add multiple software install conditions to a single software model using the following options:\n\n- **or**: Enables you to specify any of the conditions that a software installation can meet to be included in reconciliation.\n- **and**: Enables you to specify all the conditions that a software installation must meet to be included in reconciliation.\n- **+ New condition set**: Enables you to specify additional sets of conditions that a software installation can meet to be included in reconciliation.\n\n |
| \n\nSubscription 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.\n\n | \n\nCondition 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.\n\nIn the Software Asset Management classic application, you can add multiple subscription conditions to a single software model using the following options:\n\n- **Add Filter Condition**: Enables you to specify all the conditions that a subscription must meet to be included in reconciliation.\n- **Add \"OR\" Clause**: Enables you to specify any of the conditions that a subscription can meet to be included in reconciliation.\n\nIn the Software Asset Workspace, you can add multiple subscription conditions to a single software model using the following options:\n\n- **or**: Enables you to specify any of the conditions that a subscription can meet to be included in reconciliation.\n- **and**: Enables you to specify all the conditions that a subscription must meet to be included in reconciliation.\n- **+ New condition set**: Enables you to specify additional sets of conditions that a subscription can meet to be included in reconciliation.\n\n**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.\n\n |
| \n\nGeneral section\n\n | |
| \n\nShort description\n\n | \n\nBrief description of the model.\n\n |
| \n\nPlatform\n\n | \n\nPlatform of the software product to use when searching for the normalized discovery model.The default is **Anything** for Windows, macOS, UNIX.\n\n |
| \n\nLanguage\n\n | \n\nLanguage 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**.\n\n |
| \n\nAsset tracking strategy\n\n | \n\nOption to override the way assets are tracked for the model.\n\n |
| \n\nAsset tracking unit\n\n | \n\nUnit of measure for asset.\n\n |
| \n\nCost\n\n | \n\nCost of a single unit of the software.\n\n |
| \n\nCertified\n\n | \n\nOption to indicate if the product associated to this software model is approved or unapproved by TRM.\n\n 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.\n\n 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.\n\n 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.\n\n |
| \n\nRestricted software\n\n | \n\nOption for restricting software.Restricted software identifies software that you shouldn’t install in your environment \\(inappropriate software, or software with vulnerabilities, for example\\).\n\nIf the removal candidates don't exist, a scheduled job runs nightly that creates removal candidates for restricted software.\n\n |
| \n\nLicense all installs**Note:** This field appears only on software models that are associated with [resource value](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/create-resource-value-record.md) and [client access](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/t_AddAClientAccessRec.md) records, except for Oracle database software models.\n\n | \n\nOption 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 Core UI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/t_AddAClientAccessRec.md) for detailed instructions on how to add CIs to your client access records.\n\nIf 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.\n\n |
| \n\nDatabase option**Note:** This field appears only on Oracle Database software models.\n\n | \n\nOracle database option or management pack. Each option or pack requires a separate software model. The database option is an identifier for software models.\n\n This field is shown when creating software models that meet the following conditions:\n\n- The **Publisher** is **Oracle**.\n- The **Product** is **Database**.\n\n |
| \n\nDatabase 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.\n\n | \n\nCondition 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.\n\nIn the Software Asset Management classic application, you can add multiple database option conditions to a single software model using the following options:\n\n- **Add Filter Condition**: Enables you to specify all the conditions that a database option or management pack must meet to be included in reconciliation.\n- **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.\n\nIn the Software Asset Workspace, you can add multiple database option conditions to a single software model using the following options:\n\n- **or**: Enables you to specify any of the conditions that a database option or management pack can meet to be included in the reconciliation.\n- **and**: Enables you to specify all the conditions that a database option or management pack must meet to be included in reconciliation.\n- **+ 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.\n\n |
| \n\nApply to subscriptions\n\n | \n\nOption 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.\n\n |
| \n\nAuto-generate client access for allocations. **Note:** This field appears only on Oracle Database software models.\n\n **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\\)](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/request-data-collection-oracle-glas-app.md).\n\n | \n\nOption to automatically generate and manage client access records for Oracle Database. If you enable this option, the Software Asset Management application generates and manages client access records based on your latest Oracle Database 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, 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.\n\n If you enable this option and already have existing client access records for Oracle Database, 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.\n\n |
| \n\nProduct Catalog section\n\n | |
| \n\nCatalog Item\n\n | \n\nInformation 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.\n\n |
| \n\nDescription\n\n | \n\nDescription of the software model as it appears in the product catalog.\n\n |
| \n\nPicture\n\n | \n\nImage of the software logo that can be added. This logo appears in the service catalog if the software model is published.\n\n |
| \n\nActivity section\n\n | |
| \n\nWork notes\n\n | \n\nNotes about the work order task that are visible to all users within your organization.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nSuite child\n\n | \n\nChild product or products of the suite. For example, Microsoft Word and Microsoft Excel are child products of Microsoft Office.\n\n |
| \n\nMandatory\n\n | \n\nRequirement 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.\n\n |
| \n\nSuite relationship assumed\n\n | \n\nRelationship 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.\n\n |
| \n\nSuite Content Usage section\n\n | |
| \n\nInference Option: **Number** and **Percent**\n\n | \n\n**Number**: Specifies the number of components installed for the suite. Specify a number lesser than or equal to the number of components.\n\n**Note:** For any new software models being created with suite components, the **Number** option is selected by default.\n\n **Percent**: Specifies what percentage of the components must be installed for the suite.\n\n**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.\n\n 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.\n\n |
| \n\nAllow automated content update\n\n | \n\nOption to enable automatic content changes to software models.\n\n |
| \n\n \n\n | \n\nDescription\n\n |
|---|---|
| \n\nSuite parent\n\n | \n\nParent suites to which the software is assigned. For example, the parent suite for several common Microsoft products is a version of Microsoft Office.\n\n |
| \n\nSuite child\n\n | \n\nChild product or products of the suite. For example, Microsoft Word and Microsoft Excel are child products of Microsoft Office.\n\n |
| \n\nMandatory\n\n | \n\nRequirement 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.\n\n |
| \n\nSuite relationship assumed\n\n | \n\nRelationship 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.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nPublisher\n\n | \n\nName of publisher.\n\n |
| \n\nProduct\n\n | \n\nName of the software product.\n\n |
| \n\nVersion\n\n | \n\nLicensable version of the software\n\n |
| \n\nEdition\n\n | \n\nEdition of the software.\n\n |
| \n\nFull Version\n\n | \n\nThe granular licensable version of the software.\n\n |
| \n\nPhase start date\n\n | \n\nDate when the life-cycle phase starts.\n\n |
| \n\nLifecycle type\n\n | \n\nThe product life cycle type values include:- **Internal**: The life cycle date is specific to the customer \\(for example, based on their internal policy, based on a custom contract/agreement with the publisher\\).\n- **Publisher**: The life cycle date comes from publisher sources and is not specific to a customer.\n- **Publisher Add-On**\n\n |
| \n\nRisk\n\n | \n\nThe 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.\n\nRisk type values include:- **Very High**\n- **High**\n- **Moderate**\n- **Low**\n- **None**\n\n |
| \n\nLifecycle phase\n\n | \n\nLife-cycle phase values include:- **Pre Release**: Date when the software was pre-released.\n- **General Availability**: Date when the software became generally available to the market.\n- **Upgrade**\n\n**Note:** Only shown when the **Lifecycle type** field is Internal.\n\n- **End of Support**: Date by which the software will not be enhanced by the publisher.\n\nThis value corresponds to the Mainstream Support end date for Microsoft according to its [Fixed Lifecycle Policy](https://learn.microsoft.com/en-us/lifecycle/policies/fixed).\n\n- **End of Extended Support**: Date by which the publisher will no longer provide any support or updates to the software.\n\nThis value corresponds to the Extended Support end date for Microsoft according to its [Fixed Lifecycle Policy](https://learn.microsoft.com/en-us/lifecycle/policies/fixed).\n\n- **End of Life**: Date by which the software will no longer be manufactured by the publisher.\n\n**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](https://learn.microsoft.com/en-us/lifecycle/policies/fixed).\n\n\n |
| \n\nActive\n\n | \n\nIndicates 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.\n\n |
| \n\nSource\n\n | \n\nSource 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**.\n\n |
| \n\nDescription\n\n | \n\nDescription of the software product life cycle.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nDisplay name\n\n | \n\nAutomatically generated name based on the software model display name.\n\n |
| \n\nLicense metric\n\n | \n\nLicense 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/c_SAMLicenseMetrics.md).\n\n |
| \n\nMetric group\n\n | \n\nMetric group based on the Software Model field. Each metric group has a set of license metrics that are specific to the software publisher.\n\n |
| \n\nLicense type\n\n | \n\nThe 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:\n\n- Perpetual\n- Perpetual + Software Assurance\n- Software Assurance\n- Subscription\n- Step-up\n- Subscription Step-up\n\n |
| \n\nActive rights\n\n | \n\nNumber of rights granted for this entitlement.\n\n |
| \n\nPurchased rights\n\n | \n\nNumber of rights purchased for this entitlement.\n\n |
| \n\nTotal cost\n\n | \n\nTotal cost of the entitlement calculated from the unit cost.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nSoftware Model\n\n | \n\nSoftware model that the software entitlement belongs to.\n\n |
| \n\nMetric Group\n\n | \n\nMetric group that the software entitlement belongs to.\n\n |
| \n\nLicense Metric\n\n | \n\nLicense metric specified for the software entitlement.\n\n |
| \n\nLicense Cost\n\n | \n\nCost of the license.\n\n |
| \n\nLicense & Maintenance Cost\n\n | \n\nCost 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.\n\n**Note:** For SaaS licenses, only the license cost applies. The license & maintenance cost does not apply.\n\n |
| \n\nThe following fields appear when the value selected in the License Metric field is Employee.\n\n | |
| \n\nActive\n\n | \n\nIndicates whether the license cost is to be considered for true-up cost calculations.\n\n |
| \n\nLower limit\n\n | \n\nMinimum number of employees that the licenses are required for.\n\n |
| \n\nUpper limit\n\n | \n\nMaximum number of employees that the licenses are required for.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nName\n\n | \n\nName 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.\n\n |
| \n\nCount\n\n | \n\nNumber of unique users or devices that are granted access to the SAP Engine product.\n\n |
| \n\nType\n\n | \n\nType of CAL that is associated with the license usage 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.\n- **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.\n- **User/Device CAL**: Licenses each user or device that accesses the associated server.\n\n |
| \n\nUsage\n\n | \n\nTotal memory usage of the SAP Engine product in gigabytes \\(GB\\).\n\n |
| \n\nCost Center\n\n | \n\nCost center of the users or devices that are granted access to the SAP Engine product.\n\n |
| \n\nDepartment\n\n | \n\nBusiness department of the users or devices that are granted access to the SAP Engine product.\n\n |
| \n\nLocation\n\n | \n\nGeographic location of the users or devices that are granted access to the SAP Engine product.\n\n |
| \n\nCompany\n\n | \n\nCompany of the users or devices that are granted access to the SAP Engine product.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nStatus\n\n | \n\nStatus 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](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/t_ViewSWModelResults.md) for detailed descriptions of each field on the Software Model Results form.\n\n |
| \n\nAgreement type\n\n | \n\nAgreement type that is set on the software entitlement.- Common: Generic, Enterprise License Agreement \\(ELA\\)\n- IBM: Generic, Enterprise License Agreement \\(ELA\\), International Program License Agreement \\(IPLA\\), IBM Customer Agreement \\(ICA\\), Unlimited Level Agreement \\(ULA\\)\n- Microsoft: Generic, Enterprise License Agreement \\(ELA\\)\n- Oracle: Generic, Unlimited Level Agreement \\(ULA\\)\n- VMware: Generic, Enterprise License Agreement \\(ELA\\), Enterprise Purchasing Program \\(EPP\\), Volume Purchasing Program \\(VPP\\)\n\n**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.\n\n |
| \n\nUnlicensed installs\n\n | \n\nNumber of unlicensed software installations that are not covered by any entitlements.\n\n |
| \n\nTrue-up cost\n\n | \n\nEstimated 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.\n\n |
| \n\nOver-licensed amount\n\n | \n\nEstimated cost of rights not being used. The sum of the Over Licensed amount from the True-up value costs.\n\n |
| \n\nPotential savings\n\n | \n\nCost saved by optimizing unused licenses.\n\n |
| \n\nGroup\n\n | \n\nGroup specified on which to run reconciliation. Values include: - None\n- Country\n- Department\n- Company\n- Region\n- Cost Center\n\n |
| \n\nSubgroup\n\n | \n\nSubgroup specified on which to run reconciliation. Values include:- None\n- Country\n- Department\n- Company\n- Region\n- Cost Center\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nSoftware model\n\n | \n\nSoftware model associated with the metric attributes.\n\n |
| \n\nMetric group\n\n | \n\nGrouping 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**.\n\n |
| \n\nLicense metric\n\n | \n\nThe license metric that the software license is counted against when reconciliation is run \\(per user, per device, for example\\).\n\n |
| \n\nDescription\n\n | \n\nAttribute type description that is based on the license metric value.\n\n |
| \n\nAttribute\n\n | \n\nAttribute type for reconciling entitlement license metrics. For more information on each attribute type, see [Software model metric attributes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/sw-metric-attributes.md).\n\n |
| \n\nAttribute value\n\n | \n\nValue of the attribute \\(integer\\).\n\n |
| \n\nAttribute value is unlimited\n\n | \n\nOption for setting the attribute as unlimited.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nName\n\n | \n\nName 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 Core UI](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/t_AddAClientAccessRec.md) for more information on client access records in the Software Asset Management classic application. See [Create a software client access record in workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-asset-management/software-asset-management/create-clientaccess-workspace.md) for more information on client access records in the Software Asset Workspace.\n\n |
| \n\nCount\n\n | \n\nNumber 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.\n\n |
| \n\nType\n\n | \n\nType 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.\n\n- **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.\n\n- **User/Device CAL**: Licenses each user or device that accesses the associated server.\n\n**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.\n\n- **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.\n- **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.\n\n**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](https://support.servicenow.com/kb?id=kb_article_view&sys_kb_id=ef634dac83935610cdbbc430feaad3d9).\n\n |
| \n\nCost Center\n\n | \n\nCost center of the users or devices that are granted access to the associated server.\n\n |
| \n\nDepartment\n\n | \n\nBusiness department of the users or devices that are granted access to the associated server.\n\n |
| \n\nLocation\n\n | \n\nGeographic location of the users or devices that are granted access to the associated server.\n\n |
| \n\nCompany\n\n | \n\nCompany of the users or devices that are granted access to the associated server.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nDisplay name\n\n | \n\nSoftware publisher and product for the subscription.\n\n |
| \n\nUser principal name\n\n | \n\nUser's email address for the subscription.\n\n |
| \n\nSoftware model\n\n | \n\nSoftware model for the subscription.\n\n |
| \n\nLast activity\n\n | \n\nLast date when this subscription was last used.\n\n |
| \n\nInactive days\n\n | \n\nNumber 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.\n\n |
| \n\nSubscription profile\n\n | \n\nProfile that is associated with the subscription identifier.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nParent software model\n\n | \n\nParent \\(or the topmost hierarchy\\) of the software model.\n\n |
| \n\nSoftware model\n\n | \n\nSoftware 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.\n\n |
| \n\nSource\n\n | \n\nSource 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.\n\n |
| \n\nActive\n\n | \n\nOption 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.\n\nTo deactivate a downgrade right, double-click the field to display the toggle button, select **false**, and then select the Save icon \\(\\[Omitted image \"save-icon.png\"\\] Alt text: Save icon\\).\n\n- **false**: deactivates the downgrade right on the software model and on the related software entitlements.\n- **true**: reactivates the downgrade right on the software model and on the related software entitlements.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nDisplay name\n\n | \n\nName of the discovery model. This value is generated automatically using the discovered publisher, discovered product, and discovered version.\n\n |
| \n\nNormalization status\n\n | \n\nStatus of the normalization process:- Normalized\n- Partially Normalized\n- Publisher Normalized\n- Match Not Found\n- Manually Normalized\n- New\n\n |
| \n\nPublisher\n\n | \n\nNormalized publisher of the software.\n\n |
| \n\nProduct\n\n | \n\nNormalized product name of the software.\n\n |
| \n\nVersion\n\n | \n\nNormalized version of the software product.\n\n |
| \n\nEdition\n\n | \n\nNormalized edition of the software.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nPublisher\n\n | \n\nName of the publisher.\n\n |
| \n\nProduct\n\n | \n\nName of the software product.\n\n |
| \n\nVersion\n\n | \n\nLicensable version of the software.\n\n |
| \n\nFull version\n\n | \n\nGranular licensable version of the software.\n\n |
| \n\nEdition\n\n | \n\nEdition of the software.\n\n |
| \n\nLifecycle phase\n\n | \n\nLife-cycle phase values include:- **Pre Release**: Date the software was pre-released.\n- **General Availability**: Date the software became generally available to the market.\n- **Upgrade**\n\n**Note:** Only shown when the **Lifecycle type** field is Internal.\n\n- **End of Life**: Date by which the software will no longer be manufactured by the publisher.\n\n**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](https://learn.microsoft.com/en-us/lifecycle/policies/fixed).\n\n- **End of Support**: Date by which the software will not be enhanced by the publisher.\n\nThis value corresponds to the Mainstream Support end date for Microsoft according to its [Fixed Lifecycle Policy](https://learn.microsoft.com/en-us/lifecycle/policies/fixed).\n\n- **End of Extended Support**: Date by which the publisher will no longer provide any support or updates to the software.\n\nThis value corresponds to the Extended Support end date for Microsoft according to its [Fixed Lifecycle Policy](https://learn.microsoft.com/en-us/lifecycle/policies/fixed).\n\n\n |
| \n\nLifecycle type\n\n | \n\nThe product life cycle type values include:- **Internal**: The life cycle date is specific to the customer \\(for example, based on their internal policy, based on a custom contract/agreement with the publisher\\).\n- **Publisher**: The life cycle date comes from publisher sources and is not specific to a customer.\n- **Publisher Add-On**\n\n |
| \n\nSource\n\n | \n\nSource 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**.\n\n |
| \n\nDescription\n\n | \n\nDescription of the software product life cycle.\n\n |
| \n\nPhase start date\n\n | \n\nDate when the life-cycle phase starts.\n\n |
| \n\nRisk\n\n | \n\nRisk 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:\n\n- Very High\n- High\n- Moderate\n- Low\n- None\n\n |
| \n\nActive\n\n | \n\nOption 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.\n\n |
| \n\nField\n\n | \n\nDescription\n\n |
|---|---|
| \n\nAssignment Group\n\n | \n\nName 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.\n\n |
| \n\nStatus\n\n | \n\nCurrent status of the group allocation to the software model. Possible values are:- **New**: When a group allocation is created, this field is automatically set to New.\n- **Not allocated**: None of the group members are allocated to the software entitlement.\n- **Fully allocated**: All the members from the user group are allocated to the software entitlement.\n- **Partially allocated**: A partial number of group members are allocated to the software model.\n\n |
| \n\nActive\n\n | \n\nIndicates if the user group allocation to the software entitlement is active. Possible values are:- **true**: The allocation record is active and users from the assignment group are allocated to the software entitlement.\n- **false**: The allocation record is inactive and the users from the assignment group aren't allocated to the software entitlement. When a user group is changed to inactive, the group allocation record is marked as inactive and the **Allocated Quantity** field value is updated.\n\n |
| \n\nLicense metric\n\n | \n\nUser-based license metric for user allocation to the software entitlement. License metric values include:- Per Named User\n- Per User\n- User Subscription\n\n |
| \n\nGroup Members\n\n | \n\nNumber of users available in the assignment group.\n\n |
| \n\nSoftware model\n\n | \n\nField value is automatically set to the selected software model.\n\n |
| \n\nAllocated Quantity\n\n | \n\nNumber of users from the assignment group allocated to the software entitlement.\n\n |
| \n\nEntitlement condition\n\n | \n\nEntitlement condition defined to apply the group user allocation on the filtered software entitlements.\n\n |