Launch Delays Sample Clauses

The Launch Delays clause defines the procedures and responsibilities in the event that a scheduled product or service launch is postponed. Typically, this clause outlines the conditions under which a delay may occur, the required notifications between parties, and any adjustments to timelines or deliverables that result from the delay. For example, it may specify how much advance notice must be given or what remedies are available if the delay causes additional costs. Its core practical function is to manage expectations and allocate risk by providing a clear framework for handling unforeseen postponements, thereby minimizing disputes and ensuring project continuity.
POPULAR SAMPLE Copied 1 times
Launch Delays. In the event of a Launch delay that is not attributable to the Contractor, Inmarsat shall pay interest monthly to the Contractor on the total amounts given in Tables D2 and D3 of Annex D hereto, entitled Payment Plan, at the annual rate of **** for each day of delay in Launch from the date announced at the Pre-Shipment Review to the date of actual Launch on a compound basis.
Launch Delays. In the event of a Launch delay that is not attributable to the Contractor, Inmarsat shall pay interest monthly to the Contractor on the total amounts given in Tables D-2 and D-3 of Annex D hereto, entitled Payment Plan, at a rate of **** for each day of delay in Launch from the date announced at the Pre-Shipment Review to the date of actual Launch. No payment shall be due until the period of Launch delay exceeds sixty (60) days, provided however, that once the period of Launch delay has exceeded sixty (60) days, Inmarsat shall be liable to pay such interest for each day of delay from the Launch date announced at the Pre-Shipment Review provided that the interest for the initial sixty (60) days shall be compounded monthly.
Launch Delays. Customer shall notify Boeing as soon as possible after learning or becoming aware of any Launch Agency launch date delays not caused by Boeing.
Launch Delays. In the event that RouteCloud misses a mutually agreed-upon launch date for reasons reasonably in its control, the following penalties shall apply: • ProtectorMobile Launch delayed more than 90 days: TASER shall be entitled to receive [*]. Such payment shall be deducted from the contribution margin prior to sharing contribution margins as contemplated herein. • Driver Protector Launch delayed more than 90 days: TASER Shall be entitled to receive [*]. Such payment shall be deducted from the contribution margin prior to sharing contribution margins as contemplated herein. * Confidential information on this page has been omitted and filed separately with the Securities and Exchange Commission pursuant to a Confidential Treatment Request.

Related to Launch Delays

  • Tenant Delays A "Tenant Delay” shall be defined as any delay in the design, permitting or performance of the Base Building Work to the extent that such delay is actually caused by any act or, where there is a duty to act under this Lease, any failure to act by Tenant or Tenant's contractors, architects, engineers, or anyone else engaged by or on behalf of Tenant in connection with the construction of the Tenant Improvement Work as set forth in this Article III (including, without limitation, any delays resulting from the Approved Tenant Finishes under Section 3.l(C) above) and disclosed to Tenant as hereinafter provided. Notwithstanding the foregoing, in no event shall any delays in the completion of the Base Building Work caused by Tenant’s use of non-union labor constitute a Tenant Delay hereunder. Notwithstanding the foregoing, no event shall be deemed a Tenant Delay unless and until Landlord has given Tenant written notice (the "Tenant Delay Notice") advising Tenant: (x) that a Tenant Delay is occurring and setting forth Landlord's good faith estimate as to the likely length of such Tenant Delay; (y) of the basis on which Landlord has determined that a Tenant Delay is occurring; and (z) the actions which Landlord believes that Tenant must take to eliminate such Tenant Delay. No event shall be deemed to be a Tenant Delay unless and until Tenant has failed to rectify the situation causing the Tenant Delay within forty-eight (48) hours after Tenant's receipt of the Tenant Delay Notice (which for the purposes of determining receipt may be delivered by hand to Tenant's Construction Representative, with copies to follow to Tenant at the notice address set forth in Section 1.2 of this Lease within five (5) days thereafter); provided, however, that if Tenant shall fail to eliminate the delay within the aforesaid 48-hour period, then the 48-hour cure period shall be included in the period of time charged to Tenant pursuant to such Tenant Delay Notice (it being understood and agreed that if Tenant shall in fact eliminate the Tenant Delay within the 48-hour cure period, no Tenant Delay shall be deemed to have occurred for the purposes of this Article III). In addition, any delay to the extent caused by (i) Landlord Delay or (ii) subject to the limitations of subsection (D) below, Tenant's Force Majeure (as defined in said subsection (D)) shall not constitute Tenant Delay. Tenant covenants that no Tenant Delay shall delay commencement of the Term or the obligation to pay Annual Fixed Rent or Additional Rent. The Delivery Dates and/or the date of substantial completion of the Base Building Work, as applicable, shall be deemed to have occurred as of the date when such Delivery Dates and/or date of substantial completion of the Base Building Work, as applicable, would have occurred but for any Tenant Delays, as determined by Landlord in the exercise of its good faith business judgment (it being understood and agreed that the foregoing shall not be construed so as to relieve Landlord of its obligation to actually complete the Base Building Work, notwithstanding the fact that substantial completion may have been deemed to have occurred prior to actual completion as the result of Tenant Delays).

  • Excusable Delays Except with respect to defaults of subproviders, the Engineer shall not be in default by reason of any failure in performance of this contract in accordance with its terms (including any failure to progress in the performance of the work) if such failure arises out of causes beyond the control and without the default or negligence of the Engineer. Such causes may include, but are not restricted to, acts of God or the public enemy, acts of the Government in either its sovereign or contractual capacity, fires, floods, epidemics, quarantine restrictions, strikes, freight embargoes, and unusually severe weather.

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate ▇▇▇▇▇’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Milestone Schedule Please state the status and progress of each Milestone and identify any completed Milestone(s) for the previous calendar quarter.

  • Unavoidable Delays Delays due to acts of God, acts of public agencies, labor disputes, strikes, fires, freight embargoes, inability (despite the exercise of due diligence) to obtain supplies, materials, fuels or permits, or other causes or contingencies (excluding financial inability) beyond the reasonable control of Landlord or Tenant, as applicable. Landlord shall use commercially reasonable efforts to provide Tenant with prompt notice of any Unavoidable Delays.