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 model to the rights that you've purchased.
They are the most adaptable and configurable aspect of SAM Pro. Hence, due to their inherent flexibility they require higher degree of maintenance and governance.
Process to assess software models
Steps to manage software models
|
Activity S.No. |
Activity |
Activity Details |
|
5.1 |
Review Software Models with inactive DMAPs |
Discovery Maps or DMAPs are updated by content services and provide the latest content related to downgrades, suite components, inference percentage and more. Make sure to use active DMAPs on your software models to be abreast with the latest authorized ServiceNow content. To understand ServiceNow discovery maps check here. Please note that this issue mostly arises when using non- SaaS Integrations (such as Server software). In SaaS integrations once the integration is setup the right software models with active DMAPs will always be selected Where to find the issue: Run health check- General Or check the report: Software models with deactivated Discovery Maps Recommended Actions for SAM Managers/Analysts: Ensure that software entitlements are linked to software models with an active Discovery Map (DMAP). This is typically done by selecting a Publisher Part Number (PPN) on the software entitlement, which automatically creates a software model with a DMAP that enriches the data with essential details such as downgrades, suite components, and inference rules. As best practice, always use the latest DMAPs to ensure the most up-to-date content is applied for correct license compliance calculations. However, if a PPN/DMAP is not available, you can create a software model manually but ensure that all enrichment information (such as downgrades/suite components) is properly populated for accurate license compliance calculations.
|
|
5.2 |
Review Software Models created without DMAP/custom DMAP |
Discovery Maps or DMAPs are updated by content services and provide the latest content related to downgrades, suite components, inference percentage and more. Make sure to use active DMAPs on your software models to be abreast with the latest authorized ServiceNow content. To understand ServiceNow discovery maps check here. Please note that this issue mostly arises when using non- SaaS Integrations (such as Server software). In SaaS integrations once the integration is setup the right software models with active DMAPs will always be selected
Where to find the issue: Run health check- General Recommended Actions for SAM Managers/Analysts:
1. Review why you created it? Did you not have a PPN/available DMAP at that time. If yes, it might be prudent to delete this software model and associated entitlement and recreate with the right PPN- so that the right DMAP can be used If you don’t want to delete this software model- you can make sure that the right set of components and downgrades are added to it manually (Please note that this is not recommended as a best practice- as manageability of the same becomes difficult) 2. In some cases, you may want to create a software model without a DMAP for reasons such as - You want to consume licenses differently as per different licensing agreements (such as MS SQL Server on SPLA vs Enterprise agreement). Check the blog for more details here - You want to consume licenses differently as per different licensing models (SQL Server enterprise core vs Server/CAL licensing models). Check this KB article for details here - You want to ignore installs of a certain software on a certain environment (M365 software installs on Server, or SQL Server in passive environment) Please note that these are miscellaneous cases and are quite rare. In most cases, DMAP is recommended. In cases you are not using DMAP, please document the reasons for the same and check these software models on a continuing basis. |
|
5.3 |
Review Software Models with version and edition as anything or Having edition as anything |
For server products, it is not advisable to create software entitlements and link them to software models with the edition set to 'anything,’ or to software models having version and edition as “anything” as the edition is crucial for determining license compliance.
Where to find the issue: Run health check- General
Recommended Actions for SAM Managers/Analysts: 1. Check for Software models DMAPs having version and edition as anything: Before starting it is crucial to understand that for some small cases, certain DMAPs auto populate version and edition as anything for some software models- this is as per design and does not have an interference with license compliance calculations a. CAL records: CAL entitlements and software models don’t have a version or edition and hence they are marked as anything (example: SQL server user CAL created for PPN such as 359-0961) b. Microsoft P+SA entitlements: For Perpetual and Software assurance entitlement the software models created are also version and edition agnostic- in this case also the software models will be created through DMAP having version and edition as anything. Please note that based on when the SA expires the software model will “auto” upgrade to a specific software model with a specific version and edition (Example SQL Server entitlement for 7JQ-01677). Read about it here c. Only SA entitlements: Software assurance entitlements are also created with version and edition as anything. This works same as b (Example SQL Server entitlement for 7JQ-01678 is an only SA entitlement) 2. If the above cases don’t exist, ensure as below: For server products (such as Microsoft SQL Server, Windows Server), ensure that software entitlements are linked to software models with the edition field populated. This is typically achieved by selecting a Publisher Part Number (PPN) on the software entitlement, which automatically generates a software model with a Discovery Map (DMAP) that populates in the edition. If a PPN is not available and you need to create a software model manually, make sure to populate an edition on the software model and link it to the entitlement. As mentioned in 4.3 you may have a software model created for a product with version and edition as anything (with install condition) to ignore installs on a certain environment that is fine. Special scenario: For Oracle Products Following best practices apply:
|
|
5.4 |
Review Software Models with Install conditions created |
SAM managers and analysts seek methods to apply their software entitlements to environments or sets of software installations. They can utilize software model installation conditions (also known as software install conditions) or product installation conditions for this purpose. Used to apply conditions for specific software models. It is a mechanism that allows customers to control which software installations can be covered by a specific software model.
When software install condition feature is combined with License under management, the SAM Managers get even more control to exempt or ignore certain software installations from licensing,
More on this here and video of the same here Recommended Actions for SAM Managers/Analysts:
Setup of install conditions correctly leads to correct license compliance calculations. For example: If you setup an install condition such as to license all Cis on production environment but no CI is tagged as production will lead to no license being consumed.
Hence check for the following:
1. Will there be any match of my records using the installation conditions? Make sure that the condition is accurate and there is supporting data in the condition to pickup
2. Do I need to exempt (ignore) any software install records based on a condition (use Install condition + LUM= false)
3. Do I need to license a particular software model based on a condition? (use only install condition and if that software model has downgrades defined make sure to add the same
|
|
5.5 |
Review Product Install conditions |
Create product installation conditions in the Software Asset Workspace that apply across all software models of a product during reconciliation. Only those software products that meet the defined product installation conditions are included in the reconciliation process. Read about it here
Some Use cases where it can be used: 1. License All Visual studio and components on dev environment only 2. License all SQL server product and components on production environment
Recommended Actions for SAM Managers/Analysts:
Setup of install conditions correctly leads to correct license compliance calculations. For example: If you setup an install condition such as to license all Cis on production environment but no CI is tagged as production will lead to no license being consumed.
Hence check for the following:
1. Will there be any match of my records using the installation conditions? Make sure that the condition is accurate and there is supporting data in the condition to pickup
2. Do I need to exempt (ignore) any software install records based on a condition (use Install condition + LUM= false)
3. Do I need to license all software models for a particular product with a condition? (then use product install conditions and not software model install conditions)
Note: There are certain special scenarios where the installation of software from one publisher should be excluded from license calculations if it is bundled with a product from another publisher. For example, Oracle Java may be covered under the license of a Microsoft product. While such scenarios are valid, cross-publisher license recognition is currently not supported in SAM Pro. However, this capability is on our roadmap for future development. |
|
5.6 |
Review Software models created automatically through system property |
There is a system property that helps SAM managers/analyst auto create software models from installs. Read about it here The intent of this feature is to help SAM Managers determine why Product Results are non-compliant while all the software Model (s) are compliant. That happens sometimes because of missing software model for some installs which were not showing. Where to find: List view of software models with source= system property Recommended Actions for SAM Managers/Analysts: This property must be used with a lot of caution and only by mature customers as it can lead to a high number of unused software models. Best practice approach: 1. Delete the software models created through this property and thereby run reconciliation. Switch off the property 2. Check the install requiring action showing installs without a software entitlement 3. Create an entitlement and corresponding software model for those installs and thereby run reconciliation If you want to still use the automatic software model creation property, use it for a specific time and let the software models be created thereby switching it off. Verify the software models created and update the entitlement for them if they are correct
|
|
5.7 |
Review suite inference and associated component property |
Suite Inference is a ServiceNow SAM Pro feature that helps determine if the software (installed or subscribed) is a part of a software suite, so that it can be licensed efficiently. Check if these installs have been inferred correctly. Watch this video for details here and ServiceNow docs here and here: Recommended Actions for SAM Managers/Analysts: 1. Check the inference percentage (number) and mandatory/optional setting to make sure that it is set correctly based on your licensing and environment. For example: If a suite has a very high inference percentage, it means that all components of that suite need to be present for licensing the suite- this condition may not happen. Hence, it is advised to understand your infrastructure and licensing needs and change as desired. By default, SAM Pro sets the inference percentage as 75% (for some products it is different for example SQL Server it is zero percentage) 2. In some cases, there is a requirement to license the suite using its license and thereby license the component when the suite licenses run out. For example: License core infrastructure suite entitlement and then license the windows server entitlements In these cases, you need to turn on the property: use component licenses to optimize compliance when suite licenses run out to true
|
|
5.8 |
Review Duplicate software models |
SAM Pro checks for potential duplicate software models at the time of creation of them with a warning. However, for organization specific reasons, in some cases SAM managers might create them. Where to check: Check for a specific product- with a specific publisher, product, version /edition and check if there are multiple software models created. The multiple software models are a risk and my lead to incorrect software license compliance position Recommended Actions for SAM Managers/Analysts: 1. Check if the software models have different install conditions, subscription conditions or different entitlements- if they are truly different you can keep them Otherwise, you can delete the same make sure to transfer the entitlement to the main software model before deleting the duplicate software model
|
|
5.9 |
Review restricted software model |
The Restricted software model helps SAM managers remove unauthorized software from the environment. Please check the video here.
Recommended Actions for SAM Managers/Analysts: Review the restricted software model flag and make sure it is still needed. If not unflag the same |
|
5.10 |
Review requirement to update metric attributes |
Software model metric attributes control how licensing is applied; they are added automatically based on the license metric selected on the entitlement. ServiceNow ships the metric attributes as per the licensing models of the publisher Please read about them here.
Recommended Actions for SAM Managers/Analysts: Review the metric attribute and change the values if required. |
|
5.11 |
Review requirement to add CAL records |
As mentioned in 4.9 CAL records are important for certain licensing models. Hence ensure that CAL records and created and linked to the software models. Recommended Actions for SAM Managers/Analysts: Review the software models linked to user/device CAL entitlements and thereby create CAL records for them to be licensed |
|
5.12 |
Review matching discovery models |
Click on the Matching discovery models tab on the software model form to verify if the software model is linking to any of the Discovery models created. This is a useful way to verify if the software model with license installs any installs linked to the discovery models. Recommended Actions for SAM Managers/Analysts: Review the Matching discovery models tab for the software model created and make sure that there are discovery models being shown on the same Perform the exercise- for each downgrade of the software model, as well as its components if any. Check figure below for details |
Common FAQs
Q1. Does software model need to be created first or software entitlements as per best practise?
Ans. a. In server software- it is best to create entitlements from PPN which create the right software model with the correct DMAP.
In SaaS Subscription as subscription integration automatically creates software models with the right DMAP it is best to first let them be auto created and then add the entititlements
Q2. What is meant by software model result and why does it show blank for some software installs on the list view?
Ans. It is the part of the three tier reconciliation results i.e. Product results, software model results and license metric results. Check details here.
A software model results record is created only when a software model or entitlement exists for the software product. Hence, if there is no entitlement/model to cover the software install the software model result will be empty for the sofware install.
Q3. What is next version of software model and why is it important?
Ans. Next version shows the next version of the software that is provided by the publisher. For example Microsoft SQL Server 2022 Standard would be the next version of SQL Server 2019 Standard. In most cases this is auto updated by ServiceNow content services. It helps to auto assign the latest software model to the entitlement to help customers use the benefits of the latest version released when they are have software assurance enabled wich auto applies the new version benefits.
Q4. If I set the lifecycle stage status of the software to retired, will it not be considered for licensing?
Ans. No. SAM Pro doesnot determine the license compliance based on the life cycle stage status of the software model. You can delete the software model if it has no entitlements.
Q5. Should I be using the automatic software model creating property?
Ans. Only if you are mature in your SAM processes. The property creates too many software models which may make the task of maintenance of software models very tough. The intent of the property was to help customers determine why Product Results are non-compliant while all the software Model (s) are compliant. Customers were getting confused why the product result showed as non-compliant whereas the software model under it was compliant. That was because of missing software model for some installs which were not showing. The better approach may be to use the install requiring action to guide you to create software models:
Currently, we show the install requiring action for install missing entitlement and show reasoning details, so customer understand that for these installs there are no entitlements/software models, and they can add entitlement /software models to cover these software installs. This is a better way for customers to create software models from entitlements rather than from installs, as it will create software models is a more manageable way.
Q6. Should I remove unused software models and perform cleanup?
Ans.
Yes, That’s a sound strategy, since outdated software models can clutter your environment and skew your license-compliance figures. As you clean up, focus on the following:
a. Software models not linked to entitlements
Many models are created automatically for downgrade or suite components, but others may have been added manually. Identify any models that aren’t connected to entitlements and delete them if they serve no purpose.
b. Duplicate software models
Look for models with identical product, publisher, version, edition, and installation or subscription conditions. If you find duplicates, keep the most accurate one and remove the rest.
c. Automatically generated software models
Models created by the automatic-creation feature often end up detached from entitlements. Review these and eliminate any that aren’t needed.
Q7. What is the criteria that SAM Pro uses the consolidate entitlements with one or more license metric results?
ServiceNow SAM Pro automatically consolidates (adds up) entitlements that share identical downgrade rights, license metrics (licensing models), consumption rules, software model, and maintenance status. When those attributes match, the product rolls the entitlements into a single license-metric record so the software model reflects the correct total consumption. If any attribute differs—say, the downgrade rights—the entitlements stay separate and generate individual license-metric results.
Note:
SAM Pro does not consider PPN or pack information when differentiating entitlements, as these are purely purchasing details and do not impact final license consumption or compliance. For example: Microsoft confirms that a 2-core pack and a 16-core pack provide identical usage rights. In fact, eight 2-core packs and one 16-core pack are priced the same.
Excerpt from the Microsoft Windows Server Licensing Guide here:
- Page 20: Core licenses are available in 2-packs and optional 16-packs (for convenience). Eight 2-packs and one 16-pack cost the same and grant equivalent usage rights.
- Page 21: Core licenses can be purchased in 2-packs or optional 16-packs, and each individual license may be assigned to a separate physical server.
