Hi Carrie,
If we want to intelligently set the AWT Limit(rather than blindly set the value of 50), then should we be doing the following analysis?
1.Check history resusage data and probe values of WorkTypeMax08 to find the maximum value(on an average) we get in this column. Here I have one question. The value in WorkTypeMax08 is the maximum "NEW" expedited messages received right?
2. Check if tactical work is getting delayed anytime in the day using the delaytime column in DBQL
3. If there is ever delay in tactical work, then deep dive all such delay instances using rewind feature of viewpoint and find out the average number of requests that get delayed whenever tactical stuff suffers delay. Lets say the number is x
4. Set awt limit as (reservedawts * 2) + 2 + x.
Regards,
Suhail
Hi Carrie,
If we want to intelligently set the AWT Limit(rather than blindly set the value of 50), then should we be doing the following analysis?
1.Check history resusage data and probe values of WorkTypeMax08 to find the maximum value(on an average) we get in this column. Here I have one question. The value in WorkTypeMax08 is the maximum "NEW" expedited messages received right?
2. Check if tactical work is getting delayed anytime in the day using the delaytime column in DBQL
3. If there is ever delay in tactical work, then deep dive all such delay instances using rewind feature of viewpoint and find out the average number of requests that get delayed whenever tactical stuff suffers delay. Lets say the number is x
4. Set awt limit as (reservedawts * 2) + 2 + x.
Regards,
Suhail