MétaCan
Menu
Back to cohort
Record W4309073957 · doi:10.1080/00207543.2022.2139002

Dynamic allocation of human resources: case study in the metal 4.0 manufacturing industry

2022· article· en· W4309073957 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.

Bibliographic record

VenueInternational Journal of Production Research · 2022
Typearticle
Languageen
FieldEngineering
TopicScheduling and Optimization Algorithms
Canadian institutionsUniversité Laval
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsFlexibility (engineering)MachiningComputer scienceProduction (economics)Task (project management)Constraint (computer-aided design)Mathematical optimizationIndustrial engineeringOperator (biology)Dynamic programmingEngineeringAlgorithmMechanical engineeringSystems engineeringMathematics

Abstract

fetched live from OpenAlex

Industry 4.0 concepts make it possible to rethink human resources allocation, even for more traditional environments like metal machining. While parts machining on Computer Numerical Control (CNC) machines is automated, some manual tasks must still be executed by operators. The current approach is typically that operators are statically allocated to one or many machines. This causes avoidable bottlenecks. We propose an optimisation model to dynamically assign tasks to the operators with the objective of minimising production delays. Three different scenarios are compared; one representing the current widely used static allocation method and two others that allow more flexibility in the operators’ allocation. The dynamic task assignment problem is solved using a constraint programming model. The model was applied to a case study from a high-precision metal manufacturing job shop. Experimental results show that switching from a static allocation to a dynamic one reduces by 76% the average production delays caused by human operators. Supposing more versatile operators under the dynamic allocation leads to further improvements.

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.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: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.824
Threshold uncertainty score0.523

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
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.071
GPT teacher head0.390
Teacher spread0.319 · 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