Functioning of the LGB Sample Clauses

Functioning of the LGB. 3.1. Chair and Vice Chair 3.1.1. The members of the LGB may, for each school year, at their first meeting in that year, elect a Chair from among their number to serve until a successor is elected or a vacancy occurs. A person who is employed by the Company (whether or not at the Academy) shall not be eligible for election as Chair. 3.1.2. The members of the LGB may, for each school year, at their first meeting in that year, elect a vice-Chair from among their number to serve until a successor is elected or a vacancy occurs. Neither a person who is employed by the Company (whether or not at the Academy) nor a person who is at the time of election already a Director of the Company shall be eligible for election as vice-Chair. 3.1.3. Any election of a Chair or vice Chair which is contested shall be held by secret ballot. 3.1.4. The Chair or vice-Chair shall hold office as such until his successor has been appointed. 3.1.5. The Chair or vice-Chair may at any time resign his office by giving notice in writing to the Directors and to the LGB. 3.1.6. The Chair or vice-Chair shall cease to hold office if: s/he ceases to serve on the LGB; s/he is employed by the Company whether or not at the Academy; s/he is removed from office in accordance with paragraph 3.1.11 of this Scheme; or in the case of the vice-Chair, s/he is appointed in accordance with this Scheme to fill a vacancy in the office of Chair. 3.1.7. Where a vacancy arises in the office of Chair, the vice Chair shall fill that vacancy. 3.1.8. Where a vacancy arises in the office of vice-Chair, the members of the LGB shall at its next meeting elect one of their number to fill that vacancy. 3.1.9. Where the Chair is absent from any meeting the vice-Chair shall chair the meeting. 3.1.10. Where the vice-Chair is also absent from the meeting or there is at the time a vacancy in the office of vice-Chair, the members of the LGB shall elect one of their number to act as a Chair for the purposes of that meeting, provided that the person elected shall not be a person who is employed by the Company whether or not at the Academy. 3.1.11. A resolution to remove the Chair or the vice-Chair from office which is passed at a meeting of the LGB shall not have effect unless: it is confirmed by a resolution passed at a second meeting of the LGB held not less than fourteen days after the first meeting; and the matter of the removal from office of the Chair or vice-Chair is specified as an item of business on the agenda for each...
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs

Related to Functioning of the LGB

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • FUNCTIONS OF MANAGEMENT 4.01 The Union agrees that the Employer has the exclusive right and power to manage its business to direct the working forces and to suspend, discharge or discipline employees for just and sufficient cause, to hire, promote, demote, transfer or lay-off employees, to establish and maintain reasonable rules and regulations covering the operation of the stores, provided however, that any exercise of these rights and powers in conflict with any of the provisions of this Agreement shall be subject to the provisions of the Grievance Procedure as set out herein. 4.02 It is agreed that the direction of the working force shall be at the discretion of the Employer within the terms of this Agreement.

  • Commercially Useful Function A prime consultant can credit expenditures to a DBE subconsultant toward DBE goals only if the DBE performs a Commercially Useful Function (CUF). A DBE performs a CUF when it is responsible for execution of the work of a contract and carries out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the DBE must also be responsible, with respect to materials and supplies on the contract, for negotiating price, determining quality and quantity, ordering the material, and installing (where applicable) and paying for the material itself that it uses on the project. To determine whether a DBE is performing a commercially useful function, the Department will evaluate the amount of work subcontracted, industry practices, whether the amount the firm is to be paid under the contract is commensurate with the work it is actually performing and the DBE credit claimed for its performance of the work, and other relevant factors. A DBE will not be considered to perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of DBE participation. In determining whether a DBE is such an extra participant, the Department will examine similar transactions, particularly those in which DBEs do not participate. If a DBE does not perform or exercise responsibility for at least 30 percent of the total cost of its contract with its own work force, or if the DBE subcontracts a greater portion of the work of a contract than would be expected on the basis of normal industry practice for the type of work involved, the Department will presume that the DBE is not performing a commercially useful function. When a DBE is presumed not to be performing a commercially useful function as provided above, the DBE may present evidence to rebut this presumption. The Department will determine if the firm is performing a CUF given the type of work involved and normal industry practices. The Department will notify the consultant, in writing, if it determines that the consultant’s DBE subconsultant is not performing a CUF. The consultant will be notified within seven calendar days of the Department’s decision. Decisions on CUF may be appealed to the ADOT State Engineer. The appeal must be in writing and personally delivered or sent by certified mail, return receipt requested, to the State Engineer. The appeal must be received by the State Engineer no later than seven calendar days after the decision of XXXX. XXXX’s decision remains in place unless and until the State Engineer reverses or modifies BECO’s decision. ADOT State Engineer will promptly consider any appeals under this subsection and notify the consultant of ADOT’s State Engineer findings and decisions. Decisions on CUF matters are not administratively appealable to USDOT. The BECO may conduct project site visits on the contract to confirm that DBEs are performing a CUF. The consultant shall cooperate during the site visits and the BECO’s staff will make every effort not to disrupt work on the project.

  • Function It shall be the function of the Governing Board to uphold the Charter School’s mission and vision, to set policy for the Charter School, to work collaboratively with school officials to ensure the Charter School complies with the performance goals enumerated in Section 9 above, to ensure effective organizational planning, and to ensure financial stability of the Charter School.

  • Teams One team for the purposes of the Event shall consist of one Vehicle. Each Vehicle can contain a maximum of three Team Members, provided such Team Members have entered into a Team Entry Agreement with the Company or have otherwise agreed in writing to participate in the Event upon and subject to the Terms of Entry and the Event Rules. For the avoidance of doubt, it is the sole responsibility of each Team to inform themselves of the maximum numbers of persons legally permitted to travel in the Vehicle under Relevant Law. The Company shall provide each Team with the contact details of the Approved Hirer who will be able to provide each Team with a Vehicle for use in the Event, subject to the Team entering into an agreement (the "Borrowing Agreement") with the Hirer outlining the terms of use of the Vehicle. Should the Vehicle not be delivered to the Designated Finish Point by 14:00 local time on 19th September 2021, then the team will be liable for the "Hire Costs" outlined below. Each Vehicle will be of a similar specification to that outlined in Schedule 4 to the Team Entry Agreement. For the avoidance of doubt, the Company shall make no representations or warranties as to the suitability of the Approved Hirer or of the Vehicle for participation in the Event and any rights or warranties which a Team may have or be granted in relation to the Vehicle shall be limited to those contained in the Rental Agreement or implied by any Relevant Law.

  • Responsibility for Equipment City shall not be responsible for any damage to persons or property as a result of the use, misuse or failure of any equipment used by Contractor, or by any of its employees, even though such equipment be furnished, rented or loaned to Contractor by City.

  • CUTTING AND PATCHING OF WORK 4.14.1 The Contractor shall be responsible for all cutting, fitting or patching that may be required to complete the Work or to make its several parts fit together properly. 4.14.2 The Contractor shall not damage or endanger any portion of the Work or the work of the State or any separate contractors by cutting, patching or otherwise altering any work, or by excavation. The Contractor shall not cut or otherwise alter the work of the State or any separate contractor except with the written consent of the State and of such separate contractor. The Contractor shall not unreasonably withhold from the State or any separate contractor his consent to cutting or otherwise altering the Work.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • Radiation Therapy/Chemotherapy Services This plan covers chemotherapy and radiation services. This plan covers respiratory therapy services. When respiratory services are provided in your home, as part of a home care program, durable medical equipment, supplies, and oxygen are covered as a durable medical equipment service.

  • Review Systems; Personnel It will maintain business process management and/or other systems necessary to ensure that it can perform each Test and, on execution of this Agreement, will load each Test into these systems. The Asset Representations Reviewer will ensure that these systems allow for each Review Receivable and the related Review Materials to be individually tracked and stored as contemplated by this Agreement. The Asset Representations Reviewer will maintain adequate staff that is properly trained to conduct Reviews as required by this Agreement.

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