Operate Cloud 9 Establishment Sample Clauses

Operate Cloud 9 Establishment. Developer covenants and agrees by January 1, 2025, and during the Term of this Agreement to keep open to the general public the Cloud 9 Hair Salon Establishment located on the Property.
AutoNDA by SimpleDocs

Related to Operate Cloud 9 Establishment

  • PERMANENT ESTABLISHMENT 1. For the purposes of this Agreement, the term "permanent establishment" means a fixed place of business through which the business of an enterprise is wholly or partly carried on. 2. The term "permanent establishment" includes especially: (a) a place of management; (b) a branch; (c) an office; (d) a factory; (e) a workshop, and (f) a mine, an oil or gas well, a quarry or any other place of extraction of natural resources. 3. The term "permanent establishment" also includes: (a) a building site, a construction, installation or assembly project, or supervisory activities in connection therewith, but only where such site, project or activities last more than 12 months; (b) the furnishing of services, including consultancy services, by an enterprise of a Contracting State through employees or other personnel in the other Contracting State for a period or periods aggregating more than 120 days within any twelve-month period. 4. Notwithstanding the preceding provisions of this Article, the term "permanent establishment" shall be deemed not to include: (a) the use of facilities solely for the purpose of storage, display or delivery of goods or merchandise belonging to the enterprise; (b) the maintenance of a stock of goods or merchandise belonging to the enterprise solely for the purpose of storage, display or delivery; (c) the maintenance of a stock of goods or merchandise belonging to the enterprise solely for the purpose of processing by another enterprise; (d) the maintenance of a fixed place of business solely for the purpose of purchasing goods or merchandise or of collecting information, for the enterprise; (e) the maintenance of a fixed place of business solely for the purpose of carrying on, for the enterprise, any other activity of a preparatory or auxiliary character; (f) the maintenance of a fixed place of business solely for any combination of activities mentioned in sub-paragraphs (a) to (e), provided that the overall activity of the fixed place of business resulting from this combination is of a preparatory or auxiliary character. 5. Notwithstanding the provisions of paragraphs 1 and 2, where a person -- other than an agent of an independent status to whom paragraph 6 applies -- is acting on behalf of an enterprise and has, and habitually exercises, in a Contracting State an authority to conclude contracts in the name of the enterprise, that enterprise shall be deemed to have a permanent establishment in that State in respect of any activities which that person undertakes for the enterprise, unless the activities of such person are limited to those mentioned in paragraph 4 which, if exercised through a fixed place of business, would not make this fixed place of business a permanent establishment under the provisions of that paragraph. 6. An enterprise shall not be deemed to have a permanent establishment in a Contracting State merely because it carries on business in that State through a broker, general commission agent or any other agent of an independent status, provided that such persons are acting in the ordinary course of their business. 7. The fact that a company which is a resident of a Contracting State controls or is controlled by a company which is a resident of the other Contracting State, or which carries on business in that other State (whether through a permanent establishment or otherwise), shall not of itself constitute either company a permanent establishment of the other.

  • Information Systems Acquisition Development and Maintenance a. Client Data – Client Data will only be used by State Street for the purposes specified in this Agreement.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan. 9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan. 9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work. 9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right 9.2.4.1 Issue Directive Letters to Developer regarding traffic management 9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.

  • Local Health Integration Networks and Restructuring In the event of a health service integration with another service provider the Employer and the Union agree to meet. (a) The Employer shall notify affected employees and the Union as soon as a formal decision to integrate is taken. (b) The Employer and the Union shall begin discussions concerning the specifics of the integration forthwith after a decision to integrate is taken. (c) As soon as possible in the course of developing a plan for the implementation of the integration the Employer shall notify affected employees and the Union of the projected staffing needs, and their location.

  • International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • ACADEMY OPENING DATE The Academy shall open as a school on 1 April 2011 replacing Xxxxxxx School which shall cease to be maintained by the Local Authority on that date, which date shall be the conversion date within the meaning of the Academies Xxx 0000.

  • Employee Facilities Employee Facilities. Restrooms and attendant facilities shall be provided as required in the orders and regulations of the State of Washington Department of Labor and Industries. A good faith effort will be made by the Employer to provide facilities for employees’ personal belongings.

  • Operation of the Business Except as set forth on Section 10.1 of the Sentech Disclosure Schedule, as contemplated by this Agreement or as expressly agreed to in writing by Sensec and Ensec, during the period from the date of this Agreement to the Effective Time, Sentech and its Subsidiaries will conduct their operations only in the ordinary course of business consistent with sound financial, operational and regulatory practice, and will take no action which would materially adversely affect their ability to consummate the Transactions. Without limiting the generality of the foregoing, except as otherwise expressly provided in this Agreement or except as disclosed in the Sentech Disclosure Schedule, prior to the Effective Time, neither Sentech nor any of its Subsidiaries will, without the prior written consent of Sensec and Ensec: (a) amend its Charter Documents or bylaws (or similar organizational documents); (b) authorize for issuance, issue, sell, deliver, grant any options for, or otherwise agree or commit to issue, sell or deliver any shares of its capital stock or any other securities, other than pursuant to and in accordance with the terms of any Existing Options or Sentech Warrants listed on the Sentech Disclosure Schedule; (c) recapitalize, split, combine or reclassify any shares of its capital stock; declare, set aside or pay any dividend or other distribution (whether in cash, stock or property or any combination thereof) in respect of its capital stock; or purchase, redeem or otherwise acquire any of its or its Subsidiaries' securities or modify any of the terms of any such securities; (d) (i) create, incur, assume or permit to exist any long-term debt or any short-term debt for borrowed money other than under existing notes payable, lines of credit or other credit facilities or in the ordinary course of business, or with respect to its Wholly-Owned Subsidiaries in the ordinary course of business; (ii) assume, guarantee, endorse or otherwise become liable or responsible (whether directly, contingently or otherwise) for the obligations of any other Person except its Wholly-Owned Subsidiaries in the ordinary course of business or as otherwise may be contractually required and disclosed in the Sentech Disclosure Schedule; or (iii) make any loans, advances or capital contributions to, or investments in, any other Person except its Wholly-Owned Subsidiaries; (i) amend any Sentech Benefit Plan or (ii) except in the ordinary course of business consistent with usual practice or established policy (a) increase in any manner the rate of compensation of any of its directors, officers or other employees everywhere, except for increases in the ordinary course of business; (b) pay or agree to pay any bonus, pension, retirement allowance, severance or other employee benefit except as required under currently existing Sentech Benefit Plans disclosed in the Sentech Disclosure Schedule or in the ordinary course of business; or (c) amend, terminate or enter into any employment, consulting, severance, change in control or similar agreements or arrangements with any of its directors, officers or other employees; (f) enter into any material agreement, commitment or contract, except agreements, commitments or contracts for the purchase, sale or lease of goods or services in the ordinary course of business; (g) other than in the ordinary course of business, authorize, recommend, propose or announce an intention to authorize, recommend or propose, or enter into any Contract with respect to, any (i) plan of liquidation or dissolution, (ii) acquisition of a material amount of assets or securities, (iii) disposition or Encumbrance of a material amount of assets or securities, (iv) merger or consolidation or (v) material change in its capitalization; (h) change any material accounting or Tax procedure or practice; (i) take any action the taking of which, or knowingly omit to take any action the omission of which, would cause any of the representations and warranties herein to fail to be true and correct in all material respects as of the date of such action or omission as though made at and as of the date of such action or omission; (j) compromise, settle or otherwise modify any material claim or litigation not identified in the Sentech Disclosure Schedule; or (k) commit or agree to do any of the foregoing.

  • Operational Control Directing the operation of the Transmission Facilities Under ISO Operational Control to maintain these facilities in a reliable state, as defined by the Reliability Rules. The ISO shall approve operational decisions concerning these facilities, made by each Transmission Owner before the Transmission Owner implements those decisions. In accordance with ISO Procedures, the ISO shall direct each Transmission Owner to take certain actions to restore the system to the Normal State. Operational Control includes security monitoring, adjustment of generation and transmission resources, coordination and approval of changes in transmission status for maintenance, determination of changes in transmission status for reliability, coordination with other Control Areas, voltage reductions and Load Shedding, except that each Transmission Owner continues to physically operate and maintain its facilities.

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