1
1
Developing Context Sensitive Solutions:
A Tale of Two Toll Roads
Mike Heiligenstein, Executive Director
IBTTA Facilities Maintenance
2
Tale 1: 183A
2
3
183A Project
• Built using a comprehensive
development agreement
Design-build
Guaranteed price and
completion date
Original contractor aesthetics/
landscape commitment 2.5%;
raised to 4%
Context sensitive solutions
process to be contractor’s
responsibility
“Context Sensitive
Design is thinking
beyond the pavement.”
US Department of Highways
Federal Highway
Administration
4
Context Sensitive Solutions Approach
• Partner with developer
Establish community outreach
Engage community in design and construction
Initiate dialogue regarding betterments
• Input from stakeholders
Aesthetics
Shared Use Path
Landscaping
Field Operations Building
Opportunities for betterments
3
5
183A CSS: Developer’s Role
• 4% allocation for
aesthetics/landscape
• Provide aesthetic concepts and
treatments
• Participate in community
outreach
• Provide options and costs to
Aesthetic Committee
6
183A CSS: Mobility Authority’s Role
• Establish Aesthetics
Committee
• Manage community
outreach
• Provide direction on
aesthetic concepts/
treatments
• Provide timely
decisions to ensure
adherence to design-
build schedule
• Approve costs and
budgets
4
7
Lessons From CDA Approach
• Aesthetics not contractor’s top priority
• Very difficult in design build
environment. Mobility Authority detailed
CSD with more specificity in next RFP
• Client had to drive process and develop
vision with both design build team and
consultant team
• Pricing of aesthetics elements left to
negotiation – after award of CDA-DB,
leverage shits to contractor
Difficult to pin down budget
• Unable to establish clear community
vision for overall aesthetics
Pace of development schedule
Lack of previous experience
8
Tale 2: 290E
5
9
290E Project
• Originally planned to be built
using comprehensive
development agreement
Design-build
Guaranteed price and
completion