Automatic creation of software model

AvinashKumar27
Giga Contributor

Hello Everyone,

 

We recently enabled automatic creation of software model for "Not - Licensable" product type and post that we see that software models are being created for Patch, Child & Drivers too which we don't actually want to manage.

 

Is there any option to limit the model creation only to "Licensable" and "Not Licensable" and anything with product type irrespective of this can be simply ignored from automatic creation.

 

I understand the under properties there is only two options for Licensable and Not - Licensable but enabling Not -Licensable triggers software model creation for Patch, Driver or child component as well.

 

Do let me know if anything can be done in this case through Business rules.

@Srinivas Ramanu 

Thanks,

Avinash

4 REPLIES 4

dreinhardt
Tera Sage

Hi @AvinashKumar27,

I confirm your finding, by default SAMP will create software models for all product types (incl. Child, Patch, ...)

Of course, you could block the "INSERT" of the not wanted software models with the help of a BR.

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

AvinashKumar27
Giga Contributor

Thanks @dreinhardt  for the insight.

@AvinashKumar27,

are you able to share more insights about the decision to enable the option to create "non-licensable" software models? From a SAMP (e.g., Workspace) point of view the benefit is almost 0, as the models are not included into any reconciliation or license balance.

 

Best, Dennis

Should my response prove helpful, please consider marking it as the Accepted Solution/Helpful to assist closing this thread.

Not the OP, but from our point of view:

 

Just because a software product does not need a license, does not mean that it does not require Software Asset & Lifecycle Management.

 

We still need to answer, no matter the license type: 

  • Is this the right software product to solve this functional requirement (to stop software proliferation)
  • Has the capability owner agreed that this product can be used in our organisation (using the TRM)
  • Has this software product been checked for security vulnerabilities (now and going forward)
  • Is someone checking to see if the terms and conditions change so that the product is now licensable. 
  • Has someone checked that there are no data impacts in using this product (i.e. it is sending some of our data into a 3rd party where we have no control over it.)

We are using SAM Pro for more than just counting licenses. If we needed to just count licenses, instead of doing full end-to-end software asset management, we would still be using our old software license tool!