Working Description of the TRB 2013 Summer Workshop on Challenges and Opportunities In

Working Description of the TRB 2013 Summer Workshop on Challenges and Opportunities in Road Vehicle Automation

March 25, 2013

This summary represents the most current synopsis of the plan for the TRB 2013 workshop on road vehicle automation. It is being provided to the TRB workshop planning group as a shared point of reference for continued development.

1.  General update from planning meetings (as of our last meeting on March 1)

2.  Workshop overview

3.  Schedule—at least as a start

4.  Workshop planning groups (the names and email addresses for those who have signed up)

5.  Current break-out session descriptions

1. Update (last meeting held 1 March)

There are currently 11 break-out sessions; preliminary descriptions are provided in the following pages. There are more topics yet to be considered by the planning group, and, where we don’t have sufficient interest from organizers, some of the current session candidates may fall off the list. The first leader/organizers for the sessions are named. We will seek additional volunteers to lead the organization of sessions as needed. We anticipate as many as 200 registrants, but there is a limit on how many parallel sessions can feasibly be produced.

·  Day 1 breakouts will focus on identifying the challenges and opportunities for each topic, and the session organizers may choose to include expert presentations to help to inform and focus the group discussion (as was done by some break-out sessions last summer).

·  Day 2 breakouts will focus on identifying the research needs topics and, where possible, drafts of the problem statement, objective and priority of the research topic.

Each break-out session will need, at a minimum, a facilitator to keep track of the session agenda and schedule and, perhaps, lead the discussion; a note-taker who keeps track of the session discussion on large note-pads (or on screen with a lap top), and a note-taker who takes more detailed notes for the record. With two long sessions per topic, the break-out sessions may need additional note-takers and facilitators, so that no one is exhausted.

During our 1 March meeting, we attached organizer names to sessions, with the understanding that the volunteers who lead the break-out session organization do not also have to be the facilitators or note-takers. Following the chart, just below, of the workshop schedule, I have made a table of organizers, other volunteers, and assignments. Please check for your name and correct/amend as needed.

There are also additional working groups within the overall planning group: communications, fund-raising, plenary sessions, demonstrations, and registration/conference logistics.

We have tentatively added a one-afternoon break-out session for presentation and discussion of the Graham Institute expert survey results. Steve Underwood and Mo Poorsartep are working from structured expert interviews towards the development of deployment milestones and a 30-year forecast. Mo provided an overview of this survey at the subcommittee session on January 17. This break-out session will present their report and solicit workshop feedback.

During the 1 March meeting, we spoke briefly about session content. Many breakout session descriptions seem to be assuming more advanced levels of automation. We agreed that organizers should take into consideration questions about how we may assimilate automation into society, and the probability that automation will be introduced in levels. It was suggested that we add a topic on “Business models to introduce automation”. However, it was believed that this topic, as a stand-alone, was premature.

We have also discussed the possibility of posting read-aheads to the workshop website. These reports, publications, or presentations would be selected to provide background on the break-out session topics and prepare workshop participants for an informed discussion. Another suggestion made for pre-workshop activity was to produce webinars that summarized some of the key learning from last year’s workshop, or that provided information towards a certain workshop topic. It is noted that webinars are labor-intensive endeavors.

2. Workshop Overview

The 2013 TRB workshop on road vehicle automaton is planned to run Tuesday July 16 through Thursday July 18, on Stanford University campus, in Palo Alto, California. Tuesday and Wednesday morning will be devoted to plenary speakers; Tuesday and Wednesday afternoons are reserved for break-out sessions; Thursday morning is for plenary report-outs from the discussion groups. Depending upon how the demos are organized, demonstrations may be scheduled for afternoons only and run Tuesday through Thursday afternoons, or they may run throughout the workshop. Thursday afternoon, right after lunch (arrangements for Thursday lunch TBD) is tentatively reserved for (1) a more focused review of the USDOT research plan, for those who choose to stay and participate, followed by (2) the workshop planning committee meeting. Friday is reserved for ancillary meetings, such as other TRB committee meetings and the trilateral Working Group on Road Vehicle Automation. These ancillary groups will work directly with Stanford to make room reservations and arrange/pay for additional resources.

WORKSHOP OVERVIEW / Tuesday July 16 / Wednesday July 17 / Thursday July 18 /
Morning session / Plenary Speakers / Demos may run by sign-up in parallel with the plenary and break-out sessions / Plenary Speakers / Demos may run by sign-up in parallel with the plenary and break-out sessions / Plenary closing session summarizing results of break-out sessions / Demos may run by sign-up in parallel with the plenary and break-out sessions
Afternoon session / Part 1 for all break-out sessions, focused on understanding the topic issue / Part 2 for all break-out sessions, focused on identifying research gaps and needs / (1)  Focused review of USDOT research plan
(2)  Workshop planners wrap-up
Evening / Reception / Open / Open

