Vegetation and Weed Management Plan Sample Clauses

Vegetation and Weed Management Plan. ‌ The Certificate Holder shall develop an updated Vegetation and Weed Management Plan, in consultation with EFSEC staff, WDFW, and Ecology. 1. The updated plan must address any relevant changes to the vegetation or weed management requirements and protocols identified prior to beginning site operation.
Sample 1Sample 2Sample 3See All (10)
AutoNDA by SimpleDocs
Vegetation and Weed Management Plan. ‌ The Certificate Holder shall develop a Vegetation and Weed Management Plan, in consultation with EFSEC staff, WDFW, and Ecology. 1. The Plan must address vegetation management activities related to Project construction and operation. 2. The Certificate Holder shall develop the Plan to require all temporarily disturbed areas to be reseeded with an appropriate native seed mix selected in coordination with WDFW. 3. In consultation with WDFW, the Plan shall include a restoration schedule that identifies timing windows during which restoration should take place, and an overall timeline for when all restoration activities will be completed. 4. The Plan shall also include benchmarks and a timeline for revegetation success, and a plan for monitoring revegetation to ensure success. 5. This plan must address the requirements set forth in WAC 463-60-332(3). 6. The Plan must specify methods that will be implemented for effective noxious weed control and revegetation.
Sample 1Sample 2See All (5)
Vegetation and Weed Management Plan. ‌ The Certificate Holder shall develop a Vegetation and Weed Management Plan, in consultation with EFSEC staff, WDFW, and Ecology. 1. The Plan must address vegetation management activities related to Project construction and operation. 2. The Certificate Holder shall develop the Plan to require all temporarily disturbed areas to be reseeded with an appropriate native seed mix selected in coordination with WDFW. 3. In consultation with WDFW, the Plan shall include a restoration schedule that identifies timing windows during which restoration should take place, and an overall timeline for when all restoration activities will be completed. 4. The Plan shall also include benchmarks and a timeline for revegetation success, and a plan for monitoring revegetation to ensure success. 5. This plan must address the requirements set forth in YCC 16C.11.070 and WAC 000- 00-000(3). 6. The Plan must specify methods that will be implemented for effective noxious weed control and revegetation. 7. The plan must identify mowing schedule for vegetation maintenance and must be restricted March 15 to May 15 and limited to the extent practicable from February 1 to March 15 and May 15 to September 30. 8. The Certificate Holder Shall conduct two rare plant surveys and report the findings to EFSEC as specified in mitigation item 6 of the Revised MDNS. a. The Certificate Holder shall conduct a survey for Xxxxxx’x Biscuitroot (Tauschia hooveri) between March 15th and May 15th. b. The Certificate Holder shall conduct a survey for Coyote Tobacco (Nicotiana attenuata) between June 1st and September 30th. c. The Certificate Holder shall consult with EFSEC and DNR regarding the findings of these surveys to determine appropriate mitigation measures to be integrated in the Vegetation and Weed Management and other associated plans.
Sample 1

Related to Vegetation and Weed Management Plan

  • Project Management Plan 3.2.1 Developer is responsible for all quality assurance and quality control activities necessary to manage the Work, including the Utility Adjustment 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, Good Industry Practice and applicable Law. 3.2.2 Developer shall develop the Project Management Plan and its component parts, plans and other documentation in accordance with the requirements set forth in Section 1.5.2.5

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

  • Alignment with Modernization Foundational Programs and Foundational Capabilities The activities and services that the LPHA has agreed to deliver under this Program Element align with Foundational Programs and Foundational Capabilities and the public health accountability metrics (if applicable), as follows (see Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf): a. Foundational Programs and Capabilities (As specified in Public Health Modernization Manual) b. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Accountability Metric, Health Outcome Measure: c. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Accountability Metric, Local Public Health Process Measure:

  • Environmental Services 1. Preparation of Environmental Documentation (CEQA/NEPA) including but not limited to the following: a. Initial Study b. Categorical Exemption (CE) c. Notice of Exemption (XXX) d. Negative Declaration (ND) e. Mitigated Negative Declaration (MND) f. Notice of Preparation (NOP) g. Environmental Impact Report (EIR) i. Initial Document (Screen Check/Administrative Draft) ii. Addendum iii. Supplemental

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