Information incorporation policies in product development

Jian Zhu, Ali A. Yassine, Ramavarapu S Sreenivas

Research output: Contribution to conferencePaper

Abstract

In the present paper, we develop a dynamic programming (DP) model of the product development (PD) process. We conceptualize PD as a sequence of decisions: whether to incorporate a piece of information that just arrived (i.e. became available) or wait longer. We, then, utilize this formulation to analyze several different situations depending on the type and nature of information being exchanged: external versus internal information, and stationary versus dynamic information. We derive optimal decision rules to determine whether (and when) to incorporate or not for each case. An analysis of the model results in several important findings. First, we must not incorporate all available information that is related to the design activity. Once the information collection exceeds certain value, the design team should stop collecting further information. Second, only when past design work accumulates a certain threshold value should the team include the latest information and perform rework. Large uncertainty of the information and large sensitivity of the design activity make the information less likely to be incorporated. Lastly, the managerial implications are discussed with several numerical examples.

Original languageEnglish (US)
Pages219-230
Number of pages12
StatePublished - Dec 1 2004
Event2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference - Salt Lake City, UT, United States
Duration: Sep 28 2004Oct 2 2004

Other

Other2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference
CountryUnited States
CitySalt Lake City, UT
Period9/28/0410/2/04

Fingerprint

Product Development
Product development
Dynamic programming
Policy
Rework
Decision Rules
Accumulate
Threshold Value
Development Process
Programming Model
Dynamic Programming
Dynamic Model
Exceed
Likely
Internal
Uncertainty
Numerical Examples
Design
Formulation

Keywords

  • Concurrent Engineering
  • Design Iteration
  • Information
  • Overlapping
  • Product Development

ASJC Scopus subject areas

  • Modeling and Simulation
  • Mechanical Engineering
  • Computer Science Applications
  • Computer Graphics and Computer-Aided Design

Cite this

Zhu, J., Yassine, A. A., & Sreenivas, R. S. (2004). Information incorporation policies in product development. 219-230. Paper presented at 2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference, Salt Lake City, UT, United States.

Information incorporation policies in product development. / Zhu, Jian; Yassine, Ali A.; Sreenivas, Ramavarapu S.

2004. 219-230 Paper presented at 2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference, Salt Lake City, UT, United States.

Research output: Contribution to conferencePaper

Zhu, J, Yassine, AA & Sreenivas, RS 2004, 'Information incorporation policies in product development' Paper presented at 2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference, Salt Lake City, UT, United States, 9/28/04 - 10/2/04, pp. 219-230.
Zhu J, Yassine AA, Sreenivas RS. Information incorporation policies in product development. 2004. Paper presented at 2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference, Salt Lake City, UT, United States.
Zhu, Jian ; Yassine, Ali A. ; Sreenivas, Ramavarapu S. / Information incorporation policies in product development. Paper presented at 2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference, Salt Lake City, UT, United States.12 p.
@conference{fd83568f58214b0e968e62f9b8dd706d,
title = "Information incorporation policies in product development",
abstract = "In the present paper, we develop a dynamic programming (DP) model of the product development (PD) process. We conceptualize PD as a sequence of decisions: whether to incorporate a piece of information that just arrived (i.e. became available) or wait longer. We, then, utilize this formulation to analyze several different situations depending on the type and nature of information being exchanged: external versus internal information, and stationary versus dynamic information. We derive optimal decision rules to determine whether (and when) to incorporate or not for each case. An analysis of the model results in several important findings. First, we must not incorporate all available information that is related to the design activity. Once the information collection exceeds certain value, the design team should stop collecting further information. Second, only when past design work accumulates a certain threshold value should the team include the latest information and perform rework. Large uncertainty of the information and large sensitivity of the design activity make the information less likely to be incorporated. Lastly, the managerial implications are discussed with several numerical examples.",
keywords = "Concurrent Engineering, Design Iteration, Information, Overlapping, Product Development",
author = "Jian Zhu and Yassine, {Ali A.} and Sreenivas, {Ramavarapu S}",
year = "2004",
month = "12",
day = "1",
language = "English (US)",
pages = "219--230",
note = "2004 ASME Design Engineering Technical Conferences and Computers and Information in Engineering Conference ; Conference date: 28-09-2004 Through 02-10-2004",

}

TY - CONF

T1 - Information incorporation policies in product development

AU - Zhu, Jian

AU - Yassine, Ali A.

AU - Sreenivas, Ramavarapu S

PY - 2004/12/1

Y1 - 2004/12/1

N2 - In the present paper, we develop a dynamic programming (DP) model of the product development (PD) process. We conceptualize PD as a sequence of decisions: whether to incorporate a piece of information that just arrived (i.e. became available) or wait longer. We, then, utilize this formulation to analyze several different situations depending on the type and nature of information being exchanged: external versus internal information, and stationary versus dynamic information. We derive optimal decision rules to determine whether (and when) to incorporate or not for each case. An analysis of the model results in several important findings. First, we must not incorporate all available information that is related to the design activity. Once the information collection exceeds certain value, the design team should stop collecting further information. Second, only when past design work accumulates a certain threshold value should the team include the latest information and perform rework. Large uncertainty of the information and large sensitivity of the design activity make the information less likely to be incorporated. Lastly, the managerial implications are discussed with several numerical examples.

AB - In the present paper, we develop a dynamic programming (DP) model of the product development (PD) process. We conceptualize PD as a sequence of decisions: whether to incorporate a piece of information that just arrived (i.e. became available) or wait longer. We, then, utilize this formulation to analyze several different situations depending on the type and nature of information being exchanged: external versus internal information, and stationary versus dynamic information. We derive optimal decision rules to determine whether (and when) to incorporate or not for each case. An analysis of the model results in several important findings. First, we must not incorporate all available information that is related to the design activity. Once the information collection exceeds certain value, the design team should stop collecting further information. Second, only when past design work accumulates a certain threshold value should the team include the latest information and perform rework. Large uncertainty of the information and large sensitivity of the design activity make the information less likely to be incorporated. Lastly, the managerial implications are discussed with several numerical examples.

KW - Concurrent Engineering

KW - Design Iteration

KW - Information

KW - Overlapping

KW - Product Development

UR - http://www.scopus.com/inward/record.url?scp=14044263033&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=14044263033&partnerID=8YFLogxK

M3 - Paper

AN - SCOPUS:14044263033

SP - 219

EP - 230

ER -