1. Mark E. Hallenbeck Director Washington State Transportation Center (TRAC) University of Washington Seattle, WA USA

2. TRAC  WSDOT: “Has problems” Has money to solve problems  UW (and WSU) Bright people Need money Like to solve problems

3. TRAC  Big problem: WSDOT culture = University culture  TRAC’s role Help the two organizations work together (Communication!)

4. Mark’s Role at TRAC  Connect WSDOT staff and UW faculty/staff Any transportation related subject  Serve as a point of contact and problem solver  Perform research

5. But I also get to teach (but not this year)  Courses Intelligent Transportation Systems (when budgets allow) Urban Transportation Planning (used to)  Office location 1107 NE 45 th St, Suite #535 (west of the Ave.) 543-6261 tracmark@u.washington.edu

6. Major Personal Research Areas What can you measure, how do you measure it, and how can you use it to describe/improve system performance or meet policy needs? Congestion monitoring Intelligent transportation systems deployment and use Transportation’s role in growth management Traffic loading for pavement design

7. Congestion Monitoring The basic need is to monitor facility use and performance (real-time management/planning) Vehicle use Person use Speeds (travel time) Reliability (frequency of congestion)

8. Congestion Monitoring  These needs must be met in a manner that allows for: collection of adequate information lowest possible cost comparison between modes / strategies tracking of policy decisions

9. Congestion Monitoring - State Track congestion for Legislative / DOT policy needs Identify size and scope of congestion problem Allow evaluation of congestion relief efforts Allow for comparison / prioritization between locations

10. Congestion Measures ● V / C can be ●Hourly ●Daily ●Peak period ● How do you measure “C”? ● How do you measure “V”? ● How do you account for variation in “V”?

11. Congestion Measures Limitations in V / C have led to the adoption of alternative congestion measures, mostly: Travel time, Speed, or Delay

12. Using Intelligent Transportation Systems ITS provides a variety of “continuous” data collection / surveillance systems that can provide travel time and speed data New traffic control systems Vehicle location systems (the GPS in your phone can turn your car into a probe)

20. Time PMAM 02468101224681012 Time PMAM 02468101224681012 405 5 Montlake Blvd. 520 Arboretum 92nd Ave. B’vue. Way 148th Ave. NE 60th St. 84th Ave. Lk. Wash. Uncongested, near speed limit Restricted movement but near speed limit More heavily congested, 45 - 55 mph Extremely congested, unstable flow Westbound SR 520 Traffic Profile General Purpose Lanes 1997 Weekday Average Eastbound

27. SR 520 Performance After Tolling  Daily, then weekly, then monthly reporting  Changes from initial condition  Summary statistics

28. Geographic ContextColorEqualsStatisticalChange

29. Volume Variability and Change

30. Peak- Period Cross-lake Trips 30 Peak-Period Person-Trips Across Lake Washington Post Tolling Peak-Period Person-Trips Across Lake Washington Pre Tolling

31. 31 Increased SR 520 bus service more than 20 percentIncreased SR 520 bus service more than 20 percent o 15 percent ridership increase due to service investment o 10 percent ridership increase since tolling started Vanpools in the SR 520 corridor have increased 18 percentVanpools in the SR 520 corridor have increased 18 percent Park and ride usage is similar to pre-tolling with most lots remaining fullPark and ride usage is similar to pre-tolling with most lots remaining full Improved travel times on SR 520 means improved on-time performanceImproved travel times on SR 520 means improved on-time performance Successful Transit Deployment

32. Travel Time Variability and Change

33. Geographic Changes in Congestion NowBefore

34. Arterial Travel Times

35. Arterial Performance  So what about arterials? Can we use data collected at signals? Do we need to change how it is recorded/reported? How do we present that data? Can we use other data sources? Blue tooth readers? Vehicle probes Single points? Or actually tracking vehicles?

36. Arterial Performance  What about bike use?  What about pedestrian use?  http://vimeo.com/24572222 http://vimeo.com/24572222

37. Potential Research questions  How do you collect bike/ped data? On a trail At an intersection Jaywalking behavior Along a corridor  How do you analyze these data? Sample plan? Sampling what? For what?  How do you report performance of bike/ped?

38. What About Freight (Trucks?)

39. Zone to Zone travel via GPS

40. ITS and Congestion Monitoring Data Sources How do we get data from existing control systems? How do we work with control systems to place surveillance in the right places? Do we use crowd sourced data? With what privacy controls? What do we ask for? How do we use it? What do we do with the data once we have it?

41. Research NW Region Freeway Performance  How do you take dissimilar data and make a cohesive, functional database / decision support system? Roadway performance (volume, speed) Incidents (accidents, disabled vehicles, debris) Special Events (unusual volumes) Weather  Note different geographic / temporal attributes

42. SHRP2 - LO3: Analytic Procedures for Determining Impacts of Reliability Mitigation Strategies  Determine the causes of congestion  Develop analytical metrics that describe how operational improvements reduce delays  (Results were also used for a WSDOT project looking at the benefits of incident response)

43. Normal Congestion Incident Condition X Congested Slower than free flow Faster than normal Slower than normal ABCDE Travelers entering at C or D do better under incident conditions Travelers using A to C experience unusually long delay Travelers going from A to E only experience moderate time increases

44. Major Blocking Crash Occurs 5:30 – 7 AM, ~Milepost 23

45. Probability of Being in Congestion: Rain Versus No Rain SR 520 Westbound From Bellevue to Seattle

46. Increase in Mean Travel Times With the Increase in Probability of Congestion Due to Rain I-90 Westbound from Issaquah

47. Comparison of Mean Travel Times With and Without the Influence of Incidents. I-5 Northbound Through the Seattle Central Business District

48. Expected Travel Time Under Different Conditions I-90 Issaquah Segment WB Weekdays This study measures the difference between “No Disruption” and “Incident” conditions – and calls it “incident caused”

49. Findings  Disruptions (crashes, incidents and bad weather) cause 30 percent of all delay on the Seattle metropolitan freeway system Crashes alone cause ~ 11 percent of delay  This equals 5,300,000 veh-hours of delay in 2006 Crashes cause 1,950,000 veh-hrs of delay

50. Findings  “Incidents” by themselves do not cause congestion The same is true for crashes  Incidents only cause congestion when the disruption they create causes functional capacity to fall below actual demand

51. Summary Effects of Incidents Assumes that a linear relationship applies (see report): Average Vehicle Delay per Minute of Incident 576 Veh-min / min Average Effect of a Lane Closure 814 veh-min/min

52. Variability in Incident Delays High Delay Segments CorridorVeh-Min Delay / Min of Incident Veh-Min Delay / Min of Closure I-405 Bellevue SB 20891915 I-5 North Seattle SB 19752106 SR 167 Renton NB 1652591 I-5 South (Fed Way) SB 11441493 I-405 Kennydale SB 9071235 SR 520 WB Redmond 919174 Low Delay Segments CorridorVeh-Min Delay / Min of Incident Veh-Min Delay / Min of Closure I-90 Issaquah EB 10<1 I-90 Bellevue EB 1539 I-5 Everett SB6361 I-90 Issaquah WB 8553 I-405 North NB95268 SR 167 Auburn NB 139117

53. There Are Other Important Benefits – Not Included in the Travel Time Benefit  Safety: Crash rates increase under incident conditions In AM peak, crash probability more than doubles on most corridors when an event (crash/incident) has affected travel In PM peak, crash probability increases by ~50% (Midday less stable, but on average it too doubles) At night there aren’t enough crashes to be statistically significant

54. ITS Can Also Give Information Directly to the Public

55. WSDOT’s Seattle Congestion Map

57. Transit Information (OneBusAway) Phone (voice or SMS) iPhoneWeb

58. Framework for Monitoring Change in VMT  RCW says that we will reduce VMT/Capita by 50% by 2050  Monitor whether the state is on track and why

59. VMT Reduction Dashboard  Primary Indicators Statewide VMT Statewide VMT / Capita  Programmatic Indicators Statewide annual transit ridership Percentage of people in SOV by major urban corridor (peak periods only) Trips Reduced by CTR program VMT reduced by CTR program Number of employees covered by CTR program Cost per VMT reduced by CTR VMT Reduced by specific projects (construction mitigation efforts by project) Volume of use of key non-motorized facilities (e.g., bike trail on SR 520) Special event vehicle volumes versus attendance CurrentTrend

60. VMT Reduction Dashboard  Regional or Jurisdiction Level Indicators County VMT County VMT / Capita County transit ridership Could use the number of revenue hours of transit service provided Walkscore (or combined Walk/Transit/Bike Score) per city/county Percent of population living within GTEC (by jurisdiction) Alternative: Percent of population living within an area with a Walkscore/Transit score of 80 (or some other value) Percent of jobs located within a GTEC (by jurisdiction) Alternative: Percent of jobs located within either walkscore, transit score, or bike score of 80 (or some other value) Volume of use of key non-motorized facilities (specific to jurisdiction) Mode split during peak periods to major job centers (or downtown, or…) Percent of planned walk/bike network completed  Indicators of Future Performance Number of cities in compliance with VMT reduction criteria Needs work to identify the criteria to be tracked (see Mark Anderson) Change in land use permits (sq ft?) granted within the last five years in GTECs or designated urban centers versus those granted outside of those areas (by jurisdiction) Census journey to work mode split (update frequency?) Vehicle registrations per capita

61. Growth Management: The Concept of Concurrency  Developed in support of growth management efforts  Development should not occur unless an adequate transportation system exists (or will exist) to handle that growth

62. The Initial Problem  How do we determine if “adequate transportation” exists?”  State law says that each jurisdiction defines “adequate” within their jurisdiction State routes aren’t included in the process

63. Cities Usually Measure Congestion (v/c)  Is roadway congestion the only “transportation facility” that matters?  Does the term “adequate transportation facilities” include other modes of travel?

64. Results: Other Limitations  Concurrency is applied only to “local” impacts, This skews development decisions Regional impacts soon “trump” local decisions  Many “solutions” require commitments from other jurisdictions No money source exists for these services No local control exists over these services

65. Regional Trip Making Origin: Trip concentration Destination: Trip distribution Line Haul Portion All three parts of a trip must be shared ride mode friendly if an alternative to the SOV is to be used.

66. Recommendations  Need both Local and Regional concurrency Local Determine key modes Permit / No permit decision Regional Remove financial incentives to export costs

67. GTEC Assistance  Cities understand what GTECs are  City politics and land developers do not always agree with the idea of compact, mixed use, walkable development

68. Measurement of Smart Growth Impacts  Research Questions: Does Smart Growth “work?” Is it simply self selection? Does it reduce VMT? Do people walk/bike more, if… I put in more sidewalks Mix uses

69. Measurement of Smart Growth Impacts  Current WSDOT projects: RideshareOnline Secondary function: document effectiveness of commute trip reduction efforts Our role: help with documentation Prediction of VMT reduction impacts Framework for monitoring VMT reductions

70. Destination 2030 - Taking An Alternative Route  A project done in four-week time span for King County Funded through budget office At the request of the County executive In conjunction with Booze Allen  Also known as “Examination of Regional Tolling”

71. Initially Tolled Network

72. Traffic Load Data And Pavement Design Engineers Traffic Load Inputs For the MEPDG (Mechanistic-Empirical Pavement Design Guide)

75. Tandem Axle Load Distribution – Mixed Truck Loads 0 0.02 0.04 0.06 0.08 0.1 0.12 68101214161820222426283032343638404244464850 Maximum Weight in a Given Axle Weight Group (x 1,000 lbs) Fraction of Tandem Axles In Weight Group

76. ESAL Comparison Lightly Loaded Tandems = 0.186 (flexible) Moderately Loaded Tandems = 0.355 Heavily Loaded Tandems = 0.666 Simple conclusion: Not knowing the loaded/unloaded condition can equal a 3X error in life expectancy

77. Time of Day Truck Volume Variation

78. Day of Week Truck Volume Variation

79. Seasonal Truck Volume Variation