Problem Severity Sample Clauses

Problem Severity. Upon receipt of a properly submitted Problem, Bonitasoft shall prioritize it in accordance with the guidelines below. Problem Severity shall be defined jointly with Customer and supported by business cases where necessary. Problem Severity may be re-evaluated upon submission of a workaround. Blocking Problem — Blocking Problems are major production problems with in the Bonitasoft Software that severely impact the Customer’s production environment, or that result in a loss of production data or interruption of service, or that cause significant impact to portions of the Customer’s business operations and productivity, and no work-around exists. Bonitasoft will use continuous efforts during its normal hours of operation to provide are solution for any Blocking Problem as soon as is commercially reasonable. The Bonitasoft Problem Monitoring tool shall show such issues with a “Block” status. Non-Blocking Problem — A Non-Blocking Problem is any other problem with in the Bonitasoft Software where the Customer’s system is functioning. This includes situations where the Customer’s system is operating but in a reduced capacity, or for which Bonitasoft has provided a reasonably effective work-around. Problems existing in a non-production environment that would otherwise qualify as a Blocking Problem if they were in a production system qualify as Non-Blocking. Bonitasoft will use reasonable efforts during its normal hours of operation to provide are solution for any Non-Blocking problem as soon as is commercially reasonable. The Bonitasoft Problem Monitoring tool shall show such issues with a “Non-Blocking” status. Enhancement Request (ER) — An ER is a recommendation for future product enhancement or modification to add official support and documentation for unsupported or undocumented feature, or features that do not currently exist in the Bonitasoft Software. Bonitasoft will take ERs into consideration in the product management process, but has no obligation to deliver enhancements based on any ER. The Bonitasoft Problem Monitoring tool shall show such issues with a “Feature” status.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Problem Severity. The severity of a Problem will be determined by Nortel and Seller based on the criteria in the matrix below.
Sample 1Sample 2
Problem Severity. All problems are classified by the severity it causes. For the purpose of this agreement there will be three severity levels defined as: Severity 1 - Application cannot run or continued use will cause corruption of data. Severity 2 - Problem is persistent but a workaround is available. Must be addressed, but can afford to follow established procedures to migrate the fix to the production environment. Categorized in Optics as Urgent priority. Severity 3 - Problem is intermittent, may cause minimal impact on operation of application. Work around is available. Can wait for future release to correct the problem. Characterized in Optics as High or lower priority.
Sample 1
Problem Severity. Nortel and Seller will mutually categorize Problems and Seller will provide Technical Support Services according to the definitions in Section 3.1 above and the priority levels set forth in the matrix below and the service level responsibilities set out in Section 3.4.
Sample 1
Problem Severity. ANDA defines three problem severity classifications for Reported Problems aligning with TL9000 R3.0 standards. In order to classify a request, ANDA technical support personnel will confirm with Customer the impact of the reported problem to determine an appropriate classification. Where parties disagree on the classification of a particular Reported Problem, Customer and ANDA technical contacts will undertake to discuss the problem with a view to reaching a mutually acceptable classification, where possible.
Sample 1
Problem Severity. For purposes hereof, the levels of severity for providing Support Services are defined as follows: Sev1: Emergency – an issue that prevents Visitors from receiving Content Recommendations. Sev2: Limitation – an issue or problem rendering Content Recommendations inaccurate or partially unavailable AND with significant impact on Customer’s ability to provide services to its Visitors, or ExactTarget’s ability to provide services to Customer. Sev3: Minor Defect – an issue or problem in which Content Recommendations are generally available and functionality is not significantly affected, but in which a correction or modification is required to enable the normal function and operation of the Content Recommendations.
Sample 1
Problem Severity. 1. The problem severity is defined by its impact on the operational A-VDGS system. There are two types of problems: (I)
Sample 1
AutoNDA by SimpleDocs
Problem Severity. As long as Customer is current in making the payments required by the submission of payment and this Agreement, ZYRL will respond to problems reported by a Customer Representative according to the problem severity levels defined below. ZYRL reserves the right to assign or modify the Severity of a given problem if one is not provided by the Customer or if the submitted severity level does not meet, in ZYRL’s sole discretion, the definition as defined below. Severity Definition Example Critical/Down Loss of service to ZYRL Product ● Inability for Customer to access ZYRL Dashboard ● Inability for customers to use ZYRL product. ● ZYRL apps not loading at all Major Outage or problem affecting specific application or parts of Dashboard ● Inability to customize tagging on ZYRL dashboard ● Inability to customize campaign on ZYRL Dashboard ● Inability to view tagging and campaign statistics on ZYRL dashboard ● ZYRL apps not loading Average Problem results in incorrect, incomplete, or inconsistent results ● Inability to enable/disable secondary features of products or applications in the ZYRL Dashboard ● Inability to enable/disable secondary features of products or applications in the ZYRL Dashboard that do not affect app performance Minor Minor problem or request that is not time sensitive ● Intermittent issues that cannot be replicated consistently ● Minor issues to ZYRL Dashboard or application that do not affect performance ● Product change request ● Product version updates
Sample 1

