MétaCan
Menu
Back to cohort
Record W2147638424 · doi:10.5555/2693848.2694267

Bi-level project simulation methodology to integrate superintendent and project manager in decision making: shutdown/turnaround applications

2014· article· en· W2147638424 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 · 2014
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsCritical path methodShutdownTurnaround timeComputer scienceOperations researchDuration (music)CrewScheduling (production processes)Monte Carlo methodProject managementResource (disambiguation)Project managerDiscrete event simulationResource allocationProject planningWork (physics)Reliability engineeringIndustrial engineeringSystems engineeringEngineeringSimulationOperations management

Abstract

fetched live from OpenAlex

The critical path method (CPM) provides the standard approach to scheduling construction projects. Limited crew resources compound CPM analysis by imposing resource availability constraints. However, there is no generalized methodology yet to quantitatively determine the optimal quantities of resources to execute specific work packages based on CPM analysis. Furthermore, in project evaluation and review technique (PERT) simulation, the occurrence of uncertain events is represented by probability distributions for activity durations in an implicit fashion. In this paper, a bi-level project simulation methodology is proposed to (1) determine the optimal resource quantities and activity times for each work package and (2) estimate total project duration and man-hour budget at the upper level for project planning through Monte Carlo simulation, based on defining a limited quantity of likely scenarios for each work package. An industrial plant shutdown and turnaround project serves as case study to illustrate application of the proposed methodology.

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.005
metaresearch head score (Gemma)0.010
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.681
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.010
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0020.002
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0010.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.397
GPT teacher head0.495
Teacher spread0.098 · 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