USDOT Connected Vehicle Research Program

Robert J. Sheehan ITS Multimodal and V2I Program Manager ITS Joint Program Office U.S. Department of Transportation (USDOT)

Connected Vehicle Research Program Overview  Introduction to the USDOT Connected Vehicle Research Program  Program Products □

Applications Research and Development

□

Enabling Technologies Research

□

Reference Implementation Architecture

□

Standards Development

□

Affiliated Test Beds

□

Research Data Exchange (RDE)

 Key Research Findings □

Why we think the timing is right for an opportunity to move research products into operational practice U.S. Department of Transportation ITS Joint Program Office

2

Transportation Challenges Safety 33,561 highway deaths in 2012 5,615,000 crashes in 2012 Leading cause of death for ages 4, 11-27

Mobility 5.5 billion hours of travel delay $121 billion cost of urban congestion

Environment 2.9 billion gallons of wasted fuel 56 billion lbs. of additional CO2

U.S. Department of Transportation ITS Joint Program Office

3

Connected Vehicles

Vehicle Data: Latitude, Longitude, Speed, Brake Status, Turn Signal Status, Vehicle Length, Vehicle Width, Bumper Height Infrastructure Data: Signal Phase and Timing, Drive 35 mph, 50 Parking Spaces Available

U.S. Department of Transportation ITS Joint Program Office

4

Path to Deployment Defined V2V Apps

Defined Safety (V2I), Mobility (V2V & V2I), AERIS and Weather Apps

Application Development

Pilots/Early Deployments

FHWA Deployment Guidelines NHTSA Decision to Move Forward with V2V Communication for Light Vehicles NHTSA Decision for Heavy Vehicles Safety Pilot in 2013

U.S. Department of Transportation ITS Joint Program Office

5

Connected Vehicle Application Research and Development Programs V2V Safety V2I

Mobility

Dynamic Mobility Applications

AERIS Environment Road Weather Applications

U.S. Department of Transportation ITS Joint Program Office

6

Connected Vehicle Applications V2I Safety

Environment

Eco-Approach and Departure at Signalized Intersections Eco-Traffic Signal Timing Eco-Traffic Signal Priority Connected Eco-Driving Wireless Inductive/Resonance Charging Eco-Lanes Management Eco-Speed Harmonization Eco-Cooperative Adaptive Cruise Control Eco-Traveler Information Emergency Electronic Brake Lights (EEBL) Eco-Ramp Metering Forward Collision Warning (FCW) Low Emissions Zone Management Intersection Movement Assist (IMA) AFV Charging / Fueling Information Left Turn Assist (LTA) Eco-Smart Parking Blind Spot/Lane Change Warning Dynamic Eco-Routing (light vehicle, (BSW/LCW) transit, freight) Do Not Pass Warning (DNPW) Eco-ICM Decision Support System Vehicle Turning Right in Front of Bus Warning (Transit) Red Light Violation Warning Curve Speed Warning Stop Sign Gap Assist Spot Weather Impact Warning Reduced Speed/Work Zone Warning Pedestrian in Signalized Crosswalk Warning (Transit)

V2V Safety

Road Weather Motorist Advisories and Warnings (MAW) Enhanced MDSS Vehicle Data Translator (VDT) Weather Response Traffic Information (WxTINFO)

Agency Data

Probe-based Pavement Maintenance Probe-enabled Traffic Monitoring Vehicle Classification-based Traffic Studies CV-enabled Turning Movement & Intersection Analysis CV-enabled Origin-Destination Studies

Please see your handout

Mobility Advanced Traveler Information System Intelligent Traffic Signal System (I-SIG) Signal Priority (transit, freight) Mobile Accessible Pedestrian Signal System (PED-SIG) Emergency Vehicle Preemption (PREEMPT) Dynamic Speed Harmonization (SPD-HARM) Queue Warning (Q-WARN) Cooperative Adaptive Cruise Control (CACC) Incident Scene Pre-Arrival Staging Guidance for Emergency Responders (RESP-STG) Incident Scene Work Zone Alerts for Drivers and Workers (INC-ZONE) Emergency Communications and Evacuation (EVAC) Connection Protection (T-CONNECT) Dynamic Transit Operations (T-DISP) Dynamic Ridesharing (D-RIDE) Freight-Specific Dynamic Travel Planning and Performance Drayage Optimization

Smart Roadside Wireless Inspection Smart Truck Parking U.S. Department of Transportation

7

Safety – Crash Prevention  Vehicle-to-Vehicle (V2V) Communications

 Vehicle-to-Infrastructure (V2I) Communications

 V2V and V2I communications reduce crashes through: 

Driver Advisories – hazards ahead



Driver Warnings – immediate crash hazards



Vehicle Control (Connected Automation)

V2V and V2I applications have the potential to address up to 80% of vehicle crashes involving unimpaired drivers U.S. Department of Transportation ITS Joint Program Office

8

Safety Applications

V2V

     

Forward Collision Warning (FCW) Emergency Electronic Brake Light (EEBL) Blind Spot/Lane Change Warning (BSW/LCW) Do Not Pass Warning (DNPW) Intersection Movement Assist (IMA) Left Turn Assist (LTA)

V2I

   

Curve Speed Warning (CSW) Red Light Violation Warning (RLVW) Stop Sign Gap Assist (SSGA) Transit Pedestrian Warning U.S. Department of Transportation ITS Joint Program Office

9

9

Mobility – Better Data, Many Applications Data

Applications Reduce Speed 35 MPH

Transit Signal Priority

Weather Application

Data Environment

Fleet Management/ Dynamic Route Guidance

Truck Data

Transit Data

U.S. Department of Transportation ITS Joint Program Office

10

V2I Mobility Applications

U.S. Department of Transportation ITS Joint Program Office

11

Data Capture and Management (DCM) – Develop and Deploy Relevant Data Environments  OBJECTIVE: Develop data environments that enable integration of data from multiple sources for use in transportation management and performance measurement  STATUS: Eight data environments created and deployed on the Research Data Exchange (RDE) □ The DCM program has demonstrated it is possible to assemble multiple integrated data environments to support research □ Developed guidelines for consistent meta-data □ Combined and organized diverse data in a logical way  WHAT'S STILL NEEDED: Explore integrated real-time data environments □ Move beyond archival environments of pre-connected vehicle/traveler data □ Create integrated data environments focused on competing alternative capture protocols and communications media to address key research questions □ Support real-time data provisioning for application prototypes

www.its-rde.net

U.S. Department of Transportation ITS Joint Program Office

12

Environment – AERIS: Operational Scenarios and Applications ECO-LANES o o

Eco-Lanes Management (similar to HOV lanes)

o

Eco-Cooperative Adaptive Cruise Control (similar to adaptive cruise control and

Eco-Speed Harmonization

(similar to variable speed limits)

platooning)

Eco-Ramp Metering (similar to ramp metering)

o o

Connected Eco-Driving (similar to eco-driving

strategies)

Wireless Inductive/Resonance Charging

