<?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-21T02:38:04Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/34515" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/34515</identifier><datestamp>2022-02-01T18:48:11Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>com_1721.1_80738</setSpec><setSpec>com_1721.1_1773</setSpec><setSpec>col_1721.1_131023</setSpec><setSpec>col_1721.1_80739</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">Kirkor Bozdogan.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Glazner, Christopher G</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Technology and Policy Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Technology and Policy Program</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2006-11-07T12:38:56Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2006-11-07T12:38:56Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2006</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2006</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/34515</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">70892082</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Engineering Systems Division, Technology and Policy Program, 2006.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Page 184 blank.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 179-181).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Over the last decade, many companies in industries that produce complex and technologically-advanced products have begun to integrate their operations along the value chains of the primary products they design, produce or sustain. Increasingly, integration efforts have moved beyond the boundaries of the core or focal enterprise serving as the prime contractor or system integrator to span the entire value chain, to form virtual extended enterprises. These structures allow the members of the virtual extended enterprise to focus on their core competencies in order to collaboratively deliver a world-class product at a competitive price. While integration offers many benefits to enterprises, a high degree of integration is not always desirable or advantageous in a limited duration virtual extended enterprise composed of autonomous companies. Virtual extended enterprises must find a balance between decoupled collaboration and highly coupled integration, balancing the need to closely coordinate their efforts with the need protect the autonomy of their members. The objective of this research is to explore the extent to which a focal enterprise, such as a prime contractor or system integrator, should consider integration across its virtual extended enterprise, identify major barriers to integration, and define key enablers of integration overcoming these barriers.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">(cont.) Analysis focuses on the extent of integration based on the characteristics of the virtual extended enterprise, such as the duration and scope of the program in question, product system architecture, the organizational architecture, and the external environment. In particular, three key conceptual dimensions of integration are developed and explored-technological integration, strategic integration, and organizational integration. This framework is applied in an in-depth case study of integration strategies on the virtual extended enterprise of the F-35 Joint Strike Fighter (JSF) Program. The knowledge gained from the case study is used to make recommendations for the development of integration strategies for future programs.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Christopher G. Glazner.</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">184 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">8847878 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">8855606 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">Technology and Policy Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Enterprise integration strategies across virtual extended enterprise networks : a case study of the F-35 Joint Strike Fighter Program enterprise</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="b368b3ce-1d56-466d-8791-84d46b354759">
	&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>Enterprise integration strategies across virtual extended enterprise networks : a case study of the F-35 Joint Strike Fighter Program enterprise&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2006&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Glazner, Christopher G&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>Technology and Policy Program.&lt;/Keyword>
   	&lt;Abstract>Over the last decade, many companies in industries that produce complex and technologically-advanced products have begun to integrate their operations along the value chains of the primary products they design, produce or sustain. Increasingly, integration efforts have moved beyond the boundaries of the core or focal enterprise serving as the prime contractor or system integrator to span the entire value chain, to form virtual extended enterprises. These structures allow the members of the virtual extended enterprise to focus on their core competencies in order to collaboratively deliver a world-class product at a competitive price. While integration offers many benefits to enterprises, a high degree of integration is not always desirable or advantageous in a limited duration virtual extended enterprise composed of autonomous companies. Virtual extended enterprises must find a balance between decoupled collaboration and highly coupled integration, balancing the need to closely coordinate their efforts with the need protect the autonomy of their members. The objective of this research is to explore the extent to which a focal enterprise, such as a prime contractor or system integrator, should consider integration across its virtual extended enterprise, identify major barriers to integration, and define key enablers of integration overcoming these barriers.&lt;/Abstract>
   	&lt;Abstract>(cont.) Analysis focuses on the extent of integration based on the characteristics of the virtual extended enterprise, such as the duration and scope of the program in question, product system architecture, the organizational architecture, and the external environment. In particular, three key conceptual dimensions of integration are developed and explored-technological integration, strategic integration, and organizational integration. This framework is applied in an in-depth case study of integration strategies on the virtual extended enterprise of the F-35 Joint Strike Fighter (JSF) Program. The knowledge gained from the case study is used to make recommendations for the development of integration strategies for future programs.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>