| ITS Deployment Evaluation

Lessons Learned: Transit Pedestrian Indication (PT11)

51 unique lessons found.

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

Date Posted: 12/19/2017 | Source Date:

Connected Vehicle Deployment Technical Assistance: Roadside Unit (RSU) Lessons Learned and Best Practices

05/01/2020

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

Date Posted: 12/19/2017 | Source Date:

Connected Vehicle Deployment Technical Assistance: Roadside Unit (RSU) Lessons Learned and Best Practices

05/01/2020

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

Date Posted: 12/19/2017 | Source Date:

Connected Vehicle Deployment Technical Assistance: Roadside Unit (RSU) Lessons Learned and Best Practices

05/01/2020

Separately deploying mileage-based user fee and in-vehicle safety alert functions helps ensure each technology has the best opportunity for user acceptance.

Date Posted: 09/26/2017 | Source Date:

Connected Vehicles for Safety, Mobility, and User Fees: Evaluation of the Minnesota Road Fee Test

02/02/2013

Deploying advanced wayfinding technologies in transit agencies present communications, legal, institutional, and technical challenges

Date Posted: 02/27/2017 | Source Date:

Traveler Information Systems and Wayfinding Technologies in Transit Systems: Summary of State-of-the-Practice and State-of-the-Art

05/02/2011

Conduct a data collection pilot test to validate end-to-end data acquisition, transfer, processing, and quality assessment processes.

Date Posted: 01/31/2017 | Source Date:

Safety Pilot Model Deployment: Lessons Learned and Recommendations for Future Connected Vehicle Activities

09/02/2015

Specify interoperability testing requirements and steps as part of the connected vehicle device requirements prior to starting multiple rounds of testing, feedback, reset, and retesting.

Date Posted: 01/31/2017 | Source Date:

Safety Pilot Model Deployment: Lessons Learned and Recommendations for Future Connected Vehicle Activities

09/02/2015

Clearly communicate requirements and testing procedures to connected vehicle device developers, and allow for industry input and iteration for less mature devices.

Date Posted: 01/31/2017 | Source Date:

Safety Pilot Model Deployment: Lessons Learned and Recommendations for Future Connected Vehicle Activities

09/02/2015

Develop a focused outreach plan that identifies all stakeholders, the message appropriate for each stakeholder and the method in which you will reach the stakeholders when embarking on a connected vehicle project.

Date Posted: 01/31/2017 | Source Date:

Safety Pilot Model Deployment: Lessons Learned and Recommendations for Future Connected Vehicle Activities

09/02/2015

Use a modular project structure and focus on high priority objectives and project components when deploying complex ITS projects such as those with connected vehicle technologies.

Date Posted: 01/31/2017 | Source Date:

Safety Pilot Model Deployment: Lessons Learned and Recommendations for Future Connected Vehicle Activities

09/02/2015