MétaCan
Menu
Back to cohort

Applied Data Analytics Approach for Defect Root Causes Analysis in Manufacturing: The Case of Multi-Product Assembly Lines

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

Venuenot available
Typearticle
Languageen
FieldEngineering
TopicAssembly Line Balancing Optimization
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsRoot cause analysisAnalyticsRoot (linguistics)Computer scienceProduct (mathematics)Data analysisRoot causeData scienceData miningReliability engineeringEngineeringMathematics

Abstract

fetched live from OpenAlex

Multi-product assembly lines are commonly used for their flexibility in mass-customized production, but their complexity makes identifying the root causes of defects difficult. This research addresses the limitations of traditional methods for analyzing the root causes of defects in this context. It introduces a four-step methodology for preparing data and conducting descriptive analysis of defect root causes. Product families are created by segmenting production data from the company's information systems using AHC algorithms or company knowledge. Defect rates are then calculated for each product group and the transitions between product sequences. Finally, a CART decision tree is used to generate rules that lead to defective clusters. These rules are used for descriptive analysis of defect root causes and are seen as improvement opportunities for multi-product assembly lines. The methodology was applied to two case studies using real production data. This led to the identification and validation of the root causes of defects by the partner companies. Nevertheless, limitations must be taken into account, e.g., the reliance on expert judgment for the identification of root causes, the sensitivity of the data used, and the necessity of regenerating the decision tree for each new analysis.

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.818
Threshold uncertainty score0.551

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.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.050
GPT teacher head0.293
Teacher spread0.242 · 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

Quick stats

Citations0
Published2024
Admission routes1
Has abstractyes

Explore more

Same topicAssembly Line Balancing OptimizationFrench-language works237,207