SPaT Challenge Webinar SeriesWebinar #9: Operational SPaT Deployments

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

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, Introduction, and Updates Blaine Leonard, Utah DOT

• Operational SPaT Deployments Mohd Aslami, North Carolina DOT Alan Davis, Georgia DOT

• Q&A

4

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!

2 1/2 years of progress:39 Locations

26 States

500 RSUs Operating

2360 RSUs Planned

5

SPaT Challenge Websitehttps://transportationops.org/spatchallenge

6

SPaT Challenge Webinars to Datehttps://transportationops.org/spatchallenge/webinarseries

• Eight webinars conducted to date Recordings available in full or by topic on SPaT

Challenge website

1. Initial SPaT Challenge Activities (March 6) SPaT Challenge introduction Systems Engineering Approach Overview of Model Concept of Operations and

Requirements documents Costs, Procurement, and Corridor Selection

7

SPaT Challenge Webinars to Datehttps://transportationops.org/spatchallenge/webinarseries

2. Design Considerations, Part 1 (March 20) SPaT Messages, Data Assembly, and the Signal

Controller Interface V2I Hub Overview Agency experience with deploying on-board units

3. Design Considerations, Part 2 (April 17) Overview of MAP Messages Utah DOT’s MAP Message Creation Approach Vehicle Position Correction Need and Solutions

8

SPaT Challenge Webinars to Datehttps://transportationops.org/spatchallenge/webinarseries

4. MAP Creator Tool Demonstration (April 24) USDOT MAP Creator Tool (Leidos / Saxton Lab) Information about accessing/using the Tool

5. Design Considerations, Part 3 (May 15) RSU Specification v4.1 Roadside Equipment & Backhaul Communications DSRC Licensing

6. Deployment and Validation (June 12) Security Credential Management Verifying SPaT Deployments’ Compatibility with Vehicles Michigan DOT Completed SPaT Deployment Verification USDOT CAV Support Services

9

SPaT Challenge Webinars to Datehttps://transportationops.org/spatchallenge/webinarseries

7. Operational SPaT Deployments (July 17) Las Vegas Virginia DOT Utah DOT

8. SPaT Challenge Next Steps (August 14) Operational SPaT Deployments in Pennsylvania Connected Fleet Challenge Equipping Transit Fleet Vehicles with OBUs in Utah

10

SPaT Challenge Websitehttps://transportationops.org/spatchallenge

11

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

12

Upcoming SPaT Challenge Webinar

• Operational SPaT Deployments

January 22, 2019: 2:00 – 3:30pm Eastern

Register and find more information at: https://transportationops.org/spatchallenge/webinarseries

13

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

14

SCMS Systems Webinar 6 included a presentation on SCMS systems, functions and needs Trust is the key element of SCMS Recommended that we implement

certificate systems sooner, rather than laterUSDOT led the creation of the SCMS Proof-of-Concept system to support CV Pilots Proof-of-Concept system not suitable to scale up for

national deployment No overall policy framework / No misbehavior detection

15

SCMS SystemsFHWA recently held two workshops to develop strategies for deploying a full-scale SCMS system Governance and Oversight High-level Policies Roles and Responsibilities Business and Financial Models

A National SCMS System is not imminent

16

SCMS SystemsThe current landscape: CV Pilot sites are using a private certificate provider GM (Cadillac) has a certificate system for their models Some agencies are exploring certificates through

private providersThese workable and available solutions are not the same as a complete national SCMS system

17

Federal AV GuidanceNew guidance for automated vehicles (ver 3.0) released in September Increases focus on other modes Reiterates that connectivity (V2V and

V2X) is a complementary technology that will enhance automation

SPaT Challenge is mentioned USDOT encourages continued

deployment and use of the 5.9GHz spectrum but does not promote any specific technology

Operational SPaT Deployments

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

Statewide Connected Vehicles

Deployment Experience and Future Plans

Connected Vehicles

Mobility

Safety

Freight

Partnerships

Alan Davis, PE, PTOEAssistant State Traffic Engineer

•Primary goal: Develop back-end infrastructure, network components, and business processes to support broad vehicle to infrastructure applications that is broadcast-medium agnostic, scalable, and sustainable.

•Secondary goal: Begin broad installation of roadside units and equipped vehicles to facilitate applications that improve safety and mobility.

Primary Application Spaces:

MobilitySafety Freight Partnerships

Pilot Deployment Objectives

Active Deployments

Phase 1: Pilot – June 2018

• SR 141 (Peachtree) from SR 9 to I-285

• SR 8 (Ponce de Leon) from Peachtree to SR 42

• 54 traffic signals

• 12 ramp meters

• Signal Phasing and Timing (SPaT)

• Red light warning

• Pedestrian in signalized crosswalk

• Phase termination/next signal phase

• Green-band speed

GDOT CV Architecture

• CV Application resides on signal controller

