Lesson

Include technical, operations, and legal personnel in stakeholder meetings to address the requirements of the CV deployment and ensure that participants' privacy is being maintained

Success Stories from the USDOT’s Connected Vehicle Pilot Program

11/01/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

The NYCDOT leads the New York City Pilot, which aims to improve the safety of travelers and pedestrians in the city through the deployment of V2V and V2I connected vehicle technologies. This objective directly aligns with the city’s Vision Zero initiative, which seeks to reduce crashes and pedestrian fatalities and increase the safety of travelers in all modes of transportation. Approximately 310 intersections in Midtown Manhattan and central Brooklyn will be instrumented with roadside devices to communicate with up to 8,500 vehicles (taxis, buses, commercial fleet delivery trucks, and city-owned vehicles) equipped with after-market safety devices. These devices will monitor communications with other connected vehicles and infrastructure and provide alerts to vehicle. In addition, NYCDOT will deploy approximately 8 roadside devices along the higher-speed FDR Drive to address challenges such as short-radius curves, a weight limit and a minimum bridge clearance and 36 roadside devices at other strategic locations throughout the City to support system management functions.

NYCDOT first approached the Taxi and Limousine Commission (TLC), Metropolitan Transportation Authority (MTA), United Parcel Service (UPS), and others to propose a large-scale deployment of connected vehicles. The meetings included technical, operations, and legal personnel to address a wide range of issues, including device installation, maintenance requirements, operating hours, operator selection, geographic coverage areas, stakeholder responsibilities, system operation, driver interface, and data collection activities. A concern of all stakeholders was that any data generated could, if collected, be used for driver evaluation or that such data could be subpoenaed for criminal and/or civil suits or the subject of a freedom of information act (FOIA) request for any and all records available that could then be merged with other records (e.g. police accident reports) and used in legal proceedings, disciplinary proceedings, or insurance negotiations. However, the City assured their stakeholders that they would be implementing a number of measures to protect the privacy of the participants and to make sure that the data collected cannot be disaggregated and analyzed or merged with other data (e.g. police accident records) to determine the exact actions and location history of any specific operator or vehicle.

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

Connected Vehicle Pilot Deployment Program: Success Stories

Author: Glassco, Rick; James O'Hara; Barbara Staples; Kathy Thompson; and Peiwei Wang

Published By: USDOT Office of the Secretary for Research and Deployment

Source Date: 11/01/2017

URL: https://www.its.dot.gov/pilots/success_lessonslearned.htm

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Kathy Thompson


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Lessons From This Source

Allow for increased coordination with the Interdepartmental Radio Advisory Committee (IRAC) early on in the DSRC licensing process to help reduce what is traditionally a very lengthy process.

Connected Vehicle Pilot Deployment Program yields program management best practices for integrating and testing large disparate systems.

Connected vehicles should rely on more than one data feed to determine accurate location and speed

Consider installing additional vehicle detection equipment if it is determined that there is not sufficient market penetration for CV traffic signal control applications to work at their full potential

Facing a gap in standards interpretation, the Tampa and New York City Connected Vehicle Pilot Sites worked together to harmonize message structure for pedestrian safety applications.

For pedestrian safety warning applications, opt to collect pedestrian location data from LIDAR sensors instead of pedestrian mobile devices that often have insufficient accuracy.

Incentivize participation in CV deployments through benefits such as toll discounts

Include technical, operations, and legal personnel in stakeholder meetings to address the requirements of the CV deployment and ensure that participants' privacy is being maintained

Incorporate standardized over-the-air update procedures to permit efficient firmware updates for connected vehicle devices.

Obtain working prototypes of CV applications from the USDOT’s Open Source Application Data Portal (OSADP) to prevent time spent doing duplicative software development

Prevent the need for channel switching (a safety hazard) by designing CV communications to include dual radios in each vehicle

Publish all CV planning documentation to serve as an example for other early deployers to follow

The USDOT’s three Connected Vehicle Pilots successfully demonstrate cross-site over-the-air interoperability among six participating vendors.

Use local student mechanics where possible to perform CV equipment installations to provide students with required trainee experience and to contain costs

Use on-board connected vehicle (CV) technology and SPaT / MAP infrastructure messages to prevent wrong way entries on reversible express lanes.

When installing antennas on streetcars to support wireless connected vehicle applications, verify that radio performance is not compromised by interference from high-voltage power lines.

Lesson ID: 2017-00794