Central Texas IH 35 Widening Project Short Course, October 2011

Greg A. Malatek, P.E.

Deputy District Engineer

Austin District

Robert E. Brydia

Research Scientist

Texas Transportation Inst.

More than 30 million travelers per year pass through this corridor – about 100,000 people a day.

Estimates suggest that 60% or more

of those driving the corridor

reside elsewhere.

IH 35 Main Street Texas Expansion

Section 1A

From Williamson County line to South FM 2268

6.02 miles

Construction is complete

Section 6B

From SH 22 to East/West split

2.22 miles

Construction is complete

Section 6A

From FM 310 to SH 22

4.68 miles

Construction is complete

Completed Construction

Section 3C

From FM 2063 to South Loop 340

3.41 miles

Construction ends Spring 2011

Under Construction

Section 5C

From FM 1304 to FM 310

5.46 miles

Bid Amount: $36.8 million

Construction Ends: Fall 2012

Under Construction

Section 3C

Under Construction

Section 3C

Section 1C

From FM 2484 to US 190 in Belton

8.0 miles

Bid Amount: $106.8 million

Construction Ends: Fall 2014

Section 5C

Section 1C

Section 5A

From North Loop 340 to FM 1858

13.37 miles

Bid Amount: $166.8 million

Construction Ends: Fall 2014

Under Construction

Section 3C Section 3C

Section 5C

Under Construction Section 1C

Section 3C

Section 5C

Section 5B

From FM 1858 to FM 1304

8.0 miles

Bid Amount: $100.9 million

Construction ends: Fall 2014

Section 5A

Section 3A(1)

From North Loop 363 to North Troy City Limits

6.38 miles

Construction Costs: $123.6 million

Construction Ends: Spring 2016

Funded PS&E

Section 5A

Funded PS&E

Section 3A(1)

Section 3A(2)

From North Troy City Limits to Woodlawn Road

9.59 miles

Construction Costs: $120.7 million

Construction Ends: Spring 2016

Section 5A

Funded PS&E

Section 3A(1)

Section 3A(2)

Section 1B

From FM 2268 to North FM 2484 in Salado

3.41 miles

Construction Costs: $70.4 million

Construction Ends: Spring 2015

Section 5A

Funded PS&E

Section 3A(1)

Section 3A(2)

Section 1B

Section 3B

From Woodlawn Road to FM 2063

6.23 miles

Construction Cost: $190 million

Construction Ends: Spring 2016

Section 3B

Brazos River frontage road bridges

Section 2B

From South Loop 363 to North Loop 363 in Temple

5.85 miles

Construction Costs: $200 million

Construction Funding Source: Prop 12 V2

ROW Costs: $110 million

Funded PS&E

Section 4

From South Loop 340 to North Loop 340 in Waco

7.90 miles

Construction Cost: $312.9 million

Construction Funding Source: Unfunded

ROW Costs: $45.1 million (Unfunded)

Unfunded PS&E

Section 5B Hillsboro Area Office

Section 3B Waco Area Office

Section 1B Georgetown AO

Section 3A(2) Belton Area Office

Section 3A(1) Belton Area Office

Section 5A Waco Area Office

Section 5C Hillsboro Area Office

Section 1C Georgetown Area Office

Section 3C Waco Area Office

Section 6 Hillsboro Area Office

Responsible Area Offices For Construction

TxDOT Requested TTI Assistance

Mobility Coordination

Traveler Information During Construction (TIDC)

Long Term Corridor Plan

Challenge the size of Texas

Over the next decade, I-35 will be the scene of $1.9 billion in construction.

Every construction delay along

that route has the potential

to impact someone in your district.

Miles Under Construction

I-35 Construction Policy

I-35 lane closures limited to evenings

No holiday lane closures Contractors fined for peak

hour lane closures Incentives for completing

construction ahead of schedule

Public Expectations

• Tell us what you plan to do, and do what you say

• Finish as quickly as possible • If lanes must be closed, make

sure there’s actual construction activity going on

• Minimize the impact of those closures

• Provide information about alternate routes

Challenge the size of Texas

