MétaCan
Menu
Back to cohort
Record W2069867923 · doi:10.1139/l08-121

Delay analysis in resource-constrained schedules

2009· article· en· W2069867923 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2009
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsnot available
FundersKorea Institute of Construction and Transportation Technology Evaluation and PlanningKorea Institute of Construction Technology
KeywordsScheduleCritical path methodDuration (music)Computer scienceScheduling (production processes)Path (computing)Resource (disambiguation)Mathematical optimizationReduction (mathematics)Operations researchReliability engineeringEngineeringMathematicsComputer network

Abstract

fetched live from OpenAlex

The schedule for construction delay analysis should consider resources because it is acknowledged that a schedule without resources is not realistic. However, the conventional resource-constrained scheduling (RCS) technique is not properly operated for the widely accepted delay analysis techniques such as the contemporaneous period analysis (CPA) and the “but-for” method. The “CPM + RCS” method for rescheduling to analyze delay impacts may cause unexpected activity sequence changes and the “RCS-only” method does not reflect the time impact of the duration reduction of an activity and may cause substantial project completion delay by a minor change in the activity duration. This study analyzes the problems that arise when CPA and the “but-for” method are performed on the basis of the conventional RCS technique and shows how the resource-constrained critical path method can be utilized in those delay analyses that have advantages as compared with the RCS technique.

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.005
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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.517
Threshold uncertainty score0.958

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.005
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0060.004
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.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.030
GPT teacher head0.282
Teacher spread0.252 · 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