<?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-19T18:49:12Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/17726" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/17726</identifier><datestamp>2022-01-13T07:54:48Z</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">Stephan E. Kolitz.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Koepke, Corbin G. (Corbin Gene), 1977-</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Operations Research Center.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Massachusetts Institute of Technology. Operations Research Center</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Sloan School of Management</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2005-06-02T18:24:34Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2005-06-02T18:24:34Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2004</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2004</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/17726</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">56472796</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (S.M.)--Massachusetts Institute of Technology, Sloan School of Management, Operations Research Center, 2004.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references (p. 143-145).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The United States Air Force's Air Mobility Command is responsible for creating a schedule and executing that schedule for a large-scale air mobility network that encompasses different mission areas. One of the mission areas is channel route. Channel route execution often experiences disruptions that motivate a need for changes in the current channel route schedule. Traditionally, re-planning the channel route schedule has been a manual process that usually stops after the first feasible set of changes is found, due to the challenges of large amounts of data and urgency for a re-plan. Other challenges include subjective trade-offs and a desire for minimal changes to the channel route schedule. We re-plan the channel route schedule using a set of integer programs and heuristics that overcomes these challenges. The integer programs' variables incorporate many of Air Mobility Command's operating constraints, so they do not have to be explicitly included in the formulations. The re-plan uses opportunities in the other mission areas and reroutes channel route aircraft. Finally, our methods can quickly find a solution, allow for "what-if' analysis and interaction with the user, and can be adapted to an evolution in Air Mobility Command's operations while the underlying models remain constant.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Corbin G. Koepke.</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">146 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">6381858 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">6381671 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">Operations Research Center.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Multi-mission optimized re-planning in air mobility command's channel route execution</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="07791dcc-e3a9-4c48-879b-d89d6261b4c7">
	&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>Multi-mission optimized re-planning in air mobility command&amp;apos;s channel route execution&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2004&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Koepke, Corbin G. (Corbin Gene), 1977-&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>Operations Research Center.&lt;/Keyword>
   	&lt;Abstract>The United States Air Force&amp;apos;s Air Mobility Command is responsible for creating a schedule and executing that schedule for a large-scale air mobility network that encompasses different mission areas. One of the mission areas is channel route. Channel route execution often experiences disruptions that motivate a need for changes in the current channel route schedule. Traditionally, re-planning the channel route schedule has been a manual process that usually stops after the first feasible set of changes is found, due to the challenges of large amounts of data and urgency for a re-plan. Other challenges include subjective trade-offs and a desire for minimal changes to the channel route schedule. We re-plan the channel route schedule using a set of integer programs and heuristics that overcomes these challenges. The integer programs&amp;apos; variables incorporate many of Air Mobility Command&amp;apos;s operating constraints, so they do not have to be explicitly included in the formulations. The re-plan uses opportunities in the other mission areas and reroutes channel route aircraft. Finally, our methods can quickly find a solution, allow for &amp;quot;what-if&amp;apos; analysis and interaction with the user, and can be adapted to an evolution in Air Mobility Command&amp;apos;s operations while the underlying models remain constant.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>