Error Classification. Upon observing a valid Error, the Customer shall describe it, collect evidence, classify its severity and report such description, evidence and classification through a Ticket. Errors shall be classified according to their severity as follows:
Error Classification. 4.1 The Errors are classified as follows: Error Severity Level Classification
Error Classification. State Street shall have the right to change the classification of severities as reported by the Client based on State Street’ assessment, in its sole discretion, of the situation from time to time.
Error Classification. Sun shall classify each Error reported in an Escalation Call according to the following criteria: IMPACT: Error IMPACT to customer's operation Red Alert: Significant or potentially significant financial/business impact to customer. Critical: System is down or effectively unusable as a result of the Error, or the Error causes critical impact on the customer's operation with no acceptable Workaround. Significant: System is up and running, but the Error causes significant impact and has no acceptable Workaround. Limited: System is up and running, and the Error causes only limited or insignificant impact. FUNCTIONALITY: Customer FUNCTIONALITY affected by Error Red Alert: Customer system is or is susceptible to being rendered down and/or unusable. Functionality affected by the Error may include Customer experiencing or being susceptible to experiencing data corruption, a security breach or exposure, inability to run a new application or a miss in key production dates. No acceptable Workarounds or Error Corrections are available. Primary: Functionality used to perform tasks considered to be essential to business operations, project completion or normal productivity of end-user. Secondary: Functionality used to perform tasks considered to be important, but not primary to immediate business operations. Nonessential: Functionality that is not important and infrequently used. SEVERITY: The Severity level of an Error (e.g., Severity 1) is determined by the criteria set forth below and in the Severity Matrix, and establishes the time period by which Supplier shall respond to an Escalation Call and perform an Error Correction, as elaborated in Section 5.4 ("Error Corrective Action"). Two components establish the Severity of an Error:
Error Classification. Any instance of failure of the Program Product(s) to be operative.
Error Classification. When Customer reports an Incident, Entrust will, in consultation with Customer, first classify the Incident according to its severity and nature into one of the categories below. The Incident will then be logged in Entrust’s tracking system.
Error Classification. Upon identification of an Error, Company shall notify Superna using a Technical Support Services Method set forth above (“Technical Support Services Method”). Superna shall only respond to notifications that are properly submitted through a Technical Support Services Method. Company must provide Superna with sufficient information to locate and reproduce the Error. Superna will use commercially reasonable efforts to acknowledge receipt of the Error report within two (2) hours for all case types and target response for unplanned failover of 30 minutes. Superna will make the final determination of the classification of such Error.
Error Classification. Each Escalation Report shall include Dot Hill's proposed classification of the Severity Level of the Error(s), and the reason for such proposed classification, in accordance with the classification criteria set forth in Section 4.2 ("Error Classification"). Infortrend shall accept Dot Hill's proposed classification, unless Infortrend provides a reasonable basis why an Error should be assigned a different classification. If the parties do not agree, which agreement shall not be unreasonably withheld, delayed or conditioned, on the classification for any Error within [...***...] of notification to Dot Hill of Infortrend's different Error classification, the dispute shall be escalated to the management of each party for resolution in good faith. [...***...] = CERTAIN CONFIDENTIAL INFORMATION CONTAINED IN THIS DOCUMENT, MARKED BY BRACKETS, HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO RULE 24b-2 OF THE SECURITIES EXCHANGE ACT OF 1934, AS AMENDED. Each Error shall be classified according to impact on the operation of the Dot Hill Customer's system ("Impact") and the loss of functionality of the Software ("Functionality").
Error Classification. In the following error classification scheme is used for possible errors of the EQS Cloud Services. Severity Type of error Description Level 1 Critical error The system does not work at all or important functions of the system are severely restricted and there is no work around.
Error Classification
