Utility Coordination in Alternative Delivery Methods for Transportation Projects: Utility Responsibility Matrix and Design Development—Lessons Learned from Detailed Design Process and Construction
Bibliographic record
Abstract
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.020 | 0.025 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.004 | 0.008 |
| Scholarly communication | 0.011 | 0.009 |
| Open science | 0.003 | 0.005 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.005 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".