Watershed Management Plan Sample Clauses

Watershed Management Plan. The Organization shall prepare a Watershed Management Plan for the Upper Rum River Watershed. The plan shall be in compliance with Minnesota Statutes, Chapter 103B.231, Subd. 4 and 6 as from time to time amended. The Chapter describes plan contents to include but not limited to the following.
AutoNDA by SimpleDocs
Watershed Management Plan. As required by law, the Joint Powers Board shall prepare and adopt a Watershed Management Plan as required by law.
Watershed Management Plan. The Commission shall develop a watershed management 5 plan including a capital improvement program in conformance with Minn. Stat. § 103B.231. The 6 Commission shall adopt the plan within 120 days after BWSR's approval of the plan. After adoption, the 7 Commission shall implement the watershed management plan and enforce the regulations set out in the plan.
Watershed Management Plan. Submittal of the Plan. The CRWA will recommend the plan to the parties of the Agreement. The CRWA will be responsible for initiating a formal review process for the watershed-based plan conforming to Minnesota Statutes Chapters 103B and 103D, including public hearings. Upon completion of local review and comment, and approval of the plan for submittal by each party, the CRWA will submit the watershed-based plan jointly to the Minnesota Board of Water and Soil Resources (BWSR) for review and approval.
Watershed Management Plan. The Organization shall prepare a Watershed Management Plan for the Sunrise River Watershed. The plan shall be in compliance with Minnesota Statutes, chapter 103B.231, Subd. 4 as from time to time amended. This Chapter describes plan contents to include but not limited to the following:
Watershed Management Plan. (Plan). The Board shall adopt a water management plan, as required by the Act. The Plan shall be subject to the appropriate governmental unit review as required by the Act.
Watershed Management Plan. (Plan). The Commission shall prepare and/or update a water management plan, as required by the Act. The Plan, either a new one or an updated one, shall be recommended to the Board of Directors for approval. The Plan shall be compliant with Minnesota Statutes, Ch. 103B as it may be amended and applicable Minnesota Rules. The Plan shall be subject to the appropriate governmental unit review as required by the Act.
AutoNDA by SimpleDocs
Watershed Management Plan. The Northwest Florida Water Management District, in cooperation with the Florida Department of Environmental Protection, developed the Pensacola Bay System Surface Water Improvement and Management Plan in 1997. In 2005, the Bay Area Resources Council, under the auspices of the West Florida Regional Planning Council developed the Pensacola Bay Area Watershed Management Plan, which includes components that identify causes and sources that need to be controlled, action plans for measures to achieve load reductions, information, education and monitoring components. The City of Pensacola (Grantee) also has a stormwater management plan to aid water quality. PROJECT OVERVIEW: The City of Pensacola is one of the oldest cities in the state of Florida, with a history of urban settlement dating back 300 years. In this coastal community, tropical storms and hurricanes have periodically reminded residents of the critical need to manage the large volumes of runoff generated in short time periods by sub- tropical weather systems. Urbanization has put substantial pressure on both the natural and man-made hydrologic systems to accommodate increasing amounts of runoff carrying ever more complex pollutants. All of the runoff from the City discharges into the Pensacola Bay watershed. With only a few exceptions, the runoff within the watershed passes through some feature of the Grantee’s conveyance system, discharging to either Bayou Chico or Bayou Texar en route to Pensacola Bay. As the City has largely "built-out", the land available for stormwater treatment and storage facilities has diminished, and intense urban development is leading to increasing impervious area coverage and stormwater runoff volume. Many areas of this urbanized watershed were developed before implementation of the 1982 State surface-water rule (Chapter 17-25 FAC) and lack any means of formal treatment addressing water quality. As a result, stormwater runoff from those developed areas often discharges at rates exceeding pre-development flows and in some cases directly to Pensacola Bay. The Grantee has moved on several fronts within the last several years to address stormwater impacts. First, and foremost, improving stormwater management has been elevated to a priority concern by both the City Council and city staff. This reflected in both operational changes as well as reflected in the Grantee's budget. A Stormwater Management Improvement Plan was developed and is posted on the Grantee’s web site. Educat...
Watershed Management Plan. The Board shall update as needed and administer the Watershed Management Plan for the Upper Rum River Watershed. The Watershed Management Plan shall comply with Minnesota Statutes, section 103B.231, subdivision 4, Minnesota Rules, chapter 8410, and other applicable laws.

Related to Watershed Management Plan

  • Management Plan The Management Plan is the description and definition of the phasing, sequencing and timing of the major Individual Project activities for design, construction procurement, construction and occupancy as described in the IPPA.

  • Construction Management Plan Contractor shall prepare and furnish to the Owner a thorough and complete plan for the management of the Project from issuance of the Proceed Order through the issuance of the Design Professional's Certificate of Material Completion. Such plan shall include, without limitation, an estimate of the manpower requirements for each trade and the anticipated availability of such manpower, a schedule prepared using the critical path method that will amplify and support the schedule required in Article 2.1.5 below, and the Submittal Schedule as required in Article 2.2.3. The Contractor shall include in his plan the names and resumés of the Project Superintendent, Project Manager and the person in charge of Safety.

  • Project Management Plan 6.4.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work. Developer shall undertake all aspects of quality assurance and quality control for the Project and Work in accordance with the approved Project Management Plan and Good Industry Practice.

  • Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.

  • Workload Management 11.1 The parties to this Agreement acknowledge that employees and management have a responsibility to maintain a balanced workload and recognise the adverse affects that excessive workloads may have on employee/s and the quality of resident/client care.

  • AGREEMENT MANAGEMENT Pinellas Community Foundation (AGENCY) designates the following person(s) as the liaison for the AGENCY: Xxxxxx Xxxxxx, CEO Pinellas Community Foundation 00000 XX Xxxxxxx 00 Xxxxx, Xxxxx 000 Clearwater, FL 33764 000-000-0000 GRANTEE BENEFICIARY designates the following person(s) as the liaison for the GRANTEE BENEFICIARY: Xxxxxxx X. Xxxxxx, CEO Society of St. Xxxxxxx xx Xxxx South Pinellas, Inc. 000 00XX Xxxxxx Xxxxx, Xx. Xxxxxxxxxx, XX 00000 727-954-7990 SIGNATURE PAGE FOLLOWS

  • SITE MANAGEMENT We reserve the right, but not the obligation, to: (1) monitor the Site for violations of these Terms of Use; (2) take appropriate legal action against anyone who, in our sole discretion, violates the law or these Terms of Use, including without limitation, reporting such user to law enforcement authorities; (3) in our sole discretion and without limitation, refuse, restrict access to, limit the availability of, or disable (to the extent technologically feasible) any of your Contributions or any portion thereof; (4) in our sole discretion and without limitation, notice, or liability, to remove from the Site or otherwise disable all files and content that are excessive in size or are in any way burdensome to our systems; and (5) otherwise manage the Site in a manner designed to protect our rights and property and to facilitate the proper functioning of the Site.

  • Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Facility. Developer shall manage traffic so as to preserve and protect safety of traffic on the Facility and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Facility and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan.

  • 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.

  • Procurement Plan 8. The Borrower shall update the Procurement Plan as needed throughout implementation of the Project, and on each anniversary of the Effective Date, the Borrower shall in consultation with ADB determine whether the Procurement Plan needs to be updated. The Borrower shall implement the Procurement Plan in the manner in which it has been approved by ADB.

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