MétaCan
Menu
Back to cohort
Record W2070375064 · doi:10.5555/2431518.2431929

Scheduling simulation-based techniques for earned value management on resource-constrained schedules under delayed scenarios

2011· article· en· W2070375064 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

VenueWinter Simulation Conference · 2011
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsComputer scienceScheduleEarned value managementScheduling (production processes)Project managementDynamic priority schedulingDiscrete event simulationOperations researchReal-time computingDistributed computingProject planningSystems engineeringSimulationOperations managementEngineering

Abstract

fetched live from OpenAlex

Earned value management (EVM) is widely utilized for project progress monitoring and cost control purposes. However, traditional EVM techniques are intended for ideal scheduling scenarios without considering the effect of activity-level and project-level delays. The EVM fails to account for dynamic changes of project status in terms of project time extension and associated cost overrun, potentially generating misleading project performance tracking indicators. This research proposes a refined EVM approach based on discrete event simulation (scheduling simulation) to tackle complicated resource-constrained scheduling. A case study is used to demonstrate its applications on a resource-constrained schedule under postulated delay scenarios. It is found that this approach is conducive to truthfully reflecting the project performance status given a resource-constrained schedule subject to complicated activity-project delay. Conclusions are drawn by recapitulating the research contributions and addressing the limitations in the end.

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.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.885
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
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.0010.000
Research integrity0.0000.000
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.174
GPT teacher head0.380
Teacher spread0.207 · 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