Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.
NOTE: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
Search
Languages
Select Interface Language:
Advertising
Please contact us via the feedback page to discuss advertising rates.
The Itil Community Forum: Forums
ITIL :: View topic - Opening Support jobs as it comes in
Posted: Tue Apr 22, 2008 1:16 pm Post subject: Opening Support jobs as it comes in
Hello,
I'm sorry if this has been posted before but was wondering if any one can shed some light here.
With ITIL in mind, do you open support jobs as it comes in?
As in a logger logs a job in the logging system and it stays as new until some one at the service desk opens the call.
Even if the person isn't actively working on the issue do you still open the call to acknowledge to the user that the call has been accepted?
If this is the case then how do you assess how long the task took to resolve?
I have been doing this at my work and realised that I can't work out how long the staff has been taking to resolve a lot of the issues because after acknowledging the call they come back and resolve the call with descriptions, so I have no idea how long the actual issue took to resolve.
Joined: Mar 04, 2008 Posts: 1894 Location: Helensburgh
Posted: Tue Apr 22, 2008 4:51 pm Post subject:
Hi,
I'm not sure whether you are asking about elapsed time for the call or for the task.
You need to measure the time from the call is raised until it is closed satisfactorily. To do this you have to open the incident/request on receipt. That is the time the user experiences and if you have SLAs that is the time to be measured for the SLA.
If you want to know (and you do) how much work time the job costs, then your technicians must record their time to that job.
If you want to know how much time the job takes to work through the system, then you need to record start times for things like assigned or placed in queue, allocated to start work, ready for checking with user, etc.
Your service desk software should allow you to have a whole string of status types that a call will go through allowing you to break down your analysis as you want.
You also have to understand how you deal with "dead time", such as out of work hours, waiting for response from user or waiting for third party supplier. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Thank you,
I was after the ITIL's best practice... forgotten....
The system we use at my work are quite premitive and doesn't do a lot.
Contains a lot of info in the database but don't extract out nearly as much as we can. So...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum