Schedule Progress Updates Sample Clauses

Schedule Progress Updates. The Contractor shall update the Current Baseline Schedule on a monthly basis to provide Schedule Progress Updates. These Schedule Progress Updates shall not constitute a modification of the Current Baseline Schedule. The purpose of Schedule Progress Updates shall be to accurately document the progress of the Work to date and to correct the schedule to accurately reflect the Contractor’s current plan for the timely completion of the Work. The Schedule Progress Updates shall not contain significant changes such as addition of activities, deletion of activities, significant changes to logic, changes to activity descriptions, significant changes to activity durations; such changes will result in rejection of the schedule. Any significant changes shall be submitted as a proposed Revised Baseline for the Authority approval. The Schedule Progress Updates shall also be used to record progress for payment purposes and to reflect how the Work is being performed. Submission of and obtaining either a “Statement of No Objection”, or a “Statement of No Objection With Comments” on the submitted Schedule Progress Update is a condition precedence for a full payment due under a monthly invoice. The Contractor failure to achieving either a “Statement of Non Objection” or a “Statement of No Objection With Comments” status on a Schedule Progress Update will result in 10% withholding on the payment due to the Contractor. Such withholding will only be released to the Contractor once a “Statement of No Objections” or a “Statement of No Objection With Comments” is achieved on the schedule. Schedule Progress Updates shall never be used as the basis for any adjustment in the Completion Deadlines. Any acceptance of the Schedule Progress Update by the Authority, either expressed or implied, shall only apply to the issue of progress and not to any issue of acceptability or accuracy of the Schedule Progress Update for use as a basis for measuring adjustments in Completion Deadlines. The Schedule Progress Update submittal shall be due with Contractor’s invoice for payment and shall be a prerequisite to payment by the Authority.
Sample 1
AutoNDA by SimpleDocs
Schedule Progress Updates. The Contractor shall update the Current Baseline Schedule on a monthly basis. This shall not constitute a modification of the Current Baseline Schedule. The purpose of Schedule Progress Updates shall be to accurately document the progress of the Work to-date and to correct the schedule to accurately reflect the Contractor’s current plan for the timely completion of the Work. Schedule Progress Updates shall be used to record progress for payment purposes and to reflect how the Work is being performed. EXECUTION VERSION Schedule Progress Updates shall never be used as the basis for any adjustment in the Completion Deadlines. Any acceptance of the Schedule Progress Update by the Authority, either expressed or implied, shall only apply to the issue of progress and not to any issue of acceptability or accuracy of the Schedule Progress Update for use as a basis for measuring adjustments in Completion Deadlines. The Schedule Progress Update submittal shall be due with Contractor’s invoice for payment, and shall be a prerequisite to payment by the Authority.
Sample 1

Related to Schedule Progress Updates

  • Progress Update Information included with the annual Data Access Request (DAR) renewal or Closeout summarizing the analysis of controlled-access datasets obtained through the DAR and any publications and presentations derived from the work.

  • Schedule Updates the Contractor agrees to maintain the Work duration schedule updates on an ongoing basis and, when the County requests it, include the updates in its payment request. The Contractor may be required to submit a narrative report with each monthly update which shall include a description of current and anticipated problem areas, delaying factors and their impact, and an explanation of corrective action taken or proposed. Failure to do so may be considered a material breach of the Contract. Any additional or unanticipated costs or expense required to maintain the schedules shall be solely the Contractor’s obligation and Contractor agrees not to charge the County.

  • Salary Schedule Progression Employees shall progress from step to step in salary grade on the basis of satisfactory job performance based upon established standards of performance. Seasonal employee's initial anniversary date shall be established after being in pay status for two thousand eighty (2,080) hours. Such date shall then be used for annual performance evaluation and step progression consideration. When an employee's anniversary date falls on any day from the first day of a pay week through Wednesday of the pay week, the employee's merit increase shall be effective as of the first day of the pay week within which the anniversary date falls. Otherwise, the merit increase shall be effective on the first day of the next pay week. Grievances arising from the denial of merit increases shall not be arbitrable under this Agreement but shall be processed as follows:

  • PROGRESS SCHEDULE The Contractor, within ten (10) working days of receiving notice of the award of the contract, shall prepare and submit for the State's and Architect's information an estimated progress schedule for the Work. The progress schedule shall be related to the entire Project to the extent required by the Contract Documents, and shall provide for expeditious and practicable execution of the Work.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • Contractor’s Submittals The Contract shall submit with reasonable promptness consistent with the Work Project Schedule and in orderly sequence all Shop Drawings, Samples, or other information required by the Contract Documents, or subsequently required by Change Order. Prior to submitting, the Contractor shall review each submittal for compliance with the Contract Documents and certify its approval by an approval stamp affixed to each copy. Submittal data presented without the Contractor’s certification will be returned without review or comment, and any delay resulting from such certification is the Contractor's responsibility.

  • Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.

  • APPENDIX F Appendix F, HBITS Processes and Forms, attached hereto, is hereby expressly made a part of this Contract as fully as if set forth at length herein. The Parties agree that the processes and forms set forth in this appendix may be updated as necessary, such as to facilitate the development of a web portal or other automated systems. OGS reserves the right to make changes to these processes and forms without seeking the prior written approval of the Department of Law or OSC, however, OGS agrees that any such changes shall comply with the terms and conditions of this Contract and not be material or substantive in nature. The Parties agree that detailed instructions for the completion of these forms shall be set forth in the “How to Use” document presented on the OGS web site or as part of the web portal or other automated system. Form 8, Monthly Report, shall be submitted electronically in Microsoft Excel 2007 or higher format, which will be separately provided by OGS.

  • Work Progress Schedule Refer to Special Conditions and Division 1 General Administration Specifications for additional schedule requirements. Unless indicated otherwise in those documents, Contractor shall submit to the ODR and the A/E its initial Work Progress Schedule for the Work in relation to the entire Project not later than twenty-one (21) days after the effective date of the Notice to Proceed. Unless otherwise indicated in the Contract Documents, the Work Progress Schedule shall be based upon a computerized Critical Path Method (CPM) with full reporting capability. This initial schedule shall indicate the dates for starting and completing the various aspects required to complete the Work, including mobilization, procurement, installation, testing, inspection, and acceptance of all the Work of the Contract. When acceptable to the Owner, the initially accepted schedule shall be the Baseline Schedule for comparison to actual conditions throughout the contract duration.

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