MétaCan
Menu
Back to cohort
Record W2134545418 · doi:10.1061/9780784413517.163

Analyzing Scaffolding Needs for Industrial Construction Sites Using Historical Data

2014· article· en· W2134545418 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 2014 · 2014
Typearticle
Languageen
FieldEngineering
TopicConstruction Engineering and Safety
Canadian institutionsCanadian Natural ResourcesPCL Construction (Canada)University of Alberta
Fundersnot available
KeywordsScaffoldWork (physics)Computer scienceOil refineryEstimationTransport engineeringEngineeringSystems engineeringDatabaseMechanical engineering

Abstract

fetched live from OpenAlex

Industrial construction includes a wide range of construction projects, such as petroleum refineries and chemical plants. These involve several trades, such as civil, mechanical, and electrical. Different trades carry out different tasks on these projects, and often depend on scaffolds to access their work areas. Quantification of scaffold requirements of large projects is difficult because of variability in work area heights and congestion and the multiple trades that need to be serviced by the scaffold system. Traditional estimating methods rely on percentages of direct trade hours or volume of work area and usually result in significant deviation from real scaffold costs. The study presented in this paper aims to develop better understanding and estimates of scaffold needs for industrial construction sites, based on analysis of data collected from a mega-project over the course of two and a half years by a major contractor. The study seeks to discover patterns and reliable correlations that may exist between required scaffold hours and other work attributes that can allow for development of a reliable estimation model. The paper presents the results of initial analysis and exploration of data mining experiments, in addition to the challenges faced and future research recommendations.

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 categoriesMeta-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.755
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.001
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.001
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.156
GPT teacher head0.339
Teacher spread0.184 · 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