MétaCan
Menu
Back to cohort
Record W4402104876 · doi:10.1080/03155986.2024.2393039

A line balancing problem with parallel workers and cycle time minimization

2024· article· en· W4402104876 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

VenueINFOR Information Systems and Operational Research · 2024
Typearticle
Languageen
FieldEngineering
TopicAssembly Line Balancing Optimization
Canadian institutionsHEC Montréal
FundersSocial Sciences and Humanities Research Council of Canada
KeywordsMinificationComputer scienceLine (geometry)Time lineMathematical optimizationParallel computingMathematicsGeometry

Abstract

fetched live from OpenAlex

We study the problem of balancing assembly lines with parallel workers, motivated by features observed at a third-party logistics provider. The assembly line differs from the two known types of line balancing problems in the literature since it determines simultaneously the line cycle time and the number of workers per station. Furthermore, each station can be occupied by more than one worker and a restriction on the minimum number of stations is imposed. This new type of line balancing problem minimizes the line cycle time, where two types of decisions must be made: how to group the tasks into stations and how many workers to assign to each station. We adapt mathematical models based on assembly line balancing problems with parallel stations. Furthermore, we propose a new model based on network flow formulations for the special case of lines with a serial task structure, frequently observed at the company. We perform an extensive computational study with realistic instances in order to compare the speed of solving different formulations, which is important as such a problem is at the operational level. We also provide a sensitivity analysis of key parameters aiming to better understand the trade-offs and provide meaningful managerial insights.

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: none
Teacher disagreement score0.768
Threshold uncertainty score0.952

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.000
Science and technology studies0.0000.000
Scholarly communication0.0010.002
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.013
GPT teacher head0.269
Teacher spread0.256 · 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