blank space

South Dakota Department of Transportation
Project Synopsis
SD2000-14


Title: Unified Reporting of Commercial and Non-Commercial Traffic Accidents
Project Researcher: ,
Project Manager: Hal Rumpca
Research Period: 3/1/2001 - 8/31/2001
Status: Dead
Cost: $65,000.00

Problem Statement:In October 1999, the South Dakota Business Research Bureau completed Research Project SD99-05 "Identification of Methods for Truck Crash Reduction". The project identified at least two databases that document motor vehicle crashes. These are the South Dakota Accident Reporting System, which documents all South Dakota reportable crashes, and a database from the National Governors Associations SAFETYNET, which documents United States Department of Transportation (USDOT) reportable events.

The study also identified two forms that are currently used in South Dakota to record commercial and non-commercial vehicle accidents. These forms are the State of South Dakota Investigators Motor Vehicle Traffic Accident Report and the South Dakota Uniform Truck/Bus Supplemental Form. The technical panel overseeing the study recommended "the Office of Accident Records should combine the forms using the Model Minimum Uniform Crash Criteria (MMUCC). The new forms should include additional data fields for speed, approximate weight, and whether the driver holds a Commercial Drivers License (CDL). The Office of Accident Records should develop a data dictionary, instruction manual and coder instructions by June 1, 2001. The office should assist the Highway Patrol in a statewide training effort on the use of the new form". The panel also recommended that "The Office of Accident Records incorporate the use of latitude/longitude coordinates and time in the accident reporting system". Finally, it was recommended that commercial vehicle accident reporting data should be included in the Level 1 Commercial Vehicle Information Systems and Networks (CVISN) Plan, and the Office of Accident Records should update the South Dakota Investigators Motor Vehicle Traffic Accident File to include SAFETYNET data.

The SD CVISN Top Level Design and Program Plan identifies the following objectives for "Safety Information Exchange:

  1. 1)Automate vehicle inspection at major sites,

  2. 2) Exchange interstate carrier and vehicle information with other states,

  3. 3) Share Intrastate safety information within state agencies,

  4. 4) Improve commercial accident reporting manual forms, and automate to improve efficiencies,

  5. 5) Monitor safety and put unsafe carriers in improvement programs. In addition, the CVISN Plan recommends that trucking industry representatives be allowed to query and review their records by password admitted user.

While it may be feasible to combine the State of South Dakota Investigators Motor Vehicle Traffic Accident Report and the South Dakota Uniform Truck/Bus Supplemental Form, major Accident Record System modifications are necessary in order to truly obtain significant benefits. Various jurisdictions including City Police Departments, County Sheriff Departments, the State Highway Patrol (SDHP), Bureau of Indian Affairs (BIA), and Tribal Police record accidents. This requires both paper and electronic reporting procedures. The Highway Patrol has expressed a desire to access the database via law enforcement vehicles, other remote ports, or a web based application. A study needs to be completed to determine the feasibility and requirements for modifying the existing Accident Records Database System or designing and constructing a new Accident Records System. That System must effectively function on its own, yet be compatible with the National SAFETYNET Database, State and National CVISN efforts, and the reporting requirements from the National Center for Statistics Fatal Analysis Reporting System (FARS).



Findings: The main recommendation from this study is to use TraCS as a key component of the migration plan for the front-end data collection piece of the proposed accident reporting system. The use of a client/server-based architecture with a relational database is needed to support the data storage and analysis needs of the users. The FMCSA SAFETYNET commercial vehicle accident data needs to be collected and stored in the electronic database. The report also contains a preliminary design of the combined South Dakota Traffic Accident Report/SAFETYNET form, a detailed data model, a detailed process model, a Process/Entity Usage Matrix (CRUD), a data dictionary, and the approved data elements. Based on the results of the July 25, 2001 technical panel meeting, it may be necessary to revise the form from a one page double sided to a two page folded 11x17 form to include all of the approved Model Minimum Uniform Crash Criteria (MMUCC) items.

Research Objectives:
1  To document the current business processes, forms, and data used for accident reporting in South Dakota's and applicable National Databases.
2  To determine functional requirements for a single system that can record, manage, and track accident information.
3  To define a logical data architecture to address the single system to record, manage, and track accident information.
4  To develop a migration plan for designing and building an updated accident reporting system including costs, resource requirements, phasing, training needs, and time frames.

Research Tasks:
1  Meet with the project's technical panel to review the project's scope and work plan.
2  Review and summarize literature, including other state's experiences, pertinent to accident reporting procedures, American National Standards (ANSI) D16.1, SAFETYNET, Fatal Analysis Reporting System (FARS), and the Model Minimum Uniform Crash Criteri
3  Conduct workshops with the technical panel, affected agencies, local governments and other stakeholders: a) to understand current processes, forms, and data; b) to define the high level functional requirements; and c) identify candidate improvement o
4  Provide a technical memorandum and meet with the technical panel to review and approve the workshop findings.
5  Develop detailed business requirements, data elements, processes, definitions and relationships for the approved candidate improvement.
6  Provide a technical memorandum and meet with the technical panel to approve the information developed in Task 5.
7  Define a logical data architecture for the proposed accident reporting system.
8  Meet with the technical panel to review and approve the proposed data architecture.
9  Develop and recommend a migration plan for designing and building the approved accident reporting form and system including costs, resource requirements, phasing, training needs, and time frames.
10  Submit a final report and executive summary including findings, methods, conclusions, functional requirements, and recommendations. Deliverables will include an entity relationship diagram (as-is), process model (as-is), and detailed Entity Interacti
11  Make an executive presentation to the technical panel and the Research Review Board at the conclusion of the project.

Documents Available:
SD2000_14_Final_report.pdf
blank space