Error Severity Levels Clause Samples

Error Severity Levels. 3.8.1 IAR uses the following four (4) severity levels to categorize reported Errors: a) Critical level: The Product(s) functionality is inoperable causing critical impact to business operations if functionality is not restored quickly. If the Error is occurring during the development phase of the Licensee’s product, the Error hinders all of the Licensee’s development, integration, or testing in such a critical way that development progress is halted. No viable workaround is known.

Error Severity Levels. Motive shall exercise commercially reasonable efforts to correct any Error reported by Mercury Interactive in the current unmodified release of Licensor Software in accordance with the Severity level reasonably assigned to such Error by Motive. · Severity 1 Errors – Motive shall promptly commence the following procedures: (i) assign Motive qualified Second Level Support engineers to investigate the Error; (ii) promptly notify Mercury Interactive support contact that steps being taken to correct such Error(s) as soon as possible in accordance with the provisions herein; (iii) provide Mercury Interactive with periodic reports on the status of the investigation and upon request; and (iv) initiate work to provide Mercury Interactive with a Workaround or Fix as soon as possible. Response Time for all Severity Level 1 Errors is 30 minutes and resolution through a Fix or Workaround as soon as possible but no later than 1 business day. · Severity 2 Errors – Motive shall promptly commence the following procedures: (i) assign Motive qualified Second Level Support engineers to investigate the Error; (ii) promptly notify Mercury Interactive support contact that steps being taken to correct such Error(s) as soon as possible in accordance with the provisions herein; (iii) provide Mercury Interactive with periodic reports on the status of the investigation and upon request; and (iv) initiate work to provide Mercury Interactive with a Workaround or Fix as soon as possible. Response Time for all Severity Level 2 Errors is 4 hour and resolution through a Fix or Workaround within 5 business days with reasonable efforts to do so within 4 business days. · Severity 3 Errors – Motive may include the Fix for the Error in a future release of the Licensor Software. Motive shall promptly commence the following procedures: (i) assign Motive qualified Second Level Support engineers to investigate the Error; (ii) promptly notify Mercury Interactive support contact that steps being taken to correct such Error(s) as soon as possible in accordance with the provisions herein; (iii) provide Mercury Interactive with periodic reports on the status of the investigation and upon request; and (iv) initiate work to provide Mercury Interactive with a Workaround or Fix as soon as possible. Response Time for all Severity Level 3 Errors is 1 business day and resolution through a Workaround within 10 business days and a Fix within 21 business days. · Mercury Interactive is responsible for providing su...

Error Severity Levels. TransactTools shall exercise reasonable efforts to correct any Error (as defined below) reported in the current unmodified release of Licensed Software in accordance with the Severity level reasonably assigned to such Error by TransactTools. Severity levels are defined below in the Definitions section of this Exhibit A. Severity 1 Errors—TransactTools shall promptly commence the following procedures upon notification of the problem during Regular Hours and upon confirmation by TransactTools that the Error is a Severity 1 Error:

Error Severity Levels. Service Provider shall assign all replicable --------------------- Errors a severity level as follows: (a) [*] (b) [*] (c) [*] Depending on the severity level of an Error, Service Provider shall use commercially reasonable efforts to correct such Error within its standard, U.S. and worldwide time periods. As part of Service Provider's amendments from time to time of its Error Correction policy, Service Provider shall have the right to revise program code, program specifications, design, Documentation, messages, error messages, and operating procedures applicable to all I'! Affiliates.

Error Severity Levels. When reporting Errors to Supplier, Credit Suisse shall classify each Error as follows:‌ (i) A Severity 1 Error is (i) any Error that prevents or seriously disrupts the use of a Product or any major function for its intended purpose, and (ii) any Severity 2 Error that has not been resolved by a temporary workaround or permanent solution within the applicable Resolution Time specified below. (ii) A Severity 2 Error is (i) any Error that seriously impairs, but does not prevent or seriously disrupt, the use of a Product or any major function for its intended purpose, and (ii) any Severity 3 Error that has not been resolved by a temporary workaround or permanent solution within the applicable Resolution Time specified below. (iii) A Severity 3 Error is any Error that causes only a minor impairment in the use of a Product, in whole or in part, for its intended purpose. (iv) A Severity 4 Error is any Error that has no or only a trivial impact on the use of a Product, in whole or in part, for its intended purpose, such as cosmetic or minor spelling errors.

Error Severity Levels. Severity 1 (Critical): The production environment for the Licensed Software is unavailable, causing critical impact to system operation if service is not restored quickly. No workaround is available. Severity 2 (Severe): The production environment is severely degraded, impacting significant aspects of system operations. No workaround is available. Severity 3 (Standard): The production environment is degraded. Functionality is noticeably impaired, but most system operations continue. Severity 4 (Low): Licensee requires information or assistance on the capabilities, installation, or configuration of the Licensed Software.

Error Severity Levels. Any Errors will be handled depending on the level of severity as defined below: (a) High – major functionality is impacted or significant performance degradation is experienced. The Error is persistent and affects many users and/or major functionality. The DreamApply cannot perform its main intended purpose. No reasonable workaround is available. (b) Medium – the Error is affecting some but not all users. The DreamApply can still perform its main intended purpose, but requires additional effort on part of the users. A short-term workaround is available, but not scalable.

Error Severity Levels. All errors reported to MPDV by Customer shall be assigned a severity level by MPDV, as follows:

Error Severity Levels. Service Provider shall assign all replicable --------------------- Errors a severity level as follows: (a) [*********************************************************** ************************************************************ ************************************************************ ******************************** ******************************************] (b) [*********************************************************** *************************************************************************** ***************************************************************************** **] (c) [*********************************************************** ****************************************] Depending on the severity level of an Error, Service Provider shall use commercially reasonable efforts to correct such Error within its standard, U.S. and worldwide time periods. As part of Service Provider's amendments from time to time of the AOL Error Correction Policy, Service Provider shall have the right to revise program code, program specifications, design, Documentation, messages, error messages, and operating procedures applicable to all JV Affiliates.