MétaCan
Menu
Back to cohort

Improving Concurrency Assessment and Resolving Misconceptions about But-For Delay Analysis Technique

2020· article· en· W3005950680 on OpenAlexaff
Moneer Bhih, Tarek Hegazy

Bibliographic record

VenueJournal of Legal Affairs and Dispute Resolution in Engineering and Construction · 2020
Typearticle
Languageen
FieldComputer Science
TopicNetwork Traffic and Congestion Control
Canadian institutionsUniversity of Waterloo
Fundersnot available
KeywordsConcurrencyComputer scienceReliability engineeringProgramming languageEngineering

Abstract

fetched live from OpenAlex

But-for delay analysis is a popular technique used in practice and accepted by arbitration boards and courts. However, misconceptions are common when the analysis results are interpreted from different parties’ viewpoints. In addition, the adoption of either the literal or functional views on concurrent delays affects the results. This paper thus clarifies the misleading interpretations of but-for results and introduces improvements and an explicit implementation procedure that matches the delay analysis requirements of professional bodies such as the Association for the Advancement of Cost Engineering International (AACEI). To more accurately perform but-for analysis considering all parties’ viewpoints, the paper uses Venn representation and suggests a simplified procedure to check for true concurrency. A case study was used to show a detailed procedure for applying but-for with multiple analysis windows as a more accurate approach to assess concurrent delays and to consider baseline updates. The applicability of the proposed improvements was then confirmed using a second practical case study. The paper is expected to remove the existing but-for misconception and provide a procedure for more accurate and repeatable delay analysis considering concurrent delays.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.030
metaresearch head score (Gemma)0.111
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.030
Threshold uncertainty score0.156

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0300.111
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0040.002
Science and technology studies0.0020.003
Scholarly communication0.0080.013
Open science0.0040.004
Research integrity0.0010.004
Insufficient payload (model declined to judge)0.0050.001

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.006
GPT teacher head0.222
Teacher spread0.215 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations12
Published2020
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Legal Affairs and Dispute Resolution in Engineering and ConstructionSame topicNetwork Traffic and Congestion ControlFrench-language works237,207