WorkGroup Meeting 15 June 2017 Commit: WSCC Technical Panel reviews - - PowerPoint PPT Presentation
WorkGroup Meeting 15 June 2017 Commit: WSCC Technical Panel reviews - - PowerPoint PPT Presentation
WorkGroup Meeting 15 June 2017 Commit: WSCC Technical Panel reviews Submittal: June 30 Initial: July 18 Formal: July 28 Review: [Final] Workplan Review Section 3: Characterization of PacCo Ag Section 5:
15 June 2017
Objectives
✓ Commit: WSCC Technical Panel reviews
- Submittal: June 30
- Initial:
July 18
- Formal:
July 28
✓ Review:
[Final] Workplan Review
- Section 3: Characterization of PacCo Ag
- Section 5: Monitoring & Adaptive Mgmt
- Appendix H: Monitoring & Adaptive Mgmt
Handouts
✓ Agenda ✓ Individual Stewardship Plan (email) ✓ Workplan (posted) ✓ Benchmarks/Monitoring (email) ✓ Prioritized Activities (email) ✓ Related … Plans and Data ✓ Critical Areas and Functions ✓ FAQ ✓ Regulatory Backstop ✓ Incentive Programs ✓ Google Earth “How To…”
Workgroup Postings:
meeting recordings, presentations, notes …
Time Topic Action Leader
:01
Agenda review/approval
Approve Kelly
:15 Calendar Check:
- WSCC formal review
- Overall work calendar
Recap Kelly
:60 Workplan Draft Review:
- Section 3
Baseline Conditions
- Section 5
Benchmark Monitoring & Adaptive Management Feedback All
:05 Next steps
Inform Kelly
Adjourn
Agenda: 15 June 2017
Wrokgroup Timeline
Month Content Action June Launch July Critical Areas & Ag: Mapping Aug Critical Area Functions Sept Work Plan Scope & Goals Oct-Nov Best Practices & Objectives Dec Monitoring and Reporting Jan’17 Stewardship Template Feb-Mar 1st Draft Apr 2nd Draft May Final Draft June Final Draft July
Inform & Align Synthesize & Recommend Refine & Scribe
“Submit” for Approval “Review”
Pacific County WorkGroup assembled and actively engaged…
When we submit the Workplan to the WSCC “Technical Panel” …
- 45 day clock begins (for Tech Panel review)
- Tech Panel meets to “informally review” the submitted plans
- Tech Panel meets “formally” to vote for approval/denial
- Tech Panel: two plans per month capacity
Wrokgroup Timeline
Month Content Action June Launch July Critical Areas & Ag: Mapping Aug Critical Area Functions Sept Work Plan Scope & Goals Oct-Nov Best Practices & Objectives Dec Monitoring and Reporting Jan’17 Stewardship Template Feb-Mar 1st Draft Apr 2nd Draft May Final Draft June Final Draft July
Inform & Align Synthesize & Recommend Refine & Scribe
Update:
- Jun 30: Submit to WSCC
- July 18: Informal Review
- July 28: Formal Review
July 18 (Olympia) “Initial Review” PacCo WorkGroup “Third Thursday” June 30: Submit Workplan to WSCC July 28 (Olympia) “Formal Review”
July 18 (Olympia) “Initial Review” July 28 (Olympia) “Formal Review”
Road Trip?
Protocol: we “submit…” the Plan
(WSCC technically “approves”)
Thu 5/18/2017 1:36 PM
Hi Kelly – just wanted to send you this reminder as Pacific County gets ready to submit their VSP work plan to the Commission and Technical Panel - the action the work group should take is to vote to send/submit the work plan to the Commission and VSP Technical Panel, rather than vote to approve the work plan (for submittal to the Commission).
- Bill Eller
Washington State Conservation Commission
VSP WORK PLAN PUBLIC COMMENT: The public is invited to comment on any VSP work plan submitted to the VSP Technical Panel within 14 days of submittal. The public can use a public comment form to capture any comments made. The Technical Panel will be provided with any comments received at the end of that period. The form is available on the Commission’s VSP web page http://scc.wa.gov/vsp/
Perspectives from June 9 Review….
…of Grant & Skagit Workplans
- Monitoring: need encompass entire watershed
(beyond just acreages enrolled in VSP)
- Clarity: what are we measuring? Methods and
protocols?
- Completeness: document needs to “spell out” details
- Option to regulate: if County CAO applied to ag, still
should monitor for protections effectiveness (through regulations)
Time Topic Action Leader
:01
Agenda review/approval
Approve Kelly
:15 Calendar Check:
- WSCC formal review
- Overall work calendar
Recap Kelly
:60 Workplan Draft Review:
- Section 3
Baseline Conditions
- Section 5
Benchmark Monitoring & Adaptive Management Feedback All
:05 Next steps
Inform Kelly
Adjourn
Agenda: 15 June 2017
Switch to Word doc’s for section by section walkthru
5.xx Monitoring
To be performed every two years (biennial), by Dec 31 Then, included in biennium reports, by Aug 29 “Implementation” what we’re “doing…”
- Trends in adoption of stewardship activities
- Collected via Individual Stewardship Plans (ISP)
“Effectiveness” validate the implementation
- Actual effects on critical areas functions
- Combines existing monitoring with add’l PCD collection
“Indicators” broad-area tracking data
- Information valuable for adaptive management
Table 5-2 (page 59-60)
Priority Issue (Benchmark ID) Baseline Fecal coliform (WQl-1) PROTECT: Avoid increasing agricultural contributions to fecal coliform bacteria and nutrient loading ENHANCE: Reduce…
Baseline to be established via Conservation District monitoring conducted during first five years (2017-2022)
Pesticides (WQl-2) PROTECT: Avoid increasing agricultural contributions to known surface water and groundwater quality impairments by pesticides and herbicides ENHANCE: Reduce… Sediment / turbidity (WQl-3) PROTECT: Ensure no increase agricultural contributions to the transport of fine sediment in runoff ENHANCE: Reduce …
Next up… TBD
Appendix
Confidentiality…
pages 65-66
Completed ISPs are kept and maintained by the PCD. VSP success depends on open participation by producers. This
- pen participation hinges on the assurance that confidential
business information will not be disclosed. According to guidance from the Washington State Conservation Commission, statutory provisions on the confidentiality and disclosure of a farm plan also apply to ISPs collected by the
- PCD. Importantly, information contained in individual ISPs
will be maintained by the PCD as confidential information. ISP results will be summarized at the watershed or sub- watershed scale such that no personally identifying information is available.
Ron Schulz is developing legal language to protect ISP information from release under public records requests; this will be included once available.