MétaCan
Menu
Back to cohort
Record W3188792054 · doi:10.1061/9780784483619.004

Utility Coordination in Alternative Delivery Methods for Transportation Projects: Utility Responsibility Matrix and Design Development—Lessons Learned from Detailed Design Process and Construction

2021· article· en· W3188792054 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenuePipelines 2021 · 2021
Typearticle
Languageen
FieldEngineering
TopicUnderground infrastructure and sustainability
Canadian institutionsIBI Group (Canada)
Fundersnot available
KeywordsStakeholderIntegrated project deliveryScheduleProject stakeholderProcess (computing)Process managementProject charterGeneral partnershipProject managementEngineering managementEngineeringProject management triangleRisk analysis (engineering)BusinessComputer scienceSystems engineeringFinanceEconomicsManagement

Abstract

fetched live from OpenAlex

Stakeholder involvement in large linear infrastructure projects under public–private partnership (P3) usually is one of the main risk contributors in terms of cost overruns and schedule slippages. Utilities are not the exception, and their involvement from the early stages of the project is crucial for the project success. In order to clearly setting rules, a utility responsibility matrix should be conceived since the planning stages of these P3 projects, even before project award. The responsibility matrix not only determines who does what in terms of design but also during construction. Some utility agencies are more conservative and prefer to have both the design and construction done by the Utility Agency or its contractors, while others are open to transfer that risk to the Project Co. There are other cases, in between these two, where the Utilities provide a list of their preferred or approved contractors and consultants, being managed by the Project Co. Construction or Design Joint Venture. However, the fact of having the rules set often creates other challenges that affect the design process and hence impacting the overall schedule, adding more complexities on the Utility Coordination task. This paper will explore and explain these complexities in detail based on a large Light Rail Train Project in Canada and will seek for opportunities to improve this process, sometimes overlooked by the stakeholders involved [Utility Companies, Project Owner/Technical Advisor, Project Co. (Construction and Designer Joint Venture), Approved Sub Consultants, among others].

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.898
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
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.059
GPT teacher head0.345
Teacher spread0.286 · 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