MétaCan
Menu
Back to cohort
Record W2397726616 · doi:10.1061/9780784479827.004

Design Change Time Ripple Effect Analysis Using a BIM-Based Quantification Model

2016· article· en· W2397726616 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

VenueConstruction Research Congress 2016 · 2016
Typearticle
Languageen
FieldEngineering
TopicBIM and Construction Integration
Canadian institutionsConcordia University
Fundersnot available
KeywordsScheduleScope (computer science)Computer scienceRippleRisk analysis (engineering)Plan (archaeology)Work (physics)Project managementFrame (networking)Operations researchSystems engineeringBusinessEngineering

Abstract

fetched live from OpenAlex

Changes arising from the addition, deletion, and/or modification of a project’s design frequently cause delays. Such changes may take many forms; however, owner-acknowledged change should receive more attention than other types of change, as it might present a risk to both owners and contractors. These changes, both individually and collectively, can have a ripple effect on what appears to be the unchanged scope of a project’s work plan, with varying impacts on project schedule. The efficient management of design changes requires a minimization of the time impacts of these changes. This paper presents a building information modeling (BIM)-based quantification model, developed to help design professionals quantify the ripple effect of contemplated design changes requested by owners after the completion of the design phase and before the commencement of construction. The developed model calculates the impact of changes on a project’s time frame. After analyzing the ripple effect of time, the model updates the project schedule accordingly. The developed model is expected to help owners and their agents make better decisions about approving or rejecting contemplated changes. The model has been applied to a case project to demonstrate its use and to illustrate its essential features.

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.000
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: none
Teacher disagreement score0.908
Threshold uncertainty score0.741

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.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.104
GPT teacher head0.335
Teacher spread0.231 · 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