MétaCan
Menu
Back to cohort
Record W4296579871 · doi:10.1139/cjce-2022-0029

Enhanced repetitive scheduling formulation for meeting deadlines and resource constraints in linear and scattered projects

2022· article· en· W4296579871 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.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2022
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsScheduling (production processes)Computer scienceLinear programmingScheduleCrewCritical path methodOperations researchMathematical optimizationDistributed computingIndustrial engineeringEngineeringSystems engineeringAlgorithmMathematics

Abstract

fetched live from OpenAlex

The majority of civil infrastructure projects involve activities that are repeated across a number of linear units (e.g., highway sections) or scattered units (e.g., multi-bridge rehabilitations). For these projects, Critical Path Method (CPM)/line-of-balance (LOB) repetitive scheduling combines the benefits of CPM and LOB analyses to maintain work continuity across units, yet assumes simple sequential unit order and results in schedule delays for practical projects with non-identical units, constrained resources, and (or) strict deadlines. To improve CPM/LOB scheduling, this paper introduces powerful and easy-to-use enhancements, including (1) designed interruptions to reduce time gaps; (2) efficient resource-constrained first-come first-serve crew assignment; (3) crew adjustment loop to meet deadlines; and (4) representation of flexible unit sequence. These simplified enhancements computationally produce schedules that respect deadlines, individual resource limits, and desired sequence among units. Example projects are then presented to prove that the proposed enhancements offer flexible scheduling features that can meet the strict constraints of infrastructure projects.

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.004
metaresearch head score (Gemma)0.006
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.036
Threshold uncertainty score0.773

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.006
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
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.042
GPT teacher head0.290
Teacher spread0.248 · 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