MétaCan
Menu
Back to cohort
Record W2406074900 · doi:10.1061/9780784479827.062

A Stochastic Simulation Approach for the Integration of Risk and Uncertainty into Megaproject Cost and Schedule Estimates

2016· article· en· W2406074900 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueConstruction Research Congress 2016 · 2016
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsMegaprojectScheduleComputer scienceRisk analysis (engineering)Mathematical optimizationSystems engineeringEngineeringMathematicsBusiness

Abstract

fetched live from OpenAlex

During the estimation phase of megaprojects, many traits must be addressed and taken into account in order to obtain realistic results. Objectives, influential factors, and their interdependencies must be accurately identified and measured. As part of this process, it is crucial to determine the uncertainty around project objectives as well as risk events that may impact the project on various levels. This paper proposes a method of defining and incorporating the uncertainty and risk events around the two main objectives of any megaproject (i.e., cost and schedule). To serve this purpose, a stochastic event simulation model which operates based on Monte Carlo simulation and uses Microsoft Project and @Risk for Microsoft Excel as an integrated simulation platform has been developed. The goal of the proposed model is to incorporate uncertainty and risk into the project schedule and assess the variations of the model output with respect to the deterministic estimation of cost and schedule. The focus of this study is on megaprojects that incorporate both sequential construction activities as well as cyclical manufacturing activities. The project used to validate this approach is a nuclear plant Retube and Feeder Replacement (RFR) project in Ontario, Canada.

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.011
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
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.980
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0050.011
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0010.002
Scholarly communication0.0000.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.171
GPT teacher head0.450
Teacher spread0.279 · 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