Commercial gas turbine engine platform strategy and design

Product development challenges companies to produce designs that meet customer requirements yet, that are within their technological and financial means to do so. The proliferation of customized or unique designs may tax the resources of a firm if product variety cannot be achieved in a cost-effective manner. A product platform strategy allows a set of core elements or subsystems to be shared across all or part of a company's product portfolio, while design flexibility allows differentiated functions to satisfy specific customer needs. A framework for identifying potential platform elements from among key system design variables is provided. This framework supports the hypothesis that system design variables with low normalized coupling and low normalized variation across a set of conceptual product designs should be considered as potential platform elements. A system level approach for identifying the coupling and variation of these elements is facilitated through the formulation and use of a modified quality function deployment (QFD) mapping procedure. Normalized coupling is quantified as the relative importance of relationships between stakeholder needs, system requirements and system design variables, divided by a ranking of the difficulty in their achievement. Normalized variation of system design variables from a sample of parameter data is calculated as the standard deviation divided by the mean. The proposed framework and hypothesis is validated with a case study of the Pratt & Whitney PW4000 family of commercial gas turbine engines where predicted platform elements were consistent with actual design choices. Thesis Advisor: Kevin N. Otto Title: Associate Professor of Mechanical Engineering

[1]  R. Verma,et al.  Using conjoint analysis to help design product platforms , 1999 .

[2]  Greg Paula,et al.  Reinventing a core product line , 1997 .

[3]  E. Rechtin,et al.  The art of systems architecting , 1996, IEEE Spectrum.

[4]  S. Sanderson,et al.  Managing product families: The case of the Sony Walkman , 1995 .

[5]  K. Ulrich,et al.  Planning for Product Platforms , 1998 .

[6]  R. Kaplan,et al.  The Balanced Scorecard: Translating Strategy into Action , 1996 .

[7]  Management ™ are Trademarks of SAP AG. The Management Cockpit ™ is a Trademark of SAP AG, originally created by Prof. , 2022 .

[8]  Jo Ruetta Roberson Designing effective portfolio variety using customer need discrimination thresholds , 1999 .

[9]  James M. Utterback,et al.  The product family and the dynamics of core capability , 1992 .

[10]  C. Prahalad,et al.  The Core Competence of the Corporation , 1990 .

[11]  Susan Carlson Skalak House of Quality , 2002 .

[12]  Leonard Bridgeman,et al.  Jane's All the World's Aircraft , 1970 .

[13]  Kevin Otto,et al.  Product Architecture Definition Based Upon Customer Demands , 1999 .

[14]  Deborah G. Ancona,et al.  Managing for the Future: Organizational Behavior and Processes , 1998 .

[15]  Rahul Singh,et al.  A Model-Based Approach for Planning and Developing a Family of Technology-Based Products , 1999, Manuf. Serv. Oper. Manag..

[16]  Javier P. Gonzalez-Zugasti,et al.  A Method for Architecting Product Platforms , 2000 .

[17]  Michael A. Cusumano,et al.  Thinking Beyond Lean: How Multi Project Management is Transforming Product Development at Toyota and Other Companies , 1998 .

[18]  Peter F. Drucker,et al.  Managing for the Future , 1992 .

[19]  Henry Cohen,et al.  Gas Turbine Theory - 4th Edition , 1987 .