License and Community Agreement Sample Clauses

License and Community Agreement 
AutoNDA by SimpleDocs

Related to License and Community Agreement

  • Cooperation Agreement At the Closing, PCC and Buyer shall, and PCC shall cause PCC Parent to, execute and deliver the Cooperation Agreement pursuant to which Buyer, PCC Parent and PCC shall provide each other certain information and other assistance in connection with the collection, administration and/or satisfaction of certain of the Retained Liabilities.

  • License Agreement The Trust shall have the non-exclusive right to use the name "Invesco" to designate any current or future series of shares only so long as Invesco Advisers, Inc. serves as investment manager or adviser to the Trust with respect to such series of shares.

  • INDEMNITY AGREEMENT The Indemnity Agreement Regarding Hazardous Materials made by the Borrower and Guarantors, in favor of the Agent and the Lenders, as the same may be modified, amended or ratified, pursuant to which each of the Borrower and the Guarantors agrees to indemnify the Agent and the Lenders with respect to Hazardous Substances and Environmental Laws.

  • GENERAL AGREEMENT In the event Indemnitee was, is, or becomes a Participant in, or is threatened to be made a Participant in, a Proceeding, the Company shall indemnify the Indemnitee from and against any and all Expenses which Indemnitee incurs or becomes obligated to incur in connection with such Proceeding, to the fullest extent permitted by applicable law.

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

  • Confidentiality Agreements The parties hereto agree that this Agreement supersedes any provision of the Confidentiality Agreements that could be interpreted to preclude the exercise of any rights or the fulfillment of any obligations under this Agreement, and that none of the provisions included in the Confidentiality Agreements will act to preclude Holder from exercising the Option or exercising any other rights under this Agreement or act to preclude Issuer from fulfilling any of its obligations under this Agreement.

  • Legal Agreement This Software License Agreement (“Agreement”) is a legal agreement between the LICENSEE using the Cryptovision Software and Cryptovision. By using the Cryptovision Software LICENSEE agrees to be bound the terms and conditions of the Agreement. If LICENSEE does not agree with the terms of this Agreement, it may not use the Cryptovision Software and, if applicable, it must return the entire unused package to the reseller together with the receipt for a refund. The Software may include or be bundled with other software programs licensed under different terms and/or licensed by a licensor other than Cryptovision. Use of any software programs accompanied by a separate license agreement is governed by that separate license agreement. Cryptovision is not responsible for LICENSEE’s use of any third party software and shall have no liability for the use of third party software

  • Arrangement Agreement This Plan of Arrangement is made pursuant to, and is subject to the provisions of, the Arrangement Agreement, except in respect of the sequence of the steps comprising the Arrangement, which shall occur in the order set forth herein.

  • INTERLOCAL AGREEMENT This Agreement provides authority in addition to those vested by RCW 28A.310.200 and RCW 28A.320.080, is be deemed to be in satisfaction of the provisions of RCW 39.34, and is deemed a contract pursuant to RCW 39.34.080

  • DISCLOSURE AGREEMENT Contractors and each employee or subcontractor with access to State Data, as defined in the Master Agreement will be required to sign a standard State non-disclosure agreement if there is not already one on file. SCOPE OF WORK PURPOSE

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