PROJECT DEVELOPMENT TIME SCHEDULE Sample Clauses

PROJECT DEVELOPMENT TIME SCHEDULE. Recipient agrees to the following Project Development Time Schedule: Authorized Award End Date 24 months from the Date of Award Submission of Final Project Progress Report No later than 90 days from the Attachment: EXHIBIT A to ORDINANCE-Cooperation Agreement (Cooperation Agreement-CON/EDA-Revolving Loan Funds) Authorized Award End Date Submission of Final Financial Documents (SF-425) No later than 90 days from the Authorized Award End Date Recipient shall diligently pursue the development and implementation of the project upon receipt of the EDA Award so as to ensure completion within this time schedule, and shall promptly notify EDA in writing of any event that could substantially delay meeting any of the time limits set forth above. Recipient further acknowledges that failure to meet the Project Development Time Schedule may result in EDA pursuing remedies for non-compliance, potentially including termination of the Award, in accordance with the regulations set forth at 2 C.F.R. §§ 200.338–200.342.
AutoNDA by SimpleDocs
PROJECT DEVELOPMENT TIME SCHEDULE. The Recipient agrees to the following Project development time schedule: Time allowed in Financial Assistance Award after EDA Award date: Period of Performance July 1, 2015 to June 30, 2018 Second Funding Period July 1, 2016 to June 30, 2017 Third and Final Funding Period… July 1, 2017 to June 30, 2018 Return of Executed Financial Assistance Award…Due no later than 30 calendar days after receipt of Form CD-450/451 Annual CEDS Performance Report… Due June 30, 2018 GPRA… Due June 30, 2018 Semi-Annual Progress Report. Due January 31, 2018, July 31, 2018 Semi-Annual Financial Reports (Form SF-425)… Due January 31, 2018, July 31, 2018 Authorized Award End Date… June 30, 2018 Final Financial Report (Form SF-425) Due no later than 90 calendar days after the end of the period of performance The Recipient shall diligently pursue the development of the Project so as to ensure completion within this time schedule. Moreover, the Recipient shall promptly notify EDA in writing of any event that could substantially delay meeting any of the proscribed time limits for the Project as set forth above. The Recipient further acknowledges that failure to meet the development time schedule may result in EDA’s taking action to terminate the Award in accordance with the regulations set forth at 2 C.F.R. §§ 200.338 through 200.342, as applicable.

Related to PROJECT DEVELOPMENT TIME SCHEDULE

  • 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 Timeline The Project Timeline establishes a start and end date for each Phase of the Project. Developed during the Initiate & Plan Stage and revised as mutually agreed to, if needed, the timeline accounts for resource availability, business goals, size and complexity of the Project, and task duration requirements.

  • 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 Development a. Collaborate with COUNTY and project clients to identify requirements and develop a project Scope Statement.

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

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

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

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

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

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

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