MétaCan
Menu
Back to cohort
Record W4413929950 · doi:10.1016/j.mfglet.2025.06.011

Balancing trade-offs between first three moments of completion times for one-stage production

2025· article· en· W4413929950 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

VenueManufacturing Letters · 2025
Typearticle
Languageen
FieldEngineering
TopicScheduling and Optimization Algorithms
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsProduction (economics)Stage (stratigraphy)Completion (oil and gas wells)Computer scienceOperations managementEconomicsEngineeringGeologyMechanical engineeringMicroeconomics

Abstract

fetched live from OpenAlex

For one-stage production, operations management faces the following three challenges to make decisions, which are inconsistencies between key performance indicators (KPIs) for production, trade-offs between the expected return and the risk in modern portfolio theory (MPT), and uncertainties in processing times. Traditionally, total completion time ( TCT ) and variance of completion times ( VCT ) are two KPIs for one-stage production scheduling, which relate to the first and second moments of completion times, respectively. We question whether the third moment of completion times is good to address the three challenges. In this paper, we introduce the skewness of completion times ( SCT ) in scheduling, and propose the ToB( a , b ) heuristics for trade-off balancing. Through case studies with 5 levels of processing time uncertainties and compared to existing ToB( α ) heuristics which balance trade-offs between TCT and VCT , we show that our ToB( a , b ) heuristics dominate ToB( α ) heuristics in terms of smaller expected values ( E ) of weighted sum of deviations from the best solutions of KPIs and smaller risks ( σ ) associated with these KPI deviations. Therefore, our ToB( a , b ) heuristics are more robust to balance trade-offs between the three KPIs under processing time uncertainties.

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

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.017
GPT teacher head0.224
Teacher spread0.207 · 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