MétaCan
Menu
Back to cohort
Record W4220755885 · doi:10.1061/9780784483961.132

Optimization of Labor Flow Efficiency in Steel Fabrication Project Planning

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

VenueConstruction Research Congress 2022 · 2022
Typearticle
Languageen
FieldDecision Sciences
TopicResource-Constrained Project Scheduling
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsSolverProductivityComputer scienceWorkstationFlow shop schedulingLabor costOperations managementOperations researchJob shop schedulingEngineeringScheduleEconomicsOperating systemMechanical engineering

Abstract

fetched live from OpenAlex

This study considers projects that employ multi-skilled labor resources in performing different tasks aiming at improving labor utilization efficiency. Based on field observation, the journeymen employed in a steel girder fabrication shop for bridge construction exemplify multi-skilled labor resources in a practical setting. In particular, the need for crew transferring and waiting between various workstations on the shop floor gives rise to the bulk of semi-productive labor time. Unpredictable and unnecessary semi-productive worker hours are considered as a kind of waste as per lean principles. Increasing labor flow efficiency by properly allocating limited labor resources to project activities would reduce the semi-productive labor hours while enhancing the labor flow reliability, leading to better productivity and leaner processes. Labor Flow Waste Index (LFWI) is defined based on the determination of the semi-productive worker hours using resource-constrained project scheduling analysis. Further, the optimization problem of minimizing LFWI is formulated. A case study was conducted Utilizing Microsoft Excel Solver, resulting in significant decrease on the waste in labor resource flow.

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.014
metaresearch head score (Gemma)0.011
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Insufficient payload (model declined to judge)
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.069
Threshold uncertainty score0.998

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0140.011
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.008
Science and technology studies0.0010.001
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0020.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.160
GPT teacher head0.448
Teacher spread0.288 · 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