Pilot Data Collection Tool

The online data collection tool was developed using a combination of

Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), PHP, and JavaScript. The data collection tool incorporated several dynamic features but was not designed to automatically perform quality checks. Instead, quality checks were conducted manually. Should manual quality checks require additional information, participants were encouraged to provide contact information with the stipulation that all contact information would remain confidential. Additionally, participants were reassured that contact information provided would only be used to verify responses to the pilot study and not for any purpose beyond the pilot study.

The pilot data collection tool was designed to enable bulk package accident damage information to be collected accurately and with minimal difficulty for pilot study

participants. However, the project team envisions the incorporation of several additional features in a fully implemented system. To identify useful features, participants were also

167

asked to share their ideas on how to improve the collection process through a series of comment boxes.

5.2.1 Pilot Data Collection Tool Launch Site

All invitations to participate in the pilot study directed the participants to a website that introduced the project and provided information about the types of information to be requested as part of the pilot study. (Screenshots of the sections of the pilot study data collection tool that are discussed here and below can be seen in Appendix E.) From the website’s home page, participants could access the pilot data collection tool to submit a report.

5.2.2 Pilot Data Collection Tool Instructions

Upon accessing the pilot data collection tool, participants were instructed to forgo using their browser’s “back,” “forward” or “refresh” commands prior to submitting the report. This was necessary because the data collection tool was not sophisticated enough to prevent a resetting of the form when the browser refreshed a page thereby causing their responses to be erased.

The participant was then directed to the instruction page for the data collection tool. The participant was again reminded not to leave the page or refresh their browser prior to submitting their information because doing so would cause the information entered to be lost. They were informed that the submit button could be found on the "Accident

Information" tab, once the type of bulk package was identified. To start, the participant was asked to identify the type of bulk package. This resulted in the appearance of additional fields that were specific to the type of package selected. After completing the fields that were specific to the package type, the participant was asked to proceed to the "Bulk Package Information" tab.

The instructions also informed participants that if they were unsure what information was being requested or would like clarification concerning the available responses, they should refer to the tab marked "Pilot Test Supplemental Information." If the information was not there, they were requested to leave a comment so that this

information could be provided in the future.

Finally, participants were informed that because this was a pilot study, quality checks had not been built into the data collection tool. Therefore, participants were asked to take

168

measures to ensure that they had responded correctly. Participants were also asked to provide their contact information so that clarification could be obtained should an

unexpected result be received. They were once again informed that all contact information provided would remain confidential and be removed from the dataset containing the results of the pilot study after the information had been corroborated.

5.2.3 Data Collection Pages

The pilot data collection tool consisted of the following four sections:

 Bulk Package Design Information. For cargo tanks, this section recorded

information that was visually detected or listed on the cargo tank name plate. To clarify what information was requested, an exemplar name plate was included. For portable tanks, this section recorded information that was: found visually, stamped on the tank's head or a separate placard, or provided as part of the container specifications.

 Basic Commodity Information. This section recorded information found in

shipping papers associated with the commodity transported at the time of the accident.

 Bulk Container Damage Information. This section recorded information on

the area(s), components, and type of damage incurred in the accident as well as the amount of lading lost. Several dynamic form features were used, including the following:

– Displaying the appropriate damage location image for a portable tank, a trailer-mounted cargo tank or a truck-mounted cargo tank, dependent on the package type selected.

– Not displaying questions associated with undamaged components

– Not displaying questions associated with damage type and subsequent fields until the damage location had been selected.

– Not displaying damage dimensions and questions concerning a release until the damage type had been selected.

– Not displaying bulk package breach dimension questions until a release had been verified.

169

 Basic Accident Information. This section recorded information concerning the

object impacting the bulk package, speeds of the vehicle(s) involved in the accident (when applicable), and whether the bulk package rolled over.

Note that the pilot data collection tool did not display location-specific components.

5.2.4 Supplemental Information

To further clarify what information was being requested, a supplemental information page was included in the pilot data collection tool. The intention was to provide responses to questions or comments previous participants had included in the comments fields. Initially, however, the only supplemental information provided were the exemplar specification plates for a cargo tank or portable tank, corresponding to the type of bulk package initially identified (Appendix E).