<?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-20T01:11:26Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/80986" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/80986</identifier><datestamp>2022-01-28T14:01:14Z</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">Roy Welsch and Olivier L. de Weck.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Clarke, Sarah (Sarah Kathleen)</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. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Sloan School of Management</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2013-09-24T19:35:10Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2013-09-24T19:35:10Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2013</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2013</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/80986</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">857788480</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Engineering Systems Division; and, (M.B.A.)--Massachusetts Institute of Technology, Sloan School of Management; in conjunction with the Leaders for Global Operations Program at MIT, 2013.</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 (p. 39-40).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">UTC Aerospace Systems has a wide variety of problem solving tools driven by their Achieving Competitive Excellence (ACE) program. One tool that is frequently used to resolve and capture customer escapes is the 8D methodology. It is an eight-step process designed to identify, correct, and eliminate recurring problems and is useful in providing a feedback mechanism between the customers and suppliers. Its goal is to establish a permanent corrective action and focuses on the origin of the problem by determining its root causes. The objective of the project is to fully understand the cost benefit of implementing the 8D methodology. The initial investigation of the 8D process uncovered that some defects recorded using the 8D tool are omitted in metrics reporting, leading to poor issue resolution and limited feedback between customers and suppliers. Because the tool requires additional steps that were not required in previous problem solving techniques at UTC Aerospace Systems, it is both more cost and time intensive. To avoid wasteful spending, it is therefore important that the tool be applied only when necessary. A study was performed to identify situations when the 8D tool is used improperly. Two situations were identified: (1) when an 8D investigation is performed unnecessarily and (2) when the 8D investigation is not performed in a situation when it should be. In the first situation, the unnecessary implementation of the 8D tool results in wasted effort within the organization. In the second situation, the missed opportunity to implement the tool has the potential to allow future occurrences of the same defect that may have otherwise been avoided. Preventing a defect from occurring in the future is often achieved by redesigning a part to eliminate a systemic issue. It is therefore important to use the 8D tool in order to identify systemic issues more quickly and thereby reduce future repair costs. The costs associated with these two situations are further quantified in the project.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Sarah Clarke.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">M.B.A.</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">40 p.</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 &#xd;
copyright. They may be viewed from this source for any purpose, but &#xd;
reproduction or distribution in any format is prohibited without written &#xd;
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 Systems Division.</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">Issue resolution at a large aerospace manufacturer</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="73a263d0-fcf3-4f62-acb9-8e3d33ab6295">
	&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>Issue resolution at a large aerospace manufacturer&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2013&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Clarke, Sarah (Sarah Kathleen)&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 Systems Division.&lt;/Keyword>
    &lt;Keyword>Sloan School of Management.&lt;/Keyword>
    &lt;Keyword>Leaders for Global Operations Program.&lt;/Keyword>
   	&lt;Abstract>UTC Aerospace Systems has a wide variety of problem solving tools driven by their Achieving Competitive Excellence (ACE) program. One tool that is frequently used to resolve and capture customer escapes is the 8D methodology. It is an eight-step process designed to identify, correct, and eliminate recurring problems and is useful in providing a feedback mechanism between the customers and suppliers. Its goal is to establish a permanent corrective action and focuses on the origin of the problem by determining its root causes. The objective of the project is to fully understand the cost benefit of implementing the 8D methodology. The initial investigation of the 8D process uncovered that some defects recorded using the 8D tool are omitted in metrics reporting, leading to poor issue resolution and limited feedback between customers and suppliers. Because the tool requires additional steps that were not required in previous problem solving techniques at UTC Aerospace Systems, it is both more cost and time intensive. To avoid wasteful spending, it is therefore important that the tool be applied only when necessary. A study was performed to identify situations when the 8D tool is used improperly. Two situations were identified: (1) when an 8D investigation is performed unnecessarily and (2) when the 8D investigation is not performed in a situation when it should be. In the first situation, the unnecessary implementation of the 8D tool results in wasted effort within the organization. In the second situation, the missed opportunity to implement the tool has the potential to allow future occurrences of the same defect that may have otherwise been avoided. Preventing a defect from occurring in the future is often achieved by redesigning a part to eliminate a systemic issue. It is therefore important to use the 8D tool in order to identify systemic issues more quickly and thereby reduce future repair costs. The costs associated with these two situations are further quantified in the project.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>