Rolling Requirement Forecasts Clause Samples

The Rolling Requirement Forecasts clause establishes a process by which one party regularly provides updated projections of its anticipated needs or requirements to the other party. Typically, this involves submitting forecasts on a periodic basis—such as monthly or quarterly—that outline expected quantities or services for upcoming periods. This mechanism enables suppliers or service providers to plan production, inventory, or resource allocation more effectively, thereby reducing the risk of shortages or overstock and ensuring smoother operations for both parties.
Rolling Requirement Forecasts. Prior to the beginning of each calendar month (M1) during the Term, Codexis shall provide Arch with a written forecast of Codexis’ expected requirements for Product during the following twenty-four (24) months broken down by months (M1–M24), and which shall include projected order dates, quantities, and shipping dates (“Rolling Requirement Forecast”). In each Rolling Requirement Forecast, the terms set forth for (a) the first three (3) months (months M1–M3) shall be firm orders binding on Codexis; provided that Codexis shall have the right to increase or decrease the firm order for month M3 by twenty percent (20%) in the subsequent Rolling Requirement Forecast; and (b) the subsequent twenty-one (21) months (months M4–M24) shall be non-binding estimates. In the event Codexis requests additional quantity of Product in excess of the amount set forth for the first two (2) months, or in excess of twenty percent (20%) more than the amount set forth for the third (3rd) month, of the Rolling Requirement Forecast, Arch shall use commercially reasonable efforts to deliver such quantities and shall promptly provide Codexis written notice in the event that Arch will not able to delivery such quantities.
Rolling Requirement Forecasts. On a Product-by-Product basis, at least thirty (30) days prior to the beginning of each Calendar Quarter, Arch shall provide Codexis a written forecast of Arch’s expected requirements for each of the Codexis Enzyme(s) based on Arch’s good faith projected sales of Products, during the following twelve (12) calendar months broken down by calendar months, and which shall include projected order dates, quantities, shipping dates, and quality standards (as applicable) (each, an “Rolling Requirement Forecast”).

Related to Rolling Requirement Forecasts

  • Forecasting Requirements 19.5.1 The Parties shall exchange technical descriptions and forecasts of their Interconnection and traffic requirements in sufficient detail necessary to establish the Interconnections necessary for traffic completion to and from all Customers in their respective designated service areas.

  • 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.

  • Child Abuse Reporting Requirement Grantee will: a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements. c. use the System Agency Child Abuse Reporting Form located at ▇▇▇▇▇://▇▇▇.▇▇▇▇.▇▇▇▇▇.▇▇.▇▇/Contact Us/report abuse.asp as required by the System Agency. d. retain reporting documentation on site and make it available for inspection by the System Agency.

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇.▇▇▇. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇.▇▇▇. (2) The Contractor shall report the following information pursuant to paragraph (d)(1) of this clause (i) Within one business day from the date of such identification or notification: the contract number; the order number(s), if applicable; supplier name; supplier unique entity identifier (if known); supplier Commercial and Government Entity (CAGE) code (if known); brand; model number (original equipment manufacturer number, manufacturer part number, or wholesaler number); item description; and any readily available information about mitigation actions undertaken or recommended. (ii) Within 10 business days of submitting the information in paragraph (d)(2)(i) of this clause: any further available information about mitigation actions undertaken or recommended. In addition, the Contractor shall describe the efforts it undertook to prevent use or submission of covered telecommunications equipment or services, and any additional efforts that will be incorporated to prevent future use or submission of covered telecommunications equipment or services.

  • Staffing Requirements Licensee will be in full compliance with the main studio staff requirements as specified by the FCC.