MétaCan
Menu
Back to cohort
Record W2105356973 · doi:10.1139/cjce-2012-0531

Factor analysis of the interface management (IM) problems for construction projects in Alberta

2013· article· en· W2105356973 on OpenAlex
Nesreen Weshah, Wael El Ghandour, George Jergeas, Lynne Cowe Falls

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.
venuePublished in a venue whose home country is Canada.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2013
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsInnovative Targeting Solutions (Canada)University of Calgary
Fundersnot available
KeywordsInterface (matter)Construction managementBiddingProject managementWork (physics)Construction industryEngineeringComputer scienceConstruction engineeringEngineering managementOperations managementCivil engineeringBusinessSystems engineeringMarketing

Abstract

fetched live from OpenAlex

Interface management (IM) is one of the major keys for construction project success. The severity of interface problems for different projects does not only delay the project, but also impacts overall project performance. This paper is an extension of a previous work that defined major IM problems in Alberta’s construction projects. This research study intended to investigate, identify, and classify interface problem factors in Alberta’s construction projects. The study included four stages. The first stage was a comprehensive literature review, pilot studies and face-to-face interviews in industry. In the second phase, a web-page questionnaire was conducted with participants from industry. Based on that, in the last two phases, a factor analysis and Pearson’s correlation matrix were applied on the collected data. The study identified six IM factors, namely: “management”, “information, bidding and contracting”, “by-law and regulation”, “technical engineering and site issues”, and “other interface problems”. Finally, correlation between IM factors and different construction data was tested. The data analysis results provided a comprehensive view of the main causes behind IM conflicts in Alberta’s construction industry.

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: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.249
Threshold uncertainty score0.769

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.032
GPT teacher head0.269
Teacher spread0.237 · 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