Modification of Development Plan Sample Clauses

Modification of Development Plan. Licensee may modify the then applicable Development Plan from time to time to improve Licensee’s ability to meet the Development Milestones.
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs
Modification of Development Plan. Should Client want to change a Development Plan or to include therein additional services to be provided by CBSW, Client may propose to CBSW an amendment to such Development Plan with the desired changes or additional services ("Change Order"). If CBSW determines that it has the resources and capabilities to accommodate such Change Order, CBSW will prepare a modified version of the applicable Development Plan reflecting such Change Order and will submit such modified Development Plan to Client for review and comment. The modified Development Plan shall be binding on the Parties only if signed by both Parties, whereafter such modified version of the Development Plan will be deemed to have replaced the prior version of the Development Plan.
Sample 1Sample 2Sample 3See All (6)
Modification of Development Plan. If, as the results of Development dictate, REPLIDYNE intends to substantially modify the Development Plan, REPLIDYNE shall notify DSP of such intention and the Parties shall promptly discuss, in good faith, such modification; provided, however, that if the Parties are unable to reach an agreement within sixty (60) days, REPLIDYNE shall have the right to make the final decision with respect to any such modifications.
Sample 1Sample 2
Modification of Development Plan. The Development Plan may be modified by mutual agreement as necessary. Modifications of LESSEE’s development plan may be made through the written approval of the KPB Mayor. A modified development plan shall be submitted by LESSEE to KPB in writing at least 60 days prior to anticipated modification of activities. Approved modifications shall be attached to this lease and effective upon the Mayor’s written approval.
Sample 1
Modification of Development Plan. If either Party wishes to modify or add to any activities or other aspects of the Development Plan or if Almirall wishes to conduct any Development in the Field in the Territory outside the Development Plan, then such Party shall propose such modifications or additions to the JDC, which shall review the proposal and make a recommendation to the JSC to amend the Development Plan in accordance with this Section 5.1.3. No material modification to the Development Plan shall become effective unless and until approved by the Parties and formalized as an amendment to the Agreement and to the Development Plan, provided that amendments or supplements to EXHIBIT D-3 with respect to Development of the Product in the Territory for moderate-to-severe atopic dermatitis may be approved by the JSC in accordance with Section 9.6.5.
Sample 1
Modification of Development Plan. Microbot may make, from time to time, such adjustments to the then applicable Development Plan as Microbot believes, in its good faith judgment, are needed or desirable in order to ensure Microbot’s ability to achieve the Development Milestones. Notwithstanding the aforesaid, Microbot shall not be entitled to change the Development Milestones or the time frames for achieving the Development Milestones without the prior written consent of TRDF thereto, except in accordance with the provisions of Section 4.5.
Sample 1

Related to Modification of Development Plan

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

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Concession Area, including its abandonment.

  • Development Agreement As soon as reasonably practicable following the ISO’s selection of a transmission Short-Term Reliability Process Solution, the ISO shall tender to the Developer that proposed the selected transmission Short-Term Reliability Process 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 Short-Term Reliability 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 STAR or 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 Short-Term Reliability Process 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.

  • Commencement of Development 5.3.1 In the event that development on the Lands has not commenced within five (5) years from the date of registration of this Agreement at the Registry of Deeds or Land Registry Office, as indicated herein, the Agreement shall have no further force or effect and henceforth the development of the Lands shall conform with the provisions of the Land Use By-law. For the purpose of this section, commencement of development shall mean issuance of a Mobile Home Park Construction Permit. 5.3.2 For the purpose of this section, Council may consider granting an extension of the commencement of development time period through a resolution under Section 4.1 of this Agreement, if the Municipality receives a written request from the Developer at least sixty (60) calendar days prior to the expiry of the commencement of development time period.

  • Commercialization Plan At such times as the JGC will deem appropriate, the JGC will direct the Parties to mutually prepare a Worldwide Commercialization Plan, and the JGC will review and approve such initial Worldwide Commercialization Plan. Thereafter, the JGC will have one or the other Party (or both) update the Worldwide Commercialization Plan each calendar year, and the JGC will review and approve any such update or any other amendment to the Worldwide Commercialization Plan. Notwithstanding anything in this CCPS Agreement to the contrary, the Parties acknowledge and agree that (i) Bluebird may decline to perform any Commercialization activity proposed to be conducted by Bluebird in the Worldwide Commercialization Plan (other than Manufacturing of Vectors and associated Payloads), and (ii) the Worldwide Commercialization Plan will not include, and Bluebird will have no obligation to perform, any such Commercialization activity that Bluebird has declined to perform, provided that once Bluebird has agreed to perform a Commercialization activity, it will be obligated to perform, and cannot decline to perform, such activity. In addition, either Party may request at any time that the JGC consider and approve other updates to the Worldwide Commercialization Plan. Further: (a) The JGC will set the required form and contents of the Worldwide Commercialization Plan. The Worldwide Commercialization Plan will reflect a singular marketing and sales approach worldwide, and will specify, among other things, the number of sales reps in the U.S. for each Party, allocation of regions in the U.S. for each Parties’ sales force, creation of marketing materials, planning for conferences, and other marketing activities. CERTAIN CONFIDENTIAL PORTIONS OF THIS EXHIBIT WERE OMITTED AND REPLACED WITH “[***]”. A COMPLETE VERSION OF THIS EXHIBIT HAS BEEN FILED SEPARATELY WITH THE SECRETARY OF THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO AN APPLICATION REQUESTING CONFIDENTIAL TREATMENT PURSUANT TO RULE 406 PROMULGATED UNDER THE SECURITIES ACT OF 1933, AS AMENDED. (b) Neither Party (itself or by or through any others, including any Affiliates or Sublicensees) will take any material action regarding the Commercialization of Licensed Product unless described in the Worldwide Commercialization Plan or approved by the JGC. (c) All Commercialization of Licensed Product for U.S. Administration will be conducted under the supervision of the JGC and as part of the U.S. Development & Commercialization Program. (d) Celgene will have final decision making authority for all Commercialization activities worldwide, including timing of launch and pricing and the Worldwide Development Plan.

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

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Collaboration Agreement The Collaboration Agreement shall not have been terminated in accordance with its terms and shall be in full force and effect.

  • Joint Development If joint development is involved, the Recipient agrees to follow the latest edition of FTA Circular 7050.1, “Federal Transit Administration Guidance on Joint Development.”

  • MODIFICATION OF CONTRACT TERMS The terms and conditions set forth in the Contract shall govern all transactions by Authorized User(s) under this Contract. The Contract may only be modified or amended upon mutual written agreement of the Commissioner and Contractor. The Contractor may, however, offer Authorized User(s) more advantageous pricing, payment, or other terms and conditions than those set forth in the Contract. In such event, a copy of such terms shall be furnished to the Authorized User(s) and Commissioner by the Contractor at the time of such offer. Other than where such terms are more advantageous for the Authorized User(s) than those set forth in the Contract, no alteration or modification of the terms of the Contract, including substitution of Product, shall be valid or binding against Authorized User(s) unless authorized by the Commissioner or specified in the Contract Award Notification. No such alteration or modification shall be made by unilaterally affixing such terms to Product upon delivery (including, but not limited to, attachment or inclusion of standard pre-printed order forms, product literature, “shrink wrap” terms accompanying software upon delivery, or other documents) or by incorporating such terms onto order forms, purchase orders or other documents forwarded by the Contractor for payment, notwithstanding Authorized User’s subsequent acceptance of Product, or that Authorized User has subsequently processed such document for approval or payment.

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