UCSF University of California, San Francisco      About UCSF       Search UCSF       UCSF Medical Center     
  Education & Training    Research    Patient Care   
 
Print This Page For Normal View, Click Here For Larger Font Sizes', Click Here

 
 
Information Services Unit
Help and Support
Our Services
Recharge
Client Portfolio
About Us
Contact Us / Request Services
Policies and Procedures
Security

 

Service Level Agreement

Contacting a Technician

Call the ISU Helpdesk at 502-1919 or contact us via email.

  • In most cases, a technician will be available to answer your call during Business Hours.
  • If a technician does not answer your call, please leave a voicemail message with a description of the problem and your contact information.
  • If your call is urgent during Business Hours OR on Saturday and Sunday 7 AM - 6 PM, please key 1-1-2 at the end of your message to mark the call as urgent and automatically page an ISU technician.

    Note:
    High Priority Response and Resolution Times will be honored only if 1-1-2 is keyed at the end of your message.
  • If your call is urgent during other Off-Hours, the Helpdesk voicemail message will provide you with a pager number for the on call support technician. Call that pager directly to contact a technician.

    Note: This service is only intended for Priority 1 outages. Fixes for lower priority outages will be addressed the next business day.
  • Contact us via e-mail for reporting non-critical outages and requests. Email messages will be reviewed periodically during Business Hours.

back to top

Response and Resolution Times

Priority of the incident – assigned by the Service Desk when the Remedy Ticket is opened and is determined primarily on the basis of urgency and impact. All Incidents have a 30 minute initial response time.

Priority
Impact/Tier
Response Time & Initiate Fix
High/1
Medium/2
Low/3
 
Urgent
P1 P1 P2
<1hr <1hr <8-24hrs
High
P1 P2 P3
<1hr <8-24hrs <16-48hrs
Medium
P2 P3 P4
<8-24hrs <16-48hrs <1wk-TBD
Normal
P3 P4 P4
<16-48hrs <1wk-TBD <1wk-TBD

P1 = Priority 1 Incident – Kick off SOM ISU Incident Management Communication Plan

P2 = Priority 2 Incident – Kick off SOM ISU Incident Management Communication Plan*

P3 = Priority 3 Incident*

P4 = Priority 4 Incident*

** Note: Hours stated in terms of business hours, e.g., 48 hours equal 6 business days.

*Note: This service is only intended for Priority 1 outages. Fixes for lower priority outages will be addressed the next business day.

See a full list of application and server priorities.

back to top

Support Hours

Business Hours: Monday through Friday 7 am – 6 pm.
Off Hours: Monday through Friday 6 pm – 7 am,
Weekends and Holidays

*Support Outside Business Hours:
During after hours support all incidents have a 1 hour initial response time.  Priority 1 incidents have a 3 hour window to initiate a fix while all other priority levels will be addressed the next business day.

back to top

Special Considerations

Customers may contact the ISU Helpdesk with one-week lead-time to make special arrangements for more responsive after hours support for a specific period of time for unique projects or activities. For example, it may be imperative that a certain application has high availability over a specific weekend. In this situation, additional on call technicians may be assigned over the weekend and put on high alert to respond to problems in a more timely fashion.

back to top

Problem Severity

  • Impact of the incident – extent of the deviation from the normal service level, in terms of the number of users or business processes affected.  Major incidents are those for which the degree of impact on the user community is extreme.  Incidents for which the timescale of disruption (to even a relatively small percentage of users) becomes excessive may also be regarded as major.  System Tiers are defined and correlate to Impact Rankings.

    Rank
    Impact Criteria

    Tier 1 /
    High Impact

    • Entire department, floor, branch, line of business, or external customer affected.
    • Greater than 100 people affected

    Tier 2/
    Medium Impact

    • Between 21-99 people affected

    Tier 3/
    Low Impact

    • Less than 20 people affected

    Urgency of the incident – the acceptable delay, to the user or business process, in solving the incident.

    Rank
    Urgency Criteria

    Urgent

    • Impacts Enterprise
    • Impacts multiple business units

    High

    • Process Stopped; customer can not work
    • System and/or service unavailable
    • no work around available

    Medium

    • Process affected; certain functions are unavailable to customers
    • system and/or service is degraded
    • May or may not have workaround available

    Normal

    • Process affected; certain functions are unavailable to customers
    • System and/or service inconvenienced but still available
    • Workaround available.