• No additional hardware (outside of RSU) required

• Open access to third parties

• Controller can handle application

• Signal priority

ATC Signal Controller

CV App

NTCIP 120112021211

HTTPS/WS

Open Data API

HTTPS/WS

Signal Central System

HTTPS/WS

DSRC Radio

SAEJ2735

SPaTMAPBSMBIMTIM

SAEJ2735

HTTPS/JSON

Multiple Broadcast Channels

Car 1: Non-connected vehicle

Car 3: 5.9 GHz DSRC connected vehicle

Car 2: Cellular connected vehicle

Intersection 1No DSRC

Intersection 2No DSRC

Intersection 3DSRC Installed

Intersection 4DSRC Installed

Third Party Service

Real-time signal phasing and timing information

Aggregated data analytics for increased

route efficiency

Increased awareness improving safety and mobility

Phase 1 SPaT ApplicationsRed light warning Safety for drivers – alerts of

inability to safely clear intersection

Pedestrian in crosswalkSafety for drivers and pedestrians –

turning vehicles have additional awareness of other users

Phase service remainingEfficiency for drivers – alert drivers

for safe intersection passage or efficient stopping

Green speed for coordinated signals

Efficiency for drivers – inform drivers of the optimal driving speed

through coordinated signals to minimize stops

ACTIVE DSRC IN METRO ATLANTA• SR 141 (Peachtree) – 39 intersections• SR 8 (Ponce de Leon) – 15 intersections

• North Ave – 22 intersections (Renew)

Deployment

Deployment

Deployment

Deployment

Phase service

remaining

Intersection name

Debug information

Minimum speed

required to clear green

Vehicle speed

Red light running warning

Validation and Testing• Properly formatted, J2735-compliant messages

• Ingress lanes that include a ConnectsTo but that egress lane is not defined (or is not defined as an egress)

• Ingress lanes that do not include a ConnectsTo

• Ingress lanes that do not include a signal phase/approachId

• Incorrect or missing ingress/egress definitions for each approach

• Overlap/underlap of lanes and widths

• Incorrect ‘ConnectsTo’ lanes

• General layout and structure of lane paths/geometries

• Signal phases being reported as “dark” or “unavailable”

• Correctness of the time remaining values

• Inconsistency of the reported minTime and maxTime (ie. min greater than max)

• Unexpected changes in minTime and maxTime

• Accuracy of the reported phase vs the actual signal

• Transmit rate of each message type

Project Challenges• Device interoperability

• Controller to RSU

• RSU to OBU

• OBU to OBU

• MAP message creation and validation

• Protected/permissive left turns

• What’s a ramp meter?

• Application deployments

• Security credentialing

• Data

• Limited fleet

• Regional communications network

• Communications• ATC Signal

Controller• DSRC Radio

Scalable Deployment

Strategy

Broad deployment potential in

Georgia

Phase 2 Deployment

Phase 2 Deployment

Phase 2: RTOP – June 2020

• 1,700 traffic signals in metro Atlanta• 185 ramp meter locations• Safety applications• Signal applications

• Red light warning

• Pedestrian in signalized crosswalk

• Phase termination/next signal phase

• Green-band speed

• Road and traffic conditions information

Phase 2 Deployment

Phase 2: RTOP – June 2020

• First 250 of FY 2019 to be installed by end of 2018• Connectivity on every major arterial in metro Atlanta• Open data stream to third parties also available

Phase 2 Deployment Est. FY 2019 (600) FY 2020 (1100)

RSU Equipment $780,000 $1,430,000

RSU Deployment $510,000 $935,000

RSU Configuration & Support $1,200,000 $2,200,000

TOTAL $2,490,000 $4,565,000 •1,700 Roadside units at $1,300 per device. Total: $7,055,000 •RSU deployment at $850 per location.

First 250 RSUs of FY 2019 to be installed by end of 2018

•RSU configuration at $2,000 per device.

•OBU costs at $1,000 per device (optional).

Phase 2 Deployment

Alan Davis, PE, PTOEAssistant State Traffic Engineer

404-635-2832aladavis@dot.ga.gov

SPaT Challenge Implementation

Mohd Aslami, PE, CPMNC DOT- ITS & Signals Unit

Payload=0013534484D0000800009C3E4000006201043435723811804002020464350D36B4804002030434352F36D6804002040434352F378D80400205046434A5B4D100400206043434C734F280400216043434C734F2804000

2

SystemOverview

• 20 Locations in Cary, NC• 16 locations along NC

Highway 55 – 6.6 miles• Additional 4 locations

along High House Rd –1.6 miles

3

Locations• NC Highway 55 &

Parkside Green• NC Highway 55 &

O’Kelly Chapel• NC Highway 55 &

540 NB On Ramp• NC Highway 55 &

540 NB Exit Ramp• NC Highway 55 &

540 SB On Ramp• NC Highway 55 &