o o

Eco-Traveler Information Applications (similar to

ECO-INTEGRATED CORRIDOR MANAGEMENT o

Eco-ICM Decision Support System (similar

o o o o o

Eco-Signal Operations Applications

ATIS)

ECO-SIGNAL OPERATIONS o

Eco-Approach and Departure at Signalized Intersections (uses SPaT data )

o

Eco-Traffic Signal Timing

o

Eco-Traffic Signal Priority

o

Connected Eco-Driving (similar to eco-driving

o

(similar to adaptive traffic signal systems) (similar to traffic signal priority)

strategies)

Wireless Inductive/Resonance Charging

LOW EMISSIONS ZONES o

Low Emissions Zone Management (similar to existing Low Emissions Zones)

to ICM)

o

Connected Eco-Driving

o

Eco-Traveler Information Applications (similar to ATIS)

Eco-Lanes Applications Low Emissions Zone s Applications Eco-Traveler Information Applications

(similar to eco-driving strategies)

Incident Management Applications

ECO-TRAVELER INFORMATION o

AFV Charging/Fueling Information (similar to navigation systems providing

o o o o o o

Eco-Smart Parking (similar to parking applications)

information on gas station locations)

Dynamic Eco-Routing (similar to navigation systems) Dynamic Eco-Transit Routing (similar to AVL routing) Dynamic Eco-Freight Routing (similar to AVL routing) Multi-Modal Traveler Information (similar to ATIS) Connected Eco-Driving (similar to eco-driving strategies) U.S. Department of Transportation ITS Joint Program Office

13

Road-Weather Management and Agency Operations

U.S. Department of Transportation ITS Joint Program Office

14

Enabling Technologies: Connected Vehicle Data

Data V2I Communications Support Safety, Mobility, and Environmental Applications: • Signal Phase and Timing (SPaT) data supports red light violation warning (safety), arterial speed harmonization (mobility), and eco-signal operations (environment). • The Basic Safety Message, developed for V2V safety applications, also supports the intelligent traffic signal systems mobility application. • Probe data supports transportation operations, traveler information, transportation planning, and asset management. Common functions shared across applications: positioning, mapping, and communications.

U.S. Department of Transportation ITS Joint Program Office

15

Open Source Application Development Portal

www.itsforge.net

 Portal for sharing documentation and source code from USDOTsponsored application prototyping efforts  By end of 2014, will be populated with materials describing 20+ connected vehicle applications  Contributed code must meet documentation guidelines  Search and download functions  In prototype form now 

Enhanced Release 1 expected summer 2014 U.S. Department of Transportation ITS Joint Program Office

16

Enabling Technologies: Roadside Equipment for Connected Vehicles Equipment USDOT tested devices for placement on the Research Qualified Products List (RQPL). Five vendors of connected vehicle roadside equipment are currently on the list. Devices are based on RSE Specification v3.0. Roadside Unit (RSU) Specification v4.0 will be available spring 2014. It contains updates to the physical hardware, management information base (MIB), and firmware. Devices compliant with the 5.9 GHz DSRC RSU Specification v4.0 are expected to be available fall 2014. Other connected vehicle deployments are encouraged to use equipment compliant with the RSU specification v4.0. Results from Safety Pilot and Integrated V2I Prototype development will be used to develop a V2I reference implementation. U.S. Department of Transportation ITS Joint Program Office

17

V2I Reference Implementation  A system of specifications and requirements that allow the various components of V2I hardware, software, and firmware to work together  An agency will be able to select the capabilities and applications desired at a given installation  Under development now □

Initial testing Summer 2014

□

Field testing in Orlando late 2014

U.S. Department of Transportation ITS Joint Program Office

18

Research Data Exchange

www.its-rde.net

 Promotes sharing of archived and real-time connected vehicle data collected in USDOT-sponsored research efforts and field tests  2 TB of well-organized and documented data  Drawn from a dozen geographic locations across the country  Multi-source data (traditional sensor plus probe and connected vehicle data)  Search and download functions  Available now U.S. Department of Transportation ITS Joint Program Office

19

Standards in Connected Vehicles

Standards Interface Standards Are Essential USDOT is working with public and private sectors to define: • Communications standards for DSRC • Other media, e.g., 4G LTE and/or HD radio may be used for appropriate applications • Information exchange standards: • Message sets for V2X [SAE J2735] • Minimum performance requirements for V2X messaging [SAE J2945.x] • Signal controller messages • Certification processes will also be established to ensure off-theshelf interoperability of devices

U.S. Department of Transportation ITS Joint Program Office

20

Connected Vehicle Reference Implementation (CVRIA)  A Framework for integrating technologies and identifying interfaces for standardization  Enterprise  Functional  Physical  Communications  Under development now

U.S. Department of Transportation ITS Joint Program Office

21

Affiliated Connected Vehicle Test Beds  The vision is to have multiple interoperable locations as part of one connected system moving toward nation-wide deployment. □

Common architecture

□

Common standards

□

Independent operations

□

Shared resources

Vision

U.S. Department of Transportation ITS Joint Program Office

22

USDOT Test Bed Resources  Qualified Product List for RSE □

Five vendors

 Qualified Product List for Onboard Equipment (OBE) □

Vehicle Awareness Devices

□

Aftermarket Safety Devices

 Portable RSE Trailers  Network Listeners/Sniffers

 Test Bed Operations Staff  Signal Phase and Timing (SPaT) Resources □

Listeners

□

Interface standards from FHWA

 Security Credential Management System (SCMS) □

1609.2 certificate management system

U.S. Department of Transportation ITS Joint Program Office

23

Policy Issues: Deployment Scenarios  USDOT asked AASHTO to create a vision of a national connected vehicle infrastructure  Provides guidance to state agencies and DOTs, including: □

Infrastructure needs at regional and national levels

□

Illustrations of typical deployments at signalized intersections, urban freeways, rural roadways, international border crossings, and other locations

□

System and equipment needs and siting requirements

□

Operations, maintenance and institutional issues

□

Deployment cost estimates

 Available now U.S. Department of Transportation ITS Joint Program Office

24

Policy Issues: Security  Challenges □

Message validity

□

Security entity

□

Network

□

Business models for security operations

□

Certification Processes for Equipment and Systems

 Security Credential Management System (SCMS) □

Under development now, will be available in prototype form for pilot deployments U.S. Department of Transportation ITS Joint Program Office

25

Policy Issues: Privacy  A user cannot be tracked along his journey or identified without appropriate authorization.  User privacy can be protected further through policy means. We’ve done initial privacy analysis of the system and will have privacy experts do a comprehensive review of any final system proposed for implementation

U.S. Department of Transportation ITS Joint Program Office

26

Connected Vehicle Pilot Deployments: Our Goals  CV Pilots Program Goals: □

Accelerate early deployment of Connected Vehicle technology

□

Understand and estimate benefits associated with deployment

□

Identify and solve key technical and institutional barriers

 Pilots will serve as initial implementations of connected vehicle technology deployed in real world settings □

