<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://digitalprojects.uah.edu/items?output=omeka-xml&amp;page=265&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-04-20T22:01:59+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>265</pageNumber>
      <perPage>20</perPage>
      <totalResults>8242</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="14993" public="1" featured="0">
    <fileContainer>
      <file fileId="11601">
        <src>https://digitalprojects.uah.edu/files/original/204/14993/Hydrogenase_a_bacterial_enzyme_activating_molecular_hydrogen.jpg</src>
        <authentication>e09705a350c0a8abb58da9d52aa8b5b5</authentication>
      </file>
    </fileContainer>
    <collection collectionId="204">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="216150">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="216151">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222996">
                <text>Hydrogenase: a bacterial enzyme activating molecular hydrogen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222997">
                <text>Van Rensselaer, Miranda</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="222998">
                <text>Hydrogenase: a bacterial enzyme activating molecular hydrogen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222999">
                <text>This document is a copy of one of Marjory Stephenson's, along with her colleague L.H. Strickland, most important papers, the discovery of the hydrogenase enzyme. It is just one of her many research papers on enzymes that laid the foundation for detailed studies of metabolism, both in bacteria and higher-level organisms. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="223000">
                <text>2025-05-2</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="223001">
                <text>Miranda Van Rensselaer&#13;
HON 399 Study Abroad in London&#13;
Spring 2025</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="223002">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="223003">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9461" public="1" featured="0">
    <fileContainer>
      <file fileId="8236">
        <src>https://digitalprojects.uah.edu/files/original/17/9461/Friday_September_28_2018_at_10_34_25_AM_default_122089af.mp4</src>
        <authentication>df649eabe8313ace025f36733a17e556</authentication>
      </file>
    </fileContainer>
    <collection collectionId="17">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="178">
                  <text>Oral History Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17144">
                  <text>Oral History Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201666">
                  <text>The University of Alabama in Huntsville's Oral History Collection contains oral interviews with the men responsible for some of America's greatest achievements in outer space and the individuals who helped make UAH what it is now.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="143281">
                <text>Friday__September_28__2018_at_10_34_25_AM_default_122089af</text>
              </elementText>
              <elementText elementTextId="143282">
                <text>MC_136_</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143283">
                <text>Oral History Interview With Charles Van Valkenburg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143284">
                <text>Charles Van Valkenburg grew up in Huntsville, AL, and he went to Auburn University. There, he majored in Industrial Design and he had a part-time job as a draftsman at one of the civil engineering firms. After graduating college, he received a job at Essex in Huntsville. At this job, Charles would get in the water of the Neutral Buoyancy Tank and make sure that all the tools and everything was in place for an astronaut. Sometimes, he would even be the test subject. After all the testing from the day, they would all have a debriefing session at this company where the astronaut, human factors experts, and engineers would all make inputs. After the debriefing, they would take the ideas and get the machinists to make some modifications to the hardware. Charles would also work in pressure suits, and he explains how restricted the suit made him feel. He also mentions the foot restraints, and how difficult they were to work with. In his career, Charles was also able to help design the underwater version of the manned maneuvering unit.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143285">
                <text>Van Valkenburg, Charles</text>
              </elementText>
              <elementText elementTextId="143286">
                <text>Stokes, Jack</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143287">
                <text>2018-09-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143289">
                <text>Space simulators</text>
              </elementText>
              <elementText elementTextId="143290">
                <text>Astronautics--Human factors</text>
              </elementText>
              <elementText elementTextId="143291">
                <text>Space suits</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143292">
                <text>.MP4</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143293">
                <text>Interviews</text>
              </elementText>
              <elementText elementTextId="143294">
                <text>Video</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="143295">
                <text>Oral History Collection</text>
              </elementText>
              <elementText elementTextId="143296">
                <text>University of Alabama in Huntsville Archives and Special Collections</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143297">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143298">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="143321">
                <text>2010-2019</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12">
        <name>Oral History</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="14825" public="1" featured="0">
    <fileContainer>
      <file fileId="11405">
        <src>https://digitalprojects.uah.edu/files/original/204/14825/oakshott-birthsite-brown.jpeg</src>
        <authentication>d3f2b60cfe3f8f62460abad507fb9720</authentication>
      </file>
    </fileContainer>
    <collection collectionId="204">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="216150">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="216151">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221649">
                <text>Home of Mary Wollstonecraft marked by brown plaque</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221650">
                <text>Vanderwaal, Sophia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="221651">
                <text>oakshott-birthsite-brown</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221652">
                <text>Home of Mary Wollstonecraft marked by brown plaque in Oakshott Court. Plaque reads "In a house on this site lived Mary Wollstonecraft, author of "A Vindication of the Rights of Woman", 1759 - 1797. Camden London Borough Council." This is the location where Mary Shelley was born and Mary Wollstonecraft died. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221653">
                <text>2025-03-13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="221654">
                <text>Sophia Vanderwaal, HON 399 Study Abroad in London, Spring 2025</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221655">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221656">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14827" public="1" featured="0">
    <fileContainer>
      <file fileId="11407">
        <src>https://digitalprojects.uah.edu/files/original/204/14827/mary-percy-blue.jpeg</src>
        <authentication>27895c305335d8e4669397bbabc71df5</authentication>
      </file>
    </fileContainer>
    <collection collectionId="204">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="216150">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="216151">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221665">
                <text>Home of Percy Shelley and Mary Shelley marked by blue plaque</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221666">
                <text>Vanderwaal, Sophia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="221667">
                <text>mary-percy-blue</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221668">
                <text>Home of Percy Shelley and Mary Shelley marked by a blue plaque in London, England. Plaque reads "Percy / Bysshe Shelley / 1792-1822 / Poet &amp; Radical Thinker /  &amp; /  Mary Shelley / 1797-1851 / Author of Frankenstein / lived in a house / on this site / 1815-1816." Photo taken by Sophia Vanderwaal</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221669">
                <text>2025-03-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="221670">
                <text>Sophia Vanderwaal&#13;
HON 399 Study Abroad in London&#13;
Spring 2025</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221671">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221672">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14828" public="1" featured="0">
    <fileContainer>
      <file fileId="11408">
        <src>https://digitalprojects.uah.edu/files/original/204/14828/mary-shelley-blue.jpeg</src>
        <authentication>23b4d1de69dab61dd39d6c60aa9740ab</authentication>
      </file>
    </fileContainer>
    <collection collectionId="204">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="216150">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="216151">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221673">
                <text>Home of Mary Shelley marked by blue plaque</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221674">
                <text>Vanderwaal, Sophia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="221675">
                <text>mary-shelley-blue</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221676">
                <text>Home of Mary Shelley marked by blue plaque in London, England. Plaque reads "MARY SHELLEY 1797-1851 Author of Frankenstein lived here 1846-1851." Photo taken by Sophia Vanderwaal.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221677">
                <text>2025-03-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="221678">
                <text>Sophia Vanderwaal&#13;
HON 399 Study Abroad in London&#13;
Spring 2025</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221679">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221680">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14835" public="1" featured="0">
    <fileContainer>
      <file fileId="11421">
        <src>https://digitalprojects.uah.edu/files/original/204/14835/mary-wollstonecraft-grave.jpeg</src>
        <authentication>8279459b4a13214db47054720880e298</authentication>
      </file>
      <file fileId="11422">
        <src>https://digitalprojects.uah.edu/files/original/204/14835/mary-jane-godwin-grave.jpeg</src>
        <authentication>da11957eb676607ea338df5b0abc7a64</authentication>
      </file>
      <file fileId="11423">
        <src>https://digitalprojects.uah.edu/files/original/204/14835/william-godwin-grave.jpeg</src>
        <authentication>3442de8eda840f234e6ae07cc8143d85</authentication>
      </file>
    </fileContainer>
    <collection collectionId="204">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="216150">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="216151">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221740">
                <text>Tomb of Mary Wollstonecraft Godwin, William Godwin, and Mary Jane Godwin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221741">
                <text>Vanderwaal, Sophia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="221742">
                <text>mary-wollstonecraft-grave</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221743">
                <text>Three sides of a grave stone for Mary Wollstonecraft Godwin, William Godwin, and Mary Jane Godwin. The inscriptions are faded, the faces of the grave stone worn. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221744">
                <text>2025-03-12</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="221745">
                <text>Sophia Vanderwaal&#13;
HON 399 Study Abroad in London&#13;
Spring 2025</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221746">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="221747">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14916" public="1" featured="0">
    <fileContainer>
      <file fileId="11520">
        <src>https://digitalprojects.uah.edu/files/original/204/14916/serpentine-photo.jpeg</src>
        <authentication>29d5032b418f51983e1201b08c52e508</authentication>
      </file>
    </fileContainer>
    <collection collectionId="204">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="216150">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="216151">
                  <text>HON 399 Research in London</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222442">
                <text>Photo of the Serpentine in Hyde Park, London, England</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222443">
                <text>Vanderwaal, Sophia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="222444">
                <text>serpentine-photo</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222445">
                <text>Photo of the Serpentine Lake in Hyde Park, London England. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222446">
                <text>2025-03-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="222447">
                <text>Sophia Vanderwaal&#13;
HON 399 Study Abroad in London&#13;
Spring 2025</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222448">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="222449">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1141" public="1" featured="0">
    <fileContainer>
      <file fileId="988">
        <src>https://digitalprojects.uah.edu/files/original/20/1141/spc_stnv_000057.pdf</src>
        <authentication>dd110f801b9cebaa3dc3698b49514d40</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177275">
                    <text>March 1, 1963

SATURN HISTORY DOCUMENT
Uniues&amp;cy of Alabama

~ w f ~ S e i w

-&amp;

ALIGNMENT TOOL AIDS
IN

�Development of a two-piece mechanical alignment tool has solved a major
problem for welding large, ukusual contoured skin sections. Massive mechanical, pneumatic, or hydraulically-operated devices are no longer required for
- *-

effecti~e-tankwall alignment.
The tool, a manually attached device, can be positioned along the weld
line at any interval dictated by the material thickness or rigidity of the
parent metals.

A one-inch wide (.005 inch thick) steel band connects the two aligning
members of the tool. This steel band will serve as the medium by which the

' workpieces will be brought into alignment. The steel band is firmly secured
to the clamp (with shearing mechanism), passed between the two workpieces
at the weld line and attached to the takeup spool.

This slotted spool attached

o a takeup block, is used to remove the slack in the steel band. A shaft
1

-

to which the take*:hlock

is attached is used to apply sufficient force to

-----.

The steel band is__secwed
to the clamp by threading
---

align the workpieces.

_
I

it over and under two dowels in such a manner that when pressure from the
spool is applied, the friction of the band itself will hold it fi&amp;ly
place on the dowels.

in

'

A single thickness af the band will withstand a pull of 850 pounds and
a double thickness will withstand approximately 1500 pounds.

In order to

realize proper tension on the band, a torque wrench is used.

A detachable

�-adapter,which serves as the attaching point for the torque wrench, is mounted
- --

on the clamping lever.

-- .

-

-

Attaching the alignment tool to the workpieces can be accomplished more

----------

-

easily when two- operators are used.

One operator threads the steel band onto

the d o w e l s - b n ~ p - t e - s e c u r e it. He then positions the clamp while
passing the band between the workpieces. The operator on the opposite side
of the workpiece receives the band, feeds the band into the slotted takeup
spool, and turns the takeup spool until the two clamping members are brought
into contact with the workpiece surfaces.

Necessary power to force the work-

pieces into proper alignment is then applied through operating the clamping
.lever.

..

An arm member or handle, designed in the clamp, serves as an instru-

ment of instant disengagement. When this a h is depressed, it will actuate a
shearing mechanism within the clamp, thereby cutting the steel band and releasing the entire tool from the workpiece.

During the welding operation it

is essential that the alignment tool be disengaged just a h e a h e h e welder
1
.

to eliminate interference with the seam tracking device.
In fabricating the large diameter tanks for the Saturn V Booster, hori-

-

zontal, vertical, and circumferential welds must be performed on materials
- - -o ? - ~ &amp; ~ i nthicknesses
~
and contours. Since this tool applies its aligning
force in a localized area and can be attached to the workpieces anywhere
required, its application and use is not dictated by any size or contour.

This

tool is also used during welding of outlet fittings where large or bulky holddown devices would make it virtually inaccessible for the welder to perform.

�This alignment tool was designed by Mr. W. J. Franklin, chief-of
Structures Engineering Branch, and Mr. N. C. Martin, Chief of Tool Engineering
I

Section.

These two organizations are part of the Manufacturing Engineering

Division at NASA's George C. Marshall Space Flight Center, Huntsville,
A1 abama.

�IDEAS-

MECHANICAL

Clamping Tool
Aligns Odd-Shaped Sections for Welding
Margaret A. Maas, Southeastern Editor

Alignment of large and unusually contoured
sections for welding purposes can be achieved
by a two-piece, manually operated tool.
The tool is a clamping device connected by
a 1-inch-wide (0.005-inch-thick) steel band.
The steel band is threaded over and under two
dowels in such a manner that when tension
is applied to the band, the friction of the band
itself holds it in place. The band is passed 'between the sections being clamped and fed into
a slotted takeup spool, which is turned until
the two clamping members contact the work-

ing surfaces. A torque wrench used on a shaft
mounted to the takeup spool block applies
sufficient force to align the piece.
A single band will withstand a pull of 850
lb and a double-thickness band, 1500 lb. Band
is sheared just ahead of welder by depressing
a shear arm designed into the clamp.
The alignment tool was designed by W. J.
Franklin and N. C. Martin of NASA's George
C. Marshall Space Flight Center, Huntsville,
Ala.

U
DESIGN

NEWS-SEPTEMBER

4,

1 9 6 3

