<?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-19T10:28:54Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/112486" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/112486</identifier><datestamp>2022-01-28T17:45:57Z</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">Olivier L. de Weck and Roy Welsch.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Good, Marissa Ann</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Leaders for Global Operations Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Leaders for Global Operations Program at MIT</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Department of Aeronautics and Astronautics</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Sloan School of Management</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2017-12-05T19:14:58Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2017-12-05T19:14:58Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2017</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2017</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/112486</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">1011503866</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M., Massachusetts Institute of Technology, Department of Aeronautics and Astronautics, in conjunction with the Leaders for Global Operations Program at MIT, 2017.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: M.B.A., Massachusetts Institute of Technology, Sloan School of Management, in conjunction with the Leaders for Global Operations Program at MIT, 2017.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Cataloged from PDF version of thesis.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (page 84).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Launch vehicle hardware is traditionally very expensive to design, develop, produce and certify, because it must operate in extreme environments with high reliability. The result is that most hardware for NASA-funded launch vehicles is custom built to execute a specific mission on a single platform. In contrast to other industries (e.g. automotive), very few components are used across product platforms, a strategy known as reuse that has the potential to decrease the cost, schedule and risk of new product introduction. Budget constraints on NASA's next launch vehicle, the Space Launch System (SLS), brought about a desire to realize some of the benefits associated with reuse. However, the reuse strategy as employed has met limited success. This brings about the fundamental question: is there something inherently unique about launch vehicle design that prevents or limits reuse? If not are there strategies that can be implemented to realize the benefits of proactive reuse during launch vehicle design? The Boeing Company, the prime contractor of the SLS cryogenic stages, would like to develop a reuse approach as they begin work on the next phase of the SLS, the Exploration Upper Stage (EUS), to improve project affordability. To develop this approach, a case study of the Core Stage (CS) was performed to identify lessons learned, resulting in the following insights: 1. Capturing the benefits of reuse is enabled by modularity and platforms within single-vehicle architectures rather than across vehicles. The time offset between any two launch vehicles is too great (20-30 year product lifecycles) for reuse across vehicles. Furthermore, manned and unmanned vehicles carry different requirements which must be considered when evaluating the potential for shared assets. 2. Race should be defined as the baseline, rather than as an opportunity. This requires aligning incentives and architecting the organization to enforce reuse from the outset. 3. Plan for forward reuse. Consider future requirements when designing the current vehicle. Reuse will not happen by coincidence; it must be designed into the system. These insights form the basis of a reuse approach for the Exploration Upper Stage (EUS). In combination with some organization and process-based suggestions, a strategy to realize the benefits of reuse has been developed for the EUS and other future launch vehicles.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Marissa Ann Good.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">M.B.A.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">84 pages</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">MIT theses are protected by copyright. They may be viewed, downloaded, or printed from this source but further reproduction or distribution in any format is prohibited without written permission.</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Aeronautics and Astronautics.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Sloan School of Management.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Leaders for Global Operations Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Developing a component reuse strategy for space launch vehicles</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="a03cf25c-0e0f-487b-9e93-e1307491cf3d">
	&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>Developing a component reuse strategy for space launch vehicles&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2017&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Good, Marissa Ann&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>Aeronautics and Astronautics.&lt;/Keyword>
    &lt;Keyword>Sloan School of Management.&lt;/Keyword>
    &lt;Keyword>Leaders for Global Operations Program.&lt;/Keyword>
   	&lt;Abstract>Launch vehicle hardware is traditionally very expensive to design, develop, produce and certify, because it must operate in extreme environments with high reliability. The result is that most hardware for NASA-funded launch vehicles is custom built to execute a specific mission on a single platform. In contrast to other industries (e.g. automotive), very few components are used across product platforms, a strategy known as reuse that has the potential to decrease the cost, schedule and risk of new product introduction. Budget constraints on NASA&amp;apos;s next launch vehicle, the Space Launch System (SLS), brought about a desire to realize some of the benefits associated with reuse. However, the reuse strategy as employed has met limited success. This brings about the fundamental question: is there something inherently unique about launch vehicle design that prevents or limits reuse? If not are there strategies that can be implemented to realize the benefits of proactive reuse during launch vehicle design? The Boeing Company, the prime contractor of the SLS cryogenic stages, would like to develop a reuse approach as they begin work on the next phase of the SLS, the Exploration Upper Stage (EUS), to improve project affordability. To develop this approach, a case study of the Core Stage (CS) was performed to identify lessons learned, resulting in the following insights: 1. Capturing the benefits of reuse is enabled by modularity and platforms within single-vehicle architectures rather than across vehicles. The time offset between any two launch vehicles is too great (20-30 year product lifecycles) for reuse across vehicles. Furthermore, manned and unmanned vehicles carry different requirements which must be considered when evaluating the potential for shared assets. 2. Race should be defined as the baseline, rather than as an opportunity. This requires aligning incentives and architecting the organization to enforce reuse from the outset. 3. Plan for forward reuse. Consider future requirements when designing the current vehicle. Reuse will not happen by coincidence; it must be designed into the system. These insights form the basis of a reuse approach for the Exploration Upper Stage (EUS). In combination with some organization and process-based suggestions, a strategy to realize the benefits of reuse has been developed for the EUS and other future launch vehicles.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>