Connected Fleet Challenge Webinar Series

Webinar #1

2:00 – 3:30 PM (Eastern) | October 3, 2019

2

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

3

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

4

SPaT ChallengeThe 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

5

SPaT ChallengeTo 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 Planned9200 Vehicles Planned

6

SPaT Challenge Websitehttps://transportationops.org/spatchallenge

7

SPaT Challenge Webinarshttps://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

8

SPaT Challenge Webinarshttps://transportationops.org/spatchallenge/webinarseries

1. Initial SPaT Activities2. Design Considerations – Part 13. Design Considerations – Part 24. J2735 MAP Creator Tool Demo 5. Design Considerations – Part 36. SPaT Challenge Deployment & Validation7. SPaT Challenge Operational Deployments8. Beyond the SPaT Challenge 9. SPaT Challenge Operational Deployments10. Operational SPaT Deployments

Helping SPaT ChallengeSites to Get Started

Examples of applications and updates on SPaT Deployments

9

SPaT Challenge Websitehttps://transportationops.org/spatchallenge

10

SPaT Challenge Resource Pagehttps://transportationops.org/spatchallenge/resources

11

SPaT and Fleet Challenge Request for Information

• Sample documents along the entire V diagram fordeploying 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

12

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

Q&ASubmit 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  

Controller DSRC RSU DSRC OBU With Display

NTCIP 1202 SPaT Data

UPER MAP Data

V2I Hub

J2735 SPaTJ2735 MAP

J2735 SPaTJ2735 MAP

Cellular Network Communications Path

Controller Traffic Server LTE Radio With Display

V2I Hub

J2735 SPaTJ2735 MAP

Internet

DB SPaTDB MAP

DB SPaTDB MAP

NTCIP 1202 SPaT Data

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

2

THE CONNECTED FLEET CHALLENGEEncourages 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.

3

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

4

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

5

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

6

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

7

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

8

Builds on the SPaT Challenge

• Equipped vehicles can be used to ensure the SPaT and MAP messages are being transmitted properly

• Allow for demonstrations of applications that use the SPaT data such as Red Light Violation Warning and Eco Glidepath

• Equipped vehicles are also challenged to broadcast the Basic Safety Message (BSM), allowing DOTs to understand the receipt and processing of BSM data

9

Benefits Both IOO and OEMs

• Experience installing OBUs • Technicians gain experience • Lessons learned

• Experience sending & receiving BSM

• Can test other CV applications

• Can test RSU/OBU interoperability

• Opens the door for more Day 1 applications

• Increased market penetration of connected vehicles

• Safety benefits for drivers if high risk vehicles are equipped

• Plows, TMAs, Paint Trucks

• Aftermarket devices

• IOO continue to show support

Infrastructure Owner Operators Original Equipment Manufacturers

10

Simplistic Concept – Elevator Speech• You can’t have V2I without the “V”

• More and more pilot deployments popping up Connected fleet is a fraction of that size

• Unlike the SPaT challenge that focused on DOTs and municipalities that own traffic signals, the Connected Fleet Challenge is more than just DOTs

11

Logistics• A partnership between fleet operators and the

IOOs operating SPaT Challenge broadcasts • Fleet operators will:

Equip at least 2 vehicles (1 heavy duty, 1 light duty) with an OBU that receives SPaT/MAP data and broadcasts the BSM

Work with the IOO to test and verify the receipt of SPaT/MAP data

• The IOOs will: Work with the partners to test and verify successful

communication of the SPaT/MAP data Develop ability to receive BSM message

12

Maintenance Fleets

Transit Fleets Emergency Responders

More Than Just DOTs

Taxi Fleets

This challenge will form key partnerships with various fleet operators and help to shape

connected vehicle deployments in the future

13

Connected Fleet Challenge Website

14

Connected Fleet Challenge Website

15

Connected Fleet Challenge Website – map not yet live

16

Connected Fleet Challenge Website

17

Connected Fleet Challenge Request for Information

• Sample documentation for deploying agencies to use Including procurement or bid documents, cost information, lessons

learned, general technical resources

• Document Connected Fleet Challenge deployment information for map on website Planned or operational sites

OBU Installation & TestingOngoing Initiatives and Lessons Learned

Mark C. KopkoDirector, Office of Transformational Technology

Pennsylvania Department of Transportation

717.783. 1903markopko@pa.gov

Objective

• Equipment a PennDOT fleet vehicle with an Onboard Unit (OBU) to communicate with existing and planned connected infrastructure.

Procurement

• Challenges: – Unlike RSUs, US DOT has never developed specifications for OBU.– Not an approved product.

• Approach– Purchase Order through existing IT contract

• Low volume• Low cost (<$2,000 per unit)

– Used specifications from other states and cut sheets• Going Forward

– Develop specification– Standardize procurement

OBU Build Quality Concerns

• We noticed some issues with the build quality of some devices

• Device will not accept SSH login credentials• Once logged in, the enable password will not work to adjust the configuration• Factory reset did not reset the enable password and device reset physical

button was not connected to circuit board• Device has hot glue to keep the antenna connections in place• Device has screws that appear nearly stripped

Initial Test & Lessons Learned

Initial test was a failure – no communications due to different firmware versions

• OBU– Brand new device still required firmware upgrade– Lack of documentation, even from the vendor.

• Interoperability– Even though RSU and OBU were the same, they did not communicate– Other OBUs had issues sending and receiving messages

Internal Policy – Lesson Learned

Thought the technology would be the hard part

• Installation must be handled by DOT staff– Consults have to guide the process

• Broadcasting positioning information– Limits who can use the vehicle

• HMI Flexibility– iPads are locked down

• CAN bus

THEA CV Pilot Lessons Learned and Truck Platooning Steve Novosad HNTB/ THEA CV Pilot System Engineering Lead

2

Agenda• Tampa Hillsborough Expressway Authority

(THEA) Connected Vehicle (CV) Pilot• Challenges• Platooning

3

THEA CV Pilot

4

Challenges

• Participant Recruitment• Manage/Perform Professional Privately

Owned Vehicle Installs• Security• Ensure Solving Real World Problems• Adequate CV Penetration vs Traditional ITS

Detection Devices

5

Challenges• Better Knowledge of AppsOpen SourceIndividual Vendors

• Prep Work Required to Successfully Deploy• Pedestrian Detection• Lightning Strikes• Communication Infrastructure

6

Challenges

• Over the Air Updates• Datalog upload from Onboard Units• Early real-life testing with actual

infrastructure in deployed to verify end-to-end system/application performance

• Distributed Team Across the Country and in Europe and India

7

Truck Platooning• ChallengesRoadway Entry/ExitRoadway Wear/TearBridge WeightsVehicle Cutoffs

• BenefitsMove more freight efficiently Improve Energy EfficiencyReduce Costs Improve SafetyHelp address driver shortage

8

Questions