Project Implementation Schedule Sample Clauses

Project Implementation Schedule. The whole of the work and services under the Project shall be carried out strictly in accordance with the Scope indicated in this Agreement, and as per the following: a) The provisions in the Naya Raipur Development Plan 2031 including the Development Control Regulation therein and Naya Raipur Urban Design Guidelines including their modifications/ alterations from time to time which are mandatory for any land development or building activity in Naya Raipur. For any other provisions required for Land development/ building activity, the "Chhattisgarh Bhumi Vikas Rules 1984" and National Building code shall be applicable. The lessee shall completely abide by the above mentioned frame works in execution of it obligations under the present agreement.
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Project Implementation Schedule. 6.3.1 The Developer shall in accordance with the terms and conditions of this agreement submit to NRDA for its approval Project Implementation methodology, Construction Milestones and time schedule within 60 days from the date of this agreement 6.3.2 The whole of the work under the project shall be carried out strictly in accordance with the scope indicated in this Agreement, and as per the following: 1) National Building Code 2) Codes & Standards of Bureau of Indian standards
Sample 1Sample 2See All (4)
Project Implementation Schedule. 6.3.1. The whole of the work under the project shall be carried out strictly in accordance with the scope indicated in this Agreement, and as per the following: 1) National Building Code 2) Codes & Standards of Bureau of Indian standards The Developer shall adhere to the above specification given above in same order of preference.
Sample 1Sample 2
Project Implementation Schedule. Note: The City of Missoula/NeighborWorks Montana CDBG-CV project does not involve construction, and CDBG-CV funding is not being used for the Environmental Review Record process. START-UP 1 Submit updated Management Plan, Budget & Schedule for CDBG-CV contract Project Manager (City) August 2022 2 Complete ERR/Submit to MDOC Project Manager: NWMT to complete/City to submit August 2022 3 Secure MDOC Approval of RROF (request for release of funds) September 2022 1 Submit first drawdown request Project Manager (City) Sept/Oct 2022 2 Property Acquisition NWMT/ROC October 2022 1 Project Closeout Begins November 2022 2 Project Completion Report Nov/Dec 2022 3 Audit is conducted/reveiwed October 2023 The City of Missoula received a Community Development Block Grant – CARES Act (CDBG-CV) Program grant from the Montana Department of Commerce (MDOC). The City of Missoula has entered into a sub-recipient agreement with the Montana Homeownership Center dba NeighborWorks Montana to manage loan repayments from this grant award as state CDBG program income. The non-administrative portion of that grant was made available to NWMT who will in turn lend the funds to a non-profit corporation, Old Hellgate Village, Inc, made up of community residents; Old Hellgate Village will use the funds to acquire their property. Old Hellgate Village will repay the loan to NWMT and those payments will become state CDBG Program Income. The terms of the loan agreement are specified in a duly recorded loan document on record at the City of Missoula, Montana. That document is hereby incorporated by reference into this Program Income Plan. The repayments on this loan will be paid into an interest-bearing Program Income fund account, to be used for state CDBG-eligible activities that meet a national objective and primarily benefit LMI households. The NeighborWorks Montana Program Income Plan is designed to stimulate affordable housing activity by assisting private sector organizations, to create or preserve affordable housing for low- and moderate-income people. These funds will be used in situations where a funding gap exists and alternative sources of public and private financing are not adequate to complete the CDBG-eligible activity. These funds are intended to complement conventional housing financing techniques by leveraging funding from other federal and state financing programs and private lending institutions. The Program Income Plan is designed to assist affordable housing projects by m...
Sample 1
Project Implementation Schedule. 8.1 The Project implementation schedule shall be prepared and agreed upon by the Parties, and implemented in a prompt and appropriate manner to serve the Company’s benefits and purposes in accordance with this JV Contract and the Charter.
Sample 1
Project Implementation Schedule. The project is estimated to be completed in one (1) year as shown in the table below. E-Readiness Assessment 1 day Execution of Memorandum of Agreement and Local Ordinance 2 weeks System Orientation and Briefing 1 day Users Training 3 days Preparation for Hosting 2 days Data Build-up 2 weeks Pilot Implementation 3 months Launching and User Acceptance 1 day Implementation monitoring 1 year Evaluation 1 week Project Turnover / Closure
Sample 1
Project Implementation Schedule a. The Concessionaire shall prepare in consultation with the Independent Engineer and submit a Project Implementation Schedule to the Authority before the Compliance Date. The programme shall include the following: i. The order in which the Concessionaire proposes to carry out the Works, internal and external services (including each stage of design, procurement, manufacture, delivery to Project Site) ii. All major events and activities in the production of Construction Documents as per article
Sample 1
AutoNDA by SimpleDocs
Project Implementation Schedule. The detailed schedule developed and maintained by the Contractor that lists all tasks related to the design, development, testing, installation and deployment of the I-15 ML toll collection system as defined in Section 6.2
Sample 1
Project Implementation Schedule a. The Concessionaire shall strictly abide by the Project Implementation Schedule as per the timeframe indicated in Schedule 4 of this Agreement. b. Any deviation from the time frame indicated in the Project Implementation Schedule will be considered as a breach of the conditions of this Agreement.
Sample 1

