Lessons learned from green infrastructure project experience in developing code requirements and...

59
CWAA ― Urban Water Sustainability Leadership Conference October 4, 2011 Lessons Learned from Green Infrastructure (GI) Project Experience in Developing Code Requirements and Community Engagement

description

Seattle's decade of experience installing Green Infrastructure (GI) projects has provided a substantial knowledge base. Two key areas of growth will be discussed: 1) Key policy issues in the development of the Seattle's Stormwater Code requirement for use of GI to the “maximum extent feasible” for projects on private property and right-of-way, and 2) public engagement success, failures, and proposed approach in moving forward in installing GI in public and private places, including a look at using GI to assist with combined sewer overflows.

Transcript of Lessons learned from green infrastructure project experience in developing code requirements and...

Page 1: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

CWAA ― Urban Water Sustainability Leadership ConferenceOctober 4, 2011

Lessons Learned from Green Infrastructure (GI) Project Experience in Developing Code

Requirements and Community Engagement

Page 2: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Overview

• Seattle and Seattle’s Green Infrastructure (GI) Program

• GI in the Right-of-Way• Public Involvement to Maximize Success• Strategies for Multiple Benefits

Page 3: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Presented by: Nancy Ahern, Deputy Director, Seattle Public Utilities

Seattle Public Utilities and Seattle’s Green Infrastructure Program

Page 4: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Water Supply

Page 5: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Manage Solid Waste

Page 6: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Urban Drainage and Wastewater

Page 7: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Seattle’s Drainage and Wastewater System

System Drivers:• Combined Sewer Overflow

(CSO) and Stormwater Permit Compliance

• Sediment cleanup• Urban flooding• Water quality• Creek habitat• Climate change

Page 8: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Green Stormwater Infrastructure

• Integrating into Capital and O&M Programs• Analyzed cost/performance of parcel

and ROW based strategies• Used that analysis in planning• Have retrofit 232-acres of Seattle’s

creek watersheds to date

• Incorporation into Code• New development must use GI

• Incorporation into Rate Structure• Rate credits for impervious area

managed

Page 9: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Why Include GI in the Urban Drainage Strategy?

• Citizen interest: • Alternative for right-of-way improvements for

informal areas• Reducing environmental impacts on Seattle’s

receiving water bodies• Providing ratepayers cost-effective solutions

that maximize social and environmental benefits • Helps toward other City goals

– 2030 Challenge– Seattle reLeaf

Page 10: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Natural Drainage SystemsBuilding GI Experience and Knowledge

Project Project Drainage Area

SEA Street #1 2.3 acres

NW 110th Cascade 28 acres

Broadview Green Grid 32 acres

Pinehurst Green Grid 49 acres

High Point 129 acres

Page 11: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

1111

SPU CSO System

• 90 permitted CSO outfalls– 37 CSO outfalls do not meet CSO

requirements

• 35 CSO storage facilities (8.1 MG)• 100-200 million gallons CSO

discharged annually• About 200 CSO discharge events

annually• Integration with King County

Page 12: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

May 4, 2010 - Meeting No. 1

12

History Sets Context for CSO Control

Page 13: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

CSO Control Approaches

CSO Control Relative Cost Range per gallon

• Green Stormwater Infrastructure $2.50 to $22

• System Retrofits $1 to $2

• Infiltration/Inflow $30 to $32

• Flow Transfer site specific

• Wet Weather Storage $12 to $40

• Wet Weather Treatment $8 to $25

Page 14: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

CSO Reduction: Leading with Green

Private parcels: RainWise

Alleys: Retrofitted with permeable pavement

Roadways: Retrofitted with roadside rain gardens

Photos Courtesy of T. Tackett (SPU)

Page 15: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

CSO Compliance with Anticipated Consent Decree

Big Pipe Photo

Solutions

Grey Green

Page 16: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Presented by: Tracy Tackett, Green Stormwater Infrastructure Program Manager, Seattle Public Utilities

GI in the Right-of-Way

Page 17: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Public Rights-of-Ways and Roadside Rain Gardens

Page 18: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Potential Seattle & King County Joint GI Implementation

Potential Right-of-way Bioretention or Permeable Pavement

Seattle CSO Basins

King County CSO Basins

City Boundary*All KC and SPU uncontrolled basins are under consideration for RainWise

Page 19: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Green is Not Always the Silver Bullet

Page 20: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Public Sensitivities to Roadside Rain Gardens

• Reduction in parking availability• Perceived safety issues• Change in neighborhood

aesthetics• Resistance to any changes• O&M concerns

Page 21: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Raingardens not exactly to scale.

Parking: How big is a Rain Garden?

Page 22: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Policy:Is Participation Voluntary vs. Mandatory?

Page 23: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Sensitivities to GI Challenges with Developers or Other Departments

• Competing needs for space• Change in desired aesthetic• Cost

Page 24: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Citywide Policy

• What is financial feasibility?

• Is parking higher or lower priority than stormwater goals?

• What is our risk tolerance?

Page 25: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Has your agency had any push back for adoption of green practices in the ROW?

Examples?

Discussion Question:

Page 26: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Presented by: Jennifer Price, Program Manager, CH2M HILL

Public Involvement to Maximize Success

Page 27: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

• Manage expectations– Show interim conditions – Schedule and adaptation

• Community concerns are specific– Curb and gutter vs.

unimproved– Importance of street character– Duration of residence matters

• Don’t rely on community meetings alone

Lessons Learned from the Ballard Community

Page 28: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Getting to Informed Consent on GI Projects

• Engage vs. inform• Early and often in process

– Meaningful engagement for residents in siting and design

• Transparent decision processes

• Find common ground• Inform about O&M levels of

service

