Pre-Launch Sample Clauses

Pre-Launch. In the event that a Third Party attacks the validity of any particular Kissei Patents or Biphasic Patents in any country of the Territory prior to the time that any Product is launched in any country of the Territory, BHV will use reasonable efforts to allow ISLT to provide input and comment on the conduct of the defense of such claim, and ISLT shall give all reasonable assistance (excluding financial assistance) to Kissei and BHV in connection with such defense. The Parties acknowledge that Kissei has the first right to control the suit and proceeding with respect to such pre-launch defense of Kissei Patents under the Kissei Agreement. In the event that BHV assumes control and defense of a claim in the Territory in accordance with the Kissei Agreement, BHV shall not agree to any settlement of the suit without the prior written consent of ISLT. BHV shall control any suit and proceeding with respect to such pre-launch defense of Biphasic Patents in the Territory, and BHV shall not agree to any settlement of the suit without the prior written consent of ISLT. In the event that neither Kissei nor BHV elects to assume control or defense of such a suit or claim with respect to the Kissei Patents in the Territory, BHV shall notify ISLT of that election within in a commercially reasonable time and, if ISLT so requests, contact Kissei and convey ISLT’s request to assume control or defense of such suit or claim with respect to the Kissei Patents. If Kissei approves such request, then ISLT, at its discretion, may assume control or defense of such claim. In the event that BHV elects not to assume control or defense of such a suit or claim with respect to the Biphasic Patents in the Territory, then ISLT, at its discretion, may assume control or defense of such claim. In the event that ISLT assumes control or defense of any action under this Section 12.4(a), ISLT will assume all responsibility, including financial responsibility for the legal action. BHV shall give all reasonable assistance (excluding financial assistance) to ISLT. BHV may be represented by counsel of its own selection in such legal action. ISLT shall reimburse BHV for reasonable costs and shall not agree to any settlement of the suit without the prior written consent of BHV.
AutoNDA by SimpleDocs
Pre-Launch. Prior to commercial launch of PRODUCT in TERRITORY A, each Party will be allowed to allocate to the JOINT P&L calculated under Section 7.1.14 only OUT-OF-POCKET COSTS which are SALES COSTS, MARKETING COSTS, PATENT COSTS, TRADEMARK COSTS or OTHER OPERATING INCOME/EXPENSE, all subject to the prior approval of the JCC or in accordance with the then current JOINT MARKETING PLAN. In no event shall Xxxxxxx be permitted to allocate to the JOINT P&L any SALES EFFORT expenses for any personnel employed on a full-time or part-time basis by Xxxxxxx during the period preceding the commercial launch of PRODUCT in TERRITORY A."
Pre-Launch. The Center will conduct a meeting (in-person or via telephone) with Ecology (and other members of the State Ocean Caucus?) to delineate expectations about the project scope, roles/responsibilities of the facilitation team, process design, and desired outcomes. The Center will also conduct a series of short phone interviews (or a short pre-meeting survey) with advisory body members and other affiliated parties to preview the issues, objectives, timelines and desired outcomes. The Center will use the information gathered to customize a process design, and prepare a draft meeting design and agenda for the advisory body and Ecology to discuss and modify during the first preparation meeting.
Pre-Launch. The parties will use best efforts to complete their respective obligations to provide the data elements (including collection and reporting of complete Quality Measures pursuant to Exhibit 5) required to complete a test Financial Reconciliation for 2015. No party will have any financial obligations to the other party based on the results of this test Financial Reconciliation for 2015.
Pre-Launch. During the ‘Pre-Launch’ period you will be introduced to your Trading Team. These will be your additional points of contact throughout your time at Pontiac, supplementing the Sales Representative. After receiving a signed IO, we can go live in a minimum of 48 hours. Here are the things needed to go live: • Creatives (adhering to the specs sent on the IO/Proposal, and including the click through URL) o Ads sent our way must be uploaded and audited. This audit is conducted by our DSP and ensures branding matches the destination URL and is brand-safe. That process takes up to 48 hours. • Pixels (if applicable) o Pixels are pieces of code that will be added to your website. They are very light and do not slow down the loading of your page, but will fire when someone lands there, helping us to track the campaign. o Pixels will be created and provided to you by your Pontiac Trading Team. You will then need to place them on the relevant web pages as needed for campaign execution. o Segment pixels are placed on the homepage and utilized for remarketing. Your remarketing audience will not start growing until the pixel is placed and properly firing. Remarketing campaigns cannot go live until these pixels are confirmed to be placed and we see loads in our console. o Conversion pixels are placed on ‘Thank you’ pages and utilized to record the desired action, such as a purchase or a form fill-out. If conversion pixels are in play in the campaign, we cannot go live until these are confirmed to be placed and we see loads in our console. • Any other specific pieces to your campaign including custom audiences, site lists, etc. – aka if we’re onboarding data, we need the CRM list. These nuances will be discussed on a case-to-case basis and could potentially increase the lead time needed prior to launch. o Specifically, we recommend a two-week lead time when working with LiveRamp. • The Pontiac Trading Team and Sales Representative may schedule a kick-off call with you to ensure that all pieces have been collected, that your goals are clear and attainable, and to set a reporting cadence. This call should happen at least 48 hours prior to the launch of the campaign. If the campaign is a quick-start, the call will take place after the IO is signed if needed. • If you wish to pay on Net Terms, instead of Credit Card Daily or Credit Card Prepay, you will need to fill out the Credit Application in Appendix B. Note we need a minimum of 7 business days to process Credit Apps and if...
Pre-Launch. Prior to the Launch Date, USAA hereby agrees that it shall, in good faith and to the extent of its commercially reasonable abilities, market the USAA Auto Program to USAA Members, including in such a manner and through such channels and means as follows: (1) provide a prominent place within any and all USAA Member web sites to promote the USAA Auto Program, (2) offer the USAA Auto Program at the end of each online USAA automobile loan or lease application, as well as within the USAA call center as a USAA service available to USAA Members interested in purchasing an automobile, and (3) work with ZAG to determine what USAA marketing and publicity is reasonably needed and acceptable to USAA to further expand and grow the USAA Auto Program.
Pre-Launch. Prior to commercial launch of PRODUCT in TERRITORY A, each Party will be allowed to allocate to the JOINT P&L calculated under Section 7.1.14 only OUT-OF-POCKET COSTS which are SALES COSTS, MARKETING COSTS, PATENT COSTS, TRADEMARK COSTS or OTHER OPERATING INCOME/EXPENSE, all subject to the prior approval of the JCC or in accordance with the then current JOINT MARKETING PLAN, except that Coulxxx xxxll also be allowed to allocate to the JOINT P&L an amount equal to [*] (i.e., [*]) for [*] the commercial launch of PRODUCT in TERRITORY A (such amount [*]), provided that such allocation shall not occur if the PRODUCT is not commercially launched in TERRITORY A, and such allocation shall be made only after the PRODUCT is commercially launched in TERRITORY A.
AutoNDA by SimpleDocs

