Preparation of Tolling Method Gain Forecasts Sample Clauses

Preparation of Tolling Method Gain Forecasts. The independent firm shall prepare two forecasts of annual Net Project Cash Flows for the period from the date of implementation of the Tolling Method Change through the end of the Term. The two forecasts shall use the same formulas, data, economic indicators, inputs, and assumptions, except that the first forecast shall assume that the Tolling Method Change is not implemented (the “first forecast”) and that the second forecast shall assume that the Tolling Method Change is implemented (the “second forecast”). The forecasts shall be based upon forecasts of traffic and Toll Revenues made at that time, as opposed to assumptions included in Developer’s Proposal. The second forecast shall be supported by a traffic and revenue study and analysis showing the projected effects of the Tolling Method Change relative to the first forecast.
AutoNDA by SimpleDocs

Related to Preparation of Tolling Method Gain Forecasts

  • Billing Method 2.6.1 To receive payment for services rendered pursuant to this contract the Contractor shall submit a fully completed invoice for work previously performed to: 2.6.2 At a minimum, the invoice shall detail the following information: 2.6.2.1 Unique invoice number; 2.6.2.2 Contractor’s name, address, and telephone number; 2.6.2.3 Date of invoice and/or billing period; 2.6.2.4 Applicable Contract No.;

  • Accounting Method For both financial and tax reporting purposes, the books and records of the Company shall be kept on the accrual method of accounting applied in a consistent manner and shall reflect all Company transactions and be appropriate and adequate for the Company’s business.

  • Accounting Methods Implement or adopt any change in its accounting principles, practices or methods, other than as may be required by generally accepted accounting principles.

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

  • Change in Accounting Method Neither Company nor any of its Subsidiaries has agreed to make, nor is it required to make, any material adjustment under Section 481(a) of the Code or any comparable provision of state, local, or foreign Tax Laws by reason of a change in accounting method or otherwise.

  • Accounting Methods and Financial Records Maintain a system of accounting, and keep such books, records and accounts (which shall be true and complete in all material respects) as may be required or as may be necessary to permit the preparation of financial statements in accordance with GAAP and in compliance with the regulations of any Governmental Authority having jurisdiction over it or any of its properties.

  • Rolling Forecasts No later than ten (10) days of the Commencement Date, the Client shall provide Patheon with a written non-binding 18 month forecast of the volume of the Drug Product that the Client then anticipates will be required to be produced and delivered to the Client during each month of that 18 month period. Such forecast will be updated by the Client monthly on a rolling 18 month basis and updated forthwith upon the Client determining that the volumes contemplated in the most recent of such forecasts has changed by more than 20%. The most recent 18 month forecast shall prevail.

  • 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 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. (ii) The remainder of the Forecast shall set forth Buyer’s best estimate of its Product production and supply requirements for the remainder of the Forecast period. Each portion of such Forecast that is not deemed to be a Firm Order shall not be deemed to create a binding obligation on Buyer to purchase and take delivery of Products nor a binding obligation of Seller to deliver Products, except as otherwise provided in Section 2.2(f). (iii) Forecast and Purchase Orders shall be in full Standard Manufacturing Batches. If a Product has multiple SKUs, then the composite of the forecasted SKU must equate to the Standard Manufacturing Batch. One Purchase Order shall be issued for each full Standard Manufacturing Batch of Product and contain the required information set forth in Section 2.2(e) hereof.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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