Software Lifecycle Reporting for Software Installation

[jmayger]

Hi All,

Currently facing a challenge whereby the customer wants to report on "End of Life" Software models specifically where the installation 'installed_on' is not retired. Seems simple enough, where we run into issues however, is the duplication of data from the 'sam_sw_product_lifecycle' table. 

I have configured the attached Database View that I am reporting on to do the filtering for installed_on.install_status and Risk Score. We are matching the Software Installation with the corresponding Product Lifecycle based on 'norm_product' and 'norm_full_version' 

The join on 'cmdb_sam_sw_discovery_model' was because we are receiving duplicates from the different editions stored in the 'sam_sw_product_lifecycle' table (See attached). Meaning that we are over reporting on the issue.  I have tried matching on Discovery Model edition and Software Product Lifecycle Edition, however the values are different between the tables or the edition value is simply empty, which the database view wont match on.

Has anyone been able to solve this, we want to report on the installation level so the 'End of Life Products' widget on the Software Asset Workspace doesn't suit this purpose.

[kaushal_snow]

Hi @jmayger ,

Please check below article, might be helpful for you:

https://www.servicenow.com/community/sam-blog/lifecycle-report-with-install-info/ba-p/2283634

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[jmayger]

Thanks @kaushal_snow 

Unfortunately, this produces the same result, whereby the installation record will pull multiple matches from the Software Product Lifecycle Table where the full version is the same but there are multiple editions of a Software.

Have you implemented something similar or do you use OOB Capabilities ?

Thanks

Jared

[dreinhardt]

Hi @jmayger ,

I can’t contribute to your question, but wanted to ask you about the following 

Currently facing a challenge whereby the customer wants to report on "End of Life" Software models specifically where the installation 'installed_on' is not retired

Isn’t it a invalid state or quality issue when you’ve sw install records for retired CI in your sw install table? By default a business rule takes care about the removal of all install records after the install_status changed to „Retired/Stolen“

best, Dennis

[jmayger]

Hi @dreinhardt 

This is true, however there have been some changes and most of the information is pre-Washington. Do you know which BR / Scheduled Job is doing this in current ServiceNow Versions ?

Thanks

Jared