Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat
Cited by 167

The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.

Lean product development flow

Oppenheim, Bohdan W. · 2004 · Systems Engineering

Abstract

A general holistic framework, also called a process—named “Lean Product Development Flow (LPDF)”—for organizing the engineering work of Product Development (PD), has been proposed as a contribution to the emerging field of Lean Systems Engineering. The framework is based on Lean Principles, with emphasis on PD value‐pulling workflow pulsed by takt periods. The value is defined as (1) mission assurance/product quality, (the traditional goals of Systems Engineering) and (2) reduced program cost and schedule achieved by a radical reduction of waste. LPDF is recommended for smaller design programs based on a high degree of legacy knowledge, with technologies mature enough so that the program feasibility is not in question. LPDF may involve limited‐scope research, provided that it can be identified early in the program, and carried out separate from the main workflow. The paper is focused on aerospace and defense programs, which are presently burdened with as much as 60–90% of waste, but the process is also applicable to commercial programs. LPDF can be applied to the entire PD, to one or more milestones, and to a multilevel program. LPDF requires both detailed preparations and disciplined execution. The preparations include detailed Value Stream Mapping, separation of research from the main workflow, parsing of the Value Stream map into Takt Periods, architecting the LPDF team using dynamic allocation of resources, and team training. LPDF execution is organized as a flow through a series of short and equal work Takt Periods, each followed by an Integrative Event for structured, comprehensive coordination. Strategic and flexible tactical mitigations of uncertainties must be applied during the flow. LPDF also requires excellent leadership of a Chief Engineer, modeled after Toyota and Honda, who is a dedicated program “owner,” an expert systems designer, a strong leader focused on the program and product integrity, and skilled in consensus‐building. The Chief Engineer is responsible for the entire program, with Assistant Chiefs assisting in selected technical areas, and a Project Manager assisting with program administration. An industrial pilot program is currently being undertaken to validate the method. © 2004 Wiley Periodicals, Inc. Syst Eng 7: 352–376, 2004

Overview

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Integrity signals

Registry

Crossref · 10.1002/sys.20014

Cites

1 of 1 references verified0 citation errors · 0 not checkable

Statistics

Verification

Claims the paper makes

The claims and statistics of this paper haven’t been checked yet.

Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.

A few free checks a day · papers already verified open instantly · results are public

Self-check

Percentages, sums and reported differences re-computed from the paper’s own numbers.

The self-check needs the paper’s full text.

Citations

Cites

Show all 1 references

Cited by

Metadata

Authors
Oppenheim, B. W.
Venue
Systems Engineering
Publisher
Wiley
Published
2004-01
Volume
7
Issue
4
ISSN
  • 1098-1241 (ISSN-L)
  • 1520-6858
OpenAlex
W2157646506
Cited by
167
References
1
FWCI
6.42
Type
journal article
Language
en
Open access
closed

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review

Data sources

Bibliographic data: Semantic Scholar, OpenAlex, Crossref.

Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).

Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.