A critique of the SAE conditional driving automation definition, and analyses of options for improvement
DOI: 10.1007/s10111-018-0471-5
archive: archived pipeline: cataloged verified
Get this paper ↗ (DOI — opens at the source; we link to it, we don't host it)
Summary
This paper critiques the Society of Automotive Engineers’ (SAE) definition of Level 3 (LoDA 3) “conditional driving automation,” arguing that the current standard is incomplete and technically unsound. LoDA 3 requires automation to perform the complete dynamic driving task (DDT) within a limited operational domain but mandates that the driver intervene upon a request to intervene (RTI). The authors contend that this definition fails to account for scenarios where drivers fail to respond or are unable to take over safely, leaving a gap in the hierarchy of automation levels. To analyze this problem, the authors apply the generic “levels of automation” (LoA) framework, originally developed for human-machine systems, to design RTI messages. They evaluate four RTI design alternatives based on LoA levels: a Baseline (simple command to intervene), LoA 5 (automation disengages only after confirming driver takeover), LoA 6 (driver can veto the request, prompting automation to handle fallback), and LoA 6.5 (automation disengages immediately after warning). Using an expected utility model that weighs the benefits of successful driver takeover against the costs of uncontrolled vehicle states, the authors derive an optimal design. They also examine the impact of automatic safety controls, such as partial braking, during the transition period. The analysis reveals that the Baseline RTI is suboptimal. The optimal design corresponds to LoA 5, where the automation continues to operate the vehicle if the driver fails to respond, thereby avoiding a state where neither party controls the car. However, this optimal design contradicts the SAE definition of LoDA 3, which stipulates that the automation does not perform DDT fallback. The authors demonstrate that an RTI coupled with LoA 5 functionality effectively creates a new automation level that sits between LoDA 3 and LoDA 4. They conclude that the SAE list of automation levels is missing this intermediate category. To resolve this, the paper proposes two solutions: either insert the “High Automation” definition from the previous SAE standard (which allows automated fallback) between LoDA 3 and LoDA 4, or revise the LoDA 3 definition to permit automated fallback when the driver fails to respond. Without such changes, LoDA 3 remains an unrealistic target for development.
Provenance
The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed.
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | OpenAlex-citations | — | — | 1 | 2026-06-18 |
| archive | success | unpaywall | — | — | 2 | 2026-06-25 |
| extract | success | cached | — | — | 2 | 2026-06-26 |
| clean | success | clean | — | — | 1 | 2026-06-18 |
| chunk | success | chunk | — | — | 1 | 2026-06-18 |
| embed | success | embed | Qwen/Qwen3-Embedding-8B | — | 1 | 2026-06-18 |
| promote | success | — | — | — | 1 | 2026-06-18 |
| summarize | success | llm | qwen3.6-27b-prismaquant | summ-v5 | 1 | 2026-06-26 |
| tag | success | vector_similarity | — | — | 6 | 2026-06-18 |
| verify | success | — | — | — | 1 | 2026-06-26 |
Summary generated by qwen3.6-27b-prismaquant on 2026-06-26; verification: verified.
Topics
Ranked by relevance to this paper. Hover a topic for its definition.
Information type
What kind of knowledge this paper contributes, grouped by family — independent of topic (what it is about) and method (how it was studied).
- Theoretical Contribution: conceptual framework