<?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-19T13:47:47Z</responseDate><request verb="GetRecord" identifier="oai:dspace.mit.edu:1721.1/106263" metadataPrefix="dim">https://dspace.mit.edu/server/oai/request</request><GetRecord><record><header><identifier>oai:dspace.mit.edu:1721.1/106263</identifier><datestamp>2022-01-13T07:55: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">John Williams.</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" lang="en_US">Seekins, Ryan N. (Ryan Nicholas)</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" lang="en_US">Massachusetts Institute of Technology. Engineering and Management Program</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">System Design and Management Program.</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2017-01-06T16:14:24Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2017-01-06T16:14:24Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="copyright" lang="en_US">2016</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued" lang="en_US">2016</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/1721.1/106263</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="oclc" lang="en_US">962184048</dim:field>
   <dim:field mdschema="dc" element="description" lang="en_US">Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, School of Engineering, System Design and Management Program, Engineering and Management Program, 2016.</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 (pages 92-96).</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">The number of people and things connected to the Internet continue growing at an exponential rate. This record setting growth along with the reduction in small sensor costs and machine learning enabled a concept called the Internet of Things (IoT) to thrive. With numerous applications in both commercial and government spaces, the IoT has the ability to transform any organizations network capabilities. The Air Force has a unique set of requirements centered on cyberspace superiority and the ability to command and control people and things. This paper leverages the traditional systems engineering "'V" model as a framework to develop and analyze a concept for an Air Force command and control network. Methods and tools such as stakeholder analysis, hierarchical control structures and object-process diagrams are used to develop the concept of operations, system architecture, and the preliminary design. The programs technology readiness is also assessed before outlining key milestones and deliverables required for transitioning the program forward in the acquisition life-cycle.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="statementofresponsibility" lang="en_US">by Ryan N. Seekins.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">S.M. in Engineering and Management</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent" lang="en_US">96 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">Engineering and Management Program.</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">System Design and Management Program.</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">The Internet of things applied to command and control networks</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="1d3281aa-0099-4480-928c-40ee9f1ae889">
	&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>The Internet of things applied to command and control networks&lt;/Title>
   	&lt;PublishedIn>
    	&lt;Publication>
      	&lt;/Publication>
   	&lt;/PublishedIn>
   	&lt;PublicationDate>2016&lt;/PublicationDate>
   	&lt;Authors>
      	&lt;Author>
        	&lt;DisplayName>Seekins, Ryan N. (Ryan Nicholas)&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 and Management Program.&lt;/Keyword>
    &lt;Keyword>System Design and Management Program.&lt;/Keyword>
    &lt;Keyword>Engineering Systems Division.&lt;/Keyword>
   	&lt;Abstract>The number of people and things connected to the Internet continue growing at an exponential rate. This record setting growth along with the reduction in small sensor costs and machine learning enabled a concept called the Internet of Things (IoT) to thrive. With numerous applications in both commercial and government spaces, the IoT has the ability to transform any organizations network capabilities. The Air Force has a unique set of requirements centered on cyberspace superiority and the ability to command and control people and things. This paper leverages the traditional systems engineering &amp;quot;&amp;apos;V&amp;quot; model as a framework to develop and analyze a concept for an Air Force command and control network. Methods and tools such as stakeholder analysis, hierarchical control structures and object-process diagrams are used to develop the concept of operations, system architecture, and the preliminary design. The programs technology readiness is also assessed before outlining key milestones and deliverables required for transitioning the program forward in the acquisition life-cycle.&lt;/Abstract>
	&lt;Access xmlns="http://purl.org/coar/access_right" 
    >
    &lt;/Access>
&lt;/Publication>
</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>