Best practice Software Model usage within SAM Pro

[Serkan Yilmaz]

Hi SNC,

I'm wondering if there are best practice guidelines for setup Software Models.

What I mean is on which level do we need to create Software Models?

Options:

1. Software Product has multiple Software Models per version/ edition and all these Software Models have their own lifecycle and entitlements per version/ edition.

2. Software Product has one Software Models for any versions/ editions and contains lifecycle and entitlement data for any versions/ editions.

Which option do you prefer and what is the best practice of ServiceNow?

Hoop to hear from you!

Cheers,

Serkan

[dreinhardt]

Hi @Serkan Yilmaz ,

if we have a PPN (SKU) for a software entitlement, then we first use this data when creating entitlements and let the system create the associated software models. If there is no PPN available, we create the software model as detailed as possible with regards to the proof of purchase. Furthermore, it also depends on how detailed certain relationships need to be mapped, or whether a license balance based on manufacturer/product & any version is fine for the customer & vendor :).

Best, Dennis

[Serkan Yilmaz]

Hi @dreinhardt,

Does this means that ServiceNow don't have a best practice in this?

The reason why I'm asking this is that the auto generation of Software Models doesn't have a "logic", because sometimes the Software model gets a lot of details, such as version, edition etc. and sometimes it gets created as a generic Software model without version and contains with this configuration multiple installations/ Discovery models.

Hope to get guidelines of ServiceNow in this, because they should have a vision on SAM Pro...

Cheers,

Serkan