<?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-18T22:33:58Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/118550" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/118550</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">James M. Lyneis.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Garufi, David (David J.)</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Integrated Design and Management Program.</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">Massachusetts Institute of Technology. Integrated Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2018-10-15T20:24:50Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2018-10-15T20:24:50Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2018</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2018</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/118550</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">1055163110</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2018.</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 68).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">System dynamics modelling is used to explore varying levels of concurrency in a typical design-build-produce project introducing a new product. Faster product life-cycles and demanding schedules have introduced the importance of beginning downstream work (build/manufacturing) while upstream work (design) is incomplete. Conceivably, this project concurrency improves project schedule and cost by forcing rework to be discovered and completed earlier in the project life. Depending on the type of project, some design errors may only be discoverable once the build phase has begun its work. Namely, systemic errors and assembly errors that cannot be easily discovered within the design phase. Pushing build activity earlier in the project allows the rework to be discovered earlier in the project, shortening the overall effort required to complete the project. A mathematical simulation, created using Vensim@ system modeling software, was created by James Lyneis to simulate two-phase rework cycles. The model was tuned to match data based on a disguised real project. Various start dates (as a function of project percentage complete) for downstream phases were explored to find optimal levels of concurrency. Project types were varied by exploring three levels of "rework discoverable within the design phase" to cover a range of project types. The simulation found that for virtually all project types, significant schedule and effort benefits can be gained by introducing the downstream phase as early as 30% to 40% into the project progress and ramping downstream effort over an extended period of time.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by David Garufi.</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">93 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">Engineering and Management Program.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Integrated Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Error propagation in concurrent product development</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="f484416f-d94e-4f23-84a8-9476b8d2c4a7">
	&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>Error propagation in concurrent product development&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2018&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Garufi, David (David 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>Engineering and Management Program.&lt;/Keyword>
    &lt;Keyword>Integrated Design and Management Program.&lt;/Keyword>
   	&lt;Abstract>System dynamics modelling is used to explore varying levels of concurrency in a typical design-build-produce project introducing a new product. Faster product life-cycles and demanding schedules have introduced the importance of beginning downstream work (build/manufacturing) while upstream work (design) is incomplete. Conceivably, this project concurrency improves project schedule and cost by forcing rework to be discovered and completed earlier in the project life. Depending on the type of project, some design errors may only be discoverable once the build phase has begun its work. Namely, systemic errors and assembly errors that cannot be easily discovered within the design phase. Pushing build activity earlier in the project allows the rework to be discovered earlier in the project, shortening the overall effort required to complete the project. A mathematical simulation, created using Vensim@ system modeling software, was created by James Lyneis to simulate two-phase rework cycles. The model was tuned to match data based on a disguised real project. Various start dates (as a function of project percentage complete) for downstream phases were explored to find optimal levels of concurrency. Project types were varied by exploring three levels of &amp;quot;rework discoverable within the design phase&amp;quot; to cover a range of project types. The simulation found that for virtually all project types, significant schedule and effort benefits can be gained by introducing the downstream phase as early as 30% to 40% into the project progress and ramping downstream effort over an extended period of time.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>