MétaCan
Menu
Back to cohort

Life-Cycle Cost Analysis Framework to Support Data Procurement Strategies for Infrastructure Assets

2020· article· en· W3117738059 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.

Bibliographic record

VenueJournal of Infrastructure Systems · 2020
Typearticle
Languageen
FieldEconomics, Econometrics and Finance
TopicHousing Market and Economics
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsProcurementOutsourcingData collectionVendorCost estimateDecision support systemComputer scienceAgency (philosophy)Operations researchRisk analysis (engineering)Process managementBusinessEngineeringSystems engineeringMarketingData mining

Abstract

fetched live from OpenAlex

The collection of infrastructure performance data is critical for agencies to cost-effectively maintain and preserve their existing assets. This paper presents a decision-support tool developed to support a state planning agency seeking to select a cost-effective data procurement strategy; specifically, the agency is considering whether to continue collecting and processing infrastructure performance data in-house or outsource to a third-party vendor. The probabilistic tool integrates uncertainty estimation via statistical methods and elicitation of expert judgement with Monte Carlo simulations to compute the probabilistic life-cycle cost of alternative data procurement strategies. For this particular case study, the expected cost to continue data collection and processing activities in-house is higher than the cost to outsource such activities. More importantly, the case study results lead to other important insights and contributions that are more generalizable to other contexts. For example, the labor resources required to collect, process, and maintain infrastructure condition data is the largest driver of total life-cycle costs for in-house data collection. Furthermore, because the decision to outsource data collection is made well before an agency selects a vendor, and such cost estimates are frequently unknown, there is a higher level of uncertainty and potential risk associated with outsourcing these activities. These conclusions, as well as the methods and framework presented in this paper, should assist planning agencies as they develop their data procurement strategy.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.839
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.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0010.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.051
GPT teacher head0.277
Teacher spread0.227 · 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