Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J3197: Engineering the Future of Automated Driving Data Logging
This SAE recommended practice establishes uniform specifications for data loggers in vehicles equipped with Automated Driving Systems (ADS). By defining event types, data capture triggers, and a minimum set of data elements, J3197 enables consistent event analysis and system evaluation across the industry. Let’s dive into the key aspects of this standard.
Event Definitions and Time Zero
The standard defines three categories of events that must be captured: front/side/rear impact, pedestrian impact, and rollover. Each event has a clearly defined beginning (Time Zero), end, and duration, ensuring that data recording is triggered consistently regardless of vehicle platform.
| Event Type | Beginning of Event (Time Zero) | End of Event | Duration |
|---|---|---|---|
| Front/Side/Rear Impact | First contact between vehicle and object | When no contact remains | From Time Zero to end of contact |
| Pedestrian Impact | First contact with pedestrian | When contact is lost | From Time Zero to loss of contact |
| Rollover Event | Roll angle exceeds a specified threshold (e.g., 0° relative to road plane) | When roll angle returns below threshold | From Time Zero until stabilisation |
Engineering Insight: Clear Time Zero definitions are critical for deterministic event analysis. This standard eliminates ambiguity by providing a fixed reference point for each event type, enabling objective post-event reconstruction.
Data Capture Triggers and Record Management
The logger can be triggered by event-based situations (e.g., impact or rollover) or by system states such as ADS activation. The standard recommends that data records include both pre- and post-trigger data to fully contextualise the event. Additionally, records must be time-aligned across all sensors and control units, with clear handling of unavailable or invalid signals using defined exception codes.
⚠️ Important: Data time alignment is not optional. All logged data should reference a synchronized clock to avoid temporal mismatches that can lead to incorrect conclusions.
The standard also specifies requirements for annotated images, which must include salient objects, the relevant field of view, and the operational design domain (ODD) context at the time of the event.
Minimum Data Elements and Best Practices
J3197 defines a minimum set of data elements that every ADS data logger must capture. These include:
- ADS Action – requested braking, steering, gear, etc.
- ADS Mode – indicates whether the system is active or not.
- ADS Reference Vehicle Speed – especially during automated operation.
- Annotated Image – visual record with metadata.
- Data Record Trigger Type – how the recording was initiated.
- Environmental Input – e.g., location, heading, emergency vehicle flag.
- Passenger-Initiated Emergency Stop (if equipped) – records passenger override attempts.
- Request to Intervene – logs when the ADS issues a takeover request.
These elements are split into mandatory and optional categories, balancing standardisation with manufacturer flexibility. The standard also requires that data element accuracy be defined to ensure reliability of logged data.
🛠️ Best Practice: Always log both requested and actual vehicle motion control to enable a direct comparison between ADS intent and system response during analysis.
Frequently Asked Questions (FAQ)
What events can trigger the ADS data logger?
The logger triggers automatically upon detection of a front/side/rear impact, pedestrian impact, rollover, or when the ADS enters certain modes (e.g., activated or deactivated).
What are the mandatory data elements that must be recorded?
Mandatory elements include ADS Action (e.g., requested lateral/longitudinal control), ADS Mode, ADS Reference Speed, Annotated Image, Data Record Trigger Type, Time Stamp, and Vehicle Indicated Status, among others. A complete list is in Section 7 of the standard.
How does the standard handle data unavailability or invalidity?
Data elements that are unavailable or invalid must be explicitly marked using the “Not Available” or “Invalid” exception codes defined in Section 6.6. This prevents misleading interpretations of missing data.
Why is time alignment critical for ADS data loggers?
Without synchronized timestamps across sensors, ECUs, and the logger, it becomes impossible to correlate events accurately. The standard mandates that all data streams be aligned to a common time reference to support reliable event reconstruction.
