MétaCan
Menu
Back to cohort
Record W566223240

Evaluating the use of Subsurface Utility Engineering in Canada

2007· article· en· W566223240 on OpenAlex
Hesham Osman, Tamer E. El-Diraby

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

VenueTransportation Research Board 86th Annual MeetingTransportation Research Board · 2007
Typearticle
Languageen
FieldEngineering
TopicUnderground infrastructure and sustainability
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsLiberian dollarReturn on investmentInvestment (military)DepictionScale (ratio)BusinessEngineeringEconomicsFinanceOperations managementGeographyPolitical scienceLawCartography
DOInot available

Abstract

fetched live from OpenAlex

The market for Subsurface Utility Engineering (SUE) in Canada is slowly following its U.S. counterpart. In Ontario, the market for SUE has seen rapid growth especially on large-scale municipal projects. This paper presents the results of a 12-month study that investigated the challenges and opportunities facing SUE in Ontario. The study took an in-depth look at 9 large municipal and highway reconstruction projects that utilized SUE to provide an enhanced depiction of buried utilities. Based on this analysis, a cost model for SUE utilization was proposed that takes into account both tangible and intangible benefits. This model was applied to gauge the expected cost savings due to SUE utilization on these 9 projects. All projects showed a positive return-on-investment (ROI) that ranged from $2.05 to $6.59 for every dollar spent on SUE. Although these ROI figures should not be considered universal, they indicate that with careful scoping of SUE services, project risks can be appropriately reduced at reasonable cost. The paper concludes with a set of lessons learned by various project participants from the SUE experience in Ontario.

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.011
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: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.415
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0110.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.003
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.002
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.091
GPT teacher head0.367
Teacher spread0.276 · 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