<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" version="2.0">
<channel>
<title>Lean Aerospace Initiative</title>
<link>http://hdl.handle.net/1721.1/1785</link>
<description>U.S. Air Force, aerospace industry, labor, and MIT collaborate to
achieve lean capability at the enterprise level to deliver value to
every stakeholder.</description>
<image>
<title>The Channel Image</title>
<url xmlns="http://apache.org/cocoon/i18n/2.1">http://dspace.mit.edu:80/retrieve/101</url>
<link>http://hdl.handle.net/1721.1/1785</link>
</image>
<item>
<title>Value Creation Through Integration Workshop</title>
<link>http://hdl.handle.net/1721.1/7529</link>
<description>Value Creation Through Integration Workshop

Warmkessel, Joyce

</description>
<pubDate>Tue, 29 Jan 2002 22:58:59 GMT</pubDate>
</item>
<item>
<title>Preliminary Observations on Program Instability</title>
<link>http://hdl.handle.net/1721.1/7528</link>
<description>Preliminary Observations on Program Instability

Rebentisch, Eric

This white paper reports emerging findings at the end of Phase I of the Lean Aircraft&#13;
Initiative in the Policy focus group area. Specifically, it provides details about research on&#13;
program instability. Its objective is to discuss high-level findings detailing: 1) the relative&#13;
contribution of different factors to a program’s overall instability; 2) the cost impact of program&#13;
instability on acquisition programs; and 3) some strategies recommended by program managers for&#13;
overcoming and/or mitigating the negative effects of program instability on their programs.&#13;
Because this report comes as this research is underway, this is not meant to be a definitive&#13;
document on the subject. Rather, is it anticipated that this research may potentially produce a&#13;
number of reports on program instability-related topics.&#13;
&#13;
The government managers of military acquisition programs rated annual budget or&#13;
production rate changes, changes in requirements, and technical difficulties as the three top&#13;
contributors, respectively, to program instability. When asked to partition actual variance in their&#13;
program’s planned cost and schedule to each of these factors, it was found that the combined&#13;
effects of unplanned budget and requirement changes accounted for 5.2% annual cost growth and&#13;
20% total program schedule slip. At a rate of approximately 5% annual cost growth from these&#13;
factors, it is easy to see that even conservative estimates of the cost benefits to be gained from&#13;
acquisition reforms and process improvements can quickly be eclipsed by the added cost associated&#13;
with program instability.&#13;
&#13;
Program management practices involving the integration of stakeholders from throughout&#13;
the value chain into the decision making process were rated the most effective at avoiding program&#13;
instability. The use of advanced information technologies was rated the most effective at mitigating&#13;
the negative impact of program instability.

</description>
<pubDate>Wed, 09 Oct 1996 22:58:59 GMT</pubDate>
</item>
<item>
<title>Measuring Value in Product Development</title>
<link>http://hdl.handle.net/1721.1/7527</link>
<description>Measuring Value in Product Development

Smith, Jim

“What is value in product development?” is the key question of this paper. The answer is&#13;
critical to the creation of lean in product development. By knowing how much value is added by&#13;
product development (PD) activities, decisions can be more rationally made about how to&#13;
allocate resources, such as time and money.&#13;
&#13;
In order to apply the principles of Lean Thinking and remove waste from the product&#13;
development system, value must be precisely defined. Unfortunately, value is a complex entity&#13;
that is composed of many dimensions and has thus far eluded definition on a local level. For this&#13;
reason, research has been initiated on “Measuring Value in Product Development.” This paper&#13;
serves as an introduction to this research. It presents the current understanding of value in PD,&#13;
the critical questions involved, and a specific research design to guide the development of a&#13;
methodology for measuring value.&#13;
&#13;
Work in PD value currently focuses on either high-level perspectives on value, or detailed looks&#13;
at the attributes that value might have locally in the PD process. Models that attempt to capture&#13;
value in PD are reviewed. These methods, however, do not capture the depth necessary to allow&#13;
for application. A methodology is needed to evaluate activities on a local level to determine the&#13;
amount of value they add and their sensitivity with respect to performance, cost, time, and risk.&#13;
&#13;
Two conceptual tools are proposed. The first is a conceptual framework for value creation in&#13;
PD, referred to here as the Value Creation Model. The second tool is the Value-Activity Map,&#13;
which shows the relationships between specific activities and value attributes. These maps will&#13;
allow a better understanding of the development of value in PD, will facilitate comparison of&#13;
value development between separate projects, and will provide the information necessary to&#13;
adapt process analysis tools (such as DSM) to consider value.&#13;
&#13;
The key questions that this research entails are:&#13;
· What are the primary attributes of lifecycle value within PD?&#13;
· How can one model the creation of value in a specific PD process?&#13;
· Can a useful methodology be developed to quantify value in PD processes?&#13;
· What are the tools necessary for application?&#13;
· What PD metrics will be integrated with the necessary tools?&#13;
&#13;
The research milestones are:&#13;
· Collection of value attributes and activities (September, 200)&#13;
· Development of methodology of value-activity association (October, 2000)&#13;
· Testing and refinement of the methodology (January, 2001)&#13;
· Tool Development (March, 2001)&#13;
· Present findings at July INCOSE conference (April, 2001)&#13;
· Deliver thesis that captures a formalized methodology for defining value in PD (including&#13;
LEM data sheets) (June, 2001)&#13;
&#13;
The research design aims for the development of two primary deliverables: a methodology to&#13;
guide the incorporation of value, and a product development tool that will allow direct&#13;
application.

</description>
<pubDate>Sun, 27 Feb 2000 22:58:59 GMT</pubDate>
</item>
<item>
<title>Lean Transition of Emerging Industrial Capability (LeanTEC)</title>
<link>http://hdl.handle.net/1721.1/7526</link>
<description>Lean Transition of Emerging Industrial Capability (LeanTEC)

Shroyer, E.

Lean Transition of Emerging Industrial Capability (LeanTEC) program was a cooperative agreement between the Boeing Company&#13;
and AFRL conducted from January 1998 to January 2002. The results of this program are documented in the Manual for Effective&#13;
Technology Transition Processes included as an attachment to this report. This manual provides processes, procedures, and tools for&#13;
greatly improving technology transition in the aerospace industry. Methodology for the implementation of these improvements is&#13;
given along with methods for customizing the various processes, procedures, and tools for a given company or business unit. The&#13;
indicated methodology was tested by the LeanTEC team and results are documented in the report.

</description>
<pubDate>Tue, 26 Feb 2002 22:58:59 GMT</pubDate>
</item>
</channel>
</rss>
