Inclusion Process Sample Clauses

Inclusion Process. (a) Subject to the other provisions of this Clause 6.1, the Intermediary may include in the Portfolio (for their full original principal amount, and not partially) SME Transactions that: (i) comply with the Eligibility Criteria and all other relevant provisions of this Agreement; and (ii) are entered into during a period (the “Inclusion Period”) commencing on (and including) the first day of the Availability Period and ending on the last day of the Availability Period (the “Availability Period End Date” or the “Inclusion Period End Date”). (b) If a Trigger Event has occurred on the relevant Trigger Event Determination Date then, unless otherwise notified by the Counterparty to the Intermediary in writing, the last day of the Availability Period shall be deemed to be such Trigger Event Determination Date and the other provisions of this Agreement shall be construed accordingly. The Intermediary hereby undertakes to notify promptly the Counterparty upon the occurrence of one or more Trigger Event(s) by sending to the Counterparty a notice in the form of Schedule 10 (Form of Trigger Event Notice) and to provide the Counterparty on each Trigger Event Determination Date with information relating to (as applicable) (a) the aggregate value of the Collateral on such date, (b) the aggregate Defaulted Amounts incurred on such date and (c) the Actual Portfolio Volume on such date. (c) The Intermediary shall submit an Inclusion Notice by each Report Date in respect of SME Transactions entered into in the calendar quarter preceding the date of the relevant Inclusion Notice provided that the last Inclusion Notice shall not be sent later than on the date falling one month after the Inclusion Period End Date. In case no SME Transactions are to be included in the Portfolio during a particular calendar quarter, an Inclusion Notice stating that no SME Transactions are to be included shall be sent to the Counterparty by the relevant Report Date. The Intermediary shall promptly after the Availability Period End Date deliver to the Counterparty a notice in the form of Schedule 2 (Form of Approval at the end of the Availability Period) including the required information on any SME Transactions approved by the Intermediary before the end of the Availability Period and that may be included in the Portfolio after such date, as applicable.
Sample 1
AutoNDA by SimpleDocs
Inclusion Process. If, after the Effective Date, a Party wishes to acquire rights under any New Technology that would be Sage Licensed Technology or Biogen Licensed Technology, as applicable, then such Party will so notify the JSC and provide the JSC with a summary of the terms of any license or agreement, including any Third Party Payments owed to a Third Party as a result of the grant to the other Party of rights with respect to such New Technology or a Party’s practice or use of any such New Technology in the performance of activities under this Agreement, under which such Party would acquire the rights to such subject matter in accordance with Section 8.3.2.1 (New Technology) (such applicable terms, the “New Technology Terms”). In connection with the discussion of the New Technology Terms, the JSC may also discuss [**]. In the event the JSC agrees to include such New Technology under this Agreement for the Profit-Share Territory, then such New Technology will be included in the Sage Licensed Technology or the Biogen Licensed Technology, as applicable and will be subject to the terms and conditions of this Agreement, and the Parties will be bound by such New Technology Terms. If the JSC does not agree to include such New Technology under this Agreement for the Profit-Share Territory as Sage Licensed Technology or Biogen Licensed Technology, as applicable, and one Party believes that such New Technology is [**], then the resolution procedure of Section 8.3.2.4 (New Technology Disputes) will apply. For clarity, with respect to New Technology other than [**], the Party proposing to acquire rights to such New Technology will have the right to obtain a license to such New Technology, but the other Party will not be bound by any agreement related to such New Technology or have any rights under, or cost-sharing obligations with respect to, such new Technology, unless such other Party agrees to include such New Technology under this Agreement.
Sample 1Sample 2
Inclusion Process. (a) Subject to the other provisions of this Clause 6.1, the Intermediary may include in the Portfolio (for their full original principal amount, and not partially) SME Transactions that: (i) comply with the Eligibility Criteria and all other relevant provisions of this Agreement; and (ii) are entered into during a period (the “Inclusion Period”) commencing on (and including) the first day of the Availability Period and ending on:
Sample 1
Inclusion Process. If, after the Effective Date, a Party wishes to include [***] “New Technology”) [***], then such Party shall so notify the other Party and provide the other Party with a summary of the terms of any license or agreement under which such Party acquired such subject matter prior to the Effective Date or, if after the Effective Date, would acquire or has acquired such subject matter in accordance with Section 6.5.2(a) (Acquisition) (such applicable terms, “New Technology Terms”). In the event the Parties agree in writing to include [***], then [***] shall be included in Denali IP or Biogen IP, as the case may be, and subject to the terms and conditions of this Definitive LRRK2 Agreement and the Parties shall be [***].[***]
Sample 1

Related to Inclusion Process

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Manufacturing Services Jabil will manufacture the Product in accordance with the Specifications and any applicable Build Schedules. Jabil will reply to each proposed Build Schedule that is submitted in accordance with the terms of this Agreement by notifying Company of its acceptance or rejection within three (3) business days of receipt of any proposed Build Schedule. In the event of Jabil’s rejection of a proposed Build Schedule, Jabil’s notice of rejection will specify the basis for such rejection. When requested by Company, and subject to appropriate fee and cost adjustments, Jabil will provide Additional Services for existing or future Product manufactured by Jabil. Company shall be solely responsible for the sufficiency and adequacy of the Specifications [***].

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

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