MétaCan
Menu
Back to cohort
Record W2070599978 · doi:10.1108/13552511111134619

Reliability and availability analysis of a robot‐safety system

2011· article· en· W2070599978 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 Quality in Maintenance Engineering · 2011
Typearticle
Languageen
FieldEngineering
TopicReliability and Maintenance Optimization
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsBackupReliability engineeringRobotReliability (semiconductor)Process (computing)EngineeringSystem safetyMarkov processMean time between failuresMarkov chainMarkov modelComputer scienceSimulationFailure rateArtificial intelligence

Abstract

fetched live from OpenAlex

Purpose The purpose of this paper is to study reliability, availability, and mean time to failure of a repairable robot‐safety system composed of n robots, m safety units, and a perfect switch. Design/methodology/approach Generalized expressions for system state probabilities, system availability, reliability, and mean time to failure are developed. Supplementary variable and Markov methods were used to develop these expressions. Findings This study clearly demonstrates that backup robots, safety units, and the repair process help to improve system availability. Practical implications This study will help maintenance engineers and reliability practitioners to become aware of the combined effect of backup robots, safety units, and the repair process on the performance of the robot‐safety system. Consequently, they will make better maintenance related decisions in organizations that make use of robots. Originality/value This paper has studied the effects of having redundant robots, safety units, and the repair facilities on the performance of a robot‐safety system with perfect mechanism to turn on a safety unit. This is one of the first attempts to study the combined effects of all these factors on a robot‐safety system.

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.004
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.423
Threshold uncertainty score0.691

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
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.016
GPT teacher head0.227
Teacher spread0.210 · 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