MétaCan
Menu
Back to cohort
Record W1980858669 · doi:10.1080/07408170590516764

Complex assembly variant design in agile manufacturing. Part I: System architecture and assembly modeling methodology

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

VenueIIE Transactions · 2004
Typearticle
Languageen
FieldEngineering
TopicManufacturing Process and Optimization
Canadian institutionsBell (Canada)
FundersNational Science Foundation
KeywordsAssembly modellingAgile manufacturingDesign for assemblyComponent (thermodynamics)Agile software developmentComputer scienceGraphEngineeringArchitectureSystems engineeringEngineering drawingProduct (mathematics)Software engineeringTheoretical computer scienceMechanical engineering

Abstract

fetched live from OpenAlex

In the distributed and horizontally integrated manufacturing environment found in agile manufacturing, there is a great demand for new product development methods that are capable of generating new customized assembly designs based on mature component designs that might be dispersed at geographically distributed partner sites. To cater for this demand, this paper addresses the methodology for complex assembly variant design in agile manufacturing. It consists in fundamental research in two parts: (i) assembly modeling; and (ii) assembly variant design methodology. This paper, the first of a two-part series, presents the assembly variant design system architecture and the assembly modeling methodology. First, a complementary assembly modeling concept is proposed with two kinds of assembly models, the hierarchical assembly model and the relational assembly model. The first explicitly captures the hierarchical and functional relationships between constituent components whereas the second explicitly captures the mating relationships at the form-feature-level. These models are complementary in the sense that each of them models only a specific aspect of assembly-related information but together they include the required assembly-related information. They are further specialized to accommodate the features of assembly variant design. As a result, two kinds of assembly models, the assembly variants model and the assembly mating graph are generated. These assembly models serve as the basis for assembly variant design which is discussed in the companion paper.

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: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.860
Threshold uncertainty score0.856

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.064
GPT teacher head0.254
Teacher spread0.190 · 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