<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-22T09:06:28Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/29154" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/29154</identifier><datestamp>2022-01-13T07:55:19Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor" lang="en_US">Daniel Whitney.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Mascoli, Gregory J</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Sloan School of Management.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Sloan School of Management</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2005-09-27T20:56:33Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-09-27T20:56:33Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">1999</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">1999</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/29154</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">45279359</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, System Design &amp; Management Program; and, (S.M.)--Massachusetts Institute of Technology, Sloan School of Management, 1999.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 91-92).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Engineering and Manufacturing firms face increasing pressure to continuously improve product development performance in terns of time to market, development cost, and customer satisfaction. The product development organization continues to evolve, first from a strictly functional focus to a product centric focus, and currently to some middle ground between the two extremes, where the strengths of the functional organization are recognized along with the merits of product focused teams. Almost simultaneously, many firms are becoming more distributed geographically and culturally, driven by internal and external influences including: efficiencies of co-location and outsourcing, business partnerships, joint ventures, and offset agreements. As the product development organization becomes less centralized, the challenge of integrating components into the top level system becomes much more complex relative to the time when all the components were designed and built in a relatively central location. One approach to address the increasingly critical integration issues is to develop and execute a process that encourages a system level approach to product development, a process that complements the part- and assembly-level design process. This thesis outlines the definition and implementation of a systems engineering process for jet engine development and delivery at a large aerospace company. We assess how well systems engineering manages component integration issues and determine whether it sufficiently mitigates the inherent risks associated with product development in a highly distributed engineering and manufacturing environment. The Design Structure Matrix is used to critique the tasks identified in this process as well as the plan for integrating them. We then make specific recommendations regarding: a) process enhancements; and b) roles and responsibilities of the Systems Engineering Organization to help ensure the overall success of the enterprise.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Gregory J. Mascoli.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">139 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">11604633 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">11604393 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">eng</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en_US">Massachusetts Institute of Technology</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en_US">M.I.T. theses are protected by copyright. They may be viewed from this source for any purpose, but reproduction or distribution in any format is prohibited without written permission. See provided URL for inquiries about permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Sloan School of Management.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">A systems engineering approach to aero engine development in a highly distributed engineering and manufacturing environment</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dspace" element="authorsordered">false</dim:field>
   <dim:field mdschema="dspace" element="entity" qualifier="type">Publication</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="others" element="access-status">unknown</dim:field>
   <dim:field mdschema="cerif" element="openaire" authority="" confidence="-1">&lt;Publication xmlns="https://www.openaire.eu/cerif-profile/1.1/" id="d082b3cb-22b4-4f61-a09b-16ead9e23a3b">
	&lt;Type xmlns="https://www.openaire.eu/cerif-profile/vocab/COAR_Publication_Types">http://purl.org/coar/resource_type/c_1843&lt;/Type>
	&lt;Language>eng&lt;/Language>
   	&lt;Title>A systems engineering approach to aero engine development in a highly distributed engineering and manufacturing environment&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>1999&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Mascoli, Gregory J&lt;/DisplayName>
         	&lt;Affiliation>
         		&lt;OrgUnit>
         		&lt;/OrgUnit>
         	&lt;/Affiliation>
      	&lt;/Author>
	&lt;/Authors>
   	&lt;Editors>
	&lt;/Editors>
    &lt;Publishers>
        &lt;Publisher>
            &lt;DisplayName>Massachusetts Institute of Technology&lt;/DisplayName>
            &lt;OrgUnit />
        &lt;/Publisher>
    &lt;/Publishers>
    &lt;License>http://dspace.mit.edu/handle/1721.1/7582&lt;/License>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
    &lt;Keyword>Sloan School of Management.&lt;/Keyword>
   	&lt;Abstract>Engineering and Manufacturing firms face increasing pressure to continuously improve product development performance in terns of time to market, development cost, and customer satisfaction. The product development organization continues to evolve, first from a strictly functional focus to a product centric focus, and currently to some middle ground between the two extremes, where the strengths of the functional organization are recognized along with the merits of product focused teams. Almost simultaneously, many firms are becoming more distributed geographically and culturally, driven by internal and external influences including: efficiencies of co-location and outsourcing, business partnerships, joint ventures, and offset agreements. As the product development organization becomes less centralized, the challenge of integrating components into the top level system becomes much more complex relative to the time when all the components were designed and built in a relatively central location. One approach to address the increasingly critical integration issues is to develop and execute a process that encourages a system level approach to product development, a process that complements the part- and assembly-level design process. This thesis outlines the definition and implementation of a systems engineering process for jet engine development and delivery at a large aerospace company. We assess how well systems engineering manages component integration issues and determine whether it sufficiently mitigates the inherent risks associated with product development in a highly distributed engineering and manufacturing environment. The Design Structure Matrix is used to critique the tasks identified in this process as well as the plan for integrating them. We then make specific recommendations regarding: a) process enhancements; and b) roles and responsibilities of the Systems Engineering Organization to help ensure the overall success of the enterprise.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>