FAQ

How is spending per user calculated with respect to per month and rolled up for YTD?

Spending per user is calculated based on the chargeback settings, which can be configured for each application within the application overview. You can select the appropriate chargeback setting depending on whether the spend needs to be attributed only to licensed users, all active users, or in a custom manner.

In such cases, all mapped transactions for the application are distributed proportionately across the users.

For year-to-date (YTD) spending per user, the spend per user per month is aggregated and displayed.

How does Zluri Calculate Estimated Wastage & Savings?

Optimization is a core offering of Zluri. Here’s how Zluri calculates estimated wastage and savings:

Zluri categorizes licenses into five different buckets:

1. Unassigned: The number of licenses not assigned to any user or lying surplus.
2. Un-de-provisioned: Licenses assigned to users marked inactive in SSO.
3. Unused: Licenses assigned to users who have not used the application in the last 30/60/90 days (configurable).
4. Underused: Licenses assigned to users with usage below 30%/40%/50% (percentage is configurable).

Potential Savings is calculated as the sum of licenses multiplied by the cost of a license per month.
Estimated Wastage is calculated by counting the number of optimizable licenses in the last month that were not unassigned from the user.
Realized Savings is presented as an annualized number based on the licenses identified as optimizable and unassigned from the user.