Defect Severity Levels Sample Clauses

Defect Severity Levels. Defects (classified as Catastrophic, Critical, Major, or Minor defects) for all Products are defined in this Section. The classification and reclassification of the defect level shall be at the reasonable discretion of BTE; provided, however, that such classifications and reclassifications shall be in accordance with the definitions set forth in this Section. In the event a defect is reclassified to a higher severity level by BTE, the Service Restoration time period shall begin at the time the defect is reclassified.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Defect Severity Levels. Defects in the Software are classified according to severity of impact on the use of the Software as follows: 2 Continued performance of one or more essential functions is impaired and may be circumvented or avoided on a temporary basis by the intended user. 3 Continued performance of one or more non-essential functions is impaired.
Sample 1Sample 2Sample 3
Defect Severity Levels. Defects (classified as Catastrophic, Critical, Major, or Minor defects) for all Products are defined in this Section. The classification and reclassification of the defect level shall be at the sole discretion of School District; provided, however, that such classifications and reclassifications shall be in accordance with the definitions set forth in this Section. In the event a defect is reclassified to a higher severity level by School District, the Service Restoration time period shall begin at the time the defect is reclassified.
Sample 1Sample 2
Defect Severity Levels. Fatal Defect Level: any one of these results will cause the issue to receive the highest priority eligible for emergency bug fix. Examples: System consistently crashes or stop responding and there is no work-around, Major function that would impact a majority of the customer base and there is no work-around.
Sample 1

Related to Defect Severity Levels

  • Performance Levels (a) The Performance Levels which apply to the performance by the respective Parties of their obligations under this Agreement are set out in Part 1 of Schedule 5. A failure by either Party to achieve the relevant Performance Level will not constitute a breach of this Agreement and the only consequences of such failure as between the Parties shall be the consequences set out in this Clause 5.6. (b) If the Operator does not comply with the Operator Performance Level then the Access Holder must pay to QR Network the amount determined in accordance with Schedule 5 as part of the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following QR Network becoming entitled to that amount. Where there is no next Billing Period, the Operator must pay such amount to QR Network within fourteen (14) days after receipt of a Tax Invoice from QR Network. (c) If QR Network does not comply with the QR Network Performance Level then QR Network will credit to the Access Holder the amount determined in accordance with Schedule 5 by way of a deduction from the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following the Access Holder becoming entitled to that amount. Where there is no next Billing Period, QR Network must pay such amount to the Access Holder within fourteen (14) days after receipt of a Tax Invoice from the Access Holder. (d) The Parties must, if requested by either Party, meet to review the Performance Levels subject to such review not occurring within six (6) Months after the Commitment Date or any previous review of the Performance Levels. If either Party notifies the other that it considers that the Performance Levels are no longer appropriate, the Parties may agree on varied Performance Levels and any associated variations to the Agreement including the Base Access Charges and the Train Service Description. If the Parties are unable to agree to such variations, then the existing Performance Levels shall continue to apply unless varied by QR Network in accordance with the provisions of Clause 5.6(e). (e) In the event that the Access Holder and/or the Operator (i) does not comply in any material respect with the Train Service Description; and (ii) the Access Holder fails to demonstrate to the reasonable satisfaction of QR Network when requested to do so, that the Access Holder will consistently comply with the Train Service Description for the remainder of the Term then, following consultation with the Access Holder, QR Network will be entitled to: (iii) vary the Train Service Description to a level it reasonably expects to be achievable by the Access Holder for the remainder of the Term having regard to the extent of previous compliance with the Train Service Description (ignoring, for the purpose of assessing previous compliance, any non-compliance to the extent that the non-compliance was attributable to a Railway Operator (other than the Access Holder) or to QR Network); and (iv) vary the Agreement (including, without limitation, the Operator Performance Level and the Base Access Charges) to reflect the impact of the change in the Train Service Description. (f) The Access Holder shall be entitled to dispute any variation proposed by QR Network pursuant to Clause 5.6(e) and such dispute will be referred to an expert for resolution in accordance with Clause 17.3.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Staffing Levels To the extent legislative appropriations and PIN authorizations allow, safe staffing levels will be maintained in all institutions where employees have patient, client, inmate or student care responsibilities. In July of each year, the Secretary or Deputy Secretary of each agency will, upon request, meet with the Union, to hear the employees’ views regarding staffing levels. In August of each year, the Secretary or Deputy Secretary of Budget and Management will, upon request, meet with the Union to hear the employees’ views regarding the Governor’s budget request.

  • Corrective Measures If the Participating Generator fails to meet or maintain the requirements set forth in this Agreement and/or the CAISO Tariff, the CAISO shall be permitted to take any of the measures, contained or referenced in the CAISO Tariff, which the CAISO deems to be necessary to correct the situation.

  • Temperature Measurement Temperature will be measured by the nearest automatic Melbourne Bureau of Meteorology Monitoring Station for example (but not limited to): Melbourne, Moorabbin, Dunns Hill, Melbourne Airport, Frankston, and Point Xxxxxx. At the commencement of each project, the onsite management and employee representatives shall agree which is to be the applicable automatic weather monitoring station.

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Service Levels All service level requirements will be set forth in Exhibit A (“XXXX.xxx Referral Service Level Requirements”). Recipient Xxxxxx agrees to adhere, and encourage Recipient Agent’s adherence, with the version of the XXXX.xxx Referral Service Level Requirements in effect at the time XXXX.xxx identifies the Referral to Recipient Broker/Agent.

  • Technical Objections to Grievances It is the intent of both Parties of this Agreement that no grievance shall be defeated merely because of a technical error, other than time limitations in processing the grievance through the grievance procedure. To this end, an arbitration board shall have the power to allow all necessary amendments to the grievance and the power to waive formal procedural irregularities in the processing of a grievance, in order to determine the real matter in dispute and to render a decision according to equitable principles and the justice of the case.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!