back to top

Incident Communication Plan

  1. Incident Management is Kicked Off
    1. An Incident is suspected by SOM ISU Staff and is immediately reported to SOM Management or Sr. Architects
    2. An Incident is Identified by SOM ISU Staff and they contact the SOM Service Desk, starting the SOM ISU Incident Management Process.
    3. SOM Service Desk identifies and documents the Incident Owner in the Incident Management System (currently Remedy).
      • The Incident Owner owns the Incident and is responsible for working with and informing the SOM Service Desk in intervals appropriate to the priority level of the incident.  During a Priority 1 or 2 incident the Incident Owner has the power to draft in to his/her service any resource they deem necessary to more efficiently handle the Incident.
      • The Service Desk Incident Manager owns the SOM ISU Incident Management Process and is responsible for coordinating communications with the Incident Owner.
  2. Initial Incident Communications
    1. ISU Internal Communications Service (Service Desk Incident Manager):
      After a half hour or a Resolution to the Incident (whichever comes first) the Service Desk Incident Manager is tasked with minimally communicating to SOM ISU Sr. Management the following:
      • Via Phone:
        • Call all SOM ISU Sr. Management
      • Via Email:
        • A brief summary of the incident
        • The Ticket Number in of the Incident in the Incident Management System
        • The identified and documented Incident Manager
        • Priority level of the incident
        • Estimated time to Resolution
        • Estimated impact
        • Estimated time of next update or communication
      • Via Text Message:
        • 911 — Priority 1 — Call 502-1919 (or phone ext. of the documented Incident Manager
    2. Client Communications (Incident Owner)
      • Via Phone:
        • Escalate to the client(s) the Incident with a phone call within 5-15 minutes of reported Incident
      • Via Email:
        • Email the incident and summary of any dialogue of the escalation phone call to the client(s)
      • The Incident Owner continues to contact the Business Owner until there is an acknowledgement their communications are received. A Business Owner is responsible for acknowledging this initial communication.
  3. Continued Communications:
    1. Incident updates are coordinated by the SOM Service Desk with the Incident Manager at intervals determined by the priority level of the incident to appropriate audience including SOM ISU Sr. Management.
    2. Communication Intervals for Internal ISU communications (Incident Manager):
      • Determined by the demands of the incident, to be documented and adhered to by the SOM Servioce Desk Incident Manager
      • Coordinate Status Meeting every 1hr with all involved staff.
    3. Communication Intervals By Priority Level for Client Communications (Incident Owner):
      • Priority 1 - 1hr
      • Priority 2 - 3hrs
    4. Business Responsibilites:
      • The Business Owner is to continue to acknowledge communications and work on internal procedural work arounds (i.e. paper processes)
  4. Incident Resolved
    1. The Incident cannot be Resolved until the Business Owner acknowledges that theIncident is Resolved.
    2. Incident Resolution is to be communicated to all appropiate units and customers.
    3. The Incident Resolution is to be documented in the Incident Management System, SOM KB, and any other applicable system. All systems where the Incident Resolution is documented are to be documentedin the Incident Management System, as well
  5. Post Mortem & Documentation
    1. Post Mortem Review is to be scheduled and documented in the Incident Management System and assigned to the Incident Manager.
    2. Post Mortem Review is to be held and all meeting notes, findings, and required actions are to be documented in the Incident and Problem Management Systems. (Remedy, On Time, Etc.)
    3. Close Incident:
      • The Incident can be closed once all required actions from the Post Mortem Review of the Incident are Implemented and Documented.
Updated: December 4, 2008
    Site Map    Contact Info     ©UC Regents