Forecast Customer shall provide Flextronics, on a monthly basis, a rolling [***] forecast indicating Customer’s monthly Product requirements. The first [***] of the forecast will constitute Customer’s written purchase order for all Work to be completed within the first [***] period. Such purchase orders will be issued in accordance with Section 3.2 below.
Forecasting Manager and Sprint PCS will work cooperatively to generate mutually acceptable forecasts of important business metrics including traffic volumes, handset sales, subscribers and Collected Revenues for the Sprint PCS Products and Services. The forecasts are for planning purposes only and do not constitute Manager's obligation to meet the quantities forecast.
Forecasts and Purchase Orders On or before the twelfth (12th) day of each month, beginning on January 12, 2022, Indivior shall furnish to Curia a written twelve (12) month rolling forecast of the quantities of Product that Indivior intends to order from Curia during such period ("Rolling Forecast"). The first six (6) months of such Rolling Forecast shall constitute a firm and binding commitment to order quantities of Product specified therein ("Firm Period Forecast"), and the following six (6) months of the Rolling Forecast shall be non-binding, good faith estimates. Each month of the Rolling Forecast shall begin on the twelfth (12th) of the calendar month in which such Rolling Forecast is submitted and end on the eleventh (11th) day of the following calendar month. With exception to the Firm Period Forecast, Curia reserves the right to reject any Rolling Forecast that does not align with the physical Processing capabilities of the Facility(ies) and the parties shall work in good faith to adjust the Rolling Forecast based on available resources, Facility capacity and other relevant factors. Indivior shall have the right to request an increase of the Firm Period Forecast to include additional units of Product. Curia may, in its sole discretion, supply such additional quantities, subject to Curia's other supply commitments and manufacturing capacity. In the event Curia agrees to supply such additional quantities, Indivior shall submit a Purchase Order for such additional quantities, with the required lead times as specified below. In no event shall Curia's inability to fulfill Purchase Orders for quantities in excess of the Firm Period Forecast be deemed a breach of this Agreement, nor relieve Indivior of its obligations under this Agreement. Indivior shall submit with each Rolling Forecast, a non-cancelable Purchase Order for the Firm Period Forecast (or such portion of the Firm Period Forecast not covered by previously submitted Purchase Orders). Indivior may alternatively submit Purchase Orders for certain portions of the Firm Period Forecast subsequent to the submission of the Rolling Forecast, provided the Purchase Orders provide the required lead time for Processing as set forth below. Curia shall notify Indivior of acceptance of the Rolling Forecast and any Purchase Order within seven (7) business days of receipt. Curia shall be deemed to have accepted Purchase Orders which it does not acknowledge within seven (7) business days of receipt. Curia shall have the right to reject Rolling Forecasts and Purchase Orders that are inconsistent with this Agreement. Each Purchase Order shall specify the quantity of Product being ordered, and the desired delivery date. Upon mutual agreement in writing for additional quantities of Product beyond the Firm Period Forecast, including projected delivery date(s), Indivior shall issue the applicable Purchase Order to be accepted by Curia as described above. Once placed, all Purchase Orders for Product shall be non-cancelable. No different or additional terms or conditions set forth in any Purchase Order shall modify in any way the terms and conditions of this Agreement, and in the event of a conflict between terms in any Purchase Order and this Agreement, the terms of this Agreement shall control. All Purchase Orders submitted in accordance with the terms of this Agreement shall be effective and binding on the parties upon acceptance by Curia. Except as otherwise provided herein, neither party shall have the right or power to refuse, reduce, or otherwise modify their obligations under any Purchase Order; however, Purchase Orders may be amended (i) upon written mutual agreement regarding such modification that is signed by both parties; or (ii) as otherwise provided in this Section 4.3 or Section 4.4.
Rolling Forecasts The Client shall provide Patheon with a written non-binding [ * ] forecast of the volume of each Product that the Client then anticipates will be required to be produced and delivered to the Client during each [ * ] of that [ * ] period. Such forecast will be updated by the Client [ * ] on or before the [ * ] day of each [ * ] on a rolling [ * ] basis. The most recent [ * ] forecast shall prevail.
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.
Rolling Forecast (i) On or before the fifteenth (15th) calendar day of each month during the Term (as defined in Section 6.1 herein), Buyer shall provide Seller with an updated eighteen (18) month forecast of the Products to be manufactured and supplied (each a “Forecast”) for the eighteen (18) month period beginning on the first day of the following calendar month. The first two months of each Forecast will restate the balance of the Firm Order period of the prior Forecast, and the first three (3) months of the Forecast shall constitute the new Firm Order period for which Buyer is obligated to purchase and take delivery of the forecasted Product, and the supply required for the last month of such new Firm Order period shall not be more than one (1) full Standard Manufacturing Batch from the quantity specified for such month in the previous Forecast (or Initial Forecast, as the case may be). Except as provided in Section 2.2(a), Purchase Orders setting forth Buyer’s monthly Product requirements will be issued for the last month of each Firm Order period no later than the fifteenth calendar day of the first month of each Firm Order period, and such Purchase Order will be in agreement with the Firm Order period of the Forecast. If a Purchase Order for any month is not submitted by such deadline, Buyer shall be deemed to have submitted a Purchase Order for such month for the amount of Product set forth in Buyer’s Forecast for such month.
Annual Forecasts As soon as practicable and in any event no later than thirty (30) days after the beginning of each Fiscal Year, an annual forecast prepared by management of the Parent, in reasonable detail and in the form customarily prepared by management of the Parent for its internal use and setting forth an explanation for the principal assumptions on which such forecasts were based, of balance sheets, income statements and cash flow statements with respect to the Parent and its Subsidiaries on a quarterly basis for each Fiscal Year thereafter until the Maturity Date.
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.
Commercial Milestone Payments For each Licensed Product, Licensee shall pay Arvinas the following one-time milestone event payments when the aggregate Net Sales of such Licensed Product in one or more particular country(ies) for a given calendar year (“Annual Net Sales”), where such Licensed Product is a Valid Claim Licensed Product at the time of sale in each of such country(ies), first achieves the corresponding threshold as set forth in this Section 6.3.2 below, subject to the terms of this Section 6.3 and the payment provisions in Article 7 below: Commercial Milestone Event Milestone Event Payment (US$)
Development Milestone Payments In partial consideration for the rights and licenses granted to Coya hereunder, within ten days after the first achievement of each milestone event in a given Indication set forth in this Section 5.2 (Development Milestone Payments) with respect to a Product (each, a “Development Milestone Event”) by or on behalf of Coya or any of its Affiliates or Sublicensees, Coya shall provide ARScience Bio written notice to ARScience Bio identifying the Development Milestone Event achieved. Upon receipt of any such notice of first achievement of a Development Milestone Event by Coya or its Affiliates or Sublicensees, ARScience Bio will promptly invoice Coya for the applicable Development Milestone Event and Coya will make a milestone payment to ARScience Bio in the amount set forth in this Section 5.2 (Development Milestone Payments) corresponding to such Development Milestone Event (each, a “Development Milestone Payment”) within 45 days of receipt of such invoice. On an Indication-by-Indication basis, each Development Milestone Payment shall be payable only upon the first achievement of the corresponding Development Milestone Event by a Product, in any given Indication for which the Development Milestone Events have not been previously achieved (each such Indication, a “New Indication”). No amounts shall be due for subsequent or repeated achievements of such Development Milestone Event with respect to the same or different Mono Product or Combination Product, as applicable, in such Indication. Accordingly and for clarity, the Development Milestone Payment shall be paid only once, when first achieved by Coya, an Affiliate or a Sublicensee, but no payment shall be due if the same milestone is subsequently achieved by one of Coya, an Affiliate or a Sublicensee. For clarity, the amounts owed in Column (a) below shall be due for the first Combination Product to achieve the Development Milestone Events in a New Indication and the amounts owned in Column (c) below shall be due for the first Mono Product to achieve the Development Milestone Events in a New Indication. Any Combination Product or Mono Product to achieve the Development Milestone Events in a New Indication after the first achievement of the Development Milestone Events as described in the foregoing sentence will cause the amounts in Column (b) with respect to a Combination Product and Column (d) with respect to a Mono Product to be due and payable by Coya upon each such occurrence. If the first Product to achieve a Development Milestone Event in any Indication is a Combination Product, the amounts in Column (a) below shall be due and payable by Coya. If the next Product to achieve a Development Milestone Event in a New Indication is a Mono Product, the amounts in Column (c) below would be due and payable by Coya; provided, that if such next Product to achieve a Development Milestone Event in a New Indication is a Combination Product, the amounts in Column (b) would be due and payable by Coya. By way of example, if a Combination Product achieves IND Acceptance in ALS, and is the first Product to achieve a Development Milestone Event under this Agreement, [***] will be due and payable by Coya. If subsequently a Mono Product achieves IND Acceptance in ALS, no Development Milestone Payments will be due and payable by Coya under this Agreement. However, if subsequently any Combination Product achieves IND Acceptance in Alzheimer’s disease, [***] would be due and payable by Coya.
