Practical Design in ODOTPractical Design in ODOT

Roadway ConferenceApril 13, 2010

Cathy Nelson, PETechnical Services Manager/Chief Engineer

Transportation ChallengesTransportation Challenges

• Growing Population

• Aging Infrastructure

• Limited Resources

Practical Design PhilosophyPractical Design Philosophy

• Stretching scarce resources as far as possible to best meet transportation system needs

• Balancing cost and system value

• Good Business Practice– Jobs & Transportation Act (JTA)

Requires Formal Practice

ODOT Practical Design Strategy ODOT Practical Design Strategy Implementation PlanImplementation Plan

1. Strategy Research Jan – July 2009

2. Draft Strategy Oct 1, 2009• Internal Review

3. Communication Plan Dec 2009 • E-mails & website

4. Final Strategy March 2010• Internal & External Review

5. Rollout & Training April 2010

6. Legislative Report Nov 2010 Deadline

So…. What’s Different?So…. What’s Different?

• Purpose & Need Agreements – “what, why, how”

• System context in addition to project context

• Emphasis placed on incremental system improvements

Practical Design Strategy Practical Design Strategy GoalsGoalsGoal #1

– Direct available dollars toward activities and projects that optimize the highway system as a whole

Goal #2– Develop solutions to address the purpose and

need identified for each project

Goal #3– Design projects that make the system better,

address changing needs, and/or maintain current functionality by meeting, but not necessarily exceeding, the defined project purpose and need and project goals.

Safety

• Maintain or improve overall system safety

• Make system as safe as practical

• Are there any high value add-ins with minimal cost? - make practical, appropriate, and beneficial choices

around safety - apply sound engineering judgment to safety

decisions

Corridor Context

• When establishing or evaluating design criteria, work within intended corridor use.

• Does this "fix" fit with the rest of the corridor and its natural and built environments?

• Roadways should reflect both character of the community and current and planned land uses

Optimize the System

• Adopting more of an asset management approach

• Develop specific maintenance, repair, rehabilitation and replacement strategies

• Optimize the life-cycle investment in that particular asset

• Optimize the entire highway system for safety, mobility and financial investment

Public Support

• Work in partnership with local communities. Provide opportunities to shape the solutions.

• Have needs for pedestrians, bicyclists, transit users, freight and mobility been considered?

• Are the project purpose and need clear and have they been communicated well?

• Is this project aligned with Oregon's overall plan for the transportation system?

Efficient Cost• Strive to stretch limited funds

• Develop projects that meet the specific, desired purpose and need

• Should an incremental improvement be considered?

• Could funds be redistributed from lower priority items to areas producing greater system benefits?

• Focus on making strategic decisions that benefit the overall system

Implementing Practical DesignImplementing Practical Design

• Defining / Documenting / Delivering the “Right” Solution

ToolsTools

• Strategy Document• Project Charters• Decision Matrix Practical Design

PROJECT CHART...

Strategy DocumentStrategy Document

Online @ http://transnet.oregon.gov/ODOTINTRA/HWY/TECHSERV/practical_design.shtml

Philosophy, focus, decision-making roles & responsibilities, tools and examples

Will expand with future on-line links

Design Team SuccessDesign Team Success

• Better problem descriptions and purpose and need statements

• The availability of information to the design team about the vision for the overall corridor

• Demonstrated confidence by the design teams that it is OK to do something different when exercising their project related decision making capabilities

Practical Design FocusPractical Design Focus

• Clarity of Purpose and Need– Project Charters

• Decision-making– SCOPE values integration & documentation at

key milestones– Design Exceptions

• Tools & processes– 1R– Design Speed Tech Bulletin

• System performancemeasures

Questions?Questions?