css class 26 using css in practice 113009

Context Sensitive Solutions in Transportation Planning, Environmental

Analysis and Design

1

Class 26

Using CSS in Practice


Analysis and Design

• CSS is still “new”

• CSS is encouraged, not required, by FHWA

– Proactive approach to meet NEPA intent

– Thinking beyond “just the pavement”

Using CSS

2


Analysis and Design

• Most state DOTs have accepted CSS– Varying use in projects

• Large• Difficult• Previously rejected or opposed• all

– Varying institutionalization• Policy• Manuals• Training• Practice

• Local agencies highly variable

Using CSS

3


Analysis and Design

• State DOT manuals– Project development– Geometric design

• State DOT policy– Policy and procedure memoranda– Minute orders– Legislation– Training programs

• Local agencies– Policy– Design or public works manuals

Finding CSS policy

4


Analysis and Design

• FHWA

• AASHTO

• ITE/CNU

• CSS.org

Finding CSS

5


Analysis and Design

• Project work program• Agency decision

– Agency policy– Responsible administrator– District engineer– District or state design engineer– Project manager– Public works director– Capital programs director– City/county engineer

Using CSS in projects

6


Analysis and Design

• General policy

• Project– Issues

– Complexity

– Community sensitivity

• Project manager decision

• Consultant proposal

Basis for using CSS

7


Analysis and Design

• Commitment to open input– True “continuous” stakeholder involvement– Use of constructive input– Consideration of varying alternatives

• Collaborative process– Stakeholders– Partner agencies– Public

What is needed for true CSS?

8


Analysis and Design

• Design flexibility– AASHTO green book – full extent– Other CSS/flexibility guidelines– Willingness to support design exceptions– (Preferred) design manual

• Flexible ranges, not just standards


9


Analysis and Design

• Proactive approach to NEPA– Address issues during development, not just in

impact analysis


10


Analysis and Design

• Note and use lessons learned– Experiences

• Successes• Shortfalls• Opportunities for improvement

– Costs• Project development• “Rework”• Project implementation


11


Analysis and Design

• Note and use lessons learned(cont.)– Time

• Project development• Total

– Community acceptance• Duration of approval process• Partner funding shares• Time lost addressing opposition• Lawsuits• EIS and permit approval delays


12


Analysis and Design

• Note and use lessons learned(cont.)– Training

• What is CSS?• How to use CSS process• CSS-NEPA relationships• Public involvement techniques• Design flexibility and creativity• Broadening projects to support non-transportation

community objectives• Evaluation of alternatives


13


Analysis and Design

Where can you use CSS?

Discussion

14


Analysis and Design

• Do you need numerous stakeholders to use CSS?

Discussion

15


Analysis and Design

• Does project size matter when deciding whether to use CSS?

Discussion

16


Analysis and Design

• Does the size of the sponsoring/owning agency matter?

Discussion

17


Analysis and Design

• Does the owning agency have to initiate the project or CSS?

Discussion

18


Analysis and Design

• What are reasons why CSS is not always used?

Discussion

19


Analysis and Design

• CSS can be used– For all projects– By any agency– With plenty of references and precedents

• Owning agency has final decision authority– Subject to environmental clearance

• CSS is the correct way to proceed

Summary

20

css class 26 using css in practice 113009

Technology

design css

environmental analysis

context sensitive solutions

true css

environmental clearance

design note

design commitment

design exceptions