ACM Home Page
Please provide us with feedback. Feedback
Help desk support: to be or not to be eligible
Full text PdfPdf (255 KB)
Source User Services Conference archive
Proceedings of the 30th annual ACM SIGUCCS conference on User services table of contents
Providence, Rhode Island, USA
Pages: 89 - 94  
Year of Publication: 2002
ISBN:1-58113-564-5
Authors
Rachel Niedzwiecki  Princeton University, Princeton, NJ
Macauley Peterson  Princeton University, Princeton, NJ
Sponsors
SIGUCCS: ACM Special Interest Group on University and College Computing Services
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 53,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/588646.588665
What is a DOI?

ABSTRACT

As a help desk becomes an integral player in a University's ability to expand technology to the community, its capability to keep up with the constantly changing and growing support needs becomes an increasingly difficult challenge. A help desk is often called to support systems and resources before the sponsoring group provides formal training to the users. Often a help desk receives calls about a new system before help desk consultants are introduced to the system or resource by the sponsoring group. Certainly, Service Level Agreements (SLAs) were designed to deal with this issue. But how can SLAs best assist a help desk in managing the never-ending need to provide cutting edge technical support.SLAs were designed to allow internal customers to state their service level needs. And, in turn, suppliers would be able to focus their resources into providing services at the required level. However, a help desk can be considered both a supplier and a customer. Therefore, the question becomes how can we design a SLA so it defines both the minimum requirements necessary before a help desk will support a service or resource as well as provides an agreed level of service to be delivered to the customer.This paper is designed to review SLAs and discuss questions including: What are the important elements to include in a SLA? What requirements are necessary for a system or resource to become eligible for support? What characteristics make up a production application? Should training, communication of outages, and 2nd tier support be included in a SLA?


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Karten, N. Establishing Service Level Agreements
 
2
Koch, C. Put IT in Writing. CIO Magazine, (Nov. 15, 1998).
 
3
Trimble, P.S. Service-Level Agreements Defined. Federal Computer Week, (Jan. 22, 2001).

Collaborative Colleagues:
Rachel Niedzwiecki: colleagues
Macauley Peterson: colleagues