Regional Programme Director Sample Clauses

Regional Programme Director. 11.2.1 The Regional Programme Director shall attend the Joint Committee meetings but shall not have the right to vote on any Joint Committee Matters. 11.2.2 The Regional Programme Director shall have decision making powers delegated to them personally (and not the Programme Board) pursuant to Schedule 1 (Delegations Policy). 11.2.3 Where the Regional Programme Director exercises any decision making powers, the Regional Programme Director shall first consult with the Chairperson of the Joint Committee and the relevant Joint Committee portfolio lead.
AutoNDA by SimpleDocs

Related to Regional Programme Director

  • Educational Program A. DSST PUBLIC SCHOOLS shall implement and maintain the following characteristics of its educational program in addition to those identified in the Network Contract at DSST XXXX MIDDLE SCHOOL (“the School” within Exhibit A-3). These characteristics are subject to modification with the District’s written approval:

  • Technical Committee 1. The Technical Committee shall comprise: (a) nine experts representing different regions of the Agreement Area, in accordance with a balanced geographical distribution; (b) one representative from the International Union for Conservation of Nature and Natural Resources (IUCN), one from the International Waterfowl and Wetlands Research Bureau (IWRB) and one from the International Council for Game and Wildlife Conservation (CIC); and (c) one expert from each of the following fields: rural economics, game management, and environmental law. The procedure for the appointment of the experts, the term of their appointment and the procedure for designation of the Chairman of the Technical Committee shall be determined by the Meeting of the Parties. The Chairman may admit a maximum of four observers from specialized international inter- governmental and non-governmental organizations. 2. Unless the Meeting of the Parties decides otherwise, meetings of the Technical Committee shall be convened by the Agreement secretariat in conjunction with each ordinary session of the Meeting of the Parties and at least once between ordinary sessions of the Meeting of the Parties. 3. The Technical Committee shall: (a) provide scientific and technical advice and information to the Meeting of the Parties and, through the Agreement secretariat, to Parties; (b) make recommendations to the Meeting of the Parties concerning the Action Plan, implementation of the Agreement and further research to be carried out; (c) prepare for each ordinary session of the Meeting of the Parties a report on its activities, which shall be submitted to the Agreement secretariat not less than one hundred and twenty days before the session of the Meeting of the Parties, and copies shall be circulated forthwith by the Agreement secretariat to the Parties; and (d) carry out any other tasks referred to it by the Meeting of the Parties. 4. Where in the opinion of the Technical Committee there has arisen an emergency which requires the adoption of immediate measures to avoid deterioration of the conservation status of one or more migratory waterbird species, the Technical Committee may request the Agreement secretariat to convene urgently a meeting of the Parties concerned. These Parties shall meet as soon as possible thereafter to establish rapidly a mechanism to give protection to the species identified as being subject to particularly adverse threat. Where a recommendation has been adopted at such a meeting, the Parties concerned shall inform each other and the Agreement secretariat of measures they have taken to implement it, or of the reasons why the recommendation could not be implemented. 5. The Technical Committee may establish such working groups as may be necessary to deal with specific tasks.

  • Executive Director (a) The HMO must employ a qualified individual to serve as the Executive Director for its HHSC HMO Program(s). Such Executive Director must be employed full-time by the HMO, be primarily dedicated to HHSC HMO Program(s), and must hold a Senior Executive or Management position in the HMO’s organization, except that the HMO may propose an alternate structure for the Executive Director position, subject to HHSC’s prior review and written approval. (b) The Executive Director must be authorized and empowered to represent the HMO regarding all matters pertaining to the Contract prior to such representation. The Executive Director must act as liaison between the HMO and the HHSC and must have responsibilities that include, but are not limited to, the following: (1) ensuring the HMO’s compliance with the terms of the Contract, including securing and coordinating resources necessary for such compliance; (2) receiving and responding to all inquiries and requests made by HHSC related to the Contract, in the time frames and formats specified by HHSC. Where practicable, HHSC must consult with the HMO to establish time frames and formats reasonably acceptable to the Parties; (3) attending and participating in regular HHSC HMO Executive Director meetings or conference calls; (4) attending and participating in regular HHSC Regional Advisory Committees (RACs) for managed care (the Executive Director may designate key personnel to attend a RAC if the Executive Director is unable to attend); (5) making best efforts to promptly resolve any issues identified either by the HMO or HHSC that may arise and are related to the Contract; (6) meeting with HHSC representative(s) on a periodic or as needed basis to review the HMO’s performance and resolve issues, and (7) meeting with HHSC at the time and place requested by HHSC, if HHSC determines that the HMO is not in compliance with the requirements of the Contract.

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

  • Training Program It is agreed that there shall be an Apprenticeship Training Program, the provisions of which are set forth in Exhibit "D", which is attached hereto and forms part of this Agreement.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • COMMERCIAL REUSE OF SERVICES The member or user herein agrees not to replicate, duplicate, copy, trade, sell, resell nor exploit for any commercial reason any part, use of, or access to 's sites.

  • Professional Development Program (a) The parties agree to continue a Professional Development Program for the maintenance and development of the faculty members' professional competence and effectiveness. It is agreed that maintenance of currency of subject knowledge, the improvement of performance of faculty duties, and the maintenance and improvement of professional competence, including instructional skills, are the primary professional development activities of faculty members. (b) Information collected as part of this program shall be the sole property of the faculty member. This information or any judgments arising from this program shall not be used to determine non-renewal or termination of a faculty member's contract, suspension or dismissal of a faculty member, denial of advancement on the salary scale, nor affect any other administrative decisions pertaining to the promotion or employment status of the faculty member. (c) A joint advisory committee consisting of three regular faculty members who shall be elected by and are P.D. Committee Chairpersons and three administrators shall make recommendations for the operation, financing and management of the Professional Development Program.

  • Stock Plan Administration Service Provider The Company transfers the Optionee's Personal Information to Fidelity Stock Plan Services LLC, an independent service provider based in the United States, which assists the Company with the implementation, administration and management of the Plan (the “Stock Plan Administrator”). In the future, the Company may select a different Stock Plan Administrator and share the Optionee's Personal Information with another company that serves in a similar manner. The Stock Plan Administrator will open an account for the Optionee to receive and trade Shares acquired under the Plan. The Optionee will be asked to agree on separate terms and data processing practices with the Stock Plan Administrator, which is a condition to the Optionee’s ability to participate in the Plan.

  • TRAINING AND EMPLOYEE DEVELOPMENT 9.1 The Employer and the Union recognize the value and benefit of education and training designed to enhance an employee’s ability to perform their job duties. Training and employee development opportunities will be provided to employees in accordance with Employer policies and available resources. 9.2 Attendance at employer-required training will be considered time worked. The Employer will make reasonable attempts to schedule employer-required training during an employee’s regular work shift. The Employer will pay the registration and associated travel costs in accordance with Article 23, Travel, for employer-required training.

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