MétaCan
Menu
Back to cohort
Record W2310024467 · doi:10.1139/cjce-2014-0500

Prediction of maintenance cost for road construction equipment: a case study

2016· article· en· W2310024467 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.
fundA Canadian funder is recorded on the work.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2016
Typearticle
Languageen
FieldHealth Professions
TopicQuality and Safety in Healthcare
Canadian institutionsCanadian Natural Resources
FundersNatural Sciences and Engineering Research Council of CanadaMcGill University
KeywordsData collectionPredictive maintenanceCost estimateCost databaseReliability engineeringEngineeringPreventive maintenanceComputer scienceRegression analysisWork (physics)Operations researchSystems engineeringStatisticsDatabaseMachine learning

Abstract

fetched live from OpenAlex

Equipment maintenance cost is significant in construction operations budgets. This study proposes a systematic approach to predict maintenance cost of road construction equipment. First, maintenance cost data over more than 10 years was collected from a partner company’s equipment management information system. Data was cleaned and analyzed to obtain a general understanding of maintenance costs trends. Next, traditional cumulative cost models and alternative data mining models were generated to predict maintenance cost based on available equipment and operation attributes. Data mining models were evaluated and validated using portions of the collected data that have not been used in model development. Data collection, analyses, modeling, and validation steps are discussed. The paper also presents the performance of different model types. Based on the case study data, regression model trees performed better than other model types with equipment work hours being the most significant parameter for predicting maintenance cost.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.415
Threshold uncertainty score0.830

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.087
GPT teacher head0.353
Teacher spread0.266 · 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