Additional Receptors to Existing BMS Targets Sample Clauses

Additional Receptors to Existing BMS Targets. Without limiting BMS’ rights to add or substitute BMS Receptors and BMS Targets pursuant to Section 2.2.1(a) or Section 2.1.1(b), with respect to any existing BMS Target, BMS shall have the right, on a BMS Target-by-BMS Target basis, at any time and in its discretion, to add additional TCRs or additional CARs, as applicable, that are Directed to such existing BMS Target to this Agreement (each, an “Additional Receptor”) by providing written notice thereof to Immatics; provided that, [**]. If BMS provides such notice, then the Additional Receptor(s) shall become BMS Receptors hereunder (either as a BMS TCR or BMS CAR, as applicable) with respect to the applicable BMS Target. Notwithstanding the foregoing, in all cases, (i) BMS may only designate TCRs that are 2019 Collaboration TCRs (as of the time of designation) as BMS TCRs pursuant to this Section 2.1.1(d), (ii) BMS may only designate CARs that are owned (solely or jointly with a Third Party) or controlled (through license or otherwise) by BMS or its Affiliate or otherwise publicly available (in each case as of the time of designation) as BMS CARs pursuant to this Section 2.1.1(d); and (iii) [**]. For the avoidance of doubt, no additional amounts shall be payable for the designation of an Additional Receptor pursuant to this Section 2.1.1(d). In the event BMS designates an Additional Receptor pursuant to this Section 2.1.1(d) with respect to the First BMS Product or Second BMS Product, as applicable, then BMS may (but shall not be required to) add activities to be conducted by Immatics for such Additional Receptors to the applicable Research Plan, provided that BMS may only add such activities to the Research Plan if the reasonable Research Costs anticipated to be incurred by Immatics for reperforming any element of the Research Plan with the Additional Receptor for the applicable BMS Target shall be included in the overall Research Budget as reasonably agreed to by the Parties and subject to reimbursement by BMS as Eligible Research Costs in accordance with Section 6.2.2 and Section 6.2.3 in accordance with the Research Budget.
Sample 1
AutoNDA by SimpleDocs

