Common use of Requesting Service Clause in Contracts

Requesting Service. The following are the supported methods of contacting ITS for service: Standard Service Critical/Urgent Service Purchasing Email: xxxx_xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 Email: xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 (On Call) Email: xxxx_xxxx@xxxxxxxx.xxx Phone: 000-000-0000 For non-emergency support, the conventional service request protocol is for an ITS representative to serve as the first point of contact for all computing-related issues. When a request for support is received (in person, by phone, or by email), a representative of IT Technology Support Services (TSS) will create a new service request, and the new service request and the corresponding service issue will be managed according to the tiered triage protocols described below. If an ITS Technology Support Service representative is not immediately available to log and triage the issue, the support requestor may contact an alternative representative of ITS, in which case the attending representative will open a new service request as the first step toward triage and resolution. Tiered service requests can only be escalated if changes in circumstances justify escalation. Escalations will be considered upon request. However, automatic escalation ensues by default according to schedules outlined by tier. Automated escalations can be reset by mutual agreement between ITS and HR or if higher priority University requirements coincide.

Requesting Service. The following are the supported methods of contacting ITS for service: Standard Service Critical/Urgent Service Purchasing Email: xxxx_xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 Email: xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 (On Call) Email: xxxx_xxxx@xxxxxxxx.xxx Phone: 000-000-0000 For non-emergency support, the conventional service request protocol is for an ITS representative to serve as the first point of contact for all computing-related issues. When a request for support is received (in person, by phone, or by email), a representative of IT Technology Support Services (TSS) will create a new service request, and the new service request and the corresponding service issue will be managed according to the tiered triage protocols described below. If an ITS Technology Support Service representative is not immediately available to log and triage the issue, the support requestor may contact an alternative representative of ITSITS (or the Center for Spatial Studies, for issues relating to the ESRI software suite), in which case the attending representative will open a new service request as the first step toward triage and resolution. Tiered service requests can regularly only be escalated if changes in circumstances justify escalation. Escalations will be considered upon request. However, automatic escalation ensues by default according to schedules outlined by tier. Automated escalations can be reset by mutual agreement between ITS and HR ISEA or if higher priority University requirements coincide.

Requesting Service. The following are the supported methods of contacting ITS for service: Standard Service Critical/Urgent Service Purchasing Email: xxxx_xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 Email: xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 (On Call) Email: xxxx_xxxx@xxxxxxxx.xxx Phone: 000-000-0000 For non-emergency support, the conventional service request protocol is for an ITS a Technology Support Services (TSS) representative to serve as the first point of contact for all computing-related issues. When a request for support is received (in person, by phone, or by email), a representative of IT Technology Support Services (TSS) will create a new service request, and the new service request and the corresponding service issue will be managed according to the tiered triage protocols described below. If an ITS Technology Support Service representative is not immediately available to log and triage the issue, the support requestor may contact an alternative representative of ITS, in which case the attending representative will open a new service request as the first step toward triage and resolution. Tiered service requests can only be escalated if changes in circumstances justify escalation. Escalations will be considered upon request. However, automatic escalation ensues by default according to schedules outlined by tier. Automated escalations can be reset by mutual agreement between ITS and HR MSGIS/CSS Management or if higher priority University requirements coincide.

Requesting Service. The following are the supported methods of contacting ITS for service: Standard Service Critical/Urgent Service Purchasing Email: xxxx_xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 Email: xxxxxxx@xxxxxxxx.xxx Phone: 000-000-0000 (On Call) Email: xxxx_xxxx@xxxxxxxx.xxx Phone: 000-000-0000 For non-emergency support, the conventional service request protocol is for an ITS representative to serve as the first point of contact for all computing-related issues. When a request for support is received (in person, by phone, or by email), a representative of IT Technology Support Services (TSS) will create a new service request, and the new service request and the corresponding service issue will be managed according to the tiered triage protocols described below. If an ITS Technology Support Service representative is not immediately available to log and triage the issue, the support requestor may contact an alternative representative of ITS, in which case the attending representative will open a new service request as the first step toward triage and resolution. Tiered service requests can only be escalated if changes in circumstances justify escalation. Escalations will be considered upon request. However, automatic escalation ensues by default according to schedules outlined by tier. Automated escalations can be reset by mutual agreement between ITS and HR Facilities Management or if higher priority University requirements coincide.