Response Targets Sample Clauses

Response Targets. PowerSchool will make commercially reasonable efforts to ensure that submitted cases are assigned the proper level of priority. “Response Time” is the time it takes before a support agent makes initial contact with the Technical Contact individual who submitted the Case. Except for Priority 0 cases logged by the Customer, response times are calculated within Standard Support Hours. Response Time is not a resolution goal and should not be interpreted as a guarantee of service. PowerSchool will use commercially reasonable efforts to adhere to the time frames listed below. Contractor does not provide resolution targets and Response Time should not be interpreted as a commitment regarding resolution timeframes. Severity Target Response Times Priority 0 – Urgent 1 hour Priority 1 – Critical must have 4 hours Priority 2 – Must have not critical 8 hours Priority 3 – Nice to have 2 business days
AutoNDA by SimpleDocs
Response Targets. 1. SRSB will use its best commercial efforts to meet the targets set out in this Schedule for the Software Maintenance.
Response Targets. 1. STSB will use its best commercial efforts to meet the targets set out in this Schedule for the Software Maintenance.
Response Targets. The following table defines severity class level response timeframes, effort required until resolution, and update frequencies currently employed by XXXX Support staff: Severity Class Initial Response to Customer Effort Required Until Resolution Update Frequencies Class 1 No greater than four hours if reported between 9 AM and 1 PM on normal business days at XXXX's business location. Errors reported other times will receive a response within four hours on the next normal business day at XXXX's business location. Constant effort during normal business hours until relief is provided in the form of a Work-Around or a software hotfix. As mutually agreed but at a minimum, every business day during normal business hours at XXXX's registered business location unless both Parties have agreed to a different frequency.
Response Targets. Individual Force requirement is shown below and are estimated based on known positions at the time of tender and therefore they maybe subject to amendment
Response Targets. Unitrends Technical Support follows a tiered response target system based on issue severity, as defined below. Unitrends will use commercially reasonable efforts to meet response targets but cannot guarantee meeting response targets. Note that Cases generated at the end of the Contract Coverage Hours, for which the Case response target rolls to the next business day, will be responded to the next business day. 12 Severity Level Definition Response Target Severity 1 One or more of the following: • The Customer’s production server or other mission critical system(s) are down • A substantial portion of the Customer’s mission critical data is at a significant risk of loss or corruption • The Customer has had a substantial loss of service • The Customer’s business operations have been severely disrupted • The Customer has not met a major milestone in a required test system • An issue in which the product causes the Customer’s network or system to fail catastrophically or that compromises overall system integrity or data integrity when the product is installed or when it is in operation (i.e., causing a system crash, loss or corruption of data, or loss of system security) and significantly impacts the Customer’s ongoing operations in a production environment. Requires an immediate workaround or solution. One (1) Business Hours Severity 2 • A problem or issue is adversely impacting production operations, but the production system is not down; product operates, but is seriously restricted. Three (3) Business Hours

