License Agreement Summary Sample Clauses

License Agreement Summary. The following summary contains an overview of the key points of the Agreement. Note that this summary should not be considered a complete, accurate, and binding description of the terms and conditions of the Agreement. The summary is merely provided for your personal convenience, and does not bind you or Altsoft in any way. The terms and conditions described below under the heading Full License Agreement constitute the only legally valid and binding elements of the Agreement. • Licenses are PER CUSTOMER. The XML2PDF API Company Wide license entitles you to: o make [x] copies of the Software on a maximum of [x] machines (hereafter referred to as “Development Systems”). On each Development System, the Software may be integrated in unmodified form into your own software (hereafter referred to as the “Non-Altsoft Code”). Note that the license allows up to [x] people to work simultaneously on the development on up to [x] Development Systems, but only if: ▪ All developers who come into contact with the Software source code are employed exclusively by you. Specifically, no development work may be done on the Development Systems by independent contractors, interns, trainees, volunteers, or employees who are engaged in part-time employment for a different employer than you, if this development work allows them access to the Software source code. ▪ Additionally, all Development Systems must be under your exclusive control, either as a result of your exclusive ownership of the Development Systems, or following an exclusive lease agreement or similar arrangement which precludes any and all third parties from accessing any information on your system without your prior knowledge and consent, or without a legal requirement to comply with the binding orders of any regulatory authority or as required by law or by judicial decree. o run one copy of the Non-Altsoft Code containing the integrated Software on one machine (hereafter referred to as the “Runtime System”). The Runtime System may be used as a server, including as a web server if desired, and the license allows an unlimited amount of users to use the Non-Altsoft Code containing the integrated Software through the Runtime System. • However, you may not sell and/or redistribute the Software in any form, including after integration into any Non-Altsoft Code, as the license is non-transferable. Should you wish to redistribute any Non-Altsoft Code containing the Software, you will need to acquire a redistributable licens...
AutoNDA by SimpleDocs
License Agreement Summary. The following summary contains an overview of the key points of the Agreement. Note that this summary should not be considered a complete, accurate, and binding description of the terms and conditions of the Agreement. The summary is merely provided for your personal convenience, and does not bind you or Altsoft in any way. The terms and conditions described below under the heading Full License Agreement constitute the only legally valid and binding elements of the Agreement. • Licenses are PER CUSTOMER. A single license entitles you to: o make one copy of the Software on one machine (hereafter referred to as the “Development System”). On the Development System, the Software may be integrated in unmodified form into your own software (hereafter referred to as the “Non-Altsoft Code”). Note that the license allows multiple people to work on the development on the Development System, but not simultaneously. Only one person at a time may work on integrating the Software into the Non-Altsoft Code. If you wish for additional developers to work on the development process simultaneously, or if you wish to copy the Software on other machines than the Development System, you will need to acquire additional developer licenses from Altsoft (contact xxxxx@xxx-xxxx.xxx ).
License Agreement Summary. Shionogi has granted GARDP a non-exclusive and sub-licensable license for cefiderocol in the territory outlined below (“Territory”) to develop, register, manufacture and commercialize cefiderocol, all in accordance with the terms of the agreement. Territory technology transfer The Territory covers 135 countries, almost 70% of countries worldwide, including countries with some of the highest burden of infections due to resistant pathogens for which cefiderocol is indicated. The license agreement will include the payment of cost recoupment fees to Shionogi on net sales made in certain parts of the Territory: • High-income countries: 9% • Upper middle-income countries: 5% • Lower middle-income countries: 0% • Low-income countries: 0% Technology transfer and intellectual property If a manufacturer requests a technology transfer, Shionogi will provide one technology transfer of its manufacturing process, including relevant know-how, to one manufacturing sub-licensee (or, if the manufacturers of the active pharmaceutical ingredient (API) and finished pharmaceutical product are different, then one technology transfer covering the complete development from API to finished pharmaceutical product, but to two different manufacturers). In addition, Shionogi will provide access to documents and necessary rights of referral to enable product registrations at national regulatory bodies and at the WHO Prequalification Programme (PQ). Additional and subsequent sublicensees will be provided relevant technology transfer, including documentation, by either GARDP (including via a third party), CHAI, or the sublicensee that received the initial technology transfer.
License Agreement Summary. The License Agreement Term is the length of time between the Starting Date and the Ending Date. Starting Date is XXXXX XX, 20XX and the Ending Date is XXXX XX, 20XX. The Resident’s assigned space shall be used and occupied by Resident for residential purposes only. The Residence Life Staff at Massachusetts College of Art and Design shall assign Resident to the Premises at the beginning of the Term; provided, however, that the College reserves the right to reassign Resident to other accommodations for cause(s) deemed sufficient by the Office of Housing and Residence Life. In the event of reassignment, this Agreement will remain in effect and will apply to the Resident’s occupancy of that other space, the College will provide the Resident with ten (10) days written notice in the event that it elects to reassign the Resident to another bedroom. This Agreement is for a bedroom, and at no time shall be interpreted to refer to a specific unit within the building. The College will determine the specific Bedroom and Unit Number on or before the Starting Date.
License Agreement Summary. The following summary contains an overview of the key points of the Agreement. Note that this summary should not be considered a complete, accurate, and binding description of the terms and conditions of the Agreement. The summary is merely provided for your personal convenience, and does not bind you or Altsoft in any way. The terms and conditions described below under the heading Full License Agreement constitute the only legally valid and binding elements of the Agreement. • Licenses are PER CUSTOMER. A single redistributable license license entitles you to: o Install the software on as much servers/computers as needed; clients included. o Sell and/or redistribute the Software in any form, including after integration into any Non-Altsoft Code. • The Software is provided on an AS-IS BASIS, without any warranties, express, implied or statutory, with regard to merchantability or fitness for a particular purpose, except where expressly provided otherwise in the Full License Agreement or as required by law. • The Agreement entitles you to no support as support is provided on a per ticket or per hour basis. • The validity and interpretation of the Agreement is EXCLUSIVELY SUBJECT TO BELGIAN LAW, and any disputes resulting from or in connection to the Agreement may be only be presented before the competent courts of Leuven, Belgium.

Related to License Agreement Summary

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

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

  • End User License Agreement This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License. xxxx://xxxxxxxxxxxxxxx.xxx/licenses/by-nc-nd/3.0/ You are free to: Share: to copy, distribute and transmit the work Under the following conditions: Attribution: You must attribute the work in the manner specified by the author (but not in any way that suggests that they endorse you or your use of the work).

  • Client Agreement 2.1. The Company may unilaterally change any terms of this Client Agreement for any of the following reasons:

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient.

  • Agreement Scope The scope of this Agreement is as prescribed in section 46 of the Act, setting out: • the health services to be provided to the State by the HSP, • the TTR in support of the health services to be provided, • the funding to be provided to the HSP for the provision of the health services, including the way in which the funding is to be provided, • the performance measures and operational targets for the provision of the health services by the HSP, • how the evaluation and review of results in relation to the performance measures and operational targets is to be carried out, • the performance data and other data to be provided by the HSP to the Department CEO, including how, and how often, the data is to be provided, and • any other matter the Department CEO considers relevant to the provision of the health services by the HSP. Where appropriate, reference will be made in this Agreement to Policy Frameworks issued by the Department CEO pursuant to Part 3, Division 2 of the Act.

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

  • License Terms This license is for one full Semester. It cannot be cancelled or terminated except under the conditions cited in this license.

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

  • Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.

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