relations between tables of SAM

[kiran kumar m1]

I want to know the relation between 

software installation table

software discovery model table

software model table

software entitlements

Discovery maps

and is there any metric to measure how much we have consumed the license for suppose if its a subscription based is there any metric to say you have used 6 months or 3 months like that ?   

please explain in layman terms 

[MercBuilding]

Hi @kiran kumar m1 ,

   PFB explanation of tables.

software installation table - This table is populated automatically through discovery. It brings in the details of all the installations on desktops/laptops/servers etc based on your discovery coverage.

software discovery model table - The data in this table also automatically created when software installations are created. When discovery creates an entry in installation table , it will combine the list of installations which has same display name and create one discovery model for all the installations. This will be Normalized later based on discovered name, version etc.

software model table - The data in this table can be created automatically by enabling a property or we can create them manually if any software model for which we want to create entitlement doesnt exists in the system already.

software entitlements- The data in this table is created manually by uploading template or creating each record manually. This holds the information of what licenses the company owns, how many rights does it owns, expiry of those licenses, cost of the licenses etc.,

Discovery maps - This table is populate by ServiceNow 'Content Service', it just has the data related to publishers, product, versions, editions etc., On a software model it is best practise to have discovery maps populated on them.

Hope this helps! Let me know if you have any other questions.

[kiran kumar m1]

Hi @MercBuilding  thank you for your response , I want to know how they are related with each other 

like based on PPN/model/version/edition  software entitlement and software model are related

similarly

Is software model is related with software installation through discovery maps ?

[MercBuilding]

Hi,

 So PPN is stored in different content service table, if you have PPN with vendor and if all the details like product, publisher, version, edition etc then while creating entitlement which have PPN you need not to create software model manually, with the given PPN, model will be created automatically. So PPN is something similar to model which holds details of publisher, product, version, edition, license metric, agreement type (which are mostly used in entitlements) . Software model is base to create an entitlement. S/w models holds the information of pub, prod, version, edition, platform and language  whereas entitlement holds the financial details, start date ,end date, metric, agreement type etc.

S/w models, s/w entitlements -> displays the information related to licenses we own.

S/w discovery models (normalized, partially normalized) - > gives the information regarding what has been installed in our environment.

Discovery maps ties the software models with software discovery models based on normalized values of pub, product, version and edition on discovery models with pub, product, version and edition details on s/w models. Even without creating the DMAP's this is tied but as a best practise it is advised to create DMAP's.

Mark this as helpful, if it helped you in understanding basics of SAM tables.

[Tony_H]

Is it possible to explain the best way of uploading user allocations into software entitlements? I understand that this can be done manually on an individual basis, but if you have a large number of subscribers this isn't feasible. Are there jobs that run that do this? (import m365 subscriptions for example)