Related to Problem Severity

  • 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 Annex 1 to this Part A of this Call Off Schedule sets out the Service Levels the performance of which the Parties have agreed to measure. The Supplier shall monitor its performance of this Call Off Contract by reference to the relevant performance criteria for achieving the Service Levels shown in Annex 1 to this Part A of this Call Off Schedule (the Service Level Performance Criteria) and shall send the Customer a Performance Monitoring Report detailing the level of service which was achieved in accordance with the provisions of Part B (Performance Monitoring) of this Call Off Schedule. The Supplier shall, at all times, provide the Services in such a manner that the Service Levels Performance Measures are achieved. If the level of performance of the Supplier of any element of the provision by it of the Services during the Call Off Contract Period: is likely to or fails to meet any Service Level Performance Measure or is likely to cause or causes a Critical Service Failure to occur, the Supplier shall immediately notify the Customer in writing and the Customer, in its absolute discretion and without prejudice to any other of its rights howsoever arising including under Clause 12 of this Call Off Contract (Service Levels and Service Credits), may: require the Supplier to immediately take all remedial action that is reasonable to mitigate the impact on the Customer and to rectify or prevent a Service Level Failure or Critical Service Level Failure from taking place or recurring; and if the action taken under paragraph (a) above has not already prevented or remedied the Service Level Failure or Critical Service Level Failure, the Customer shall be entitled to instruct the Supplier to comply with the Rectification Plan Process; or if a Service Level Failure has occurred, deduct from the Call Off Contract Charges the applicable Service Level Credits payable by the Supplier to the Customer in accordance with the calculation formula set out in Annex 1 of this Part A of this Call Off Schedule; or if a Critical Service Level Failure has occurred, exercise its right to Compensation for Critical Service Level Failure in accordance with Clause 13 of this Call Off Contract (Critical Service Level Failure) (including subject, for the avoidance of doubt, the proviso in Clause 13.1.2 of this Call Off Contract in relation to Material Breach). Approval and implementation by the Customer of any Rectification Plan shall not relieve the Supplier of any continuing responsibility to achieve the Service Levels, or remedy any failure to do so, and no estoppels or waiver shall arise from any such Approval and/or implementation by the Customer. SERVICE CREDITS Annex 1 to this Part A of this Call Off Schedule sets out the formula used to calculate a Service Credit payable to the Customer as a result of a Service Level Failure in a given service period which, for the purpose of this Call Off Schedule, shall be a recurrent period of [one Month] during the Call Off Contract Period (the Service Period).

  • SERVICE LEVEL DESCRIPTION The Fund Accounting Agreement is hereby amended by deleting the Service Level Description attached thereto and replacing it in its entirety with the Service Level Description attached hereto.

  • Root Cause Analysis Upon Vendor's failure to provide the Services in accordance with the applicable Service Levels (for any reason other than a Force Majeure Event) Vendor will promptly (a) perform a root-cause analysis to identify the cause of such failure, (b) provide Prudential with a report detailing the cause of, and procedure for correcting, such failure, (c) obtain Prudential's written approval of the proposed procedure for correcting such failure, (d) correct such failure in accordance with the approved procedure, (e) provide weekly (or more frequent, if appropriate) reports on the status of the correction efforts, and (f) provide Prudential with assurances satisfactory to Prudential that such failure has been corrected and will not recur.

  • Business Continuity Registry Operator shall maintain a business continuity plan, which will provide for the maintenance of Registry Services in the event of an extraordinary event beyond the control of the Registry Operator or business failure of Registry Operator, and may include the designation of a Registry Services continuity provider. If such plan includes the designation of a Registry Services continuity provider, Registry Operator shall provide the name and contact information for such Registry Services continuity provider to ICANN. In the case of an extraordinary event beyond the control of the Registry Operator where the Registry Operator cannot be contacted, Registry Operator consents that ICANN may contact the designated Registry Services continuity provider, if one exists. Registry Operator shall conduct Registry Services Continuity testing at least once per year.

  • Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.

  • BUSINESS CONTINUITY/DISASTER RECOVERY In the event of equipment failure, work stoppage, governmental action, communication disruption or other impossibility of performance beyond State Street’s control, State Street shall take reasonable steps to minimize service interruptions. Specifically, State Street shall implement reasonable procedures to prevent the loss of data and to recover from service interruptions caused by equipment failure or other circumstances with resumption of all substantial elements of services in a timeframe sufficient to meet business requirements. State Street shall enter into and shall maintain in effect at all times during the term of this Agreement with appropriate parties one or more agreements making reasonable provision for (i) periodic back-up of the computer files and data with respect to the Trusts; and (ii) emergency use of electronic data processing equipment to provide services under this Agreement. State Street shall test the ability to recover to alternate data processing equipment in accordance with State Street program standards, and provide a high level summary of business continuity test results to the Trusts upon request. State Street will remedy any material deficiencies in accordance with State Street program standards. Upon reasonable advance notice, and at no cost to State Street, the Trusts retain the right to review State Street’s business continuity, crisis management, disaster recovery, and third-party vendor management processes and programs (including discussions with the relevant subject matter experts and an on-site review of the production facilities used) related to delivery of the service no more frequently than an annual basis. Upon reasonable request, the State Street also shall discuss with senior management of the Trusts any business continuity/disaster recovery plan of the State Street and/or provide a high-level presentation summarizing such plan.”

  • Service Requirement Except as otherwise provided in Section 6(e) of the Plan or Section 2 of this Agreement, this Option may be exercised only while you continue to provide Service to the Company or any Affiliate, and only if you have continuously provided such Service since the Grant Date of this Option.

  • Virus Management Transfer Agent shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within the Transfer Agent environment.

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