MétaCan
Menu
Back to cohort
Record W2547900030 · doi:10.1109/itmc.2005.7461252

Understanding and implementation of Concurrent Engineering

2005· article· en· W2547900030 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
FieldBusiness, Management and Accounting
TopicProduct Development and Customization
Canadian institutionsUniversity of Windsor
Fundersnot available
KeywordsConcurrent engineeringNew product developmentKey (lock)Computer scienceProcess (computing)Product (mathematics)Software engineeringProduct engineeringSystems engineeringProduct lifecycleManufacturing engineeringProcess managementProduct designEngineering managementEngineeringOperations managementProgramming languageBusinessScheduling (production processes)Operating system

Abstract

fetched live from OpenAlex

Concurrent Engineering (CE) represents a key trend in product development over last decade. It has changed academic and industrial approaches of looking at the product development process. This paper introduces definitions of CE and a brief comparison with traditional product development cycle, after which the enabling technologies for CE are analysed. The main purpose of this paper is to discuss implementation of CE to help a company to understand how to implement concurrent engineering.

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: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.863
Threshold uncertainty score0.219

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.001
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.039
GPT teacher head0.235
Teacher spread0.197 · 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

Citations7
Published2005
Admission routes1
Has abstractyes

Explore more

Same topicProduct Development and CustomizationFrench-language works237,207