Software Discovery Model Creation

[Mark Porter]

I'm hoping someone can help me, I'm trying to get my head around Software Discovery Models as part of the SAM Suite. With every load of data I've completed into the Software Installations table including Security Updates I'm getting a corresponding discovery model created even though the article below says it shouldn't.

https://docs.servicenow.com/bundle/london-software-asset-management/page/product/software-asset-management2/concept/c_DiscoveryModels.html

Am I just misunderstanding it or is there a script somewhere that I just haven't seen yet? Any help you can give me I would greatly appreciate.

[cody_wolf]

A few things...

Confirm you have SAM-Pro plugins activated

If yes...

1 Discovery Models can tie to N Software Installs.

Normalization is ran against the Discovery Model table

1 Software Model ties to N Software Entitlements

Discovery Map on the SW Entitlement is how we tie-off Software Installs to Software Entitlement rights.

PDF attached - (Content Service_

Here is a snip of the data model...

[Jeffrey Wu]

hi, what about the relationship between Discovery model and Software model, is it 1 Discovery Models can only tie to 1Software model？

[Daniel Slocum]

Hi Mark,

The "Create a Software Normalization" Business Rule on the Software Installations table both inserts a Software installation record and either links that record to an existing Discovery Model, or creates a new Discovery Model and normalizes the Discovery Model using values from the ServiceNow SAM Content Library.

As Cody mentioned in his reply above, in most cases there will be a many to one relationship between Software Installations and a Discovery Model.  If you are seeing only one to one relationships between Software Installations and Discovery Models, something is wrong and you should open a HI incident.  

Daniel

[Mark Porter]

Thanks for the replies, we're using the SAM Foundation plugin so obviously different to what you've mentioned. The discovery models all seem to create successfully and we end up with many installations against one discovery model but what I need to know is how the line below is supposed to happen, I can't see any scripts so far that prevent that from happening.

"Discovery models are not created for software installations that have a name containing Security Update"