CLAMPING TOOL aligns outlet fitting for weldii

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20029">
                <text>spc_stnv_000057</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20030">
                <text>"Alignment Tool Aids in Large Tank Fabrication."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20031">
                <text>Includes the clipping "Clamping Tool Aligns Odd-Shaped Sections for Welding" from &lt;i&gt;Design News&lt;/i&gt;, September 4, 1963, written by Margaret A. Maas.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20032">
                <text>Vardaman, W. K.</text>
              </elementText>
              <elementText elementTextId="20033">
                <text>George C. Marshall Space Flight Center</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20034">
                <text>1967-03</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20035">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20036">
                <text>Saturn Project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20037">
                <text>Liquid propellant rockets--Fuel tanks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20038">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="20039">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20040">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20041">
                <text>Box 8, Folder 19</text>
              </elementText>
              <elementText elementTextId="205808">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20043">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20044">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20045">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="48" public="1" featured="0">
    <fileContainer>
      <file fileId="48">
        <src>https://digitalprojects.uah.edu/files/original/7/48/loc_mshc_0000047_web.pdf</src>
        <authentication>fdc8fe1ef0607c8600063fe5f5473c7b</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="176594">
                    <text>�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="7">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="57">
                  <text>Jane Barr Monte Sano Historical Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3771">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/37"&gt;View the Jane Barr Monte Sano Historical Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17163">
                  <text>Jane Barr Monte Sano Historical Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="745">
                <text>loc_mshc_000047</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="746">
                <text>Topographical map of Monte Sano.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="747">
                <text>This map was drawn by William W. Varnedoe, Jr. and published by the Monte Sano Civic Association. It shows Monte Sano's neighborhoods, the state park, and the mountain's natural features, including springs and caves. The map also notes changes in elevation. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="748">
                <text>Varnedoe, William W., Jr.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="749">
                <text>1956</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="750">
                <text>1950-1959</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="751">
                <text>Huntsville (Ala.)--Maps</text>
              </elementText>
              <elementText elementTextId="781">
                <text>Monte Sano State Park (Ala.)</text>
              </elementText>
              <elementText elementTextId="782">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="1055">
                <text>Madison County (Ala.)</text>
              </elementText>
              <elementText elementTextId="8401">
                <text>Monte Sano Mountain (Huntsville, Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="752">
                <text>Maps</text>
              </elementText>
              <elementText elementTextId="1136">
                <text>Topographic maps</text>
              </elementText>
              <elementText elementTextId="30122">
                <text>Still Image</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="755">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="757">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="758">
                <text>loc_mshc_2018</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="969">
                <text>Monte Sano Historical Collection</text>
              </elementText>
              <elementText elementTextId="205277">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="8217" public="1" featured="0">
    <fileContainer>
      <file fileId="7134">
        <src>https://digitalprojects.uah.edu/files/original/123/8217/r04a04-22.pdf</src>
        <authentication>183cc4c7bddf114c88c850e480ec5212</authentication>
      </file>
    </fileContainer>
    <collection collectionId="123">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="133745">
                  <text>Series 04, Subseries A: Huntsville History</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="133746">
                  <text>Series 04, Subseries A: Huntsville History</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="135494">
                <text>r04a04-22</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="135495">
                <text>Frances Cabaniss Roberts Collection</text>
              </elementText>
              <elementText elementTextId="185040">
                <text>Series 4, Subseries A, Box 4, Folder 22</text>
              </elementText>
              <elementText elementTextId="209742">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="135496">
                <text>Smith, Carlos</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="135497">
                <text>r04a-210924</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185033">
                <text>Varner, Sarah A.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185034">
                <text>1951-12-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="185035">
                <text>1950-1959</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185036">
                <text>History–Sources</text>
              </elementText>
              <elementText elementTextId="185037">
                <text>Smith, Cartlos Greene</text>
              </elementText>
              <elementText elementTextId="185038">
                <text>University of Alabama–History</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185039">
                <text>Correspondence</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185042">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="185043">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1147" public="1" featured="0">
    <fileContainer>
      <file fileId="994">
        <src>https://digitalprojects.uah.edu/files/original/20/1147/spc_stnv_000063.pdf</src>
        <authentication>4f6b05a7994bd629cc076c96c8443e3d</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177281">
                    <text>SATURY UlSTORY DOCUMENT
University of Alabama Research Institute
Histofy OF Science &amp; Techrloloyy Group

--

Date - - - - - . - - - - DOC NO. - - -"ANALYSIS AND PROJECTIONS O F S P A C E VEHICLE
AUTOMATIC CHECKOUT ANC L 4UNCH"

by
C. R. Vedane
T e c h n i c a l S y s t e m s Office
G e o r g e C. M a r s h a l l Space Flight C e n t e r
Huntsville. 41a b a m a

-I

b
1

INTRODUCTION
At t h e t i m e t h e d e c i s i o n w a s m a d e t o apply a u t o m a t i c techniques t o
t h e p r o c e s s of checking out and launching a S a t u r n v e h i c l e , t h e t o t a l
o p e r a t i o n w a s u n d e r m a n u a l c o n t r o l . C o n s i d e r a b l e a d v a n c e s have been
m a d e i n t h e t r a n s i t i o n f r o m m a n u a l t o c o m p u t e r c o n t r o l . The purpose
of t h i s p a p e r i s t o p r e s e n t a projection of the i m p r o v e m e n t s t h a t m u s t
be m a d e b e f o r e m a x i m u m benefits c a n be obtained f r o m t h e a u t o m a t i o n
e f f o r t . A brief d e s c r i p t i o n i s given of t y p i c a l checkout o p e r a t i o n s and
of t h e evolution of h a r d w a r e . With t h i s a s background, a n a n a l y s i s i s
m a d e of t h e i m p l e m e n t a t i o n p r o b l e m s e x p e r i e n c e d in a u t o m a t i o n ; and
f i n a l l y , f r o m t h i s a n a l y s i s p r o j e c t i o n s a r e d e r i v e d and s t a t e d .
CHECKOUT OPER 4TIONS
As s t a t e d above, t h i s s e c t i o n p r e s e n t s a brief d e s c r i p t i o n of t h e
t e s t i n g o p e r a t i o n . No a t t e m p t i s m a d e t o d e s c r i b e a l l of the i n t r i c a c i e s
of t h e t a s k s i n c e t h i s i s not t h e t h e m e of t h e p a p e r . The p u r p o s e i s t o
e x p o s e t h e r e a d e r t o the p a r a m e t e r s which m u s t be c o n t r o l l e d and
m o n i t o r e d , plus provide a g e n e r a l u n d e r s t a n d i n g of t h e n a t u r e of t h e
o p e r a t i o n . T h i s i s n e c e s s a r y f o r the r e a d e r t o u n d e r s t a n d t h e h a r d w a r e r e q u i r e m e n t s and s u b s e q u e n t a n a l y s i s s e c t i o n .
F i g u r e 1 i s u s e d t o a i d t h e a c c o m p l i s h m e n t of t h i s objective. It
d o e s not r e p r e s e n t a n y s p e c i f i c t e s t p r o g r a m ( s u c h a s post-manufacturing
c h e c k o u t , s t a t i c f i r i n g , e t c . ) but p r e s e n t s the g e n e r a l s t r u c t u r e of a l l
t e s t o p e r a t i o n s . P r e s e n t e d a r e t h e v a r i o u s s y s t e m s t e s t s which a r e
gene r a l l y p e r f o r m e d c o n c u r r e n t l y , followed by t y p i c a l combined s y s t e m s
tests.
T h e following d i s c u s s i o n w i l l d e s c r i b e t h e t y p e s of s i g n a l s involved a n d g r o s s l y t h e i r a r r a n g e m e n t .

�T h e n e t w o r k s a r e u s u a l l y defined a s t h e c i r c u i t r y w h i c h c o n t r o l s ,
m o n i t o r s , a n d s u p p l i e s power t o t h e v a r i o u s black boxes u s e d i n t h e
vehicle. In performing control functions, this c i r c u i t r y usually applies
o r r e m o v e s d . c . v o l t a g e t o o r f r o m t h o s e b l a c k boxes a c c o r d i n g t o
p a r t i c u l a r s e q u e n c e a n d / o r s e t of l o g i c . In doing s o , i t a c c o m p l i s h e s
s u c h o p e r a t i o n s a s ; s t a r t , cutoff a n d s a f i n g , m a l f u n c t i o n d e t e c t i o n ,
s e p a r a t i o n , d e s t r u c t , e t c . T h e m o n i t o r i n g f u n c t i o n c o n s i s t s of providing
high r e s o l u t i o n , r e l i a b l e , r e a l - t i m e i n f o r m a t i o n t o t h e g r o u n d s y s t e m s
and personnel. This information, a s with the control functions, i s u s u a l l y i n t h e f o r m of 2 8 v o l t s i g n a l s w h i c h a r e n e i t h e r on o r off. E a c h
of t h e c i r c u i t s m u s t be v e r i f i e d t o i n s u r e t h a t e a c h c o m p o n e n t w i l l p e r f o r m i t s intended function without interfering with other c i r c u i t s .
D u r i n g t h e t e s t s of t h e o t h e r s y s t e m s , d i f f e r e n t t y p e s of s i g n a l s
a r c e n c o u n t e r e d . T h e g u i d a n c e a n d c o n t r o l c h e c k s r e q u i r e being a b l e
to apply simulated e r r o r signals to the stabilized nlatform, r a t e gyros,
c o n t r o l a c c e l e r o m e t e r s a n d o t h e r e r r o r s e n s i n g d e v i c e s . The r e s p o n s e
f r o m these devices m u s t b e m e a s u r e d simultaneously with the application
of t h e s t i m u l i t o c h e c k t h e c a l i b r a t i o n . In m o s t c a s e s t h e s e s i g n a l s a r e
a n a l o g , c o n s i s t i n g of v a r i o u s v o l t a g e s a n d f r e q u e n c i e s ; c o m m u n i c a t i o n
w i t h t h e c o m p u t e r i s v i a a d i g i t a l l i n k , r e p r e s e n t i n g a n o t h e r t y p e of
s i g n a l . In i t s v e r i f i c a t i o n v a r i o u s d i a g n o s t i c r o u t i n e s m u s t be p e r f o r m e d , plus v e r i f y i n g t h e i n t e r f a c i n g of t h i s e q u i p m e n t w i t h t h e o t h e r
f u n c t i o n a l e l e m e n t s of t h e g u i d a n c e a n d c o n t r o l s y s t e m s . T h i s r e q u i r e s
the capability to handle, i n s o m e c a s e s , the s a m e analog p a r a m e t e r s
a s previously mentioned and i n other c a s e s , d i s c r e t e signals which
o p e r a t e v a r i o u s c o m p o n e n t s on t h e v e h i c l e v i a t h e s w i t c h s e l e c t o r .
T e s t i n g of t h e i n s t r u m e n t a t i o n a n d R F ( r a d i o f r e q u e n c y ) s y s t e m s
r e p r e s e n t s t i l l a n o t h e r t y p e of o p e r a t i o n . V e r i f i c a t i o n of t h e TM ( t e l e m e n t r y ) p a c k a g e s r e q u i r e s o s c i l l a t o r a d j u s t m e n t , p o w e r output c h e c k s ,
etc. ; and the R F packages requires frequency interrogation, 4GC checks
plus VSWR on a l l a n t e n n a e . As f a r a s t h e p a r a m e t e r s a r e c o n c e r n e d
on t h e input t o t h e T M p a c k a g e , t h e y a r e not a n y d i f f e r e n t (with t h e e x c e p t i o n of v i b r a t i o n m e a s u r e m e n t s ) i n t y p e t h a n e n c o u n t e r e d i n t h e o t h e r
s y s t e m s . The differences a r e in the acquisition and processing methods
T h e p r i m a r y function of t h e i n s t r u m e n t a t i o n s y s t e m i s t o m o n i t o r t h e
p e r f o r m a n c e of t h e o t h e r s y s t e m s . T h e r e f o r e , t h e v e r i f i c a t i o n m u s t
be a c c o m p l i s h e d d u r i n g t h e t e s t i n g of t h e s e s y s t e m s . C o n s e q u e n t l y ,
a highly i n t e g r a t e d a n d c o o r d i n a t e d o p e r a t i o n i s n e c e s s a r y .

�Testing the mechanical s y s t e m s requires the capability t o control
D r e s s u r e t o the v a r i o u s pneumatic and propellant s y s t e m s , verify
e n g i n e s , both m e c h a n i c a l l y a n d e l e c t r i c a l l y , e t c . The p a r a m e t e r s i n volved i n s u c h a n o p e r a t i o n r u n t h e g a m u t . An a d d i t i o n a l a t t r i b u t e of
t h i s o p e r a t i o n i s s a f e t y , t h u s r e q u i r i n g continuous m o n i t o r i n g of c e r t a i n
parameters.
In t h e c o m b i n e d s y s t e m s t e s t s , t h e o p e r a t i o n c h a n g e s f r o m p a r a l l e l
t o s e r i e s . With e x c e p t i o n of a c t u a l l y loading p r o p e l l a n t s , no new p a r a m e t e r s a r e i n v o l v e d ; h o w e v e r , t h e whole n a t u r e of t h e o p e r a t i o n c h a n g e s .
The specific s y s t e m s t e s t s have the p r i m a r y objective t o verify the int e r n a l f u n c t i o n s of e a c h s y s t e m . The p r i m a r y o b j e c t i v e of t h e c o m b i n e d
s y s t e m s t e s t s i s t o a s s u r e t h a t t h e r e a r e no i n t e r f a c i n g p r o b l e m s a m o n g
t h e s y s t e m s . E a c h of t h e c o m b i n e d s y s t e m s t e s t s h a s d i f f e r e n t o b j e c t i v e s , but t h e c o m m o n a s p e c t i s t h a t a l l of t h e s y s t e m s a r e o p e r a t i n g i n
a n itt egrated fashion. This requires that the total operational sequence
be p r e - p l a n n e d a n d t h a t e a c h s y s t e m e n g i n e e r h a v e t h e c a p a b i l i t y t o
know t h e p e r f o r m a n c e of h i s s y s t e m .
MANUAL HARDW ARE REQUIRED
T u r n i n g t o t h e GSE r e q u i r e d t o p e r f o r m t h e m a n u a l t e s t i n g o p e r a t i o n ,
F i g u r e 2 r e p r e s e n t s a typical testing complex. The figure depicts the w a y i n w h i c h t h e G S E i s o r g a n i z e d , by s y s t e m s , a n d t h e v a r i o u s t y p e s
of s i g n a l s d e s c r i b e d p r e v i o u s l y . I n g e n e r a l , t h e f i g u r e i s p r e t t y s e l f e x p l a n a t o r y . E a c h t e s t e n g i n e e r c o n t r o l s h i s s y s t e m v i a p a n e l s equipped
with switches f o r s t i m u l i a n d m e t e r s and lights for r e s p o n s e monitoring.
H o w e v e r , t h e o p e r a t i o n involving t h e i n s t r u m e n t a t i o n s y s t e m m a y r e .
q u i r e e l a b o r a t i o n . T o i n s u r e t h e c a l i b r a t i o n of t h e m e a s u r e m e n t s , i t i s
f i r s t n e c e s s a r y t o c h e c k f r o m t h e t r a n s d u c e r t h r o u g h t h e s i g n a l conditioni n g , w h i c h i s a c c o m p l i s h e d by obtaining a h a r d w i r e r e c o r d i n g . T h e
m e a s u r e m e n t i s then switched to the telemetry s y s t e m and a recording
i s o b t a i n e d v i a R F link. T h e s e r e c o r d i n g s a r e t h e n c o m p a r e d t o i n s u r e
a c c u r a c i e s of t h e T M s y s t e m .
l
T h e a n i m a t i o n p o r t i o n of t h e f i g u r e d e p i c t s how t h e t e s t i n g o p e r a t i o n
i s coordinated and conducted. E a c h s y s t e m engineer i s responsible for
h i s s y s t e m s w i t h t h e t o t a l o p e r a t i o n being d i r e c t e d by a t e s t c o n d u c t o r .
REASONS F O R AUTOMATION
It m i g h t s e e m a p p r o p r i a t e a n d helpful a t t h i s point t o a s k t h e q u e s t i o n
"If t h e h a r d w a r e n e c e s s a r y t o a c c o m p l i s h t h e job i s a v a i l a b l e , why

�develop complex digital equipment t o automate the proces s t ' ? The
basic r e a s o n s a r e found in the design concept and m i s s i o n r e q u i r e m e n t s
of the S a t u r n v e h i c l e s . F r o m the d e s i g n viewpoint, the concept is a
staging a p p r o a c h with e a c h s t a g e being developed a t a different location
i n t h e United S t a t e s . F r o m a m i s s i o n viewpoint the s a m e basic vehicle
m u s t be a b l e t o a c c o m p l i s h varying m i s s i o n s with v a r y i n g launch r a t e s .
T o provide the capability t o i n t e g r a t e t h e s e s t a g e s into a launch vehicle
a t t h e launch s i t e and provide the n e c e s s a r y m i s s i o n flexibility a n onboard c o m p u t e r s e e m e d t o be the a n s w e r .
In addition, the data r e q u i r e m e n t s t o v e r i f y a s t a g e w e r e becoming
quite voluminous. T h e r e a r e two c o n s i d e r a t i o n s to this point. F i r s t ,
i s t k d a t a n e c e s s a r y on a r e a l - t i m e b a s i s during the t e s t i n g operation.
Second, i s the d a t a that needs t o be analyzed, but t h i s a n a l y s i s c a n be
p e r f o r m e d a f t e r the t e s t i s completed. F i g u r e 2 shows the t e s t engineeF
a s t h e m e a n s of accomplishing the data a n a l y s i s i n a r e a l - t i m e situation
As t h e s y s t e m s become l a r g e r and m o r e complex, m o r e people a r e
involved. This i n c r e a s e s the complexity of the coordination n e c e s s a r y
t o a c c o m p l i s h the t e s t i n g operation. 4 c o m p u t e r has the capability to
monitor a l l of t h e data points, c o m p a r e the a c c u r a c i e s , i s s u e subs e q u e n t c o m m a n d s , a n d c o o r d i n a t e t h e p e r f o r m a n c e of l a r g e t e s t s
than the e n g i n e e r s involved. S i m i l a r l y , t h e magnitude of the off-line
data a n a l y s i s t a s k i n c r e a s e d , which a c o m p u t e r c a n p e r f o r m much
faster.
In the data gathering and p r o c e s s i n g , t h e r e a r e s o m e r e a l advantag e s t o be gained f r o m automation concerning a c c u r a c y and repeatibility.
If a t e s t p r o c e d u r e i s c o n v e r t e d t o a n a u t o m a t i c p r o g r a m , t h i s t e s t
will be p e r f o r m e d i n t h e s a m e m a n n e r e a c h t i m e i t i s run. Consequently,
the d a t a d e s c r i b i n g the p e r f o r m a n c e of the s y s t e m should be r e p e a t a b l e .
4 1 ~ 0 ,i t was planned that the s a m e t e s t p r o g r a m could be p e r f o r m e d a t
d i f f e r e n t t e s t l o c a t i o n s , s u c h a s t h e f a c t o r y checkout and s t a t i c t e s t
l o c a t i o n s . However, t h i s objective has not m a t e r i a l i z e d t o the d e g r e e
initially planned. This l a r g e l y i s a r e s u l t of GSE and s t a g e configuration
differences.
Another advantage i s t h a t a higher d e g r e e of a c c u r a c y i s obtained
through g r e a t e r s e n s i t i v i t y of the m e a s u r i n g d e v i c e s . This i s evidenced
i n m e a s u r i n g analog p a r a m e t e r s and i n timing the bi-level s i g n a l s .
4nother advantage of significance i s the s h o r t t i m e r e q u i r e d to
p e r f o r m a t e s t provided no a n o m a l i e s o c c u r r e d . This has p a r t i c u l a r
payoffs by being a b l e t o p e r f o r m l a t e c h e c k s of a s y s t e m p r i o r t o
s t a t i c f i r i n g o r a n a c t u a l launch.
4

�AUTOMATION HARDWARE CCPJCEPT
T h e p o s t - m a n u f a c t u r i n g c h e c k o u t of a S a t u r n s t a g e p r o v i d e d t h e
f i r s t a p p l i c a t i o n of a u t o m a t i c t e c h n i q u e s a n d a r e s t i l l i n u s e . I n h e r e n t
in the application w e r e s o m e c o n s t r a i n t s which proved t o have f a r - r e a c h ing i m p a c t s . C o n s o l i d a t e d a n d r e d u c e d t o t h e b a s i c e l e m e n t s , t h e s e
c o n s t r a i n t s w e r e : ( 1 ) no s c h e d u l e i m p a c t t o t h e p r o g r a m , a n d ( 2 ) no
l a r g e r e d e s i g n e f f o r t t o t h e s t a g e a n d GSE. T h e f i r s t c o n s t r a i n t m e a n t
t h a t t h e a d a p t i o n of a u t o m a t i c e q u i p m e n t t o t h e m a n u a l e q u i p m e n t would
b c a c c o m p l i s h e d on a n o - i n t e r f e r e n c e b a s i s . T h e s e c o n d c o n s t r a i n t
m e a n t t h a t t h e a u t o m a t i c e q u i p m e n t a n d t e c h n i q u e s would be d e s i g n e d t o
i n t e r f a c e w i t h t h e GSE a n d not w i t h t h e v e h i c l e s y s t e m s .
F i g u r e 3 d e m o n s t r a t e s t h i s point a n d i s u s e d t o p o r t r a y t h e s y s t e m
w h i c h h a s b e e n i m p l e m e n t e d . I t c o n s i s t s of a t h r e e g e n e r a l p u r p o s e
c o m p u t e r complex with r e m o t e satellite t e s t stations. 4 p r i m a r y a s s e t
of t h i s s y s t e m i s i t s f l e x i b i l i t y p r o v i d e d t h r o u g h t h e u s e of t h r e e individ u a l c o m p u t e r s . T h e c o n s t r a i n t s of no p r o g r a m i m p a c t m a g n i f i e d t h e
i m p o r t a n c e of t h i s f l e x i b i l i t y . It a l l o w e d one c o m p u t e r t o be v e r i f y i n g
t h e i n t e r f a c e w i t h t h e p e r i p h e r y e q u i p m e n t a n d developing u t i l i t y p r o g r a m s w h i l e t h e o t h e r two c o m p u t e r s c o u l d be v e r i f y i n g t h e t e s t s t a t i o n
i n t e r f a c e s and developing t e s t p r o g r a m s .
A f t e r t h e v e r i f i c a t i o n of t h e a u t o m a t i o n s y s t e m a n d d u r i n g t h e s t a g e
t e s t i n g o p e r a t i o n s , a l l of t h e c o m p u t e r s w e r e u s e d s i m u l t a n e o u s l y only
d u r i n g t h e o v e r a l l s y s t e m s t e s t s . C o n s e q u e n t l y , a t l e a s t one c o m p u t e r
w a s a v a i l a b l e f o r debugging p r o g r a m s t o be u s e d i n f u t u r e t e s t s .
E a c h t e s t s t a t i o n w a s g i v e n t h e c a p a b i l i t y t o a c c e p t a n d output
d i s c r e t e a n d a n a l o g s i g n a l s . T h e d e g r e e of c a p a b i l i t y f o r e a c h type
d e p e n d e d upon t h e s t a g e s y s t e m f o r w h i c h t h e s t a t i o n w a s d e s i g n e d .
Man-machine interfacing with e a c h t e s t station w a s provided through
a f l e x o - w r i t e r . T h i s a l l o w e d t h e t e s t e n g i n e e r t o o p e r a t e a l l of t h e
i n p u t / o u t p u t c a p a b i l i t y of t h e t e s t s t a t i o n m a n u a l l y . I n a d d i t i o n , t h e
e x e c u t i v e p r o g r a m w a s d e s i g n e d t o allow h i m t o c a l l u p p r o g r a m s f r o m
t h e c e n t r a l c o m p u t e r c o m p l e x . O n c e a p r o g r a m w a s o n - l i n e , i t could
be s i n g l e s t e p p e d o r r u n c o m p l e t e l y a u t o m a t i c . C o m m u n i c a t i o n between the central computer complex and the t e s t stations was via a
distribution m a t r i x which allowed any c o m p u t e r t o work with any t e s t
station.

�As r e f e r e n c e d p r e v i o u s l y , t h e a m o u n t of d a t a w h i c h w a s n e c e s s a r y
t o r e c o r d a n d a n a l y z e w a s g e t t i n g unwieldly. T o be a b l e t o handle t h e
d i s c r e t e b i - l e v e l t y p e s i g n a l s , a CEE ( d i g i t a l e v e n t s e v a l u a t o r ) w a s
developed.
T h i s d e v i c e h a s t h e c a p a b i l i t y t o a c c e p t a c h a n g e of s t a g e ,
r e c o r d t h e t i m e a n d i d e n t i f i c a t i o n a n d output a r e c o r d on t a p e o r p r i n t e r .
C a p a b i l i t y i s p r o v i d e d by s o f t w a r e f o r r e a l - t i m e o r off-line e v a l u a t i o n .
As c a n be o b s e r v e d by c o m p a r i n g F i g u r e s 2 a n d 3 , s o m e m o d i f i c a t i o n s w e r e m a d e t o t h e GSE t o a l l o w c o n t r o l a n d m o n i t o r i n g of t h e
s t a g e s y s t e m s . B e c a u s e of t h e c o n s t r a i n t of no l a r g e r e d e s i g n e f f o r t ,
t h e m o d i f i c a t i o n s w e r e e n g i n e e r e d u s i n g t h e g u i d e l i n e s of providing
a c c e s s t o the existing m a n u a l control and monitoring functions. In
the e l e c t r i c a l a r e a s , this w a s relatively e a s y since the s t a g e s have
a l w a y s b e e n c o n t r o l l e d a n d m o n i t o r e d by r e m o t e t e c h n i q u e s . T h e r e f o r e , i n t h e g e n e r a l c a s e , i t w a s a m a t t e r of " t e e i n g " t h e s e f u n c t i o n s
i n a blockhouse d i s t r i b u t o r a n d c o n n e c t i n g t h e m t o t h e a p p r o p r i a t e
t e s t station.
A u t o m a t i o n of t h e i n s t r u m e n t a t i o n s y s t e m t e s t i n g o p e r a t i o n r e q u i r e d
a s o m e w h a t d i f f e r e n t a p p r o a c h . I n F i g u r e 3 , t h e p r o b l e m of gaining
a c c e s s t o r e c o r d t h e m e a s u r e m e n t s b e t w e e n t h e s i g n a l conditioning and
t h e T M p a c k a g e w a s a m a t t e r of "teeing" t h e m e a s u r e m e n t a n d c o n n e c t ing t o the r e c o r d e r and Instrumentation T e s t Station. However, t o
a c c o m p l i s h t h e c o m p a r i n g of h a r d w i r e r e c o r d i n g w i t h t h e T M r e c o r d
r e q u i r e d digitizing the information the T M ground station received.
T h i s w a s a c c o m p l i s h e d by d e s i g n i n g e q u i p m e n t t o a c c e p t t h e TM s i g n a l s
a t t h e d i s c r i m e n a t o r s and d e c o m m u t a t o r s , digitize t h e s e m e a s u r e m e n t s
and i n t e r f a c e t h e m with the Instrumentation T e s t Station. P r o g r a m s
w e r e p r o v i d e d t o do t h e c o m p a r i s o n a n d p r i n t t h e r e s u l t s on t h e f l e x o writer.
About t h i s t i m e , a n o t h e r m e t h o d of a c c o m p l i s h i n g t h e s a m e t e c h n i q u e s u s i n g o n - b o a r d e q u i p m e n t w a s being d e v e l o p e d . T h i s m e t h o d
h a s c o m e t o be known a s DDAS ( D i g i t a l Data A c q u i s i t i o n S y s t e m ) a n d
h a s r e p l a c e d t h e e a r l i e r t e c h n i q u e i n m o s t c a s e s . T h e a d v a n t a g e s of
converting the m e a s u r e m e n t s t o digital f o r m on the s t a g e i s the reducti o n of n o i s e p r o b l e m s a n d l e s s g r o u n d e q u i p m e n t i s r e q u i r e d . L e s s
s u s c e p t i b i l i t y t o n o i s e i s a c h i e v e d by having l e s s w i r e l e n g t h b e t w e e n
t h e m e a s u r e m e n t a n d t h e A / D c o n v e r t e r (analog t o d i g i t a l ) . L e s s
e q u i p m e n t i s a c h i e v e d by e l i m i n a t i n g a n d / o r r e d u c i n g t h e need f o r g r o u n d
recorders.

�F i g u r e 3 does not depict one piece of equipment used in the e a r l y
phases of automating i n s t r u m e n t a t i o n checkout. This w a s a p r e s s u r e
balance s y s t e m u s e d t o a p p l y a known p r e s s u r e s t i m u l i t o the p r e s s u r e
t r a n s d u c e r , thus providing a b a s i s f o r c o m p a r i n g t h e r e c o r d i n g taken
a t t h e s i g n a l conditioner output. I n c r e a s e d quality and reliability of
t h e t r a n s d u c e r and the implementation of t h e R 4CS (Remote Automatic
C a l i b r a t i o n S y s t e m ) h a s deleted t h e n e c e s s i t y for t h i s technique. The
RACS provide f o r a two-point c a l i b r a t i o n check of the a m p l i f i e r by
being a b l e t o apply a known signal a t the high and low end of a n a m p l i f i e r
r a n g e . The t r a n s d u c e r provides a t h i r d point by m e a s u r i n g the a m b i e n t
conditions of t h e s y s t e m which i t i s monitoring.
In t h e m e c h a n i c a l s y s t e m s , much m o r e modification w a s n e c e s s a r y
t o obtain c o m p l e t e r e m o t e a u t o m a t i c control. As mentioned previously,
the m e c h a n i c a l checkout o p e r a t i o n w a s neither r e m o t e l y o r automatically
c o n t r o l l e d . G e n e r a l l y , p r e s s u r e s w e r e s e t up by using hand valves and
hand l o a d e r s and w e r e m o n i t o r e d by a l o c a l gauge. To achieve r e m o t e
c o n t r o l r e q u i r e d t h e addition of solenoid o r m o t o r d r i v e n l o a d e r s f o r
venting loading p r e s s u r e s f o r shut-down, t r a n s d u c e r s t o provide r e a d i n g s
a t r e m o t e locations and s o m e s e l f - d i a g n o s t i c capability i n c a s e of
a b n o r m a l conditions.
Space will not p e r m i t t h e d e s c r i p t i o n of the a u t o m a t i c s y s t e m s
t h a t a r e now u s e d i n the S a t u r n I B and S a t u r n V P r o g r a m s . The s y s t e m s now u s e d , with one exception, employ a single c o m p u t e r r a t h e r
t h a n a m u l t i - c o m p u t e r a s the c e n t r a l c o m p u t e r complex. In one p a r t i c u l a r application of t h e c e n t r a l c o m p u t e r complex s y s t e m a l l of t h e
input/output capability i n c o r p o r a t e d i n the t e s t s t a t i o n h a s been integrated.
IMPLEMENTATION ANALYSIS
So f a r , this paper has been devoted t o a d e s c r i p t i o n of the testing
o p e r a t i o n , the h a r d w a r e and h a r d w a r e changes n e c e s s a r y t o convert t h i s
o p e r a t i o n f r o m m a n u a l t o automatic. The next phase will p r e s e n t a n
a n a l y s i s of t h e p r o b l e m s e n c o u n t e r e d during t h e implementation phase.
T h e s e p r o b l e m s c a n be grouped into t h r e e c a t e g o r i e s :
(1)
(2)
(3)

Hardware
Software
People

�T h e r e a d e r w i l l note i m m e d i a t e l y t h a t t h e s e a r e v e r y g e n e r a l c a t e g o r i e s ; t h e r e f o r e , the s p e c i f i c s within m u s t be f r a m e d .
Hardware
In t h e h a r d w a r e c a t e g o r y , i n c o m p a t i b i l i t y p r o b l e m s w e r e e n c o u n t e r e d within t h e a u t o m a t i o n e q u i p m e n t i t s e l f ; t h e r e w e r e i n c o m patibility p r o b l e m s e n c o u n t e r e d w i t h t h e s i g n a l functions which the
e q u i p m e n t w a s d e s i g n e d t o handle. T h e r e w e r e o t h e r p r o b l e m s conc e r n i n g t h e c a p a b i l i t y of the e q u i p m e n t t o m a n a g e t h e o p e r a t i o n a l
r e q u i r e m e n t s . T h e s o l u t i o n t o t h e s e p r o b l e m s h a s brought a b o u t a
c o n s i d e r a b l : a m o u n t of a d v a n c e s i n h a r d w a r e d e s i g n and t e c h n i q u e s .
T h e r e i s a b a s i c s y s t e m p r o b l e m t h a t b e c o m e s evident a f t e r the
automation equipment i s interfaced and i s performing a testing o p e r ation. This problem was alluded t o in the discussion concerning the
c o n s t r a i n t s i m p o s e d i n t h e i n i t i a l a p p l i c a t i o n of a u t o m a t i c t e c h n i q u e s .
It w a s pointed out t h a t t h e r e w a s t o be no m a j o r r e d e s i g n e f f o r t of the
v e h i c l e . T h i s r e s u l t e d i n t h e a u t o m a t i o n e q u i p m e n t being i n t e r f a c e d
w i t h t h e GSE r a t h e r t h a n t h e s t a g e s y s t e m s . H e r e i n l i e s t h e s y s t e m
p r o b l e m . T h e e f f e c t being not a r e d u c t i o n of g r o u n d s u p p o r t equipm e n t ; but i n s t e a d a n a d d i t i o n of a u t o m a t i o n e q u i p m e n t t o p e r f o r m the
c o m m u n i c a t i o n a n d i n t e g r a t i o n t a s k t h a t the m a n w a s doing.
With t h e c o n c e p t of i n t e r f a c i n g t h e 110 (input-output) of t h e c o m p u t e r
t o t h e GSE, t h e GSE i s c o n s i d e r e d t o be t h e d e c i s i o n making d e v i c e .
T h e c o m p u t e r i s c o n s i d e r e d only a m e a n s of c o m m u n i c a t i n g the s t a t u s
of t h e GSE a n d v e h i c l e t o t h e e n g i n e e r s . T h i s c o n c e p t f a i l s t o u s e one
of t h e s t r o n g a s s e t s of t h e c o m p u t e r ; t h i s i s i t s c a p a b i l i t y t o g a t h e r
d a t a a n d m a k e s u b s e q u e n t d e c i s i o n s . A continuance of t h i s philosophy
w i l l i n c r e a s e t h e s i z e a n d c o m p l e x i t y of t h e h a r d w a r e and s o f t w a r e
system.
Another way of d e s c r i b i n g t h e s a m e p r o b l e m i s by taking a r a t h e r
a n t h r o p o m o r p h i c view of t h e v e h i c l e a n d GSE. T h e method of c o m m u n i c a t i o n of a c o m p u t e r i s a d i g i t a l language. With the e x c e p t i o n of t h e
o n - b o a r d c o m p u t e r s a n d t h e DDAS (which c o n c e r n s only r e s p o n s e s ) t h e
v e h i c l e u n d e r s t a n d s only d i s c r e t e a n d a n a l o g language. T h e r e f o r e , t h e
m a j o r p u r p o s e of t h e e l e c t r i c a l GSE i s t o be a n i n t e r p r e t e r between t h e
c o m p u t e r a n d the v e h i c l e . I t b e c o m e s a p p a r e n t t h e n t h a t s t e p s need t o
be t a k e n t o g e t t h e v e h i c l e t o c o m m u n i c a t e i n a language m o r e c l o s e l y
a l i g n e d w i t h t h e c o m p u t e r language. T h e two e x c e p t i o n s r e f e r r e d t o

�above r e p r e s e n t s t e p s i n this d i r e c t i o n s i n c e both communicate via
digital links. By expanding t h e i r u s e provides the key f o r a c c o m p l i s h ing the additional s t e p s n e c e s s a r y . The w r i t e r w i s h e s t o make v e r y
e x p l i c i t , a t t h i s point, that the above logic i s u s e d t o e s t a b l i s h a longr a n g e goal. T h e r e a r e many i n c r e m e n t a l s t e p s n e c e s s a r y before that
goal c a n be r e a c h e d . Also, t h e r e a r e many t r a d e - o f f s concerning
complexity which m u s t be m a d e between the vehicle and t h e ground
equipment. T o r e a c h this goal, t h e following actions need t o be taken:
(1) I n c r e a s e d r e l i a n c e on DDAS.
r e l i a b i l i t y and handling techniques .

This will r e q u i r e i m p r o v e d

(2) R e a s s e s s t h e balance of complexity between the vehicle
and GSE. In o r d e r t o achieve l a r g e reductions of e l e c t r i c a l GSE, i t
would be profitable t o allow m o r e complexity on-board the vehicle.
( 3 ) E l i m i n a t e the need f o r t o t a l checkout capability a t the
launch o p e r a t i o n s . T h i s c a n be achieved by delivering t o the launch
o p e r a t i o n s totally configured and v e r i f i e d s t a g e s .
(4) Review the interlocking r e q u i r e m e n t s , using t h e guiclel i n e of allowing t h e c o m p u t e r t o m a k e t h e decision.

(5) Develop m e a n s of controlling vehicle s y s t e m s through the
u s e of o n - b o a r d techniques a n d / o r expanded u s e of p r e s e n t c a p a b i l i t i e s .
By being a b l e t o c o n t r o l t h e vehicles through u s e of on-board s y s t e m s ,
a r e d u c t i o n i n t h e i n t e r f a c e points between the vehicle and GSE i s gained.
If the n u m b e r of the i n t e r f a c e points i s r e d u c e d , two i m p a c t s a r e a
consequence. F i r s t , t h e r e i s a g e n e r a l reduction of GSE, s i m p l y bec a u s e t h e r e a r e l e s s functions t o be handled. Second, t h e r e i s l e s s
possibility of a change i n the vehicle causing a subsequent change i n
t h e GSE. An e x a m p l e of this i s i n the way the DDAS p e r f o r m s . S e v e r a l
hundred m e a s u r e m e n t s m a y input t o the DDAS, but the output i s a single
wave t r a i n . T h e r e f o r e , many m e a s u r e m e n t changes c a n be m a d e with
the only e f f e c t t o t h e GSE being a change t o the m e a s u r e m e n t a d d r e s s
in the CDAS wave t r a i n . This type of change c a n be accepted by a
change in the s o f t w a r e .
Software
Providing a s o f t w a r e s y s t e m to i m p l e m e n t the automation of thc,
checkout and launch o p e r a t i o n s h a s been and continues to be one of the
m o s t challenging a s p e c t s of the automation endeavor.

�T h e d i s c u s s i o n c o n c e r n i n g t h e n a t u r e of t h e t e s t i n g o p e r a t i o n
pointed out t h e v a r i e t y of s i g n a l s involved a n d t h e d i f f e r e n t t y p e s of
t e s t s c o n d u c t e d . T o c r e a t e a s o f t w a r e s y s t e m t o m a n a g e t h i s t y p e of
o p e r a t i o n r e q u i r e s a t r e m e n d o u s a m o u n t of c a p a b i l i t y a n d f l e x i b i l i t y .
I n doing a n a n a l y s i s of t h e d i f f i c u l t i e s t h a t w e r e e n c o u n t e r e d , e a c h
s e e m e d t o be r o o t e d t o a v e r y b a s i c a n d f u n d a m e n t a l point; t h a t of being
a b l e t o d e s c r i b e a l l of t h e r e q u i r e m e n t s of t h e job. Of c o u r s e , t h i s i s
a n e s s e n t i a l i n g r e d i e n t i n a n y t a s k . But, i t r e a f f i r m s t h e point t h a t t h e
b e s t s p e n t t i m e i n a n y new e n d e a v o r i s t h a t s p e n t i n d e s c r i b i n g t h e t a s k
a n d planning i t s i m p l e m e n t a t i o n .
T h e p r o b l e m s t h e t e s t e n g i n e e r e n c o u n t e r e d i n providing s y s t e m s
t e s t r e q u i r e m e n t s t o t h e p r o g r a m m e r w e r e d i r e c t m a n i f e s t a t i o n s of t h e
a b o v e point. P r i o r t o a u t o m a t i o n , t h e e n g i n e e r h a d n e v e r b e e n r e q u i r e d
t o d e s c r i b e i n h i s t e s t p r o c e d u r e s a l l of t h e s t e p s , w i t h t h e e x p e c t e d
r e s p o n s e s a n d l i m i t s , t o t h e d e t a i l r e q u i r e d by a c o m p u t e r p r o g r a m .
O t h e r d i f f i c u l t i e s w e r e e n c o u n t e r e d i n d e t e r m i n i n g t h e a m o u n t of
c a p a b i l i t y and f l e x i b i l i t y r e q u i r e d i n t h e e x e c u t i v e p r o g r a m . I n o r d e r
t o d e v e l o p a n e x e c u t i v e p r o g r a m , d e c i s i o n s h a v e t o be m a d e c o n c e r n ing m a n - m a c h i n e r e l a t i o n s h i p s , o n - l i n e o r off-line c o m p i l a t i o n , m e m o r y
c a p a b i l i t y a n d i n p u t / o u t p u t r e q u i r e m e n t s t o n a m e a few. T h e s e d e c i s i o n s
m u s t be m a d e a s e a r l y a s p o s s i b l e s i n c e c h a n g e s t o t h e s e i t e m s w i l l
cause m a j o r impact to the executive p r o g r a m development.
The language the t e s t engineer should u s e i n writing the t e s t i s
p r o b a b l y t h e m o s t c o m p l e x a n d c o n t r o v e r s i a l i s s u e . P a r t of t h e
d i f f e r e n c e of opinion i s a r e s u l t of t h e t y p e of s y s t e m being a u t o m a t e d .
F o r example, to monitor the instrumentation s y s t e m m a y require a
p r o g r a m t o c o n t i n u o u s l y s c a n a g r o u p of m e a s u r e m e n t s . T h i s r e q u i r e s
a c o m p l e t e l y d i f f e r e n t t y p e of p r o g r a m t h a n one t o c h e c k o u t t h e cutoff
circuitry.
The f o r m e r c a s e requires a p r o g r a m t o perform a monitoring
function continuously with v e r y little man-machine interfacing. A
machine language p r o g r a m i s probably best suited f o r t h e s e needs.
T o p e r f o r m a c h e c k of t h e cutoff r e q u i r e s i s s u i n g h i - l e v e l s i g n a l s a n d
m o n i t o r i n g f o r c o r r e c t r e s p o n s e s on a s t e p by s t e p b a s i s . T h e r e i s
m o r e man-machine interfacing concerning display requirements,
c a p a b i l i t y t o c h a n g e t h e c o u r s e of t h e t e s t and s a f e t y c o n d i t i o n s . A
m a c h i n e l a n g u a g e p r o g r a m d o e s n ' t p r o v i d e t h e f l e x i b i l i t y , plus t h e t e s t
e n g i n e e r l o s e s h i s knowledge of t h e p r o g r a m i n m a c h i n e l a n g u a g e d o c u mentation.

10

�It i s t h e w r i t e r s opinion t h a t t h e s e a r c h f o r a c o m m o n l a n g u a g e
(defined a s one l a n g u a g e i n w h i c h a l l t e s t p r o g r a m s a r e w r i t t e n ) i s t h e
w r o n g a p p r o a c h . T h e w r i t e r f e e l s t h a t t h e l a n g u a g e u s e d should be
d e t e r m i n e d by s u c h c r i t e r i a a s : ( 1 ) t h e n u m b e r of d e c i s i o n s t h e
e n g i n e e r s m a y h a v e t o m a k e d u r i n g t h e o p e r a t i o n , (2) t h e r e p e t i v e n e s s of t h e o p e r a t i o n , ( 3 ) t h e s a f e t y c o n s i d e r a t i o n s , (4) t h e d i s p l a y
r e q u i r e m e n t s , e t c . All of t h e a b o v e c r i t e r i a a r e c o n c e r n e d w i t h d e t e r m i n ing t h e t y p e of o p e r a t i o n t h a t i s t o be p e r f o r m e d . T h i s i s r e a l l y t h e k e y
in d e t e r m i n i n g the language best suited f o r the t e s t p r o g r a m . A language
f o r p e r f o r m i n g c o m b i n e d s y s t e m s t e s t s c a n be d e v e l o p e d w h i c h XT i l l
c o n t r o l t h e t o t a l o p e r a t i o n a n d a l s o allow t h e a p p r o p r i a t e s u b l a n g u a g e
t o be u s e d .
Of t h e c r i t e r i a u s e d t o d e v e l o p a s o f t w a r e l a n g u a g e , b e i n g c a p a b l e
of a c c e p t i n g c h a n g e s i s c l o s e t o being t h e m o s t i m p o r t a n t . The S a t u r n
h a r d w a r e (vehicle and GSE) w e r e designed with m i s s i o n flexibility in
mind. Mission flexibility o r a n y flexibility f o r that m a t t e r i s synonymous
w i t h c h a n g e s . T h e r e f o r e , a s u s t a i n e d l e v e l of c h a n g e s c a n be e x p e c t e d
f o r t h e d u r a t i o n of t h e p r o g r a m . T h e c h a l l e n g e i s t o d e s i g n h a r d w a r e
and s o f t w a r e s y s t e m s that will a c c e p t changes with m i n i m u m impact.
I m p a c t i n t w o w a y s : (1) t u r n a r o u n d t i m e a n d ( 2 ) t o t a l c o s t ( d o c u m e n t ation, time, manpower).
S o f t w a r e s y s t e m s m u s t be v e r i f i e d p r i o r t o t h e i r u s e i n t h e o n - l i n e
hardware system. The techniques used for the verification activities
m u s t be planned e a r l y . T h e r e a r e m a n y c o s t v s . d e g r e e of v e r i f i c a t i o n t r a d e - o f f s t h a t m u s t be m a d e . T h a t i s , f o r a g i v e n p r o g r a m
t h e r e i s a r a n g e of v e r i f i c a t i o n t e c h n i q u e s t h a t c a n be u s e d . T h e y r a n g e
f r o m using another software p r o g r a m t o using duplicate h a r d w a r e .
Running t h e p r o g r a m o n d u p l i c a t e h a r d w a r e w i l l p r o d u c e t h e m a x i m u m
c o n f i d e n c e t h a t t h e g i v e n p r o g r a m i s v e r i f i e d . But, i n g e n e r a l , i t i s
a l s o t h e m o s t e x p e n s i v e . F o r t h e v e r i f i c a t i o n of a t o t a l s o f t n a r e s y s t e m
t h i s t e c h n i q u e i s n e c e s s a r y . F o r c o m p o n e n t s of t h e s y s t e m a l e s s e r
d e g r e e of c o n f i d e n c e c a n p o s s i b l y be a c c e p t e d a n d s u b s e q u e n t l y a l e s s
c o s t l y m e t h o d u s e d . What m e t h o d i s u s e d s h o u l d be planned c o n c u r r e n t l y
w i t h t h e i n i t i a l d e s i g n of t h e s y s t e m . T h e n e c e s s i t y f o r t h i s i s q u i t e
obvious b e c a u s e of t h e t i m e r e q u i r e d t o d e v e l o p t h e v e r i f i c a t i o n p r o g r a m s
a n d / o r h a r d w a r e . 4 1 ~ 0 ,a n y c h a n g e s i n plans f r o m a n o r i g i n a l v e r i f i cation concept will cause serious schedule impacts.
P r o b a b l y t h e g r e a t e s t m i s c a l c u l a t i o n i n t h e g e n e r a t i o n of a s o f t w a r e
s y s t e m w a s t h e t i m e r e q u i r e d . T h e difficulty e n c o u n t e r e d i n t h e

�g e n e r a t i o n of the s y s t e m s r e q u i r e m e n t s w a s a contributor t o this t i m e .
Independent of this i s the t i m e r e q u i r e d t o c r e a t e , document and v e r i f y
a p r o g r a m . P r e v i o u s t o automation the t e s t p r o c e d u r e s w e r e g e n e r a t e d
f r o m s y s t e m s r e q u i r e m e n t s , but they could be g e n e r a t e d s h o r t l y p r i o r
to running the t e s t . With t h e advent of m o r e complex s y s t e m s and
automation t h i s i s no l o n g e r possible. The optimum solution would be to
develop a l l of t h e h a r d w a r e e a r l y enough t o allow adequate t i m e f o r
s o f t w a r e development. T h i s optimum solution cannot be obtained i n a
c o n c u r r e n t p r o g r a m s o techniques m u s t be developed to t r a n s f e r s y s t e m s r e q u i r e m e n t s t o s o f t w a r e p e r s o n n e l c o n c u r r e n t with h a r d w a r e
development.
E x p e r i e n c e t o date h a s brought the r e a l i z a t i o n that a t o t a l softw a r e s y s t e m h a s t o be developed i n t h e s a m e m a n n e r a s a h a r d w a r e
s y s t e m . F i g u r e 4 depicts a software s y s t e m which i s r e p r e s e n t a t i v e
of a type t h a t i s n e c e s s a r y f o r the launch o p e r a t i o n s . The m a j o r decisions
c o n c e r n i n g t h e components of t h i s s y s t e m have been d i s c u s s e d above.
Once t h e s e d e c i s i o n s have been r e a c h e d and the r e l a t i o n s h i p among the
components e s t a b l i s h e d , they should c o m e under a configuration management s c h e m e . T h i s will i n s u r e the c o n t r o l of any i n t e r f a c e impacting
c h a n g e s . A s e r i o u s d e t e r e n t t o a n automation effort i s t h e lack of u n d e r standing of the c a p a b i l i t i e s and limitations of the s o f t w a r e s y s t e m s .
Putting the s o f t w a r e s y s t e m u n d e r a configurationmanagement s c h e m e
enhances i t s understanding, because it f o r c e s the s o f t w a r e t o be t r e a t e d
a s a s y s t e m with a l l of t h e accompanying documentation. To f u r t h e r
a c c e l e r a t e the understanding p r o c e s s t r a i n i n g s e s s i o n s should be conducted explaining t h e design and o p e r a t i o n of the s y s t e m .
People
L a s t , but m o s t i m p o r t a n t i s t h e people problem. This c a t e g o r y
i s probably t h e m o s t complex a s w e l l a s being the m o s t i m p o r t a n t . The
w r i t e r i s not s u r e that t h e r e a r e any distinct c h a r a c t e r i s t i c s t h a t can be
d e s c r i b e d i n a n explicit, independent fashion. However, t h e r e a r e a
couple which s e e m t o be basic and c a n be d e s c r i b e d .
F i r s t , t h e r e i s i n a n y new endeavor a knowledge-time p a r a m e t e r .
That i s , a t t h e initiation of a n activity t h e r e i s a lack of knowledge of
how that a c t i v i t y c a n be a c c o m p l i s h e d , but a s t i m e proceeds this knowledge b e c o m e s a v a i l a b l e . The p r o b l e m i s t o develop the communication
methods ( i n t e r m s of organization and information t r a n s f e r ) t o apply t h i s
knowledge effectively t o a l l r e q u i r ing a c t i v i t i e s . In the c a s e of automating

�S a t u r n I s t a g e t e s t i n g , t h e r e w a s a n u n d e r s t a n d i n g of t h e c h e c k o u t
o p e r a t i o n a s i t w a s being p e r f o r m e d m a n u a l l y . T h e r e w a s not a
t h o r o u g h u n d e r s t a n d i n g of e a c h h a r d w a r e , s o f t w a r e a n d o p e r a t i o n
r e q u i r e m e n t , n o r o r how t h e s e r e q u i r e m e n t s s h o u l d be fulfilled t o
a c h i e v e t h e a u t o m a t i o n job. A s s t a t e d a b o v e , t h e r e i s nothing unique
a b o u t t h i s s i t u a t i o n . I t a p p l i e s t o a n y new e f f o r t . T h e a s p e c t i n t h e
S a t u r n p r o g r a m which m a k e s this m o r e impacting i s the time element.
By e x a m i n i n g t h e k n o w l e d g e - t i m e r e l a t i o n s h i p d e s c r i b e d i n F i g u r e
5 i t c a n be s e e n t h a t t h e a u t o m a t i o n s y s t e m c o n c e p t , w h i c h w a s t o s e t
t h e pace f o r the S a t u r n I B and V p r o g r a m s , w a s f o r m e d p r i m a r i l y
f r o m t h e a c c u m u l a t e d e x p e r i e n c e of only one S a t u r n s t a g e . B e f o r e t h e
f u l l c o m p l i m e n t of e q u i p m e n t w a s o p e r a t i o n a l a y e a r a n d a half w a s
c o n s u m e d . A s o n e m i g h t e x p e c t , knowledge of how t o d o t h e job
a c c u m u l a t e d d u r i n g t h a t t i m e c a u s i n g h a r d w a r e , s o f t w a r e and o r g a n izational changes.
T o t a k e this relationship and expand i t over the total S a t u r n I B and
V p r o g r a m s , t h e p r o b l e m i s g r e a t l y i n c r e a s e d . It c a n be s e e n f r o m
F i g u r e 5 t h a t t h e i n i t i a l c o n c e p t s w e r e being d e v e l o p e d t o p e r f o r m
factory checkout, static testing and launch operations - engrossing
nine d i f f e r e n t l o c a t i o n s , f i v e s t a g e c o n t r a c t o r s , a n d two NASA C e n t e r s .
Very little actual experience, i n proportion to the total program, exi s t e d a t t h a t t i m e . I m p l e m e n t a t i o n of t h e s e c o n c e p t s r e q u i r e d a p p r o x i m a t e l y t h r e e y e a r s . During t h e s e t h r e e y e a r s much experience w a s
gained, thus considerably a l t e r i n g the concepts that w e r e f i r s t applied.
The second characteristic concerns the attitude toward automating
the testing operations. Unfavorable attitudes concerning automation
h a v e g e n e r a l l y r e s u l t e d f r o m a l a c k of u n d e r s t a n d i n g of t h e long r a n g e
n e e d s a n d b e n e f i t s . T h e s e a t t i t u d e s involved, of c o u r s e , v a r y w i t h i n
t h e knowledge-tim:: r e l a t i o n s h i p . I n t h e S a t u r n - A p ~ l l op r o g r a v t h r e e
o r four y e a r s a r e required for the launch site personnel t o acquire the
s a m e a m o u n t of e x p e r i e n c e a s t h o s e involved i n t h e i n i t i a l d e s i g n and
c h e c k o u t o p e r a t i o n s . F u r t h e r , t h i s t i m e i n v o l v e s t h o u s a n d s of people
w i t h d i f f e r e n t d i s c i p l i n e s a n d b a c k g r o u n d s . T h e r e f o r e , if t h e l a s t
o p e r a t i o n i s t o t a k e a d v a n t a g e of t h e e x p e r i e n c e a n d knowledge g a i n e d
p r e v i o u s l y , t h e p r o c e s s of a c c u m u l a t i n g a n d c o m m u n i c a t i n g t h i s e x p e r i e n c e m u s t be a c c e l e r a t e d .

�PROJECTIONS AND CONCLUSIONS
B e f o r e t h e m a x i m u m benefits c a n be r e a p e d f r o m a u t o m a t i c t e c h niques s e v e r a l a d v a n c e s need t o be m a d e . The f i r s t a n d f o r e m o s t a r e
i n t h e people c a t e g o r y .
F i r s t of a l l , g o a l s need t o be e s t a b l i s h e d and p r o c l a i m e d . T h e s e
g o a l s m u s t be i n t e r m s of f u t u r e conditions f o r which a u t o m a t i c t e c h niques a r e t h e only a n s w e r . In t h e S a t u r n p r o g r a m , g r o u p s of people
have r e s i s t e d a u t o m a t i o n on t h e b a s i s t h a t the i m m e d i a t e job, with
w h i c h they w e r e c o n c e r n e d , could be done b e t t e r t h e old way. The
l o n g e r r a n g e needs should be d e s c r i b e d and explained.

A r e c e n t s u r v e y of t h e S a t u r n - A p o l l o P r o g r a m d i s c l o s e d that t h e
only functions t h a t h a d n ' t been a u t o m a t e d , a t one location o r a n o t h e r ,
w e r e l e a k c h e c k s , a m p l i f i e r c a l i b r a t i o n and s o m e monitoring of
c r i t i c a l functions. Of t h e s e , i t would be a w a s t e of money t o a u t o m a t e
l e a k c h e c k s and s o f t w a r e techniques have been developed t o e l i m i n a t e
t h e need f o r a m p l i f i e r c a l i b r a t i o n . S o t h e p r o b l e m i s not technology,
but u n d e r standing a n d a t t i t u d e s .
T r a i n i n g i s a n a c t i v i t y t h a t n e e d s t o be e x p l o r e d . It i s probably
t h e only way i n which t h e l e a r n i n g c u r v e c a n be i m p r o v e d . As d i s c u s s e d
p r e v i o u s l y , t h i s i s a v e r y s e r i o u s a s p e c t i n the S a t u r n - A p o l l o p r o g r a m
w i t h i t s t i m e s p a n between t h e beginning a n d the end of the t e s t i n g
o p e r a t i o n . A l s o , t r a i n i n g c a n be u s e d t o e r a s e a t t i t u d e p r o b l e m s .
In t h e h a r d w a r e a r e a s e v e r y s t e p which w i l l allow the vehicle t o be
m o r e autonomous should be t a k e n . T h i s w i l l have the effects of r e d u c ing t h e GSE and r e l i e v i n g s o m e of the s o f t w a r e b u r d e n s . To i t e r a t e
s o m e of t h e points d i s c u s s e d p r e v i o u s l y , t h e review of interlocking
r e q u i r e m e n t s , d e v e l o p m e n t of g r e a t e r r e l i a n c e on DDAS and developm e n t of o n - b o a r d s y s t e m s provide t h e g r e a t e s t potential. B e f o r e the
l a t t e r c a n be i m p l e m e n t e d i n t h e m a i n s t r e a m , t e s t a r e a s need t o be
provided t o d e v e l o p t h e c h a n g e s . T h i s would a l s o allow t h e p e r s o n n e l
t o gain confidence u n d e r r e a l i s t i c conditions, thus aiding t h e i m p l e m e n t ation process.
The m a j o r point t h a t n e e d s t o be m a d e i n the s o f t w a r e a r e a i s t h a t
i t needs t o be t r e a t e d a s a s y s t e m . Also, i t should be t r e a t e d on an
e q u a l b a s i s a s t h e h a r d w a r e . In t h e S a t u r n - A p o l l o P r o g r a m t h i s m e a n s

�a t r i a n g u l a r s i t u a t i o n of v e h i c l e , G S E and s o f t w a r e . No change should
bc m a d e t o one without c o n s i d e r i n g t h e effect of the other. T o i m p l e m e n t
t h i s r e q u i r e s t h a t t h e r e be c o n c u r r e n c y among a l l t h r e e f r o m t h e initial
concept t h r o u g h the l a s t launching. Of c o u r s e , t h i s adds complexity t o
t h e t o t a l p r o g r a m , but not n e a r a s much a s would be i f this w a s not
recognized.

-

P r o j e c t i n g outside t h e t h e m e of t h i s p a p e r , t h e r e i s one l a s t point
t h a t should be e x a m i n e d . T h a t i s t h a t t h e checkout and launch i s only
one f a c e t of t h e Saturn-Apollo P r o g r a m . Since they a r e the l a s t
a c t i v i t i e s a l l o t h e r a c t i v i t i e s s u p p o r t t h e m . T h e r e f o r e , if f a s t e r , m o r e
effective techniques a r e applied t o t h e s e a c t i v i t i e s t h e s a m e techniques
need t o be applied t o t h e supporting a c t i v i t i e s . An e x a m p l e of t h i s i s
i n a t e s t p r o g r a m which s e n d s a s t i m u l i t o the vehicle t h e n i n t e r r o g a t e s
a d a t a t a p e f o r the p r o p e r r e s p o n s e d a t a . The d a t a t a p e i s t o be supplied
by e n g i n e e r i n g containing a l l of the p a r a m e t e r s and t h e i r l i m i t s . Howe v e r , if e n g i n e e r i n g i s n ' t g e a r e d t o s u p p o r t t h i s type of o p e r a t i o n , the
d a t a t a p e w i l l n e v e r be a v a i l a b l e on s c h e d u l e nor w i l l change capability
e x i s t . T h i s s o r t of supporting r e q u i r e m e n t s r e p r e s e n t s a whole field
t h a t m u s t be e x p l o r e d and i n t e g r a t e d into t h e t o t a l job.

�W I -

= w
=
&gt;
C3

��INSTRUMENTATION
TEST STATION
PERIPHERY EQUIP

TEST STATION

RELAY LOGIC
ANALOG GEN

FIGURE 3
AUTOMATED CHECttOUT OPERATI ON

�MAN-MACH INE

FIGURE 4
SOFTWARE SYSTEM

IN PUT-OUT PUT

�DEFINITION O F

DEFINITION 0

FIGURE 5

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="20157">
                <text>spc_stnv_000063</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20158">
                <text>"Analysis and Projections of Space Vehicle Automatic Checkout and Launch."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20159">
                <text>Vedane, C. R.</text>
              </elementText>
              <elementText elementTextId="20160">
                <text>George C. Marshall Space Flight Center</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20161">
                <text>1966-10-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="20162">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20163">
                <text>Saturn project (U.S.)</text>
              </elementText>
              <elementText elementTextId="20164">
                <text>Automatic test equipment</text>
              </elementText>
              <elementText elementTextId="20165">
                <text>Rockets (Aeronautics)--Launching</text>
              </elementText>
              <elementText elementTextId="20166">
                <text>Space vehicle checkout program</text>
              </elementText>
              <elementText elementTextId="20167">
                <text>Launching</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20168">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="20169">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="20170">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="20171">
                <text>Box 19, Folder 17</text>
              </elementText>
              <elementText elementTextId="205814">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20173">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="20174">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="20175">
                <text>spc_stnv_000051_000074</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10244" public="1" featured="0">
    <fileContainer>
      <file fileId="9182">
        <src>https://digitalprojects.uah.edu/files/original/20/10244/zerostage_082707085507.pdf</src>
        <authentication>3798949d9a5d3372c1c7b9185e9fcaaf</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="152905">
                <text>zerostage_082707085507.pdf</text>
              </elementText>
              <elementText elementTextId="152906">
                <text>spc_stnv_000942</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152907">
                <text>"A 'Zero Stage' for the Saturn IB Launch Vehicle."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152908">
                <text>To meet the demands of increasing payload size and weight, and to fill the large payload gap between the Saturn IB and Saturn V, a number of methods of uprating the Saturn IB have been studied by NASA and Chrysler Corp. of providing increased payload capability is discussed in this paper.  Four 120 in. United Technology Center UA-1205 solid propellant motors, originally developed for the Air Force Titan III program, are clustered around the S-IB first stage of the Saturn IB launch vehicle.  These four solid propellant motors provide the total thrust for liftoff of the vehicle, with S-IB stage ignition occurring just prior to burn-out and separation of the solid propellant motors.  The term "Zero Stage" is applied to this added stage.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152909">
                <text>Vehko, Vaino J.</text>
              </elementText>
              <elementText elementTextId="152910">
                <text>Ruhland, William E.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152911">
                <text>3/1/1966</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="152912">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152913">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="152914">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="152915">
                <text>Solid propellant rockets</text>
              </elementText>
              <elementText elementTextId="152916">
                <text>Saturn 1B launch vehicles</text>
              </elementText>
              <elementText elementTextId="152917">
                <text>Spacecraft propulsion</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152918">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="152919">
                <text>Reports</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="152920">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="152921">
                <text>Box 16, Folder 23</text>
              </elementText>
              <elementText elementTextId="210105">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152923">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152924">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="152925">
                <text>spc_stnv_000925_000942</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="152926">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17414</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10278" public="1" featured="0">
    <fileContainer>
      <file fileId="9027">
        <src>https://digitalprojects.uah.edu/files/original/20/10278/TheupratedSaturn_I_012208114543.pdf</src>
        <authentication>13c9ad846f77d2a4f528ed751afda843</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="153572">
                <text>TheupratedSaturn I_012208114543.pdf</text>
              </elementText>
              <elementText elementTextId="153573">
                <text>spc_stnv_000907</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153574">
                <text>"The uprated Saturn I - its growth potential &amp; future role in space."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153575">
                <text>Remarks by Vaino J. Vehko, Director of Engineering, Chrysler Corporation Space Division at 30th Annual Meeting, Aviation/Space Writers Association, Las Vegas, Nevada</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153576">
                <text>Vehko, Vaino J.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153577">
                <text>1967-05-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="153578">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153579">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="153580">
                <text>Apollo project</text>
              </elementText>
              <elementText elementTextId="153581">
                <text>Saturn launch vehicles--Design and construction</text>
              </elementText>
              <elementText elementTextId="153582">
                <text>Saturn 1 launch vehicles</text>
              </elementText>
              <elementText elementTextId="153583">
                <text>Apollo spacecraft</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153584">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="153585">
                <text>Speeches</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="153586">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="153587">
                <text>Box 22, Folder 22</text>
              </elementText>
              <elementText elementTextId="210113">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153589">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153590">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="153591">
                <text>spc_stnv_000900_000924</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="71">
            <name>Is Referenced By</name>
            <description>A related resource that references, cites, or otherwise points to the described resource.</description>
            <elementTextContainer>
              <elementText elementTextId="153592">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17682</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10916" public="1" featured="0">
    <fileContainer>
      <file fileId="9408">
        <src>https://digitalprojects.uah.edu/files/original/20/10916/Letttomrdavi_110110142006.pdf</src>
        <authentication>270d110f0f73789147d08fbc2197e44d</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="166116">
                <text>Letttomrdavi_110110142006.pdf</text>
              </elementText>
              <elementText elementTextId="166117">
                <text>spc_stnv_000393</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166118">
                <text>"Letter to Mr. David Christensen."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166119">
                <text>Letter to David L. Christensen from Ralph I. Villers responding to a request from Christiansen. Enclosed is the material requested.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166120">
                <text>Villers, Ralph I.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166121">
                <text>1969-07-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="166122">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166123">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="166124">
                <text>Apollo project</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166125">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="166126">
                <text>Correspondence</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="166127">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210608">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="70">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="166129">
                <text>Is part of: Saturn S-IV engines.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166130">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166131">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="166132">
                <text>spc_stnv_000375_000399</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11138" public="1" featured="0">
    <fileContainer>
      <file fileId="9733">
        <src>https://digitalprojects.uah.edu/files/original/20/11138/LettDaveChris1969.pdf.pdf</src>
        <authentication>d0f65286bc735c52b0e34656bce8ae0b</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="170731">
                <text>LettDaveChris1969.pdf</text>
              </elementText>
              <elementText elementTextId="170732">
                <text>spc_stnv_000372</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170733">
                <text>Letter to Mr. David L. Christensen.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170734">
                <text>Letter from C.A. Perkins to David L. Christensen regarding a request for information regarding cryogenic pump and motor development</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170735">
                <text>Villers, Ralph I.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170736">
                <text>1969-08-08</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="170737">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170738">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="170739">
                <text>Letter</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170740">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="170741">
                <text>Correspondences</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="170742">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210829">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170744">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="170745">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="170746">
                <text>spc_stnv_000350_000374</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="904" public="1" featured="0">
    <fileContainer>
      <file fileId="745">
        <src>https://digitalprojects.uah.edu/files/original/52/904/spc_lude_008_026.pdf</src>
        <authentication>b5a1927b10fd45b87eac5eaf4207547b</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="177171">
                    <text>�������������������</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="52">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="16118">
                  <text>Hermann Ludewig Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17117">
                  <text>Hermann Ludewig Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="17158">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/18"&gt;View the Hermann Ludewig Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201667">
                  <text>Hermann Richard Rudolf Ludewig was born October 12, 1898 in Berlin, Germany. From December 1916 to January 1919, he served in the German Army in Flanders during World War I. After the war, he worked as a fireman on a locomotive and in 1921, he entered school at Beuth-Schule, Hoehere Technische Lehranstalt der Stadt Berlin, from which he graduated with a degree in mechanical engineering in 1924. From 1925 to 1937, he worked for Orenstein and Koppel, a major engineering company, in Berlin, Germany. During this time, he married Emma Berta Pauline Jaglitz on June 12, 1935.&#13;
&#13;
Likely through his friend Bernhard Tessmann, with whom he worked at Orenstein and Koppel, Ludewig began work with the rocket development project in Peenemünde, Germany, which was under the direction of Dr. Wernher von Braun, in May 1937. Ludewig’s first position was the Deputy of Design Chief under Walter Riedel, and in February 1942, he became the Chief of Acceptance and Inspection under Dr. von Braun. Ludewig’s daughter Christel was born on November 20, 1939 while he was stationed at Peenemünde. On the night of August 17/18, 1943, the British bombed the Peenemünde facility as part of Operation Hydra, destroying the Ludewig family’s home; however, Ludewig and his family survived the bombing. After the raid, Ludewig transferred from Peenemünde to assignments in Nordhausen and Berlin.&#13;
&#13;
After the end of the war, the Ludewig family moved to Trebbin, Germany to manage the farm of his father. At that time, Trebbin was inside East Germany, and in the Soviet sphere of influence. Ludewig worked to conceal the fact that he had worked with the rocket team at Peenemünde, fearing he would be forced to work on the Soviet rocket program. In 1953, he made an agreement to join many of his former colleagues in the United States and the family escaped to Berlin. The family arrived in New York on October 31, 1953 and by November were in Huntsville. Ludewig worked on the Redstone and Jupiter rocket program at Redstone Arsenal for the Army Ballistic Missile Agency until 1960, when he transferred to NASA at the George C. Marshall Space Flight Center. He worked in a variety of capacities there, including in the Systems Office as a Special Assistant under Konrad Dannenberg on the Saturn project. He retired from NASA in 1967.&#13;
&#13;
Hermann Ludewig passed away in Huntsville, Alabama on March 2, 1986.&#13;
&#13;
The family established a scholarship in the memory of Emmy and Hermann Ludewig at the University of Alabama in Huntsville in 2000.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="16489">
                <text>spc_lude_008_026</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16490">
                <text>"Rocket City Astronomical Association."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16491">
                <text>The pamphlet includes a reprint of an article from RCAA publication &lt;i&gt;Space Journal&lt;/i&gt;, a history of the organization with photos, and membership information.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16492">
                <text>Vitra Engineering Company</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="16493">
                <text>1950-1959</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16494">
                <text>Von Braun, Wernher, 1912-1977</text>
              </elementText>
              <elementText elementTextId="16495">
                <text>Astronomical observatories</text>
              </elementText>
              <elementText elementTextId="16496">
                <text>Astronomy--United States</text>
              </elementText>
              <elementText elementTextId="16497">
                <text>Rocket City Astronomical Association</text>
              </elementText>
              <elementText elementTextId="16498">
                <text>Scientists--United States</text>
              </elementText>
              <elementText elementTextId="16499">
                <text>Telescopes</text>
              </elementText>
              <elementText elementTextId="16500">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="16501">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16502">
                <text>Pamphlets</text>
              </elementText>
              <elementText elementTextId="16503">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="16504">
                <text>Hermann Ludewig Collection</text>
              </elementText>
              <elementText elementTextId="16505">
                <text>Box 1, Folder 36</text>
              </elementText>
              <elementText elementTextId="205708">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="90">
            <name>Provenance</name>
            <description>A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. The statement may include a description of any changes successive custodians made to the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="16507">
                <text>This item was digitized for the Apollo 11 50th anniversary celebration.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16508">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16509">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="16510">
                <text>ap11_exhibit_2019_08</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="52" public="1" featured="0">
    <fileContainer>
      <file fileId="73">
        <src>https://digitalprojects.uah.edu/files/original/1/52/loc_hilt_0000006_0000042.pdf</src>
        <authentication>94ebf56693fc08ca3fd96cd86d9fe518</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="176613">
                    <text>.-..

~

.

-

~-

•

Remarks by Dr. We rnher von Braun. Dir ec t or
George C. Marshall Spa ce Flight Center
National Ae r onautics and Space Administration
Huntsville. Alabama
A l abam a Legislature
Montgomery, Alabarna
J une 20, 19 61, 11:00 a.m.

Your Excellency Gove rnor Patterson, Lieutenant Governor
Boutwell, Speaker Ashwo rth and gentlemen of this joint session of the
Legislature of Alabama:
I want you to know that it is a very real honor for me, a
citizen of A l abama . to add r es 5 you today in the Capit a l City of our
Great State .

1 deeply appreciate your thoughtfulness in inviting me

to be with you in this historic C a pitol Bu ilding .
It is my privilege to know a number of you pe r sonally , and

I wish I knew tTlore of you.

I'm su r e that if the appropriations for the

George C. Marshall Spa ce Flight Center carne directly from the
Legi s i"at ure of Alabama ins te ad of the Congress I would know many
more of you.
I have been privileged for some time, of cou r se, to know
Governor John Patterson.

In fact, I enjoyed a ve ry pleasant luncheon

and conve r sation in Washington wi t h the Gove rn or not so long ago.

•

�•
&lt;.

2

Also, I frequently see and talk with our own representatives
from Madison County:

Senator Dave Archer, Representative Roscoe

Roberts and Representative Luke Reynolds.

I should like to give a

little public credit to Dave and Roscoe and Luke for the tremendous
help they have been to the Marshall Space Flight Center and the U. S.
Army at Huntsville.

They have frequently helped pull us over the

rough spots as the rocket and space exploration business in Alabama
began to have more and more impact on the State and South.
I am. glad to say, too, that you gentlemen of the Legislature
have responded ITlore than once to our expanding needs.

And thanks to

the persuasiveness of our Madison County delegation -- and your own
good judgement and conscience - - I
as we wanted you to.

~m

glad to add that you responded

We are delighted, of course, that you did, and

we are grateful.
As you may recall, some of my former German colleagues
and I carne to Alabama from Ft. Bliss, Texas , some ten or

~leven

years ago, and six years ago this past spring we were awarded our
Alnerican citizenship.
I want to take advantage of this occasion to express my
sincere appreciation to the many fine citizens of this State for the
warm, truly Southern hospitality which they have extended to us.
We like -- and we are proud of -- our Alabama friends and neighbors.

•

�-"
3

As you will remember, during the past few years all of us in
Alabama have shared some exciting. history-making moments together.
First there were the pioneering Redstone and Jupiter missile

programs~

then our laounching of the Free World's first satellite around the earth,
built right here in Alabama; then our launching of the Free World's first
satellite around the sun, again built right here in Alabama; then only a
few weeks ago came our launching of the Free World's first man into
space.

And, 1 hasten to add, with the Saturn deep space rocket and

other programs now underway at the Marshall Center. we expect to ring
up a few more firsts before too long.

Even now a lot of people still ask me, "Why do you want to
go to the moon? II I like to remind them about one of this country's most
famous scientists.
When wise old Ben Franklin sent up his kite that day in the
thunderstorm, he got his knuckles singed by electricity.
Franklin learn by this experiment?
from the clouds would shock him.

Not much.

What did

Only that electricity

But because Ben was curious about

the world around him, his simple research -- plus a few other experiments conducted elsewhere -- stirred up a lot of interest.

A burst of

attention was then focussed on electrical research, and as a result, old
Ben Franklin's kite sparks flew around the world.

Today, we can't

drive a tractor, fly an airplane, light a house, or send a satellite into
space without electricity.

•

�,
4

My point here is that as wise as Ben Franklin was, he didn't
have the faintest idea of the great benefits that were in store for mankind
as a result of the first faltering experiments that he and others about that
time carried out.

But Franklin did have scientific curiosity.

It was

curiosity that made him go fly a kite that day. not some mysterious.
prophetic knowledge that he was about to help pave the way for va'st new
benefits for all mankind.

So when somebody tells you to go fly a kite, don't punch him
in the nose.

Who knows?

You too might discover electricity.

Incidentally, as you know, Benjamin Franklin was not only
a s.c ientist and inventor, but he was also a great statesman and politician.

In fact, he would be equally as much at home -- were he alive today -with the employees of the Marshall Space Flight Center as he would with
the m.em.bers of our Legislature.

And after reading som.ething of som.e

of the rem.arkably skillful operations conducted around Goat Hill here
lately. I wouldn't be surprised if we couldn't learn m.ore fro.m. Franklin
about our business than you could learn from. hitn about yours.
It is curiosity that sets m.an apart .

•

It is curiosity that m.akes hitn learn.
This has been true throughout history .... first curiosity; then
learning; then advancement.

•

�•

5

But the guy who is curious -- the restless searcher for new
knowledge -- never knows where his curiosity will lead him.

All he

knows is that SQIne time, in Borne way. the knowledge he digs up will
better the lot of his fellow man.

For instance, the great bacteriologist, Sir Alexander Fleming.
found one day that certain bacteria were killed by a mold.

This "accidental

discovery -- which happened because Fleming was curious about mold -gave us penicillin.
He didn't have the faintest idea that what he saw under his
microscope that day would end up by saving many, many thousands of
h~an

liv es.

It's always that way.

•

We just never know what the next bit of information will bring
f orth.
That's why we want to -- and why we must -- explore space.
!tIS

our next frontier, our newest challenge. and the greatest unknown

today.
I am convinced that the exploration of outer space will produce
undream e d of benefits for all of us.

And the very fact that nobody knows

for sure what all of these benefits will be opens new prospects and excites
our imagination to further progress .

It has been said (Henry Ward Beecher)

that lithe soul without imagination is what an observatory would be without
a telescope.

II

Now how are we going to space?

�6

I'd like now to show you a few slides of actual space hardware
and d i scuss with you some promising methods we plan t o

US~

to get out

there.
The other day The President said we should go to the moon.
Well, he's not alone.
Let us just hope that somebody named Ivan Ivanovich or Yuri
Gagarin doesn't get there first.

How are we going to get there?

And when?

F i rst, l e t me say here and now that this country has nothing
to be ashamed o f in c omparison with the Soviets in space exploration to
date.

This c omparison may have been valid three years ago, but today

we have orbited many more scientific satellites than they; and from
them we have gleaned a great deal more new flcientific information from.
the universe than anyone else.
The area where we are obviously behind is in the field of big
boosters .... the big push.

That is the bottleneck.

That',s why I should

like to talk with you today about our efforts in big space booster development.

I shall discuss two in particular:

The Saturn and Nova .

But, before I go into that let me say that we're all highly
gratified , of course, at Alan Shepard's successful and historic voyage
aboard the Mercury-Redstone rocket.

•

�7

LIGHTS OFF
SLIDE I
But to achieve this we had to fall back on that old reliable
Alabama-made Redstone rocket.

The Redstone . taking off on the left ,

was first developed as a weapon .

It has never yet been fired in anger .

But when we got into trouble (and maybe angry) because the Russ.ians
beat us up there with the Sputniks, we had to call on the Redstone to
put the first American earth satellites into orbit.

In the middle is the

Jupiter C which lofted Explorer satellites I , III, and IV.

Then after

Yuri Gagarin 1 s orbit ... . in an effort to stay in the man-in-space race .. ..
we again relied on that old reliable Redstone to boost our first American

•
into space.

You see it on the right -with the space capsule on top.

Following the Mercury-Redstone will be the Mercury-Atlas
which will'J?lace an American in orbit later this year.
Well, as to How and When . .. . to put it sinlply the United States
now has a whole stable-full of other good rockets to do the job with; and
from all indications we're going to accelerate our most vital space exploration programs and tinletables rapidly and forcefully.
I should like now to talk with you about two big space exploration
vehicles .

SLIDE Z

�8

First the Saturn .

Thanks to a little clever fCfking .... and with

the cooperation of the Governor's press secretary .... we see the Saturn
deep space rocket right on the lawn of our Capitol building.
This particular ve rs ion of Saturn stands about 18 stories. high .
The Saturn rocket not only compares in size with the Capitol, but I suspe,ct
a comparison in internal complexity and perhaps an ability to shift courses
might be made,
With the belp of private industry and universities around the
country, the Saturn space carrier vehicle is under development here in
Alabama for the National Aeronautics and Space Administration.
Several versions of the Saturn are being considered.
smallest --

80

called

Even the

is the world's largest known rocket.

SLIDE 3
Here is a cutaway of the Saturn booster showing· the fuel and
oxygen tanks.

There are eight tanks six feet in diameter surrounding

one tank in the middle of the cluster that is nine feet in diameter.
of the outer tanks -- and the middle t ank - - hold liquid oxygen .

Four

The

remaining carry the kerosene.
You can't see them all here. but the booster has eight keroseneoxygen engines. each of which can develop 188.000 pounds of thrust. By
"thrust" we mean lifting force.

•

�., •
9

The Saturn represents a four-fold jwnp in thrust power ....
from the 360. 000 pound thrust Atlas to the 1.5 million pound thrust
Saturn.

This is equal to the energy developed by almost all the

100, 000 or more automobiles in Montgomery, Alabama.
This particular first stage will be used to boost the first two
versions of the Saturn rocket now under consideration into space.
For our purposes, we call the three versions of the Saturn
the C-l, C-2. and C-3.

SLIDE 4
Here is the second stage of the first -- or C-l -- version
of Saturn.

This stage will be powered by six hydrogen-oxygen engines,

each developing 15, 000 pounds thrust.
These new hydrogen engines represent the first step forward
in advanc ed li quid propellants .

Our earlier space vehicles generally

used sorne type of kerosene as fuel.
This stage is some 17 feet in diarneter and about 40 feet tall.

SLIDE 5
A new developrnent in liquid rocket engines is underway to
power this, t he number two stage. of the second -- or C-2 -- Saturn
vehicle,

Four new hydrogen engines. each developing 200,000 pounds

thrust, will be combined to give this stage a total of 800,000 pounds
thrust.

This new engine will be a really big step in the development

of hydrogen engines ... , frorn 15,000 pounds to 200, 000 pounds thrust.

SLIDE 6

•

�..
10

Here at a glance you can get a good look at the three Saturns.
The first version, . on the left, can put la, 000 pounds of payload into low
earth orbit.
earth.

It is also designed· to put three men into orbit around the

The £irst launching of the Saturn C - l . without a payload,. is

schedul ed for the last quarter of this year.
about 180 feet tal1 .

With payload, it stands

It weighs about 1, 000, 000 pounds at liftoff.

The second Saturn, in the middle, will be about 210 feet high.
It will have three stages and will be capable of orbiting manned or un-

manned payloads of more than 44, 000 pounds around the earth, soft -lan d
a 3,000 pound payload on the moon and back to earth, or put instruments

•

on Mars or Venus.
The third Saturn shown here is a rather radical departure over
the other versions in that the booster will be powered by two huge new
kerosene engines, each of which develops 1. 5 million pounds of thrust.
This Saturn booster, then, will be twice as powerful -- with three
million pounds thrust - - as the earlier version.

The second stage will

have the same four 200,000 pound hydrogen engines, and the third will
have six hydrogen engines with 15,000 pounds thrust each.

•

1,6, OOtIt can put"*, 000, 000 pounds into earth orbit, or fly a multiple
crew around the moon or send 24,000 pounds on a one-way trip to Mars.
Ten launchings of research and development vehicles are
scheduled in the current Saturn program.

�::

.

11
We expect the Saturn deep space rocket to be the major rocket
for U. S. space exploration for a number of years.

It is the first large

rocket to be developed in the U. S. for scientific peaceful research.

SLIDE 7
When the Saturn puts men into space it will carry a spacecraft
known as Apollo.

Here you see the Saturn booster out in space separating

from the remaining stage and the Apollo.

The Apollo is not only an

extension of the Mercury-man-in-space program, it has other capabilitie.8.
For instance, men can use it to observe the surface and envirorunent of
the moon before a manned landing takes place.

The Apollo is also

sufficiently flexible to serve as a manned orbiting laboratory .... a
laboratory where man can perform useful space research in a low earth
orbit.

This orbiting laboratory is a necessary step leading toward a

permanent {nanned space station.
This will be the main application of the Saturn rocket ... . man
into space.

SLIDE 8
Here is a promising plan to recover Saturn boosters and thus
save a lot on money.

Rockets are usually considered expendable, but by

using this unique Rogalla kite -- called a paraglider -- _we think we can
return boosters and some upper stages to land and fly them again.

•

�•

IZ

The paraglider would actually be guided down from the ground -as you see here -- through a radio remote cont r ol system.

Lines attaching

the kite to the booster can be pulled in or let out to cont r ol the kite as it
descends and finally approaches the landing strip.
SLIDE 9
The special barge was built because it's about the only way -- at
present, anyway -- that we can get the Saturn booster from the Marsha ll
Center to Cape Canaveral.

However, due to an accident at the Wheeler

lock on the Tennessee River not long ago , it looks as if we're going to have
to use two water - going vessels temporarily.
name of this barge -- to get it to the lock.

WeI ll use the Palaernon -- the

ITlQve

it by a whee led transporter

around the lock. then re-load on a former Navy barge and proceed to the
Cape.

It 1 s a 2,200 mile trip by river. the intercoastal waterway that runs

across the southern tip of Alabama. the Gulf of Mexico and the Atlantic Ocean.
The skipper of this unusual craft describes the barge as a crOBB
between a mine sweeper, a garbage scow and a blimp hanger.
SLIDE 10
Moving the upper stages of Saturn by air is a possibility.

A

rather startling proposal by Douglas Aircraft has been made to carry
the Saturn second stage on top of an aircraft in piggy-back fashion.
seriously looking into this scheme.

We 1 r e

The idea is to save time and money.

�13

When I first studied this proposal I couldn't help thinking
about the caterpillar who, like too many of us, never can accept a new
idea.

Two caterpillars were strolling along in the dust one day when a

butterfly went by overhead.

One caterpillar said to the other:

"They'll

ne ve r get me up in that thing. "
SLIDE 11

Here is Saturn with a nuclear upper stage.

In this concept of

a nuclear rocket, hydrogen is heated by passing it through a nuclear
reactor and then exhausted through a nozzle yielding about twice the
propellant economy you get with a hydrogen oxygen engine.

With this

rn.ore efficient engine, smaller quantities of propellants will be needed,
thus ITlaking ou r payloads a lot bigger.

•

NASA and the Marshall Space

Flight Center are making a number of studies in this area.

Also, NASA

and the Atomic Energy Commission jointly are pushing forward the pace
of the Rover development, as the nuclear rocket reactor program is
called.

We should fly our first prototype nuclear rocket by 1966.

This

first nuclear rocket will be called RIFT .... for" Reactor In Flight Test tt •
Itls easy to see that we call dream up weird alphabetical abbreviations
with the best of them.
The RIFT nuclear vehicle will be flight-tested as a second
stage of the Saturn C-3.

)

.

�14

SLIDE 12
As we approach manned space travel involving several men . ...
and women, eventually, of course .... we must put up much bigger payloads .
Incidentally. Bob Gilruth, the man in charge of the U. S. Mercury
program, was asked the other day if he plans to use women astronauts in the
man-in-space program .

With a straight face, Bob replied:

"Well, we are

reserving 110. pounds of payload for recreational equipment.
T o put these bigger payloads up it takes thrust.

II

Here is a dramatic

example.
The smallliquid engine you see creates 188, 000 pounds thrust.
Eight of these make up the Saturn first stage which produces, as you now
know. ' 1. 5 million pounds.

Then , at one stroke. comes a single engine that

produces the same amount of thrust - - · 1. 5 million pounds - - that the whole
Saturn engine~ cluster produces .

Both are kerosene engines .

To express myself in more familiar terms, this big rocket engine
produces 33, 000 , 000 horsepower, compared with these two diesel locomotive
units at the left which together produce only about 4, 000 horsepowe r .

Now

by clustering a batch of these big engines you can see that we can really

•

achieve power.
SLIDE 13
And h ere is where we will need it.
possible Nova space vehicle concepts.
Saturn.

This slide depicts one of the

Nova is the next big step beyond

•

�15

By clustering the Saturn C-3 boosters -- those first stages
with the two 1. 5 million pound single chamber engines -- on the left
we come up with this clustered Nova vehicle in the center.

For very

high speed it would be advantageous to increase the propellant capacity
of the top stage.

Thus Nova would offer us an escape payload of up to

140, 000 pounds.

By "escape" we mean escape from the earth's gravity .

With Nova, we could land a locomotive on the moon if anyone
wanted one there.

What is more important, this Nova space rocket can

put a spacecraft -- like the one on the right -- with three men on the

moon and return them to earth, and at the same time leave 40, 000
pounds of supplies and equipment to support a manned lunar station .

•
With a nuclear third stage, it could go into orbit around Mars and return
to earth later on.

Nova vehicles of this class give us the most direct

approach to manned lunar and planetary exploration.

LIGHTS ON

Before Nova, though, comes Saturn.

I might mention here

that the Saturn space rocket will be shown to the public for the first time
on July 1.

In fact you can see two fully assembled Saturn rockets which

we will display at an open house we are having to celebrate the first
anniversary of the Marshall Center.

�16

We will also erect a

Mercury~Redstone

capsule like the one Al Shepard rode in.

rocket, complete with a spa.ce
We would be most happy to

have any of you who can to visit us that day.

We hope it will provide

you and the public with a pretty good .- and rather interesting -- look
at Alabama's major role in the national space program.

We will conduct

four live, that is hot, static tests of a Saturn engine for you.

Also; for

the first time each of the 10 space research laboratories of the Marshall
Center will be opened to the general public.
8: 30 to 3: 30.

Our open house will be from

I'd like to remind you that Huntsville - - for the first time

in several years -- is on Central Standard Tirne this swnmer .

As a

reward for our cooperation in staying on standard time, however, they
give us the privilege of going to work at seven o'clock in the morning .
July 1 is on Saturday, so I s,;!ggest you come up to Huntsville for a visit
to the space center and leave your politics ba.ck here.
Now .... what will it take for this country to regain lost prestige
and once more asswne its place as the scientific and technological leader
among nations?

More particularly, what can the people of Alabama do?

What can the people in this room do?
These slides you have just seen show how much the national
space program depends upon the work going on here in the State of Alabanla.
Just as important for the country's well-being, of course, is the enormous
national defense effort being carried out at Huntsville by the Army Ordnance
Missile Command and the Army Ordnance Guided Missile School.

•

�•
17

The 25. 000 persons employed at Huntsville who carryon this
work receive an annual payroll of about $200, ODD, DOD,

The total money

spent by these agencies each year is nearly Z. 2 billion dollars. and about
16 per cent of this (or 350 million dollars) is spent in Alabama with companies
and educational institutions throughout the state.
I haven't mentioned this to Dave Archer yet, but when the

~igure

of 25, 000 arsenal and Marshall Center employees was ITlentioned in a
ITleeting in Huntsville th e other day. somebody suggested:
"With all these voters around here, why don't we elect a Senator
frOrri Redstone Arsenal?"

The Marshall Center is now in the process of hiring more than

•
1600 new employees.
engineers

Most of the people we need

and ~ scientists.

60

urgently are graduate

In other words, highly skilled and e ducated men

and women .
Although a substantial nwnber of our present technical people
are products of Alabama's educational system , most of ther;,., frankly. have
come f rom e lsewhere ... . from all 50 states and several other countries, as
a matter of fact.

•

�18

You've heard and seen something now about the kind of people
we need and what we need them for.

We need the best, and we need them

for one of the most vital jobs in the history of free men.
This. I submit, is substantial evidence to show that opportunity
is indeed knocking on Alabama's door, and knocking hard, just as oppor tunity knocked on California's door a few decades ago when the aircraft
industry was beginning to blossom.
The question today is. II Will Alabama open the door?"
As a proud citizen of this state and of this count ry

I

I feel a

responsibility to raise this question with you and to discuss it openly
and frankly.
Shakespeare said. "There is a tide in the affairs of men, which,
taken at the flood, leads on to fortune".
now -- but is passing fast.

For Alabama. the tide is at flood

My appeal to you is to recognize this and to

take action today while the opportunity is still available.

I am sure there

are very few problems in Alabama which could not be solved with more
money -- the proper capital investment at this time can produce that
money for the State of Alabama.
Now what investment am I s peaking of?

I am speaking of an

investment in people -- strong. capable, educated people!

Opportunity

goes where the best people go, and the best people go where good
education goes.

•

�19

Unless we get -- and keep -- many more bright young men and
women very soon to help us carry the present load, our programs -- and
Alabama -- will suffer.
, This danger was sensed last winter by a keen Washington official
during his visit with us.

We were asking for rn.ore funds for construction

of facilities, and he raised the question as to whether it was really .smart
for the Federal Government to continue to build up its facilities in a place
which has much difficulty in obtaining the right kind of senior personnel
to operate these facilities,

like a business:

You see, a goverrunent agency functions much

Success is not guaranteed by past successes; no one in

Washington is assuring our future; if we begin to falter -- as we most
certainly will without the right kind of personnel -- serious consequences
will surely

r~esu1t.

To lTlake Huntsville lTlore attractive to technical and scientific
people across the country -- and to further develop the people we have
now - - the acadelTlic and research environment of Huntsville and AlabatTla
lTlust be Unproved and Unproved UnlTlediately.

As lTlany of you know, the

University of AlabalTla has a University Center in Huntsville, which is
definitely a step in the right direction.

In addition they have just opened

a slTlall Research Institute closely affiliated with this Center.

•

�20

As this Institute grows. large corporations will be encouraged to establish
research organizations nearby to form an industrial research park as a part
of the University complex, which in turn will give birth to major new industries
throughout the State.
Unless, however, large swns of lTloney can be found immediately
to improve and enlarge this University complex, its real value may come too
late to help us attract and develop the kind of people we must have.
The citizens of Alabama should recognize even more fully that
the United States, as well as the other leading countries of the world, now
lives in a technological age.

The efforts along this line that have been taken

in the past -- in developing our technological manpower and other industrial
resources -- will not, I repeat , will not suffice to keep pace with the other
states and nati ons today.
It's the university climate that brings the business.
What do you think attracted the aircraft industry to the Los Angeles
area?

The desert and smog?

No, it was U. C. L. A. and Cal Tech and the

Art Institute and St. Mary's and The University of Southern California.
Was it beans that brought great electronic and other industri es
to Boston?

It was the Educational Triangle of Boston University, Harvard

and M. 1. T.

A friend of mine said last week that if M. 1. T. was as close to

Huntsville as are the University of Alabama and Auburn University that
M. 1. T . would own Redstone Arsenal.

•

�21

Let's be honest with ourselves about it:

it's not water, or real

estate. or labor. or power, or cheap taxes that brings industry to a state
or city.

It's brainpower.

make it rich.

Nowadays, brainpower dwnped in a desert will

Right now you could run a profitable electronics firm on

the moon, if the company liked the climate.

Educational c1hnate, that is.

Without question, such a climate is the most important
resource in attracting new people and new ideas.
process.

si~gle

It's a self-generating

Once you get it started, it snowballs.
The top people in industry and goverrunent today like to improve

themselves.
them.

TheY llike flourishing research institutions.

They thrive on

1£ they have a bachelor's degree, they want a master's.

If they

•
have a master's, they want a Ph. D.
to teach and do research.
are not satisfied.

And if they have a Ph. D. they want

So our young engineers with bachelor's degrees

If they could get advanced degrees and remain near an

academic environment, they would stay with us.

Lacking such opportunities

they want to move on to California and Massachusetts.
While we are trying to bootleg young engineers from other states ...
because w e don't produce them here .... the same states are stealing our
senior scientists,

�22

The State of Alabama ... . in this case

I

you .... has a very real

responsibility to promote the advancement of science and higher education.

In short, itls up to you to create the right climate.
In Huntsville we are trying to create a vigorous and varied
educational and research clilnate.

The seed is sown with the University

Center and the infant Research Institute.

But the seed is starving.

It

needs s o mething green .... Money.
To be specific. the Research Institute needs .... at this very
moment . . . . three million dollars for buildings and equipment.

Following

this first investment the Institute will not only be self-sustaining, but will
enrich the State both financially and culturally.
Let me remind you of something:

the rocket and missile business

at Huntsville pours 350 million dollars annually into the State of Alabama.
That's

more ~ than

a hundred dollars a year per man, woman and child.

The only reason that Alabarrta has this bonanza at all is because
the Army had a big chunk of spare real estate that served the immediate
purpose of providing a home.

We've lived in that home for more than

ten years now, and it's about time we got a schoolhouse.

And everything

that goes with it.
For a three million dollar investment now, I promise you that
you'll reap billions.

Easily billions.

is more than a third of a billion.

350 million dollars, don't forget,

�23
The President has asked the Congress for from seven to nine
billion dollars for space for the next five years alone.
that dough will e nd up in Alabama .

A big hunk of

End up in Alabama, that is

I

if

Alabama can attract the kind of people we have to have . provide them
,

with a decent educational. scientific and cultural climate . and make
them want to stay.
If Alabama does this. then the prosperity and culture of the

entire state will g r ow and fl ou rish .

If Alabama doesn't . ... Well, I'd hate to see those Saturn
and Nova r ockets begin that long and lucrative trip to the moon from
the State of California.

•

Now, it is not my place to tell you what to change or how to
change it . but I tru s t you may take this warning seriously.
I' m not a s king for something next year, or n ext month, or
next week, or tomorrow .

I'm asking that you -- each of you, individually

and collectively -- do something now .
On one hand , you have the greatest opportunity fo r wealth ,
prosperity and culture ever offered to this state and seldom to any other
state .

While on the other, you face the greatest of dangers . . . . n ot only

the danger of a ggress ion and lo ss of prestige, but also the danger of
economic competition from other cities • . states and nations all over
the world .

�Z4

When a prospective employee looks at us he does not try to
decide whether to liv e in Huntsville or Montgomery , he is choosing
between Alabama and Los Angeles. New York or Boston.

It is your

decision whether you want to make Alabama attractive enough to stay
in this race.
I do not believe you will back away from this competition .
I believe I know the citizens of my state well enough to say with full
confidence that they will accept this challenge with the gusto of Macbeth
as he said:

"Lay on, Macduff. and damn'd be hiIn that first cries.

'Hold, enough!

II'

•

I

�I

•

"'_-..

•

. --

~

~-

,

, .~

~

# !

4

Q

•
•

��SATURN
C-I FIRST STAGE
C-2 FIRST STAGE

�SATUR!'\
C-I SECOND STAGE

•

�'~------~---------

SATURN
c- 2

SECOND STAGE

•

�Story Bldg

--

•

��- MAT
'-

•

-,

;T

0'-

•

",~
"
•

~

�•

�•

�•

��MODULAR NOVA CONCEPT

.
"'~ '=""lP

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="1">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1">
                  <text>Heinz Hilten Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3767">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/29" target="_blank" rel="noreferrer noopener"&gt;View the Heinz Hilten Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="32747">
                  <text>Heinz Hilten Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201665">
                  <text>At the start of the Second World War, Heinz Hilten (1909 to 2013) was drafted into the German army, where he worked with von Braun’s V-2 rocket team at Peenemünde. In 1954, Hilten made his way to America, where he rejoined von Braun.&#13;
&#13;
Hilten helped plan the growth of Alabama’s Redstone Arsenal until 1960, when he began designing laboratories, control centers, test stands, and administrative buildings for the newly minted Marshall Space Flight Center; Hilten also helped design the Saturn rocket program.&#13;
&#13;
Hilten was also a founding member of the Huntsville Symphony Orchestra.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1008">
                <text>Transcript of a speech given by Wernher von Braun to the Alabama Legislature.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1009">
                <text>Aerospace industries</text>
              </elementText>
              <elementText elementTextId="1010">
                <text>Alabama. Legislature</text>
              </elementText>
              <elementText elementTextId="1011">
                <text>George C. Marshall Space Flight Center</text>
              </elementText>
              <elementText elementTextId="1012">
                <text>Saturn Project (U. S.)</text>
              </elementText>
              <elementText elementTextId="1013">
                <text>University of Alabama in Huntsville</text>
              </elementText>
              <elementText elementTextId="1014">
                <text>University of Alabama in Huntsville. Research Institute</text>
              </elementText>
              <elementText elementTextId="1015">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="1016">
                <text>Madison County (Ala.)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1017">
                <text>Von Braun, then the director of Marshall Space Flight Center in Huntsville, Alabama, delivered this speech to the legislature in 1961. In the speech, he emphasizes that Alabama must take advantage of its position in the aerospace industry and create a robust "academic and research environment" in Huntsville to attract businesses that "will give birth to major new industries throughout the state." He exhorts the legislature to fund the newly established University of Alabama Research Institute (now part of the University of Alabama in Huntsville), arguing that "the Institute will not only be self-sustaining, but will enrich the State both financially and culturally." The legislature later approved von Braun's request of $3 million for the Research Institute, enabling the purchase of 200 acres of land for the campus and the construction of the Institute in 1964. The speech includes copies of slides von Braun used during his presentation, including diagrams of Saturn and Nova rockets as well as a mockup of a Saturn rocket on the lawn of the state capitol in Montgomery.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1018">
                <text>Von Braun, Wernher, 1912-1977</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="1019">
                <text>Heinz Hilten Collection</text>
              </elementText>
              <elementText elementTextId="1020">
                <text>Box 2</text>
              </elementText>
              <elementText elementTextId="205280">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1021">
                <text>1961-06-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1022">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1025">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1026">
                <text>Photographs</text>
              </elementText>
              <elementText elementTextId="1027">
                <text>Speeches</text>
              </elementText>
              <elementText elementTextId="1028">
                <text>Transcripts</text>
              </elementText>
              <elementText elementTextId="30169">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="30170">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="1029">
                <text>loc_hilt_000006_000042</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="1030">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1981" public="1" featured="0">
    <fileContainer>
      <file fileId="1829">
        <src>https://digitalprojects.uah.edu/files/original/91/1981/spc_geis_000001_000041.pdf</src>
        <authentication>826fc6a2ebb2501b2f32a7ec24ef0910</authentication>
      </file>
    </fileContainer>
    <collection collectionId="91">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="39392">
                  <text>Ernst Geissler Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="39393">
                  <text>Ernst Geissler Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201588">
                  <text>Ernst D. Geissler was born on August 4, 1915 in Chemnitz, Saxony, Germany, where he attended grammar school and high school until 1934. From there, he left to attend a technical university in Dresden, Germany, where he graduated with a diploma in Technical Physics. After graduating, he went to work with the Von Braun missile team, where he eventually patented new steering methods for guided missiles and homing devices against aircraft.&#13;
&#13;
On November 16, 1945, Geissler and his wife, Gerda K. Stricker, immigrated to the United States. Geissler began to work with the U.S. Army in Fort Bliss, Texas as a group leader for flight mechanics and aerodynamics on the Hermes II missile. After five years, Geissler went on to work for Redstone Arsenal as the Director of the Aeroballistics Laboratory in charge of theoretical and experimental aerodynamics and flight mechanics. While there, Geissler helped develop the Explorer I satellite and the Pioneer V space probe, and the Redstone, Jupiter, and Pershing missiles. He also developed patents for an aerodynamically stabilized missile and an artificially stabilized missile.&#13;
&#13;
In 1960, Geissler left Redstone and joined the George C. Marshall Space Flight Center of NASA. He worked as the Director of the Aerodynamics and Astrodynamics Laboratory, working on the Saturn I - Saturn V family and space shuttle development. In 1973, Ernst Geissler retired from NASA and eventually passed away on June 3, 1989.</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="205158">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/87"&gt;View the Ernst Geissler Collection finding aid on ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="39380">
                <text>spc_geis_000001_000041</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39381">
                <text>"Firing of Explorer I."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39382">
                <text>This speech was given by Wernher von Braun, then the director of the Development Operations Division at the Army Ballistic Missile Agency, at the 1958 ASME-ARS Aviation Conference in Dallas, Texas.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39383">
                <text>Von Braun, Wernher, 1912-1977</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39384">
                <text>1958-03-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="39385">
                <text>1950-1959</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39386">
                <text>Speeches</text>
              </elementText>
              <elementText elementTextId="39387">
                <text>Text</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="39388">
                <text>Ernst Geissler Collection</text>
              </elementText>
              <elementText elementTextId="206388">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39390">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="39391">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10846" public="1" featured="0">
    <fileContainer>
      <file fileId="9359">
        <src>https://digitalprojects.uah.edu/files/original/20/10846/Meetwithhuntcomm_073112203222.pdf</src>
        <authentication>93ad7427812c0f94d10267f703b51eff</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="164808">
                <text>Meetwithhuntcomm_073112203222.pdf</text>
              </elementText>
              <elementText elementTextId="164809">
                <text>spc_stnv_000447</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164810">
                <text>"Meeting with Huntsville community leaders, Morris Auditorium."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164813">
                <text>1969-11-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="164814">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164815">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="164816">
                <text>Apollo project</text>
              </elementText>
              <elementText elementTextId="164817">
                <text>Scientists</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164818">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="164819">
                <text>Transcriptions</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="164820">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210563">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164822">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164823">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="164824">
                <text>spc_stnv_000425_000449</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="182488">
                <text>Von Braun, Wernher, 1912-1977</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="182497">
                <text>Transcription of a conversation with Wernher von Braun.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10876" public="1" featured="0">
    <fileContainer>
      <file fileId="9399">
        <src>https://digitalprojects.uah.edu/files/original/20/10876/Letttothevicepres52461_121008162821.pdf</src>
        <authentication>0a7ec688d237345df716db79233b0273</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1033">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="3772">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/60" target="_blank" rel="noreferrer noopener"&gt;View the Saturn V Collection finding aid in ArchivesSpace&lt;/a&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="43">
              <name>Identifier</name>
              <description>An unambiguous reference to the resource within a given context</description>
              <elementTextContainer>
                <elementText elementTextId="17145">
                  <text>Saturn V Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="201655">
                  <text>&lt;p&gt;The Saturn V was a three-stage launch vehicle and the rocket that put man on the moon. (Detailed information about the Saturn V's three stages may be found&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_first_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_second_stage.html"&gt;here,&lt;span&gt; &lt;/span&gt;&lt;/a&gt;and&lt;span&gt; &lt;/span&gt;&lt;a href="https://www.nasa.gov/centers/johnson/rocketpark/saturn_v_third_stage.html"&gt;here.&lt;/a&gt;) Wernher von Braun led the Saturn V team, serving as chief architect for the rocket.&lt;/p&gt;
&lt;p&gt;Perhaps the Saturn V’s greatest claim to fame is the Apollo Program, specifically Apollo 11. Several manned and unmanned missions that tested the rocket preceded the Apollo 11 launch. Apollo 11 was the United States’ ultimate victory in the space race with the Soviet Union; the spacecraft successfully landed on the moon, and its crew members were the first men in history to set foot on Earth’s rocky satellite.&lt;/p&gt;
&lt;p&gt;A Saturn V rocket also put Skylab into orbit in 1973. A total of 15 Saturn Vs were built, but only 13 of those were used.&lt;/p&gt;</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="165358">
                <text>Letttothevicepres52461_121008162821.pdf</text>
              </elementText>
              <elementText elementTextId="165359">
                <text>spc_stnv_000402</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165360">
                <text>"Letter to the Vice President of the United States and White House."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165361">
                <text>This is an attempt to answer some of the questions about our national space program raised by The President in his memorandum to you dated April 20, 1961.  I should like to emphasize that the following comments are strictly my own and do not necessarily reflect the official position of the National Aeronautics and Space Administration in which I have the honor to serve.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165363">
                <text>1961-04-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="165364">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165365">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="165366">
                <text>Space race</text>
              </elementText>
              <elementText elementTextId="165367">
                <text>Aeronautics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165368">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="165369">
                <text>Correspondances</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="165370">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210568">
                <text>University of Alabama in Huntsville Archives, Special Collections, and Digital Initiatives, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="70">
            <name>Is Part Of</name>
            <description>A related resource in which the described resource is physically or logically included.</description>
            <elementTextContainer>
              <elementText elementTextId="165372">
                <text>Is part of: Dr. von Braun / NASA HQ Correspondence July 1968.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165373">
                <text>en</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="165374">
                <text>This material may be protected under U. S. Copyright Law (Title 17, U.S. Code) which governs the making of photocopies or reproductions of copyrighted materials. You may use the digitized material for private study, scholarship, or research. Though the University of Alabama in Huntsville Archives and Special Collections has physical ownership of the material in its collections, in some cases we may not own the copyright to the material. It is the patron's obligation to determine and satisfy copyright restrictions when publishing or otherwise distributing materials found in our collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="165375">
                <text>spc_stnv_000400_000424</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="182483">
                <text>Von Braun, Wernher, 1912-1977</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
