Monitoring Schedules/Delivery Dates/Budgets Sample Clauses

Monitoring Schedules/Delivery Dates/Budgets. The consultant shall describe the procedures and company reports or information to be used by the Project Manager and management to properly monitor the project and track the status of the following: • Schedules and deliverables including corrective action to be taken if the consultant falls behind schedule. • Budgets including corrective action to be taken if the project will not be completed within budget.
AutoNDA by SimpleDocs

Related to Monitoring Schedules/Delivery Dates/Budgets

  • Initial Forecasts/Trunking Requirements Because Verizon’s trunking requirements will, at least during an initial period, be dependent on the Customer segments and service segments within Customer segments to whom CSTC decides to market its services, Verizon will be largely dependent on CSTC to provide accurate trunk forecasts for both inbound (from Verizon) and outbound (to Verizon) traffic. Verizon will, as an initial matter, provide the same number of trunks to terminate Reciprocal Compensation Traffic to CSTC as CSTC provides to terminate Reciprocal Compensation Traffic to Verizon. At Verizon’s discretion, when CSTC expressly identifies particular situations that are expected to produce traffic that is substantially skewed in either the inbound or outbound direction, Verizon will provide the number of trunks CSTC suggests; provided, however, that in all cases Verizon’s provision of the forecasted number of trunks to CSTC is conditioned on the following: that such forecast is based on reasonable engineering criteria, there are no capacity constraints, and CSTC’s previous forecasts have proven to be reliable and accurate.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Delivery Schedule The scheduled months of delivery of the Aircraft are listed in the attached Table 1. Exhibit B describes certain responsibilities for both Customer and Boeing in order to accomplish the delivery of the Aircraft.

  • Requesting Price Increase/Required Documentation Contractor must submit a written notification at least thirty (30) calendar days prior to the requested effective date of the change, setting the amount of the increase, along with an itemized list of any increased prices, showing the Contractor’s current price, revised price, the actual dollar difference and the percentage of the price increase by line item. Price change requests must include H-GAC Forms D Offered Item Pricing and E Options Pricing, or the documentation used to submit pricing in the original Response and be supported with substantive documentation (e.g. manufacturer's price increase notices, copies of invoices from suppliers, etc.) clearly showing that Contractor's actual costs have increased per the applicable line item bid. The Producer Price Index (PPI) may be used as partial justification, subject to approval by H-GAC, but no price increase based solely on an increase in the PPI will be allowed. This documentation should be submitted in Excel format to facilitate analysis and updating of the website. The letter and documentation must be sent to the Bids and Specifications manager, Xxxxxxx Xxxxxx, at Xxxxxxx.Xxxxxx@x-xxx.xxx Review/Approval of Requests If H-GAC approves the price increase, Contractor will be notified in writing; no price increase will be effective until Contractor receives this notice. If H-GAC does not approve Contractor’s price increase, Contractor may terminate its performance upon sixty (60) days advance written notice to H-GAC, however Contractor must fulfill any outstanding Purchase Orders. Termination of performance is Contractor’s only remedy if H-GAC does not approve the price increase. H-GAC reserves the right to accept or reject any price change request.

  • DELIVERY SCHEDULES In accordance with the "Non-State Agencies Participation in Centralized Contracts” and “Extension of Use” clauses herein, this Contract is extended to local governments, political subdivisions and others authorized by law as well as State agencies. The Delivery Schedules (based on Requirement Letter RL182) are available as a guide to indicate proposed delivery points and estimated annual requirements. Delivery Schedules may be revised or clarified as necessary. Any specific questions regarding the site conditions should be directed to the end-user at the telephone number shown on the Delivery Schedule. The Delivery Schedules are available upon request. Contractors shall be obligated to deliver under the Contract to any State agency which places a purchase order under the Contract, whether or not such delivery location is identified in the Delivery Schedules. Any political subdivision or other non-State entity which has not filed a requirement with OGS as of the date of the bid opening shall be eligible to receive deliveries at Contractor's option only, upon placement of a valid purchase order to the Contractor's address as indicated in the award. Contracts created by OGS in response to receipt of Filed Requirements are considered to be binding. At Contractor's request, Contractor will be advised in writing regarding political subdivisions or other Non-State entities which have filed on a timely basis but do not appear on the Delivery Schedule. Where “Standby” is indicated in the Delivery Schedule, this reflects those facilities which normally use a fuel supply (i.e. natural gas) other than fuel oil and will only use fuel oil when alternate fuel is unavailable.

  • Alternate Work Schedules Workweeks and work shifts of different numbers of hours may be established for overtime-eligible employees by the Employer in order to meet business and customer service needs, as long as the alternate work schedules meet federal and state law. When there is a holiday, employees may be required to switch from their alternate work schedules to regular work schedules.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Operating Schedule Purchaser shall, be- fore commencing operations, provide in writing an annual Operating Schedule of anticipated major activities and needs for logging Included Timber, such as logging, road maintenance, Scaling, and road construction, including construction staking under B5.212 and material delivery under B5.22. Upon reasonable notice to Forest Service, such schedule shall be subject to modifications necessi- xxxxx by weather, markets, or other unpredictable circum- stances. Subject to B6.6 and when the requirements of B6.66 are met, Purchaser’s Operations may be conducted out- side Normal Operating Season. “Normal Operating Sea- son” is the period(s) beginning and ending on the dates stated in A16 of any year.

  • DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

Time is Money Join Law Insider Premium to draft better contracts faster.