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

Appendix C - PBCAT User Comments

Note: Those comments with an asterisk were addressed as part of the final version known as release 1.00.

PBCAT Software

Installation

  • We were required to close running apps prior to setup.
  • Installed smoothly.
  • Installed easy.
  • Installation was very easy.
  • Installing to D: drive resulted in errors; C: drive ok.*
  • Definitely recommended to close out other programs prior to installation.
  • Had to install three times before it would run, kept getting "run time 76" error message.*
  • Very easy and well laid-out.
  • I did not install but read thru as co-worker installed it.

Startup – Overview

  • Very clear.
  • This is explained in literature, so repetitive.
  • Clear -- may want to add additional examples of possible variable fields (you list one example -- county).

Startup – Preferences

  • Somewhat overwhelming at first, but as I began experimenting I enjoyed the extra user control.
  • Good selection along with variable user defined.
  • The written documentation was helpful here.
  • Recommend users create database in a root directory.

Pedestrian

Introduction – Purpose

  • Informative.
  • Easy to understand.
  • Clear.

Introduction – Examples

  • Excellent.
  • Good intro and runs the screens well.
  • Same as bike.
  • Clear.

Database Transfer

  • Did not have an opportunity to use.
  • Trouble with dates, year.*
  • Database transfer was very hard to read.
  • Did not use this feature, but instructions seemed clear.
  • Didn't use.
  • Not used. Did try briefly but no luck (probably due to my inexperience).
  • I had a lot of trouble with the database transfer -- trouble with names of files and renaming.

Crash Typing – Data Entry

  • Data entered inconsistent with data in final report. (e.g. data field).
  • Very easy.
  • Entered 1992 and 2092 appeared.*
  • At times I wasn't sure which variable to choose. It happened very rarely.
  • Confusion about codes for novices.
  • After doing a few entries I started to get a good feel for the options and I felt it was straightforward.
  • Simple to enter data, lots of fields (necessary) adds to input time.
  • You can’t tab through hit & run menu—you must use mouse to select.*
  • Entry is simple, however, there was constant change between hand entries and using the mouse.*

Crash Typing – Typing

  • Very interesting/engaging.
  • Had to re-enter.
  • Need clearer instruction to direct to the codes; need to know how to calculate military time quickly.
  • On a couple of the Florida crash reports, I wanted more choices for turning movement conflicts. All directions of potential conflicts should be given as choices -- not the case as you move through the software.
  • No "blame" assigned.
  • I entered the whole ped data three times and was surprised to fine that I occasionally did not arrive at the same results each time.

Crash Reports

  • Different format took getting used to.
  • Did not use.
  • Sometimes overwhelming and remembering what is what on the fields.
  • Very simple and easy to use.
  • Same as bike.
  • Didn't use on test #2.

Countermeasures

  • Did not use.
  • Reviewed several, very general.
  • Very useful tool.
  • If you select crash group only (backing vehicle) and select view countermeasures you get crash type 110 not 211. Not clear on difference between crash type vs. crash group. Need back navigator button.
  • Very broad overly general countermeasures for some crash types.
  • Would rather use a cross-reference table on paper.
  • Didn't use on test #2.

Bicycle

Introduction – Purpose

  • Instructive.
  • Easy to understand.
  • Clear.

Introduction – Examples

  • Nice walk-through.
  • Typo in "single variable summary" -- interset --> interest.*
  • Clear -- clarity of scanned graphics varies.

Database Transfer

  • Did not use.
  • Same trouble with dates 1992-2092.*
  • Hard to read.
  • Did not use this feature, again instructions appeared straightforward.
  • Didn't utilize.
  • Not attempted for bicycle crash reports.
  • I had a lot of trouble with the database transfer -- trouble with names of files and renaming.

Crash Typing – Data Entry

  • Same as ped "crash typing data entry."
  • Clear and easy.
  • Once familiar with the hierarchy.
  • Had a little more difficulty with this batch than with ped. More to enter.
  • Again clarity of instruction.
  • The bicycle section took a little more getting used to the 3 choices for parallel or crossing paths.
  • Very much liked more detailed options compared to old cross-fisher typing.
  • Simple to enter data.
  • Entry is simple, however, there was constant change between hand entries and using the mouse.

Crash Typing – Typing

  • In some instances crash typing might get confusing.
  • More difficult than pedestrian segment.
  • Too general.
  • Took a little getting used to. I did not initially realize that each picture led to different choices.
  • Fine.
  • No "blame" assigned -- would be useful for educational purposes.
  • I entered the whole bike data three times and was surprised to find that I occasionally did not arrive at the same results each time. Determining type was easier than for ped. Differing between veh 1 and veh 2 was time consuming, but "doable."

Crash Reports

  • Same as ped "crash reports."
  • Did not use.
  • Can help to identify.
  • Very simple and easy to use.
  • Still getting run-time error '383' .*
  • Didn’t use.

Countermeasures

  • Did not use.
  • Not sure these are all that useful, general fixes that border on the obvious.
  • Very useful tool.
  • Include bike helmet recommendation.
  • Very broad overly general countermeasures for some crash types.
  • Would rather use a cross-reference table on paper.
  • Didn’t use.

Manual Comments

Installation

  • Minimum free drive space needs to be increased.*
  • Prefer to use printed copy to on-screen PDF.
  • I did not install but read thru it.

Startup – Overview

  • The manual is very well done. Use of color is probably expensive, but really helps improve ease of use (clearly connects to what is on screen). A "searchable online" manual would be great. Overall, 8-10 for ease, clarity, function, practicality.

Pedestrian

Database Transfer

  • Not done, but directions OK.
  • Not enough detailed info for those who are working off higher access versions.*

Crash Typing – Data Entry

  • More info regarding "save" feature.

Crash Typing – Typing

  • Clear and easy to find crash type.

Crash Reports

  • Not done.

Countermeasures

  • Not done.
  • Didn't really use this feature.

Bicycle

Database Transfer

  • Not done, but directions OK.
  • Not enough detailed info for those who are working off higher access versions.

Crash Typing – Data Entry

  • More info regarding "save" feature.

Crash Typing – Typing

  • Clear and easy to find crash type.

Crash Reports

  • Very brief in manual, covered well in software example.
  • Not done.