ACM Home Page
Please provide us with feedback. Feedback
Adventures in XSC: our six-week countdown to extended service coverage
Full text PdfPdf (235 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: 64 - 71  
Year of Publication: 2002
ISBN:1-58113-564-5
Authors
Jeffrey Lane  New York University, NY, NY
Annette Cutino  New York University, NY, NY
Marilyn McMillan  New York University, NY, NY
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): 0,   Downloads (12 Months): 7,   Citation Count: 0
Additional Information:

abstract   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.588661
What is a DOI?

ABSTRACT

In Summer 2001, Information Technology Services (ITS) - New York University's central IT organization serving some 65,000 students, faculty, and staff - was charged with taking major steps toward meeting our clients' growing requirements for round-the-clock IT services and support. From this, our Extended Services Coverage project (XSC) was begun.ITS had been formed two years earlier when three distinct IT organizations were combined under the leadership of the University's first Chief Information Technology Officer (CITO). XSC's Phase I allotted ITS a mere six weeks' time to gear up and extend integrated, formalized business-hours-type support to all our services during evenings, nights, and weekends. Helpdesk hours alone would be increased by more than 73%; onsite technical system support during "off-hours" would also be significantly increased - for University administrative systems, NYU-NET, e-mail, and instructional systems. We would need to be ramped up by the time students and faculty returned at the end of August.All this raised significant challenges for ITS' 200-member staff. XSC would require changing how we worked together. We would need to devise incident management workflows and operating procedures that cut across previously distinct service groups; formalize notification procedures and mechanisms for our staff, service partners, and clients; develop standard protocols for prioritizing, routing, escalating and resolving problem reports; quickly recruit new staff and train all staff in new procedures; and measure, track and improve our practices systematically.This paper will outline ITS' early experiences with XSC - challenges, implementation issues, and future plans - particularly from the perspectives of the managers of the two helpdesks from which XSC processes are initiated. We will also note how we leveraged on initiatives already underway with respect to our helpdesk procedures and Remedy incident management system, and how, as an unanticipated benefit of XSC, we were better prepared to support the NYU community in dealing with the September 11 WTC tragedy and its aftermath.


Collaborative Colleagues:
Jeffrey Lane: colleagues
Annette Cutino: colleagues
Marilyn McMillan: colleagues