How is Potential Savings calculated in SAM, It shows 0$

[susmitha17]

How is Potential Savings calculated in SAM, It shows 0$

[PrashantLearnIT]

HI @susmitha17 

Here's how the potential savings are typically calculated and what you might need to check:

 Calculation of Potential Savings

1. Unused or Underused Software:

   - Identify software installations that are unused or underused. Unused software is installed but not used at all, while underused software is used less frequently than the defined threshold.

2. License Cost Information:

   - Ensure that the cost per license is entered correctly in the software model record. This cost information is crucial for calculating potential savings.

3. Normalization:

   - Software installations need to be normalized correctly to the right software model. Normalization ensures that usage data is correctly associated with the software models.

4. Usage Data:

   - Accurate and comprehensive usage data is necessary. This data can come from various sources such as SCCM, JAMF, or other discovery tools integrated with ServiceNow.

 Reasons for $0 Potential Savings

1. Missing Cost Data:

   - Check if the cost per license is entered correctly in the software model. Without cost data, potential savings cannot be calculated.

2. Incorrect Normalization:

   - Ensure that software installations are normalized correctly. Misnormalized installations won't be associated with the correct software models and their costs.

3. Lack of Usage Data:

   - Verify that usage data is being imported and is up-to-date. If the system doesn't have recent usage data, it won't be able to identify unused or underused software.

4. License Compliance:

   - If the organization is already compliant and there are no unused or underused licenses, potential savings would naturally be $0.

5. Configuration Issues:

   - Ensure that the SAM configurations and scheduled jobs related to usage data collection and normalization are running correctly without errors.

 Steps to Troubleshoot

1. Verify License Costs:

   - Go to the Software Models and check that the license cost is entered for each relevant model.

2. Check Normalization:

   - Review the normalization results to ensure that software installations are correctly associated with the software models.

3. Review Usage Data:

   - Check the software usage data for completeness and accuracy. Ensure that the data sources are correctly configured and are regularly updated.

4. Run Scheduled Jobs:

   - Verify that scheduled jobs related to data collection and normalization are running successfully. This includes jobs like "SAM - Software Usage Data Collection" and "SAM - Normalize Software Installations."

5. Check SAM Compliance Dashboard:

   - Use the SAM Compliance dashboard to review the overall compliance status and potential savings opportunities.

6. Update Software Entitlements:

   - Make sure that all software entitlements are up-to-date and reflect the current license agreements.

By ensuring that all these aspects are correctly configured and up-to-date, you should be able to accurately calculate potential savings in ServiceNow SAM. If issues persist, it might be helpful to review the SAM documentation or contact ServiceNow support for more specific troubleshooting based on your instance configuration.

[susmitha17]

Hi @PrashantLearnIT ,

In OOB Instance, For Microsoft company, the potential savings are $0 where as for company named BOX there is some value. Do you know why this happens

[dreinhardt]

@susmitha17 ,

the definition per SN docs is the following:

Potential savings

Estimated cost of savings if software installations are reclaimed. The sum of all potential savings from all removal candidates.

If no removal candidates are calculated for MSFT you'll see no savings (requires M365 integration).

Best, Dennis