Minimum Viable software Model

[Gowthaman Jayab]

Hi community

Iam trying to find out all the installation records associated with the software model. Can we use the field Minimum Viable Software Model field in the software installation table for establishing the relationship? I understand that this field gets populated during reconciliation process but will this be available for all the installation records ?Can someone help to understand this in detail ?

Thanks

[Daniel Slocum]

The baseline product does not have an attribute directly linking SW Installations to SW Models.  Reconciliation queries the Discovery Model table using the values populated on the SW Model when a Discovery Map is selected, then the SW Installations that are related to the Discovery Model are used in compliance calculations. 

You mention the Minimum Viable Software Model attribute. This will not be available for every SW Installation record. Some SW Installs are not considered by the reconciliation engine for a number of reasons two of which are that they are for not licensable software or the installation is related to an excluded Configuration Item.

This is a forward-looking statement covered by Safe Harbor. The ITAM BU is working on a reporting solution to assist with this use case which is expected to ship in Tokyo or Utah.

One last note with two ideas that you might explore. There is a "software_model" attribute on the Installation record that was used by the older SAM Plugin but is not used by the Software Asset Management Product (frequently called SAM Pro). Some customers have invested in efforts to keep this value populated either through automation or through manual efforts.  A second idea is to develop a database view to achieve your goals. You'd need to build something similar to what @Alex Panzarella developed to report on software lifecycles. 

[Gowthaman Jayab]

Hi Dan

ok, as long as the reconciliation engine populates the Minimum Viable Software Model for the install records that are considered for compliance calculation, I think that makes sense. 

Hope the you are referring the software_model field in discovery model not in install table. Right now am exploring this.

On the other suggestion, I don't think you can create a view like @Alex Panzarella suggested as there is no direct relationship or common field between SM,DM and install table. We need to do scripting to interpret the DMAP conditions and match it with discovery models.

Thanks