Automated Bus Dispatching, Operations Control and Service Reliability: Analysis of Tri-Met Baseline Service Data
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 study establishes a baseline assessment of bus service reliability for Tri-Met, the Portland metropolitan transit agency, prior to the full implementation of a new computer-aided bus dispatch system (BDS) utilizing automatic vehicle location (AVL) technology. The research addresses the critical industry challenge of maintaining service reliability amidst increasing roadway congestion, which exacerbates issues like bus bunching and schedule deviations. The primary motivation is to quantify current performance levels to later evaluate the impact of automated operations control on reducing operating costs and improving passenger experience. The methodology involved a comprehensive field survey conducted over ten weekdays in November 1996. Researchers selected eight routes representing various typologies, including radial, through-routed, cross-town, and feeder services. Surveyors manually recorded arrival and departure times at route origins and destinations, yielding 3,910 arrival, 3,650 headway, and 3,152 run time observations. Additionally, an on-board rider survey collected 1,815 responses regarding perceived reliability and satisfaction. The study defined four specific reliability indicators: on-time performance (within a one-minute early to five-minute late window), headway ratio variability, run time ratio variability, and estimated excess passenger waiting time. Statistical models were also developed using Automatic Passenger Counter (APC) data for a subset of trips to identify determinants of delay. The results indicate that baseline service reliability was significantly lower than historical benchmarks, with only 61.7% of arrivals meeting the on-time standard, compared to 88% in 1991. Performance was poorest during the PM peak period (55.2% on-time), while evening service performed best (66.3%). Route 14 (Hawthorne) exhibited the highest headway variability, confirming severe bus bunching issues, whereas Routes 54 and 59 showed the lowest variability but poorest on-time performance. Run times consistently exceeded schedules, with an average delay of 1.5% overall and 5.4% during the PM peak. Notably, rider perceptions did not align with operational metrics; riders rated the most unreliable routes as having high reliability, likely conflating frequency with punctuality. The study estimated that the average excess waiting time due to irregularity was 1.68 minutes, rising to nearly three minutes during the PM peak. The significance of this report lies in its provision of a rigorous quantitative baseline against which the efficacy of the new BDS can be measured. The findings highlight that unreliability is concentrated in the PM peak and is driven by traffic congestion and operational inefficiencies. The authors estimate that a 10% reduction in excess waiting time could yield annual benefits of approximately $1.5 million to riders. By documenting these baseline conditions, the study enables future analysis of whether automated dispatching and active operations control can effectively mitigate bunching, reduce delays, and improve the overall cost-benefit profile of transit operations.
Key finding
Only 62% of bus arrivals met the on-time standard, with PM peak periods showing the worst performance and the 14 Hawthorne route exhibiting the highest headway variability due to bus bunching.
Methodology
naturalistic
Sample size: 3910
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.