Pilot deployments are not field tests, and (if successful) are expected to remain in operational practice at the completion of the pilot period

 Request for Information (RFI) issued March 2014  Procurement action anticipated for multiple pilot deployment concepts in 2015

U.S. Department of Transportation ITS Joint Program Office

27

Connected/Automated Vehicles An automated vehicle communicates with other vehicles and the infrastructure to self-drive.

vs.

Source: Carnegie Mellon University

An autonomous vehicle is selfcontained and does not interface with other vehicles or infrastructure. Source: Carnegie Mellon University

Connected vehicle technology is an important input to realizing the full potential benefits and broad-scale implementation of the highest level of automation. U.S. Department of Transportation ITS Joint Program Office

28

Stay Connected Visit our website for information on: • Webinars • Events • Publications • News

Twitter: @ITSJPODirector Facebook: https://www.facebook.com/DOTRITA Website: http://www.its.dot.gov U.S. Department of Transportation ITS Joint Program Office

29

AASHTO Connected Vehicle support Institutions SSOM Briefing May 6th, 2014

Background • • • • • •

What is it? Who is it? How did it come about? What do they do? What has been achieved History with SSOM & Other AASHTO Committees • Possible future relationship to SSOM & other AASHTO Committees 2

What is it? • Technical group consisting of states, counties, associations interested in advancing the connected vehicle program in their own locations and nationally known as the “AASHTO Deployment Coalition” • Leadership group of states, counties, auto manufactures, USDOT and associations interested in advancing the CV program nationally known as the

“Executive Leadership Team” or “ELT”

3

Who is it? • AASHTO Deployment Coalition (Technical Working Group)  New York, Virginia, Florida, Pennsylvania, Michigan, Minnesota, Texas, Idaho, Utah, Washington State, California, Arizona  Palm Beach County, Florida; Oakland County, Michigan; Maricopa County, AZ; Metropolitan Transportation Commission Bay Area, CA  Transport Canada  Connections to the VIIC, joint meetings, calls, etc. 4

Who is it? ELT • Auto Industry       

GM, Ford, Chrysler Toyota, Honda, Nissan Hyundai, Audi, KIA Mercedes, BMW, VW Global Auto Makers Alliance VII Consortium

• Transport Canada 5

• USDOT  NHTSA, JPO, FHWA

• AASHTO States  MI, UT, CA, AZ, NY  VA, WS, MN, TX, FL, PA, CO, MTC, AASHTO President

• Associations  NACO, ITE, ITSA, IBTTA, AASHTO

How Did it Come About? • Deployment Coalition (Technical Working Group)  Part of a stakeholder group for FHWA early 2000’s  ~ 2003 becomes more formally recognized as the VII Working Group, complementing the auto industries’ VII technical group and solidifying as an open public team supporting the VII program managed & supported by USDOT JPO  Over the years grew into a group that had an identity and numerous relationships with the broad Connected Vehicle community

6

What do they Do? (Technical Working Group) • Participate in USDOT stakeholder meetings ~ 6 plus/year  Security, Data Management, CVRIA, SAE J2735 message sets, program updates • Monthly webinars, auto industry, issue discussions, state updates, projects • Cooperative Transportation System Pooled Fund  Implementation work ~ AZ/CA test sites

• Speakers at conferences, workshops, stakeholder meetings, state meetings, county meetings, ITS meetings • Members of ITE CV Task Force, ITSA CV task force • Oversee projects such as National Infrastructure Footprint Analysis

7

How did it come about • Executive Leadership Team  Fall 2003 AASHTO Annual meeting in Utah  AASHTO President, FHWA, AASHTO discussed how to manage the emerging VII program  Conceived a high level leadership group consisting of States, Auto Industry and USDOT  Organized an executive breakfast at Feb 2004 legislative briefing Presented the program concept and asked do we want to work together on this effort Answer - yes 8

What do they do? ELT • Two or more meetings every year • Discuss issues such as  Security, privacy, education, infrastructure, aftermarket devices, implementation, support resolutions on joint development, receive briefings on the program

• Learn about the internal and external issues facing each group and ways we might work together 9

What have they achieved? • Deployment Coalition (Technical working group)  2008? States wanted more influence Held a facilitated session with FHWA and states discussing most effective ways to work together

 2009 “AASHTO IntelliDriveSM Strategic Plan  Leadership, Partnerships, Communications, Stable environment, Research, Deployment Much of this work is still valid today 10

What have they achieved? • Deployment Coalition (Technical working group)  2011 AASHTO Connected Vehicle Deployment Analysis - themes  setting the direction, showing success, Jump starting deployments, expanding the field, taking solutions to market, growing to meet demand Strategies 2011 – 2020 Implementation of a national DSRC Footprint

 AASHTO National Infrastructure Footprint Analysis  Positive reputation and a sustaining institution for technical engagement 11

What have they achieved? • Executive Leadership Team  Privacy Guidelines  Auto industry site visits  Resolution supporting research to implementation  PASSED AND ADOPTED by the VII Executive Leadership Team on May 15th, 2008 by the following representing their membership:

 Aftermarket device discussions  DSRC spectrum discussions and leadership  Conversations and understanding of the different business environments  Security and Infrastructure discussions  Positive reputation and a sustaining institution for engagement  More!! 12

History with SSOM & other AASHTO Committees • SSOM  Information exchange & briefings  NCHRP benefit costs analysis State agency DSRC readiness New Road Map proposal + follow on research

 Resolutions  Policy Resolutions (PPR) Palm Desert, California – October 24, 2009 SCOH & AASHTO Board of Directors STANDING COMMITTEE ON HIGHWAYS – SUBCOMMITTEE ON SYSTEMS OPERATION AND MANAGEMENT – support IntelliDrive

13

History with SSOM & other AASHTO Committees • Annual meetings  Several round table discussions with auto industry

• SCOH  Several presentations, auto industry, ELT chair, staff

• Traffic Engineering  Joint briefings with FHWA

• Transport  Joint briefings with JPO

14

History with SSOM & other AASHTO Committees • Communications  AASHTO Communications staff  Seeking to mobilize all 50 states communication directors

• Administration  Connection with NHTSA legal staff on states rules that may apply to the NHTSA rulings

• NACE Transport Committee • Cooperative Transportation Pooled Fund 15

Where are we today? • NHTSA decision clarified and moving toward clear statement on safety value • Advanced state of development & emerging timelines for implementation    

AASHTO Footprint being completed FHWA Implementation Guidance 2015 JPO pilot Sites (2 to 5?) in 2015 Auto industry  Substantial technology available on vehicles  connected consumers

• Penn DOT - strategic directions for agency fall 2013 • Florida – automated vehicle workshop fall 2013 • ARUP – impacts of automated vehicle on design 2014 16

AASHTO Subcommittee on System Operations Management (SSOM) Annual Meeting May 5-9, 2014 Nashville, Tennessee

VII Consortium Ed Thai VII CONSORTIUM 1

