<?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-19T23:10:16Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/90761" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/90761</identifier><datestamp>2022-01-28T15:10: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">Itai Ashlagi and Chris Caplice.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Cummings, Charles R., III (Charles Ronald)</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. 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">2014-10-08T15:27:30Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2014-10-08T15:27:30Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2014</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2014</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/90761</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">891376515</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: M.B.A., Massachusetts Institute of Technology, Sloan School of Management, 2014. In conjunction with the Leaders for Global Operations Program at MIT.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M., Massachusetts Institute of Technology, Department of Mechanical Engineering, 2014. In conjunction with the Leaders for Global Operations Program at MIT.</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 72).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Amazon is one of the world's largest retailers with revenues of $74.5 billion in 2013 and 22% growth over 2012. As Amazon continues to grow and offer greater selection, more products are flowing through an expanding inbound network. While this growth has added complexity for the inbound transportation organization, it has also created opportunities to reduce transportation cost and improve performance. Inbound transportation managed by Amazon currently represents 60% of the company's inbound freight. For this freight, Amazon uses automated shipment-planning systems to select a carrier for all shipments. The systems run once per day, selecting carriers for a set of shipment requests where each vendor has specified a freight ready date of tomorrow. Several inputs are included to achieve a low transportation cost for the network, but the systems are constrained by the vendor's freight ready date. By introducing dynamic pickup windows based on when the freight is needed in the fulfillment centers (FCs), Amazon has the opportunity to reduce transportation cost and mitigate out-of-stock occurrences. A current state analysis revealed that approximately 70% of Amazon's freight was shipped through expensive less-than-truckload and small-parcel methods. While truckload shipments are ideal in transportation, ordering smaller lots more frequently is preferable to maintain high in-stock levels in the FCs while keeping inventory holding costs low. Therefore, Amazon's shipment-planning systems minimize transportation cost by building multi-stop routes to pick up smaller shipments from several vendors before delivering to the FC. The dynamic pickup window solution changes the planning process by relaxing the constraint of tendering a shipment today to a high cost transportation mode if that freight does not need to ship today. If shipment requests are not tendered today and instead sent to tomorrow's pool of requests, two types of consolidation can occur: (1) a single-vendor consolidation and (2) a multi-vendor consolidation. A model was developed to simulate shipment planning on the entire network for one week, resulting in a 2% transportation cost reduction and 4% fewer shipments while protecting in-stock levels. Amazon piloted in late 2013 with success and plans to implement throughout the network in early 2014. While the dynamic pickup window solution is presented with Amazon as the case study, the solution is applicable to any business with stochastic demand and lead time, a large vendor base, and control of managing its inbound transportation.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Charles R Cummings, III.</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">77 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">Sloan School of Management.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Mechanical Engineering.</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">Improving the inbound supply chain through dynamic pickup windows</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="cdfe0f66-5df3-4f07-91f1-aa220f061add">
	&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>Improving the inbound supply chain through dynamic pickup windows&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2014&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Cummings, Charles R., III (Charles Ronald)&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>Sloan School of Management.&lt;/Keyword>
    &lt;Keyword>Mechanical Engineering.&lt;/Keyword>
    &lt;Keyword>Leaders for Global Operations Program.&lt;/Keyword>
   	&lt;Abstract>Amazon is one of the world&amp;apos;s largest retailers with revenues of $74.5 billion in 2013 and 22% growth over 2012. As Amazon continues to grow and offer greater selection, more products are flowing through an expanding inbound network. While this growth has added complexity for the inbound transportation organization, it has also created opportunities to reduce transportation cost and improve performance. Inbound transportation managed by Amazon currently represents 60% of the company&amp;apos;s inbound freight. For this freight, Amazon uses automated shipment-planning systems to select a carrier for all shipments. The systems run once per day, selecting carriers for a set of shipment requests where each vendor has specified a freight ready date of tomorrow. Several inputs are included to achieve a low transportation cost for the network, but the systems are constrained by the vendor&amp;apos;s freight ready date. By introducing dynamic pickup windows based on when the freight is needed in the fulfillment centers (FCs), Amazon has the opportunity to reduce transportation cost and mitigate out-of-stock occurrences. A current state analysis revealed that approximately 70% of Amazon&amp;apos;s freight was shipped through expensive less-than-truckload and small-parcel methods. While truckload shipments are ideal in transportation, ordering smaller lots more frequently is preferable to maintain high in-stock levels in the FCs while keeping inventory holding costs low. Therefore, Amazon&amp;apos;s shipment-planning systems minimize transportation cost by building multi-stop routes to pick up smaller shipments from several vendors before delivering to the FC. The dynamic pickup window solution changes the planning process by relaxing the constraint of tendering a shipment today to a high cost transportation mode if that freight does not need to ship today. If shipment requests are not tendered today and instead sent to tomorrow&amp;apos;s pool of requests, two types of consolidation can occur: (1) a single-vendor consolidation and (2) a multi-vendor consolidation. A model was developed to simulate shipment planning on the entire network for one week, resulting in a 2% transportation cost reduction and 4% fewer shipments while protecting in-stock levels. Amazon piloted in late 2013 with success and plans to implement throughout the network in early 2014. While the dynamic pickup window solution is presented with Amazon as the case study, the solution is applicable to any business with stochastic demand and lead time, a large vendor base, and control of managing its inbound transportation.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>