ESA Recovery Plans Sample Clauses

ESA Recovery Plans a. Bull Trout and Steelhead On June 10, 1998, the U.S. Fish and Wildlife Service (“USFWS”) listed the bull trout (Salvelinus confluentus) Columbia River Distinct Population Segment (“DPS”) as a threatened species under the Endangered Species Act (“ESA”) (63 FR 31647). This DPS was also included in the November 1, 1999, listing for bull trout in the coterminous United States (64 FR 58909). Subpopulations in the Deschutes River are included in this listing. In November 2002, the USFWS proposed designation of critical habitat for the Klamath River and Columbia River distinct population segments of bull trout (50 CFR Part 17, RIN 1018-AI52). For the Columbia River DPS, the proposed critical habitat designation totals approximately 29,251 km (18,175 miles) of streams, including 5,460 km (3,391 miles) of streams and 18,077 ha (44,670 ac) of lakes and reservoirs in Oregon. Critical habitat proposed for the Lower Deschutes River subunit (extending from Big Falls on the middle Deschutes River above the Project to the confluence with the Columbia River) includes the lower Deschutes River and tributaries; the Project reservoirs; and the Metolius, Deschutes, and Crooked rivers (and their tributaries) above the Project. A recovery plan for the Deschutes Recovery Unit has been prepared by the USFWS in conjunction with the Deschutes Recovery Unit Team (USFWS 2002). The goal of the Deschutes bull trout recovery plan is to “ensure the long-term persistence of self-sustaining complex interacting groups of bull trout distributed throughout the species’ native range, so that the species can be delisted.” The recovery plan establishes several objectives toward achieving this goal and identifies specific actions associated with each objective. Among these prescribed actions is restoring fish passage at the Xxxxxx Round Butte Project and implementing a monitoring strategy. The Middle Columbia River (“MCR”) Evolutionarily Significant Unit (“ESU”) of steelhead (Oncorhynchus mykiss) was listed by the National Marine Fisheries Service (“NOAA Fisheries”) as threatened on March 25, 1999 (64 FR 14517). The listing determination was only for naturally spawned, anadromous populations of O. mykiss residing below impassable natural barriers. The MCR steelhead occur in the lower Deschutes River below the Project. NOAA Fisheries concluded that the Deschutes River (ODFW stock 66) hatchery stock should be considered part of the ESU but not essential for its recovery. NOAA Fisheries designated ...
Sample 1
AutoNDA by SimpleDocs

Related to ESA Recovery Plans

  • Disaster Recovery Plan Contractor agrees that upon request of System Agency, Contractor shall provide copies of its most recent business continuity and disaster recovery plans.

  • Development Plans 4.3.1 For each Licensed Indication and corresponding Licensed Product in the Field, Licensee will prepare and deliver to Licensor a development plan and budget (each a “Development Plan”). The initial Development Plans for each Licensed Indication will be delivered within […***…] after the Grant Date for such Licensed Indication.

  • DISASTER RECOVERY AND BUSINESS CONTINUITY The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

  • Disaster Recovery PFPC shall enter into and shall maintain in effect with appropriate parties one or more agreements making reasonable provisions for emergency use of electronic data processing equipment to the extent appropriate equipment is available. In the event of equipment failures, PFPC shall, at no additional expense to the Fund, take reasonable steps to minimize service interruptions. PFPC shall have no liability with respect to the loss of data or service interruptions caused by equipment failure, provided such loss or interruption is not caused by PFPC's own willful misfeasance, bad faith, gross negligence or reckless disregard of its duties or obligations under this Agreement.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • Improvement Plans a. An improvement plan is a clearly articulated assistance program for a teacher/counselor/SLP whose overall summative rating is ineffective.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

  • Cost Recovery for RSTEP Requests by Registry Operator for the approval of Additional Services pursuant to Section 2.1 may be referred by ICANN to the Registry Services Technical Evaluation Panel (“RSTEP”) pursuant to that process at xxxx://xxx.xxxxx.xxx/en/registries/rsep/. In the event that such requests are referred to RSTEP, Registry Operator shall remit to ICANN the invoiced cost of the RSTEP review within fourteen (14) calendar days of receipt of a copy of the RSTEP invoice from ICANN, unless ICANN determines, in its sole and absolute discretion, to pay all or any portion of the invoiced cost of such RSTEP review.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic DHCS PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than 24 hours.

  • TREATMENT PLANS Within a reasonable period of time after the initiation of treatment, Xxxxxxxxx Xxxxx will discuss with you her working understanding of the problem, treatment plan, therapeutic objectives, and her view of the possible outcomes of treatment. If you have any unanswered questions about any of the procedures used in the course of your therapy, their possible risks, Xxxxxxxxx Xxxxx 's expertise in employing them, or about the treatment plan, please ask and you will be answered fully. You also have the right to ask about other treatments for your condition and their risks and benefits.

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