MétaCan
Menu
Back to cohort
Record W2003903403 · doi:10.1287/opre.1090.0788

Coordinated Multistage Scheduling of Parallel Batch-Processing Machines Under Multiresource Constraints

2010· article· en· W2003903403 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

VenueOperations Research · 2010
Typearticle
Languageen
FieldEngineering
TopicScheduling and Optimization Algorithms
Canadian institutionsSimon Fraser University
Fundersnot available
KeywordsComputer scienceScheduling (production processes)Production scheduleInteger programmingJob shop schedulingScheduleDistributed computingMathematical optimizationDynamic priority schedulingBatch productionFair-share schedulingAlgorithmOperations managementEngineeringMathematics

Abstract

fetched live from OpenAlex

Motivated by scheduling challenges of burn-in ovens in back-end semiconductor manufacturing, we propose a linear-programming-based algorithm, an integer-programming-based algorithm, and a heuristic-based algorithm to schedule nonhomogenous parallel batch machines with nonidentical job sizes and incompatible job families. We consider the common scheduling of consecutive steps that are linked together through secondary scarce resources. Our approach addresses the availability and compatibility of several resources required to make each process possible. The algorithms strive to meet short-term production targets expressed by product and step. The algorithms are shown to be effective and computationally efficient for this purpose. Taken together with previously developed methodology for the practical translation of target output schedules into short-term local production targets, this article suggests how a complex supply chain manufacturing system can be efficiently and effectively managed by decentralized local scheduling algorithms striving to meet short-term production targets that in turn ensure maintenance of an appropriate dynamic profile across production steps for work-in-process.

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.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: Empirical
Teacher disagreement score0.116
Threshold uncertainty score0.535

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.039
GPT teacher head0.341
Teacher spread0.302 · 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