This page was last edited on July 30, 2013, at 12:49.
Comments or questions about this documentation? Contact us for support!
License Reporting Manager uses the concurrent-seat measurement to indicate concurrent peak usage and time of the concurrent peak usage (rounded to the previous one-minute boundary). LRM determines peak concurrent-seat usage by calculating the actual number of seats instantaneously in use at one minute intervals.
A seat is a physical chair whose occupant is logged in to T-Server, Interaction Server, or SIP Server and provides data on Place and DN details. A login session includes login from a:
LRM assumes that each login session has a unique ID. Seat usage is based on a Place; when a Place is not available in the login session, seat usage is based on a DN.
The table below shows how the seat usage is determined by the Place and DN data in the login session.
Place name |
DN name |
Seat for which this login session is counted |
---|---|---|
Place 1 | DN1DN2DN3 | Seat 1 |
DN4 | Seat 2 | |
Place 1 | Seat 1 |
License Reporting Manager can be configured to calculate the number of concurrent seats. To calculate concurrent seats, LRM records the peak number of logged-in seats for each 24 hour interval, and the time of the concurrent peak usage.
LRM calculates concurrent seats by performing the following:
A data snapshot of concurrent peak use is used to calculate concurrent-seat measurements. Concurrent peak use is determined as the actual peak during the 24-hour period, using a continuously updated record of seats in use according to the license definitions. The data snapshot of concurrent peak use is an instantaneous snapshot taken at one-minute intervals.
The concurrent peak use calculation includes a method of filtering or minimizing the weight of concurrent-seat peak values, possibly on predefined time intervals. For example, during Agent shift change overlaps. This filtering mechanism is enabled by configuring the lrm-excluded-time option. For more information about how to configure this option, see Configuration Options.
To calculate concurrent seats peak usage data for a given period, the date and hour of concurrent peak usage during that period is also recorded.