MétaCan
Menu
Back to cohort
Record W2886943487 · doi:10.24908/pceea.v0i0.10128

A Tool for Systematically Accessing the Level of Readiness of Engineering Design in Product Development

2018· article· en· W2886943487 on OpenAlexaffvenue
Kamran Behdinan, Mahi Fahimian, Remon Pop‐Iliev

Bibliographic record

VenueProceedings of the Canadian Engineering Education Association (CEEA) · 2018
Typearticle
Languageen
FieldEngineering
TopicTechnology Assessment and Management
Canadian institutionsOntario Tech UniversityUniversity of Toronto
Fundersnot available
KeywordsDeliverableNew product developmentSystems engineeringEngineering design processComputer scienceProduct designProduct (mathematics)Process (computing)Product design specificationManufacturing engineeringSoftware engineeringProcess managementEngineeringBusinessMechanical engineeringMathematics

Abstract

fetched live from OpenAlex

Abstract – This paper introduces a top down, system-engineering approach to develop a quantifiable and systematic tool, referred to as Design Readiness Level (DRL), to gauge design at each stage of product development. It is developed to facilitate communication between different stockholders of a design project and to address the complexities arising during all the phases of product design, from initiation to completion. The design process as one of the pillars of DRL has been studied thoroughly and is categorized into nine stages to reflect the technical flow in product development. The design stages are iterative at any level from 1 to 9 and have distinctive deliverables at the end of each stage. The deliverables simplify and characterize the assessment of the design from the technical point of view. Developing a comprehensive DRL metrics that encompasses all the stockholders’ perspectives in a design is a work in progress.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.021
metaresearch head score (Gemma)0.095
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.021
Threshold uncertainty score0.111

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0210.095
Meta-epidemiology (narrow)0.0020.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0210.006
Science and technology studies0.0010.001
Scholarly communication0.0060.006
Open science0.0010.004
Research integrity0.0010.002
Insufficient payload (model declined to judge)0.0040.002

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.026
GPT teacher head0.238
Teacher spread0.212 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2018
Admission routes2
Has abstractyes

Explore more

Same venueProceedings of the Canadian Engineering Education Association (CEEA)Same topicTechnology Assessment and ManagementFrench-language works237,207