Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.

Software models and entitlements

Log in to subscribe to topics and get notified when content changes.

Software models and entitlements

A software model is a profile of the software that you've purchased, including information about the publisher, version, and discovery map. Software entitlements are used to relate the software profile to the rights that you've purchased.

Software models

Software models are used to record publisher information and create a profile. By recording your publisher information, you can link multiple entitlements in one to one profile, which allows you to monitor license information.

If you delete a software model, all records related to the software model, in the Downgrade Rights [samp_sw_downgrade_model and samp_downgrade_model] tables, are automatically deleted.

Software suites

For any software model that you create, you can specify whether the model is a suite (parent) or a component (child). A software suite is a group of related software offered as one. For example, Microsoft Office Professional is a suite of office productivity software tools that includes PowerPoint, Word, Excel, Outlook, and Access. Each of the software tools included in that suite would be a component.

A software model can also be a component in multiple suites. For example, Microsoft Word is a component in Microsoft Office Standard and Microsoft Office Professional.

If a software model contains child components and is automatically created as part of a scheduled job, the components are created automatically. The components appear in the Suite Components sub tab.

Use the Inference percent and Mandatory fields if the suite parent is not defined in the install table.
  • Inference percent: Specifies what percentage of the components in the suite must be installed for the software to be identified as a suite.
  • Mandatory: Enforces whether a specific component in a suite must be installed to infer that the suite is installed. The choices are: Optional, Always Mandatory, and Mandatory Group.

For example, you can specify the Inference percent as 80% and set the Mandatory field to Always Mandatory on Microsoft Access. These settings specify that Microsoft Access must be installed, along with three out of four other products (Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and Microsoft Outlook) to infer that Microsoft Office Professional is installed on a device.

When a suite parent is detected during reconciliation, the suite components do not count for the individual license.

For subscriptions, if you have a subscription to a suite parent, any related child component installations on that device are inferred as part of the suite parent, because the suite parent license determines compliance. If you have a subscription to a child component of a suite parent, the related child component is not inferred as part of the suite parent, and the child component license determines the compliance.

Software Model Lifecycle Report

You can also track a software model lifecycle phase for use with the Technology Portfolio Management.

View the Software Model Lifecycle Report to be informed about the products nearing end-of-life, end-of-support, and end-of-extended support. View the report by navigating to Reports > View/Run. The report is based on the scheduled job, SAM - Get install count for software model. You can also embed this report in your dashboard.

Software entitlements

To track the software rights for you software, create a software entitlement that can be linked back to the publisher information.

A software entitlement records the terms of your software license. By using software entitlements, you can:

  • Rapidly address if license allotment has been exceeded and return to compliant status by removing unauthorized software or ordering more licenses.
  • Lower the number of future licenses purchased if the license allotment is not being used completely.

For example, a company purchases a software entitlement for 100 rights. From the software entitlement, 100 employee or machine allocations are created that are rightfully assigned a license. If Discovery finds the software installed on 200 machines, the software asset manager must identify the employees or machines that have the software installed without a license, and remediate the situation.

Import software entitlements

Rather than adding you software entitlements individually, you can import a Microsoft Excel spreadsheet with all of your entitlements. If there are errors with your imported entitlements, an error record is generated with suggestions on how you can update the entitlement with accurate information.

Add your entitlement data to the Page 1 tab of the template file (samp_entitlement_import.xlsx) that can be downloaded from the Import Entitlement form. After you've added your entitlement data, you can uploaded the spreadsheet.

If a Publisher Part Number (PPN) is specified for the entitlements that you import, the PPN is matched to PPN in the Content Service Library and the data is used to create software model automatically.

When the import completes, the total number of entitlements imported is shown, as well as any errors that occurred during the import. Errors can be viewed in the Entitlement Import Errors list, where several actions can be taken on the error (create part number, ignore error, or save for later).
Note: If a Publisher Part Number not found error occurs during import of the software entitlement (product, publisher, version, edition, platform, and language) but a discovery map is found, then a custom publisher part number is automatically created. If a discovery map is not found, you have the option to create a discovery map to be associated with the publisher part number.

If the import spreadsheet contains a conflicting (or missing) PPN, the PPN value is set to the value in the existing product definition, when available.

Note: If you import a batch of Microsoft entitlements and the License Duration field is set to Contractual, you must specify both a start and end date.

The step-up license type is only available if the publisher is Microsoft. If you try to specify another publisher, an error message is displayed.

To avoid import errors:
  • All cells in an entitlement row must contain a value, including cells with a list.
  • Each entitlement row must be unique.

Microsoft Software Assurance (SA) entitlements

Microsoft offers Software Assurance (SA) as a way to provide active maintenance to its users. It's important that software managers track the dates that are under active maintenance, along with licenses usage, rights, and user allocation.

As an example, if you're covered under Microsoft Software Assurance, you can also upgrade, or step up, a standard version of your software to an enterprise edition. Use the Software Entitlement form to link related versions of your software under active maintenance and your upgrades.
Note: You can step up at any time if you have the Microsoft Open Value agreement with Software Assurance.

For example, if you have the Microsoft SQL Server Enterprise edition with SA, for the license metric Per Core, you can run unlimited virtual machines on the host machine, irrespective of the number of physical cores that you have licenses for. For example, if you have a license for running only four physical cores on a host machine, you can run unlimited virtual machines on the host machine.

If a software entitlement is created while receiving a purchase order and if SA is activated on that entitlement, the entitlement is created with the following values:
  • License Type: Perpetual + Software Assurance.
  • Start date: <the current date>.
  • End date: Set this value to reflect the end date of the SA service.
Note: You cannot use SA entitlements to license your software, so SA entitlements are not counted during reconciliation. Reconciliation only considers perpetual license entitlements.
Feedback