Your SlideShare is downloading. ×
0
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Mike Heiligenstein: Developing Context Sensitive Solutions
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Mike Heiligenstein: Developing Context Sensitive Solutions

275

Published on

CTRMA's Executive Director Mike Heiligenstein's presentation Developing Context Sensitive Solutions: A Tale of Two Roads

CTRMA's Executive Director Mike Heiligenstein's presentation Developing Context Sensitive Solutions: A Tale of Two Roads

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
275
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Developing Context Sensitive Solutions: A Tale of Two Toll Roads <ul><li>Mike Heiligenstein, Executive Director </li></ul><ul><li>IBTTA Facilities Maintenance </li></ul>
  • 2. Tale 1: 183A
  • 3. 183A Project <ul><li>Built using a comprehensive development agreement </li></ul><ul><ul><li>Design-build </li></ul></ul><ul><ul><li>Guaranteed price and completion date </li></ul></ul><ul><ul><li>Original contractor aesthetics/ landscape commitment 2.5%; raised to 4% </li></ul></ul><ul><ul><li>Context sensitive solutions process to be contractor’s responsibility </li></ul></ul>“ Context Sensitive Design is thinking beyond the pavement.” US Department of Highways Federal Highway Administration
  • 4. Context Sensitive Solutions Approach <ul><li>Partner with developer </li></ul><ul><ul><li>Establish community outreach </li></ul></ul><ul><ul><li>Engage community in design and construction </li></ul></ul><ul><ul><li>Initiate dialogue regarding betterments </li></ul></ul><ul><li>Input from stakeholders </li></ul><ul><ul><li>Aesthetics </li></ul></ul><ul><ul><li>Shared Use Path </li></ul></ul><ul><ul><li>Landscaping </li></ul></ul><ul><ul><li>Field Operations Building </li></ul></ul><ul><ul><li>Opportunities for betterments </li></ul></ul>
  • 5. 183A CSS: Developer’s Role <ul><li>4% allocation for aesthetics/landscape </li></ul><ul><li>Provide aesthetic concepts and treatments </li></ul><ul><li>Participate in community outreach </li></ul><ul><li>Provide options and costs to Aesthetic Committee </li></ul>
  • 6. 183A CSS: Mobility Authority’s Role <ul><li>Establish Aesthetics Committee </li></ul><ul><li>Manage community outreach </li></ul><ul><li>Provide direction on aesthetic concepts/ treatments </li></ul><ul><li>Provide timely decisions to ensure adherence to design-build schedule </li></ul><ul><li>Approve costs and budgets </li></ul>
  • 7. Lessons From CDA Approach <ul><li>Aesthetics not contractor’s top priority </li></ul><ul><li>Very difficult in design build environment. Mobility Authority detailed CSD with more specificity in next RFP </li></ul><ul><li>Client had to drive process and develop vision with both design build team and consultant team </li></ul><ul><li>Pricing of aesthetics elements left to negotiation – after award of CDA-DB, leverage shits to contractor </li></ul><ul><ul><li>Difficult to pin down budget </li></ul></ul><ul><li>Unable to establish clear community vision for overall aesthetics </li></ul><ul><ul><li>Pace of development schedule </li></ul></ul><ul><ul><li>Lack of previous experience </li></ul></ul>
  • 8. Tale 2: 290E
  • 9. 290E Project <ul><li>Originally planned to be built using comprehensive development agreement </li></ul><ul><ul><li>Design-build </li></ul></ul><ul><ul><li>Guaranteed price and completion date </li></ul></ul><ul><ul><li>Contractor provided with detailed description of aesthetic and landscaping design requirements </li></ul></ul><ul><ul><ul><li>183A CDA did not provide this level of detail </li></ul></ul></ul>
  • 10. 290 East CSS Process: <ul><li>Engage stakeholders through workshops </li></ul><ul><li>Gather input from stakeholders </li></ul><ul><li>Identify issues and concerns </li></ul><ul><li>Define a solution that works within the context of the community </li></ul><ul><li>Incorporate solution into the design </li></ul>Goal: Design a facility that meets mobility and safety needs but also complements the community.
  • 11. Engage the Community to Determine: <ul><li>What are some existing community characteristics? </li></ul><ul><ul><li>What makes the area unique? </li></ul></ul><ul><ul><li>How can the look and character of the roadway reflect the values of the community? </li></ul></ul><ul><ul><li>Are there existing themes upon which we can build? </li></ul></ul><ul><li>Character of design elements </li></ul><ul><ul><li>Bridges and retaining walls </li></ul></ul><ul><ul><li>Lighting </li></ul></ul><ul><ul><li>Signs </li></ul></ul><ul><ul><li>Pedestrian facilities </li></ul></ul><ul><ul><li>Landscaping and hardscape </li></ul></ul>
  • 12. Visual Preference Survey <ul><li>Preference Surveys were solicited </li></ul><ul><li>Input from these meetings inspired 3 design concepts </li></ul>
  • 13. Final Community Wide Workshop <ul><li>Entire community was invited to attend a final meeting to identify a preferred design concept </li></ul><ul><li>On-line input was also taken via the Mobility Authority’s Web site </li></ul>
  • 14. 290 East CSS Design Guidelines <ul><li>Aesthetic guidelines for project based on input from workshops </li></ul><ul><li>Look and character reflect region </li></ul><ul><li>Provide shared-use path/pedestrian facilities </li></ul><ul><li>Address safety considerations </li></ul><ul><li>Address mobility considerations </li></ul><ul><li>Provide a flexible document: </li></ul><ul><ul><li>Used for Design Build or Design Bid Build </li></ul></ul>
  • 15. 290 East Measures of Success <ul><li>Community Acceptance </li></ul><ul><li>Environmental Compatibility </li></ul><ul><li>Engineering and Technical Functionality </li></ul><ul><li>Financial Feasibility </li></ul><ul><li>Hopefully! Timely Delivery </li></ul>
  • 16. Developing Context Sensitive Solutions: A Tale of Two Toll Roads <ul><li>Mike Heiligenstein, Executive Director </li></ul><ul><li>IBTTA Facilities Maintenance </li></ul>

×