Project Schedule Joint Review and Acceptance Sample Clauses

Project Schedule Joint Review and Acceptance a. The Project Schedule and successive updates or revisions thereof are for Contractor’s use in managing the Work. The Project Schedule is for the information of City and to demonstrate Contractor has complied with requirements for planning the Work. City’s acceptance of a Schedule, Schedule update(s) or revisions constitutes City’s agreement to coordinate its own activities with Contractor’s activities, as shown on the schedule. b. Within fourteen (14) calendar days of receipt of Contractor’s proposed Project Schedule, City shall evaluate the Schedule for compliance with this specification and notify Contractor of its findings. If City requests a revision or justification, Contractor shall provide satisfaction to City within seven (7) calendar days. If Contractor submits a Project Schedule for acceptance, based on a sequence of work not shown in the Plans, Contractor shall notify City in writing of said sequence of work, separate from the Schedule submittal. c. City's review and acceptance of Contractor's Project Schedule only is for conformance to the requirements of the Contract Documents. Review and acceptance by City of Contractor's Project Schedule does not relieve Contractor of any of its responsibility for the Project Schedule, Contractor's ability to meet interim milestone dates (if so specified) or meeting the Contract completion date, nor does such review and acceptance expressly or by implication warrant, acknowledge or admit the reasonableness of the logic, durations, manpower or equipment loading of Contractor's Project Schedule. In the event Contractor fails to define any element of Work, activity or logic and City’s review does not detect this omission or error, such omission or error, whether or when discovered by Contractor or City, shall be corrected by Contractor at the next monthly schedule update and shall not affect the Project or Contract completion date. d. Acceptance of the Project Schedule, or update and/or revision thereto, does not indicate any approval of Contractor’s proposed sequences and duration. e. Acceptance by City of the Project Schedule or updated Project Schedule which exceeds contractual time does not alleviate Contractor from meeting the contractual completion date. f. Acceptance of a Project Schedule update or revision indicating early or late completion does not constitute City’s consent to any changes, alter the terms of g. Contractor’s scheduled dates for completion of any activity or of the entire Work do not ...
Sample 1
AutoNDA by SimpleDocs
Project Schedule Joint Review and Acceptance. 3.10.8.1 The Project Schedule and successive updates or revisions thereof are for Contractor’s use in managing the Work. The Project Schedule is for the information of Owner and to demonstrate that Contractor has complied with requirements for planning the Work. Owner’s acceptance of a Schedule and Schedule updates or revisions constitutes Owner’s agreement to coordinate its own activities with Contractor’s activities, as shown on the schedule. 3.10.8.2 Within fifteen (15) calendar days of receipt of Contractor’s proposed Project Schedule, Owner shall evaluate the Schedule for compliance with this specification and notify Contractor of its findings. If Owner requests a revision or justification, Contractor shall provide satisfaction to Owner within seven (7) calendar days. If Contractor submits a Project Schedule for acceptance, based on a sequence of work not shown in the plans, Contractor shall notify Owner in writing of said sequence of work, separate from the Schedule submittal. 3.10.8.3 Owner's review and acceptance of Contractor's Project Schedule only is for conformance to the requirements of the Contract Documents. Review and acceptance by Owner of Contractor's Project Schedule does not relieve Contractor of any of its responsibility for the Project Schedule, Contractor's ability to meet interim milestone dates (if so specified) or meeting the Contract completion date, nor does such review and acceptance expressly or by implication warrant, acknowledge or admit the reasonableness of the logic, durations, manpower or equipment loading of Contractor's Project Schedule. In the event Contractor fails to define any element of Work, activity or logic and Owner’s review does not detect this omission or error, such omission or error, whether or when discovered by Contractor or Owner, shall be corrected by Contractor at the next monthly schedule update and shall not affect the Project or Contract completion date. 3.10.8.4 Acceptance of the Project Schedule, or update and/or revision thereto, does not indicate any approval of Contractor’s proposed sequences and duration. 3.10.8.5 Acceptance by Owner of the Project Schedule or updated Project Schedule which exceeds contractual time does not alleviate Contractor from meeting the contractual completion date. 3.10.8.6 Acceptance of a Project Schedule update or revision indicating early or late completion does not constitute Owner’s consent to any changes, alter the terms of the Contract, waive either Contractor’...
Sample 1

Related to Project Schedule Joint Review and Acceptance

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Project Completion Report At the completion of construction and once a Project is placed in service, the Subrecipient must submit a Project Completion Report that includes the total number of units built and leased, affordable units built and leased, DR-MHP units built and leased, an accomplishment narrative, and the tenants names, demographics and income for each DR-MHP unit.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Work Order (s) means a detailed scope of work for a Service required by Transnet, including timeframes, Deliverable, Fees and costs for the supply of the Service to Transnet, which may be appended to this Agreement from time to time.

  • Contract Task Order A- E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The County Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with County Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by County Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, County Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned County Project Manager within the timeframe indicated in the CTO or as directed by County Project Management staff.

  • Contract Schedule The information set forth in the Contract Schedule is true and correct.

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives. C.1. <Title> Deliverable 1

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