MétaCan
Menu
Back to cohort
Record W2336675174 · doi:10.1177/1748006x16631202

Reliability estimation considering usage rate profile and warranty claims

2016· article· en· W2336675174 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

VenueProceedings of the Institution of Mechanical Engineers Part O Journal of Risk and Reliability · 2016
Typearticle
Languageen
FieldEngineering
TopicReliability and Maintenance Optimization
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsWarrantyReliability (semiconductor)Reliability engineeringFailure rateComputer sciencePopulationField (mathematics)EstimationTask (project management)EngineeringMathematics

Abstract

fetched live from OpenAlex

Providing more realistic reliability prediction based on small proportion of failed population or test data has always been a challenging task. Manufacturers rely heavily on reliability prediction for designing warranty plan. Furthermore, to predict warranty claims for the remaining warranty period, it is important to have more realistic reliability assessment by considering a larger proportion of the population or the maximum possible information on the remaining population. However, generally this information is not readily available and is very difficult to gather on the scattered population. In this work, we propose to use customer usage rate profile to generate censored usage data on the remaining population that do not have any failure and warranty claims yet. We intend to use field data available such as warranty claims, field failures, recall data, and maintenance data to develop usage rate profile and subsequently estimate censored usage time. Finally, reliability estimation methodology is developed considering both censored data and field failure data to provide more reasonable reliability prediction for the remaining warranty period. The proposed methodology is demonstrated considering real-life data from a big manufacturing company.

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.002
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.234
Threshold uncertainty score0.387

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
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.006
GPT teacher head0.196
Teacher spread0.190 · 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