Connected Fleet Challenge Webinar Series Webinar #1 2:00 3:30 PM - PowerPoint PPT Presentation

Connected Fleet Challenge Webinar Series Webinar #1 2:00 – 3:30 PM (Eastern) | October 3, 2019

Webinar Logistics • All lines are muted • Webinar will be recorded • Submit questions and comments in chat or Q&A section of webinar window • Questions will be answered at webinar conclusion 2

Agenda • Welcome and Introduction – Blaine Leonard, Utah DOT • SPaT Challenge Background and Update – Blaine Leonard, Utah DOT • Connected Fleet Challenge Background – Mark Kopko, PennDOT • Focus on Deployment  PennDOT – Mark Kopko, PennDOT  THEA CV Pilot – Steve Novosad, HNTB  NHDOT SPaT Deployment – Curtis Thompson, Sebago Technics • Q&A 3

SPaT Challenge The basis of the SPaT Challenge is to broadcast:  SPaT Message  MAP Message Using DSRC technologies. Subsequent efforts could include:  Broadcast a Security Certificate (SCMS)  Broadcast a GPS Correction Message (RTCM)  Install OBUs in vehicles (Fleet Challenge)  Implement V2I Applications 4

SPaT Challenge To challenge state and local public sector transportation infrastructure owners and operators (IOOs) to deploy DSRC infrastructure with SPaT (and MAP) broadcasts in at least one corridor or network (approximately 20 signalized intersections) in each state by January 2020 20 intersections in 50 states by 2020! 3 years of progress: 47 Locations 27 States 670 RSUs Operating 3325 RSUs Planned 9200 Vehicles Planned 5

SPaT Challenge Website https://transportationops.org/spatchallenge 6

SPaT Challenge Webinars https://transportationops.org/spatchallenge/webinarseries • Ten webinars conducted  March 2018-January 2019  Recordings available in full or by topic on SPaT Challenge website • Information for all Connected Fleet Challenge webinars, including registration and recordings will also be available on this website 7

SPaT Challenge Webinars https://transportationops.org/spatchallenge/webinarseries 1. Initial SPaT Activities 2. Design Considerations – Part 1 Helping SPaT 3. Design Considerations – Part 2 Challenge Sites to Get 4. J2735 MAP Creator Tool Demo Started 5. Design Considerations – Part 3 6. SPaT Challenge Deployment & Validation 7. SPaT Challenge Operational Deployments Examples of 8. Beyond the SPaT Challenge applications and updates on 9. SPaT Challenge Operational Deployments SPaT 10. Operational SPaT Deployments Deployments 8

SPaT Challenge Website https://transportationops.org/spatchallenge 9

SPaT Challenge Resource Page https://transportationops.org/spatchallenge/resources 10

SPaT and Fleet Challenge Request for Information • Sample documents along the entire V diagram for deploying agencies to use  Including procurement or bid documents, cost information, lessons learned, general technical resources • Document SPaT Challenge deployment information for map on website  New planned or operational sites  Update status for sites already on map 11

Upcoming Connected Fleet Challenge Webinars • Webinar #2: November 21, 2019 at 2p ET  Register and more information at: https://transportationops.org/event/webinar-series-connected- fleet-challenge-webinar-2 • Webinar #3: January 9, 2020 at 2p ET  Register and more information at: https://transportationops.org/event/webinar-series-connected- fleet-challenge-webinar-3 • Topics will include plans and updates from SPaT and Connected Fleet Deployments  Including applications, benefits, available resources 12

Q&A Submit questions and comments in chat or Q&A section of webinar window

New Hampshire’s Response to AASHTO’s SPaT Challenge Curtis Thompson P.E., Sebago Technics Inc. cthompson@sebagotechnics.com

Our Project Partners • NHDOT • FHWA • AASHTO • City of Dover, New Hampshire • McCain, Vista CA • DENSO International America, Vista CA • UNH Connectivity Research Center • Electric Light Company (Electrical Contractor)

Research Objectives • Satisfy the Goals of the SPaT Challenge • Compare two communication paths for V2I connectivity • Test the FHWA V2I Hub Software • Contribute field‐tested research addressing: – Is DSRC the optimum solution for V2I? – Should “mobility” and “safety” information use different paths?

DSRC Path V2I Hub DSRC RSU DSRC OBU Controller With Display J2735 SPaT J2735 SPaT NTCIP 1202 SPaT Data J2735 MAP J2735 MAP UPER MAP Data

