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

Related to Modification of Development Plan

  • Initial Development Plan Not later than the Effective Date, Licensee shall have provided Merck with an initial Development plan for the Licensed Product in the Field in the Territory, which shall be incorporated as part of this Agreement as Attachment 3.02(a) (as may be amended in accordance with this Agreement, the “Development Plan”). **CERTAIN INFORMATION IN THIS EXHIBIT HAS BEEN OMITTED AND WILL BE FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION PURSUANT TO A CONFIDENTIAL TREATMENT REQUEST.

  • 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 Contract Area, including its abandonment.

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

  • Commercialization Plan On a Product by Product basis, not later than sixty (60) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory, the MSC shall prepare and approve a rolling multiyear (not less than three (3) years) plan for Commercializing such Product in the Copromotion Territory (the "Copromotion Territory Commercialization Plan"), which plan includes a comprehensive market development, marketing, sales, supply and distribution strategy for such Product in the Copromotion Territory. The Copromotion Territory Commercialization Plan shall be updated by the MSC at least once each calendar year such that it addresses no less than the three (3) upcoming years. Not later than thirty (30) days after the filing of the first application for Regulatory Approval of a Product in the Copromotion Territory and thereafter on or before September 30 of each calendar year, the MSC shall prepare an annual commercialization plan and budget (the "Annual Commercialization Plan and Budget"), which plan is based on the then current Copromotion Territory Commercialization Plan and includes a comprehensive market development, marketing, sales, supply and distribution strategy, including an overall budget for anticipated marketing, promotion and sales efforts in the upcoming calendar year (the first such Annual Development Plan and Budget shall cover the remainder of the calendar year in which such Product is anticipated to be approved plus the first full calendar year thereafter). The Annual Commercialization Plan and Budget will specify which Target Markets and distribution channels each Party shall devote its respective Promotion efforts towards, the personnel and other resources to be devoted by each Party to such efforts, the number and positioning of Details to be performed by each Party, as well as market and sales forecasts and related operating expenses, for the Product in each country of the Copromotion Territory, and budgets for projected Pre-Marketing Expenses, Sales and Marketing Expenses and Post-Approval Research and Regulatory Expenses. In preparing and updating the Copromotion Territory Commercialization Plan and each Annual Commercialization Plan and Budget, the MSC will take into consideration factors such as market conditions, regulatory issues and competition.

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

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

  • Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.

  • Marketing Plan The MCP shall submit an annual marketing plan to ODM that includes all planned activities for promoting membership in or increasing awareness of the MCP. The marketing plan submission shall include an attestation by the MCP that the plan is accurate is not intended to mislead, confuse or defraud the eligible individuals or ODM.

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

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