MétaCan
Menu
Back to cohort
Record W3087926714 · doi:10.1177/1063293x20958916

Performance measurement of a lean product development process

2020· article· en· W3087926714 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

VenueConcurrent Engineering · 2020
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicQuality and Supply Management
Canadian institutionsConcordia University
Fundersnot available
KeywordsProcess (computing)New product developmentLean laboratoryProduct (mathematics)Lean project managementEngineeringProcess managementManufacturing engineeringLean manufacturingSystems engineeringMeasure (data warehouse)ChartComputer scienceSoftware developmentBusinessData mining

Abstract

fetched live from OpenAlex

Over the past few years, organizations have faced pressure from stakeholders to implement lean principles in their product development processes. However, the existing methods are not capable of measuring the benefits of adopting lean initiatives in the product development process. This research aims to develop a performance measurement model that can measure the effects of implementing lean in the engineering process. Engineering effort is analyzed in order to identify hidden wastes (e.g. inventory in the form of information about product specifications or engineering errors) in the engineering process. The model has been implemented in a civil design process of an engineering consultant company to validate the general applicability of the new model. The implementation of the model provides visibility on the waste hidden in the engineering process and quantifies that waste. The most significant contribution of this research is the development of new performance metrics and a decomposition chart. Finally, performance metrics are properly linked and the model treats lean as a holistic system, quantitatively measuring performance at different organizational levels.

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: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.546
Threshold uncertainty score0.693

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.049
GPT teacher head0.216
Teacher spread0.167 · 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