Best Practice for Entitlement Matching When Edition Field is Missing from Normalized Discovery Model

[YILMAZA]

Hi SAM Community,

Looking for guidance on a compliance gap we're running into in our SAM Pro implementation — specifically around entitlements failing to match normalized discovery models due to a missing edition field.
 

Background

In our environment, the edition field is often not populated by discovery sources. This happens for two reasons: either the discovery source doesn't capture it, or the installer itself doesn't carry edition information (e.g., TechSmith and similar edition-less installers). Even after SAM Pro normalizes the software installation discovery models, the edition field is frequently left empty.
 

The result: entitlements that specify an edition remain unmatched against the corresponding discovery models, creating inaccurate compliance positions.

This gets more complex when multiple editions or plans exist in the environment but the software installs table doesn't differentiate between them — making it unclear which install maps to which entitlement.
 

What We've Already Tried — Publisher Part Numbers (PPNs)

We are already using Publisher Part Numbers (PPNs) for entitlement creation. Our process is to select PPNs from the content library to match the exact software model that corresponds to what we're purchasing. This should, in theory, provide a precise match — but it doesn't fully solve the problem.

The issue: the Discovery Map (DMAP) linked to a given PPN carries additional fields, including edition. Because the discovery models normalized by SAM Pro don't have the edition field populated, they fail to match against the DMAP associated with the PPN — even when everything else aligns. So "using PPNs" alone is not a reliable solution for these cases. We are using PPNs and DMAPs from Content Library to create correct entitlements and still facing this issue.

What We're Considering

We see two potential paths forward:

Option 1 — Pattern Normalization Rules: Use pattern-based rules to inject edition data into discovery models. The risk here is incorrectly normalizing installations that shouldn't be categorized under a given edition, potentially creating false compliance positions. When multiple plans/editions exist under one entitlement but installs carry no edition, how do we ensure correct mapping without over-normalizing?

Option 2 — Downgrade Rights via Software Models: Create dedicated software models reflecting downgrade rights (covering both version and edition) and associate them as downgrade entitlements. More controlled, but adds meaningful model maintenance overhead.

What We'd Like to Know

• Which of these approaches aligns with ServiceNow SAM Pro best practices?
• Are there other recommended approaches we haven't considered?
• How should PPNs and DMAPs be used effectively when discovery data lacks edition information and DMAP specifies edition?
• What are the compliance and audit implications of each approach?
• Has anyone handled edition-less installers in a scalable way without risking false compliance?

Any pointers to relevant ServiceNow documentation or KB articles, or your applied experience/suggestions would be very helpful. Thanks in advance

[pr8172510]

Hi @YILMAZA,

Publisher Part Numbers (PPNs) should be used to create software entitlements, while Discovery Maps (DMAPs) are used during normalization to associate discovered software with the correct software model.

If the discovery source does not provide the attributes required by the DMAP (such as Edition), SAM Pro cannot reliably match the normalized discovery model to the entitlement. In this scenario, the limitation is the quality of the discovery data rather than the entitlement configuration.

For your options

• Pattern Normalization Rules should only be used when you can reliably determine the edition from discovery data. Populating the Edition field based on assumptions can lead to incorrect normalization and inaccurate compliance results.
• Downgrade Rights should only be configured when they are supported by the publisher's licensing terms. They are intended to model licensing rights, not to compensate for missing discovery attributes.

From a compliance perspective, it is generally better to leave an installation unmatched than to force a match using inferred edition values.

If edition is required for accurate reconciliation, the recommended approach is to improve or enrich the discovery data so the required attributes are available before normalization.