I. IDENTIFY AND PROTECT INSTREAM FLOWS Sample Clauses

I. IDENTIFY AND PROTECT INSTREAM FLOWS. Recovery cannot be accomplished without securing, protecting, and managing sufficient flows to provide habitat to support self-sustaining populations of the endangered fishes. Identification and protection of instream flows are key elements in this process. The first step in instream flow protection is to identify flow regimes needed by the fish, typically characterized in terms of peak and base flow needs over a range of hydrologic conditions. In the Recovery Program, determining flow needs is primarily the responsibility of the Service (in cooperation with other participants). Factors considered in determining flow needs include: flow effects on reproduction and recruitment; flow effects on food supplies and nonnative fishes; and interrelationships between flow and other habitat parameters believed to be important for the fish, such as channel structure, sediment transport, substrate characteristics, vegetative encroachment, and water temperature. Flow recommendations often are made in stages, with initial flow recommendations based on the best available scientific information, historic conditions, and extrapolation from similar reaches. Recommendations then are refined following additional field research. The contribution of tributaries to recovery was ranked by Xxxx and Xxxxxxxx (2001). Flow recommendations have been approved for reaches of the Colorado (Osmundson and Xxxxxxx 1991; XxXxx 2003), Yampa (Xxxxx and Xxxxx 1995; Xxxxx et al. 1999), Xxxxx (Xxxx et al. 2000), Gunnison (XxXxx 2003), and Xxxxxxxx (Xxxxx and Xxxxxxx 2003) xxxxxx. Flows in the Little Snake and Yampa rivers after estimated future depletions were identified in the Yampa River Management Plan and Environmental Assessment (Xxxxx 2004). Interim flow recommendations for the White River were completed in 2004 (Xxxxxx et al. 2004), and are currently under revision. A White River management plan will be drafted in 2016-17, which will ultimately serve as the basis for a White River programmatic biological opinion. This management plan will include flow recommendations. Under the Gunnison River Basin Programmatic Biological Opinion and Aspinall Unit Study Plan (2011), the Recovery Program is conducting monitoring to assess how well the operation of the Aspinall Unit contributes to meeting target flows in the Gunnison and Colorado Rivers and to help determine if managed flows from the Gunnison and the Colorado rivers are sufficient for recovery on the Colorado River from the Gunnison River to...
Sample 1
AutoNDA by SimpleDocs

Related to I. IDENTIFY AND PROTECT INSTREAM FLOWS

  • CONFIDENTIALITY AND PRIVACY POLICIES AND LAWS The Contractor shall comply to the extent applicable with all State and Authorized User policies regarding compliance with various confidentiality and privacy laws, rules and regulations, including but not limited to the IRS Publication 1075, Family Educational Rights and Privacy Act (FERPA), the Health Insurance and Portability Act of 1996 (HIPAA) and the Health Information Technology for Economic and Clinical Health Act (HITECH). Contractor shall cooperate in executing a written confidentiality agreement under FERPA and/or a Business Associate Agreement (HIPAA/HITECH) or other contractual provisions upon request by the State or any Authorized User.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • Violence Policies and Procedures The Employer agrees to have in place explicit policies and procedures to deal with violence. The policy will address the prevention of violence, the management of violent situations, provision of legal counsel and support to employees who have faced violence. The policies and procedures shall be part of the employee's health and safety policy and written copies shall be provided to each employee. Prior to implementing any changes to these policies, the employer agrees to consult with the Association.

  • Provisions for Covered Entity to Inform Business Associate of Privacy Practices and Restrictions (a) Covered Entity shall notify Business Associate of any limitation(s) in the notice of privacy practices of Covered Entity under 45 CFR 164.520, to the extent that such limitation may affect Business Associate’s use or disclosure of protected health information.

  • RECORDS USAGE, DUPLICATION AND REDISCLOSURE RESTRICTIONS USAC and the Department agree to these restrictions on use, duplication, and disclosure of information furnished by the other Party:

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • Confidentiality and Safeguarding Information 1. Each Party may have access to confidential information made available by the other. The provisions of the Florida Public Records Act, Chapter 119, F.S., and other applicable state and federal laws will govern disclosure of any confidential information received by the State of Florida.

  • Summary of Policy and Prohibitions on Procurement Lobbying Pursuant to State Finance Law §139-j and §139-k, this Contract includes and imposes certain restrictions on communications between OGS and a Vendor during the procurement process. A Vendor is restricted from making contacts from the earliest notice of intent to solicit offers/bids through final award and approval of the Procurement Contract by OGS and, if applicable, the Office of the State Comptroller (“restricted period”) to other than designated staff unless it is a contact that is included among certain statutory exceptions set forth in State Finance Law §139-j(3)(a). Designated staff, as of the date hereof, is identified in Appendix G, Contractor and OGS Information, or as otherwise indicated by OGS. OGS employees are also required to obtain certain information when contacted during the restricted period and make a determination of the responsibility of the Vendor pursuant to these two statutes. Certain findings of non-responsibility can result in rejection for contract award and in the event of two findings within a four-year period; the Vendor is debarred from obtaining governmental Procurement Contracts. Further information about these requirements can be found on the OGS website: xxxx://xxx.xxx.xx.xxx/aboutOgs/regulations/defaultSFL_139j-k.asp.

  • Identifying Information and Privacy NOTIFICATION (a) Identification Number(s). Every invoice or New York State Claim for Payment submitted to a New York State agency by a payee, for payment for the sale of goods or services or for transactions (e.g., leases, easements, licenses, etc.) related to real or personal property must include the payee's identification number. The number is any or all of the following: (i) the payee’s Federal employer identification number, (ii) the payee’s Federal social security number, and/or (iii) the payee’s Vendor Identification Number assigned by the Statewide Financial System. Failure to include such number or numbers may delay payment. Where the payee does not have such number or numbers, the payee, on its invoice or Claim for Payment, must give the reason or reasons why the payee does not have such number or numbers.

  • Vendor Identity and Contact Information It is Vendor’s sole responsibility to ensure that all identifying vendor information (name, EIN, d/b/a’s, etc.) and contact information is updated and current at all times within the TIPS eBid System and the TIPS Vendor Portal. It is Vendor’s sole responsibility to confirm that all e-correspondence issued from xxxx-xxx.xxx, xxxxxxx.xxx, and xxxxxxxxxxxxxxxx.xxx to Vendor’s contacts are received and are not blocked by firewall or other technology security. Failure to permit receipt of correspondence from these domains and failure to keep vendor identity and contact information current at all times during the life of the contract may cause loss of TIPS Sales, accumulating TIPS fees, missed rebid opportunities, lapse of TIPS Contract(s), and unnecessary collection or legal actions against Vendor. It is no defense to any of the foregoing or any breach of this Agreement that Vendor was not receiving TIPS’ electronic communications issued by TIPS to Vendor’s listed contacts.

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