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. 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. 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. 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. 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. 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. 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.
