Future Development Plans Sample Clauses

Future Development Plans. Batch Processing (▇▇▇▇▇▇) gave an overview of the current status of, and plans for further developing, batch processing capabilities within ESAP. Refer to §§2.3.7 & 2.4 of this document for an overview of these plans. A key aim of this talk was to solicit guidance from the community about which batch systems they regard as a priority, as well as developer effort to help integrate ESAP with their own systems. The WP5 leadership adopts the position that selection of a batch system or systems should be largely community driven: rather than WP5 choosing a standardized system, WP5 will work with the community to enable whatever batch systems they require (within the limits of available resources). The primary advocates of ESAP interfaces with batch computing come from CTA, who require interfaces with DIRAC. We agreed that development would prioritize this work; members of the community were encouraged to work with WP5 developers to push this effort forward. Managed Database (▇▇▇▇▇▇▇) discussed the Managed Database service being proposed for ESAP (§2.3.9), including an impressive live demo. The discussion focused around technical aspects of the system: the tech‐ nologies used, and how they could be integrated with the rest of the ESAP system. The suggestion of the Managed Database service being used as the basis for potential improvements to the shopping basket (§2.3.3) was discussed. This could unlock a range of new possibilities. However, the Managed Database is currently an immature prototype, and the work package is cognizant of its commitments to make robust deliveries of promised functionality on time. The current plan is therefore to continue development of the existing shopping basket system, while working on the Managed Database service in parallel and remaining alert to opportunities for future enhancements. Interested members of the community were encouraged to connect directly with the WP5 developers to provide additional use cases and guide the development effort.
Future Development Plans. Alios and Vertex plan to initiate clinical development of each compound in the fourth quarter of 2011, which is expected to include studies of the compounds in healthy volunteers followed by short-duration safety and viral kinetic studies in people with hepatitis C. The goal of the first clinical studies of these compounds is to generate data to enable the initiation of Phase 2 studies as early as the end of 2012. These Phase 2 studies are expected to evaluate multiple combination regimens of ALS-2200, ALS-2158, INCIVEK and VX-222. The combination studies would be designed to generate sustained viral response (SVR or viral cure) data. Additional details on the clinical development program for ALS-2200 and ALS-2158 will be provided later in 2011 upon initiation of the first clinical study. As part of the agreement, Alios will receive a $60 million up-front payment from Vertex for the worldwide rights to ALS-2200 and ALS-2158. Vertex is responsible for development costs related to ALS-2200 and ALS-2158 and will also provide research funding to Alios. In addition, Alios would be eligible to receive research and development milestone payments up to $715 million if both compounds are approved. Vertex expects to pay approximately $35 million in development milestones in 2011. Alios is also eligible to receive up to $750 million in sales milestones on sales of all approved medicines under the collaboration. The agreement also includes tiered royalties on product sales. Important Information About INCIVEKTM (telaprevir) tablets INCIVEKTM (telaprevir) is a prescription medicine used with the medicines peginterferon alfa and ribavirin to treat chronic (lasting a long time) hepatitis C genotype 1 infection in adults with stable liver problems, who have not been treated before or who have failed previous treatment. It is not known if INCIVEK is safe and effective in children under 18 years of age. INCIVEK should always be taken in combination with peginterferon alfa and ribavirin. Ribavirin may cause birth defects or death of an unborn baby. Therefore, you should not take INCIVEK combination treatment if you are pregnant or may become pregnant, or if you are a man with a sexual partner who is pregnant. INCIVEK and other medicines can affect each other and can also cause side effects that can be serious or life threatening. There are certain medicines you cannot take with INCIVEK combination treatment. Tell your healthcare provider about all the medicines you take, inc...

Related to Future Development Plans

  • Future Developments The Seller continuously monitors technological developments and applies them to Technical Data, document and information systems’ functionalities, production and methods of transmission. The Seller will implement and the Buyer will accept such new developments, it being understood that the Buyer will be informed in due time by the Seller of such new developments and their application and of the date by which the same will be implemented by the Seller.

  • Development Plans Customer has provided Provider with a report attached hereto as Exhibit D (the “Current Development Plan”) describing in detail, as of January 1, 2017, the planned development, drilling, production, processing, treating, marketing and other activities to take place with respect to Dedicated Production and Customer Injected NGLs for the applicable Development Period. The information contained in the Current Development Plan is, 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, production, processing, treating, marketing and other activities that Customer expects to take place with respect to Dedicated Production and Customer Injected NGLs for the then-applicable Development Period. Customer and Provider shall each make their respective representatives available to participate in such meetings and discussions. No later than August 1 of each such Year, Customer shall provide (or cause to be provided) to Provider 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, production, processing, treating, marketing and other activities to take place with respect to Dedicated Production and Customer Injected NGLs for the then-applicable Development Period (any such update, an “Updated Development Plan” and, together with the Current Development Plan, each, a “Development Plan”). (b) Each proposed Development Plan shall include information as to the following, in each case, broken out, 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) forward-looking production estimates for the applicable time period covered by such Development Plan for all Customer Gas and Customer Injected NGLs (A) that Customer reasonably and in good faith believes will become owned or Controlled by Customer during the time period covered by such Development Plan, and/or (B) that will be produced from (I) in the aggregate, all ▇▇▇▇▇ then-existing and (II) in the aggregate, all ▇▇▇▇▇ 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, 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 (**). (ii) (A) each new receipt point (including the location thereof) proposed by Customer with respect to the Dedicated Production Estimate reflected in such Development Plan (each such receipt point, a “Planned Receipt Point”), (B) each Receipt Point at which Customer expects to Tender Customer Gas or Customer Injected NGLs reflected in such Development Plan into the TGP System, and (C) the estimated portion of the Dedicated Production Estimate contained in such Development Plan that Customer expects to Tender at each such Receipt Point and Planned Receipt Point; (iii) (A) each new delivery point (including the location thereof) proposed by Customer with respect to the Dedication Production Estimate reflected in such Development Plan (each such delivery point, a “Planned Delivery Point”), (B) each Delivery Point at which Customer expects to Nominate Customer Residue Gas or Customer NGLs produced from the Dedicated Production Estimate reflected in such Development Plan to be redelivered to Customer, and (C) the estimated volumes of Customer Residue Gas and Customer NGLs produced from the Dedication Production Estimate contained in such Development Plan that Customer expects to Nominate to each such Delivery Point; (iv) the earliest date on which each Planned Receipt Point and Planned Delivery Point included in the Development Plan is required by Customer to be placed into service, 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 Receipt Point or Planned Delivery Point was delivered to Provider hereunder; (v) the anticipated characteristics of the production from the ▇▇▇▇▇ and Planned ▇▇▇▇▇ 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 Customer may utilize the existing and historical production information from similarly situated ▇▇▇▇▇; (vi) any (A) proposed revision to the then-existing Dedicated Area and/or any then-existing Dedicated Contract and/or (B) any new contract that Customer proposes to be a Dedicated Contract; and (vii) other information reasonably requested by Provider that is relevant to the design, construction, and operation of the TGP System, including (A) any applicable Plant Expansion or Facilities Modification proposed by Customer, (B) the relevant Receipt Point and Planned Receipt Point facilities applicable to such Development Plan, and (C) the relevant Delivery Point and Planned Delivery Point facilities applicable to such Development Plan. 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 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.

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

  • Development Program A. Development activities to be undertaken (Please break activities into subunits with the date of completion of major milestones) B. Estimated total development time