Page 29: Lessons learned from green infrastructure project experience in developing code requirements and community engagement
Page 30: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

30

Page 31: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Revised Public Involvement Processfor GI Projects

• Introduce CSO problem and solutions by leading with RainWise

• Use design visualization to demonstrate why GI is a good solution

• Identify all potential stakeholders• Maintain consistent

communications• Engage stakeholders in multiple

benefits

Page 32: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

FeasibilityAnalysis

FeasibilityAnalysis

Internal Site Visits

Internal Site Visits

Identify Stakeholders and Policies

Identify Stakeholders and Policies

Update Basin Specific

Outreach Plan

Update Basin Specific

Outreach Plan

Field/Site Specific

Feasibility

Field/Site Specific

Feasibility

Modeling and BMP

Sizing

Modeling and BMP

Sizing

Interactive Workshop• Project purpose

and need• Criteria for selection

Interactive Workshop• Project purpose

and need• Criteria for selection

FinalizeCommunications

Plan

FinalizeCommunications

Plan

Concept Analysis

And Scenario Building

Concept Analysis

And Scenario Building

Initial Communications• Community Briefings• Stakeholder Interviews• Personalized mailing• CSO Community Council

Initial Communications• Community Briefings• Stakeholder Interviews• Personalized mailing• CSO Community Council

GI Project Timeline

2-3 months

Project Initiation Preliminary Evaluation of Alternatives

3-4 months

RainWise MarketingRainWise Marketing

Proj

ect M

anag

emen

t Pu

blic

Com

mun

icat

ions

Page 33: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

DesignDesign

Electronic or MailCommunication

Electronic or MailCommunication

ReviseScenarios

ReviseScenarios

5% Site Plan2-3 Scenarios5% Site Plan2-3 Scenarios

Status UpdatesStatus

Updates

Interactive Workshop

• Selected streets• Design input

Interactive Workshop

• Selected streets• Design input

Electronic or MailCommunication

Electronic or MailCommunication

CSO Community Council MeetingCSO Community Council Meeting

Proj

ect M

anag

emen

t Pu

blic

Com

mun

icat

ions

CouncilBriefingCouncilBriefing

SelectOption

Project Approval

Revisit Technical Feasibility as Needed

6 months minimum 1+ years

GI Project TimelineDetailed Evaluation of Alternatives Design

One-on-one Outreach to

address concerns

One-on-one Outreach to

address concerns

On-Site Walks-and-Talks

On-Site Walks-and-Talks

CSO Community Council MeetingCSO Community Council Meeting

Interactive Workshop

• Design input

Interactive Workshop

• Design input

Communications Plan Update

Communications Plan Update

Page 34: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

What strategies or approaches have you used to gain acceptance of a Green Infrastructure project?

Discussion Question:

Page 35: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Presented by: Peg Staeheli, Principal, SvR Design Company

Strategies for Multiple Benefits

Page 36: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

The quest: How to get more benefit from our public

infrastructure investments

Page 37: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Permitting Maintenance

Finance

Taxes/Bonds

Local / State/ Federal

Private

Planning

Policy

Government

Development Pattern

Public/Private

Delivery

Public Crews

Private Contract

Volunteers

Local

State

Federal

Departmental Partners in

Process

Construction

Traditional

Alternative

Involve

Collaborate

Communicate

Page 38: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Multi-Benefit Solutions- Looking at the Systems

Page 39: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Stormwater Goals via Stormwater

Code

CSO Reduction

Bioretention/ Rain Garden

Permeable Pavement

Rainwater Harvesting/ Detention Cistern

Trees

Greenroofs

GI for CSO Reduction and More

Page 40: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Some Examples: How GI Gets You More

• Significant reduction in total stormwater volume

• Increased awareness about stormwater and impacts

• Increased green space (increased walkability, increased habitat)

Page 41: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Yale Street Private Development

Page 42: Lessons learned from green infrastructure project experience in developing code requirements and community engagement
Page 43: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Bell Street ParkFrom SEAstreet to People Place Bringing it all

Together

Page 44: Lessons learned from green infrastructure project experience in developing code requirements and community engagement
Page 45: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

THREE MOVES: reclaim. elevate. mix.

www.depave.org

Page 46: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

water section: down garden

Page 47: Lessons learned from green infrastructure project experience in developing code requirements and community engagement
Page 48: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Winslow Way, Bainbridge Island, WA

Page 49: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Winslow Way, Bainbridge IslandStrategies for the Multifunctional Street

Page 50: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

• Ensuring walkable space• Using Bioretention in several forms with enhanced landscape• Permeable pavement – strategic use• Manufactured systems when space is tight• Retaining mature tree canopy• Additional Trees

Page 51: Lessons learned from green infrastructure project experience in developing code requirements and community engagement
Page 52: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

GI into Northgate Area Comprehensive Planning

“transforming the center’s underutilized, auto-oriented office/retail area into a higher intensity mix of office, retail, and housing …

emphasis has been placed on creating new public plazas and parks, and on restoring degraded environmental features.”

Page 53: Lessons learned from green infrastructure project experience in developing code requirements and community engagement
Page 54: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Northgate Mall, Seattle WA 2007- 2011

Page 55: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Seattle Public Utilities partnered with the Seattle Department of Planning & Development

Result: Client Assistance Memo – CAM515 extending the strategy beyond a single project

Page 56: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

High Point Seattle

High Point- SPU’s Successful GI Implementation 2001-2011

Page 57: Lessons learned from green infrastructure project experience in developing code requirements and community engagement
Page 58: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

How does your agency involve other departments (from Planning through Inspection) in your planning and implementation for Green Infrastructure?

Discussion Question:

Page 59: Lessons learned from green infrastructure project experience in developing code requirements and community engagement

Thank YouThank You