MétaCan
Menu
Back to cohort
Record W4399550361 · doi:10.1061/jcemd4.coeng-14821

Mitigating Project Schedule Risks by Identifying Subcritical Paths and Variance-Critical Activities

2024· article· en· W4399550361 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

VenueJournal of Construction Engineering and Management · 2024
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsUniversity of AlbertaGovernment of Alberta
Fundersnot available
KeywordsScheduleVariance (accounting)Critical path methodComputer scienceRisk analysis (engineering)Operations researchEnvironmental scienceEngineeringBusinessSystems engineeringAccounting

Abstract

fetched live from OpenAlex

Significant risks in project completion delay could be buried in the development of project schedules because of theoretical flaws in project schedule risk analysis. Major project delays hamper infrastructure development endeavors and cause negative consequences to project finance, the public interest, and socioeconomic growth. This research critically reviews the theoretical foundation of the Program Evaluation and Review Technique (PERT) and identifies two major flaws: (1) failing to account for variances of activities on subcritical paths; and (2) lacking the functionality of characterizing variance-criticality for activities in a project network. Further, the path variance-criticality index and the activity variance-criticality index are formalized for defining the subcritical path(s) and identifying the variance-critical activities. Reducing time duration variances in the identified variance-critical activities exerts a significant impact on mitigating project schedule delay risks. A case study is given to illustrate the analytical steps for identifying variance-critical activities in a project. Monte Carlo simulations were conducted to validate the effectiveness of the proposed analytical approach. The enhanced PERT for project schedule risk analysis is instrumental in (1) identifying critical and subcritical paths in the project network model; (2) clarifying the notion of variance-criticality for prioritization of activities based on the impact of activity time variance on project time variance; and (3) reining in project schedule risks by reducing time duration variances on those variance-critical activities in project planning.

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.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.714
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0010.001
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.058
GPT teacher head0.371
Teacher spread0.312 · 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