Related to Pre-Launch

  • Regulatory Approval 25.1 The Parties understand and agree that this Agreement and any amendment or modification hereto will be filed with the Commission for approval in accordance with Section 252 of the Act and may thereafter be filed with the FCC. The Parties believe in good faith and agree that the services to be provided under this Agreement are in the public interest. Each Party covenants and agrees to fully support approval of this Agreement by the Commission or the FCC under Section 252 of the Act without modification.

  • Development Milestones In addition to its obligations under Paragraph 7.1, LICENSEE specifically commits to achieving the following development milestones in its diligence activities under this AGREEMENT: (a) (b).

  • Development Milestone Payments In partial consideration for the rights and licenses granted to Coya hereunder, within ten days after the first achievement of each milestone event in a given Indication set forth in this Section 5.2 (Development Milestone Payments) with respect to a Product (each, a “Development Milestone Event”) by or on behalf of Coya or any of its Affiliates or Sublicensees, Coya shall provide ARScience Bio written notice to ARScience Bio identifying the Development Milestone Event achieved. Upon receipt of any such notice of first achievement of a Development Milestone Event by Coya or its Affiliates or Sublicensees, ARScience Bio will promptly invoice Coya for the applicable Development Milestone Event and Coya will make a milestone payment to ARScience Bio in the amount set forth in this Section 5.2 (Development Milestone Payments) corresponding to such Development Milestone Event (each, a “Development Milestone Payment”) within 45 days of receipt of such invoice. On an Indication-by-Indication basis, each Development Milestone Payment shall be payable only upon the first achievement of the corresponding Development Milestone Event by a Product, in any given Indication for which the Development Milestone Events have not been previously achieved (each such Indication, a “New Indication”). No amounts shall be due for subsequent or repeated achievements of such Development Milestone Event with respect to the same or different Mono Product or Combination Product, as applicable, in such Indication. Accordingly and for clarity, the Development Milestone Payment shall be paid only once, when first achieved by Coya, an Affiliate or a Sublicensee, but no payment shall be due if the same milestone is subsequently achieved by one of Coya, an Affiliate or a Sublicensee. For clarity, the amounts owed in Column (a) below shall be due for the first Combination Product to achieve the Development Milestone Events in a New Indication and the amounts owned in Column (c) below shall be due for the first Mono Product to achieve the Development Milestone Events in a New Indication. Any Combination Product or Mono Product to achieve the Development Milestone Events in a New Indication after the first achievement of the Development Milestone Events as described in the foregoing sentence will cause the amounts in Column (b) with respect to a Combination Product and Column (d) with respect to a Mono Product to be due and payable by Coya upon each such occurrence. If the first Product to achieve a Development Milestone Event in any Indication is a Combination Product, the amounts in Column (a) below shall be due and payable by Coya. If the next Product to achieve a Development Milestone Event in a New Indication is a Mono Product, the amounts in Column (c) below would be due and payable by Coya; provided, that if such next Product to achieve a Development Milestone Event in a New Indication is a Combination Product, the amounts in Column (b) would be due and payable by Coya. By way of example, if a Combination Product achieves IND Acceptance in ALS, and is the first Product to achieve a Development Milestone Event under this Agreement, [***] will be due and payable by Coya. If subsequently a Mono Product achieves IND Acceptance in ALS, no Development Milestone Payments will be due and payable by Coya under this Agreement. However, if subsequently any Combination Product achieves IND Acceptance in Alzheimer’s disease, [***] would be due and payable by Coya.

  • Required Regulatory Approvals Certain transactions required, permitted or otherwise contemplated by this Agreement may under certain circumstances require prior filings with and approvals, or non-disapprovals, from the Indiana Department of Insurance or the Indiana Insurance Commissioner. Such transactions include: (a) issuance or purchase of any additional capital stock of the Company or other securities convertible into or exchangeable or exercisable for capital stock of the Company pursuant to Sections 1.2 or 3.4; (b) transfer of Shares to a wholly owned subsidiary of a Shareholder, to another Shareholder or to a wholly owned subsidiary of another Shareholder pursuant to Sections 3.1(a) or 3.4; (c) exercise of preemptive rights by a Shareholder pursuant to Section 3.2; and (d) exercise of call rights by the Company or a Shareholder pursuant to Section 3.3 (including pursuant to the two provisos in Section 3.1(b)). Notwithstanding anything to the contrary contained in this Agreement, any such transactions requiring filings with and approvals, or non-disapprovals, from the Indiana Department of Insurance or the Indiana Insurance Commissioner shall not, to the extent within the control of a party hereto, be entered into or consummated unless and until the required filings have been made and the required approvals (or non-disapprovals) have been obtained, and to the extent not within the control of an applicable party hereto, such party shall use best efforts to cause such transactions not to be entered into or consummated unless and until the required filings have been made and the required approvals (or non-disapprovals) have been obtained.

  • Milestone A principal event specified in the Contract Documents including the Material Completion and Occupancy Date and other events relating to an intermediate completion date or time.

  • Product Changes Vocera shall have the right, in its absolute discretion, without liability to End User, to update to provide new functionality or otherwise change the design of any Product or to discontinue the manufacture or sale of any Product. Vocera shall notify End User at least 90 days prior to the delivery of any Product which incorporates a change that adversely affects form, fit or function (“Material Change”). Vocera shall also notify End User at least 90 days prior to the discontinuance of manufacture of any Product. Notification will be made as soon as reasonably practical for changes associated with regulatory or health and safety issues.

  • Milestone Event Milestone Payment [***] [***]

  • Product Recall (a) If a recall is required by applicable Law, or if Buyer or Supplier reasonably determines that a recall is advisable because the goods may create a potential safety hazard, are not in compliance with any applicable code, standard or legal requirement, or contain a defect or non-conformance with the requirements of this Order occurring or likely to occur in multiple goods, which such defects or non-conformances are substantially similar or have substantially similar causes or effects (collectively a “Serial Defect”), the parties shall promptly communicate such facts to each other. At Buyer’s request, Supplier shall promptly develop a corrective action plan satisfactory to Buyer, which shall include all actions required to recall and/or repair the goods and any actions required by applicable Law (“Corrective Action Plan”) for Buyer’s review and approval. At Buyer’s election, Xxxxx may develop the Corrective Action Plan. In no event shall Buyer and Supplier’s failure to agree on the Corrective Action Plan delay the timely notification of a potential safety hazard, non-compliance or Serial Defect to users of the goods, cause either party to be non-compliant with applicable Law or prevent Buyer from taking reasonable actions to prevent injury or damage to persons, equipment or other property. Supplier and Buyer shall cooperate with and assist each other in any corrective actions and/or filings, if applicable.

  • Commercialization License Subject to the terms of this Agreement, including without limitation Section 2.2 and Theravance's Co-Promotion rights in Section 5.3.2, Theravance hereby grants to GSK, and GSK accepts, an exclusive license under the Theravance Patents and Theravance Know-How to make, have made, use, sell, offer for sale and import Alliance Products in the Territory.

  • Licensed Product “Licensed Product” shall mean any article, composition, apparatus, substance, chemical material, method, process or service whose manufacture, use, or sale is covered or claimed by a Valid Claim within the Patent Rights. For clarity, a “Licensed Product” shall not include other product or material that (a) is used in combination with Licensed Product, and (b) does not constitute an article, composition, apparatus, substance, chemical material, method, process or service whose manufacture, use, or sale is covered or claimed by a Valid Claim within the Patent Rights.

Time is Money Join Law Insider Premium to draft better contracts faster.