3. Schedule

Leading into the workshop:

·  NOW: Start planning the break-out sessions—Identify leaders who will convene the break-out session planning groups, invite the volunteers who signed up at the 1/17 subcommittee meeting, set up first and subsequent meetings to plan and produce the break-out sessions. Leaders need access to toll-free conference numbers, whether a number of their own or another volunteer. Plan to meet weekly until your session takes form (objectives, agenda, focus), then focus on the details (e.g., securing speakers, developing supporting materials, presentations, discussion guide).

·  March 15 (the date has already passed!): Formal Save the date announcement with dates and as much detail as we’ve got. This assumes a primary website for user reference.

·  Late April: Registration fee established and sleeping room block (or facsimile) established! Communications-newsletter to LinkedIn subscribers. Registration site opened on website. Should have ancillary meetings identified. All sponsoring TRB Committee chairs send announcement to their members and friends.

·  May 24: Near-to-final draft break-out session agendas and materials distributed to all workshop planners for review, shared awareness, and coordination

·  Late May: Another newsletter with updates

·  June 28: FINALIZED--All workshop speakers, supporting roles, materials, including break-out session descriptions and materials, managing demos, and ancillary meetings.

·  July 5: Final pre-workshop communications; final agenda etc, read-aheads are posted to the site and sent on Linked In

·  June 16-19: WORKSHOP!!!

4. Break-out Session Organizer Assignments

Task

/

Organizer Leads

/

Comments

/

Interest from Jan 17 subcommittee session

Plenaries / Jane Lappin, , Steve Shladover, , Bob Denaro, , others as needed / There’s time for 7 plenary speakers each morning
Fund-raising / Bob Denaro, , Greg Fitch, , Alain Kornhauser, , Steve Shladover, eley,edu, / Greg suggested Bendix and Wabco
Communications / Greg Fitch, , Andy Palanisamy, Jane Lappin,
Poster session / Kevin Heaslip, / This was not among the sign-up sheets at TRB; others are welcome to join / Zia Wadud;
Demos / Jim Misener, Barry Pekilis, Bryant Walker Smith
Registration/Conference Logistics / Elaine Adolfo, Stanford Law, Rich Cunard, TRB
Break-out session 1. Challenges and Opportunities in Infrastructure/Operations / Joe Peters, joe.peters.dot.gov, Bob Ferlis, / Siva Narla,; Ginger Goodin, ; Reinhard Pfliegl, ; Dick Mudge, ; Shannon McDonald, smcdonald.siu.edu; Chunming Qiao, ; Stan Young, ; Kevin Heaslip, ; Yu Yuan, ; Jim Misener, ; Bart van Arem, ; Bob Ferlis, ; Max Donath, ; Maxime Flement, ; Tony Newkirk, ; (electrified roadways)
…2…V2X and Architecture / Frank Perry, / Paul Rau, , will look within NHTSA for someone to help organize this session
…3…Risk, Liability and Insurance / Bryant Walker Smith, ; Steve Wood, ; Frank Douma, / Bryant Walker Smith, ; James Anderson, ; John Collins, ; Mohamed Benmimoun, ; Frank Douma, ; ; Maxime Flament, ; Eric Williams, IIHS,; ; Guy Fraker,
…4… Data Ownership, Protection, and Access / Walker Smith, Wood, Douma
…5… Testing, Certification and Licensing / SAE Committee / Steve Shladover, , will seek leadership from within the SAE Committee; we will also reach out to states and others with interest in this area / Rick Weiland, ; Fares Beiny, ; Mohamed Benmimoun, ; Frank Perry, ; Ching-Yao Chan, ; Siva Narla, ; ; Wei-Bin Zhang, ; ; Eric Williams, IIHS, ; Yu Yuan, ; , Chunming Qiao, ; Maxime Flament, ; ; Bryant Walker Smith,
…6…Cybersecurity / Jim Misener, Ed Fok, ; Alan Chachich / Mike Dinning and the TRB Cyber Security Subcommittee, ; Art Carter, ; Jim Misener, ; Chas McCarthy, ; R. Pfliegl, ; Peter Thompson, ; Ryan Gerdes, ; Alan Chachich, ;
…7… Shared Mobility and Transit / Stan Young, Shannon McDonald, Alain Kornhauser / Mohamed Benminoun, ; Rick Weiland, ; Wei-Bin Zhang, ; Fawzi Nashashibi, ; ; Tim Gordon, ; Paul Leiby, ; Geoff Wardle, ; Dick Mudge,
…8… Automated Commercial Vehicle Operations / This was not part of the groups offered at TRB
…9… Energy/Environment / Paul Leiby, / Mohammed Benmimoun, ; Tyler Folsom, ; Zia Wadud, ; ; Yu Yuan, ; Jim Misener, ; Phil Blythe, ; Ching-Yao Chan, ; Kevin Heaslip, ; Zia Wadud, ; Keith Kahl, ; Paul Leiby, (liaison, TRB Transportation Energy ADC70)
…10… Human Factors and Human-Machine Interfaces / Greg Fitch, , Michael Manser, , Paul Rau, / Chunming Quiao, ; Ader Sadek, ; Sean Wu; Kevin Hume, ; Max Donath, ; Janet Creaser; Mike Manser, ; Yu Yuan, ; Judith Burki-Cohen, ; Susan Cohen, ; Myra Blanco, ; Natasha Merat,
…11… Safety, Risk and Dependability / Tim Gordon / Was not part of the original sign-up sheets; needs volunteers

