MétaCan
Menu
Back to cohort
Record W2068014134 · doi:10.1115/detc2010-29005

A Product Lifecycle Management Framework to Support the Exchange of Prototyping and Testing Information

2010· article· en· W2068014134 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
TopicManufacturing Process and Optimization
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsProduct lifecycleComputer scienceNew product developmentKnowledge managementProduct managementProduct design specificationProcess managementProduct designProduct life-cycle managementMerge (version control)Context (archaeology)Product (mathematics)Systems engineeringSoftware engineeringEngineeringBusiness

Abstract

fetched live from OpenAlex

The modern perspective on product life cycle and the rapid evolution of Information and Communication Technologies in general have opened a new era in product representation and product information sharing between participants, both inside and outside the enterprise and throughout the product life. In particular, the Product Development Process relies on cross-functional activities involving different domains of expertise that each have their own dedicated tools. This has generated new challenges in terms of collaboration and dissemination of information at large between companies or even within the same organization. Within this context, the work reported in this paper focuses on a specific stakeholder within product development activities — the testing department. Its business is typically related to the planning and building of prototypes in order to perform specific tests on the future product or one of its sub-assemblies. This research project aims at investigating how results from testing activities can efficiently interface with other departments, in particular to offer relevant information feedback to designers. As a first step, a study based on an open source initiative is described to show how two natively disparate PLM tools can dialogue to merge information in a central environment. The principles applied in the study are then transposed to introduce a framework where information from prototyping and testing activities could be mapped and merged with design activities to match needs in a cross-functional setting.

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: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.912
Threshold uncertainty score0.143

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.009
GPT teacher head0.210
Teacher spread0.201 · 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

Citations9
Published2010
Admission routes1
Has abstractyes

Explore more

Same topicManufacturing Process and OptimizationFrench-language works237,207