Amenity Units: Fitness Facility License Agreement Sample Clauses

Amenity Units: Fitness Facility License Agreement. Purchaser acknowledges and agrees that (i) certain Condominium Units within the Project designated as an “Amenity Unit” in the Declaration and identified as “Amenity Unit A” and “Amenity Unit B” on the East Map are not Common Elements of the Project and shall be owned and operated by the owner of the applicable Amenity Unit, subject to the restrictions of the Declaration, (ii) Amenity Unit A will be initially owned and operated by Seller or an affiliate of Seller as it determines within its exclusive discretion, subject, however, to any requirements of the Declaration and the terms of that certain Fitness Facility License Agreement entered into between the Association and Seller (the “Fitness Facility License Agreement”), (iii) pursuant to the Fitness Facility License Agreement, Purchaser as owner of the Unit will enjoy certain access privileges while in residence and be subject to certain obligations, to the extent that the Fitness Facility License Agreement remains in full force and effect, and (iv) Amenity Unit A is subject to other license agreements with other associations and third parties who shall enjoy access rights and privileges to the Amenity Unit. Purchaser is advised to review the Fitness Facility License Agreement and any limitations and/or restrictions on such rights and the related obligations. Purchaser is also advised to review the applicable provisions of the Declaration related to the Amenity Units, which provisions include, without limitation, the obligation of the Association, at the election of the owner of either Amenity Unit, to accept a future conveyance of the applicable Amenity Unit and to operate such Amenity Unit in accordance with any restrictions and obligations to which such Amenity Unit is subject (e.g., the fitness facility license agreements then in effect for Amenity Unit A).
Sample 1Sample 2Sample 3See All (6)
AutoNDA by SimpleDocs

Related to Amenity Units: Fitness Facility License Agreement

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

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

  • 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 GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:

  • Enterprise License The large corporations with revenue more than $500 million and large government entities must purchase an Enterprise License. An Enterprise license is also applicable if any target customer of your product using the Software have revenue more than $500 million. Please contact us at xxxx@xxxxxxxxxx.xxx for a quote for an Enterprise License.

  • PROVISIONAL AGREEMENT RESULTING FROM INTERINSTITUTIONAL NEGOTIATIONS Subject: Proposal for a regulation of the European Parliament and of the Council on a Pan- European Personal Pension Product (PEPP) (COM(2017)0343 – C8-0219/2017 – 2017/0143(COD)) The interinstitutional negotiations on the aforementioned proposal for a regulation have led to a compromise. In accordance with Rule 69f(4) of the Rules of Procedure, the provisional agreement, reproduced below, is submitted as a whole to the Committee on Economic and Monetary Affairs for decision by way of a single vote. AG\1177088EN.docx PE634.848v01-00 EN United in diversity EN REGULATION (EU) 2019/... OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of ... on a pan-European Personal Pension Product (PEPP) (Text with EEA relevance) THE EUROPEAN PARLIAMENT AND THE COUNCIL OF THE EUROPEAN UNION, Having regard to the Treaty on the Functioning of the European Union, and in particular Article 114 thereof, Having regard to the proposal from the European Commission, After transmission of the draft legislative act to the national parliaments, Having regard to the opinion of the European Economic and Social Committee1, Acting in accordance with the ordinary legislative procedure2,

  • SOFTWARE LICENSE GRANT Where Product is acquired on a licensed basis the following shall constitute the license grant:

  • Business License Prior to commencement of work, Consultant shall obtain a business license from City.

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