Severity Definitions Sample Clauses

Severity Definitions. Severity Level Description 1 A Severity 1 problem exists if any FAST Licensed Software or major function thereof is (i) inoperative, or (ii) is experiencing terminable/intermittent problems that is having a significant impact on the Customer’s ability to use FAST Licensed Software. 2 A Severity 2 problem exists if functionality of the FAST Licensed Software is found to be defective or absent, or contains a problem that renders FAST Licensed Software difficult, but not impossible to use. 3 A Severity 3 problem exists if the customer experiences a non-critical degradation of performance, or experience minor problems that need correction in either FAST Licensed Software or the relevant FAST product manuals.

Severity Definitions. Severity Description Severity Description

Severity Definitions. Severity Definition Examples

Severity Definitions. Severity Level Impact Description

Severity Definitions. Severity Level Definition

Severity Definitions. Severity Level Description 1 A Severity 1 problem exists if the DT Product causes problems with the Customer’s platform or a major function of the Product is (i) inoperative, or (ii) is experiencing terminable/intermittent problems that is having a significant impact on the Customer's ability to use the DT Product consistent with the instruction manual or written documentation. 2 A Severity 2 problem exists if functionality of the DTSA product is found to be defective or absent, or contains a problem that renders the DTSA product difficult, but not impossible to use consistent with the instruction manual and other written documentation. 3 A Severity 3 problem exists if the Customer experiences a non-critical degradation of performance, or problems that need correction in either the DTSA product or the relevant DTSA product manuals.

Severity Definitions. Service requests for Oracle Cloud Services may be submitted by Your designated technical contacts via the Cloud Customer Support Portal noted above. The severity level of a service request submittedby You is selected by both You and Oracle, and must be based on the following severity definitions:

Severity Definitions. ‌ Service requests for supported Oracle programs may be submitted by you online through Oracle’s web- based customer support systems or by telephone. The service request severity level is selected by you and Oracle and should be based on the severity definitions specified below. Your production use of the supported programs is stopped or so severely impacted that you cannot reasonably continue work. You experience a complete loss of service. The operation is mission critical to the business and the situation is an emergency. A Severity 1 service request has one or more of the following characteristics:  Data corrupted  A critical documented function is not available  System hangs indefinitely, causing unacceptable or indefinite delays for resources or response  System crashes, and crashes repeatedly after restart attempts Reasonable efforts will be made to respond to Severity 1 service requests within one hour. For response efforts associated with Oracle Communications Network Software Premier Support and Oracle Communications Network Software Support & Sustaining Support, please see the Oracle Communications Network Premier & Sustaining Support and Oracle Communications Network Software Support & Sustaining Support sections above. Except as otherwise specified, Oracle provides 24 hour support for Severity 1 service requests for supported programs (OSS will work 24x7 until the issue is resolved) when you remain actively engaged with OSS working toward resolution of your Severity 1 service request. You must provide OSS with a contact during this 24x7 period, either on site or by phone, to assist with data gathering, testing, and applying fixes. You are requested to propose this severity classification with great care, so that valid Severity 1 situations obtain the necessary resource allocation from Oracle.

Severity Definitions. Seller’s TSC personnel will assign appropriate priority to each support request by using one of four defined severity levels, Severity levels denote the status of each support request. Table 1 shows each level and explains the criterion used to assign the proper severity level.