Severity 2 Errors definition

Severity 2 Errors. A Severity Two Error means (i) the production system is functioning with limited capabilities, or (ii) is unstable with periodic interruptions, or (iii) mission critical applications, while not being affected, have experienced material system interruptions. PICS assigns a specialist to begin an Update, and provides additional, escalated procedures as reasonably determined necessary by PICS Support staff. PICS exercises commercially reasonable efforts to provide a workaround or include a fix for the Severity 2 Errors in the next Maintenance Release.
Sample 1Sample 2
Severity 2 Errors. A Severity Two Production Error means (i) the production system is functioning with limited capabilities, or (ii) is unstable with periodic interruptions, or (iii) mission critical applications, while not being affected, have experienced material system interruptions. A Severity Two Development Error means (iv) there is a time sensitive question impacting performance or deliverables, or (v) a major subsystem under development is blocked. BEA assigns a specialist to begin an Update, and provides additional, escalated procedures as reasonably determined necessary by BEA Support Services staff. BEA exercises commercially reasonable efforts to provide a workaround or include a fix for the Severity 2 Errors in the next Maintenance Release.
Sample 1
Severity 2 Errors. Definition: A problem has been identified that severely affects or restricts major functionality. The problem is of a time sensitive nature and important to long-term productivity but is not causing an immediate work stoppage. No workaround is available and operation can continue in a restricted fashion. Response Commitment: A Support engineer will respond to a call within two (2) hours 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 リースで✲用可能になった時点で、そ✰アップデートを Gen に提供することとします。 (c) 取り扱い中止になったソ➚トウェア✰すべて✰代替製品 (d) ➚リーダイヤル✰電話ホットライン、または電子メールアカウント (あるいはそ✰両方) - サポート対応時間は 24 時間 365 日で、ソ➚トウェア✰技術サポートに精通したスタッ➚が対応すること (e) 診断ツール、Web ベース✰ケース提出機能、FAQに対する回答、テクニカルサポートニ➦ースグループへ✰アクセス、Gen がプ➫バイダ✰サポート機能を十分に活用するため✰、プ➫バイダ✰内部サポート手順と操作に関する説明、プ➫バイダ✰サポート対象顧客に提供するそ✰他✰ Web リソース (f) サポートに関する一般的な問題に対応するため✰メール通知サービス Gen が、サポートを提供するプ➫バイダに対して、Gen ✰ネットワークに直接またはリモートでアクセスすることを許可した場合、プ➫バイダは、安全なネットワークアクセスに関する追加規約へ✰同意を求められることがあります。 3. サポート✰手順と分類: Gen は、以下に記載されている手順に従い、プ➫バイダ✰サポート部門に連絡できるも✰とします。 プ➫バイダ✰サポート部門に対する最初 ✰連絡は、次✰ように処理されます: (i) 最初✰連絡を受けてから 15 分以内にサポート担当者が対応するか、連絡がサポートキ➦ーに直接格納される、(ii) 連絡がプ➫バイダ ✰問い合わせトラッキングシステムに記録される、(iii) 連絡にケース番号が割り当てられる。 Gen は、各サポート依頼を以下に示す重大度に従って分類し、プ➫バイダは、以下に示す対応を行うも✰とします。 問い合わせに対するすべて✰回答は、英語または Gen が指定するそ✰他✰言語 (あるいはそ✰両方) により、プ➫バイダが提供することとします。指定された言語でサポートを提供できるだけ✰能力を有するサポート担当者が、回答を行う必要があります。 • 重大度 1 ✰エラー: 定義: 重要なシステムにおいて問題が発生し、1つ以上✰機能が継続的に✲用できない状態 (または、機能が大きく制限されている状態) になっており、重要な業務に対して重大なリスクが発生している場合は、重大度 1 ✰エラーとして分類されます。こ✰問題により、データ✰損失やデータ✰可用性✰制限が発生したり、Gen が大きな財務的影響を受けたりする可能性があります。 対応: サポートエンジニアは、問題✰報告を受けてから 1 時間以内に電話対応を行います。 プ➫バイダは、すみやかにサポートエンジニアを割り当てて問題を調査し、重大度 1 ✰エラー✰報告を受けたことと、当該エラーを修正するため✰措置を講じていることを Gen に通知します。 プ➫バイダは Gen に対して、少なくとも 3 時間ごとに調査✰状況について報告を行うこととします。プ➫バイダは、Gen に回避策/修正方法を提供するため✰作業を行うこととします。4 時間以内に回避策/修正方法が見つからなかった場合は、プ➫バ
Sample 1

Examples of Severity 2 Errors in a sentence

  • We will provide status updates for Severity 1 Errors every business day and for Severity 2 Errors every two business days until resolved.

  • For Severity 1 and Severity 2 Errors, Entrust will advise Customer periodically at reasonable intervals as to the progress made by Entrust in diagnosing and/or correcting any reported Error.

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

  • Radiant’s support specialist shall use commercially reasonable efforts to respond to Severity 1 and Severity 2 Errors in accordance with the following Response Schedule.

  • Federal Committee on Statistical Methodology Statistical Policy Seminar, Washington, DC, November 6-72002 WC Hadden, C Muntaner, N Kravets.

  • Examples of Severity 2 Errors are: Long delays to processing of subscriptions, individual users are unable to authenticate, or specific browser issues (while other browsers work).

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

  • All Severity 1 or Severity 2 Errors on Production Environment Software should be reported by Customer to Entrust by telephone support during the time when telephone support is available (as set out above).

  • Email: xxxxxxx@xxxxxxxxxxx.xxx Telephone UK: +00 (0) 0000 000 000 Telephone US: Toll Free 000 000 0000 Telephone AUS: +00 0000 000000 The preferred method of communication is email except that all Severity 1 and Severity 2 Errors must be reported to Thunderhead by telephone.

  • Qlik will communicate with Partner 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 7 below) or work-around is provided.


More Definitions of Severity 2 Errors

Severity 2 Errors means a Support Ticket level indicating a less severe Service Degradation than those described as Severity 1; Severity 2 Tickets means the Service is (i) functioning with limited capabilities, or (ii) is unstable with periodic interruptions, or (iii) mission critical applications, while not being affected, have experienced material system interruptions.
Sample 1
Severity 2 Errors. A "Severity Two Production Error" means: (i) the production system is functioning with limited capabilities; or (iI) is unstable with periodic interruptions; or (iii) mission critical applications, while not being affected, have experienced material system interruptions. A Severity Two Development Error means: (1) there is a time sensitive question impacting performance or deliverables; or (2) a major subsystem under development is blocked. Tarsin assigns a specialist to begin an Update, and provides additional, escalated procedures as reasonably determined necessary by Tarsin Support services staff. Tarsin exercises commercially reasonable efforts to provide a workaround or include a fix for the Severity 2 Errors in the next Maintenance Release.
Sample 1

Related to Severity 2 Errors

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

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

  • Outage means the state of a component when it is not available to perform its intended function due to some event directly associated with that component. An outage may or may not cause an interruption of service to customers, depending on system configuration.

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

  • Problem means an unknown underlying cause of one or more Incidents.

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

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

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

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

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

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

  • Outages means the planned unavailability of transmission and/or generation facilities dispatched by PJM or the NYISO, as described in Section 35.9 of this Agreement.

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

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