VII Consortium (VIIC) Industry consortium (Michigan 501 (c) (06) non-profit) consisting of ten light-duty vehicle manufacturers

VII CONSORTIUM 2

VIIC focus within the Connected Vehicle Initiative The Connected Vehicle initiative encompasses a wide range of evolving technologies developed by many government, industry, and academic partners. The VIIC is primarily focused on deployment of cooperative safety and mobility applications based on 5.9 GHz DSRC

ITS Connected vehicle 5.9 GHz DSRC

Safety and mobility applications

VII CONSORTIUM 3

Sustainable Transportation The Connected Vehicle communication system can become a cornerstone for future transportation sustainability. It is more than a safety system or an environmental technology, it is a suite of V2V and V2I applications that: Provide enhanced active safety Leverage existing infrastructure for greater mobility and productivity Improved fuel economy and reduce greenhouse gases VII CONSORTIUM 4

Connectivity is Key “The Network”

E-payment

Opportunity for Innovation

 Real Time Network Data

Safety Messages

Signal Phase and Timing

Situation Relevant Information

Probe Data

Instrumented Roadside VII CONSORTIUM 5

General DSRC Requirements Required for Deployment: Different Manufacturers

Same Frequency: 5.9 GHz DSRC (IEEE 1609.4)

– Communicating on the Same Frequency  Where do we go to talk – Using the Same Language  We understand each other  Data in messages meets same minimum requirements

