Traffic Forecast Sample Clauses

Traffic Forecast. Three Forecast Scenarios
AutoNDA by SimpleDocs
Traffic Forecast. 3.6.1 The content of the traffic forecast at each POI/Location shall be as follows:-
Traffic Forecast. 5.1 Customer agrees that performance may be dependent in significant part upon Customer’s forecasts and projections. Company may request Customer to identify such traffic volumes for Service. Customer agrees to provide Company with good faith non-binding forecast of Customer’s expected monthly traffic volume and geographic distribution over a one- month period. If requested by Company, forecasts shall be provided at least thirty (30) days in advance of the forecasted period and updated more frequently if a submitted forecast is no longer accurate.
Traffic Forecast. Retailer shall work closely with their distributors and PSINet to make their best efforts in predicting product demand in their geographic markets and implement a forecasting model based on trending and previous sales for the purpose of allowing PSINet to adequately provide facilities for the increased demand. The Purchaser shall provide this forecasting information to PSINet beginning in the first full month following the date of this agreement. Retailer shall use its best efforts to provide reasonably accurate forecasts, but both parties acknowledge and agree that such forecasts are not binding in any way. 4.
Traffic Forecast. Retailer shall work closely with their distributors and PSINet to make their best efforts in predicting product demand in their geographic markets and implement a forecasting model based on trending and previous sales for the purpose of allowing PSINet to adequately provide facilities for the increased demand. ***
Traffic Forecast. The traffic forecast is based on increasing sessions, increasing page views per session, and increasing orders per session. The bottom line called "sell-through" is the overall dollars in order per user session, an important indicator that should be increasing over time
Traffic Forecast. 3.6.1 The content of the traffic forecast shall be as follows:- - Traffic from ILDO's to MTNL (For each tandem/local exchange of MTNL) - Traffic from MTNL to ILDO's network 3.6.2 Each traffic forecast shall contain - BHCA. - Busy hour Traffic in Erlangs. 3.6.3 Busy hour may vary for various exchanges and it shall be determined from actual traffic figures in the network. 3.6.4 The traffic figures indicated in the forecast shall be reviewed after the implementation of the ILDO's network on monthly basis. Both parties shall provide traffic report on all trunk groups used for interconnection.
AutoNDA by SimpleDocs

Related to Traffic Forecast

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

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

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

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

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

  • Product Sales Subject to Sections 10.3(c) and 10.3(d), Licensee agrees that it will not sell, offer for sale, or assist third parties (including Affiliates) in selling Product except for the sale and offer for sale of (A) TAF Product, TAF Combination Product, TDF Product and TDF Combination Product for use in the Field and in the countries of the TDF-TAF Territory, (B) COBI Product and COBI Combination Product for use in the Field and in the countries of the COBI Territory, and (C) EVG Product, EVG Combination Product and Quad Product for use in the Field and in the countries of the EVG-Quad Territory.‌ (i) Licensee agrees that during the period in which the Patents are valid and enforceable (on a Product-by-Product basis) it will prohibit its Distributors from selling Product (A) to any other wholesaler or distributor, (B) outside the Territory for which Licensee is licensed for sale of such Product pursuant to Section 2.2, or (C) for any purpose outside the Field. (ii) Licensee agrees that it will not administer the TAF Quad to humans, or sell the TAF Quad until Gilead has obtained marketing approval for the TAF Quad from the FDA. Licensee agrees that it will not administer EVG to humans, or sell Products containing EVG until Gilead has obtained marketing approval for an EVG Product from the FDA. Licensee agrees that it will not administer COBI to humans, or sell Products containing COBI until Gilead has obtained marketing approval for a COBI Product from the FDA. Licensee agrees that it will not administer TAF to humans, or sell Products containing TAF until Gilead has obtained marketing approval for a TAF Product from the FDA. If Gilead obtains marketing approval from the FDA for any Quad Product or a Combination Product containing TAF, COBI or EVG (“Approved Combination Product”) prior to obtaining marketing approval for a TAF Product, EVG Product or COBI Product from the FDA, then Licensee will be allowed to administer such Quad Product or such Approved Combination Product to humans, and sell such Quad Product or such Approved Combination Product from and after the date of such marketing approval from the FDA, but will not (A) administer to humans or sell Combination Products containing EVG other than such Quad Product or such Approved Combination Product until Gilead has obtained marketing approval from the FDA for an EVG Product, or (B) administer to humans or sell Combination Products containing COBI other than such Quad Product or such Approved Combination Product until Gilead has obtained marketing approval from the FDA for a COBI Product or (C) administer to humans or sell Combination Products containing TAF other than such Quad Product or such Approved Combination Product until Gilead has obtained marketing approval from the FDA for a TAF Product.

  • Required Vendor Sales Reporting By responding to this Solicitation, you agree to report to TIPS all sales made under any awarded Agreement with TIPS. Vendor is required to report all sales under the TIPS contract to TIPS. If the TIPS Member entity requesting a price from the awarded Vendor requests the TIPS contract, Vendor must include the TIPS Contract number on any communications with the TIPS Member entity. If awarded, you will be provided access to the Vendor Portal. To report sales, login to the TIPS Vendor Portal and click on the PO’s and Payments tab. Pages 3-7 of the Vendor Portal User Guide will walk you through the process of reporting sales to TIPS. Please refer to the TIPS Accounting FAQ’s for more information about reporting sales and if you have further questions, contact the Accounting Team at xxxxxxxxxx@xxxx-xxx.xxx. The Vendor or vendor assigned dealers are responsible for keeping record of all sales that go through the TIPS Agreement and submitting same to TIPS.

  • Contract Year A twelve (12) month period during the term of the Agreement commencing on the Effective Date and each anniversary thereof.

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.

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