The Planners’ Perspective on Train Timetable Errors in Sweden
Why this work is in the frame
A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.
Bibliographic record
Abstract
Timetables are important for train punctuality. However, relatively little attention has been paid to the people who plan the timetables: the research has instead been more centred on how to improve timetables through simulation, optimisation, and data analysis techniques. In this study, we present an overview of the state of practice and the state of the art in timetable planning by studying the research literature and railway management documents from several European countries. We have also conducted interviews with timetable planners in Southern Sweden, focusing on how timetable planning relates to punctuality problems. An important backdrop for this is a large project currently underway at the Swedish Transport Administration, modernizing the timetable planning tools and processes. This study is intended to help establish a baseline for the future evaluation of this modernization by documenting the current process and issues, as well as some of the research that has influenced the development and specifications of the new tools and processes. Based on the interviews, we found that errors in timetables commonly lead to infeasible timetables, which necessitate intervention by traffic control, and to delays occurring, increasing, and spreading. We found that the timetable planners struggle to create a timetable and that they have neither the time nor the tools required to ensure that the timetable maintains a high quality and level of robustness. The errors we identified are (a) crossing train paths at stations, (b) wrong track allocation of trains at stations, especially for long trains, (c) insufficient dwell and meet times at stations, and (d) insufficient headways leading to delays spreading. We have identified eleven reasons for these errors and found three themes among these reasons: (1) “missing tools and support,” (2) “role conflict,” and (3) “single-loop learning.” As the new tools and processes are rolled out, the situation is expected to improve with regard to the first of these themes. The second theme of role conflict occurs when planners must strive to meet the demands of the train operating companies, while they must also be unbiased and create a timetable that has a high overall quality. While this role conflict will remain in the future, the new tools can perhaps help address the third theme by elevating the planners from first- to double-loop learning and thereby allowing them to focus on quality control and on finding better rules and heuristics. Over time, this will lead to improved timetable robustness and train punctuality.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it