5. Break-out Session Descriptions

1.  Challenges and Opportunities in Infrastructure/Operations

·  What are the considerations for road owners/operators, tolling authorities?

·  What are the business models that enable vehicle and infrastructure system interaction?

·  What are the unique requirements for urban, highway and rural environments?

·  What are the opportunities for infrastructure to adapt to or support vehicle automation functions?

·  How to manage interactions between automated and manually operated vehicles?

2.  Challenges and Opportunities in V2X and Architecture

·  Benefits and issues for automated vehicles operating in autonomous or cooperative operation?

·  What needs to be done to bring each to fruition?

3.  Challenges and Opportunities in Risk, Liability and Insurance

·  How does ISO 26262 apply to vehicle automation?

·  How are liability issues likely to affect the design, cost, and deployment of automated vehicle technologies?

·  How are judges and juries likely to approach punitive damage awards?

·  What new service and business models may be appropriate for addressing liability?

·  What new insurance models may be appropriate for addressing liability?

·  What case studies could provide insight on these questions?

4.  Challenges and Opportunities in Data Ownership, Protection, and Access

·  What kind of data are likely to be collected—and in what form?

·  Who owns these data?

·  What special issues might automated vehicles raise for pretrial discovery?

·  How might automated vehicles implicate consumer privacy protections?

·  How might automated vehicles implicate Fourth Amendment protections?

·  How might automated vehicles implicate other restrictions on government use of data?

·  How might Federal Information Processing Standards apply to automated vehicles?

·  How should anonymity be handled?

·  Are there or should there be track-ability (trip privacy) constraints?

·  How does data ownership affect monetization?

5.  Challenges and Opportunities in Testing, Certification and Licensing

·  What are the roles of Federal agencies (e.g. NHTSA) and state authorities (DMVs) in defining guidelines and rules for automated driving?

·  Do on-board systems and automation functions become certified? How and by whom?

·  What kind of testing is needed to support certification of automated vehicles

·  Do vehicles need to periodically recertified

·  What kinds of standards are needed?

6.  Challenges and Opportunities in Cybersecurity

·  How to preserve system resiliency in the face of threat? What types of threats?

·  How does resiliency affect functionality and operations?

·  How to detect and handle misbehaving entities?

·  How to prevent intrusion to the supervisory control and data acquisition (SCADA) component of the automated system?

·  How does one present intrusion to the on-board or vehicular component of the automated system?

·  What are the institutions and policies necessary to address resiliency?

·  Do we need to create a new authority to oversee end-to-end cybersecurity?

·  What are the advantages and disadvantages in cybersecurity with autonomous or cooperative systems?

7.  Challenges and Opportunities for Shared Mobility and Transit

·  How can automation help improve mobility and accessibility across all segments of the population? Include buses, PRT and shared vehicles/shared rides as well as new automation concepts to help solve the “last mile” problem for public collective transport services.

·  Are there generational opportunities, e.g, ethos of younger generations to use shared, commoditized transportation, older populations who may need automation to assist in mobility, choice commuters who desire comfort and convenience?

·  What are the similar or dissimilar attributes of CVA to automated transit?

8.  Challenges and Opportunities forAutomated Commercial Vehicle Operations

·  How can automation best contribute to improving commercial vehicle operations?

·  What are the benefits in terms of increased productivity, safety, security enforcement and reduced energy consumption/emissions and labor cost savings, as well as the risks associated with labor relations and prolonged hours of service issues?