Same Language (IEEE 802.11) WAVE Short Message (IEEE 1609.3) Basic Safety Message (SAE J2735) Basic Vehicle State (Veh. ID, Seq. #, time, position, motion, control, veh. size ) Mandatory in Basic Safety message Vehicle Safety Extension

- With Security  We trust what we say to each other - Managing Channel Loading  We vary message frequency and power together

• • • •

Event Flags Path History Path Prediction RTCM Corrections

Required for V-V safety applications Other optional safety-related data

Security (IEEE 1609.2)

VII CONSORTIUM 6

MODEL DEPLOYMENT SITE – ANN ARBOR, MI Key Site Elements:  75 miles of instrumented roadway - 27 roadside units  ~3000 vehicles -Cars, trucks, buses - Integrated, aftermarket, and retrofit 1 year of data collection, now extended to 18 months

VII CONSORTIUM 7

Mobility: $78 billion cost of urban congestion USDOT data shows traffic congestion is a $78 billion annual drain on the U.S. economy… – 4.2 billion lost hours – 2.9 billion gallons of wasted fuel = 58 fully loaded supertankers. Preventing crashes reduces the most common source of congestion Basic safety message monitoring by infrastructure allows optimization of traffic flow DSRC driver information minimizes local impact of traffic disruptions Vehicle communication with local infrastructure enables more effective traffic management algorithms to be implemented – more throughput from existing roadways

VII CONSORTIUM 8

Mobility Program Real-time Data Capture and Management

Dynamic Mobility Applications Reduce Speed 35 MPH

Transit Signal Priority

Weather Application

Data Environment

Fleet Management/ Dynamic Route Guidance

Truck Data

Transit Data

VII CONSORTIUM 9

DYNAMIC MOBILITY APPLICATIONS PROGRAM DATA ENVIRONMENTS AND APPLICATIONS

VII CONSORTIUM 10

AASHTO – VIIC Coordination AASHTO is conducting a comprehensive “Connected Vehicle Field Infrastructure Footprint Analysis” Applications Analysis Deployment Concepts Timelines and Cost Estimations

VIIC members have reviewed these documents and offered automaker comments and input as appropriate

FHWA V2I Deployment Guidance is expected to be completed in 2015 VII CONSORTIUM 11

Another Key Area for AASHTO-VIIC Coordination - Security TRUST

TRUST

Messages from other Vehicles and the Infrastructure must be trusted

• Autonomous vehicle safety applications depend upon sensor data from within the same vehicle • Cooperative safety and mobility applications depend upon data from other vehicles and from the infrastructure • This data must be trusted in order for a cooperative system to work VII CONSORTIUM 12

Security Design Balance

VII CONSORTIUM 13

Security Models to Support Deployment Security Framework comprises three major functional components: • Security Credential Management System (SCMS) • On-board elements • Communication (interaction) between the on-board elements and the SCMS

VII CONSORTIUM 14

SCMS Deployment Model

Key Functions: 1.Device Initialization 2.Certificate Provisioning 3.Misbehavior Detection and Revocation

VII CONSORTIUM 15

SCMS Manager Research The VIIC has a dedicated work group of member company participants to address the following key questions: Legal relationship between SCMS Manager and SCMS elements Is there a preferred organizational structure? Who are the recommended members of the SCMS Manager entity – private, public, both? What are the membership responsibilities? What legal protections will the SCMS need?

VII CONSORTIUM 16

Mission of the SCMS Manager The expected mission is to: – set SCMS organization structure and operators of SCMS elements – establish operational rules and processes – define means for separation of functions – provide certification, audit and enforcement capabilities – establish required funding mechanisms and – provide adequate risk management

VII CONSORTIUM 17

Policy Work within the SCMS Research Internal Governance and Funding of SCMS  Define specific governance demands  Identify funding opportunities appropriate for the SCMS entity

DSRC Device Certification/Authentication  Clarify the role of SCMS in certification  Certification strategy outside of FMVSS (e.g., third party) • Authority to enforce devices outside of FMVSS control • Certification for channels beyond 172 (e.g., channel 174, interference) • Infrastructure safety messages on channel 172 • Ongoing maintenance of functionality

 Data Access/Ownership  Access to and ownership of linkage databases

VII CONSORTIUM 18

Autonomous Vehicles Automated Vehicles

Development

Testing

AV

Connected Vehicles

Development

Testing

V2V V2I

Connected Automation

Automation

Connected Automation

Vehicle V2X

Vehicle Automation Development – Can proceed independently of connectivity to a point – Greatly enhanced with connectivity to other vehicles and infrastructure

Benefits of Connectivity – Increases availability, speed, and reliability of information – Enables coordination of automated traffic streams The full potential benefits of road vehicle automation may be enhanced VII CONSORTIUM through a connected environment 19

Final Thoughts State and local DOT’s

USDOT

Connected Automation

Customer / Constituents

Automakers

Need to Collaborate on a Focused Suite of Applications that Motivate VII CONSORTIUM Stakeholders to Take Action for a Successful Deployment. 20

AASHTO National Connected Vehicle Field Infrastructure Footprint Analysis SSOM May 6, 2014

with financial contribution from:

Background • In 2012 USDOT requested AASHTO to form a team to conduct a national connected vehicle field infrastructure footprint analysis  Consider broad range of CV apps and scenarios  Include safety, mobility and environmental apps  Include light vehicles, transit, commercial vehicle and pedestrian apps  Include urban, rural, freeway, arterial, and freight/ intermodal facilities, and land border crossings

with financial contribution from:

2

Footprint Development Process • Develop a Tech Memo to initiate engagement with State and local agencies (Task 3) • Assess the range of applications and their enabling requirements such as data & communication needs (Task 4) • Develop design concepts (Task 5) • Develop deployment scenarios, a preliminary national footprint, and cost estimates (Task 6)

with financial contribution from:

3

Tech Memo “This is a major undertaking for AASHTO, Transport Canada, and the United States as we prepare for a safer and more productive transportation environment.” Mike Lewis, AASHTO President and Director, Rhode Island DOT “We are proud to invest in innovation and new opportunities to improve transportation safety and efficiency. By working together now we can lay the groundwork to align standards and regulations in North America and prevent barriers to cross-border travel and trade.” Susan Spencer, Director of ITS Programs, Transport Canada

with financial contribution from:

4

Footprint Applications Assessment Application Packages • V2I Safety • Mobility/Environment • Road Weather • Smart Roadside • Int. Border Crossings • Fee Payments • Agency Operations

Application Requirements • Data from Vehicles and Infrastructure  Basic Safety Message  Probe Message  Signal Phase and Timing

• Communication Modes  DSRC, Cellular

• Backhaul Options • Back Office

with financial contribution from:

5

Design Concepts • Selected to represent settings into which an agency might want to deploy CV applications • Documented with conceptual plan sheets and supporting descriptions • Include variations and alternatives to enable broader range of applications • Identify example applications appropriate to that setting and concept with financial contribution from:

6

Urban Intersection Example

with financial contribution from:

7

Ten Sample Design Concepts • • • • •

Urban Intersection Urban Highway Urban Corridor Rural Roadway International Border Crossings

• • • • •

 Canada & Mexico

with financial contribution from:

8

Smart Roadside DOT Operations Fee Payments Freight Facility Cellular Concept

Deployment Scenarios • Discussions with selected agencies using application assessment and design concepts • Ask how they would proceed with implementation and acquire funding • Results were used to describe 1. National launch footprint for infrastructure ~ 2020? 2. A typical agency deployment process 3. A national deployment progression

with financial contribution from:

9

Infrastructure Timelines 2014

2015

2016

Plan

2017

Pilot

2018

2019

Evaluate

Pilot

Evaluate

Deploy

DSRC on 20% of signals

1st CV-enabled ATM

Plan

Pilot

Evaluate

2035

2040

DSRC on up to 80% of signals

Expand

Mobility

Freight Mobility

2030 Expand

DSRC for Other Local Safety Apps

1st DSRC on signals

Plan

2025

Deploy

Safety NHTSA Light V2V Decision

2020

Deploy

Traveler Info on 90+% of Roadways

System-wide Active Traffic Mgmt

Expand

NHTSA Heavy V2V Decision

Border Crossings Agency Operations

Plan

Plan

Pilot

Evaluate

Pilot

Deploy

Evaluate

Expand

MN/NV/MI Integrated Mobile Observations

with financial contribution from:

10

Deploy

Expand

Deployment Progression

with financial contribution from:

11

Potential Intersection Sites • Signalized intersections (311,000 total) Deployment Fraction 20%

50%

80%

Objective Deploy only at highest volume intersections (50% of intersection crashes) Deploy at half of all intersections (80% of intersection crashes) Deploy at all intersections where warranted

with financial contribution from:

12

Number of Deployment Sites 62,200

155,500

248,800

Potential Non-Intersection Sites • ITS Deployment Sites  Exclude some detection sites  Allow for some duplicates  ~25,000 sites with financial contribution from:

Data Collection Equipment

Loop Stations

Reported Number of Deployments 12,465

Radar Stations

7,184

Video Image Detection Stations Freeway CCTV Cameras

2,261 10,481

Toll Tag Readers (for data collection)

707

Dynamic Message Signs

4,038

Ramp Meters

933

Toll Plazas

845

Toll Collection Lanes with ETC

4,669

NORPASS Weigh Station Locations (US)

41

PrePass

310

Environmental Sensor Stations (ESS)

2151

13Total

46,085

Infrastructure Cost Estimation • Deployment Costs

• Other Costs

 DSRC RSUs  Backhaul  Signal Controller Replacement  Total Deployment

 Operations and Maintenance  Backend Systems  OBU on Fleets  Cellular Data Costs  Probe Data from Third Parties

with financial contribution from:

14

DSRC Deployment Experience • DSRC RSU deployment costs were surveyed from existing and planned deployments Deployment Site

Michigan

Arizona

Virginia

TFHRC

Average

$9,850.00

$4,200

$8,400

$6,100

$7,450

$4,000

$3,000

$3,800

$3,400

$3,550

Design and Planning

$7,300

$5,900

$6,900

$6,400

$6,600

Total Direct Connected Vehicle Costs

$21,150

$13,100

$19,100

$15,900

$17,600

Connected Vehicle DSRC Hardware Installation Labor

Compared to $150K to upgrade an intersection, DSRC deployment would add 10-15%

with financial contribution from:

15

Estimated DSRC Unit Deployment Cost Element

Cost (2013$)

(DSRC) Equipment and Site Deployment

$17,600

Backhaul Upgrades and Deployment (Weighted Average)

$30,800

Traffic Signal Controller Upgrades

$3,200

Total Potential Site/Unit Cost

$51,600

with financial contribution from:

16

Estimated DSRC Unit O&M Costs Cost Element

Per Device Cost per Year (2013$)

Power

$100

Traditional Maintenance

$500

License/Maintenance Agreements

$200

SCMS Certificate License

$50

Annualized Replacement Cost (every five to ten years)

$1100 - $2200

Total

$1950 - $3050

with financial contribution from:

17

What’s Next for the Footprint? • Outreach  May 6th AASHTO SSOM  May 22nd Open T3 webinar  May 29th States & OEM webinar

• Complete Report  Publish Final Report by June 30  Documents posted at AASHTO & USDOT with financial contribution from:

18

What we have Achieved • Better understanding for states on what DSRC infrastructure is needed and how much it may cost • Realization that we need more clarification on:     

Cellular Role Application development & management Understanding Data needs & availability Backhaul Options beyond traditional view State leaders willing to take the next move  USDOT Pilots should help considerably  Need State group for peer exchanges when deployment begins

 Continued Collaboration with OEM’s & USDOT    

VIIC – Security, data availability, etc. CAMP – Applications, DSRC vs Cellular, etc. FHWA operations – Implementation Guidance JPO Pilot Effort 2015

with financial contribution from:

19

Website for Documents • Footprint Documents for Tasks 3, 4 & 5 are on the AASHTO SSOM Web Site: http://ssom.transportation.org/Pages/Connected-Vehicles.aspx

• JPO web site for Final Report (after 6/30) http://www.its.dot.gov/connected_vehicle/connected_vehicle.htm

• [email protected] • [email protected] • [email protected] with financial contribution from:

20

ITE Engagement in Connected and Autonomous Vehicles AASHTO Subcommittee on System Management and Operations May, 6, 2014

Douglas E. Noble, P.E., PTOE Senior Director, Management and Operations

ITE Engagement • Connected Vehicle Task Force • Management and Operations/ITS Council Ad hoc Committee on Connected Vehicle/Autonomous Vehicle Outreach

Connected Vehicle Task Force • Role: provides comment, review and input to major areas of the connected vehicle program. Updates to keep community up to date • NHTSA decision on V2V • FHWA 2015 V2I deployment guidance development • Updates on DSRC, V2V and AASHTO Footprint analysis

• Representation: • Public and Private sectors, co-chair from each

• Relationships • AASHTO, ITS America, NACE, TRB, SAE, IEEE

• Supported thru ITS-JPO

Connected Vehicle Task Force • 2014 Focus Areas • Cyber and infrastructure security • Applications for C.V. common interface environment • Roadside unit specifications and standards

ITE CV/AV Outreach ITE hosted conference sessions: • Plenary address by Andrew Chatham, Principal Software Engineer, Google Self-Driving Cars (March 2014) • Connected vehicle and infrastructure cybersecurity (March 2014) • Discussion forum on infrastructure cybersecurity (August 2014) • Connected vehicle session in pecha kucha format --- 20 slides show for 20 seconds each

ITE CV/AV Outreach ITE developed the following presentation to: • Increase awareness • Lead in to discussion panels at ITE District and Section Meetings • Outreach to wider transportation and decision-maker community

Contact • Douglas E. Noble, P.E., PTOE • [email protected] • (202) 785-0060, x148

ITS Standards Program

AASHTO Subcommittee on System Management and Operations May, 6, 2014

Douglas E. Noble, P.E., PTOE Senior Director, Management and Operations

Program Elements • ITS Standards: • Development • ITS Standards Maintenance • Professional Capacity Building • Intelligent Transportation Systems ePrimer

• ITE is a Standards Development Organization in partnership with A ASHTO and NEMA

ITS Standards Development • Advanced Traffic Controller Working Group • ATC 5202 Model 2070 Controller Standard v03 (Published) • ATC Standard 5.2b (Published, at 5-Year Review) • ATC 5201 ATC Standard v06.xx (Comment Disposition)

• ITS Cabinet Working Group • ITS Cabinet Standard v01.02.15 (Published, Superseded) • ITS Cabinet Standard v01.02.17b (Published) • ITS Cabinet Standard v2.0 (Requirements complete, in Design)

ITS Standards Development • ATC Application Programming Interface Working Group • API for ATC Version 1 (Published, Superseded) • API for ATC Version 2 (Published) • API Reference Implementation (Requirements complete, in Design)

• Strategic 2-Year Planning: • Connected Vehicle Roadside Equipment • Network Security

ITS Standards Development • NTCIP 1202 v3 Data messaging protocol for adaptive control (Ex. SPaT data)

• NTCIP 1204 v4.03 Environmental Sensor Stations and linkage to Clarus

• ATC 5401 Reference project to test software for compliance with ATC API

• Available at: www.ite.org/standards

ITS Standards Maintenance • Maintains published ATC, TMDD, and NTCIP standards • Driven by any one or combination of the needs, as necessary, to keep standards current with • • • •

Lessons learned from deployment On-going technology upgrades Maintaining support for existing users Interoperability with other standards and their interfaces.

ITS Standards Professional Capacity Building Program ITE has developed 37 course modules for ITS JPO in the Year 1 and 2 of the program • Both Systems Engineering and Non-Systems Engineering curriculum in path in initial courses • Available here: www.pcb.its.dot.gov/stds_training.aspx

ITS Standards Professional Capacity Building Program

Year 3 Course Development Sequence#

Course Name

C201

Introduction to the Simple Network Management Protocol (SNMP) and its Applications in the Field Devices Based on NTCIP Standards (L)

C202

Introduction to the Application Level Protocols for Center-to-Center Communication System Interface Implementation (NTCIP 2306 XML) (L)

I 231

Vehicle-to-Infrastructure (V2I) ITS Standards for Project Managers

I241

Vehicle-to-Vehicle (V2V) ITS Standards for Project Managers

T203a

How to Develop Test Cases for ITS Standards Test Plan

T203b

How to Develop Test Cases for ITS Standards Test Plan

T204a

How to Develop Test Procedures for ITS Standards Test Plan

T204b

How to Develop Test Procedures for ITS Standards Test Plan

A307a

Understanding User Needs for ATC Version 6 Controller (Non-SEP Path)

A307b

Specifying Requirements for ATC Version 6 Controller (Non-SEP Path)

A334a

Understanding User Needs for 1207 RM Std v2 (A334a)

A334b

Specifying Requirements for 1207 RM Std (A334b)

T334

Applying your test plan to the 1207 RM Std v2

T312

Applying your test plan to the 1209 TSS Std v2

A315b

Specifying Requirements for Actuated Traffic Signal Controllers (ASC) Based on NTCIP 1202 Standard (LO 3 & 6), B1

ITS Standards Professional Capacity Building Program • Transit Course Development • • • • • • • • • •

Introduction to Transit ITS Standards TCIP Part 1 TCIP Part 2 Traveler Information, Part 1 Traveler Information, Part 2 Transit Management, Part 1 Transit Management, Part 2 Electronic Payment Systems Transit Signal Priority (Arterial Management) Connected Vehicle/Emerging Technologies

Intelligent Transportation Systems ePrimer ITE with ITS America developed the ePrimer for ITS JPO: • http://www.pcb.its.dot.gov/ePrimer.aspx

Webinars • May 13 - ITS ePrimer Module 7: Public Transportation • May 15 - ITS ePrimer Module 14: ITS Emerging Opportunities and Challenges

Contact Siva Narla Transportation Technology Senior Director [email protected] (202) 785-0060, x119

AASHTO STSMO Conference Connected Technologies for Improved Systems Transportation Management & Operations Steven J. Cook, P.E. Engineer of Systems Operations & Maintenance Michigan Department of Transportation

• • • • • •

Connected Vehicle Activities in Michigan MDOT Data Use Analysis and Processing (DUAP) Project Safety Pilot and Mobility Transformation Center - UMTRI FHWA/MDOT Integrated Mobile Observations (IMO)Weather Response Traffic Management (WxTINFO) Connected Technologies in Michigan 2014 ITS World Congress – Detroit (September 7-11)

MDOT Connected Vehicle Activities Data Use • DUAP - Phase 1 & 2 Data Collection

• Critical Highway Infrastructure Monitoring Project • Partner OEM Data • Vehicle Based Info & Data Acquisition System (VIDAS) • Slippery Roads Detection Project • Integrated Mobile Observations 2.0 • AVL/GPS/MDSS MDOT Fleet Project • ACC/IRI/PASER Study • USDOT Safety Pilot Model Deployment (UMTRI) Data Dissemination • I-94 Truck Parking Info and Mgmt System • Multipath SPaT Project Pooled Fund/Research

• AASHTO CV Deployment Coalition • CTS Pooled Fund Study • CAR CV Research Projects & Studies • CV Driving Simulator

Michigan Connected Vehicle Test Beds OEM Tech Center (Auburn Hills) Telegraph Rd. Corridor - SPaT POC Test Bed (Farmington Hills) Rock Financial Showcase (Novi) CVPC Intersection (Southfield) Michigan International Speedway (Brooklyn) USDOT Development & Test Environment (Novi) USDOT Safety Pilot (Ann Arbor) City of Detroit CV Test Bed I-94 Truck Parking Info and Management System

MDOT Data, Use, Analysis & Processing (DUAP) Project Performance measures

MDOT Fleet AVL/GPS

Here

OEM Fleet Data

MDOT ITS Data

RITIS

Cut River Bridge

VIDAS

DUAP

USDOT Safety Pilot

RWIS Data

Truck Parking Info

MDOT Systems (TMS) ACC IRI PASER

AV Data UAV

IMO 2.0

USDOT Safety Pilot Data

UNIVERSITY OF MICHIGAN MOBILITY TRANSFORMATION CENTER

A CONNECTED FUTURE ★★ ★ ★

★  ✪ ★

 ★

★

★ ★ ★ 

★ ★ 

★

✪



FHWA/MDOT Integrated Mobile Observations (IMO) Architecture Data Users: University of Michigan, National Center for Atmospheric Research, MDOT DUAP/TOC – Motorist Advisory Warnings & EMDSS

MDOT Vehicles – FHWA/MDOT Data Collection Vehicle Positioning GPS

Smartphone 3-axis accelerometer

Cell Tower (4G)

fiber

Cellular Service Providers Network Operations Center

UofM Server

Photo Image

MDOT/NCAR

Surface Temp & Atmospheric Conditions

20 WMTs with phones & 10 with Surface Monitor Device

40 Ford vehicles with phones & OBD key & 10 with Surface Monitor Device

Winter Maintenance Operations EMDSS

Road Surface Roughness and Distress

Demonstrations

Traveler Information Systems

IMO/WxTINFO DataProbe Data Sources SIGNAL Position speed direction altitude distance veh dynamics roughness photo VIN RPM Throttle Position ABS Trac Control ambient temp barometer pavement temp humidity dew point

Number of vehicles:

Droid

OBDKey

Surface Patrol

X X X X X X X X X X X X X X X X X X

(60)

(40)

(20)

IMO Data Source

(300,000 miles of data in 9 months)

11

7:30 AM, Thursday, February 20, 2014

8:15 AM

Weather Response Traffic Information (WxTINFO) Data Collection Roadside Dynamic Message Sign

Motorist Advisory Warnings (MAW)

MDOT DUAP & NCAR VDT

FHWA/MDOT WxTINFO Data Collection System using IMO Vehicle Data

Potential Motorist Advisory Warning Messaging •

Travel Times

•

Visibility reduced next 5 miles

•

•

•

Maintenance trucks next 10 miles – Drive with care

•

High Wind Warning

•

Road closed ahead – use alternate route

Road icy next 3 miles

Heavy rain reduced visibility next 2 miles

Connected Technologies Existing and Potential Interactions

MDOT RITIS

MDOT RWIS

Maintenance Decision Support System MDOT Data Use Analysis Processing (DUAP)

DTMB/ MDOT TOC/ATMS

MDOT TMS

FHWA/MDOT Truck Parking Information Mgt. System

SYSTEMS DATA

MDOT

Vehicle-based Information Data Acquisition System

MDOT ACC/IRI/ PASER

USDOT/MDOT Signal Phase and Timing

Autonomous Vehicle Data

MDOT Cut River Bridge

USDOT Safety Pilot, Ann Arbor, MI MDOT Unmanned Aerial Vehicles

MDOT Fleet AVL/GPS Legend Existing Unidirectional Existing Bidirectional Potential Unidirectional Potential Bidirectional

FHWA/MDOT Integrated Mobile Observations

Automakers Fleet Data

MDOT Probe Data Provider

2014 ITS World Congress - Detroit Cobo Center

2014 ITS World Congress Cobo Center – World Congress Exhibits

GM Renaissance Center and On-Star Head Quarters

Belle Isle

Thank You

Cooperative Transportation Systems Pooled Fund Study and Virginia Connected Vehicle Test Bed

Dean Gustafson, P.E., PTOE Virginia Department of Transportation May 6, 2014

COOPERATIVE TRANSPORTATION SYSTEMS POOLED FUND STUDY

2

Cooperative Transportation Systems Pooled Fund Study •

The Pooled Fund Study (PFS) is a partnership of transportation agencies who have established a program to facilitate the development and evaluation of Connected Vehicle applications

•

The program will prepare state and local transportation agencies for the deployment of Connected Vehicle technologies

•

The program will result in the following outcomes: – –

Development and demonstration of Connected Vehicle-enabled system operations algorithms, tools and applications Preparation for field demonstration tests

3

Current PFS Membership Core/Voting Members •

VDOT is lead agency with administrative support from UVA

•

Twelve Core Members: Virginia, California, Florida, Michigan, Minnesota, New Jersey, New York, Pennsylvania, Texas, Utah, Washington, Wisconsin, Maricopa County and FHWA

Associate Members •

Palm Beach Co, FL; Oakland Co, MI; MTC (Bay Area), Transport Canada, Rijkswaterstaat and North Texas Toll Authority

Liaisons •

NCHRP/SHRP 2; AASHTO (strategic and deployment plans)

4

Cooperative Transportation Systems Pooled Fund Study •

The PFS was initiated as a phased program

•

Phase I (July 2009 – July 2012) – Focused on research to educate and prepare agencies for the deployment of transportation systems

•

Phase II (July 2012 – December 2014) – Focused on developing and field testing connected vehicle applications to determine benefits and lessons learned for large scale deployments

•

Phase III (December 2014 – December 2016) – Will focus research and development of connected vehicle applications, to include autonomous vehicles

•

Dynamic Mobility Application (October 2011 – April 2015) – Focused on developing and field testing a multi-modal intelligent signal system in cooperation with USDOT

5

PFS Phase I Program July 2009 – August 2012 Round 1 Projects •

Connected Vehicle Traffic Signal Control Algorithm – Developed and evaluated a new traffic signal control algorithm using connected vehicle data

•

Pavement Maintenance Support Algorithm – Determined the benefits of using CV probe data to develop IRI estimates and detect and map potholes

•

Evaluation of Signal Phase and Timing Data – Developed CONOPS and benefits assessment for use cases of SPaT data

Round 2 Projects •

Connected Vehicle Certification Program –Educated PFS members on potential issues related to a future connected vehicle certification program

•

Aftermarket On-Board Equipment – Identified requirements for a MultiCommunications enabled OBE and provided recommendations for rapid introduction of equipment 6

PFS Phase II Program September 2012 – December 2014 Round 3 Projects •

Traffic Management Centers in a Connected Vehicle Environment – Investigated how the Connected Vehicle environment will change the TMC of the future, both technically and the role of TMC operators/managers (Complete)

•

5.9GHz DSRC Vehicle Based Road and Weather Condition Application – Developing and testing a 5.9GHz DSRC application that is used on fleet vehicles for road and weather condition data. This data will supplement the Clarus system (To be completed December 2014)

Round 4 Projects – currently in selection process

7

Dynamic Mobility Application Multi-Modal Intelligent Traffic Signal System October 2011 – April 2015 •

Objective: Develop and test a system that integrates connected vehicle information and devices into a more effective and safer traffic signal control system for multiple modes of travelers

•

Funded in part by USDOT to support its Dynamic Mobility Application Program

•

Phase I – Develop the CONOPS, systems requirements and system design (Complete)

•

Phase II – Demonstrate and field test the system in two locations – –

Maricopa County, Arizona El Camino Real, California

8

Multi-Modal Intelligent Traffic Signal System Scenarios for Deployment Operational Scenarios/Use Cases 11

Include

11.0.1

Network Section 1

X

11.0.2

Network Section 2

X

11.1

Defer

AZ

CA

MMITSS Operational Scenario

X X

Intelligent Traffic Signal System Scenarios

11.1.1

Basic Signal Actuation

X

X

X

11.1.2

Coordinated Section of Signals

X

X

X

11.1.3

Congestion Control

11.1.4

Dilemma Zone Protection

X

X

X

X

X

X

X

X

X

X

11.2 11.2.1

TSP Operational Scenarios Basic TSP Scenario and Variations Nearside Bus Stop

X

Transit Signal Priority for Left Turn with Protected Signal

X

11.2.2

Operational Scenarios for Rail Crossings in Urban Areas

11.2.3

Extended TSP Scenario 11.3

X

X X

Pedestrian Mobility Operational Scenarios

11.3.1

Unequipped Non-Motorized Traveler

-

11.3.2

Equipped Non-Motorized Traveler

X

11.3.3

Equipped Bicyclist

11.3.4

Inclement Weather Accommodations for Non-Motorized Travelers 11.4

X X

Freight Signal Priority Operational Scenarios

11.4.1

Basic Freight Signal Priority

X

X

X

11.4.2

Coordinated Freight Signal Priority along a Truck Arterial

X

X

X

11.5

Emergency Vehicle Priority

11.5.1

Single Intersection Priority/Preemptions

11.5.2

Route Based Intersection Priority/Preemption

X

X X

9

AZ – Anthem Test bed in Maricopa County; CA – Test bed in El Camino Real

VIRGINIA CONNECTED VEHICLE TEST BED

10

Virginia Connected Vehicle Test Bed •

With VDOT’s support, Virginia Tech, University of Virginia, and Morgan State University have developed a Tier 1 University Transportation Center (UTC) –

VDOT chairs the Advisory Board

•

Center will focus on research, education and workforce development for the Connected Vehicle/Infrastructure (CVI) environment

•

CVI-UTC will use current facilities, equipment and technical support to develop and test CVI applications and technology

•

Test beds in Fairfax and Blacksburg (Smart Road at VTTI) are almost complete – – – –

Smart Road Test Bed will serve as a test site prior to implementation on the Fairfax Test Bed 7 Road Side Units (RSU/RSE) are on Smart Road, including one at a signal 41 RSUs along freeways (I-66, I-495) and arterials (US 50/29 and Gallows Road) in Fairfax County 2 portable RSE trailers

11

Road Side Infrastructure – Northern Virginia

12

Road Side Infrastructure – Smart Road

13

Network Architecture NEW RSE

ENHANCED COX INTERNET SERVICE

ENCRYPT TUNNEL

REAL-TIME & LOGGED CV DATA

CISCO ROUTER

REAL-TIME & LOGGED CV DATA

2070 CONTROLLER

SIGNAL CONTROL DATA

CISCO ROUTER FIBER SWITCH

INTERNET

EXISTING INTERSECTIONS

SIGNAL CONTROL DATA

REAL-TIME & LOGGED CV DATA ENCRYPT TUNNEL

VDOT TRAFFIC SERVER

VDOT – MANASSAS TFO CV APPLICATION, SECURITY & DATA SERVERS

ENHANCED COX INTERNET SERVICE

NEW FIBER SWITCH

VDOT PSTOC REAL-TIME & LOGGED CV DATA

CCTV IMAGERY

NEW RSE

POE SWITCH

ENCRYPT TUNNEL

EXISTING SWITCH

EXISTING ENCODER

EXISTING CCTV CAMERA SITES VTTI BLACKSBURG

14

VA Testbed – Road Side Equipment • Savari StreetWAVE is a fixed wireless gateway that will be mounted on CCTV poles along the freeway and traffic signals along the arterials

TYPICAL INSTALL ARTERIAL 15

On Board Equipment

• • • • Mini Data Acquisition System

• •

10 instrumented cars • • •

•

4 sedans (GM brand) 2 SUVs (GM brand) 4 motorcycles (donated by motorcycle safety foundation)

2 instrumented heavy vehicles • •

Semi-truck Motorcoach

200 MiniDAS Aftermarket Safety Devices are being developed by VTTI System includes GPS, Microphone, Inertial Measurement Sensors System offers Road Scout (Lane Detection), MASK (Head Tracker) and epoch detection Data is captured over the vehicle network (CAN) Parametric Data collected by MiniDAS: • • • • • • •

Accel X,Y,Z Gyro X,Y,Z GPS Speed and Position Network speed Turn signal Brake Accelerator position

16

UTC Connected Vehicle Research Projects •

19 projects have been funded that focus on freeway and arterial applications: – – – – – – – – – – – –

– CV Freeway Speed Harmonization Systems Adaptive Stop/Yield – Reducing School Bus Conflicts through CVI Adaptive Lighting – NextGen Transit Signal Priority with CVI Intersection Management Using – Smartphone DMS Application Speed Adaptation – Willingness to Pay and User Acceptance Eco-Speed Control Awareness System for Roadway Workers Emergency V2V Communication Freeway Merge Management Infrastructure Safety Assessment Safety and Congestion Issues Related to Public Transportation Connected Motorcycle Crash Warning Connected Motorcycle System Performance Smartphone App Reducing Motorcycle and Bicycle Crashes

17

Connected Vehicle Test Bed Expansion

•

The Fairfax Test Bed will expand to align with the project limits of the Active Traffic Management (ATM) Project on I-66, and will include: – –

•

25 RSEs to expand the Northern Virginia Test Bed on I-66 between Vienna and Gainesville 50 MobiWAVE Savari On-board Units for VDOT Fleet Vehicles

On-board equipment can support the following Safety Applications: – – – – – –

Emergency Brake Light Warning Forward Collision Warning Intersection Movement Assist Blind Spot and Lane Change Warning Do not pass Warning Control Loss Warning

18

Additional Information •

Cooperative Transportation Systems Pooled Fund Study http://cts.virginia.edu/CTSPFS_1.html Melissa Lance – [email protected]

•

CVI UTC http://www.cvi-utc.org/ Cathy McGhee – [email protected]

19