No Management Sample Clauses

POPULAR SAMPLE Copied 1 times
No Management. Limited Partners shall not take any steps to interfere in the operation of the Partnership and shall have no right or authority to act for or bind the Partnership, including during the winding up period following dissolution of the Partnership, except that the Limited Partners may act for and bind the Partnership during the winding up period when the General Partner has been removed and their acts are first approved by a Majority.
No Management. The Limited Partner shall take no part in the management or control (within the meaning of the Act) of the Partnership's business and shall have no right or authority to act for the Partnership or to vote on Partnership matters other than as specifically set forth in this Agreement or as required under the Act.
No Management. A Member shall not be an agent of the LLC, nor can a Member bind, nor execute any instrument on behalf of, the LLC. A Member shall not participate in the management of the business or affairs of the LLC and, except as provided in this Agreement, shall not have any voting, consent or approval rights.
No Management. 7 ARTICLE IV - ADDITIONAL CAPTIAL CONTRIBUTIONS; NEW MEMBERS, PREEMPTIVE RIGHTS; CREDIT LINE...............................................7
No Management. Unit Holder may Transfer all or any part of such Member’s Interests except (i) in connection with a Liquidity Event, Covered Control Event or a Lazard Sale Event in order to give effect to such Liquidity Event, Covered Control Event or a Lazard Sale Event, (ii) pursuant to Section 9.3, or (iii) any Management Member may at any time Transfer all or any portion of his vested and non-forfeited Units (and a proportionate amount of his Capital) to his estate, direct descendents or, following the death of such Member, to a spouse, or to any trust for the benefit of such Member, his direct descendents or, following the death of such Member, a spouse, provided that, in the case of clause (iii), (A) the trustee and any successor trustees for any such trust are approved by the Lazard Board and (B) the Transferee executes and delivers to the Lazard Board an agreement in which the Transferee agrees to be bound by this Agreement and any other agreements, documents or instruments specified by the Board (each such Transferee described in this clause (iii), an “Estate Transferee”). Unless the Board otherwise determines, each Management Member who transfers Units to an Estate Transferee must transfer a proportionate amount of Capital to such Estate Transferee. An Estate Transferee pursuant to Section 9.2(b)(iii) shall become a Member, and shall be listed as a “Class A Member,” “Class B Member” and/or “Class C Member,” as applicable, on Schedule A, at such time as the events described in clauses (A) and (B) of such Section 9.2(b)(iii) shall have occurred.
No Management. Notwithstanding any other provisions of this Agreement, this paragraph shall govern. The parties acknowledge that this Agreement is not a management agreement or contract. All management decisions relating to the operation of the Casino shall be made by the Nation. The Nation shall have complete day-to-day management and control of every aspect of the operations of the Casino. The cost of resolution of any casino customer controversy relating to the Equipment shall be shared equally between the Nation and Evergreen.

Related to No Management

  • Portfolio Management Subject to supervision by Investment Manager and the Fund’s Board of Directors/Trustees (the “Board”), Subadviser shall manage the investment operations and the composition of that portion of the assets of the Fund which is allocated to Subadviser from time to time by Investment Manager (which portion may include any or all of the Fund’s assets), including the purchase, retention, and disposition thereof, in accordance with the Fund’s investment objectives, policies, and restrictions, and subject to the following understandings:

  • Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.

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

  • Patch Management All workstations, laptops and other systems that process and/or store County PHI or PI must have critical security patches applied, with system reboot if necessary. There must be a documented patch management process which determines installation timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable patches must be installed within 30 days of vendor release.

  • LABOUR MANAGEMENT RELATIONS 9:01 No employee or group of employees shall undertake to represent the Union at meetings with the Employer without the proper authorization of the Union. The Employer shall not meet with any employee or group of employees undertaking to represent the Union without the proper authorization of the Union. In representing an employee or group of employees, a representative of the Union shall be the spokesperson. In order that this may be carried out, the Union shall supply the Employer with the names of its Officers and representatives. Likewise the Employer shall supply the Union with a list of its Designated Authorities and Chairs where the Chair is not the Designated Authority. Neither the Union nor the Employer shall be required to recognize such representatives until written notification has been received. 9:02 The Union and the Employer acknowledge the mutual benefit of joint consultation and agree, therefore, that there shall be a joint labour/management committee consisting of three (3) representatives from and selected by each party. There shall be one (1) regularly scheduled Labour/Management Committee meeting in each four (4) month term or semester (January to April, May to August, September to December). In addition, meetings shall be arranged at the request of either party through the Labour Relations Department, by submitting in writing the topics to be discussed. Such meetings shall take place, at a mutually-agreeable time, within ten (10) working days of the receipt of the request for the meeting. Meetings shall not be used to discuss matters which are the subject of a grievance nor to discuss any matters which are, at the time, the subject of collective bargaining. The committee shall function in an advisory capacity only, making recommendations to the Union and/or the Employer with respect to its discussions and conclusions, and shall not have the power to add to or modify the terms of this agreement. A representative of each party shall be designated Co-Chairperson, and the two persons so designated shall alternate in presiding over meetings.