<?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-20T12:44:09Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/100110" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/100110</identifier><datestamp>2026-06-06T01:04:51Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131023</setSpec><setSpec>col_1721.1_131024</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">Eric Rebentisch and Joe Harbour.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">McCoy, Kathleen Marie, LCDR</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">System Design and Management Program.</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">Massachusetts Institute of Technology. Department of Mechanical Engineering</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2015-12-03T20:54:02Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2015-12-03T20:54:02Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2015</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2015</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/100110</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">929469966</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: Nav. E., Massachusetts Institute of Technology, Department of Mechanical Engineering, 2015.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2015.</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 (pages 92-95).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Contracting for US Navy ship procurement is complex due several factors such as budgetary and political concerns, sole or near sole source environments, and long lead-time construction. In the current climate of shrinking budgets, it is especially important to set programs up for financial success. One potential area for cost management improvement in acquisition programs is with the initial contract and incentive structure. If shipbuilding contracts could be described in engineering architectural terms, then perhaps that architecture could provide better clarity of contract options. Further, if contracting can be described as an engineering architecture, then perhaps that architecture could be optimized for a given result. These are the central questions of this thesis. To answer them, interviews were conducted with several experienced individuals from both industry and the government. Additionally, past shipbuilding contracts in both the US and Canada were examined. These insights were then used to form a contract architecture concept in accordance with the Tradespace engineering paradigm. From the concept definition came the design vector definition which included variables such as shareline definition, incentives, and contracted profit percentage. The tradespace was then populated by manipulating the design vector parameters. The Palisade tool [at]Risk was used to conduct the design vector manipulation and tradespace population. [at]Risk is an excel plug in that allows uncertain variables to be defined by probability distributions. The tradespace of contract outcomes was then evaluated against utilities such as cost, profit, and risk. Although the factors affecting the contracting environment are complex, and not all are modeled, quantitative modeling allows the architect to roughly evaluate different approaches, vice just basing the contract on past models. It also gives the government the ability to check whether shipbuilder furnished predicted costs are reasonable for a given contract structure.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Kathleen Marie McCoy.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">Nav.E.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M. in Engineering and Management</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">95 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">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" lang="en_US">http://dspace.mit.edu/handle/1721.1/7582</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Mechanical Engineering.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Engineering Systems Division.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Design and analysis of US Navy shipbuilding contract architecture</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">Design and analysis of United States Navy shipbuilding contract architecture</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="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="f6337b10-2081-4645-a565-134a8d615293">
	&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>Design and analysis of US Navy shipbuilding contract architecture&lt;/Title>
   	&lt;Subtitle>Design and analysis of United States Navy shipbuilding contract architecture&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2015&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>McCoy, Kathleen Marie, LCDR&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>Mechanical Engineering.&lt;/Keyword>
    &lt;Keyword>Engineering Systems Division.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>Contracting for US Navy ship procurement is complex due several factors such as budgetary and political concerns, sole or near sole source environments, and long lead-time construction. In the current climate of shrinking budgets, it is especially important to set programs up for financial success. One potential area for cost management improvement in acquisition programs is with the initial contract and incentive structure. If shipbuilding contracts could be described in engineering architectural terms, then perhaps that architecture could provide better clarity of contract options. Further, if contracting can be described as an engineering architecture, then perhaps that architecture could be optimized for a given result. These are the central questions of this thesis. To answer them, interviews were conducted with several experienced individuals from both industry and the government. Additionally, past shipbuilding contracts in both the US and Canada were examined. These insights were then used to form a contract architecture concept in accordance with the Tradespace engineering paradigm. From the concept definition came the design vector definition which included variables such as shareline definition, incentives, and contracted profit percentage. The tradespace was then populated by manipulating the design vector parameters. The Palisade tool [at]Risk was used to conduct the design vector manipulation and tradespace population. [at]Risk is an excel plug in that allows uncertain variables to be defined by probability distributions. The tradespace of contract outcomes was then evaluated against utilities such as cost, profit, and risk. Although the factors affecting the contracting environment are complex, and not all are modeled, quantitative modeling allows the architect to roughly evaluate different approaches, vice just basing the contract on past models. It also gives the government the ability to check whether shipbuilder furnished predicted costs are reasonable for a given contract structure.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>