Software Models

[Jay662]

Hello everyone,

Feels a little overwhelmed attempting to understand Software Models/Products. I understand that you need a 'Software Entitlement' that links to the software Model. We also have Software Product that gets linked to the Model. 

We have discovery running which has created 'Software Discovery Models' - Do these then link to a software model using reconciliation. 

Also is a software model required for every version?  

[Stephen42]

Hi Jay, welcome to the confusing world of SAM.

I've attached a diagram (can't recall where I found it) that I have pinned on my bulletin board and reference many times each day.  It shows the relationships between the various 'models'.  To answer your question, Software Models are linked to Discovery Models via the Discovery Map (samp_sw_entitlement_defintion)

The Entitlement and DMAP detail should be configured on your Software Model.  Software Models (if using Content Service detail) should have upgrade and downgrade rights, so, no, you shouldn't need a Software Model for each version, although Entitlements may be version specific.  Reconciliation takes into account the full picture, by Publisher, Title (product), Version & Edition 

Hope that helps you out somewhat

[Amarjeet Pal]

Hello @Jay662 ,

Hope below article will be helpful to you.

 A Software Model represents a specific version of a software product or suite. Each software model can have one or more associated Software Products, which represent the actual licenses or entitlements that are purchased for that model.

When you run discovery in ServiceNow, it creates Software Discovery Models based on the software that is discovered on your network. These models can be reconciled with existing software models in order to ensure accurate license compliance and usage tracking.

In general, it is recommended to create a separate Software Model for each major version of a particular software product or suite. This allows for more granular tracking and management of licenses and entitlements for each version of the software. However, this may not always be necessary depending on your organization's needs and workflows.

   +------------------+
              |  Software Model  |
              +------------------+
                   /         \
            1    /           \   *
                /             \
+----------------+     +---------------+
|  Software Prod |     |  Software Ent |
+----------------+     +---------------+
*                *      1               1
                 \    /
                  \  /
               +------+
               | User |
               +------+

Legend:
- The lines represent relationships between records.
- The numbers indicate the number of records that can be linked on each side of the relationship.

Explanation:
- Each Software Model represents a specific version of a software product or suite.
- Each Software Model can have one or more associated Software Products, which represent the actual licenses or entitlements that are purchased for that model.
- Each Software Product can have one or more associated Software Entitlements, which represent specific rights to use a particular software product or suite.
- A User record represents an individual who has been assigned a license or entitlement to use a particular software product or suite.

[mikew_samexpert]

This diagram provides additional context about Software Products

[Stephen42]

Mike,

FANTASTIC Diagram !   Anyway you can upload the actual file vs an image ?

Thanks.