CREW Network Board Liaison Visits. Board liaisons (see Section 1.7 above) will visit Chapter every other year to meet in-person with Chapter’s board and deliver a CREW Network presentation at a chapter program (customized to Chapter needs).
CREW Network Board Liaison Visits Sample Clauses
Related to CREW Network Board Liaison Visits
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.
Training Committee The parties to this Agreement may form a Training Committee. The Training Committee will be constituted by equal numbers of Employer nominees and ETU employee representatives and have a charter which clearly states its role and responsibilities. It shall monitor the clauses of this Agreement which relate to training and ensure all employees have equal access to training.
Verizon Operations Support Systems Verizon systems for pre- ordering, ordering, provisioning, maintenance and repair, and billing.
Support Services Rehabilitation, counselling and EAP’s. Support is strictly non- punitive, and can be accessed at anytime (self-identification of the need for help is strongly encouraged).
Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition. 13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management
Online Services Microsoft warrants that each Online Service will perform in accordance with the applicable SLA during Customer’s use. Customer’s remedies for breach of this warranty are described in the SLA.
Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network or non- network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network or non-network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.
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.
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.
