Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Process shall be deemed a Specification change. No change in the Specifications shall be implemented by Catalent, whether requested by Client or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Unit Pricing). Catalent shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, Catalent shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. Catalent reserves the right to postpone effecting changes to the Specifications until such time as the parties agree to and execute the required written amendment.
Annual Forecasts As soon as available and in any event no later than 90 days after the end of each Fiscal Year, forecasts prepared by management of the Borrower, in form satisfactory to the Administrative Agent, of balance sheets, income statements and cash flow statements on an annual basis for the Fiscal Year following such Fiscal Year.
Rolling Forecasts Company shall provide Polyzen with a quarterly, rolling, written non-binding twelve (12) month forecast of its purchase requirements for the Products (each, a “Forecast”). Company’s initial Forecast shall be provided to Polyzen on the Effective Date. Company’s initial Purchase Order (the “Initial Purchase Order”) shall reflect the initial three months of the Forecast and shall be subject to the terms and conditions as provided in Section 2.2 of this Agreement. Thereafter, Company shall deliver to Polyzen its updated Forecast by no later than 5:00p.m. (EST) of the last business day of the second (2nd) month of the then current Order Period. For example, since the Effective Date of this Agreement is in July 2017, the initial Forecast delivered on the Effective Date would cover August 2017 through July 2018. Polyzen will use commercially reasonable efforts to maintain sufficient production capacity and redundancy to satisfy Company’s then forecasted requirements for the Products, which, in no event, will equal less than three (3) months of orders plus twenty percent (20%) upside flexibility.
TRUNK FORECASTING 57.1. CLEC shall provide forecasts for traffic utilization over trunk groups. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as facilities and/or equipment are available. Sprint shall make all reasonable efforts and cooperate in good faith to develop alternative solutions to accommodate orders when facilities are not available. Company forecast information must be provided by CLEC to Sprint twice a year. The initial trunk forecast meeting should take place soon after the first implementation meeting. A forecast should be provided at or prior to the first implementation meeting. The semi-annual forecasts shall project trunk gain/loss on a monthly basis for the forecast period, and shall include:
57.1.1. Semi-annual forecasted trunk quantities (which include baseline data that reflect actual Tandem and end office Local Interconnection and meet point trunks and Tandem-subtending Local Interconnection end office equivalent trunk requirements) for no more than two years (current plus one year);
57.1.2. The use of Common Language Location Identifier (CLLI-MSG), which are described in Telcordia documents BR 000-000-000 and BR 000-000-000;
57.1.3. Description of major network projects that affect the other Party will be provided in the semi-annual forecasts. Major network projects include but are not limited to trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities by CLEC that are reflected by a significant increase or decrease in trunking demand for the following forecasting period.
57.1.4. Parties shall meet to review and reconcile the forecasts if forecasts vary significantly.
Changes to Fee Structure In the event of Listing, the Company and the Advisor shall negotiate in good faith to establish a fee structure appropriate for a perpetual-life entity.
Service Changes PBI may modify its Service by giving written notice to you (a “Service Change Notice”), which will state whether the change is material. After receiving a Service Change Notice, if the change is material, you may terminate Service by giving us a termination notice at the address indicated in Section 21 or you may create a case at xxxxxxxxxxx.xxx/xx/xxxxxxx-xx.xxxx (follow the instructions under “how to create a case”).
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.
Changes to the Notice Information Either Party may change this information by giving five Business Days written notice prior to the effective date of the change.
Forecasts Any forecasts provided by DXC shall not constitute a commitment of any type by DXC.
Changes to Services The Parties acknowledge and agree that there will be changes to the scope of the Services during the Contract Period. The Customer may amend the Stories that are comprised within the Minimum Marketable Features of a Release at any time during the Release at no additional charge and without adopting the Change Control Procedure set out in Clause 28 above provided that: the Customer shall not be entitled to make any changes to the Stories that form the subject of a Sprint following the mutual agreement by the Parties of the Sprint Plan for that Sprint; new Stories and/or changes to existing Stories may only be introduced if: existing Stories with an equivalent number of Story Points are removed; or existing Stories are reduced in size by the equivalent number of Story Points, such that the total number of Story Points for the Release remains constant throughout the Release. The Supplier shall consider any request by the Customer to increase the number of Story Points for a Release, and may, subject to the Change Control Procedure set out at Clause 28, agree to such request.
