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. 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: • Category 1: Errors that have a critical impact on the business operations of the End- user, in particular, some major features are unavailable, severely disturbed or fre- quently interrupted. The End-user cannot carry out his/her daily work, is at risk of losing data or is under the threat of a total system failure. There is no way to work around the problem. Excluded are: - All types of user queries in relation to the handling of the PTV Cloud Service. - All types of parameter settings. - All types of graphical settings and screen layouts. • Category 2: Errors that have a significant impact on the business operations of the End user. The Maintained Product continues to perform, but with important restrictions in performance or functionalities. Excluded are: - All types of user queries in relation to the handling of the PTV Cloud Service. - All types of parameter settings. - All types of graphical settings and screen layouts. • Category 3: Errors that have moderate impact on the business operations of the End user. Performances or functions are temporarily or partially restricted, affecting slightly the daily work. • Category 4: Errors without any impact for the customer and of lowest priority, such as functional questions or routine messages. PTV reserves the right to re-classify the Error if it appears that the original classification was not reflecting its real severity or if subsequent corrections have been partly imple- mented and have caused a change of severity.
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. A Buyer Representative reporting an error or defect will make an initial nonbinding classification of each error or defect in the Software or associated Documentation and will report such error or defect to Clinical Architecture based on the criteria set forth in the Classification Criteria table in Section 2(c). In the event there is a dispute between the Buyer Representative and Clinical Architecture regarding the classification of an error or defect, such dispute shall be promptly escalated to the party’s respective officers with responsibility over the operations (and who shall call upon others having knowledge or expertise, as applicable) who shall work together, in good faith, to resolve such dispute within one (1) Business Day.
Error Classification. Any instance of failure of the Program Product(s) to be operative.
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. RAID will respond to Customer’s Error notifications within the Response Times identified in Section 3.0 below. Reported errors will be classified into one of the following categories: Severity 1: The Product is down or not operational, meaning there is no access to Customer data. Impact on customer operations is critical and requires immediate resolution. Support personnel may require continuous availability of Customer contact until circumvention or resolution is provided. Severity 2: If Product is operational with partial access to Customer data is partial or intermittent. The resulting restrictions on product functionality have a major impact on Customer operations.
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:
