ITS Heartland 2012 Annual Meeting Kansas City, MO Presented by Kyle Garrett, Senior Systems Engineer, Mixon-Hill Inc.

1. Kyle Garrett
ITS Heartland
March 27, 2012
3/27/2012 1

2. This is not (just) a car; it’s a…
 Multimedia center
 Internet node
 Navigation device
 Sensor platform
 Safety cocoon
 Automated driving
assistant
3/27/2012 2

3. Multiply by 250,000,000
 Congestion
 Crashes
 Delay
 Wear and tear on
the roadway
… with insufficient
public resources to
Photo by: EA
keep up and solve
problems
3/27/2012 3

4. What if…
 Vehicles using the roadways provided data
to monitor and control traffic
 Vehicles and the roadway communicated
with one another to reduce the likelihood
and consequences of incidents
 Vehicles monitored and reported roadway
conditions as they use the roadways
3/27/2012 4

5. Who would be involved?
 Automakers
 Drivers and the public
 Federal, state and local agencies
 OEM and Aftermarket Suppliers
 Communication Service Providers
 Engineering Services, ITS and Consultants
 Lawmakers
3/27/2012 5

6. What would a connected roadway
look like?
 It would provide timely information about
local conditions
 It could communicate from the roadway to
vehicles, operations centers, and/or other
locations on the roadway
 It would have sensors and controls to fit the
operational needs
3/27/2012 6

7. How would it communicate?
 Telematics are already using 3/4G
wireless, sometimes from user devices
 USDOT research is focused on DSRC
 Multiple paths promote innovation and
improve reliability
 Make the form of communications fit the
application
 Short-range for local information
 Networks for broader needs
3/27/2012 7

8. What could this mean for Safety?
 USDOT and automakers are leading the
charge on V2V and V2I safety applications
 Safety Pilot Model Deployment is ramping
up in Ann Arbor, Michigan
 Other agencies are looking at apps like
in-vehicle signing and enhanced
emergency response with signal
prioritization/preemption
 Decision on communications deployment
for safety due in 2013
3/27/2012 8

9. What could this mean for Mobility?
 More traffic probe data than we know what
to do with
 Traffic data from arterials and rural roads
as well as freeways, with less infrastructure
 Adaptive traffic controls based on
measured conditions in real time
 Enhanced usage data—volumes and
origin/destination for planning studies
3/27/2012 9

10. What could this mean for Mobility?
 Enhanced commercial vehicle operations
and enforcement apps
 Air quality and congestion management
opportunities, being pursued in the USDOT
AERIS program
3/27/2012 10

11. What could this mean for
Agency Operations?
 Gathering road weather data for winter
operations
 Assessing accelerometry-based ride
response for pavement defect and surface
conditions
 Considering connected vehicle technology
for high-occupancy toll (HOT) lanes
 Potential for mileage-based road user fees
3/27/2012 11

12. But what about…?
 Privacy – how are questions of personal
privacy and public good resolved?
 Data Ownership – who gets to use the
data, and under what conditions?
 Security – does the data need to be
secured, and how?
 Distracted Driving – how can this not
distract the driver?
3/27/2012 12

13. Where and when?
 AASHTO is evaluating connected vehicle
deployment opportunities and challenges
 Schedule is driven by the 2013 communi-
cations decision and vehicle fleet turnover
 Vehicle retrofits could speed things up
 AASHTO report leans toward near-term
opportunistic infrastructure deployment
 High-value apps in high-use locations
 Accelerate deployment as connected vehicle
population increases
3/27/2012 13

14. For further information
 USDOT/RITA/JPO Connected Vehicles
web site
http://www.its.dot.gov/connected_vehicle/connected_vehicle.htm
 AASHTO Connected Vehicle Infrastructure
Deployment Analysis
https://bookstore.transportation.org/Item_details.aspx?id=1931
Kyle Garrett, jgarrett502@gmail.com
3/27/2012 14