Severity Levels / Response Times and Resolution Times Sample Clauses

Severity Levels / Response Times and Resolution Times. Motorola/Locution will comply with the response times, resolution time and resolution procedures set forth in this section for each of the priority levels of problems described herein. Customer shall assign an initial priority level for each problem reported, either orally or in writing, based on the conditions described below. Motorola/Locution will work with Customer to upgrade or reduce the level of a particular problem to a different priority level, if after examining the problem there is reason to do so. Notwithstanding the foregoing, Motorola/Locution may not upgrade or reduce the level of priority of a particular error to a different priority without Customer’s consent, which consent may not be unreasonably withheld. Priority One Critical Priority One applies if the problem could:  Prevent the accomplishment of an operational or mission essential function, OR  Cause loss of data or data corruption, OR  Causes the interruption of normal operation of other systems, hardware or software preventing the accomplishment of an operational or mission essential function. Response Time  Immediately after notification, if the problem is reported during Regular Hours  Within one hour of notification, if the problem is reported after Regular Hours.  If on-site repair is required, Locution will coordinate the repair with the customer or a local installer within the next business day. Resolution Time  Within 12 hours after the problem is first reported by Customer, if no on-site repair is required.  Within 72 hours, typically, if on-site repair is required. Priority Two Priority Two applies if the problem could:  Adversely affect (but not prevent) the accomplishment of an operational or mission essential function, and no workaround is available, OR  Increase technical risk or increase costs associated with the life cycle and support of the system, and no workaround is available.  Priority Two problems include aborts, but not loss of data or data corruption. Response Time  Within four hours of notification, if the problem is reported during Regular Hours.  Within four hours of the start of the next business day after notification, if the problem is reported after Regular Hours.  If on-site repair is required, Locution will coordinate the repair with the customer or a local installer within the next two business days. Resolution Time  Within three business days after the problem is first reported by Customer, if no on-site repair is required.  Within ...
Sample 1
AutoNDA by SimpleDocs

Related to Severity Levels / Response Times and Resolution Times

  • Response Times Qubit bases its response times and the actions it takes to resolve problems on an assessment of the impact of the reported technical issue. The more serious the impact, the higher the assigned priority. For all support issues relating to Customer, Qubit will respond in accordance with Table 1: P1 1 hour 4 hours P2 1 hour 8 hours P3 4 hours 72 hours P4 1 business day Next or a later major release **The Priority Levels are defined in Section II(2) below.

  • UDP DNS resolution RTT Refers to the RTT of the sequence of two packets, the UDP DNS query and the corresponding UDP DNS response. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • DNS resolution RTT Refers to either “UDP DNS resolution RTT” or “TCP DNS resolution RTT”.

  • Problem Resolution The parties shall meet and attempt to resolve all disputes and differences that may arise between the parties hereto concerning construction, interpretation, performance, operations, or breach of the matters referred to in this Agreement prior to seeking any legal remedy.

  • TCP DNS resolution RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the DNS response for only one DNS query. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

  • Shift Schedule The words "shift schedule" when used in this Agreement shall mean a timetable of the shifts and off days assigned to a position or group of positions which commences at the beginning of a pay period and includes one complete rotation of said shifts.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Recognition of the U.S. Special Resolution Regimes (i) In the event that any Underwriter that is a Covered Entity becomes subject to a proceeding under a U.S. Special Resolution Regime, the transfer from such Underwriter of this Agreement, and any interest and obligation in or under this Agreement, will be effective to the same extent as the transfer would be effective under the U.S. Special Resolution Regime if this Agreement, and any such interest and obligation, were governed by the laws of the United States or a state of the United States. (ii) In the event that any Underwriter that is a Covered Entity or a BHC Act Affiliate of such Underwriter becomes subject to a proceeding under a U.S. Special Resolution Regime, Default Rights under this Agreement that may be exercised against such Underwriter are permitted to be exercised to no greater extent than such Default Rights could be exercised under the U.S. Special Resolution Regime if this Agreement were governed by the laws of the United States or a state of the United States. As used in this Section 16(e):

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!