- Home
- FAQs
- General Features
- How Zluri Calculates Estimated Wastage & Savings?
How Zluri Calculates Estimated Wastage & Savings?
Optimization is one of the core offerings of Zluri. And this article explains how Zluri calculates estimated wastage & savings.
Zluri buckets the total licenses purchased into five different buckets.
Unassigned: The number of licenses not assigned to any user or lying surplus.
Un-de-provisioned: The licenses assigned to users who are marked inactive in SSO.
Unused: The licenses assigned to users who have not used the application since last30/60/90 days which is configurable.
Underused: The licenses assigned to users who have usage less than 30%/40%/50% . This percentage is configurable.
The potential savings is calculated as sum of licenses multiplied by cost of license per month.
The estimated wastage is calculated by counting the number of optimizable licenses in the last month which is not unassigned from the user in the last month.
Realized savings is presented as an annualized number based on the number of licenses which is identified as optimizable and are unassigned from the user.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article
Optimization is one of the core offerings of Zluri. And this article explains how Zluri calculates estimated wastage & savings.
Zluri buckets the total licenses purchased into five different buckets.
Unassigned: The number of licenses not assigned to any user or lying surplus.
Un-de-provisioned: The licenses assigned to users who are marked inactive in SSO.
Unused: The licenses assigned to users who have not used the application since last30/60/90 days which is configurable.
Underused: The licenses assigned to users who have usage less than 30%/40%/50% . This percentage is configurable.
The potential savings is calculated as sum of licenses multiplied by cost of license per month.
The estimated wastage is calculated by counting the number of optimizable licenses in the last month which is not unassigned from the user in the last month.
Realized savings is presented as an annualized number based on the number of licenses which is identified as optimizable and are unassigned from the user.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article