Design of an ITS-Level advanced traffic management system: a human factors perspective
archive: archived pipeline: cataloged verified
Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)
Summary
This report documents a user-centered, top-down system analysis conducted to design an Advanced Traffic Management System (ATMS) from a human factors perspective. The research was motivated by the rapid integration of advanced information and communication technologies into Intelligent Transportation Systems (ITS), which threatened to create excessive workloads and increase system-induced errors for Traffic Management Center (TMC) operators if not properly addressed. The study aimed to define system objectives, functionality, and operator roles to ensure that new technologies harmonized with human capabilities and limitations. The methodology involved a multi-step analysis beginning with interviews of "ITS visionaries" to define unconstrained operational capabilities and functional requirements for an ideal ATMS. These initial definitions were subsequently revised for realism through a comparative analysis of approximately two dozen existing control centers in North America and Europe. The researchers then performed function allocation, assigning each of 113 identified ATMS functions to one of four operator roles: Direct Performer (fully manual), Manual Controller, Supervisory Controller, or Executive Controller (fully automated). This process was guided by Operator Role Theory and included detailed task analyses to specify performance requirements and workload constraints. The findings revealed that while automation would significantly increase in data input, fusion, and output activities, human operators would remain responsible for the most challenging interpretations, decisions, and actions. Of the 113 functions analyzed, 40 were allocated solely to human operators (Direct Performer), typically involving communication with external agencies or policy implementation. Only 29 functions were deemed suitable for full automation (Executive Controller), such as sensing vehicle locations or posting pre-formatted advisories. The remaining functions required partial automation, with significant operator involvement in response selection and processing stages. The study highlighted that partial automation did not necessarily reduce workload and that initial function allocations required empirical validation. The significance of this work lies in its provision of a structured framework for ATMS design that balances automation with human oversight. The results supported the preparation of human factors specifications for TMC configuration items and informed the development of a high-fidelity TMC simulator and a human factors handbook. The report concludes that successful ITS implementation requires careful consideration of operator roles to prevent usability problems and ensure that systems are trusted and effectively utilized by end users.
Key finding
Of the 113 ATMS functions analyzed, 40 were allocated solely to human operators as direct performers and 29 to fully automated executive controllers, with the remaining functions requiring mixed human-machine effort.
Methodology
mixed_methods
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. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | rosap | — | — | 2 | 2026-05-23 |
| archive | success | — | — | — | 1 | 2026-05-23 |
| extract | success | cached | — | — | 2 | 2026-06-10 |
| clean | success | — | — | — | 1 | 2026-06-01 |
| chunk | success | — | — | — | 1 | 2026-06-01 |
| embed | success | — | — | — | 1 | 2026-06-02 |
| enrich | success | — | — | — | 1 | 2026-05-23 |
| promote | success | — | — | — | 1 | 2026-05-23 |
| summarize | success | llm | qwen3.6-27b-prismaquant | summ-v5 | 3 | 2026-06-10 |
| tag | success | vector_similarity | — | — | 24 | 2026-06-11 |
| verify | success | — | — | — | 2 | 2026-06-10 |
Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; 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).
- Applied Guidance: design guidelines