Amendments to the Joint Development Plan Sample Clauses

Amendments to the Joint Development Plan. On an annual basis (no later than [*] of the preceding calendar year), or more often as the Parties deem appropriate, the JDC shall prepare amendments to the then-current Joint Development Plan(s), including the corresponding Joint Development Budget(s), for approval of the JSC. Each such amended Joint Development Plan shall specify, with a level of detail according to Astellas’s standard practices, the items described in Section 3.2(a). Such amended Joint Development Plan shall cover the next calendar year (and additional periods as reasonably determined by the Parties) and the Joint Development Budget included therein shall appropriately itemize the costs separately for each Product. Such updated and amended Joint Development Plan shall reflect any changes, re-prioritization of studies within, reallocation of resources with respect to, or additions to the then-current Joint Development Plan. In addition, the JDC may prepare amendments for approval by the JSC to the Joint Development Plan (including the corresponding Joint Development Budget) from time to time during the calendar year in order to reflect changes in such plan or budget for such calendar year, in each case, in accordance with the foregoing. For the avoidance of doubt and without limitation, both Parties shall have the right to propose to the JDC any studies of the MDV3100 Product not then part of a Joint Development Plan, or the expansion of development of the MDV3100 Product to include any new indication(s) within the Field, or the development of any Collaboration Molecule other than MDV3100. Once approved by the JSC, the amended annual Joint Development Plan (including the corresponding Joint Development Budget) shall become effective for the applicable period on the date approved by the JSC (or such other date as the JSC shall specify). Any JSC-approved amended Joint Development Plan (including the corresponding Joint Development Budget) shall supersede the previous Joint Development Plan (including the corresponding Joint Development Budget) for the applicable period.
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Amendments to the Joint Development Plan

  • Development Plans Shipper has provided Gatherer with a report attached hereto as Exhibit D (the “Current Development Plan”) describing in detail, as of January 1, 2017, the planned development, drilling, and production activities to take place with respect to Dedicated Production for the applicable Development Period. The information contained in the TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Current Development Plan is broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by the Current Development Plan, on a Quarter-by-Quarter basis, and with respect to the remaining Years covered by the Current Development Plan, on a Year-by-Year basis. The Current Development Plan attached hereto has been approved by the Parties. (a) From time to time during each Year of the Term, the Parties shall meet to discuss the planned development, drilling, and production activities that Shipper expects to take place with respect to Dedicated Production for the then-applicable Development Period. Shipper and Gatherer shall each make their respective representatives available to participate in such meetings and discussions. No later than August 1 of each such Year, Shipper shall provide (or cause to be provided) to Gatherer a proposed update of the then-currently agreed Development Plan, prepared on the same basis as the Current Development Plan and describing in detail the planned development, drilling, and production activities to take place with respect to Dedicated Production for the then-applicable Development Period (any such update, an “Updated Development Plan” and, together with the Current Development Plan, each, a “Development Plan”). Notwithstanding anything herein to the contrary, in no event shall Gatherer be required to agree to any Updated Development Plan and corresponding updated Gathering System Plan that contains a Committed Build-Out that (i) has a corresponding Target Completion Date that occurs after the end of the Initial Term, and (ii) Gatherer, in its sole discretion, does not wish to approve. (b) Each proposed Development Plan shall include information as to the following, in each case, broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by such Development Plan, on a Quarter-by-Quarter basis, and, with respect to the remaining Years covered by such Development Plan, on a Year-by-Year basis: (i) all Xxxxx that, as of the date such Development Plan was delivered, are currently in existence and (A) the production therefrom is being delivered into the Gathering System, or (B) are awaiting connection to the Gathering System; (ii) the Xxxxx that are expected to be drilled during the time period covered by such Development Plan (each such Well reflected in such Development Plan, a “Planned Well”), and the estimated timing of the drilling of such Planned Xxxxx; (iii) forward-looking production estimates for the applicable time period covered by such Development Plan for all Shipper Gas (A) that Shipper reasonably and in good faith believes will become owned or Controlled by Shipper during the time period covered by such Development Plan, and/or (B) that will be produced from (I) in the aggregate, all Xxxxx then-existing and (II) in the aggregate, any Planned Xxxxx included in such Development Plan (such collective estimates described in subsections (A) and (B), both with respect to a particular Quarter and an entire Year, the “Dedicated Production Estimates”); TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). (iv) forward-looking estimates for the applicable time period covered by such Development Plan of the aggregate volumes of those Shipper Injected Liquids that Shipper intends to Tender to the Injection Points hereunder to receive the System Services (such estimates, both with respect to a particular Quarter and an entire Year, the “System Liquids Estimates” and, together with the Dedicated Production Estimates, the “System Production Estimates”); (v) (A) each new receipt point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such receipt point, including those located at the site of a Planned Well, a “Planned Receipt Point”), (B) each Receipt Point at which Shipper expects to Tender Shipper Gas and/or Shipper Injected Liquids reflected in such Development Plan into the Gathering System, and (C) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to Tender at each such Receipt Point and Planned Receipt Point; (vi) the earliest date on which each Planned Well included in the Development Plan is estimated to be completed and producing, which date shall not be earlier than three Months after the January 1st that is immediately subsequent to the date that the Development Plan that initially reflected such Planned Well was delivered to Gatherer hereunder; (vii) the anticipated characteristics of the production from the Xxxxx and Planned Xxxxx reflected in such Development Plan (including liquids content and gas and liquids composition) and the projected production volumes and production pressures applicable thereto; provided that Shipper may utilize the existing and historical production information from similarly situated Xxxxx; (viii) (A) each new delivery point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such delivery point, a “Planned Delivery Point”), (B) each Delivery Point at which Shipper expects Shipper Gas produced from the Xxxxx and Planned Xxxxx reflected in such Development Plan to be redelivered to Shipper, (C) each Delivery Point at which Shipper expects any Drip Liquids allocated to Shipper in accordance with this Agreement and/or Shipper Injected Liquids to be redelivered to Shipper, and (D) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to be redelivered to Shipper at each such Delivery Point and Planned Delivery Point; (ix) any (A) proposed revision to the then-existing Dedicated Area and/or any then-existing Dedicated Contract and/or (B) any new contract that Shipper proposes to be a Dedicated Contract; and (x) other information reasonably requested by Gatherer that is relevant to the design, construction, and operation of the Gathering System, including (A) any Subsystem Extension proposed by Shipper, (B) the relevant Receipt Point, Planned Receipt Point, Delivery Point and Planned Delivery Point facilities applicable to such TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Development Plan, and (C) any treating, processing, or liquids handling facilities proposed by Shipper that may be required for any Shipper Gas and/or Shipper Injected Liquids to meet applicable Downstream Facility specifications at the Delivery Points.

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

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

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

  • Commercialization Plan (a) Not later than three [***] after submission of Regulatory Filings for each Product in each country of the Territory, Licensee will provide to the JCC for review its initial Commercialization Plan for each Product for each country in the Territory. Such initial Commercialization Plan will describe Licensee’s plans for activities to be conducted for such Product for such country. Each Commercialization Plan shall include the details of obligations to be performed by Licensee to achieve the specific activities that are applicable to the stage of [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. Commercialization (e.g., pre-launch, launch planning, launch, or post-launch) of the applicable Product during the time period covered by such Commercialization Plan and subsequent time periods. (b) Prior to the First Commercial Sale for such Product in such country, Licensee will provide to the JCC for review an updated Commercialization Plan for such Product for such country. Such updated Commercialization Plan will include, but not be limited to, Licensee’s updated plans for activities to be conducted for such Product for such country prior to launch as well as activities to be conducted in connection with such launch. (c) Promptly after each anniversary of the First Commercial Sale of such Product during the Term, Licensee will provide to the JCC for review updated Commercialization Plans for such Product for such country. Such further updated Commercialization Plan will include, but not be limited to, Licensee’s plans for Commercialization activities for such Product and such country for the twelve (12) month period following the date of delivery of such Commercialization Plan. No Commercialization Plan may be implemented by Licensee if [***]. Each Commercialization Plan shall be consistent with and shall not contradict the terms of this Agreement [***], and in the event of any inconsistency between the Commercialization Plan and this Agreement, the terms of this Agreement shall prevail. Notwithstanding the foregoing, if a [***], Licensee shall [***] and shall promptly [***].

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

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

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

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

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