AEWA Action- and Management-Planning Process Sample Clauses

AEWA Action- and Management-Planning Process. Introduction In addition to the Framework for AEWA International Species Action and Management Plans as outlined above, this chapter also runs through the main steps of the actual action- and management-planning process itself, which is carried out by the selected lead compiler(s) or drafting team, in close cooperation with the UNEP/AEWA Secretariat. AEWA International Species Action and Management Plans are adopted by the Meeting of the AEWA Parties. But before a Plan reaches the stage of being presented for adoption, it has undergone a long development process beginning with the prioritization of the species/population in question for an Action or Management Plan by the AEWA Technical Committee to an internationally negotiated Plan ready for presentation to the AEWA governing bodies and adoption by the Parties. The action- and management-planning process as described below has been developed under the Agreement in an effort to ensure a transparent process that includes all relevant stakeholders and brings together the best available scientific knowledge. Both of these elements – the transparent and inclusive process as well as working on the basis of best available science – are crucial steps for enabling the subsequent implementation of International Species Action as well as Management Plans once adopted. It should be noted that action- and management-planning under AEWA remains an evolving process as the Agreement bodies as well as all involved partners continue to learn and introduce improvements over time. As these are international, consultative processes mainly dependent on the availability of external funding, the exact timetables etc. will also vary from case to case. The main steps as well as the roles and responsibilities of each of the various actors in the process, however, remain the same. As this guidance is geared in particular towards potential International Species Action or Management compilers and/or drafting teams, the NINE essential steps requiring their involvement are highlighted throughout the process below. Facilitation of Action- and Management-Planning Processes under AEWA
AutoNDA by SimpleDocs

Related to AEWA Action- and Management-Planning Process

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Project Management Plan 1 3.4.1 Developer is responsible for all quality assurance and quality control 2 activities necessary to manage the Work, including the Utility Adjustment Work.

  • Procurement Planning Prior to the issuance of any invitations to bid for contracts, the proposed procurement plan for the Project shall be furnished to the Association for its review and approval, in accordance with the provisions of paragraph 1 of Appendix 1 to the Guidelines. Procurement of all goods and works shall be undertaken in accordance with such procurement plan as shall have been approved by the Association, and with the provisions of said paragraph 1.

  • Approval Process Tenant shall notify Landlord whether it approves of the submitted working drawings within three business days after Landlord’s submission thereof. If Tenant disapproves of such working drawings, then Tenant shall notify Landlord thereof specifying in reasonable detail the reasons for such disapproval, in which case Landlord shall, within five business days after such notice, revise such working drawings in accordance with Tenant’s objections and submit the revised working drawings to Tenant for its review and approval. Tenant shall notify Landlord in writing whether it approves of the resubmitted working drawings within one business day after its receipt thereof. This process shall be repeated until the working drawings have been finally approved by Landlord and Tenant. If Tenant fails to notify Landlord that it disapproves of the initial working drawings within three business days (or, in the case of resubmitted working drawings, within one business day) after the submission thereof, then Tenant shall be deemed to have approved the working drawings in question. Any delay caused by Tenant’s unreasonable withholding of its consent or delay in giving its written approval as to such working drawings shall constitute a Tenant Delay Day (defined below). If the working drawings are not fully approved (or deemed approved) by both Landlord and Tenant by the 15th business day after the delivery of the initial draft thereof to Tenant, then each day after such time period that such working drawings are not fully approved (or deemed approved) by both Landlord and Tenant shall constitute a Tenant Delay Day.

  • Program Monitoring The Contractor will make all records and documents required under this Agreement as outlined here, in OEC Policies and NHECC Policies available to the SRO or its designee, the SR Fiscal Officer or their designee and the OEC. Scheduled monitoring visits will take place twice a year. The SRO and OEC reserve the right to make unannounced visits.

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Change Management Process If Customer or Oracle requests a change in any of the specifications, requirements, Deliverables, or scope (including drawings and designs) of the Professional Services described in any Statement of Work, the party seeking the change shall propose the applicable changes by written notice. Within forty-eight (48) hours of receipt of the written notice, each party’s project leads shall meet, either in person or via telephone conference, to discuss and agree upon the proposed changes. Oracle will prepare a change order describing the proposed changes to the Statement of Work and the applicable change in fees and expenses, if any (each, a “Change Order”). Change Orders are not binding unless and until they are executed by both parties. Executed Change Orders shall be deemed part of, and subject to, this Addendum. If the parties disagree about the proposed changes, the parties shall promptly escalate the change request to their respective senior management for resolution.

  • Program Management 1.1.01 Implement and operate an Immunization Program as a Responsible Entity

Time is Money Join Law Insider Premium to draft better contracts faster.