540 SB Exit Ramp

4

Locations• NC Highway 55 & Petty

Farm Rd• NC Highway 55 &

McCrimmon Pkwy• NC Highway 55 &

Carpenter Fire Station Rd• NC Highway 55 &

Morrisville Carpenter Rd• NC Highway 55 &

Morrisville Pkwy• NC Highway 55 & Green

Hope School Rd

5

Locations• NC Highway 55 & High House

Rd• NC Highway 55 & Parkscene Ln• NC Highway 55 & Turner Creek

Rd• NC Highway 55 & Old Jenks Rd• High House Rd & Carpenter

Upchurch Rd• High House Rd & Cornerstone

Dr• High House Rd & Davis Dr• High House Rd & Lily Ridge

Pond

6

Project Overview

• Project awarded to Econolite on July 20, 2017 • Initial approved equipment were Savari RSUs & OBUs• Anticipated completion time was estimated 19 weeks

from data of availability• 20 networked intersections were in the project scope• Procurement method was Turn-key• Payment type was Itemized• Total Project cost was $506,948.00 or $25,347.40/site

7

Existing Infrastructure

• Existing signal infrastructure included NEMA TS2 Cabinets with 2070E controllers and Econolite ASC/3 software

• The system resides on a Ethernet fiber optic network• The central software is Econolite Centracs 2.x

8

Required Upgrades

• Upgrade the existing 2070E controller units Replaced the existing 2070-1B/1E CPU

modules with 2070-1C Replaced ASC/3 OS9 local controller

software with ASC/3 Linux

9

Additional Equipment• RSUs• CV CoProcessor• PoE Injectors• Surge suppressors• Cabling• Signal pole mounting hardware

10

Initial Test Setup• SPaT equipment were installed at the DOT

facility in Garner, NC to conduct proof of concept testing

• Equipment included: Econolite Cobalt controller and ASC/3 software Network Switch PoE Injector Test RSU and OBU

11

Initial Test Setup

• Contractor created MAP & SPaTmessages

• Installed Test OBU with HMI• Verified SPaT & Map messages• Validated design concepts

12

Installation• After proof of concept, 20 Savari RSUs and 5

Savari OBUs were ordered & installed• Savari missed several delivery dates• Units provided did not meet expectation and

were not functioning properly and reliably• QA issues from factory affected delivery

deadlines and product functionality• Technical support was poor and hard to

come by

13

Reboot• On December 2017, decision was made to

cancel project with Savari• Restart the process with evaluation of

multiple RSUs & OBUs

14

Fresh Start

• Invitation to Demonstrate was sent to multiple vendors soliciting participation in January 2018

• The following RSUs were demonstrated and evaluated: Siemens Kapsch TrafficCast

Lear Applied Information Savari

15

Moving Forward

• Demonstrations wrapped up in March 2018• Evaluation was performed by a team with

members from: NCDOT Town of Cary, NC Econolite City of Concord, NC

16

Evaluation

Functionality Applications Interoperability Documentation Ease of Installation Configuration

Packaging/form factor Support MAP Development OTA Firmware

Update

Some of Evaluation Criteria Included:

17

Ranking• Result of evaluation led to the following ranking

• Since Siemens didn’t offer OBU, 1 & 3 were selected for installation on this project

• Applied Information did not offer a DSRC solution, so they ranked lower for the purpose of this project

1. Kapsch2. Siemens3. Lear

4. TrafficCast5. Applied Information6. Savari

18

Installation• New RSUs were ordered in May, 2018• Delivery of RSUs late June/early July• Installation and integration completed in July • Training completed in August• System has been in operation since July

19

Installation ImagesDanlaw OBUWith eTransApplications

Lear OBU&Applications

Samsung Tab AHMI Device

20

Lear App Images

Flashing Yellow Arrow

Demonstration

Red LightViolation Warning

21

Danlaw OBU with eTrans App Images

22

Lessons Learned

• Apply for FCC Licensing early in the process• Write detailed functional requirements• Evaluate multiple products• Require comprehensive testing and training• Require complete documentation for equipment

and construction• Be hands-on if you want to learn

23

Lessons Learned• CoProcessors provided as part of project ended

up being unnecessary• Lead time for equipment may be longer than

expected• Ensure everyone meets the current

specifications. Compatibility issues between equipment may exist due to changing specifications.

• Need for easier MAP file creation

24

Lessons Learned• Expect delays! FCC licensing Equipment lead times Weather

• Expect challenges! Reboot of project Device configuration and MAP file creation

• Don’t expect too much! Applications are still being developed Compatibility issues will arise

25

Lessons Learned

• Isolate DSRC Radio electrically from metal signal pole!

26

What is Next

• Expansion of the test corridor to another 18 intersections

• Deploy additional technology with signal system projects

• Deploy new signals with hardware & software ready for CV deployment

• Develop a statewide CV deployment policy