<?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-19T16:23:18Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/33323" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/33323</identifier><datestamp>2026-06-06T01:03:53Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>com_1721.1_101402</setSpec><setSpec>col_1721.1_131023</setSpec><setSpec>col_1721.1_101610</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">David L. Brock.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Locher, Maximilian Greer</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">Massachusetts Institute of Technology. Engineering Systems Division</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2006-07-13T15:15:18Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2006-07-13T15:15:18Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2005</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2005</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/33323</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">62313724</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (M. Eng. in Logistics)--Massachusetts Institute of Technology, Engineering Systems Division, 2005.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Two leaves of folded plates inserted in pocket on p. [3] of cover.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 51-52).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Inter-enterprise communication of RFID event data requires rules and consistency. To create those rules and consistency one has to understand the requirements for the event architecture. I identified fifty-one stakeholders and thirty touch points in a textile supply chain from manufacturer in China to retail in The United States. Each of the stakeholders has different requirements for accuracy of the read data. After calculating a rough estimate of data quantity, I reduced data by setting some standards for aggregation and creating a mathematical model for inference and communication of read accuracy. I discovered that by dividing data requirements into two types, summarized event data and detailed exception data and business forms, I could meet all the stakeholders' needs. The solution was to implement a hybrid publish/subscribe architecture and service oriented architecture.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Maximilian Greer Locher.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">M.Eng. in Logistics</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">52 p., [2] leaves of folded plates</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">2325659 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">2327735 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">Engineering Systems Division.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">A proposal for inter-enterprise communication of RFID event data</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="b6f72162-7b28-4104-b51d-3f1bbabdf24e">
	&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>A proposal for inter-enterprise communication of RFID event data&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2005&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Locher, Maximilian Greer&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;Abstract>Inter-enterprise communication of RFID event data requires rules and consistency. To create those rules and consistency one has to understand the requirements for the event architecture. I identified fifty-one stakeholders and thirty touch points in a textile supply chain from manufacturer in China to retail in The United States. Each of the stakeholders has different requirements for accuracy of the read data. After calculating a rough estimate of data quantity, I reduced data by setting some standards for aggregation and creating a mathematical model for inference and communication of read accuracy. I discovered that by dividing data requirements into two types, summarized event data and detailed exception data and business forms, I could meet all the stakeholders&amp;apos; needs. The solution was to implement a hybrid publish/subscribe architecture and service oriented architecture.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>