Lesson

Connected vehicle deployers are encouraged to utilize multi-vendor outsourcing and to source suppliers early to create a collaborative environment that enables as much parallel work as possible.

Lessons Learned from the Design/Build/Test Phase of the USDOT's Connected Vehicle Pilot Program.


12/13/2018
Tampa,Florida,United States; New York City,New York,United States; Wyoming,United States


Background (Show)

Lesson Learned

The following lessons were identified regarding engaging with project partners and device vendors.

Utilize RFPs to scrutinize and select the best suppliers
    It is suggested that agencies conduct multiple technical scans using request for proposal (RFP) documents that require on-the-road testing to identify promising suppliers who can meet system, cost and project timing requirements. Since this technology cannot be purchased off the shelf yet, the New York City pilot did a Request for Expression of Interest (RFEI) demonstration/evaluation, where two vendors were eventually selected as their Aftermarket Safety Device (ASD) suppliers. The winner of the New York City RSU bid resulted in award to the same vendor partnered with THEA's project from very early on in the Pilots. Although THEA did not go through an RFP process, NYC's selection of the same vendor as THEA validated THEA's up-front research.

    WYDOT on the other hand did not utilize RFPs in the procurement of their devices. Some of their procurements were sole-source and others were extensions of existing contracts WYDOT already had with current partners.

Utilize multi-vendor outsourcing and source suppliers early to create a collaborative environment
    Early sourcing of suppliers is key to understand how system requirements are implemented in the design and to allow for participation in developing open specifications. To reduce risk, it is wise to select more than one supplier in the event that a supplier is unable to commit to previous agreements. With multiple selected vendors, an agency can disqualify any non-performing vendors (if needed) and continue with the performing vendor for the full complement of units.

    During the implementation phase, both the New York City and Tampa Pilots had to deal with suppliers backing out. In New York City's case, they had originally selected two Onboard Unit (OBU) suppliers, however, one of the suppliers could not sign the final contract in good conscience as they did not think they could sufficiently meet NYC's design specification requirement for the vehicle's positioning accuracy. Similarly, one of Tampa's initial vendors had to withdraw because they could not provide the support outlined in the contract.

Be mindful of nuances associated with language when working with external parties
    Not everyone has the same common understanding of terminology. In discussion with their vendors, the THEA team found that vocabulary between organizations do not always match. THEA went back and forth with their device manufacturers for six months about why they would not be able to deploy THEA's planned Curve Speed Warning application. It turned out that Curve Speed Warning meant something else to the manufacturer, so THEA ended up renaming the application End of Ramp Deceleration – which the vendor was in agreement with. THEA cited that if they had known all along that it was just a misunderstanding of the application name, the issue would have been resolved in a few hours and saved them six months of hassle.

Establish contacts with traffic controller software manufacturers
    As the standards for connected vehicle systems evolve overtime, the software of the traffic controllers will likely need to be updated. Having an established relationship in place with the software manufacturers will enable them to easily access the devices to make the necessary changes when needed.


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 Driving Towards Deployment: Lessons Learned from the Design/Build/Test Phase

Author: Thompson, Kathy

Published By: USDOT Federal Highway Administration

Source Date: 12/13/2018

Other Reference Number: FHWA-JPO-18-712

URL: https://rosap.ntl.bts.gov/view/dot/37681

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Kathy Thompson


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Lesson Categories

Procurement > Method of Award

Application Areas

Intelligent Transportation Systems > Driver Assistance > In-Vehicle Monitoring

Intelligent Transportation Systems > Arterial Management > Enforcement > Speed Enforcement

Intelligent Transportation Systems > Arterial Management > Enforcement > Traffic Signal Enforcement

Intelligent Transportation Systems > Arterial Management > Surveillance > Traffic

Intelligent Transportation Systems > Arterial Management > Traffic Control > Advanced Signal Systems

Intelligent Transportation Systems > Crash Prevention & Safety > Collision Avoidance > Forward Collision Warning

Intelligent Transportation Systems > Crash Prevention & Safety > Collision Avoidance > Lane Change Assistance

Intelligent Transportation Systems > Crash Prevention & Safety > Collision Avoidance > Obstacle Detection

Intelligent Transportation Systems > Crash Prevention & Safety > Collision Avoidance > Rear Impact Warning

Intelligent Transportation Systems > Crash Prevention & Safety > Intersection Collision Warning

Intelligent Transportation Systems > Crash Prevention & Safety > Pedestrian Safety

Intelligent Transportation Systems > Crash Prevention & Safety > Road Geometry Warning

Intelligent Transportation Systems > Driver Assistance > Driver Communication

Intelligent Transportation Systems > Driver Assistance > Object Detection

Intelligent Transportation Systems > Emergency Management > Emergency Medical Services

Intelligent Transportation Systems > Emergency Management > Response & Recovery > Evacuation & Re-Entry Management

Intelligent Transportation Systems > Emergency Management > Response & Recovery > Emergency Traveler Information

Intelligent Transportation Systems > Road Weather Management > Surveillance, Monitoring, & Prediction

Intelligent Transportation Systems > Road Weather Management > Information Dissemination

Intelligent Transportation Systems > Roadway Operations & Maintenance > Work Zone Management > Speed Enforcement

Intelligent Transportation Systems > Transit Management > Operations & Fleet Management > Transit Signal Priority

Countries

United States

Systems Engineering

Show the V

None defined

Keywords

photo enforcement, speed cameras, automated speed enforcement, automated enforcement, photo radar, red light cameras, red light running, traffic signals, run red lights, RLR, red light runners, photo-red, CCTV, closed circuit television cameras, road monitoring, sensors, vehicle detector, traffic detection, traffic monitoring, congestion monitoring, coordinated signals, signal coordination, centralized signal control, signal synchronization, advanced signal control, signal timing optimization, coordinated signal control, advanced signal controller, traffic signal retiming, retiming, smart work zone systems, smart work zone, smart work zones, Smart work zone, Smart work zones, workzone, WZ, bus priority, TSP

Lesson ID: 2019-00870