MétaCan
Menu
Back to cohort
Record W4381185646 · doi:10.1017/pds.2023.6

A CASE STUDY OF THE DECISION-MAKING BEHIND THE AUTOMATION OF A COMPOSITES-BASED DESIGN PROCESS

2023· article· en· W4381185646 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueProceedings of the Design Society · 2023
Typearticle
Languageen
FieldEngineering
TopicManufacturing Process and Optimization
Canadian institutionsUniversity of Toronto
FundersMitacs
KeywordsAutomationModular designHeuristicsProcess (computing)Electronic design automationComputer scienceComputer-automated designKey (lock)Manufacturing engineeringEngineering design processProcess automation systemSystems engineeringEngineeringSoftware engineeringSystems designEmbedded system

Abstract

fetched live from OpenAlex

Abstract Automation and artificial intelligence (AI) are increasingly seen as appealing tools to perform design tasks traditionally accomplished by human designers. In today's digital economy, industries aim to adopt these tools to improve the efficiency of their complex design processes. But how does one decide what parts of their existing design process should be automated and which automation/AI tool to implement? With these questions in mind, we present a case study highlighting a company's decision-making process in converting its existing designer-dependent design process to one supported by automation. In this case study, we observed the company's decisions in selecting and rejecting certain automation and AI methods before finalizing a heuristics-based automation method that proved highly efficient compared to the company's traditional human-driven design program. In addition, we present three key discussion points observed in this case study: (1) the importance of implementing the designer's heuristics in the automation framework, (2) the importance of a uniform and modular design automation framework, and (3) the challenges of implementing AI methods.

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.001
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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.085
Threshold uncertainty score0.347

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.027
GPT teacher head0.260
Teacher spread0.233 · 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