<?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-19T00:25:14Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/35676" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/35676</identifier><datestamp>2022-01-28T21:14: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">Daniel Whitney and Roy Welsch.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Salamini, Alexey</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Leaders for Manufacturing Program.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Leaders for Manufacturing Program at MIT</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">Sloan School of Management</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2007-01-10T17:00:52Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2007-01-10T17:00:52Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2006</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2006</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/35676</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">76837699</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Dept. of Mechanical Engineering; and, (M.B.A.)--Massachusetts Institute of Technology, Sloan School of Management; in conjunction with the Leaders for Manufacturing Program at MIT, 2006.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (leaves 90-91).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The Department of Defense has issued a mandate aimed at improving its capabilities in determining the location, value, quantity, and condition of government assets. The mandate requires marking specified assemblies and components with a unique identifier using two-dimensional data matrix technology. Item Unique Identification (IUID), comprised of data matrix technology and the Unique Item Identifier (UII) data construct, was chosen to create a global standard for identification and because it showed promise in providing lifetime tracking of assets. Currently, Raytheon's implementation strategy to address the mandate has focused solely on compliance and does not aim to extract value from the IUID mandate or the UII construct. However there are many potential benefits of these capabilities. This thesis attempts to identify potential usage scenarios, determine if they are a worthwhile investment, and develop a more deliberate IUID strategy for Raytheon as a corporation within the context of the existing tracking and information landscape. It was determined that company wide pre-tax net savings of $10.6 ( 5.4) Million annually are possible from leveraging IUID technology in repair operations alone.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">(cont.) This study recommends a pilot program and if successful, to continue to leverage IUID in those repair programs with: more than 500 units processed annually, more than five workstations, and an IUID requirement in place. This study also recommends that Raytheon should not mark above contractual requirements but should encourage customers to implement IUID marking for high volume programs. This study led to additional recommendations for operations strategy at Raytheon. Automated rather than manual (keystrokes) data entry should be promoted in all operations; specifically in high volume applications. Raytheon should also make a practice of purchasing scanners that detect both bar codes and data matrices for all operations. Finally, the UII construct should be adopted in company wide operations independent of which technology (bar code, 2D Matrix, or Radio Frequency Identification (RFID)) is used to read or deliver it.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Alexey Salamini.</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">91 leaves</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">5194020 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">5197779 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</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">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">Sloan School of Management.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Leaders for Manufacturing Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Capturing value from Item Unique Identification (IUID)</dim:field>
   <dim:field mdschema="dc" element="title" qualifier="alternative" lang="en_US">Capturing value from IUID</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="b633d4b7-09fb-4d3e-9bff-515a77e0bf10">
	&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>Capturing value from Item Unique Identification (IUID)&lt;/Title>
   	&lt;Subtitle>Capturing value from IUID&lt;/Subtitle>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2006&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Salamini, Alexey&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>Sloan School of Management.&lt;/Keyword>
    &lt;Keyword>Leaders for Manufacturing Program.&lt;/Keyword>
   	&lt;Abstract>The Department of Defense has issued a mandate aimed at improving its capabilities in determining the location, value, quantity, and condition of government assets. The mandate requires marking specified assemblies and components with a unique identifier using two-dimensional data matrix technology. Item Unique Identification (IUID), comprised of data matrix technology and the Unique Item Identifier (UII) data construct, was chosen to create a global standard for identification and because it showed promise in providing lifetime tracking of assets. Currently, Raytheon&amp;apos;s implementation strategy to address the mandate has focused solely on compliance and does not aim to extract value from the IUID mandate or the UII construct. However there are many potential benefits of these capabilities. This thesis attempts to identify potential usage scenarios, determine if they are a worthwhile investment, and develop a more deliberate IUID strategy for Raytheon as a corporation within the context of the existing tracking and information landscape. It was determined that company wide pre-tax net savings of $10.6 ( 5.4) Million annually are possible from leveraging IUID technology in repair operations alone.&lt;/Abstract>
   	&lt;Abstract>(cont.) This study recommends a pilot program and if successful, to continue to leverage IUID in those repair programs with: more than 500 units processed annually, more than five workstations, and an IUID requirement in place. This study also recommends that Raytheon should not mark above contractual requirements but should encourage customers to implement IUID marking for high volume programs. This study led to additional recommendations for operations strategy at Raytheon. Automated rather than manual (keystrokes) data entry should be promoted in all operations; specifically in high volume applications. Raytheon should also make a practice of purchasing scanners that detect both bar codes and data matrices for all operations. Finally, the UII construct should be adopted in company wide operations independent of which technology (bar code, 2D Matrix, or Radio Frequency Identification (RFID)) is used to read or deliver it.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>