MétaCan
Menu
Back to cohort
Record W2091390249 · doi:10.1080/00207540410001720403

Concurrent optimization of the design and manufacturing stages of product development

2004· article· en· W2091390249 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

VenueInternational Journal of Production Research · 2004
Typearticle
Languageen
FieldEngineering
TopicManufacturing Process and Optimization
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsConcurrent engineeringMathematical optimizationNew product developmentComputer scienceProcess (computing)Product (mathematics)Function (biology)Representation (politics)Quality (philosophy)Product designGeometric programmingGoal programmingEngineering design processParametric statisticsIndustrial engineeringEngineeringMathematics

Abstract

fetched live from OpenAlex

The problem of concurrent optimization of the design and the process planning stages when a new product is developed is addressed. The paper advocates for a simultaneous approach rather than the traditional sequential one. A mathematical representation of this approach is given for these two stages. A mathematical programming technique is used to find the optimal values of the design and the process characteristics. The objective function is a quality loss function. The constraints are the customer requirements, the product's specification limits, the parts' dimensional limits and the process capability. The traditional sequential approach of concurrent engineering is compared with the proposed simultaneous approach. A parametric analysis of the objective function is performed by applying an interactive multi-objective goal programming technique. A numerical example of a low-pass electrical circuit is given. It is shown that the proposed approach leads to better efficient solutions than the sequential approach. The decision-maker interacts with the optimization process and can choose the efficient solution that best satisfies the company's needs.

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: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.991
Threshold uncertainty score0.183

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.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.056
GPT teacher head0.322
Teacher spread0.266 · 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