Cellular Network Communications Path Internet Controller V2I Hub Traffic Server LTE Radio With Display DB SPaT J2735 SPaT DB SPaT NTCIP 1202 SPaT Data DB MAP J2735 MAP DB MAP UPER MAP Data

UNH CRC Lab Testing

Lab Testing Results • Average File Size – SPaT: 450 Bytes – MAP: 700 Bytes • Average Latency in the Lab – DSRC: 70ms or 0.07 seconds – LTE: 150ms or 0.15 seconds

Field Testing • Goals – Validate RSU deployment – Determine field range of RSU – Determine LTE network speed with field conditions – Calibration of MAP file

DSRC Field Testing Results • Average Range of Latency in the Field – 5ms or 0.005 seconds to 20ms or 0.020 seconds (Lab results averaged 70ms or 0.070 seconds) • Maximum Range Measured in the Field – Measured roughly 800 feet

LTE Field Testing Results • Average Range of Latency in the Field – 128ms or 0.128 seconds to 142ms or 0.142 seconds (Lab results averaged 150ms or 0.150 seconds)

Conclusions and Observations • Interoperability challenges • Equipment Limitations • 5.9 Ghz FCC Licensing • MAP File Creation and Operations • Final Report Submitted ‐ January 2019 • The DSRC radios remain in the field for future use

The Connected Fleet Challenge Mark Kopko, Pennsylvania DOT

THE CONNECTED FLEET CHALLENGE Encourages IOOs that have responded to the SPaT Challenge to equip at least one light-duty vehicle and at least one heavy-duty vehicle with a 5.9 GHz DSRC On-Board Unit (OBU) by 2021. OBUs should be capable of broadcasting the Basic Safety Message (BSM) to Roadside Units (RSUs) and of receiving SPaT, MAP, and other data messages that are being broadcast by the infrastructure . Industry focus on diversity in the make, model, year of vehicles to learn as many lessons as possible and to share these lessons across the industry. 2

Why is the Connected Fleet Challenge Needed? • Fleet owners need experience procuring, deploying, and operating On-board units (OBUs) to prepare for future deployments • Fleet owners and IOOs would benefit from real- world trials of various applications (e.g. RLVW, Eco Glidepath) • IOOs that have participated in the SPaT Challenge need a mechanism to perform additional verification of their broadcasts 3

Scale of the Connected Fleet Challenge • Public sector fleet owners are generally not ready for wide- scale deployment of OBUs, for several reasons:  There are limited funds available, and a general ‘wait and see’ approach to observing benefits demonstrated in Pilot Site (and other early) deployments  There is limited (not none) experience with operating OBUs in the various vehicle types owned by fleet operators – resulting in uncertainty regarding operating costs, and institutional challenges • There is still a need for an initiative to help fleet operators gain the experience that will position them for future large scale deployments 4

Scale of the Connected Fleet Challenge • Diversification is the goal of the Connected Fleet Challenge  Ideally numerous variations of models and configurations of light duty and heavy-duty vehicles will be equipped in this challenge  But each fleet operator does not need to deploy each of these variations – sharing lessons learned will help build the ‘industry experience’ to include many variations of vehicles  While the SPaT Challenge tracks locations where SPaT broadcasts are developed and displays them on the map, the Connected Fleet Challenge would likely track the variations of maintenance vehicles, buses, delivery vehicles, passenger vehicles, etc. with OBUs equipped, sharing lessons learned from each variation 5

Scale of the Connected Fleet Challenge • Using Transit Buses as an Example:  If 10 transit agencies each equip two of their buses…  This could result in as many as 20 different models or configurations of buses  Through a tracking website/table, the lessons learned, costs, installation experiences of each could be reported and tracked  To the industry, this would represent a substantial percentage of ‘types’ of buses • Additionally, if several school bus fleets participate, this could result in understanding of the institutional/legal steps required to equip school buses with OBUs 6

Target Goals of the Challenge • Fleet operators equip at least 2 of their fleet vehicles, including one heavy duty and one light duty vehicle if their fleet supports it. • Fleet operators collaborate with other fleet operators to achieve as much diversification in vehicles equipped as possible nationwide and to share lessons learned • Fleet operators partner with IOOs that have deployed SPaT/MAP broadcasts to exchange data 7 7