Index
Technical Report
Background
Crash Typing Results
Survey Results
Follow-Up Process Evaluation
Approach
Results
Discussion
Conclusions
Recommendations
Appendix A and B:

Appendix C - PBCAT User Comments

Recommendations

In general, most of the participants in this test, and the last one conducted for FHWA, were pleased with the software. However, there is always room for improvement. Using the results from these tests and comments from our own project staff, the following improvements should be considered for future versions of the product:

1) Possibly reduce the number of crash types to a level that corresponds to the types of countermeasures suggested. This approach was considered when PBCAT was first conceptualized, but dropped from consideration because of the clamor for more detail from some practitioners. This issue should be revisited and considered from the viewpoints of both the researcher and the practitioner.

2) Develop a network version that would allow data entry to be completed on multiple machines in multiple offices. The data base would reside in a central location and be accessible to all remote sites.

3) Develop a web-based version that could be used on the Pedestrian and Bicycle Information Center web site. The data storage would be managed by the PBIC staff. This approach would allow for the creation of a "national" data set.

4) Enhance the countermeasures portion of the product. The countermeasures need to be more closely linked with the crash types. At the same time, there needs to be a better system for allowing users to select countermeasures. There are projects underway that will address some of these concerns. The results of these efforts need to be incorporated into future versions of the software.

5) Continue to make the product as user-friendly as possible. As the development software improves, more can be done to improve the features of the product. The version of Visual Basic available now, versus what was used to develop the software, would allow for a significant number of improvements.

6) Provide some level of product support. Currently, there is no mechanism in place to provide technical assistance to users of the software. In the short-term, this is being addressed through the PBIC.

7) Develop a long range strategy for the product, including marketing products and iterative improvements, with a goal of creating a national data set that could be used to better define pedestrian and bicycle crashes.