<?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-21T00:38:26Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/35085" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/35085</identifier><datestamp>2022-01-31T16:20:38Z</datestamp><setSpec>com_1721.1_7582</setSpec><setSpec>com_1721.1_7581</setSpec><setSpec>col_1721.1_131022</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 A. Mindell.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Kometer, Michael W</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="other" lang="en_US">Massachusetts Institute of Technology. Technology, Management, and Policy Program.</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">Technology and Policy Program</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2006-12-18T20:04:58Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2006-12-18T20:04:58Z</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/35085</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">71300787</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis (Ph. D.)--Massachusetts Institute of Technology, Engineering Systems Division, Technology, Management, and Policy Program, 2005.</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Includes bibliographical references.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">This study answers the question, "What has been the impact of the Information Age on the Air Force's doctrinal tenet of "centralized control and decentralized execution?" It traces the evolution of command and control of airpower through operations Desert Storm, Allied Force, Enduring Freedom, and Iraqi Freedom and compares its practice with classic theories established by Huntington, Cohen, Van Creveld, and Air Force doctrine. In the absence of a peer superpower in the 1990s, U.S. decision-makers often resorted to the use of detailed constraints to gain direct influence on military operations. The more detailed the constraints from the strategic level, the closer the theater military commander held authority for planning air strikes, and the less proactive the air component was in coordinating with other components. The Air Force developed the Air Operations Center (AOC) to put together battlespace information; it is not yet possible to do this at lower levels, so the AOC has become dominant in controlling air operations. Initially resistant to get involved in ongoing missions, commanders found the AOC was needed to accomplish some "time-sensitive targeting" missions; however, they have also learn to delegate to speed up the processes.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">(cont.) But the insertion of the AOC into ongoing operations also led to distribution of tasks-where before the aircrew had performed the whole "kill chain" sequence, now the aircrew often performed only the end game tasks. This distribution could increase the potential for system accidents because people tend to drift from procedures during slack times and thus to be disintegrated when the system becomes tightly coupled. Technology has not changed the fundamental principles of command and control. The information, telecommunications, sensor and weapons technology have altered the way these humans perform their jobs, and even the jobs they perform. But commanders still need to cultivate a learning organization. Uncertainty and the coupling of diverse organizations still require that they balance empowerment with accountability by developing depth in the command relationships among their subordinates. Commanders can best gain this depth through deliberate delegation, a bruising debate, and assessment of results rather than management of specific details.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Michael W. Kometer.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">Ph.D.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">259 p.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">22050515 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">22066919 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">Technology, Management, and Policy Program.</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">Command in air war : centralized vs. decentralized control of combat airpower</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="ccea8a0e-078c-40ce-abb7-1b37de7d01f6">
	&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>Command in air war : centralized vs. decentralized control of combat airpower&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2005&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Kometer, Michael W&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>Technology, Management, and Policy Program.&lt;/Keyword>
   	&lt;Abstract>This study answers the question, &amp;quot;What has been the impact of the Information Age on the Air Force&amp;apos;s doctrinal tenet of &amp;quot;centralized control and decentralized execution?&amp;quot; It traces the evolution of command and control of airpower through operations Desert Storm, Allied Force, Enduring Freedom, and Iraqi Freedom and compares its practice with classic theories established by Huntington, Cohen, Van Creveld, and Air Force doctrine. In the absence of a peer superpower in the 1990s, U.S. decision-makers often resorted to the use of detailed constraints to gain direct influence on military operations. The more detailed the constraints from the strategic level, the closer the theater military commander held authority for planning air strikes, and the less proactive the air component was in coordinating with other components. The Air Force developed the Air Operations Center (AOC) to put together battlespace information; it is not yet possible to do this at lower levels, so the AOC has become dominant in controlling air operations. Initially resistant to get involved in ongoing missions, commanders found the AOC was needed to accomplish some &amp;quot;time-sensitive targeting&amp;quot; missions; however, they have also learn to delegate to speed up the processes.&lt;/Abstract>
   	&lt;Abstract>(cont.) But the insertion of the AOC into ongoing operations also led to distribution of tasks-where before the aircrew had performed the whole &amp;quot;kill chain&amp;quot; sequence, now the aircrew often performed only the end game tasks. This distribution could increase the potential for system accidents because people tend to drift from procedures during slack times and thus to be disintegrated when the system becomes tightly coupled. Technology has not changed the fundamental principles of command and control. The information, telecommunications, sensor and weapons technology have altered the way these humans perform their jobs, and even the jobs they perform. But commanders still need to cultivate a learning organization. Uncertainty and the coupling of diverse organizations still require that they balance empowerment with accountability by developing depth in the command relationships among their subordinates. Commanders can best gain this depth through deliberate delegation, a bruising debate, and assessment of results rather than management of specific details.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>