MétaCan
Menu
Back to cohort
Record W2140684998 · doi:10.1016/j.cie.2004.12.007

Maintenance scheduling and production control of multiple-machine manufacturing systems

2005· article· en· W2140684998 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

VenueComputers & Industrial Engineering · 2005
Typearticle
Languageen
FieldEngineering
TopicManufacturing Process and Optimization
Canadian institutionsÉcole de Technologie SupérieureUniversité du Québec à Montréal
Fundersnot available
KeywordsPreventive maintenanceScheduling (production processes)Robustness (evolution)Reliability engineeringProduction controlCorrective maintenanceEngineeringComputer scienceIndustrial engineeringProduction (economics)Mathematical optimizationOperations managementMathematics

Abstract

fetched live from OpenAlex

This paper deals with the production and preventive maintenance control problem for a multiple-machine manufacturing system . The objective of such a problem is to find the production and preventive maintenance rates for the machines so as to minimize the total cost of inventory/backlog, repair and preventive maintenance. A two-level hierarchical control model is presented, and the structure of the control policy for both identical and non-identical manufacturing systems is described using parameters, referred to here as input factors . By combining analytical formalism with simulation-based statistical tools such as experimental design and response surface methodology , an approximation of the optimal control policies and values of input factors are determined. The results obtained extend those available in existing literature to cover non-identical machine manufacturing systems. A numerical example and a sensitivity analysis are presented in order to illustrate the robustness of the proposed approach. The extension of the proposed production and preventive maintenance policies to cover large systems (multiple machines, multiple products) is discussed.

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.000
metaresearch head score (Gemma)0.000
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: none
Teacher disagreement score0.672
Threshold uncertainty score0.857

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
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.011
GPT teacher head0.179
Teacher spread0.168 · 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