Lesson

Tune traffic density and speed parameters within connected vehicle (CV) applications to balance proper alerts versus false alarms in dense urban environments.

U.S. Department of Transportation Free Public Webinar Series on the Connected Vehicle Pilot Sites System Design Process.

10/02/2017
New York City; New York; United States

E-mail this Lesson  E-mail | Comment on this Lesson Post a Comment

Background (Show)

Lesson Learned

Lessons Learned from the NYCDOT Connected Vehicle Pilot Update at the System Design Milestone webinar.

    Address privacy of safety/operational data using multiple tools. Stakeholders need reassurance on the protection of their privacy. The key is to focus on privacy by design. Protection may include:
    • Memorandum of Understandings (MOU)
    • Onboard data encryption
    • Collection time limits
    • Data obfuscation, sanitization, normalization.
    Address security in all aspects of the CV and DOT system. Including but not limited to:
    • Transportation Management Center (TMC) security (physical, system access needs)
    • Devices & networks (operating firewalls, Network Address Translation (NATs), management)
    • Complexity and troubleshooting
    • Security monitoring.
    Have a correction in place to handle the inaccuracy of GPS in urban canyons. The accuracy of GPS data depends on many factors and is often limited to open sky. Accuracy diminishes in areas like NYC with tall buildings, bridges, overpasses, etc. To address this issue, the NYC Pilot vendors introduced a combination of supporting techniques to improve location accuracy, including:
    • Dead reckoning
    • CAN bus integration for speed information
    • Inertial Management Unit (IMU) integration
    • Roadside Unit (RSU) triangulation.
    Tune the applications for the proper density and speed of the environment that you are deploying in. In the absence of standard performance requirements for applications, it became evident that each vendor had their own interpretation and tuning of applications deployed. For NYC, it was key that the applications be tuned for urban density and speeds to balance proper alerts versus false alarms. This required:
    • Consistent expectations for the drivers about the sensitivity of the applications across all vendors
    • Performance tradeoffs
    • Staging open sky testing (for baseline) and urban canyon testing.
    Do not underestimate how long it will take to secure FCC Licenses for Dedicated Short Range Communications (DSRC) devices. The FCC license application process cannot be done with a bulk application. Submission for all RSUs and devices must be done one at a time. This process took 18 months for all 400 RSUs being used in the NYC deployment. NYCDOT did however obtain two waivers to help expedite the process:
    • An Interdepartment Radio Advisory Committee (IRAC) geographic coordination waiver
    • Waiver on Environmental Impact Statement on DSRC antennas.

Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

New York City (NYC) Pilot Update at the System Design Milestone Webinar

Author: Walker, Jonathan (Program Manager, Research & Demonstration, USDOT ITS-JPO); Mohamad Talas (NYCDOT, NYC CVPD Project Management Lead); Bob Rausch (TransCore, NYC CVPD Site Deployment Lead); and David Benevelli (TransCore, NYC CVPD System Engineering Lead)

Published By: ITS Joint Program Office U.S. Department of Transportation

Source Date: 10/02/2017

URL: https://www.its.dot.gov/pilots/pdf/CVP_NYCDOTSystemDesignWebinar.pdf

Lesson Contacts

Lesson Analyst:

Kathy Thompson


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Lesson ID: 2018-00809