Severity 3 Errors definition

Severity 3 Errors. A Severity Three Error means there (i) are errors in fully operational production systems, (ii) is a need to clarify procedures or information in Documentation, or (iii) is a request for a product enhancement. PICS may include an Update in the next Maintenance Release.
Sample 1
Severity 3 Errors. A "Severity Three Production Error" means there: (i) are errors in fully operational production systems; (ii) is a need to clarify procedures or information in documentation; or (iii) is a request for a product enhancement. A Severity Three Development Error means: (1) there are errors in system development that may impact performance deliverables; (2) a need to clarify procedures or information in documentation; or (3) a request for product enhancement. Tarsin may include an Update in the next Maintenance Release.
Sample 1
Severity 3 Errors. Definition: A minor problem that does not have major effect on business operations or a major problem for which a Gen acceptable Workaround exists. Response Commitment: A Support engineer will respond to a Gen call within two (2) business days of a problem report. Provider will promptly assign Provider Support engineers to investigate the problem report. Provider shall initiate work to provide Gen with a workaround or fix. If a workaround or fix is not available, Provider may include a fix for the error in a future Releases. 4.
Sample 1

Examples of Severity 3 Errors in a sentence

  • Qlik will use commercially reasonable efforts to respond (a) within the Initial Response Times set forth in the table below, to Severity 1 Errors reported by a Technical Contact to Qlik via telephone or (b) within the Initial Response Times set forth in the table below for Severity 2 and Severity 3 Errors that are reported by a Technical Contact to Qlik via telephone or the Support Portal.

  • Qlik will respond (a) within the Initial Response Times set forth in the table below to Severity 1 Errors reported by MHBE to Qlik via telephone or (b) within the Initial Response Times set forth in the table below for Severity 2 and Severity 3 Errors that are reported by MHBE to Qlik via telephone or the Support Portal.

  • Qlik will communicate with Licensee at least once each business day (with respect to any Severity 1 Errors) or otherwise as reasonably necessary based on the nature and type of Error (with respect to Severity 2 Errors and Severity 3 Errors) until the applicable Error is resolved (in accordance with Section 4.1 below) or work-around is provided.

  • Licensees who have purchased “Enterprise Support Coverage” receive, in addition to the elements of Basic Support Coverage described above, unlimited telephone support for Error determination, verification and resolution (or instruction as to work-around, as applicable) twenty-four (24) hours a day, seven (7) days a week, 365 days a year for Severity 1 Errors and 365 days a year during the applicable Enterprise Business Hours for Severity 2 and Severity 3 Errors.

  • For Severity 3 Errors, Rocket Software will provide a complete resolution to such Severity 3 Error within 30 business days of reporting.

  • Partners with Enterprise Support receive support for Error determination, verification and resolution (or instruction as to work-around, as applicable) twenty-four (24) hours a day, seven (7) days a week, 365 days a year for Severity 1 Errors and during Qlik’s Standard Business Hours for Severity 2 and Severity 3 Errors..

  • Qlik will use commercially reasonable efforts to respond (a) within the initial response time targets set forth in the tables below with respect to the applicable Qlik Products for Severity 1 Errors reported by a Technical Contact to Qlik via telephone or (b) within the Initial Response Times set forth in the table below for Severity 2 and Severity 3 Errors that are reported by a Technical Contact to Qlik via telephone or the Support Portal.

  • The occurrence of any of the following within a given 30 -day period will be deemed a “Chronic Failure”: (i) two or more Severity 1 Errors; (ii) five or more Severity 2 Errors; or (iii) 10 or more Severity 3 Errors.

  • In the event of 3 (three) or more Errors higher than the Severity 3 Errors level during any calendar month, Credit Suisse may terminate the Agreement for material breach pursuant to the provisions in section 13.3 (Termination for Cause) of the GTC, it being understood that such breach cannot be remedied in accordance with the latter section.

  • Customers with Enterprise Support receive support for Support Case Error determination, verification and resolution (or instruction as to work-around, as applicable) twenty-four (24) hours a day, seven (7) days a week, 365 days a year for Severity 1 Errors and during Qlik’s Standard Business Hours for Severity 2 and Severity 3 Errors.


More Definitions of Severity 3 Errors

Severity 3 Errors means (i) there is a need to clarify procedures or information in documentation or (ii) there is a request for a product enhancement. DNN may include an Update in the next Maintenance Release.
Sample 1
Severity 3 Errors. A Severity Three Error means there (i) are errors in fully operational production systems, (ii) is a need to clarify procedures or information in Documentation, or (iii) is a request for a product enhancement. PICS may include an Update in the next Maintenance Release. Maintenance Releases. During the Quote Term, PICS shall make Maintenance Releases available to Customer if, and when PICS makes any such Maintenance Releases generally available to its customers. If a question arises as to whether a product offering is an Upgrade or a new product or feature, PICS’ opinion will prevail, provided that PICS treats the product offering as a new product or feature for its end user customers generally. Conditions for Providing Support. PICS’ obligation to provide Support is conditioned upon the following: (a) Customer makes reasonable efforts to correct the Error after consulting with PICS; (b) Customer provides PICS with sufficient information and resources to correct the Error; and (c) Customer procures, installs and maintains all equipment, telephone lines, communication interfaces and other hardware necessary to access the Subscription Services. Support Process: PICS will provide Support during the Quote Term 24x7, 365 days a year through the PICS software support help desk. Exclusions from PICS’ Support Services. PICS is not obligated to provide Support in the following situations: (a) the Software has been changed, modified or damaged (except if under the direct supervision of PICS); (b) the Error is caused by Customer’s negligence, hardware malfunction or other causes beyond the reasonable control of PICS; (c) the Error is caused by third party software not licensed through PICS; or (d) Customer has not paid the Subscription Services fees when due. Further, PICS shall not be obligated to provide Maintenance Releases or Support for any third party products that are, or may be integrated into the Software. EXHIBIT B SERVICE LEVEL COMMITMENTS Unless as otherwise defined below, all capitalized terms shall have the meaning set forth in the Agreement.
Sample 1

