You are here: TWiki > Operations Web>QATicket (28 Oct 2015, RobQ?)

Operations Support: Quality Assurance Procedure

Version Author Notes
0.1 GOC Support Team Drat Status.

Introduction and Goal

The OSG Operations Support Desk provides the following QA techniques to assure customer tickets are being handled in a timely and efficient manner.


  • Two Reports will be generated each day. One in the morning and one in the evening. These reports identify any ticket with a NAD that is over due.

  • Each member of the Operations Support Team and Infrastructure Group will be responsible for review and updating any ticket assigned to them before the end of business each day.

  • Each day/week a member of the Support Team will be assigned the task of QA, defaulting to the support groups manager if no one else is available. This person, with the assistance of anyone else who is available, will at the end of each day ensure that proper action is taken on any ticket that is overdue. If no is needed the ticket will be bumped to the next date for further review.

  • Random ticket QA is done by all staff members on a monthly basis 5% of all tickets are reviewed internally for proper procedure.

Potential ideas for additional Quality Assurance

  • Randomly assign each GOC staffer a certain number of randomly selected tickets to qualitatively review
  • Randomly select survey participants, use a short survey with number ranking for easy tabulation
  • Compare historical data to current data (number of tickets completed, time to close, response time)

-- ChrisPipes - 27 Aug 2014

  • longitudinal ticket count:

  • closure time data:

  • closure time data (continued):

  • Screen_Shot_2014-10-16_at_11.09.34_AM.png:

  • Screen_Shot_2014-10-16_at_11.10.11_AM.png:

  • the load begins to slow our ticket time here:

  • we fine tune our procedures and knock it out of the park!:

  • tickets with vs without the software team for this year so far:

  • Screen_Shot_2014-10-16_at_2.04.17_PM.png:

Customer Survey

  • Spot Check - Smiley Face Survey?
    • Review and contact all "Frowny Face" reports.
  • In Depth Customer Satisfaction Survey - Takes time, effort, and expertise. At this point even if we could find the time and effort, expertise is lacking.

Detailed tickets purpose proposals

  • To better understand the breakdown of problem types we will propose sub-grouping ticketing into the following categories. These categories would allow extra analysis and trend tracking of technical areas within OSG.
    • Certificate
    • OSG Resource
    • OSG Software
    • OSG Infrastructure
    • Network
    • Security
Topic attachments
I Attachment Action Size Date Who Comment
pngpng Screen_Shot_2014-10-16_at_1.51.33_PM.png manage 29.8 K 16 Oct 2014 - 17:54 ElizabethChism tickets with vs without the software team for this year so far
pngpng Screen_Shot_2014-10-16_at_10.46.13_AM.png manage 38.6 K 16 Oct 2014 - 15:01 ElizabethChism longitudinal ticket count
pngpng Screen_Shot_2014-10-16_at_11.07.31_AM.png manage 71.4 K 16 Oct 2014 - 15:17 ElizabethChism closure time data
pngpng Screen_Shot_2014-10-16_at_11.09.04_AM.png manage 69.5 K 16 Oct 2014 - 15:20 ElizabethChism closure time data (continued)
pngpng Screen_Shot_2014-10-16_at_11.09.34_AM.png manage 34.6 K 16 Oct 2014 - 15:21 ElizabethChism  
pngpng Screen_Shot_2014-10-16_at_11.10.11_AM.png manage 34.5 K 16 Oct 2014 - 15:22 ElizabethChism  
pngpng Screen_Shot_2014-10-16_at_11.11.14_AM.png manage 36.1 K 16 Oct 2014 - 15:23 ElizabethChism the load begins to slow our ticket time here
pngpng Screen_Shot_2014-10-16_at_11.11.49_AM.png manage 35.0 K 16 Oct 2014 - 15:24 ElizabethChism we fine tune our procedures and knock it out of the park!
pngpng Screen_Shot_2014-10-16_at_2.04.17_PM.png manage 27.9 K 16 Oct 2014 - 18:05 ElizabethChism  
Topic revision: r7 - 28 Oct 2015 - 18:27:17 - RobQ?
Hello, TWikiGuest


TWiki | Report Bugs | Privacy Policy

This site is powered by the TWiki collaboration platformCopyright by the contributing authors. All material on this collaboration platform is the property of the contributing authors..