1A. Average Desktop Support Request Resolution Time
Current Value
0.5
Definition
Comparison
Context
Story Behind the Curve
Overview
FIC IT team consists of 4 staff including 2 contractors currently. IT office utilizes CIT infrastructure and dedicate desktop services to support FIC staff's IT needs & requirements. The core activities & serivces includes general desktop & conference room support, IT projects management and IT equipment acquisition & management, etc.
General process & procedure for IT service ticket
- FIC staff submit an IT Service Ticket
- FIC IT DST (Desktop Support Technician) contact ticket requestor to confirm/clarify IT needs and provide assistance and/or fix the issues
- FIC IT DST close the ticket after receiving confirmation from ticket requestor
Average ticket received: 41 per months. From May 2017 to May 2018, Avg is 3.6 days. Starting from June 2018, IT office imporved the process policy by monitoring the ticket queue more proactively and also modified the ticket system. DST closes the ticket right after it is fixed, and if there is no response from customer after try 3 times, DST will also close the ticket. Therefore, the resolution time is down from 3.6 days per ticket to 2.2 days per tickets. Although our target is still 2.5 days per tickets.
Current status
Our current average IT ticket closing time is three days, and we have been successful in closing most desktop incident requests within this timeframe. However, we have observed that requests for conference rooms or virtual meeting support need to remain open until the corresponding conference is concluded. This has resulted in an increase in the average resolution time.
March 2020: Staff relocation, workstation set up and maximize telework at NIH
Dec. 2019: Tickets were submitted earlier for GFE for foreign travel loaner request (3 month before travel start) and for new staff onboarding
Peak | Valley | ||
Aug. 17 |
- 8.2 days - High volumn: 51 tickets were received. - Complexity and rely on third party, such as several (2) VPN access, Website access issue, set up new iPhones (3) |
Sept. 17 |
- 3.5 days - Low volumn: 35 tickets were submitted - Less complexity and less volumn and less dependency. Requests such as mappting printer, distribution list, update digital certificate, install software... |
Oct. 17
|
- 5.6 days - High volumn: 53 tickets. - High dependency. e.g. several iPhone set up requests (3), VPN access, Loaner for travel (need keep ticket open till the travel end) - Beginning of the new FY |
Apr. 18
|
- 1.2 days - Less volumn: 37 tickets - Less complexity and most of tickets can be fixed in house, less dependency |
May 18
|
- 5.2 days - Received more loaner GFE request (3); Need keep tickets open until the travelers were back - Depend on 3rd party, such as VPN client issues - Volumn was above average |
||
June 18 |
- 3.6 days - 6 loaner GFE and have to keep ticket remain open until the travelers were back. - Dependency. Some ticket need CIT's assistance, such as grant some access to NIH staff on FIC intranet |
Positive Factors - Shorter resolution time
- Enthusiastic IT team. IT team is willing and has ethusiasm to work well, to provide better services/support and promote the use of information technology at FIC. Team member helps each other, always looks for ways to make new ideas work although the work style may be different.
- Collaborating with IC partners including but not limitted to CIT. FIC IT office has partner with NIH ICs to optimize the use of IT resources, especially, we utilize CIT as our back end support which give us more resources when helping FIC staff.
- Hiring to fill the vacant position. FIC IT office need recruit 1 staff to the team, which will reduce current IT team's workload and shorten the resolution time.
- FIC staff with increasing IT knowledge/skill and understanding. More and more FIC staff has taken IT related training to gain general/basic IT knowlege and understanding on the importance of IT regulation, process & operation. Theoretically, the resolution time may be shorten because of the shorter explanation time.
- Smaller group. FIC is a small IC and IT team is small team with 4 member. It is relatively easier for IT team establishing good relationship with staff/each other and knowing the person who we serve for and work with.
Negative Factors - Longer resolution time
- Big volumn of tickets. IT office receive more IT service tickets around the end of fiscal year than other time frame. Especially, almost every ticket requires immediate attention and help at once.
- Complex and difficut issues. Some complex IT service request such as login authentication exception, require IT developer/database adinistrator /network administrator to modify the code or setting, and also require extra approval from senior management and/or chief information security office.
- Unavailable customer. FIC staff may on travel, leave, ect. when submitting an IT ticket. The ticket will remain be open till he/she is availableto allow DST to provide services.
- Unclear/unknown requirement. Customer may select the wrong category when submitting a help desk ticket, which will take more time to find/assign the proper resource or people to help.
- Waiting time for third party resources & approval. IT service ticket resolution time can be impacted by many factors. Some factors may play critical role. E.g., IT DST depends on other resources to assist customer, which will have impact (sometimes big impact) on IT ticket process time. For example:
- The DST must coordinates with other NIH system help desk, such as eRA, nVision, CIT infrastructure team, hosting team, etc., DST has to wait until the involved third party to finish their process.
- Must wait/collaborate with NIH security committee/ISSO office for their approval.
- Coordinate with commercial partner, such as Apple, Dell, Ricoh, NetCom, Contractors or Vendors. The processing time depend on third party's response time.
- Lack of staff. FIC IT office is running under short of hand. IT team has to take additional responsibilities that outside his/her scope of work in order to meet FIC staff's IT needs. Therefore, IT tickets maybe not closed on a timely manner.
IT Service Tickets Details
Question |
# of Ticket Received |
Resolution Time (Days) |
Reason/Story behind the data |
For Jun 17 – Aug 17, why the resolution time were much longer?
|
Jun 17: 45 Jul 17: 29 Aug 17: 51 |
Jun 17: 4.2 Jul 17: 6.8 Aug 17: 8.2 |
There are many factors can cause the resolution time was longer. Summer time with people were out o the office on vacation would be a logical explanation. There could be other factors as well such as the complexity of the issue, how busy the technician was, ticket volume for that week etc. Another reason can cause the longer processing time in August was because it was approaching to end of FY, IT received more service tickets than other time frame. |
For Oct. 17: the resolution time went up again, why? |
53 |
5.6 |
There were 53 tickets which is above average. If the ticket volume was above average for the month could certainly be a factor. On the other hand, please notes, these resolution times are not true resolution time, this is the time the ticket was closed versus resolved. |
From Nov. 17 to Mar. 18: it shows the resolution time went down? |
Nov 17: 32 Dec 17: 36 Jan 18: 27 Feb 18: 40 Mar 18: 42 |
Nov 17: 1.6 Dec 17: 2 Jan 18: 1.6 Feb 18: 1.4 Mar 18: 2.3 |
Any reason of causing the curve went down (shorter resolution time)? The focus for responding to tickets has always been the same: quick response and our target is to resolve tickets within 24 hours when possible. Meanwhile, the ticket could have been resolved but not being closed. Reason for shorter resolution time: such as lower ticket volume, less complex issues, etc.
|
From May 18, the curve went up again, why is that?
|
46 |
5.2 |
Any reason of causing the curing went up (longer resolution time)? Factors such as the complexity of the issue, how busy Claude was, ticket volume went up for that week etc. In addition, manage GFE for Foreign Travel Policy was officially effective from April, 2018, which cause extra process and procedure for loaner equipment set up and requirements clarification. 3 loaners requests. Tickets has to be remain opened until the traveler was back from foreign travel. Depend on 3rd part resources, such as VPN client issues |
From June 18 to Oct. 18 |
Jun 18: 43 Jul 18: 46 Aug. 18: 41 Sept. 18: 29 Oct. 18: 27
|
Jun 18: 3.6 Jul 18: 1.7 Aug. 18: 2.7 Sept. 18: 1.6 Oct. 18: 1.8 |
Starting from June, update the ticket system and monitor proactively and close the ticket right after it is fixed. the Average resolution time is down from 3.6 days to 2.8 days
June 18: 6 loaner GFE and some ticket need CIT's assistance, such as grant some access to NIH staff on FIC intranet |
Partners
- Customer: FIC Staff
- NIH IC Partners including CIT
- CIT Desktop Support Team and Other Service Provider Team
- NIH Enterprise Systems Help Desk Team
- NIH IT Security Program Committee and Work Group
- Contractors and Vendors
What Works
- Coordinate with CIT desktop support team to make "CIT IT Services Survey" be required after each IT service is completed
- Generate and review IT service monthly report and ad hoc report to oversee the IT service status
- Monitor the IT service ticket queue and ensure the ticket is closed when the service is completed
- Update the ticket management protocol
- Training and Encourage DST to collaborate with CIT co-workers to ensure knowledge/skill up to date
- Clarify/reiterate DSTs' roles & responsibilities and primary/secodary task owner. Ensure IT office's coverage
Action Plan
- Update ticket management protocol. IT DST will close the ticket if there is no response from customer for 3 days. Customer can re-open the ticket by submitting another ticket.
- Continue work with CIT partner to enhance current IT service ticket system and reporting feature.
- Plan to create customized "IT Service Survey" internally, which can help IT office understand customers' need and requirements better, also, can help in monitoring/managing/improving DST and other IT supports.