Related to Severity 3 Errors

  • Severity 1 means the unavailability of multiple service resources and redundant capability is not available or has been exhausted.

  • Severity 2 means the unavailability of an individual resource and redundant capability is not available or exhausted.

  • Severity means the dollar amount of losses on claims.

  • Severity Level means the actual impact of a Defect on a user’s operational environment as further described in the table below.

  • Latency means the additional time, beyond that of the basic perceivable response time of the aircraft due to the response time of the FSTD.

  • NAV Error means an error in the computation of the net asset value for a Fund or class as more fully described in the NAV Error Policy.

  • Workaround means a temporary modification to or change in operating procedures for the Work that: (i) circumvents or effectively mitigates the adverse effects of a Defect so that the Work complies with and performs in accordance with the applicable Specifications and Documentation; (ii) does not require substantial reconfiguration of the Work or any reloading of data; and (iii) does not otherwise impose any requirements that would impede an end user’s efficient use of the Work.

  • Medication error means any preventable event that may cause or lead to inappropriate medication use or patient harm, while the medication is in the control of the health care professional, patient, or consumer. Such events may be related to professional practice, health care products, procedures, and systems including, but not limited to: prescribing; order communication; product labeling, packaging and nomenclature; compounding; dispensing; distribution; administration; education; monitoring; and use.

  • Bug means a repeatable phenomenon of unintended events or actions during the running of a Software Device under normal conditions that results in:

  • Encounter Data Any Contractor accessing payments for services through the Global Commitment to Health Waiver and Vermont Medicaid programs must provide encounter data to the Agency of Human Services and/or its departments and ensure that it can be linked to enrollee eligibility files maintained by the State.

  • Degradation means a decrease in the useful life of the right-of-way caused by excavation in or disturbance of the right-of-way, resulting in the need to reconstruct such right-of-way earlier than would be required if the excavation or disturbance did not occur.

  • Service Level Failure means a failure to perform the Software Support Services fully in compliance with the Support Service Level Requirements.

  • Critical Illness means an illness, sickness or disease or corrective measure as specified in Section 6 of this policy document.

  • Unplanned Outage refers to the unavailable status of the units of the Power Plant other than Planned Outage. Based on the urgency of the needs of outage, the Unplanned Outage can be classified into five categories: (1) immediate outage; (2) the outage which could be delayed for a short while but the units must exit within six hours; (3) the outage which could be postponed over six hours but the units must exit within seventy-two hours; (4) the outage which could be deferred over seventy-two hours but the units must exit before the next Planned Outage; and (5) the prolonged outage which is beyond the period of the Planned Outage.

  • Software Error means a reproducible defect or combination thereof in the Software that results in a failure of the Software when used in accordance with the Documentation. Software Errors do not include those errors caused by (a) Licensee’s negligence, (b) any unauthorized modification or alteration Licensee makes to the Software, (c) data that does not conform to Licensor’s specified data format, (d) operator error, or (e) use not conforming to the Licensor’s supported technical environment specified in the Documentation.

  • Outage has the meaning set forth in the CAISO Tariff.

  • Service Level means the standard set forth below by which IBM measures the level of service it provides in this SLA.

  • Disinfection profile means a summary of Giardia lamblia inactivation through the treatment plant.

  • Security Vulnerability means a flaw or weakness in system security procedures, design, implementation, or internal controls that could be exercised (accidentally triggered or intentionally exploited) and result in a security breach such that data is compromised, manipulated or stolen or the system damaged.

  • Problem means an unknown underlying cause of one or more Incidents. It becomes a Known Error when the root cause is known and a temporary workaround or permanent alternative has been identified.

  • Service Levels means the service levels to be met by the Services as referenced in the Contract Letter and set out in the Specification Schedule.

  • Critical Path means those Trade Contractor Work activities identified on the Construction Schedule which, if delayed, will cause a corresponding Delay in the Substantial Completion Date.

  • compatibility means compatibility as defined in point (10) of Article 2 of Directive (EU) 2019/770;

  • Downtime means the Total Minutes in the Month during which the Cloud Service (or Servers for Server Provisioning) does not respond to a request from SAP’s Point of Demarcation for the data center providing the Cloud Service (or Server for Server Provisioning), excluding Excluded Downtime.

  • Encounter means a record of a medically-related service rendered by an AHCCCS-registered provider to a member enrolled with a contractor on the date of service.

  • Root Cause Analysis Report means a report addressing a problem or non-conformance, in order to get to the ‘root cause’ of the problem, which thereby assists in correcting or eliminating the cause, and prevent the problem from recurring.