MétaCan
Menu
Back to cohort
Record W2100361444 · doi:10.1109/tsmcc.2010.2059013

Decision-Making Assistance in Engineering-Change Management Process

2010· article· en· W2100361444 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

VenueIEEE Transactions on Systems Man and Cybernetics Part C (Applications and Reviews) · 2010
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicProduct Development and Customization
Canadian institutionsUniversité de Sherbrooke
Fundersnot available
KeywordsProcess (computing)Product data managementComputer scienceProcess managementConcurrent engineeringChange management (ITSM)Collaborative engineeringProduct (mathematics)Engineering design processEngineering managementProduct designNew product developmentKnowledge managementSystems engineeringEngineeringWork in processManufacturing engineeringProduct lifecycleOperations managementBusiness

Abstract

fetched live from OpenAlex

Effective engineering-change management (ECM) is a real challenge in mechanical engineering industry and manufacturing companies. Computer-aided design systems are usually connected to other systems such as ERP or product data management, but currently this integration does not provide effective means to manage engineering change (EC). While communication between multidisciplinary teams working on a project is known to have a significantly positive impact on the ECM, the communication between disciplines is generally performed solely through message exchange. Experts could feel the need to meet to agree on the requested changes, which in turn translates into longer design and manufacturing processes. There is a need for a system that assists human experts in making decisions about ECs. Such a system will considerably reduce the processing time following a change-request procedure. This paper proposes a collaborative tool named EchoMag, which assists designers and experts during the change-management process. The proposed system ensures the coherence of data between the various disciplines involved in the change process. EchoMag also assists experts in making decisions by proposing alternative solutions when change requests are not agreed upon. Software agents were used to implement EchoMag for which a prototype was developed. Results of the implementation are discussed.

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: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.976
Threshold uncertainty score0.669

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.015
GPT teacher head0.241
Teacher spread0.227 · 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