MétaCan
Menu
Back to cohort
Record W4238610103 · doi:10.1177/0361198105190700102

Computerized System for Efficient Scheduling of Highway Construction

2005· article· en· W4238610103 on OpenAlex

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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueTransportation Research Record Journal of the Transportation Research Board · 2005
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsScheduling (production processes)ScheduleFlexibility (engineering)Computer scienceCrewOperations researchConstruction managementIndustrial engineeringEngineeringOperations management

Abstract

fetched live from OpenAlex

A practical model for scheduling and cost optimization of highway construction is presented in this paper. The model's objective is to minimize total construction cost while respecting the time and resource constraints of a project. For flexibility, the model allows each activity to have three alternative construction methods, from cheap and slow to fast and expensive. At the core of the model is an innovative scheduling algorithm for crew assignments along the various highway sections so that work continuity is maintained. The model is designed to be flexible enough to allow nontypical sections as well as variable sequence of work among the sections. For cost optimization, the model uses a nontraditional optimization technique, genetic algorithms. Details of the model formulation are presented in this paper along with its implementation in a simple-to-use computer system. To demonstrate the capabilities of the system, a realistic example is given of a highway project that is fast-tracked by using two crews working simultaneously from opposite sides. The example shows the usefulness of the system for what-if analysis, schedule optimization, and legible presentation of detailed crew assignments and activities’ progress speeds. Extensions of the model to incorporate project control features are then highlighted.

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 imitation

Not 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.

metaresearch head score (Codex)0.024
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.458
Threshold uncertainty score0.827

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0240.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.004
Science and technology studies0.0010.001
Scholarly communication0.0000.001
Open science0.0020.000
Research integrity0.0000.002
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.182
GPT teacher head0.440
Teacher spread0.258 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it