End of life products & Lifecycle risk assessment

Lionel Falk
Tera Contributor

Dear Community,

Currently working on software lifecycle reporting and risk assessment. At least 2 paths allow to visualize the lifecycle:
A) From the Software asset overview and the "End of life products" widget
B) License usage > Reports > Software product lifecycle report

It turns out that the comparison between these 2 paths returns differences and missing information.

Question 1) for path A) how come these fields (Lifecycle phase, Product, Version, Full version, Edition, Software models, etc.) are empty? What must be done to get these values in this list?

LionelFalk_0-1732035610431.png

 

Question 2) for path B) Which Risk field must be used considering that each status of the lifecycle has its own Risk?

  • General availability lifecycle > Risk
  • End of Life lifecycle > Risk
  • End of extended support lifecycle > Risk
  • End of support lifecycle > Risk
1 ACCEPTED SOLUTION

dreinhardt
Tera Sage

Hi @Lionel Falk 

Question 1) for path A)

I was unable to reproduce this issue in two customer instances. Looks like a lifecycle normalization issue or another problem with the data processed for the report in your instance.

 

1) Ensure all linked software installation records / discovery models are normalized

2) Verify the following two jobs are completed - "SAM - Generate Software Lifecycle Report" & "SAM - Create Calculated Software Lifecycles"

Navigate to table [samp_job_log.list] & filter column "name" with "*lifecycle"

dreinhardt_0-1732134024993.png

 

Question 2) for path B)

- I would suggest to use the risk field related to the "current phase" per record.

dreinhardt_1-1732134652864.png

 

Best, Dennis

 

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

View solution in original post

1 REPLY 1

dreinhardt
Tera Sage

Hi @Lionel Falk 

Question 1) for path A)

I was unable to reproduce this issue in two customer instances. Looks like a lifecycle normalization issue or another problem with the data processed for the report in your instance.

 

1) Ensure all linked software installation records / discovery models are normalized

2) Verify the following two jobs are completed - "SAM - Generate Software Lifecycle Report" & "SAM - Create Calculated Software Lifecycles"

Navigate to table [samp_job_log.list] & filter column "name" with "*lifecycle"

dreinhardt_0-1732134024993.png

 

Question 2) for path B)

- I would suggest to use the risk field related to the "current phase" per record.

dreinhardt_1-1732134652864.png

 

Best, Dennis

 

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