Related to Additional Receptors to Existing BMS Targets

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 5.4.6.1 In the event AT&T identifies additional wire centers that meet the criteria set forth in Sections 5.4.2.1 or 5.4.2.2 above, but that were not included in the Master List of Unimpaired Wire Centers or AT&T’s List of Unimpaired Wire Centers, AT&T shall include such additional wire centers in a CNL. Each such list of additional wire centers shall be considered a Subsequent Wire Center List. AT&T will follow any limitations on the frequency with which it may issue such lists and notification procedures set forth in applicable Commission orders. 5.4.6.2 TWTC shall have thirty (30) business days to dispute the additional wire centers listed on AT&T’s CNL. Absent such dispute, effective thirty (30) business days after the date of a AT&T CNL providing a Subsequent Wire Center List, AT&T shall not be required to provide DS1 and DS3 Dedicated Transport, as applicable, in such additional wire center(s), except pursuant to the self-certification process as set forth in Section 1.9.1 of this Attachment. 5.4.6.3 For purposes of Section 5.4.6.1 above, AT&T shall make available DS1 and DS3 Dedicated Transport that were in service for TWTC in a wire center on the Subsequent Wire Center List as of the thirtieth (30th) business day after the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Embedded Base) until one hundred eighty (180) days after the thirtieth (30th) business day Version: 4Q06 Standard ICA 11/30/06 from the date of AT&T’s CNL identifying the Subsequent Wire Center List (Subsequent Transition Period). 5.4.6.4 The rates set forth in Exhibit B shall apply to the Subsequent Embedded Base during the Subsequent Transition Period. 5.4.6.5 No later than one hundred eighty (180) days from AT&T’s CNL identifying the Subsequent Wire Center List, TWTC shall submit an LSR(s) or spreadsheet(s) as applicable, identifying the Subsequent Embedded Base of circuits to be disconnected or converted to other AT&T services. 5.4.6.5.1 In the case of disconnection, the applicable disconnect charges set forth in this Agreement shall apply. 5.4.6.5.2 If TWTC chooses to convert DS1 and/or DS3 Dedicated Transport to special access circuits in existence as of the Effective Date of this Agreement, AT&T will include such DS1 and/or DS3 Dedicated Transport within TWTC’s total special access circuits, and apply any discounts to which TWTC is entitled from the transition period of 3/11/2006 to the conversion date. Conversions will be subject to the switch-as-is charge set forth in Exhibit A to this Attachment 2. 5.4.6.5.3 AT&T shall not impose disconnect or nonrecurring installation charges when transitioning the Subsequent Embedded Base of DS1 and DS3 Dedicated Transport in existence as of the Effective Date of this Agreement. 5.4.6.6 If TWTC fails to submit the LSR(s) or spreadsheet(s) for all of its Subsequent Embedded Base by one hundred eighty (180) days after the date of AT&T’s CNL identifying the Subsequent Wire Center List, AT&T will identify TWTC’s remaining Subsequent Embedded Base, if any, and will transition such circuits to the equivalent tariffed AT&T service(s), or in the case of Georgia, to the equivalent 271 service(s) set forth in Exhibit 1. In the states of Florida, Kentucky, Mississippi and South Carolina, those circuits identified and transitioned by AT&T shall be subject to the applicable disconnect charges as set forth in this Agreement and the full nonrecurring charges for installation of the equivalent tariffed AT&T service as set forth in AT&T’s tariffs. In the states of Alabama, Georgia, North Carolina and Tennessee, those circuits identified and transitioned by AT&T shall be subject to the applicable switch-as-is rates set forth in Exhibit A of Attachment

  • Additional Acceptable Uses of Student Data Contractor is prohibited from using Student Data for any secondary use not described in this agreement except: a. for adaptive learning or customized student learning purposes; b. to market an educational application or product to a parent or legal guardian of a student if Contractor did not use Data, shared by or collected per this Contract, to market the educational application or product; c. to use a recommendation engine to recommend to a student i. content that relates to learning or employment, within the third-party contractor's internal application, if the recommendation is not motivated by payment or other consideration from another party; or

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • CONDITIONS FOR EMERGENCY/HURRICANE OR DISASTER - TERM CONTRACTS It is hereby made a part of this Invitation for Bids that before, during and after a public emergency, disaster, hurricane, flood, or other acts of God that Orange County shall require a “first priority” basis for goods and services. It is vital and imperative that the majority of citizens are protected from any emergency situation which threatens public health and safety, as determined by the County. Contractor agrees to rent/sell/lease all goods and services to the County or other governmental entities as opposed to a private citizen, on a first priority basis. The County expects to pay contractual prices for all goods or services required during an emergency situation. Contractor shall furnish a twenty-four (24) hour phone number in the event of such an emergency.

  • Multi-year Planning Targets Schedule A may reflect an allocation for the first Funding Year of this Agreement as well as planning targets for up to two additional years, consistent with the term of this Agreement. In such an event, the HSP acknowledges that if it is provided with planning targets, these targets: a. are targets only, b. are provided solely for the purposes of planning, c. are subject to confirmation, and d. may be changed at the discretion of the Funder in consultation with the HSP. The HSP will proactively manage the risks associated with multi-year planning and the potential changes to the planning targets; and the Funder agrees that it will communicate any changes to the planning targets as soon as reasonably possible.

  • Updates to Schedules Should any of the information or disclosures provided on any of the Schedules attached hereto become outdated or incorrect in any material respect, the Borrower shall promptly provide the Agent in writing with such revisions or updates to such Schedule as may be necessary or appropriate to update or correct same; provided, however, that no Schedule shall be deemed to have been amended, modified or superseded by any such correction or update, nor shall any breach of warranty or representation resulting from the inaccuracy or incompleteness of any such Schedule be deemed to have been cured thereby, unless and until the Required Banks, in their sole and absolute discretion, shall have accepted in writing such revisions or updates to such Schedule.

  • Combinations and Split-ups of Receipts Upon surrender of a Receipt or Receipts at the Depositary Office or such other office as the Depositary may designate for the purpose of effecting a split-up or combination of Receipts, subject to the terms and conditions of this Deposit Agreement, the Depositary shall execute and deliver a new Receipt or Receipts in the authorized denominations requested evidencing the same aggregate number of Depositary Shares evidenced by the Receipt or Receipts surrendered.

  • License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license. (b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement. (d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. (e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.

  • Geographic Area and Sector Specific Allowances, Conditions and Exceptions The following allowances and conditions shall apply where relevant. Where the Employer does work which falls under the following headings, the Employer agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

  • Additional Requirements for Sleeping Rooms The Contractor shall provide departing Attendees a secured area for storing belongings.

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