Related to Project Implementation Schedule

  • Project Implementation The Borrower shall:

  • Construction Schedule The progress schedule of construction of the Project as provided by Developer and approved by District.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

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

  • Completion Schedule 6.1 The proposed schedule for the completion of the Project is presented in “Attachment D” and is made a part hereof. 6.2 ENGINEER shall adhere to all time limits stated in this Agreement or included in any accepted time schedule. All such time limits shall be of the essence to this Agreement. 6.3 In all events the various stages and phases of ENGINEER’S services are to be completed in such sequence and at such times, and with approved or agreed upon time limits, as may be required to assure the timely, continuous, efficient and diligent prosecution of the work and services provided for by this Agreement. 6.4 OWNER may at any time, by written order, make changes within the general scope of the Agreement in the services of work to be performed. If ENGINEER believes that such a change justifies an increase in ENGINEER’S contract time or contract price required to perform the series under this Agreement it must assert such claim in writing within thirty (30) days of receipt of OWNER’S written order giving rise to the claim. No claim for adjustment in the contract time or contract price will be valid if not submitted in accordance with this paragraph. No services for which ENGINEER will charge additional compensation shall be furnished without the written authorization of OWNER. 6.5 ENGINEER shall carry on all work required under this Agreement and maintain the schedule for services during all disputes or disagreements with OWNER. No work shall be delayed or postponed pending resolution of any disputes or disagreements except as permitted in Article 8, or as ENGINEER and OWNER may otherwise agree in writing. 6.6 If the commencement, prosecution or completion of the services under this Agreement, or of the construction of the Project is delayed by any act, omission, delay, neglect or default of ENGINEER, or anyone employed by ENGINEER, or by any damage or acts caused by the negligent acts or omission by ENGINEER, then ENGINEER shall be liable to OWNER for any and all costs, assessments, expense, liabilities or damages caused thereby, in accordance with Section 4.8. 6.7 ENGINEER shall not be responsible for any time delays in the Project, or in the performance of services under this Agreement, to the extent such delays are caused solely by any act, omission, neglect or default of OWNER or anyone employed by OWNER, or by the unreasonable delay of any review agency or utility, or for any delay or damage caused by fire or the combined action of workers and which are in no way chargeable, in whole or in part, to ENGINEER, or by any other conditions or circumstances beyond the control of ENGINEER, its employee, agent, or other persons for whose acts or omissions ENGINEER is responsible. In the event of such delay, ENGINEER shall be entitled to an adjustment in the schedules or agreed time limitations for the performance of services, and this Agreement shall be modified in writing accordingly. Any claim of ENGINEER for adjustment under this cause must be asserted in writing within thirty (30) days from the date of the occurrence of the event giving rise to the claim, unless OWNER grants a further period of time before the date of final payment to ENGINEER. The adjustment of time for the performance of services, as provided in this paragraph, shall be ENGINEER’s sole exclusive right, entitlement and remedy in the event of such delays, and ENGINEER shall have no claim against OWNER for adjustment for increase in costs of performance, or other damages occurred in connection therewith.

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

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

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

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

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