...
| Expand |
|---|
|
To better understand how possible aggregation scenarios work, let’s look at the following example: | Column | Aggregation Type | Scenario |
|---|
| Hours Used/Borrowed | User | In our example, the results shown in the report are limited by Day. Scenario 1 The user uses 1 license for 8 hours. Calculation: 8 hours = 8 Hours Used Scenario 2 The user uses 2 licenses for 1 hour, then 10 licenses for 2 hours and 1 license for 2 hours.
Calculation: 1 hour + 2 hours + 2 hours = 5 Hours Used | | Max Used/Borrowed | User | In this example, the results shown in the report are limited by Day. Scenario 1 The user uses 2 licenses throughout the day.
Calculation: 2 licenses = 2 Max Used/Borrowed Scenario 2
The user uses 2 licenses throughout the day . One license is used constantly for the entire day, while the other one is used only for 1 hour.
Calculation: 2 licenses = 2 Max Used/Borrowed
| | Max Usage | User | In our example, the number of available licenses for a particular feature is 10. Scenario 1 The user uses 2 licenses throughout the day. Calculation: 2 licenses out of 10 licenses = 20% Scenario 2 The user uses 5 licenses throughout the day, but only 2 licenses are used for 1 hour.
Calculation: 5 licenses out of 10 licenses = 50% Scenario 3 The user uses 3 licenses throughout the day, but 8 licenses are used for 1 hour.
Calculation: 8 licenses out of 10 licenses = 80% |
|
Date Range
The Start Date, End Date, and Time Interval fields for which you wish to monitor license usage are interdependent, i.e. modifying the Start Date field affects the End Date field, depending on the selected Time Interval option. If you select the "Custom" option in the Time Interval options, then both fields (Start Date and End Date) can be modified; however, you will not be able to select the day earlier than the Start Date on the End Date field, and later than the End Date on the Start Date field, because the value on the other field will be automatically adjusted.