The role of associations in CAD and PLM for handling change propagation during product development
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.
Bibliographic record
Abstract
Current Computer Aided Design (CAD) systems can capture some of the design intent by creating associations between objects. This increases the productivity during product development, and helps maintain the coherence of the product definition when handling engineering changes. CAD systems establish some associations as well as their use at a rather low level of abstraction, e.g. a parallelism constraint. Product Lifecycle Management (PLM) systems, on the other hand, use associations at a higher abstraction level, generally between files. The associations handled by these systems do differ both in terms of abstraction level and formalism of the knowledge they encapsulate. Moreover, limited connections exist between the associations manipulated in both systems, so that handling change propagation in concurrent engineering remains an issue. In this paper, we propose a taxonomy and a model of the different types of associations required to support the set of tasks in the area of product development. The terms on which the taxonomy relies are: association, relation, link, and constraint. The proposed model, named RLC, uses the concepts of aggregation and decomposition to relate Relations, Links, and Constraints.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it