Notice of Development Project Status Sample Clauses

Notice of Development Project Status. Concurrently with the conversion of a Research Program into a Development Project, Regulus will notify each Licensor of such conversion and whether or not Regulus will continue to pursue the Development and Commercialization of such newly designated Development Project.
AutoNDA by SimpleDocs

Related to Notice of Development Project Status

  • Notice of Developments Each Party will give prompt written notice to the other of any material adverse development causing a breach of any of its own representations and warranties in Section 3 and Section 4 above. No disclosure by any Party pursuant to this Section 5(f), however, shall be deemed to amend or supplement the Disclosure Schedule or to prevent or cure any misrepresentation, breach of warranty, or breach of covenant.

  • NOTICE OF DELAYS Except as otherwise provided under this Contract, when either party has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this Contract, that party shall, within one (1) business day, give notice thereof, including all relevant information with respect thereto, to the other party.

  • Completion of Development 7.4.1 Upon the completion of the whole development or complete phases of the development, Council may review this Agreement, in whole or in part, and may: (a) retain the Agreement in its present form; (b) negotiate a new Agreement; (c) discharge this Agreement; or (d) for those portions of the development which are completed, discharge this Agreement and apply appropriate zoning pursuant to the Municipal Planning Strategy and Land Use By-law for Halifax Peninsula as may be amended from time to time.

  • Notice of Delay 12.1. When anything delays or threatens to delay the timely performance of the Purchase Order, Supplier must immediately provide written notice to Buyer in writing of all relevant information, including but not limited to the reasons for the potential delay and Supplier’s short-term and long-term mitigation actions.

  • Design Development Phase INDICATE IN STATEMENT OF WORK “NOT APPLICABLE” IF SECTION IS NOT APPLICABLE 1.1.6.1. The ARCHITECT/ENGINEER shall prepare from the approved Schematic Design Studies, the Design Development Documents consisting of drawings (including at least architectural, landscaping, civil, structural, mechanical and electrical plans, building sections; and finish schedule), outline specifications following the Construction Specification Institute "CSI" Format and other necessary documents to fix and describe the size and character of the entire Project as to its site, structural, mechanical, and electrical systems, materials and other such essentials as may be appropriate, for and until approved by the State. 1.1.6.2. The ARCHITECT/ENGINEER shall conduct meetings with the State, Efficiency Vermont, and relevant members of the design team, to review the Design Development Documents for the purposes of furthering the energy efficiency objectives of the Project. 1.1.6.3. The ARCHITECT/ENGINEER shall prepare for the State a revised accounting of how the Project is responding to LEED criteria. 1.1.6.4. The ARCHITECT/ENGINEER shall submit to the State a revised Statement of Probable Construction Cost based thereon for and until approved by the State.

  • Design Development Documents See Section 2, Part 1, Article 2.1.5.

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

  • Development Phase contractual phase initiated with the approval of ANP for the Development Plan and which is extended during the Production Phase while investments in xxxxx, equipment, and facilities for the Production of Oil and Gas according to the Best Practices of the Oil Industry are required.

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

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Generator Deactivation Solution, the ISO shall tender to the Developer that proposed the selected transmission Generator Deactivation Solution a draft Development Agreement, with draft appendices completed by the ISO to the extent practicable, for review and completion by the Developer. The draft Development Agreement shall be in the form of the ISO’s Commission-approved Development Agreement for its reliability planning process, which is in Appendix C in Section 31.7 of Attachment Y of the ISO OATT, as amended by the ISO to reflect the Generator Deactivation Process. The ISO and the Developer shall finalize the Development Agreement and appendices as soon as reasonably practicable after the ISO’s tendering of the draft Development Agreement. For purposes of finalizing the Development Agreement, the ISO and Developer shall develop the description and dates for the milestones necessary to develop and construct the selected project by the required in-service date identified in the Generator Deactivation Assessment, including the milestones for obtaining all necessary authorizations. Any milestone that requires action by a Connecting Transmission Owner or Affected System Operator identified pursuant to Attachment P of the ISO OATT to complete must be included as an Advisory Milestone, as that term is defined in the Development Agreement. If the ISO or the Developer determines that negotiations are at an impasse, the ISO may file the Development Agreement in unexecuted form with the Commission on its own, or following the Developer’s request in writing that the agreement be filed unexecuted. If the Development Agreement is executed by both parties, the ISO shall file the agreement with the Commission for its acceptance within ten (10) Business Days after the execution of the Development Agreement by both parties. If the Developer requests that the Development Agreement be filed unexecuted, the ISO shall file the agreement at the Commission within ten (10) Business Days of receipt of the request from the Developer. The ISO will draft, to the extent practicable, the portions of the Development Agreement and appendices that are in dispute and will provide an explanation to the Commission of any matters as to which the parties disagree. The Developer will provide in a separate filing any comments that it has on the unexecuted agreement, including any alternative positions it may have with respect to the disputed provisions. Upon the ISO’s and the Developer’s execution of the Development Agreement or the ISO’s filing of an unexecuted Development Agreement with the Commission, the ISO and the Developer shall perform their respective obligations in accordance with the terms of the Development Agreement that are not in dispute, subject to modification by the Commission. The Connecting Transmission Owner(s) and Affected System Operator(s) that are identified in Attachment P of the ISO OATT in connection with the selected transmission Generator Deactivation Solution shall act in good faith in timely performing their obligations that are required for the Developer to satisfy its obligations under the Development Agreement.

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