Related to Response Targets

  • Targets a) Seller’s supplier diversity spending target for Work supporting the construction of the Project prior to the Commercial Operation Date is ____ percent (___%) as measured relative to Seller’s total expenditures on construction of the Project prior to the Commercial Operation Date, and;

  • Regulatory Milestones Celgene shall make the following approval milestone payments to Jounce that are set forth below upon the first achievement by or on behalf of Celgene, its Affiliates or Sublicensees of the Regulatory Milestone Events set forth below with respect to the first Co-Co Product that achieves such event. For clarity, each milestone set forth below shall be due and payable one time only (regardless of the number of Co-Co Products to achieve any such Regulatory Milestone Event). CERTAIN CONFIDENTIAL PORTIONS OF THIS EXHIBIT WERE OMITTED AND REPLACED WITH “[***]”. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECRETARY OF THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO AN APPLICATION REQUESTING CONFIDENTIAL TREATMENT PURSUANT TO RULE 406 PROMULGATED UNDER THE SECURITIES ACT OF 1933, AS AMENDED. Regulatory Milestone Event (For the first Co-Co Product that achieves such event) Milestone Payments (in $ millions) [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] For each of Paragraphs (1) - (3) of this Exhibit C-2, the Parties understand and agree that in no event will more than one (1) milestone payment be paid with respect to any specific event triggering a payment under this Jounce Lead Co-Co Agreement.

  • Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving the following development milestones in its diligence activities under this AGREEMENT: (a) (b).

  • Performance Targets Threshold, target and maximum performance levels for each performance measure of the performance period are contained in Appendix B.

  • Milestones Subject to the provisions of the SGIP, the Parties shall agree on milestones for which each Party is responsible and list them in Attachment 4 of this Agreement. A Party’s obligations under this provision may be extended by agreement. If a Party anticipates that it will be unable to meet a milestone for any reason other than a Force Majeure event, it shall immediately notify the other Parties of the reason(s) for not meeting the milestone and (1) propose the earliest reasonable alternate date by which it can attain this and future milestones, and (2) requesting appropriate amendments to Attachment 4. The Party affected by the failure to meet a milestone shall not unreasonably withhold agreement to such an amendment unless it will suffer significant uncompensated economic or operational harm from the delay, (1) attainment of the same milestone has previously been delayed, or (2) it has reason to believe that the delay in meeting the milestone is intentional or unwarranted notwithstanding the circumstances explained by the Party proposing the amendment.

  • Commercial Milestones In partial consideration of the rights granted by AstraZeneca to Licensee hereunder, Licensee shall pay to AstraZeneca the following payments, which shall be non-refundable, non-creditable and fully earned upon the first achievement of the applicable milestone event:

  • Sales Milestones Subject to the terms and conditions set forth in the Agreement, in the event that the Annual Net Sales made by or on behalf of a Selling Entity for all Licensed Products in a given calendar year first exceeds a threshold set forth in the table immediately below, Pyxis shall pay to LCB the following one-time, non-refundable, non-creditable milestone payments. Annual Net Sales Milestone Threshold Payment (US Dollars) [***] [***] [***] [***] [***] [***] [***] [***] [***] [***] In the event that in a given calendar year more than one (1) Annual Net Sales milestone threshold is achieved, Pyxis shall pay to LCB each separate Annual Net Sales milestone payment with respect to each Annual Net Sales milestone threshold that is achieved in such calendar year. Pyxis shall notify LCB in writing upon the first achievement, in respect of a Licensed Product, by or on behalf of Pyxis or its Affiliate or Sublicensee, of each of the Milestones set forth in Section 5.2 (Development Milestones), Section 5.3 (Regulatory Milestones) and Section 5.4 (Sales Milestones) no later than [***] of Pyxis’s knowledge of achievement thereof, and in any event, each of the Milestones set forth in Section 5.4 (Sales Milestones) no later than [***] after the end of the applicable calendar year in which such Milestone is achieved. No later than [***] of receipt of an appropriate invoice from LCB, Pyxis shall pay the applicable payment due upon achievement of the corresponding Milestone Event. Each Milestone Event shall be deemed to be achieved once for all Licensed Products and shall be payable only once.

  • Selection Criteria Each Contract is secured by a new or used Motorcycle. No Contract has a Contract Rate less than 1.00%. Each Contract amortizes the amount financed over an original term no greater than 84 months (excluding periods of deferral of first payment). Each Contract has a Principal Balance of at least $500.00 as of the Cutoff Date.

  • Development and Regulatory Milestones With respect to each of the following milestones, Ikaria shall pay BioLineRx the corresponding payment set forth below within [**] days after the achievement by Ikaria, its Affiliates or Licensees of such milestone: MILESTONE PAYMENT

  • Timeline Contractor must perform the Services and deliver the Deliverables according to the following timeline: • •

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