I-35 crosses 7 TxDOT districts

It impacts every TxDOT district

As many as 8 projects active at a single time

~ 66% through traffic

> 75% trucks at night

I35TIDC - Vision

• Provide traveler information on current and projected travel conditions across multiple construction zones – Local

– Regional

– Corridor-wide

• Construction impact focused

I35TIDC Goals - Travelers

• Provide advance notification of planned lane closures and their anticipated impacts

• Provide real-time corridor condition information – Travel time – Delays – Queues

• Provide travelers with predicted delays for construction closures

I35TIDC Goals – Waco Operations

• Support / Supported by TxDOT Waco District ITS development

• Integrate with LoneStar where possible

• Provide video snapshots of traffic conditions from select locations within the corridor

• Support dissemination of incident information

Phase 1 of I35TIDC Deployment

• Receive scheduled lane closure information • Assess. If significant impacts:

– Alert project engineers – Deploy short-term lane closure monitoring and

queue warning system • Monitor and disseminate travel times along

corridor • Disseminate anticipated daily delays and 7-day

outlook via internet • DECEMBER 2011

Phase 2 of I35TIDC Deployment

• Disseminate predicted lane closure delays based on current real-time information

• Support dissemination of incident related information by TxDOT

• Expand to multi-faceted information dissemination strategy (en-route, pre-trip, targeted audiences, personal devices, etc)

• Performance monitoring and reports • MAY 2012

I35TIDC System

• Multiple components to overall traveler information system – Obtain information on planned closures – Assess potential impacts – Deploy short-term WZ monitoring – Travel time monitoring – Predicted closure impacts – Information dissemination – Performance metrics

Systems Engineering View

Lane Closure Assessment

• Identify those lane closures that will likely create queues and delays

• Predict queue lengths and duration

• Predict travel time delays

• Identify appropriate lane closure monitoring plan to implement (if any)

Lane Closure Predicted Impacts

Lane Closure Monitoring

• Detect when queues have developed and approximate length

• Provide real-time warning that traffic is slowed or stopped ahead

• Deployed as needed via an on-call

• Communicate with PCMS upstream to post warning messages when appropriate

Message Selection Logic

LANE CLOSED AHEAD

63 mph 67 mph 66 mph 65 mph

Speed Sensors

TRAFFIC SLOWS 3 MILES

42 mph 64 mph 62 mph 56 mph

3 miles

STOPPED TRAFFIC 2 MILES

25 mph 64 mph 52 mph 31 mph

2 miles

Travel Time Monitoring

• Display current corridor travel times to travelers

• Can be combined with other data for predictions

• Based on BT sensor deployment

• Display travel time information via PCMS

Travel Time Monitoring

• Bluetooth-based probe travel times

• Segment travel times • Pilot deployments

– 10 – 40 mile lengths – >3000 matches per day

• Ultimately 25-30 BT sensors to be deployed on I-35 in sections under construction

• Potential additional coverage on alternate routes

Lane Closure Impact Prediction

• Travelers need to know expected impacts (not current impacts) of lane-closure when they will be at lane-closure

• Develop system of providing expected impacts of ongoing lane closures based on current travel conditions

• Disseminate impacts: – far enough upstream to influence traveler decisions

– at key decision points upstream of lane closure

Traveler Information - Corridor

• PCMS – Integrated into LoneStar

– Travel time messages

– Support incident information

• Construction delay signs – Additional delay due to construction

– Human factors study of multiple sign concept

Traveler Information - Internet

• My35 website links / integration – Lane closure locations and predicted impacts – Corridor travel times – Corridor speed map

• Social media • TxDOT Dissemination

– HCRS – Camera snapshots – Incident information

My35.org

Push to Social Media

Public Outreach Tools

• Public meetings & hearings

• I-35 newsletter

• Email updates

• News releases

• Business community meetings

• 80 outreach efforts

Phase 1 Status

• Complete – Systems engineering – Concept development – Pilot deployments to test concepts

• In progress – Full-scale equipment procurement – Identification of deployment locations – Deployment – Software development – LoneStar integration

Questions?