<?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-22T04:38:11Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/106254" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/106254</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">Steven J. Spear.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Koltookian, John H. (John Haynes)</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Engineering Systems Division.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Massachusetts Institute of Technology. Engineering 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="date" qualifier="accessioned">2017-01-06T16:14:00Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2017-01-06T16:14:00Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2016</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2016</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/106254</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">961940419</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, School of Engineering, System Design and Management Program, Engineering and Management Program, 2016.</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 97-99).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Working within a large defense company has shown me the vast array of process that is created by contractors as a response to the numbers of requirements and processes that the Department of Defense has levied on the industry. These industry processes are geared towards very large defense development projects ($100M+) and, in my experience, do not work well for smaller (&lt;$10M) rapid developments. The process does not enable contractors to get new products into the hands of warfighters expeditiously. The United States Government is aware of this and has been taking steps to create rapid procurement organizations that are empowered to develop and field new capabilities faster than the traditional process permits. These new organizations have exposed a new problem; large defense companies are so encumbered by the process they have matured that they have lost their agility and are unable to develop rapidly. How can that agility be restored within an industry where traditional process isn't fast enough anymore? Thesis Statement: An alternative process can be created within large defense companies that, when followed, allows fast and agile performance on rapid developments. This thesis explores the origin of the defense industry process, provides data showing that the current process isn't optimized and suggests an updated process that is streamlined for rapid development.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by John H. Koltookian.</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">99 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">Engineering and Management Program.</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">Engineering Systems Division.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">The Government has a method to get product to soldiers fast - big defense needs to catch up</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="aec3f9dc-ded9-46a8-8eb7-0e49c4b0d6a9">
	&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>The Government has a method to get product to soldiers fast - big defense needs to catch up&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2016&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Koltookian, John H. (John Haynes)&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>Engineering and Management Program.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
    &lt;Keyword>Engineering Systems Division.&lt;/Keyword>
   	&lt;Abstract>Working within a large defense company has shown me the vast array of process that is created by contractors as a response to the numbers of requirements and processes that the Department of Defense has levied on the industry. These industry processes are geared towards very large defense development projects ($100M+) and, in my experience, do not work well for smaller (&amp;lt;$10M) rapid developments. The process does not enable contractors to get new products into the hands of warfighters expeditiously. The United States Government is aware of this and has been taking steps to create rapid procurement organizations that are empowered to develop and field new capabilities faster than the traditional process permits. These new organizations have exposed a new problem; large defense companies are so encumbered by the process they have matured that they have lost their agility and are unable to develop rapidly. How can that agility be restored within an industry where traditional process isn&amp;apos;t fast enough anymore? Thesis Statement: An alternative process can be created within large defense companies that, when followed, allows fast and agile performance on rapid developments. This thesis explores the origin of the defense industry process, provides data showing that the current process isn&amp;apos;t optimized and suggests an updated process that is streamlined for rapid development.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>