Problem analysis for Action Plans with a recovery objective Sample Clauses

Problem analysis for Action Plans with a recovery objective. In the case of recovery plans the problem analysis focuses on the direct threats to the species/population. In case of plans for single species, problems should be identified together but evaluated for each population separately. In case of multi-species plans, problems should be assessed for each species separately and summarised. Threats should be listed if they are known (or have the realistic potential) to cause population decline. Only those threats for which specific actions will be developed should be described in the Action Plan. Threats of a more global character (e.g. climate change, avian influenza and others) - if important - should be mentioned in the threats overview paragraph. However, the Action Plan itself has a limited role to play in addressing such large-scale environmental changes and usually it is not practical to include general policy actions into the Plans. The identified threats should be presented in descending order of priority according to their impact on the population. Hence, their listing in the Plan is a result of the threat prioritisation process which took part during the development of the Action Plan - especially during the action-planning workshop.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs

Related to Problem analysis for Action Plans with a recovery objective

  • Constructability Review Prepare detailed interdisciplinary constructability review within Fourteen (14) days of receipt of the plans from the District that: 10.1.2.1.6.1 Ensures construction documents are well coordinated and reviewed for errors; 10.1.2.1.6.2 Identifies to the extent known, construction deficiencies and areas of concern; 10.1.2.1.6.3 Back-checks design drawings for inclusion of modifications; and 10.1.2.1.6.4 Provides the District with written confirmation that: 10.1.2.1.6.4.1 Requirements noted in the design documents prepared for the Project are consistent with and conform to the District's Project requirements and design standards. 10.1.2.1.6.4.2 Various components have been coordinated and are consistent with each other so as to minimize conflicts within or between components of the design documents.

  • Investment Analysis and Implementation In carrying out its obligations under Section 1 hereof, the Advisor shall: (a) supervise all aspects of the operations of the Funds; (b) obtain and evaluate pertinent information about significant developments and economic, statistical and financial data, domestic, foreign or otherwise, whether affecting the economy generally or the Funds, and whether concerning the individual issuers whose securities are included in the assets of the Funds or the activities in which such issuers engage, or with respect to securities which the Advisor considers desirable for inclusion in the Funds' assets; (c) determine which issuers and securities shall be represented in the Funds' investment portfolios and regularly report thereon to the Board of Trustees; (d) formulate and implement continuing programs for the purchases and sales of the securities of such issuers and regularly report thereon to the Board of Trustees; and (e) take, on behalf of the Trust and the Funds, all actions which appear to the Trust and the Funds necessary to carry into effect such purchase and sale programs and supervisory functions as aforesaid, including but not limited to the placing of orders for the purchase and sale of securities for the Funds.

  • ADB’s Review of Procurement Decisions 11. All contracts procured under international competitive bidding procedures and contracts for consulting services shall be subject to prior review by ADB, unless otherwise agreed between the Borrower and ADB and set forth in the Procurement Plan.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

  • Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.

  • Review Systems The Asset Representations Reviewer will maintain and utilize an electronic case management system to manage the Tests and provide systematic control over each step in the Review process and ensure consistency and repeatability among the Tests.

  • Claims Review Methodology ‌‌ a. C laims Review Population. A description of the Population subject‌‌ to the Quarterly Claims Review.

  • Evaluation, Testing, and Monitoring 1. The System Agency may review, test, evaluate and monitor Grantee’s Products and services, as well as associated documentation and technical support for compliance with the Accessibility Standards. Review, testing, evaluation and monitoring may be conducted before and after the award of a contract. Testing and monitoring may include user acceptance testing. Neither the review, testing (including acceptance testing), evaluation or monitoring of any Product or service, nor the absence of review, testing, evaluation or monitoring, will result in a waiver of the State’s right to contest the Grantee’s assertion of compliance with the Accessibility Standards. 2. Grantee agrees to cooperate fully and provide the System Agency and its representatives timely access to Products, records, and other items and information needed to conduct such review, evaluation, testing, and monitoring.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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