MétaCan
Menu
Back to cohort
Record W2296579285 · doi:10.1115/detc2015-46965

Value-Driven Modeling of Tactical and Operational Decisions in Support of Aerospace Product-Service Systems Design

2015· article· en· W2296579285 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

Venuenot available
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicQuality Function Deployment in Product Design
Canadian institutionsMcGill University
FundersNatural Sciences and Engineering Research Council of CanadaCoordenação de Aperfeiçoamento de Pessoal de Nível SuperiorMcGill University
KeywordsQuality function deploymentAerospaceSoftware deploymentProduct-service systemService (business)Systems engineeringProcess managementComputer scienceProduct designProduct (mathematics)Function (biology)Manufacturing engineeringNew product developmentBusiness modelEngineering managementRisk analysis (engineering)BusinessEngineeringSoftware engineeringMarketing

Abstract

fetched live from OpenAlex

Competitive markets and complex business-to-business environments compel manufacturers to provide innovative service offerings along with their products. This necessitates effective methodologires for developing and implementing sucessful new business strategies. This article presents an approach to model tactical and operational decisions to support the design and development of Product-Service Systems (PSSs). A combination of Quality Function Deployment and Design-to-Cost techniques is proposed as the first step of a PSS design framework that aids design engineers to determine the relations among value to customer, functional requirements, design variables and cost. The objective is to identify PSS design alternatives that deliver value to customer while respecting cost targets. An aerospace software case study is conducted to demonstrate the proposed approach.

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.002
metaresearch head score (Gemma)0.001
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.448
Threshold uncertainty score0.482

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
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.147
GPT teacher head0.293
Teacher spread0.146 · 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