Provider License Agreement Format Sample Clauses

Provider License Agreement Format. If you have a License Agreement, then before submitting Software to Microchip, you will incorporate the License Agreement within the Software itself. With respect to Limited-Use Software, you are responsible to include (within the License Agreement) terms that restrict its use. You will provide any License Agreement in a click-wrap format with an “I Accept” icon or checkbox that requires the Client or its personnel to click or check the icon or checkbox to indicate agreement with the License Agreement’s terms before initially installing, running, or otherwise using the Software. Furthermore, you will ensure that the License Agreement will be easily accessible within the Software and printable by the Client at any time. If the Software or related documentation references a URL to your website that displays the License Agreement (the “License Agreement URL”), you will ensure that the License Agreement URL will always publically display the entire License Agreement and allow it to be printed. In addition, if you provide Microchip the License Agreement URL, Microchip may display it on the eStore’s webpage(s) as a hyperlink to your website, provided there are no technical problems. For clarity, Microchip has no obligation to check, track, or keep records of whether a Client has clicked or checked the “I Accept” icon or checkbox, or otherwise agreed with the License Agreement.
Sample 1
AutoNDA by SimpleDocs
Provider License Agreement Format. (1) This paragraph applies if the License Agreement is included within the Software itself. You will provide any License Agreement in a click-wrap format with an “I Accept” icon or checkbox that requires the Client or its personnel to click or check the icon or checkbox to indicate agreement with the License Agreement’s terms before initially installing, running, or otherwise using the Software. Furthermore, you will ensure that the License Agreement will be easily accessible within the Software and printable by the Client at any time. If the Software or related documentation references a URL to your website that displays the License Agreement (the “License Agreement URL”), you will ensure that the License Agreement URL will always publically display the entire License Agreement and allow it to be printed. In addition, if you provide Microchip the License Agreement URL, you will ensure that the terms posted on the License Agreement URL are consistent with the terms in the License Agreement included within the Software. Microchip may, at its sole discretion, display the License Agreement URL on the eStore’s webpage(s) as a hyperlink to your website, provided there are no technical problems. For clarity, Microchip has no obligation to check, track, or keep records of whether a Client has clicked or checked the “I Accept” icon or checkbox, or otherwise agreed with the License Agreement.
Sample 1

Related to Provider License Agreement Format

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

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

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

  • Server License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license to internally use and install the Software on the number of Server(s) listed in the Order Form for Commercial purposes. Unless stated otherwise in the Order Form, for the purposes of this license grant, you may install the Software on one (1) Machine as a substitute for, and not in addition to, one (1) Server. The total count of Server(s) where the Software is installed must not exceed the number of licenses purchased on the applicable Order Form(s).

  • Services Agreement “Services Agreement” shall mean any present or future agreements, either written or oral, between Covered Entity and Business Associate under which Business Associate provides services to Covered Entity which involve the use or disclosure of Protected Health Information. The Services Agreement is amended by and incorporates the terms of this BA Agreement.

  • Developer License We grant you a non-assignable, non-sublicensable, non-exclusive, worldwide right and license for the number of Developer(s) indicated in the Order Form to install the Software on any number of Machines in order to internally use the Software to create, develop and test Applications. For clarity, a single Software license may be re-allocated to another Developer in the event that the original Developer is no longer employed by you or has been assigned to a new role where access to the Software will no longer be required on a permanent basis.

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

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

  • Modification of Licensed Materials The Participating Institutions or the Authorized Users shall not modify or manipulate the Licensed Materials without the prior written permission of the Licensor.

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