How do you link cmdb_sam_sw_discovery_model with cmdb_software_product_model in SAM Pro?

Bhagirath Bhar1
Kilo Contributor

Looking to further understand how one can link cmdb_sam_sw_discovery_model with the cmdb_software_product_model table with SAM Pro.

With SAM Plugin there is a model field through which the relationship gets made. There is also a discoverymodelmatcher script mentioned here - https://docs.servicenow.com/bundle/paris-it-service-management/page/product/asset-management/reference/r_InstalledWithSoftwareAssetMgmt.html that I was wondering if it can be used with SAM Pro or not.

1 ACCEPTED SOLUTION

Vivektietsood
Tera Guru
Tera Guru

There are two parts to this answer. 

One Normalization - This is the act of normalizing the software information in ServiceNow. When discovery runs you get information populated on software installation table (CMDB_sam_sw_install).

This installation information is compared with s/w discovery model (cmdb_sam_sw_discovery_model), and then an entry is made as a reference to the S/W installation record.

The third step is the comparison of discovery model information with central software library to make an entry in the software model table ( cmdb_software_product_model)

This is available in SAM Pro

This completes the Normalization part

Second - Reconciliation  - This is related to license true-up or calculations to find out if enough license are procured or used or additional need to be ordered. 

In this process software model cmdb_software_product_model) is compared with discovery map to create reconciliation (samp_reconciliation_result) and license report (Samp_license_position_report).

This is available in SAM Pro

Please look at the following graphic to understand the relation between S/W install table, Discovery Model and Software Model. 

find_real_file.png

Please mark helpful or accept solution so that it helps others with a same question. 

View solution in original post

4 REPLIES 4

Vivektietsood
Tera Guru
Tera Guru

There are two parts to this answer. 

One Normalization - This is the act of normalizing the software information in ServiceNow. When discovery runs you get information populated on software installation table (CMDB_sam_sw_install).

This installation information is compared with s/w discovery model (cmdb_sam_sw_discovery_model), and then an entry is made as a reference to the S/W installation record.

The third step is the comparison of discovery model information with central software library to make an entry in the software model table ( cmdb_software_product_model)

This is available in SAM Pro

This completes the Normalization part

Second - Reconciliation  - This is related to license true-up or calculations to find out if enough license are procured or used or additional need to be ordered. 

In this process software model cmdb_software_product_model) is compared with discovery map to create reconciliation (samp_reconciliation_result) and license report (Samp_license_position_report).

This is available in SAM Pro

Please look at the following graphic to understand the relation between S/W install table, Discovery Model and Software Model. 

find_real_file.png

Please mark helpful or accept solution so that it helps others with a same question. 

Hi Thank you for your reply, this makes a lot of sense, I guess my question is around this graphic in particular, if you see the flow of links between the ci_service record right down to the software_product_model. Due to the process between the discovery_model table and the SW model table now, is there a similar flow of links that I could derive in SAM Pro?

Direct link between a CI Service/Business Application to its respective Software Product Model

Thank you again

I see - out of box in software model table nothing like this is available. But I poked around in schema and found there is a link between Business App (cmdb_ci_business_app) to software model. So you should be able to create a view picturing model with business app

find_real_file.png

 

I found another interesting one CI Server to Asset. Please mark helpful or accept solution so that it helps others with a same question. find_real_file.png

Alex Panzarella
ServiceNow Employee
ServiceNow Employee

The linkage between Discovery Models (cmdb_sam_sw_discovery_model) and Software Models (cmdb_software_product_model) are built into SAM Pro out of the box with no configuration required.

The idea is you have raw data coming into the software install table (cmdb_sam_sw_install), it gets normalized in the Discovery Model table, and then the Software Model references what Discovery Models it wants to include the compliance position.