This recommended practice aims to establish a common output format of crash-related data recorded and stored within certain electronic components currently installed in many light-duty vehicles. This document pertains only to the post-download format of such data and is not intended to standardize the format of the data stored within any on-board storage unit, or to standardize the method of data recording, storing, or extraction.

Historically, crash data recording technology in light-duty vehicles has developed and evolved based on differing technical needs of manufacturers and their customers without industry standards or government regulation. As a result, wide variations currently exist among vehicle manufacturers regarding the scope and extent of recorded data. This document is intended to be a compilation of data elements that various manufacturers are currently recording, as well as those elements reasonably predicted to be recorded in the foreseeable future, and establishes a common output format of those data elements.

The scope of this document is deliberately restricted to providing output data formatting guidelines, only. It is not intended to standardize or mandate the recording of any specific data elements or to specify a minimum data set. This restriction in the scope is to avoid imposing constraints on the type of data recorded, the method of gathering and storing data, and the pre-and/or post-processing of data that may be used by various vehicle/device manufacturers as a matter of proprietary design. The committee recognized that, given the lack of societal consensus regarding the acceptability of on-board data recording devices, and has therefore avoided specific recommendations concerning whether event data recorders should be equipped on motor vehicles, and whether, when implemented, a particular type, quantity, and manner of data collection should be used.

Readers of this series of documents are advised to examine the validity and accuracy of VEDI event data in conjunction with the results from the traditional accident reconstruction practice. Since VEDI event data are acquired only from the on-board electronics systems, they may have not accurately capture the actual dynamics of the vehicle during the accident, or may not contain the full range or length of data during the event.

This document is one of a multi-volume J1698 series of documents and provides general concepts and common definitions of event data recording. J1698-1 provides definitions of event data and J1698-2 provides data extraction protocols.

Purpose

Vehicular event data recording and extraction has several potential uses. These include diagnostic and operational information of the on-board occupant protection system, crash reconstruction, improved highway safety, and support of crash notification systems. A standard format for vehicle event data outputs will help facilitate these uses by improving the efficient use of the extracted data.

Collection of various types of data for a variety of commercial and non-commercial uses is of significant interest to many entities. The Committee passes no judgment on the appropriateness of any particular use of recorded data, but has recognized in the statement of purpose for this document those uses of recorded data that best serve the public interest, namely, the use of data to enhance the knowledge of those tasked with designing vehicles and roadways and with shaping traffic safety policy. Other uses of recorded data are beyond the scope and purpose of this Document.

Rationale

Need new rationale statement.

Customers who purchased SAE J1698
also purchased

• IEEE 1616A : Motor Vehicle Event Data Recorders (MVEDRs) Amendment 1: MVEDR Connector Lockout Apparatus (MVEDRCLA)

See More Documents