MétaCan
Menu
Back to cohort

Differentiation of Evaluation Criteria in Design-Build and Construction Manager at Risk Procurements

2019· article· en· W2958346082 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Management in Engineering · 2019
Typearticle
Languageen
FieldDecision Sciences
TopicConstruction Project Management and Performance
Canadian institutionsnot available
Fundersnot available
KeywordsProcurementSample (material)Selection (genetic algorithm)BusinessOperations managementValue (mathematics)MarketingComputer scienceEconomicsStatisticsMathematics

Abstract

fetched live from OpenAlex

The procurement processes used in the alternative contracting methods of design-build (DB) and construction manager at risk (CMAR) are heavily focused on best-value and qualifications-based selection. However, previous research has not examined the effectiveness of owners' evaluation criteria in differentiating among competing bidders. The objective of this study was to document the selection outcomes of the bidders in DB and CMAR projects and identify which evaluation criteria had the greatest differentiation in scores for competing bidders. The results were compared with previous research on the procurement of architectural and engineering consultants and design-bid-build (DBB) contractors. The study sample consisted of 362 bidders for 63 DB and CMAR projects in the United States and Canada. The statistical analysis results showed that scores on interviews and technical proposals had the greatest differentiation, while cost proposal scores had minimal differentiation. These findings provide practical guidance for owners and bidders regarding how to prioritize evaluation criteria and how to respond to them.

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.004
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: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.200
Threshold uncertainty score0.351

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.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.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.043
GPT teacher head0.323
Teacher spread0.280 · 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