Management and Conservation Plans Sample Clauses

Management and Conservation Plans. In 1988, Xxxxx Xxxxx developed the first Species Management Guide for Lomatium greenmanii (Kagan 1988). This management guide provided current information on the range, distribution and habitat requirements of the species. In addition, the management guide identified management practices consistent with the species’ needs, including the identification of essential monitoring needs. In 1989, Xxxxxx and Xxxxx wrote the first status report for X. xxxxxxxxxx. In 1999, the WWNF developed the first conservation strategy for X. xxxxxxxxxx, which included a conservation assessment (WWNF 1999). The conservation strategy was developed to ensure the survival of the species on National Forest System Lands by implementing the conservation actions identified by the plan (WWNF 1999). Following the development of the conservation strategy, the U.S. Fish and Wildlife Service and the U.S.D.A. Forest Service signed a conservation agreement to implement those actions. The agreement outlined 15 conservation action items that the WWNF would undertake to further conservation of X. xxxxxxxxxx. The 1999 conservation agreement expired on September 23, 2004. Appendix B provides a status report of the ongoing and completed conservation action items as outlined in the 1999 conservation agreement (USFWS 1999).
AutoNDA by SimpleDocs

Related to Management and Conservation Plans

  • Cloud Computing State Risk and Authorization Management Program In accordance with Senate Bill 475, Acts 2021, 87th Leg., R.S., pursuant to Texas Government Code, Section 2054.0593, Contractor acknowledges and agrees that, if providing cloud computing services for System Agency, Contractor must comply with the requirements of the state risk and authorization management program and that System Agency may not enter or renew a contract with Contractor to purchase cloud computing services for the agency that are subject to the state risk and authorization management program unless Contractor demonstrates compliance with program requirements. If providing cloud computing services for System Agency that are subject to the state risk and authorization management program, Contractor certifies it will maintain program compliance and certification throughout the term of the Contract.

  • Management and Control Systems Grantee will:

  • Enterprise Information Management Standards Grantee shall conform to HHS standards for data management as described by the policies of the HHS Office of Data, Analytics, and Performance. These include, but are not limited to, standards for documentation and communication of data models, metadata, and other data definition methods that are required by HHS for ongoing data governance, strategic portfolio analysis, interoperability planning, and valuation of HHS System data assets.

  • Procurement and Property Management Standards The parties to this Agreement shall adhere to the procurement and property management standards established in 2 CFR 200, Uniform Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards, and to the Texas Uniform Grant Management Standards. The State must pre-approve the Local Government’s procurement procedures for purchases to be eligible for state or federal funds.

  • Management; Community Policies Owner may retain employees and management agents from time to time to manage the Property, and Owner’s agent may retain other employees or contractors. Resident, on behalf of himself or herself and his or her Guests, agrees to comply fully with all directions from Owner and its employees and agents, and the rules and regulations (including all amendments and additions thereto, except those that substantially modify the Resident’s bargain and to which Resident timely objects) as contained in this Agreement and the Community Policies of the Property. The Community Policies are available at xxxxx://xxxxxxxxxxxxxx.xxx/policies.pdf or on request from the management office and are considered part of this Agreement.

  • Resource Conservation Chapter 5 of the San Francisco Environment Code (“Resource Conservation”) is incorporated herein by reference. Failure by Contractor to comply with any of the applicable requirements of Chapter 5 will be deemed a material breach of contract.

  • Procurement and Consultant Guidelines All goods, works and services required for the Project and to be financed out of the proceeds of the Grant shall be procured in accordance with the requirements set forth or referred to in:

  • FLOODPLAIN MANAGEMENT AND WETLAND PROTECTION Executive Order 11988, Floodplain Management, May 24, 1977 (42 FR 26951), 3 C.F.R., 1977 Comp., p. 117, as interpreted in HUD regulations at 24 C.F.R. Part 55, particularly Section 2(a) of the Order (For an explanation of the relationship between the decision- making process in 24 C.F.R. Part 55 and this part, see § 55.10.); and Executive Order 11990, Protection of Wetlands, May 24, 1977 (42 FR 26961), 3 C.F.R., 1977 Comp., p. 121 particularly Sections 2 and 5. COASTAL ZONE MANAGEMENT The Coastal Zone Management Act of 1972 (16 U.S.C. § 1451, et seq.), as amended, particularly sections 307(c) and (d) (16 U.S.C. § 1456(c) and (d)).

  • Professional Growth and Improvement Plans A. Professional growth and improvement plans shall be developed as follows:

  • International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

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