<?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/browse?output=omeka-xml&amp;page=60&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-09T11:51:35+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>60</pageNumber>
      <perPage>20</perPage>
      <totalResults>8239</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="13784" public="1" featured="0">
    <fileContainer>
      <file fileId="10414">
        <src>https://digitalprojects.uah.edu/files/original/193/13784/Defense_Billboard_113_001.pdf</src>
        <authentication>614e12684bde60f7bd0eded827d0f329</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="197471">
                    <text>B I L L B O A R D 113
S7I1eJ'f£nrForC?5 'n'0rma,l0n Service • Department of Defense
1601N. Farfax StreetSuite 312. •Alexandria, VA 22314-2007 • (703) 428-0283. DSN 328-0283

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="193">
      <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="194954">
                  <text>Defense Billboard Posters</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="195200">
                <text>Defense_Billboard_113</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195201">
                <text>"Somewhere...a bugle softly sounds. The message of renown, And some inside their buildings wait Until the flag comes down. And others run to get their cars Quite harrowed or dismayed, Afraid that they will not reach the gate Before retreat is played. Not thinking of the flag or those Who fought to keep it flying. How many would be glad to stand, Whose bodies now are mute, Or have no hand that they might raise And stand in proud salute. So accept it not as duty But a privilege even more And receive it as an honor Instead of just a chore. "</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="195202">
                <text>D2.9:D36/2/No.113</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195203">
                <text>Military soldier saluting a half-mast flag in a graveyard</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195204">
                <text>Department of Defense</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="195205">
                <text>1997-05-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="195206">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195207">
                <text>Department of Defense poster</text>
              </elementText>
              <elementText elementTextId="195208">
                <text>United States--Department of Defense</text>
              </elementText>
              <elementText elementTextId="195209">
                <text>Military cemeteries</text>
              </elementText>
              <elementText elementTextId="195210">
                <text>Soldiers</text>
              </elementText>
              <elementText elementTextId="195211">
                <text>United States -- Flags</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195212">
                <text>Posters</text>
              </elementText>
              <elementText elementTextId="195213">
                <text>Still Image</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="195214">
                <text>The University of Alabama in Huntsville M. Louis Salmon Library</text>
              </elementText>
              <elementText elementTextId="195215">
                <text>Defense Billboards Posters</text>
              </elementText>
              <elementText elementTextId="195216">
                <text>Case 1, Drawer 1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="195217">
                <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="195218">
                <text>This material may be protected&#13;
under U. S. Copyright Law (Title 17,&#13;
U.S. Code) which governs the&#13;
making of photocopies or&#13;
reproductions of copyrighted&#13;
materials. You may use the digitized&#13;
material for private study,&#13;
scholarship, or research. Though&#13;
the University of Alabama in&#13;
Huntsville Archives and Special&#13;
Collections has physical ownership&#13;
of the material in its collections, in&#13;
some cases we may not own the&#13;
copyright to the material. It is the&#13;
patron's obligation to determine&#13;
and satisfy copyright restrictions&#13;
when publishing or otherwise&#13;
distributing materials found in our&#13;
collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="195219">
                <text>Defense Billboards</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13851" public="1" featured="0">
    <fileContainer>
      <file fileId="10373">
        <src>https://digitalprojects.uah.edu/files/original/193/13851/Defense_Billboard_54_001.pdf</src>
        <authentication>3d4717d7a3c1ddfb09fed011e3b40479</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="197430">
                    <text>a bugle softly sounds
The message of renown,

And others run to get their cars
Before retreat is played.
Not thinking of the flag or those
Who fought to keep it flying.
How many would be glad to stand,
Whose bodies now are mute,
Or have no hand that they might raise
And stand in proud salute.
So accept it not as duty
But a privilege even more
And receive it as an honor
Instead of just a chore.

111L L11IIE li 11
American Forces Information Service, Department ot Defense
601 N. Fairfax Street, Room 312, Alexandria, VA 22314-2007

-V-

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="193">
      <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="194954">
                  <text>Defense Billboard Posters</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="196533">
                <text>Defense_Billboard_54</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196534">
                <text>"Somewhere...a bugle softly sounds. The message of renown, And some inside their buildings wait Until the flag comes down. And others run to get their cars Quite harrowed or dismayed, Afraid that they will not reach the gate Before retreat is played. Not thinking of the flag or those Who fought to keep it flying. How many would be glad to stand, Whose bodies now are mute, Or have no hand that they might raise And stand in proud salute. So accept it not as duty But a privilege even more And receive it as an honor Instead of just a chore. "</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="196535">
                <text>D2.9:So5/992</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196536">
                <text>Salute the graves of fallen soldiers and American flag</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196537">
                <text>Department of Defense</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="196538">
                <text>1992-06-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="196539">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196540">
                <text>Department of Defense poster</text>
              </elementText>
              <elementText elementTextId="196541">
                <text>United States--Department of Defense</text>
              </elementText>
              <elementText elementTextId="196542">
                <text>War cemeteries</text>
              </elementText>
              <elementText elementTextId="196543">
                <text>Soldiers</text>
              </elementText>
              <elementText elementTextId="196544">
                <text>Sun -- Rising and setting</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196545">
                <text>Posters</text>
              </elementText>
              <elementText elementTextId="196546">
                <text>Still Image</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="196547">
                <text>The University of Alabama in Huntsville M. Louis Salmon Library</text>
              </elementText>
              <elementText elementTextId="196548">
                <text>Defense Billboards Posters</text>
              </elementText>
              <elementText elementTextId="196549">
                <text>Case 1, Drawer 1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="196550">
                <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="196551">
                <text>This material may be protected&#13;
under U. S. Copyright Law (Title 17,&#13;
U.S. Code) which governs the&#13;
making of photocopies or&#13;
reproductions of copyrighted&#13;
materials. You may use the digitized&#13;
material for private study,&#13;
scholarship, or research. Though&#13;
the University of Alabama in&#13;
Huntsville Archives and Special&#13;
Collections has physical ownership&#13;
of the material in its collections, in&#13;
some cases we may not own the&#13;
copyright to the material. It is the&#13;
patron's obligation to determine&#13;
and satisfy copyright restrictions&#13;
when publishing or otherwise&#13;
distributing materials found in our&#13;
collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="196552">
                <text>Defense Billboards</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="13885" public="1" featured="0">
    <fileContainer>
      <file fileId="10403">
        <src>https://digitalprojects.uah.edu/files/original/193/13885/Defense_Billboard_90_001.pdf</src>
        <authentication>8f1c0342fc5a50aea80ad9fd54bb2a9d</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="197460">
                    <text>bws

lie

.cage 01;
0 vtvstd®

their

DU

s daO&gt;a-

•, cars
ggt^ ,1

4
1
W r£f»""lb** «*
rwilt^

&lt;

i w(vipd*

d

,nSC

Uoa "^ues,l", twit
.tU.nsC "° i.atU11 , „nlatcsalU
^
nt as **.
v ™

iv---' ;•/•••
S-'.is,-;.

;

1*411

BILLBOARD

American Forces Information Service, Department of Defense
601 N. Fairfax Street, Room 312, Alexandria. VA 22314-2007

�</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="193">
      <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="194954">
                  <text>Defense Billboard Posters</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="197205">
                <text>Defense_Billboard_90</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="197206">
                <text>"Somewhere...a bugle softly sounds. The message of renown, And some inside their buildings wait Until the flag comes down. And others run to get their cars Quite harrowed or dismayed, Afraid that they will not reach the gate Before retreat is played. Not thinking of the flag or those Who fought to keep it flying. How many would be glad to stand, Whose bodies now are mute, Or have no hand that they might raise And stand in proud salute. So accept it not as duty But a privilege even more And receive it as an honor Instead of just a chore. "</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="52">
            <name>Alternative Title</name>
            <description>An alternative name for the resource. The distinction between titles and alternative titles is application-specific.</description>
            <elementTextContainer>
              <elementText elementTextId="197207">
                <text>D2.9:D36/2/No.90</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="197208">
                <text>Military soldier saluting a half-mast flag in a graveyard</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="197209">
                <text>Department of Defense</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="197210">
                <text>1995-08-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="197211">
                <text>1990-1999</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="197212">
                <text>Department of Defense poster</text>
              </elementText>
              <elementText elementTextId="197213">
                <text>United States--Department of Defense</text>
              </elementText>
              <elementText elementTextId="197214">
                <text>Military cemeteries</text>
              </elementText>
              <elementText elementTextId="197215">
                <text>Soldiers</text>
              </elementText>
              <elementText elementTextId="197216">
                <text>United States -- Flags</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="197217">
                <text>Posters</text>
              </elementText>
              <elementText elementTextId="197218">
                <text>Still Image</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="197219">
                <text>The University of Alabama in Huntsville M. Louis Salmon Library</text>
              </elementText>
              <elementText elementTextId="197220">
                <text>Defense Billboards Posters</text>
              </elementText>
              <elementText elementTextId="197221">
                <text>Case 1, Drawer 1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="197222">
                <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="197223">
                <text>This material may be protected&#13;
under U. S. Copyright Law (Title 17,&#13;
U.S. Code) which governs the&#13;
making of photocopies or&#13;
reproductions of copyrighted&#13;
materials. You may use the digitized&#13;
material for private study,&#13;
scholarship, or research. Though&#13;
the University of Alabama in&#13;
Huntsville Archives and Special&#13;
Collections has physical ownership&#13;
of the material in its collections, in&#13;
some cases we may not own the&#13;
copyright to the material. It is the&#13;
patron's obligation to determine&#13;
and satisfy copyright restrictions&#13;
when publishing or otherwise&#13;
distributing materials found in our&#13;
collections.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="197224">
                <text>Defense Billboards</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2669" public="1" featured="0">
    <fileContainer>
      <file fileId="1970">
        <src>https://digitalprojects.uah.edu/files/original/57/2669/spc_mcca_000306-312.pdf</src>
        <authentication>814ca5f64b83766a376758ea68ce887a</authentication>
      </file>
    </fileContainer>
    <collection collectionId="57">
      <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="17166">
                  <text>Christel W. Ludewig McCanless Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="17167">
                  <text>Christel W. Ludewig McCanless Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="17168">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/17" target="_blank" rel="noreferrer noopener"&gt;View the Christel W. Ludewig McCanless 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="201618">
                  <text>Christel Ludewig McCanless was born in Germany in 1939. Her father, Hermann Ludewig, was one of the V-2 engineers at Peenemuende. Consequently, she grew up in Peenemuende until an air raid in 1943 destroyed their home. McCanless and her family moved to Trebbin, Germany, which became part of East Germany after World War II.&#13;
&#13;
In 1953, Ludewig accepted a job to work with Von Braun in Huntsville, Alabama and decided to flee East Germany with his family. McCanless continued school in the United States and graduated with a Bachelor of Arts in English from the University of Montevallo and then graduated with a Masters in Library Science from the University of North Carolina at Chapel Hill.&#13;
&#13;
She served as the first full-time, professional librarian at UAH. After serving as the Library Director at UAH, she worked in the Huntsville Times newspaper library, the Huntsville Museum of Art’s Art Reference Library, and the Huntsville Museum of Art’s Education Resource Center. In addition, she consulted for the Alabama Library Exchange and created workshops on technology and library science.&#13;
&#13;
McCanless is the author of "Fabergé and His Works: An Annotated Bibliography of the First Century of His Art" and a co-author of "Fabergé Eggs: A Retrospective."</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="52829">
                <text>spc_mcca_000306_000312</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52830">
                <text>"Sources of Biographical Information."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52831">
                <text>This document lists the building and section locations of particular book and non-book sources for biographical information on the UAH campus.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52832">
                <text>University of Alabama in Huntsville&#13;
</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="52833">
                <text>1968-03-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="52834">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="52835">
                <text>Academic libraries</text>
              </elementText>
              <elementText elementTextId="52836">
                <text>Information retrieval</text>
              </elementText>
              <elementText elementTextId="52837">
                <text>University of Alabama in Huntsville&#13;
</text>
              </elementText>
              <elementText elementTextId="52838">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="52839">
                <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="52840">
                <text>Documents</text>
              </elementText>
              <elementText elementTextId="52841">
                <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="52842">
                <text>Christel L. McCanless Collection</text>
              </elementText>
              <elementText elementTextId="52843">
                <text>Box 1, Folder 52</text>
              </elementText>
              <elementText elementTextId="206454">
                <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="52845">
                <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="52846">
                <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="52847">
                <text>spc_mcca_2020_11</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10378" public="1" featured="0">
    <fileContainer>
      <file fileId="9082">
        <src>https://digitalprojects.uah.edu/files/original/20/10378/SpacAgeManaMainTechCapaDurPeriRetr_062708142049.pdf</src>
        <authentication>e40fcf4191ce654ef3ef5dfd862afcaa</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="155585">
                <text>SpacAgeManaMainTechCapaDurPeriRetr_062708142049.pdf </text>
              </elementText>
              <elementText elementTextId="155586">
                <text>spc_stnv_000832</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155587">
                <text>"Space age management or maintenance of technical capability during a period of retrenchment."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155588">
                <text>On January 3Ist of this year the United States celebrated its tenth anniversary in Space.  In just one decade we have seen our space program climb from an humble beginning (a 30.8-pound payload put into orbit with a jury-rigged rocket) to extra-vehicular-activity and the tremendous Saturn V vehicle capable, of putting 250,000 pounds into low earth orbit. We have seen it grow from a "quick and dirty"  operation to a program which at its peak had approximately 380,000 industrial employees in excess of {dollar}5.O billion per year. The marshalling of this great management and technological team generated many "growing pains".  A few years ago the hue and cry was, "Where are we going to get sufficient people with scientific knowledge and drive to implement the space program?"  Industry, sometimes reluctantly, was pressed into tasks which required managerial and technical skills beyond those they then possessed.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155589">
                <text>Brown, William D.</text>
              </elementText>
              <elementText elementTextId="155590">
                <text>United States. National Aeronautics and Space Administration</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="155591">
                <text>1960-02-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155592">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155593">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155594">
                <text>Personnel management</text>
              </elementText>
              <elementText elementTextId="155595">
                <text>Downsizing of organizations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155596">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155597">
                <text>Memorandums</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="155598">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155599">
                <text>Box 25, Folder 27</text>
              </elementText>
              <elementText elementTextId="210188">
                <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="155601">
                <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="155602">
                <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="155603">
                <text>spc_stnv_000825_000849</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="155604">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17835</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10379" public="1" featured="0">
    <fileContainer>
      <file fileId="9081">
        <src>https://digitalprojects.uah.edu/files/original/20/10379/Spaceandtheworkingwoman_061908150158.pdf</src>
        <authentication>635fb5666e525168cb7f0b4c2a6281ec</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="155605">
                <text>Spaceandtheworkingwoman_061908150158.pdf</text>
              </elementText>
              <elementText elementTextId="155606">
                <text>spc_stnv_000834</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155607">
                <text>"Space and the working woman."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155608">
                <text>Memorandum prepared for the honoring Amelia Earhart by the Zonta Club, Birmingham, Alabama.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155609">
                <text>Wyss, G. L.</text>
              </elementText>
              <elementText elementTextId="155610">
                <text>United States. National Aeronautics and Space Administration</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="155611">
                <text>1969-01-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155612">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155613">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155614">
                <text>Women scientists</text>
              </elementText>
              <elementText elementTextId="155615">
                <text>Employment</text>
              </elementText>
              <elementText elementTextId="155616">
                <text>Discrimination</text>
              </elementText>
              <elementText elementTextId="155617">
                <text>Space race</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155618">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155619">
                <text>Memorandums</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="155620">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155621">
                <text>Box 25, Folder 18</text>
              </elementText>
              <elementText elementTextId="210189">
                <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="155623">
                <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="155624">
                <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="155625">
                <text>spc_stnv_000825_000849</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="155626">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17826</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9376" public="1" featured="0">
    <fileContainer>
      <file fileId="8166">
        <src>https://digitalprojects.uah.edu/files/original/132/9376/r10_03-01.pdf</src>
        <authentication>08535774261adb6311cd6c8655f7c618</authentication>
      </file>
    </fileContainer>
    <collection collectionId="132">
      <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="142296">
                  <text>Series 10: Books and Pamphlets</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="142297">
                  <text>Series 10: Books and Pamphlets</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="142505">
                <text>r10_03-01</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="142506">
                <text>Series 10, Box 3, Folder 1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="142507">
                <text>"Space Capitol of the Universe," Huntsville, 1959</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="142508">
                <text>r10-211020</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10387" public="1" featured="0">
    <fileContainer>
      <file fileId="9076">
        <src>https://digitalprojects.uah.edu/files/original/20/10387/Spadivnorameroccorporgcht_090408145031.pdf</src>
        <authentication>05d11e2b6f585f7e7789847b609cd941</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="155762">
                <text>Spadivnorameroccorporgcht_090408145031.pdf</text>
              </elementText>
              <elementText elementTextId="155763">
                <text>spc_stnv_000843</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155764">
                <text>"Space Division, North American Rockwell Corporation Organizational Chart."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155765">
                <text>Organization chart for North American Rockwell, 1968</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155766">
                <text>North American Rockwell Corporation. Space Division</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="155767">
                <text>1968-07-14</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155768">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155769">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155770">
                <text>Apollo project</text>
              </elementText>
              <elementText elementTextId="155771">
                <text>Organization charts</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155772">
                <text>Still Image</text>
              </elementText>
              <elementText elementTextId="155773">
                <text>Organization Charts</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="155774">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155775">
                <text>Box 27, Folder 10</text>
              </elementText>
              <elementText elementTextId="210197">
                <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="155777">
                <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="155778">
                <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="155779">
                <text>spc_stnv_000825_000849</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="155780">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17897</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10380" public="1" featured="0">
    <fileContainer>
      <file fileId="9200">
        <src>https://digitalprojects.uah.edu/files/original/20/10380/spaceflight_1_2.pdf</src>
        <authentication>e27bf4f9521da003a218e4b93b9208e3</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="155627">
                <text>spaceflight_1_071907122122&#13;
spaceflight_2_071907122730</text>
              </elementText>
              <elementText elementTextId="155628">
                <text>spc_stnv_000835</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155629">
                <text>"Space flight : first draft."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155630">
                <text>Appears to be a rough dfraft with editorial comments and revision notes. Includes references to figures and tables.;  Page 31 is missing.  Pages 37 through 44 do not exist; there is a note about this on page 36.  Page 67 also does not exist.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155631">
                <text>Josuke</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="155632">
                <text>1965-04-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155633">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155634">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155635">
                <text>Astronautics</text>
              </elementText>
              <elementText elementTextId="155636">
                <text>Space flight</text>
              </elementText>
              <elementText elementTextId="155637">
                <text>Space vehicles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155638">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155639">
                <text>Rough Drafts</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="155640">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155641">
                <text>Box 13, Folder 24</text>
              </elementText>
              <elementText elementTextId="210190">
                <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="155643">
                <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="155644">
                <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="155645">
                <text>spc_stnv_000825_000849</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="155646">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17116</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10381" public="1" featured="0">
    <fileContainer>
      <file fileId="9080">
        <src>https://digitalprojects.uah.edu/files/original/20/10381/spacfligprojtodaandtomo_032207104326.pdf</src>
        <authentication>0f7005f370171f92276f91cb6cadc700</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="155647">
                <text>spacfligprojtodaandtomo_032207104326.pdf</text>
              </elementText>
              <elementText elementTextId="155648">
                <text>spc_stnv_000836</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155649">
                <text>"Space flight projects - today and tomorrow."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155650">
                <text>NASA symposium on scientific and technical Information.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155651">
                <text>Stuhlinger, Ernst</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="155652">
                <text>1963-05-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155653">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155654">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155655">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="155656">
                <text>Saturn stages</text>
              </elementText>
              <elementText elementTextId="155657">
                <text>Manned space flight</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155658">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155659">
                <text>Symposiums</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="155660">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155661">
                <text>Box 8, Folder 32</text>
              </elementText>
              <elementText elementTextId="210191">
                <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="155663">
                <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="155664">
                <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="155665">
                <text>spc_stnv_000825_000849</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="155666">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17329</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10382" public="1" featured="0">
    <fileContainer>
      <file fileId="9079">
        <src>https://digitalprojects.uah.edu/files/original/20/10382/Spacspeaarena_120408110609.pdf</src>
        <authentication>282db3cffe6c16b2b7bf400a6e3cd29e</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="155667">
                <text>Spacspeaarena_120408110609.pdf</text>
              </elementText>
              <elementText elementTextId="155668">
                <text>spc_stnv_000837</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155669">
                <text>"Space sparks a renaissance in education."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155670">
                <text>An article which comments on the increasing interest in science and education due to the greater understanding of space.</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="155671">
                <text>1968-09-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155672">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155673">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155674">
                <text>United States. National Aeronautics and Space Administration</text>
              </elementText>
              <elementText elementTextId="155675">
                <text>Science--Study and teaching--United States</text>
              </elementText>
              <elementText elementTextId="155676">
                <text>Space sciences--Study and teaching--United States</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155677">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155678">
                <text>Articles</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="155679">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155680">
                <text>Box 27, Folder 49</text>
              </elementText>
              <elementText elementTextId="210192">
                <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="155682">
                <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="155683">
                <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="155684">
                <text>spc_stnv_000825_000849</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="155685">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17936</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="11096" public="1" featured="0">
    <fileContainer>
      <file fileId="9783">
        <src>https://digitalprojects.uah.edu/files/original/20/11096/Spacstatoper.pdf.pdf</src>
        <authentication>10040e5663a78544c573c2cdf0593019</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="169949">
                <text>Spacstatoper.pdf</text>
              </elementText>
              <elementText elementTextId="169950">
                <text>spc_stnv_000838</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169951">
                <text>"Space Station operations analysis using Gemini-Titan II-Agena."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169952">
                <text>Copy No. 026.  Ger-10866.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169953">
                <text>Smith, E. R.</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="169954">
                <text>1962-10-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="169955">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169956">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="169957">
                <text>Geminai project</text>
              </elementText>
              <elementText elementTextId="169958">
                <text>Space stations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="169959">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="169960">
                <text>Analyses</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="169961">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="169962">
                <text>Box 7, Folder 34</text>
              </elementText>
              <elementText elementTextId="210787">
                <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="169964">
                <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="169965">
                <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="169966">
                <text>spc_stnv_000825_000849</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="169967">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17266</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10385" public="1" featured="0">
    <fileContainer>
      <file fileId="9198">
        <src>https://digitalprojects.uah.edu/files/original/20/10385/spavehsysrtpprosubfy1968.pdf</src>
        <authentication>818d680731f6097629decb867d81b606</authentication>
      </file>
      <file fileId="9199">
        <src>https://digitalprojects.uah.edu/files/original/20/10385/spavehsysrtpprosubfy1968.1.pdf</src>
        <authentication>818d680731f6097629decb867d81b606</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="155727">
                <text>spavehsyssrtprosubfy1968sec1_032508133219&#13;
spavehsyssrtprosubfy1968sec2_032508133229&#13;
spavehsyssrtprosubfy1968sec3_032508133238&#13;
spavehsyssrtprosubfy1968sec4_032508133247&#13;
spavehsyssrtprosubfy1968sec5_032508133255&#13;
spavehsyssrtprosubfy1968sec6_032508133324&#13;
spavehsyssrtprosubfy1968sec7_032508133338</text>
              </elementText>
              <elementText elementTextId="155728">
                <text>spc_stnv_000841</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155729">
                <text>"Space vehicle systems" research and technology.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155730">
                <text>A collection of various graphs, resumes and recordings for space vehical systems.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155731">
                <text>George C. Marshall Space Flight Center. Research Program Office</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="155732">
                <text>1967-03-15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155733">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155734">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155735">
                <text>Space vehicles - Research</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155736">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155737">
                <text>Memorandums</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="155738">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="210195">
                <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="155740">
                <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="155741">
                <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="155742">
                <text>spc_stnv_000825_000849</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10386" public="1" featured="0">
    <fileContainer>
      <file fileId="9077">
        <src>https://digitalprojects.uah.edu/files/original/20/10386/spacvehiteststan_031907103454.pdf</src>
        <authentication>b57a07eaf39e772d64870d348910688b</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="155743">
                <text>spacvehiteststan_031907103454.pdf</text>
              </elementText>
              <elementText elementTextId="155744">
                <text>spc_stnv_000842</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155745">
                <text>"Space vehicle test stands."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155746">
                <text>One of the pacing items in this Nation's accelerated space program is the construction of facilities for the manufacture, development, testing, check-out, transportation and launching of space vehicles.  Behind each successful launching are countless hours of effort in development, quality and reliability checks and tests of engines, components, boosters, and stacked stages; including pressure tests, cold-flow tests and hot firing (or static) tests; all to assure the safest possible trip for the men or instrumentation in the space craft.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155747">
                <text>Ramsey, Robert D.</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="155748">
                <text>1962-11-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155749">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155750">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155751">
                <text>Rocket test facilities</text>
              </elementText>
              <elementText elementTextId="155752">
                <text>Test stands</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155753">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155754">
                <text>Memorandums</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="155755">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155756">
                <text>Box 7, Folder 38</text>
              </elementText>
              <elementText elementTextId="210196">
                <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="155758">
                <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="155759">
                <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="155760">
                <text>spc_stnv_000825_000849</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="155761">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17270</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10383" public="1" featured="0">
    <fileContainer>
      <file fileId="9202">
        <src>https://digitalprojects.uah.edu/files/original/20/10383/Spactelegroudata_022508152653.pdf</src>
        <authentication>7bd9ce50310f0f84d6d0ec6ba1dd8172</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="155686">
                <text>Spactelegroudata_022508152653.pdf</text>
              </elementText>
              <elementText elementTextId="155687">
                <text>spc_stnv_000839</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155688">
                <text>"Spacecraft television ground data handling system."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155689">
                <text>A design report which displays and explains how the Spacecraft Television Ground Handling System functions, is designed and what it might be used for in the future.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155690">
                <text>General Precision, Inc. Link Division</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="155691">
                <text>1967-01-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155692">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155693">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155694">
                <text>Astronautics</text>
              </elementText>
              <elementText elementTextId="155695">
                <text>Photo mapping</text>
              </elementText>
              <elementText elementTextId="155696">
                <text>Spacecraft</text>
              </elementText>
              <elementText elementTextId="155697">
                <text>Television transmission</text>
              </elementText>
              <elementText elementTextId="155698">
                <text>Data processing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155699">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155700">
                <text>Design 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="155701">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155702">
                <text>Box 20, Folder 9</text>
              </elementText>
              <elementText elementTextId="210193">
                <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="155704">
                <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="155705">
                <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="155706">
                <text>spc_stnv_000825_000849</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="155707">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/17592</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3319" public="1" featured="0">
    <fileContainer>
      <file fileId="2561">
        <src>https://digitalprojects.uah.edu/files/original/76/3319/loc_burw_-116.pdf</src>
        <authentication>6901f19ef1005a9473050f50ea37e6d9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="76">
      <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="28299">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="28300">
                  <text>Burwell Family Collection</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="46">
              <name>Relation</name>
              <description>A related resource</description>
              <elementTextContainer>
                <elementText elementTextId="133718">
                  <text>&lt;a href="http://libarchstor.uah.edu:8081/repositories/2/resources/145" target="_blank" rel="noreferrer noopener"&gt;View the Burwell Family 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="133721">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3332" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1943-1944&lt;/a&gt;</text>
                </elementText>
                <elementText elementTextId="133722">
                  <text>&lt;a href="http://libarchstor2.uah.edu/digitalcollections/items/show/3333" target="_blank" rel="noreferrer noopener"&gt;View Edwin D. Burwell's World War II service timeline, 1944-1945&lt;/a&gt;</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="133723">
                  <text>Materials donated and digitized by Dudley Burwell</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="65262">
                <text>loc_burw_000116</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65263">
                <text>"Special Orders-Number 3" providing officer appointments to the Alabama National Guard.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65264">
                <text>These orders note that Edwin D. Burwell has been assogned as a Major in the 1169th Engineer Combat Battalion in the Alabama National Guard and direct him to appear before the Examining Board.</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="65265">
                <text>1/4/1947</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="65266">
                <text>1940-1949</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65267">
                <text>Alabama. Army National Guard</text>
              </elementText>
              <elementText elementTextId="65268">
                <text>Burwell, Edwin D., Jr.</text>
              </elementText>
              <elementText elementTextId="65269">
                <text>United States. Army. Engineer Combat Group, 1169th</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="65270">
                <text>Orders (military records)</text>
              </elementText>
              <elementText elementTextId="65271">
                <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="65272">
                <text>Burwell Family Collection</text>
              </elementText>
              <elementText elementTextId="206675">
                <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="65274">
                <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="65275">
                <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="65276">
                <text>loc_burw_2021_02</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14389" public="1" featured="0">
    <fileContainer>
      <file fileId="10938">
        <src>https://digitalprojects.uah.edu/files/original/199/14389/sdsp_skyl_000054_001.pdf</src>
        <authentication>5f07de4bb64d242d23ff811adfe84526</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="215892">
                    <text>SPACE

GEORGE C. MARSHALL FLIGHT
CENTER

HUNTSVILLE, ALABAMA

SPENT STAGE EXPERIMENT
SUPPORT MODULE PROPOSAL
JUNE 1966

FOR NASA INTERNAL USE ONLY
National Aeronautics and Space Administration

Form 454 (Revised September 1961)

��FOREWORD

This proposal is submitted to assure NASA management that MSFC
possesses the technical and managerial capability to design, manufacture,
and test the Spent Stage Experiment Support Module (SSESM) on a timely
basis and within the framework of an austere program.

��TABLE OF CONTENTS
Section
I.

II.

III.

IV.

V.

VI.

Page
Introduction

1-1

1.1 Background and Philosophy
1.2 Scope

1-1
1-1

Program Summary

2-1

2.1
2.2
2.3
2.4

2-1
2-1
2-2
2-4

General
Mission Description
Spent Stage Experiment Configuration
Spent Stage Experiment Support Module (SSESM)

Mission Description

3-1

3.1
3.2
3.3
3.4

3-1
3-5
3-7
3-9

Mission Profile
Performance Capability and Lifetime Analysis
Dynamic Analysis
Mission Sequence and Analysis

Technical Description

4-1

4.1
4.2
4.3
4.4
4.5
4.6

4-1
4-24
4-30
4-55
4-68
4-78

Design Description
Structure
Environmental Control System (ECS)
Electrical Systems
Instrumentation and Communication System
Ground Support Equipment

Manufacturing and Quality &amp; Reliability Assurance Plan--5-1
5.1 Manufacturing Plan
5.2 Quality &amp; Reliability Assurance Plan

5-1
5-14

Resources and Schedules

6-1

6.1 Resource Requirements
6.2 Schedule

6-1
6-7
ii

��SECTION I. INTRODUCTION

1.1

BACKGROUND AND PHILOSOPHY

Flight performance analysis of AAP near-Earth orbiting missions indicates
that the S-IVB stage, firing in combination with the CSM to final orbit, can provide
near optimum payload characteristics for a wide range of orbits. Since the
spent S-IVB stage and the spacecraft would then be in proximity, the large
volume of the LH2 tank could be available for use as an enclosed workshop.
A docking structure and airlock are needed on the spent stage for providing
docking to the CM and access for astronauts into the large LH? tank.
The intent of this document is to propose a combined docking and airlock
structure called (Spent Stage Experiment Support Module) (SSESM) which would be
designed, manufactured, and tested in-house at MSFC. The approach covered in
this proposal is applicable to experimental missions for evaluation of the orbital
workshop beginning with flight AS-209, and to subsequent missions with operational
workshops.
The facilities and engineering capabilities to accomplish this task are
presently available at MSFC. In addition, this Center has complete knowledge
and configuration control of the S-IVB stage and S-IVB Workshop. Accordingly,
it is the intent of this proposal to delineate the management and close control
of all production elements necessary to: (1) Meet the early launch dates; (2) provide
fast reaction to program changes; and (3) restrict costs to present budget limitations.
1.2

SCOPE

This document proposes that MSFC design, build, and test the SSESM, which
is a combined docking structure and airlock suitable for mating the CM to the spent
S-IVB stage, thus, providing astronauts access to both the pressurized empty LH2
tank and to the unpressurized exterior of the vehicle. The SSESM will occupy the
space normally provided for the LEM and will attach to the descent stage attachment
points. Volume allocation will be provided for mounting experiments on the
exterior of this module. Where possible, equipment already designed for the
Saturn/Apollo or Gemini subsystems will be used for subsystems of this
module, such as environmental control, electrical power, instrumentation,
and communications. All structural manufacture and equipment adaptation
will be accomplished within MSFC Laboratories.

1-1

��SECTION II. PROGRAM SUMMARY
" 2.1

GENERAL

The S-IVB Spent Stage Experiment involves the establishment in Earth
orbit of the spent S-IVB stage with a Spent Stage Support Module (SSESM) docked to
the CSM for manned orbital missions. This system provides large volumes
for 14 to 30 days on initial flights. Rendezvous and resupply techniques may
be utilized on initial or subsequent flights to extend mission lifetime.
The spent S-IVB stage is utilized as a habitable workshop by including
as a major element of the experiment a SSESM. The SSESM is basically a
structural unit which includes an airlock, provides the dynamic and static
structural interface between the CSM and spent stage, and provides attachmai t
provisions for the desired supporting equipment and corollary experiments. It
provides the passageway from the CSM to the S-IVB workshop and to the hatch
for EVA. In this context, the SSESM will provide for either an unpressurized
or pressurized workshop flight as required by mission assignments. Instru­
mentation and electrical power are provided integral to the SSESM as required
to support the different degrees of sophistication desired in the assigned
operational missions and corollary experiments. Capability for pressurizing
the LH2 tank can be provided for pressurized flights or combination flights
(unpressurized X days, pressurized Y days) by including pressurization com­
ponents as an experiment on the SSESM or as an operational subsystem on the
SSESM.
The SSESM is designed within the framework of the mission and overall
workshop design discussed in the subsequent paragraphs. A summary of the
basic SSESM design is also discussed in a subsequent paragraph; a detailed
technical description is presented in Section IV. Alternate designs and system
flexibility are discussed in Section VIII, but the primary system proposed for
the AS-209 mission is the system discussed as the basic SSESM design. MSFC
has completed, as evidenced by the schedules and technical backup material,
that portion of the final SSESM design necessary at this time to provide system
readiness for flight AS-209. Efforts are continuing to maintain the requirements
of this flight schedule.
2 .2

MISSION DESCRIPTION

The Spent Stage Experiment mission considered for this program is a
20-day mission, 14 to 20 days depending on CSM lifetime, launched in early
1968 on flight vehicle AS-209. Longer duration flights are discussed as
alternates. The S-IVB is burned for direct injection into an elliptical orbit,
the CSM then transposes and docks with the SSESM, and the CSM is then ignited
to circularize in a low inclination, 170 nautical mile Earth orbit. After
establishment of 170 nautical mile orbit, the crew completes procedures to
passivate the S-IVB stage and to activate the Workshop.
2-1

�2.3

SPENT STAGE EXPERIMENT CONFIGURATION

The composite operational configuration in Earth orbit consists of the
spent S-IVB stage, the IU, the SLA, and the SSESM which is docked to the
Apollo Command/Service Module (refer to Figure 2.3-1). The SSESM is
attached to the S-IVB forward interstage at tte four LEM descent stage attach
points and the SSESM airlock is attached to the upper LH 2 dome by a flexible
bellows connection.
The S-IVB stage is passivated (made safe for occupancy) by disarming
the command destruct receiver and venting the LH 9 tank, L0 2 tank, cold
helium supply gases, engine pneumatic supply, engine start bottle, APS
helium supply, and stage pneumatic supply gas. The S-IVB/Workshop is acti­
vated by deployment of the SLA panels, removal of the LF^ tank hatch and
connection of the SSESM airlock to the LH 2 tank, performing an SSESM
subsystems monitor check, subsystem activation, equipment deployment
as necessary, and pressurization of the LH 2 tank. The pressurization of
the LH 2 tank may be delayed for the time period desired for performing
experiments in an unpressurized container. Prior to pressurization the
LH2 tank interior is fitted with lights, blowers, and crew-assist ropes
which will be stored on the SSESM. For the basic design, no major interface
has been established with the CSM other than docking interface. This assembled
operational configuration will allow one or two crew members to function in
the SSESM airlock, the S-IVB tank, or outside the SSESM airlock, depending
on the detailed scheduling of mission and experiment operations. Varying
periods of allowable occupancy will be provided in each area which is
discussed later in more detail. For passive thermal control, the assembled
workship is rotated at approximately six revolutions per hour oriented at
an attitude rminally broadside to the Sun or aligned with the velocity vector
during periods of LH 2 tank occupancy. The workshop could assume a random
attitude at other times.

2-2

��2.4

SPENT STAGE EXPERIMENT SUPPORT MODULE (SSESM)

The basic SSESM design being proposed is a straightforward design
with an inherent 20-day capability. The module design provides electrical
power, instrumentation, telemetry, environmental control, and experiment
support with a composite weight of approximately 9, 200 pounds. The avail­
able weight for experiments is approximately 950 pounds.
O
The configuration (refer to Figure 2.4-1) contains a 200 ft cylindrical
airlock, 65 inches in diameter, and 15 feet long which will accommodate two
crew members, required instrumentation, and storage for selected equipment.
The system provides a 32-inch diameter upper ingress/egress hatch to the
CSM. a 48-inch diameter lower ingress/egress hatch to the LH2 tank, and a
side located 36 by 55-inch rectangular sliding hatch for extra vehicular ingress/
egress. These hatch sizes, designs, and locations readily allow the transfer
of men, equipment and experiments.
The SSESM, basically of aluminum construction, has structural truss
members attaching the airlock to the S-IVB forward skirt at the four LEM
attach points. The airlock is a skin/frame of welded construction with external
ring frames and longerons for equipment attachment. A double skin meteoroid
bumper provides a large protected equipment compartment around the lower
half of the airlock exterior for selected experiments and electronics. These
items are mounted to the airlock stifle v ,ers and the truss support structure.
The upper end of the airlock accommodates a LEM docking adapter for mating with
the CSM and the lower end has an expandable non-metallic bellows which is
provided for in orbit attachment to the upper LH 2 tank dome.
The electrical power system, utilizing 21 silver zinc batteries, provides
approximately 300 KW hours of electrical power to the SSESM for housekeeping
and experiments. The power profile can be varied substantially to accommodate
periods of low and high load requirements. The batteries are mounted to hard
points around the upper portion of the airlock. A power control panel is provided
on the airlock and a portable display panel is provided for use in the LH2 tank.
The instrumentation provides the capability of monitoring all required
subsystem components and limited subsystem controls. Sufficient instrumenta­
tion is providedtomonitor several experiments. A telemetry system using
available hardware is provided for direct transmittal of data to ground via the
IU antenna.
2-4

��The environmental control system (ECS) has been designed with
emphasis on simplicity and reliability. The system utilizes components which
are largely available from existing manned space flight programs to provide
pressurization capability for the LH2 tank and airlock to 5 p.s.i.a. with 100
percent oxygen, and to provide PLSS recharge capability for extra vehicular
activity. Four 20-ft spheres are used for the ECS oxygen and one 3-ft3
sphere for the PLSS oxygen. Four blowers are distributed within the LH2
tank to circulate the oxygen for crew comfort. The system utilizes a
30-pound-per-day leakage, made up by pure oxygen, in combination with
scheduled occupancy to maintain the C02 content at a safe and acceptable
level. The occupancy time available allows, as an average, two men to
remain in the tank four hours out of every thirteen hours (four in and nine
out) for a 20-day period. Adjustments in scheduling allow one man or two
men in for longer or shorter time intervals. Thermal control, with the
exception of heating the oxygen as supplied, is handled by passive means
to maintain a 65±25°F temperature within the LH2 tank.
The system described above can be provided for an early 1968 launch
on AS-209 at minimum cost. The proposal includes three manufactured articles:
one flight article, one prototype test and training article, and one mockup
suitable for crew training and zero "g" flight training. The master schedule
summary is included as Figure 2.4-2. A resource requirement summary is
presented in Table 2.4-1. All manpower requirements would be available
within the current allotments.
In summary, the basic design proposed by MSFC provides a simple,
minimum interface, low cost design available for flight on AS-209 with
sufficient manufactured articles to complete the test, integration, training
and flight requirements. Adaptations of the design for more stringent mission
rtquirements can be accommodated by several methods without loss of any
developed major item, i.e., the items requiring development for the proposed
design would be utilized on design adaptations. The detailed aspects of this
design are described in the following sections, and additional backup information
is provided in the Appendix.

2-6

�2-7

�CO
_!
&lt;
H
O
H

EG

Crf O

u
u
H-J
&gt;
erf
W
CO

rf

%

CO
r—4

9

2-8

3,275

r129.4

as

T O T A L S

1
1

253.3

CM

CNJ
CVJ
—4

16.6

m

MOCK-UP
m

MISSION PLANNING

H

H

INTEGRATION OF EXPERIMENTS

o

919

3

r^«—•

FLIGHT ARTICLE

2
H

795

a

9.9

si &lt;/&gt;

TEST &amp; TRNG ARTICLE

CO
orf
&lt;
W
&gt;H

123

•—'

16.2

84.4

SUPPORT CONTR;
MAN YEARS

CO
Q
co z :
&lt; CO
W 3

vzi

I T E M

1

�SECTION III. MISSION DESCRIPTION
3.1

MISSION PROFILE

The mission profile for the Spent Stage Experiment as discussed in
this section is divided into three segments, ascent, orbiting profile and
return or reentry. These paragraphs describe the overall mission character­
istics and design conditions which influence the design requirements of the
Spent Stage Experiment Support Module (SSESM) as a part of the composite
configuration.
3.1.1

Ascent Profile

Tentative planning for the ascent profile for the Spent Stage
Experiment is a direct injection utilizing the Saturn IB launch vehicle into
an elliptical orbit. Preliminary parameters are: perigee 81 nautical miles,
and apogee 170 nautical miles. Firm orbital parameters will be established
after final system weights and the orbiting configuration are defined. This
is discussed further in subsequent paragraphs. After elliptical orbital
injection is confirmed, the CSM is transposed and docked to the SSESM.
The complete system, CSM/SSESM/S-IVB, will then be rotated 180 degrees
and the CSM propulsion system fired at apogee to circularize the orbit at
170 nautical miles. During the period between elliptical orbital injection
and the circularization maneuver, the lox and LH2 tanks will be venting
residual fuels. For the nominal guidance philosophy utilizing velocity
cutoff, fuel residuals and reserves range from 500 to 3000 pounds. These
residuals must be vented from the S-IVB stage.
3.1.2

Orbiting Profile

After the circularization maneuver and completion of the
venting of residuals and reserves, the orbiting space vehicle will assume
a controlled attitude nominally broadside to the sun throughout that portion
of the mission when the LH2 tank is manned, except for specific events
requiring a specified attitude such as: data transmission, status checks,
communications, and corollary experiments. Figures 3.1-1A, 3.1-1B, and
3.1-1C present a typical example of the geometric timeline for this mission.
3.1.3

Reentry Profile

After completion of the mission, the CSM will undock from the
SSESM/S-IVB and reenter. The SSESM/S-IVB will be left in orbit unstabilized
for possible revisits by later missions. The reentry profile is expected to be
similar to previous Apollo-Saturn IB missions with minor adjustments made for
the increased orbital altitude.
3-1

����3.1.4

Emergency Abort

The SSESM and associated systems of the Spent Stage Experiment
will be designed to facilitate emergency abort during any portion of the mission
profile. Existing equipment and associated abort sensing devices presently
utilized for the CSM will be employed for emergency abort for the mission.
3.2

PERFORMANCE CAPABILITY AND LIFETIME ANALYSIS
3.2.1 Performance

As discussed earlier, the selected mode for achieving the
acceptable payload capability is via injection in elliptical orbit and circular­
izing at apogee with the CSM/SPS. As stated the payload capability is defined
to be the gross injected weight above the IU less the fuel residuals and
reserves and the pressurants to be vented and dumped during stage passi­
vation. Shown on Figure 3.2-1 is a typical example of payload capability
(weight above the IU) as influenced by increasing apogee of the "parking"
orbit. It is necessary to maintain perigee at a minimum value of 80
nautical miles due to tracking constraints and to ascertain that the orbit
will not decay unsatisfactorily prior to circularization which may be
accomplished only after several revolutions.
3.2.2 Lifetime in Orbit
A major factor influencing the payload capability is the lifetime
requirements. Selection of the 170 nautical mile circular orbit as the
altitude required to yield a 20-day mission lifetime is established by the
following criteria: (a) the system is assumed to tumble randomly;
(b) mission occurs during a period of maximum solar activity; (c) the
SLA panels are extended in the nominal 45° position; (d) the influence of
20 variations on principle lifetime parameters are included. The effect
of vehicle orientation during periods of ground communication and data
transmission when the space vehicle is aligned with the velocity vector
will tend to increase the sensible lifetime over that specified for the
tumbling condition. Since the SLA panels may either be ejected or folded,
a change in the effective lifetime will be realized. If the panels are folded
to a position that reduces the configuration profile, thus, reducing drag,
the lifetime will be increased. If the panels are ejected, the lifetime will
be reduced due to the decrease in weight of the orbiting configuration.
Figure 3.2-2 illustrates the variation of orbital lifetime with altitude and
the influence on achievable payload.
3-5

�INJECTED PURGED GROSS PAYLOAD (LBS)
ABOVE THE I.U.
SPS APOGEE PROPELLANT IS THE PROPELLANT
REQUIRED TO CIRCULARIZE THE MASS OF THE
S-IVB, I.U., AND CSM.

40,000 *1

39,000 "

150 KM (81NM) PERIGEE INJECTION
ELLIPTIC ORBITS

SPS APOGEE
PROPELLANT

CIRCULAR ORBITS
VIA ELLIPTIC INJECTION

38,000 "

DIRECT INJECTION
CIRCULAR ORBITS

37,000

ALTITUDE (N.M.)
FIGURE 3.2-1. SPENT STAGE EXPERIMENT GROSS PAYLOAD AS A FUNCTION OF ALTITUDE
3-6

�3.3

DYNAMIC ANALYSIS

During the ascent phase of the mission profile, the SSESM will
experience dynamic responses, both longitudinal and lateral that will
induce acceleration loads normally encountered by the LEM. With the
maximum wind speeds, shears, and gusts occurring during the S-IB stage
thrusting phase of flight, maximum lateral accelerations are expected to
occur during the flight times where angle of attack and dynamic pressure
are maximum. Maximum longitudinal acceleration normally occur just
prior to first stage cutoff. The SSESM will be designed to withstand these
induced loading conditions as described above.
Preliminary indications are that dynamic response and acceleration
loads will be essentially those prescribed for previous Apollo - Saturn
launch vehicles (ex: AS-207) having similar ascent profiles. During
the transposition and docking maneuver, the S-IVB stage auxiliary
propulsion system will be required to maintain attitude stabilization
of the spent S-IVB stage and SSESM while the CSM is rotating and docking
with the forward end of the SSESM. This requirement dictates that this
maneuver must be completed prior to depletion of the stage electrical power
and instrument unit. To minimize disturbances during the transposition
and docking maneuver, the S-IVB lox and LH2 tank venting will have to
be interrupted. Nominal transposition and docking times for CSM/LEM
docking are essentially 30 minutes. It is expected that similar docking
times and communication requirements will also be imposed on the operation.
After the transposition and docking maneuver is completed, the CSM/
RCS is responsible for maintaining attitude control for the complete system
as required. Although the S-IVB stage is to be passivated soon after the
final circularization maneuver, it appears advantageous to utilize the
S-IVB APS to assist in attitude control prior to the passivation process,
thus, potentially increasing the useful lifetime of the CSM attitude control
system. The final circularization maneuver which utilizes the CSM pro­
pulsion system will impose dynamic loading conditions on the SSESM
since the entire system will be accelerated and controlled by the CSM.
After the circularization is completed, attitude control will also induce
bending and shear loads through the SSESM.
Analysis is now being accomplished to assess the structural stiffness
requirements of the SSESM for the loading conditions that will be experienced
during the Spent Stage Experiment. Preliminary analysis indicates that the
present SSESM structural design affords sufficient stiffness to allow controlling
the system.
3-7

�ALTITUDE (N.M.)
FIGURE 3.2-2. LIFETIME AND PURGED WEIGHT VS. ALTITUDE FOR THE DOCKED
CONFIGURATION, TUMBLING, FOR DEC. 1, 1968
3-8

�t

3.4

MISSION SEQUENCE AND ANALYSIS

The Spent Stage Experiment has as its primary mission the passivation
and activation of the spent S-IVB stage making it suitable for habitation. The
secondary mission of the Spent Stage Experiment is the performing of
corollary experiments either within the LH2 tank or EVA; the experiments
are essentially self contained and independent of the S-IVB stage and SSESM.
A preliminary functional analysis of the early mission functions is included
in Figure 3.4-1. This diagram includes events and functions from pre-launch
to pressurization of the LH2 tank as a workshop.
A preliminary time line analysis and considerable detail on specific
mission events and their sequence are included in the Appendix. The event
sequence is for the initial and terminal portions of the mission.

3-9

��SECTION IV.
4.1

TECHNICAL DESCRIPTION

DESIGN DESCRIPTION
4.1.1

Introduction

This section provides an overall systems description of the
Spent Stage Experiment Support Module (SSESM) system proposed to be
designed, manufactured, and tested by MSFC. Pertinent design guide­
lines are summarized, system characteristics and the integrated configu­
ration are described, weight summaries are presented, and major systems
interfaces are defined. Brief descriptions are also presented on the nonflight articles, the composite documentation, and the test philosophy.
Subsystem descriptions are presented in substantial detail in the subsequent
sections and the Appendix (under separate cover) contains additional data
on many items, including design ground rules, SSESM handling sequence,
crew familiarization requirements, maintenance concept, mission sequencing,
and subsystem data. Alternate designs and system flexibility are discussed
in Section VIII of this document.
4.1.2

SSESM Design Ground Rules

The detailed design ground rules used in the definition of the
MSFC proposal for a minimum cost 20-day mission duration Spent Stage
Experiment Support Module are contained in the Appendix (under separate
cover).
The design ground rules are based upon a mission objective of
providing, on flight AS-209, a pressurized S-IVB stage LH~ tank in which
astronauts can operate in a shirt-sleeve environment for 20 days.
The following design objectives and design approach considerations
were made which are reflected by the design ground rules contained in the
Appendix:
1. Maximum design simplicity.
2. Minimum program cost.
3. Passivation and activation of the S-IVB stage LH2 tank into
habitable shirt-sleeve environment volume is the primary experiment of
the mission.
4-1

�4. No major interfaces with the CSM
5. Minimum modifications to Saturn/Apollo hardware.
6. Retain AS-209 capability for Apollo backup.
7 . Maximum utilization of existing, and available Saturn/
Apollo subsystem components.
8. SSESM design to provide inherent flexibility and growth
potential for extended mission durations in a follow-on program, without
major modification to the basic systems design.
4.1.3

Description

General - The SSESM is defined as an independent airlock unit
which interconnects the CSM and the S-IVB LH2 tank and is mounted at the
attach points in the LEM adapter. The SSESM will include an airlock,
docking structure, environmental control system, electrical power system,
instrumentation and communication system, and support equipment as defined
below It wili also include the support structure for these systems, expendables,
and experiment stowage. The airlock will have the capability for independent
and integrated operation with the CSM and S-IVB Workshop. A schematic of
the SSESM system is given in Figure 4.1-1 outlining all major elements and
systems of this module.
Airlock - The airlock is used as a connecting link between the
CM, the LH2 tank, and the extra vehicular area. It provides a meteoroid
protected, environment controlled area for the crew, controls, and selected
equipments. The system is 65 inches in diameter and approximately 200
inches in length containing a 32-inch-diameter hatch at top, a 48-inch-diameter
|v'tch at bottom, and a 36-by-55-inch rectangular side hatch. These hatch sizes
and locations are designed to permit the crew with equipment to readily move
between zones of the Workshop. The airlock, 200 cubic feet, is sized to be
capable of accommodating two suited astronauts allowing for suit donning
and doffing. Provision is made for a pressure-tight connection to the LH2
tank '.orward dome mounting surface after which removal of the dome cover
provides a pressure environment for passage from the airlock to the tank.
Structure - The SSESM structure consists of the airlock cylinder,
the lower flexible boot, the support structure, the forward meteoroid protection,
the pressure spheres support structure, and the electrical batteries support
4-2

��structure. Essentially all material is aluminum and safety factors applied
are 1.4 against ultimate and 1.1 against yield. The airlock cylinder is milled
plate, all welded construction. Longerons and ringframe stiffeners are
attached on the exterior of the cylinder. The flexible boot is a non-metallic
material bolted to the LH 9 dome in orbit. The support structure is a
structural truss arrangement attaching the airlock to the four LEM attach
points. The forward meteroid protection consists of flat plates of aluminum
-'heels separated by honeycomb, closing off the area around the lower half
of me airlock between the airlock and SLA panels. A door is provided in this
shield close to the side airlock hatch, to allow EVA. The spheres are supported
by a secondary truss mounting to the lower half of the airlock. Batteries are
upported by shelves mounted to the longerons on the forward airlock section.
Attachment provisions for equipments are made at a substantial number of
points inside the airlock by tapping into local sections of the airlock skin
which is designed heavy for this purpose.
Environmental Control System - The ECS is designed to accomplish
atmosphere supply and control for the airlock, suit loops, and LH« tank. In
addition, PLSS oxygen recharge capability is provided in the airlock. Electrical
equipment mounted within the SSESM and IU are to be maintained within
operating temperature limits by passive means, thereby, eliminating active
coolant loops.
The atmosphere (oxygen) is supplied to the Lab (LH 2 tank) and
airlock from four 19.5 ft.3 high pressure gaseous storage spheres. Initial
pressurization of 3. 000 p.s.i.a. is permitted with final pressure at mission
completion of 50 p.s.i.a. planned. A 3 ft. 3 sphere isolated from the 19.5 ft.3
•spheres is used to accomplish PLSS oxygen recharge. Approximately 60 manhours
of EVA is provided. The oxygen supply to the airlock, suit loop umbilicals
and Lab for leakage replinishing is heated as required by individually thermotatically controlled heaters. The initial Lab charge is to be warmed in
^oroximately one orbit by radiant solar heating. Thermal control of the
Lab atmosphere can be kept within the 65±25°F limits by passive techniques;
reduced temperature variations can probably be achieved but this requires
further study of expected retro motor contamination of external paint characteris ics. The C0 9 contaminent limit is to be observed by scheduling leakage,
thereby oxygen make-up, in accordance to astronaut occupancy time and mission
duration. Water vapor content is kept within limits (R.H. of 30 to 70%) by a
combination of leakage/replinishments and adsorbers. The occupancy time can
be varied; however, the described design permits two astronauts to remain in
the Lab approximately 8 hours per day.
4-4

�Adjustable fans are provided in the Lab to afford crew comfort
and atmosphere mixing. The ECS controls and displays will be located
within the airlock. Two umbilicals are provided in the airlock for "closed
face plate" suit operation during ingress/egress cycles. This suited mode
of operation is required due to the inability of the PLSS sublimator to operate
in a pressure (above H20 triple point) environment.
Electrical System - The electrical system includes the electrical
power source, control panels and circuitry, distribution networks, and lighting.
The power source consists of twenty-one, 28 volt, silver zinc batteries
rated at 500 ampere hours (14 Kw-hr) each. Twenty batteries are arranged
in banks of ten batteries each and one battery is on a separate emergency
circuit. The system will deliver a total of approximately 300 kilowatt
hours and the present power profile defines a requirement of approximately
200 kilowatt hours. A control panel which provides switches, circuit
breakers, relays, meters, lights, and a distribution system is mounted in
the airlock. Displays include warning lights, ammeters, a voltmeter, a
pressure indicating meter and a temperature meter. Power distribution
is accomplished by circuit breakers on the control panel. A portable display
unit is provided to carry into the LH2 tank. The entire electrical system is
designed for manual control.
Instrumentation and Communication System - This system
provides equipment to acquire and present and relay system and experiment
data to the crew and to ground. The system is comprised of flight qualified
Saturn components including an FM/FM Telemeter, and RF Assembly, a TM
Multiplexer, a Measuring Rack, Telemeter Calibrator, and displays. The
antenna is utilized for telemetry to ground. Fifty-five signal conditioning
slots are available. One hundred seventy telemetry channels at 12 SPS and
four at 120 SPS are available. Fifteen FM/FM continuous channels are
available. Voice communication is provided by a Gemini voice system for
the SSESM, SSESM to CSM, and SSESM to LH2 tank. Voice transmission
to ground is via the CSM.
Experiment Provisions - Specific experiments are not defined for
integration into this design; however, to provide flexibility for accommodating
varied experiments many provisions have been made. Substantial space
exists in and around the airlock system for mounting experiment packages
which is reflected in the subsequent drawings. Structural provisions are
made for mounting on the airlock interior walls, the exterior longerons and
rings, and the exterior support structure. Approximately 950 pounds of
payload is available for carrying experiments and 75 to 100 kilowatt hours
4-5

�of electrical power are currently available. Monitoring instrumentation and
data telemetry capability are also provided for a significant amount of
experimentation.
Crew Equipment and GFAE - Tools and equipment will be
furnished as determined by specific task analysis. Typical items are hand­
holds, racks, reactionless wrenches, lights, and tethers. During launch
operations this equipment will be stowed in equipment storage assembly
boxes. Three portable life support systems will be furnished, one will be
stowed in the CM and two in the SSESM airlock. The PLSS is a portable
back pack life support system used in conjunction with a space suit,
i isically,
it is a closed-loop gas/liquid environmental control system
designed to maintain temperature and breathing oxygen to tolerable limits.
Three extra pressure suits will be furnished to insure astronaut safety
and comfort. GFAE of the following types will be used and stored on the
SSESM:
1. Extravehicular activity hardware.
2. Camera equipment.
3. Others as required by mission.
4.1.4

Conf iguration

Configuration drawings are included as Figures 4.1-2 through
4.1-6 presenting detailed information on the SSESM, the SSESM launch arrange­
ment, operational arrangement, overall layout and equipment placement,
structure, and docking provisions. A digest of the five drawings, all titled
Spent Stage Experiment Support Module (20-day mission) Inboard Profile
and numbered sheet 1 through 5 of SK10-7284, is given below.
Figure 4.1-2 - This drawing defines the launch configuration of
the SSESM and CSM with the bellows detached from the bulkhead, typical
experiments attached, major external equipments, and other details.
Figure 4.1-3 - This drawing defines the SSESM in its orbital
operational position and defines the arrangement of external equipment
including batteries, gox spheres, etc.
of
Of

QCRCU
• iF,r? 4'1~4A and 4-1-4B " These drawings define the interior
SSESM airlock, the location of interior and exterior equipments such as

IU cold plates.

3nd

^

POSiti°n

°f

4-6

the SSESM

instrumentation on the

�Figures 4.1-5A and 4.1-5B - These drawings define the internal
configuration and characteristics of the S-IVB LH9 tank.
Figures 4.1-6A and 4.1-6B - These drawings define the SSESM
docking adapter provisions and the mated configuration of the CM/SSESM
docking tunnel,
4.1.5

Weight Summaries

The overall payload, items above the IU, weight summary is
presented in Table 4.1-1 reflecting a weight available for the SSESM and
associated equipment and experiments of 10,132 pounds. Table 4.1-2 provides
a weight summary of the SSESM reflecting a total weight of 9,190 pounds.
Table 4.1-3 presents a detailed weight breakdown for the SSESM including
all subsystems and supporting equipment.
4.1.6

Non-Flight Articles

In addition to the flight article (5) proposed herein, MSFC will
furnish two additional hardware articles. A prototype (test and training
article) and a mockup (zero "g" test article) will be provided. The character­
istics of these articles are defined below.
Prototype (test and training article) - This system will be a
prototype unit of the flight article which has been described in detail in
the above sections. The system will be utilized for structural system
tests, high altitude mission simulation tests and detailed crew familiarization.
Selected dummy components will be utilized during the structural tests and
the unit will later be completely equipped with prototype components.
Mockup (zero "g" test article) - This system will be a mockup
of the SSESM sophisticated to the degree required to: be suitable for aircraft
flight; simulate internal configuration of flight article; interconnect with the
CSM; provide hatches, docking assembly and other mechanisms representative
of SSESM torques, forces and configurations; have operating connections for
permit crew training in pressure suits; and mock-up portions of the instrument
panels not required to be operational.

4-7

���������V

TABLE 4.1-1
SPENT STAGE EXPERIMENT WEIGHT SUMMARY
Item

Weight (lbs.)

Payload Capability * (Approximate)

37, 250

Command Module/Service Module 8*
De-orbit Propellant
Spacecraft LEM Adapter
S-IVB Modifications (Table II)
Spent Stage Experiment Support Module
(Table III)

-21,860
- l? 020
- 3, 755
- 483
- 9,190

Weight Available for Experiments &amp; Contingencies

942

Approximate capability based on launch vehicle control weights and
205, 000 pound thrust J-2 engine.
* " Based on latest mass data from MSC for AS-207 spacecraft.
*** Does not reflect installation of any external meteoroid shield.

TABLE 4.1-2
SSESM WEIGHT BREAKDOWN SUMMARY
Item

Weight (lbs.)

Docking Structure, Airlock and Systems Support Brackets

2, 000

Environmental Control System

3, 443

Instrumentation, Communications, Electrical Power, Displays

3, 364

Spent Stage Experiment Furnishings and EVA Provisions
Total Weight

383
9,190

4-16

i

�TABLE 4.1-3
DETAIL WEIGHT BREAKDOWN
Item

Weight (lbs.)

Docking Structure, Airlock and
System Support Brackets

(2, 000)

Airlock cylinder
Battery and Sphere Support Structure
Support Structure (incl. meteoroid shield)
Environmental Control System

1,150
360
490
(3,443)

Valve, Relief, 3000 p.s.i.(3)
Valve, Solenoid, 3000 p.s.i. (2)
Valve, Hand, 3000 p.s.i.(7)
Orifice (2)
Regulator 1st Stage
Regulator 2nd Stage
Regulator 3rd Stage (2)
Valve Relief, 7 p.s.i.g.(2)
Valve, Equalizer (2)
Gage, Pressure, 3000 p.s.i.
Gage, 10 p.s.i.(3)
Disconnect, gox, Ground Fill (2)
Disconnect, gox, PLSS
Filter
Check Valve (7)
Flowmeter (2)
Disconnect (4)
Hand Valve
Overboard Line
Disconnect (2)
Relief Valve
Valve (2)
T ubing
Spheres, Large, 02 (4)
Spheres, Small, PLSS
O2 for Large Sphere
02 for Small Sphere

9
3
11
1
10
10
16
4
4
1
3
2
1
1
3
1
2
2
2
1
3
5
56
I960
50
1222
60
4-17

�TABLE 4,1-3 (Cont'd.)

Item

Weight (lbs.)

Instrumentation, Communications, Electrical Power,
Displays
Measuring Racks,, ECS and Housekeeping(2)
Multiplexer 270 Mux.
FM/FM Transmitter
RF Transmitter
Measuring Racks, Experiment (3)
Transducers
Batteries
Control Panel
Voltage Sensors (2)
Display Panel
Power Supply
Wiring. Plug etc. (includes Battery Cabling)

(3 : 364)
42
21
14
13
63
50
2,940
50
1
15
5
150

Spent Stage Experiment Furnishings and EVA Provisions

(383)

LH2 Tank Fans (6)
Portable Task Lamps (3)
Airlock Lamps (3)
Lights and Fixtures (S-IVB)
Tether Kit
Reactionless Tool Kit
Astronaut C&gt;2 and Life Support Pkg. (3 lines)
Portable Life Support System (2)
PLSS Expendable (3)
Pressure Suit (2)
Thermal-Meteoroid Garment (2)
Constant Wear Garment (4)
Suit Umbilical Connect
Equipment Racks (6)
Bolt Storage
Tool Kit

30
2
2
10
8
9
20
128
8
64
46
12
3
20
1
20

Total

190
4-18

�4.1.7

Interface Requirements

Interface Areas - Four major areas of interfacing are required:
(1) Spacecraft to SSESM; (2) SSESM to Instrument Unit; (3) SSESM to S-IVB
Stage; and (4) SSESM to KSC Facilities. Areas 1, 2, and 3 are shown on
Figure 4.1-7 titled Saturn IB SSE AS-209 Interface Requirements (orbital
phase). Area 4 is shown on Figure 4.1-8 titled Saturn IB SSE AS-209 Interface
Requirements (KSC Phase).
Extended documentation will be based on these interface areas.
An outline of these interface area contingencies are:
1. Spacecraft* to SSESM
a. Command Module docking ring to docking tunnel mounted
as integral component of SSESM.
b. SSESM to SLA (LEM attach points).
c. SSESM originated electrical cables to SLA (bonded cable
support).
* Consists of CSM and spacecraft LEM adapter (SLA).
2. SSESM to Instrument Unit
a. SSESM associated electrical equipment to IU coldplates.
b. SSESM originated electrical cabling to IU coldplates.
c. Space Envelope Requirements.
3. SSESM to S-IVB Stage
a. SSESM bellows to LH2 tank.
bracket.

LH2 tank.

b. SSESM passivation cable to S-IVB forward skirt interconnect

c. SSESM originated cabling, fluid lines and equipment to

4-19

�4. SSESM to KSC Facilities
a. SSESM to handling equipment.
b. SSESM MSFC furnished checkout and control equipment to
KSC electrical and pneumatic sources.
Interface Tooling - MSC and/or the spacecraft contractor will
provide the airlock/spacecraft interface tooling. The S-IVB stage contractor
will provide the airiock/S-IVB adapter interface tooling,
Field Splice Connecting Hardware - MSFC will supply the connecting
hardware for all airlock unit field splices, The interface hardware will be
specified and documented on vehicle assembly documentation by the S-IB stage
contractor. The hardware will be delivered to Cape Kennedy in compliance with
the vehicle assembly schedule for AS-209.
Interface Control Procedures - Interface control procedures will
be under the cognizance of MSFC. All interfaces will be. controlled in accordance
with Interface Control Documents (ICD's) in the Apollo Intercenter Interface
Control Document Log (1A01) and the Saturn Interface Control Document Log (1S01).
Supplementary documentation will be prepared as required.
4.1.8

Composite Documentation Plan

All documentation for the experiment shall be prepared in
accordance with existing MSFC procedures and shall be released through
normal channels as defined in MSFC Drafting Manual. There shall be a
minimum of additional documentation developed. All existing S-IVB stage
and Instrument Unit drawings will be modified to reflect incorporation of
the experiment. The experiment shall have a system specification and sub­
ordinate specifications as required to fully reflect configuration and meet
the minimum requirements of NPC-500-1. Test plans and procedures will
be prepared in accordance with the requirements of NPC-500-10.
A documentation tree shall be prepared to reflect all specifi­
cations lest plans technical documentation, and manufacturing procedures
with procedures for preparation, schedules, and responsibilities.

4-20

���4.1.9

General Test Plan

A general test plan will be developed with the purpose to
document test planning for the SSESM flight hardware and supporting
hardware. The SSESM will be considered a stage for purpose of preparing
the test plan and defining the requirements in accordance with Apollo Test
Requirement document NPC-500-10. The majority of hardware utilized on
the stage is qualified for the Apollo program; hence, will require functional
acceptance test and documentation to verify qualifications to at least the
environment predicted for the new zones (location).
The hardware will be identified by serial numbers and quantity.
A cross reference will be made to test requirements and, upon completion of
the test, verification will be documented.
Each component shall be classified into one of three categories
of criticality and based upon these, rigid test requirements shall be developed.
The plan shall be established into major sections: Ground Test
Program Networks (PERT form of test article flow), Qualification Program
Summary, Acceptance Test Program, Piece Part and Component Test Program
and a listing of criticality and failure effects. For each of the test programs
the following types of information will be provided: Test type, test category
and title, hardware generation level, test document reference, hardware
identification, constraints, GSE and facility requirements, and responsibility
for test activity.
As an inhouse project with a critical schedule and using existing
hardware in many cases, testing and documentation will be held to a minimum
while meeting requirements of a flight worthy stage. Tests shall be designed
to obtain data for related tests and not for one alone. This is necessary
because of limited funds and urgent need for maintaining schedules.

4-23

�4.2

STRUCTURE

4-2.1

Description

I lie SSESM, as a structure, consists of a number of basic
subsystems as listed below and as shown in Figure 4.2-1:
1. Airlock cylinder
2. Flexible boot
3. Support structure
4. Forward meteoroid protection
5. Pressure container support structure
6. Electrical batteries support structure
Airlock Cylinder - The airlock cylinder is the pressurized
portion of the module, providing the connection of the CSM to the S-IVB
hydrogen container. The structure is approximately 210 inches long, 65
inches in diameter and has three hatches and doors respectively; the forward
hatch is 32 inches in diameter and it is assumed, that the basic LEM hatch
can be used without modification. The side door has a clear opening of 55
inches by 36 inches and opens to the inside of the cylinder. The aft hatch has
an opening of 48 inches in diameter, and also opens to the inside of the
cylinder. The cylinder is of welded construction, using A1 2219-T87. The
forward bulkhead incorporates the docking adapter, which is an integral
part of this bulkhead. The adapter is 32 inches in diameter, approximately
20 inches long and has all necessary features for incorporating the CSM
irogue and latching mechanism. The docking adapter loads (pressure
• inii docking) are distributed to the outside cylinder by integral stiffeners
and struts from the lower end of the docking adapter. The forward portion
of the airlock cylinder is stiffened by 16 longerons running from the forward
bulkhead to the center ring at which the horizontal airlock support struts
are attached. The skin of the cylinder is milled from approximately 1 inch
plate stock, the longerons are attached to milled ribs with mechanical
fasteners. Lugs for tapped holes (from the inside) are provided to give
maximum variability for internal attachments of components.
A smaller ring on the forward portion of the cylinder
provides attachment for the battery assembly support structure. The larger
4-24

�00

o
1

o

CO
X
CO
U
J

B

O
2
H
cd
O
a,
a.
D
CO

H
Z
W
oS
W
OH
X
w
w
o

ES

CO

EZ
OH
CO

I

CO

CN
TP
W

eH
D
O
HH
to

�center ring, attaching the horizontal struts to the airlock, has I-cross
section and is welded into the skin in the same fashion as the smaller ring
at the forward part. The lower portion of the cylinder contains the large
opening for the side door. Eight longerons are placed around the circumfer­
ence, distributing the loads introduced by the ECS system pressure containers
and the support structure. One of the longerons is cut in the area of the door
opening and is incorporated into the door frame. The adjacent two longerons,
though not cut, are also incorporated into the frame structure. The frame
itself is approximately 8 inches wide and is a built-up torque box to limit the
deflection under pressure. Again the design of an all welded construction,
with externally attached frames and longerons, is maintained. The lower
bulkhead consists of the hatch frame and a stiffened circular plate. The
stiffeners are attached to the bulkhead without fasteners through the pressure
skin. The assembly is welded into the cylinder as a ring. The hatch frame
is supported to the lower ring of the cylinder with 8 rods. The bulkhead
serves also as the ring necessary to react the loads of the four diagonal
struts of the support structure. The lower part of the cylinder is again
formed from milled skin, welded together. Eight longerons are provided
and an end ring provides attachment for the flexible boot.
The method of fabrication is as follows: the cylinder is,
as discussed above, broken into four cylinder assemblies, three ring
assemblies and the forward and aft bulkhead. These subassemblies will
be welded together with circumferential welds to form the complete airlock
cylinder. The side door is fitted to the inside of the cylinder and is supported
in the opened condition on guide rails. The single curvature door is designed
as a stiffened plate, has a cam and roller closing mechanism and a nonmetallic seal. It can be operated from both sides and incorporates a
pressure equalization valve and a small window. The circular hatch in
the lower bulkhead is hinged from the frame and is designed as a stiffened
plate. It incorporates similar features as the door, but is required to
s-al under pressures from both sides. Materials used for the basic doors
are A1 2219-T87 or A1 7075-T6.
Flexible Boot - The connection between the SSESM and the
spent stage manhole will be provided by a flexible boot, bolted to the lower
ring of the airlock cylinder. The boot is fabricated from neoprene or other
suitable material with fibrous reinforcements. Material selection is pending.
During powered flight, the boot is stored inside the lower portion of the
cylinder. During spent stage activation, the spent stage manhole cover is
the fleXU,Ie

b00t b0lted t0 the SpeM

4-26

the —a

�Support Structure - To attach the support module to the
four hard points, located in the SLA (Spacecraft-LEM Adapter), four
outriggers are connected to the airlock cylinder. The horizontal structure
consists of 8 I-beams, held together at the outside points by four fittings.
These fittings also connect to the counterparts in the shroud and are machined
parts. The other ends of the beams connect to the center ring in four places
with pinned joints. The horizontal beams also provide attachment for the
meteoroid shield and its support structure. The four diagonal struts,
extending from the outer fittings to the lower ring on the cylinder, are
made from tubes and associated end fittings to the ring. The material used
is 7075-T6.
Forward Meteoroid Protection - Additional meteoroid
protection for the forward bulkhead of the S-IVB stage is provided by a
bumper sheet, made of aluminum honeycomb 1-inch thick, supported by
channels attached to the support module. This shield forms a closed
compartment around the lower half of the SSESM and a door to permit
extravehicular activities is provided adjacent to the cylinder side door.
The structure is fabricated from A1 7075-T6.
Pressure Container Support Structure - The necessary
pressure containers for the slug pressurization of the module and spent
stage are stored in groups of two in an appropriate support, mounted to
the lower part of the airlock cylinder. The support structure is basically
a truss and connects to the cylinder at only four places, at the center and
lower rings and the intersection with the longerons. The trusses are
fabricated from A1 7075-T6.
Electrical Battery Support Structure - The necessary
batteries for the electrical power supply are mounted with a special
structure to the forward portion of the cylinder. Eight of the longerons,
(every second one) are built as machined parts in the area between the
smaller forward and the main ring. Shelves for each battery assembly
are mounted to the longerons. The material used is A1 7075-T6.
4.2.2 Structural Weights
The total weight for the structure and all parts as described
is 2, 000 pounds. A weight summary is given below:

4-27

�1. Airlock cylinder
(Including flexible boot)

1,150 lbs.

2. Battery and pressure container
support structure

360 lbs.

3. Support structure
(Including meteoroid shield)

490 lbs.

Total

2, 000 lbs.

4.2.3 Structural Test Requirements
The structural test requirements are to structurally qualify the
SSESM prior to launch by verifying the integrity of the structure under
simulated flight load environments and to substantiate the basic design
assumptions and methods of analysis. These tests will be performed on
the test and training article.
Pressure Tests - on the airlock cylinder will require three
separate pressure cycles in order to subject the door and hatches to the
required magnitude and direction of pressure, and to qualify the total
airlock cylinder.
Static Load Tests - on the entire configuration, applying both the
static load and corresponding dynamic (equivalent static) load will simulate
the most critical flight condition.
Docking Load Tests - will qualify the docking structure to the
given docking load requirements.
Component Tests - will verify locking mechanism, leak rate and
deflection on the door and hatch.
Vibration and Acoustic Tests - The assembly vibration tests will
employ sinusoidal sweep and random dwell tests in three axes on an assembled
prototype airlock structure with all associated equipment and hardware installed
Those items of equipment required to function during launch and boost should
be functionally checked during this test. Items which cannot be made available
for this test should be simulated as closely as possible with dummy items.
The assembly acoustic tests will check the airlock assembly
described above in a reverberant acoustic field to specified procedures .
Functional tests should be made on appropriate equipment.
4-28

�The meteoroid shield acoustic test will subject a representative
section of the meteoroid shield to the acoustic environments to assure
reliability. Plane wave and/or reverberant field acoustic tests will be
specified.
Detail requirements for vibration and acoustic testing are
given in the Appendix.

4-29

�4.3

ENVIRONMENTAL CONTROL SYSTEM (ECS)
4.3.1

System Description
1. Concept

The spent stage environmental control system (ECS) is
designed to provide airlock/lab atmosphere contamination and thermal
control via a combination of active and passive techniques; thereby
utilizing to the maximum extent possible, off the shelf flight qualified
hardware. These techniques afford a minimum approach to satisfy
shirt sleeve environment maintenance with the intent to be compatible
with launch schedules at minimum costs.
The large volume of the S-IVB LH2 tank is unique to
2-3 man spacecraft and permits control of metabolic CO2 generation
within allowable pressure limits by scheduling leakage compatible with
occupancy schedules. The H2O vapor generation can be kept within
limits by a combination of atmosphere leakage/02 make-up and adsorber
utilization. Thermal control of the atmosphere can be kept within limits
via judicious establishment of surface coatings and vehicle orientation.
The maintenance of electrical equipment temperatures can also be
realized with use of passive techniques rather than utilizing active
coolant loops.
The ECS is designed to the following parameters:
1. Atmosphere Environment Parameters
a.
b.
c.
d.
e.
f.
g.

Temperature
Pressure
Composition
Relative Humidity
C02 Limit
Temperature Chg/RPL Gas
Temperature Suit Loop Gas

65±25°F
3.5 to 5.5 p.s.i,a.
Oxygen (one gas)
30 to 70%
.147 p.s.i.a.
70±5° F
50±5°F

2. Metabolic
a.
b.
c.
d.

C02 Production Rates
H2O Production Rates
O2 Consumption
Heat Production
4-30

2.4 Ib/man-day
3.2 lb/man-day
2 Ib/man-day
425 BTU/man-hour

�2.

Slug Pressurizaticn Mechanics

Continuous Leakage Concept - The atmospheric conditioning
system must perform the function of removing carbon dioxide and water vapor
such that the percentage of each is within metabolic limitations. This function
can be accomplished by venting the atmosphere (02 -f- CO2 •/• H2O) over
board and replinishing with pure O2 (see Figure 4 .3-1) at a rate dependent
upon the amount of time for astronaut occupancy and time desired prior to
exceeding allowable limits. The volume of the occupied space becomes
significantly important when establishing time to available contaiminent
limits; hence the large volume of the S-IVB LH2 tank and controlled level of
astronaut occupancy afford the so called "slug" concept consideration.
Studies show that the water vapor partial pressure approaches
the maximum metabolic limits at a rate exceeding the carbon dioxide con­
centration. (see Figure 4.3-2 and 4.3-3). As subsequently discussed an
adsorber can be easily used to circumvent exceeding the maximum water vapor
limit, therefore, the C02 limit was utilized to establish mission duration and
leakage criteria. Also it should be noted from Figures 4.3-2 and 4.3-3
that the unoccupied period allows a time for the contamination level to reduce.
The mission duration dependency upon occupancy cycle and
leakage rate is depicted by the data of Figure 4.3-4. As can be observed
from the figure a leakage rate of 30 lbs/day will allow a occupancy cycle
(2 astronauts) of 4 hours in the Lab followed by 9 unoccupied hours for a
total of 18 days. As a note, 28 mission days can be realized by reducing
the occupancy cycle to 4/11 hours.
Blow Down Concept - The continuous leakage concept employs
venting oxygen Over board at varying (increasing) percentages of carbon
dioxide. By allowing the C02 to reach the maximum or near maximum limit,
then venting the Lab atmosphere down to the minimum total pressure limit
followed by re-establishing total pressure (see Figure 4.3-5) with make-up
oxygen, a total weight savings could be realized. A weight saving of 100
pounds of 02 could be realized by this technique (see Figures 4.3-6 and 4.3-7);
however, this is not currently planned until astronaut time lines and minimum
stage leakage values are established.
Moisture Removal - Moisture removal in current spacecraft
systems is accomplished via condensing heat exchangers which utilize coolant
loops for a heat sink. In the absence of coolant loops and for desired simplifi­
cation, moisture removal to accommodate the 30 to 70% relative humidity comfort
zone is to be obtained by the use of an adsorbent,
4-31

�Controlled
Leakage
(02 + COz + H20)

02 Leakage Makeup

FIG. 4.3-1 CONTROLLED LEAKAGE CONCEPT

Time (hrs)
FIG. 4.3-2 C02 CONCENTRATION

4-32

�FIG. 4.3-3 H20 CONCENTRATION

FIG. 4.3-4 MISSION DURATION DEPENDENTS
4-33

�FIG. 4.3-5 BLOWDOWN C02 CYCLE

Schedule

FIG. 4.3-6 OCCUPANCY SCHEDULE AND TIME
RELATIONSHIP
4-34

�1300

1100 -

900 -

500 300 H—i—r
0
2
Occupancy Time (days)

FIG. 4.3-7 OCCUPANCY TIME VS. TOTAL
02 WEIGHT REQUIRED

Metabolic HzO
Relative Humidity
Adsorber

3. 2 lbs/man day
30% to 70%
Silica Gel
Activated Alumina

FIG. 4.3-8 SCHEMATIC OF MOISTURE REMOVAL
4-35

�Desirable characteristics of adsorbent include: (a) large hydroscopic
depression over a considerable range of moisture content; (b) chemical
and physical stability; and (c) freedom from odors. Adsorbents used in
commercial air conditioning include silica gel and activated alumina.
The use of a silica gel system has been investigated. This system could
be located in the Lab (emplaced by an astronaut activity) as shown in
Figure 4.3-8. The amount of moisture removal required to achieve the
30 to 70% R.H. range and the amount of silica gel required is shown in
Figure 4.3-9. Additional studies are required to establish operation
concept to insure humidity control; these could include intermittent manual
operation of the fan or manual exposure of measured quantities of pre­
packaged adsorbent in order to prevent "dry" atmosphere conditions. It
is also interesting to note that desorption of the adsorber could be
accomplished by vacuum exposure thereby permitting reuse, however,
a significant weight savings is not involved.
3. Oxygen Storage
The state (cryogenic/gaseous) of storage for the atmo­
spheric oxygen storage is influenced by many parameters and/or engineering
trade-offs. The MSFC 20-day concept employs gaseous storage for the
reasons of simplicity, low cqst and reliability. As an example, GSE
cryogenic servicing capability, a key consideration, is not needed; the
bottles can be charged a considerable time prior to launch and manually
disconnected The oxygen storage requirements are dictated by the
following needs:
Lab Pressurizations
Airlock Usage
Lab Leakage
Suit Loop
Metabolic
EVA

1.25 Chgs
1 cycle/day
30 lb/day
10 lb/manhour
2 Ib/manday

The Lab leakage of 30 lb/day is a controlled leakage dictated
by mission duration and an astronaut Lab occupance schedule of 4 hours in
the Lab out of a 13 hour period (2 men). As subsequently discussed, variations
in storage can be realized by adjusting the occupancy schedule. The suit
loop oxygen storage is planned for use as primary life support during airlock
engress/ingress operation with the PLSS. No other use (EVA) is planned due
to the high 02 use rate needed for metabolic cooling when performing tasks.
The 10 Ib/hr value affords only moderate task performance. Metabolic oxygen
4-36

�FIG. 4.3-9

WATER VAPOR REMOVAL AND
ABSORBENT REQUIREMENTS

FIG. 4.3-10 ADDITIONAL OXYGEN REQUIREMENTS
VS. ASTRONAUT LAB OCCUPANCY

4-37

�is provided only for the two men when occupying the lab at the 4 of 13 hour
schedule. EVA oxygen is provided for PLSS recharge in excess of 60
manhours. Life support during stage activation tasks and other EVA are
to be accomplished via a PLSS mode. The oxygen weight breakdown is as follows:
Lab Charge
Metabolic
Leakage
Airlock
Suit Loop

340 lbs
18
540
144
180
1222 lbs

EVA

15 lbs
1237 lbs

Total

The C&gt;2 storage is to be accomplished via 19.5 ft^ containers
w h i c h w ith initial and rest pressure of 3000 p.s.i.a. and 50 p.s.i.a. respectively
will afford a useable weight of 360 lbs per sphere . Four spheres, fully
charged, will afford an 18% (220) lb contingency. PLSS recharge oxygen will be
stored in a separate 3 ftsphere since minimum pressure of approximately
1000 p.s.i.a. can be reached and yet perform the PLSS recharge functions.
4. Additional 07 Required for Added Staytime
The impact of Lab astronaut occupancy schedule upon oxygen
storage is further demonstrated by Figure 4.3-10. A schedule of less than
4/9 will permit oxygen removal since the 30 lb/day leakage valve may be
decreased whereas an increase occupancy schedule will require additional
oxygen.
5. Internal Air Distribution
The large volume of the S-IVB LH2 tank affords a space
laboratory for which judicious engineering must be pursued to provide air
movement distribution needed to accommodate astronaut metabolic cooling.
Until recently, studies of atmospheric conditioning of spacecraft have been
concerned almost exclusively with the requirements for pressure suit
operation. In all but one of the Gemini flights, as in the previous Mercury
flights, the astronaut is maintained in ventilated pressure suits which were
unpressurized in normal operation. This technique affords controlled
flow paths about the human body for cooling and/or heating. Small space­
craft cabins, such as Gemini, can accommodate a shirt sleeve environment
by judicious inflight positioning of suit loop supply hoses to cause cabin air
movement.
4-38

�Man normally dissipates waste energy by a combination
of radiation and convective heat transfer and evaporation mass transfer.
Any deficiency in the energy balance is accompanied by heat storage in
the body which results in a change in the average body temperature and
thereby placing man in an uncomfortable atmosphere. Some of the design
criteria applicable to a spacecraft shirt sleeve environment require
further study. As an example, comfort zone conditions of temperature,
humidity, and ventilation rates are commonly based on experience in the
Earth environment. However, since the reduced gravity environment
should affect only the convective heat transfer of the total energy balance,
engineering design can be employed to cause air movement by forced
means (fnas, etc.). Studies by Air Research have established apparent
zones of comfort depending upon ambient temperature and air velocity
at given conditions of inside cabin wall temperature and atmosphere
temperature (see Figure 4.3-11). Fans such as the Gemini cabin fan/
heat exchanger assembly (stripped of the heat exchanger) would afford
center line velocity as shown in Figure 4 .3-12. This velocity also varies
with radial position. Placement of four fans inside the Lab as schematically
shown in Figure 4.3-13 will afford near complete circulation of the volume. By
making these fan positions adjustable, as astronaut may be permitted to
adjust the direction and velocity at work stations to achieve as near a
comfortable environment as possible.
6. Oxygen Storage Temperature and Heating Requirements
Although gaseous storage of oxygen is to be employed, the
requirements of use necessitate warming of the gas. Althrough the oxygen
may be stored at near the desired temperature, expansion from the high
pressure storage to the use-pressue will result in gas temperatures con­
siderably lower than allowable, particularly for the suit loop &amp; airlock
charging supply. The Lab replenish O2 heating may be unnecessary due to
the small flow and orbital heating.
The use and temperature requirements are shown in
Figure 4.3-14. Individually thermostatically controlled electrical heaters are
to be employed for use oxygen temperature maintenance. It is noted that
warming of the initial Lab O2 charge is not proposed. Studies have shown
that orbital LH2 tank side wall heating will warm the initial charge within
a single orbit. Since the use temperature is also dependent upon the initial
storage temperature, studies have been performed to assess the need for
electrical heaters in the O2 bottles. Limited results depicted by Figure 4.3-15
show that passive thermal control techniques are suitable, thereby voiding
heater necessity. These sphere studies employed the assumptions shown in
Figure 4.3-15.
4-39

�M = 500 btu/hr
200-J D e w

•c
»-&lt;
J:
Requirements:
(1) M e t a b o l i c C o o l i n g
(2) A t m o s p h e r e M i x i n g

&lt;+-4

100-

&gt;

100

FIG. 4.3-11 ASTRONAUT COMFORT ZONE FOR
FORCED CONVECTION

C e n t e r l i n e D i s t a n c e (ft)

FIG. 4.3-12 GEMINI CABIN FAN VELOCITY
PROFILE
4-40

�FIG. 4.3-13 SCHEMATIC OF FAN COVERAGE

FIG. 4.3-14 OXYGEN USE AND TEMPERATURE
REQUIREMENTS

4-41

�30 Ibm/day

(hrs)

(days)
Mission Time

FIG. 4.3-15 GASEOUS BOTTLE TEMPERATURE
RESPONSE
4-42

�Of particular interest is the minimum SLA temperature condition which
corresponds to an average orbital temperature with the longitudinal
vehicle axis held paralled to the solar vector. Even with this low
temperature the oxygen rises in temperature after initial lab charging.
Rigorous thermal analysis of the entire SLA area cognizant of use rate
profiles are to be performed to further establish painting needs. Studies
are also required to assess the need for static thermal conductors in the
spheres to afford gaseous heating from the tank wall in the near zero
gravity state. The temperature of Figure 4.3-15 would not have decreased
as rapidly had such a device been considered.
7. Thermal Control of Workshop Environment
Use of active cooling and/or heating of the internal gas
atmosphere is not compatible with either schedule or available funding.
Therefore, studies have concentrated on passive thermal control methods.
That is, maintaining gas temperatures within acceptable limits (specified
as 65±25° F by MSC) through use of thermal control coatings on the S-IVB
fuel tank, and through vehicle orientation relative to the Earth and Sun.
The initial study considered the present S-IVB fuel tank
paint,°(= 0.3,£ -=0.9. This paint is unacceptable, since even with
orientation for maximum heating (vehicle side perpendicular to sun
direction), the temperatures are too low.
Considering a white paint similar to that presently used
on the S-IVB APS fairing, - 0.2, 6 - 0.2, the fluctuations in temperature
are much less (see Figure 4.3-16). Unfortunately, this paint cannot be
maintained due to the possibility of contamination to some unpredictable
extent by retro-rocket and/or launch escape system tower jettison motor
exhaust products. Figure 4.3-16 also shows predicted temperatures for
this paint after contamination. It can be seen that intolerably high temper­
atures result even after two orbits, wherein the maximum value has not
yet been reached. This shows that preflight selection of a white paint,
- 0.2, £ ^0.2 and velocity orientation is risky because concievably the
ratio °y£ could increase from 1 to 2 or 3 due to contamination, causing
extremely high environmental temperatures. Data from previous Saturn I
flights have indicated that such contamination occurs. Furthermore,
ground test measurements of test specimens contaminated by solid rocket
motor exhaust indicate that the solar absorptivity («*) of a white paint is
increased to a greater extent that the infrared emissivity (£).
4-43

�VEHICLE ROLL 6 RPH

FIG.

4.3-16

E N V I R O N M E N T A L GAS T E M P E R A T U R E S
4-44

�Figure 4.3-16 shows predicted temperatures forc&lt;s0.8,
£=0.8 for orientation of the vehicle longitudinal axis parallel to the sun
direction (end toward sun) and also velocity oriented. From this figure,
it can be seen that temperatures can be reduced substantially as orientation
is changed from velocity to end toward sun. The present thinking is that
a coating wither*0.8, 6 = 0.8 should be used in order to minimize changes
in surface properties due to contamination, and that the vehicle should be
oriented relative to the sun such as to maintain acceptable temperatures.
Presently, studies are being made to verify the feasibility of tli s approach.
A comfortable environment requires that the inner tank wall
temperature, as well as the gas, be maintained at near 70°F . A study
showed that even with the internal gas temperature maintained at 70°F, the
wall temperature varied from 25 to 130° F. Vehicle rotation of 6 RPH about
the longitudinal axis (roll) reduced the maximum temperature from 130 to
85° F and increased the minimum from 25 to 40° F . Therefore, it is
recommended that the vehicle be rotated (roll) at 6 RPH.
8. Electrical Equipment Temperature Control
To further establish the feasibility of eliminating the active
coolant loops the operating temperature of the electrical equipment must
be established and compared with allowable "skin" temperature limits.
The planned electrical equipment and their schematic locations are shown
on Figure 4.3-17. Analysis of the batteries have been pursued to assess
passive thermal control feasibility and is shown in Figure 4.3-18. The
three noted cases of Figure 4.3-18 basically show that control can be
achieved passively. Of particular interest is the minimum heating condition
(Case 3) where the batteries are off. This data shows the temperature
response to be sluggish and thereby not requiring heating on the dark side
of the orbit. However, covering the batteries with a material with low
infrared emissivity may be needed during the stage activation period and
for the inactive batteries. Also of significance is the analysis showing
that the batteries can be kept sufficiently cool when operating and the
vehicle is oriented for maximum solar irradiation (Case 2).
The components mounted on the I.U. have not been studied;
however, it is known that the current I.U. thermal conditioning systems
release approximately 30% of the total component heat load by radiant means.
With considerably reduced heat load, passive thermal control is expected
to be adequate. Additional in-depth studies are planned.
4-45

�u u n—
• [log
• foo

//

•
•
•

]
]
]

AL

\

IU
irn

//^S-1VB

HI

LH2 T a n k ^ ^ ^ ^

FIG. 4.3-17 ELECTRICAL, EQUIPMENT
TEMPERATURES

Case 1 Side to Sun
2 Side to Sun
3 E n d to S u n

180

Spinning, e=0. 5, a = 0.5, q = 100 watts
Spinning, e = 0. 8, a = 0.2, q = 100
Spinning, e = 0. 8, a = 0.2, q = 0

360
Orbit Position (deg)

FIG. 4.3-18 BATTERY TEMPERATURE DURING
ORBIT
4-46

�9. Electrical Energy Requirements
As noted in previous sections, electrical energy is needed
to provide heat for warming the life support oxygen. In addition, power
is needed to power the tank fans for air mixing and astronaut comfort
conditioning in addition to control and display power. The power require­
ments are estimated to be as follows:

Tank fans
Suit loop 02
Lab 02
Airlock 02
Control &amp; Display
Total

LOAD

DUTY

AVG

KWHR

220 watts
400
20
450
50

38%
5
100
2
38

84 watts
20
20
9
20

36.40
8.64
8.64
3.88
8.64

1140

153

66.20

The duty cycle was established by considering the estimated use period needs
subject to additional study.
10. Prelaunch Purging/Thermal Conditioning
The compartment formed by the SLA, I.U., and S-IVB
stage forward skirt will require purging to reduce explosive hazard potentials.
The injection of GN2 gas in sufficient quantities will afford 02 concentrations
less than 4% with consideration of air infiltrations. By placing covered
openings in the meteoroid shield, the current Apollo spacecraft and I.U.
purges, shown in Figure 4.3-19, will afford the required environment inclusive
of temperature control.
4.3.2

ECS System Functional Description
1. Function

The two major subsystems comprising the ECS are the
stage and airlock atmosphere system (SAAS) and the PLSS Recharge System.
The functions of the SAAS are to be provided pressurizing gox for maintaining
the LH 2 tank atmosphere, to supply gox to the astronauts space suits through
umbilical lines, and to provide gox for recharging the airlock when used for
extravehicular activity (EVA). The function of the PLSS recharge system is to
provide gox for recharging the astronauts' portable life support system backpacks
for use in EVA. Figure 4.3-20 presents a functional schematic diagram of the
systems
4-47

�FIG. 4 . 3 - 1 9 COMPARTMENT CONDITIONING

4-48

�2. Stage and Airlock Atmosphere System
Fill and Dump - Gox for the SAAS is stored in foir 19.5
cubic foot, 3000 p.s.i.a., Inconel 718, high pressure oxygen storage spheres
(1A), (IB), (1C) and (ID), Figure 4.3-20, which are located outside the
airlock on the supporting structure. Fill is accomplished through the
fill self-sealing quick disconnect coupling (15A), filter (17), and sphere
fill check valves (20B) and (20C). Each relief valve (3A) and (3B) prevents
the overpressurization of two spheres . Gox also flows through isolation
check valves (20A) and (20D) to the isolation hand valve (5A) which is closed
until after CSM turn around and docking. The isolation check valves prevent
a loss of the entire SAAS gox supply in the event of a leakage in one of the
spheres. Sphere dump valve (4A) is provided for the dumping of gox in
the event of a launch abort. Since there is no requirement for system
dump during boost or in orbit, the Sphere Dump Valve is manifolded back
to the fill line, where the self-sealing quick disconnect coupling seals
the line upon umbilical disconnect.
Pressure Test - The airlock is pressurized with gox on the
ground through a self-sealing quick disconnect coupling and a pressure leak
check is performed utilizing a ground test airlock relief valve which is
coupled to a quick disconnect coupling attached to the outlet of the airlock
relief valve (11A). After the pressure test has been performed, the ground
test airlock relief valve will be removed and the airlock relief valve will
maintain the airlock at 5.0 p.s.i.g. during the remainder of the mission.
Operation - The SSESM is pressurized initially prior to launch
and, after docking has been completed, airlock operations are initiated
by opening the CSM hatches and equalizing pressure across the airlock
upper hatch. This is accomplished by utilizing the upper hatch equalization
hand valve (12A) and upper hatch airlock pressure gage (P-4).
Airlock Depressurization - Once the airlock has been entered,
it will be necessary to perform EVA before proceeding with the mission .
To perform EVA, the airlock musl be depressurized. After closing the upper
hatch and donning and testing their space suits, the astronauts will depressurize
the airlock by opening the airlock bleed hand valve (10). When the airlock
internal pressure is sufficiently low, the side hatch may be opened and EVA
performed.
Airlock and Stage Pressurization - After the airlock has been
mated to the LH2 tank forward bulkhead and the astronauts have reentered
and sealed the airlock, pressurization of the assembly may begin. Pressuri­
zation is accomplished by opening the isolation hand valve (5A) which allows
3000 p.s.i.a. oxygen to pass through the tank flow control quick charge orifice
(bB) to trie tank quick charge hand valve (2IE). High pressure oxygen also
flows through the first stage regulator (8) where the pressure is reduced
Horn 3000 p.s.i.a. to 100 p.s.i.a. The flow then continues through the airlock
4-49

�4-50

�flow control quick charge orifice (6A) to the airlock quick charge hand
valve (21A), and also to the airlock second stage regulator hand shutoff
valve (21B) and the tank second stage regulator hand shutoff valve (21C).
Once the isolation hand valve is opened, pressurization may be accomplished
by opening the tank quick charge hand valve and the airlock quick charge
hand valve.
Airlock and Stage Pressure Control - When visual observation
of the airlock and tank pressure gages confirms that the pressure is up to
5.0±0.2 p.s.i.a., the quick charge valves are closed and the tank and airlock
second stage regulator hand shutoff valves are allowing 100 p.s.i.a. gox to
flow into tank second stage regulator (9B) and airlock second stage regulator
(9A), respectively. In these regulators, gox pressure is reduced from 100
p.s.i.a. to 5.0±0.2 p.s.i.a. Pressure relief capability is provided in both the
airlock and tank by airlock relief valve (11A) and lower trunk relief hand valve
(1 IB), respectively. A lower trunk bleed hand valve (2ID) is provided as a
backup to the lower trunk relief hand valve. The Iowa: bulkhead tank pressure
gage (P-5), lower bulkhead airlock pressure gage (P-4), and lower hatch
equalization hand valve (12B) permits equalization of pressure across, and
use of,the lower hatch.
Umbilical Extra Vehicular Activity - To provide a backup
capability for EVA using the SAAS gox system, umbilical attach points
have been provided. To utilize this capability, the isolation hand valve
(5A) must be open to allow 3000 p.s.i.a. gox to flow through the first stage
regulator (8), where the pressure is reduced to 100 p.s.i.a., to the manual
O2 metering valve (13). When umbilical EVA is required, the suit
umbilical will be plugged into either suit umbilical self-sealing quick
disconnect coupling (14A) or(14B), and suit exhaust self-sealing quick
disconnect coupling (14C) or (14D) will be attached to the outlet port
of the suit. The manual 02 metering valve will be opened and adjusted
to provide 3.5 p.s.i.g. in the suit. The low pressure suit umbilical relief
valve (22) will maintain the umbilical line pressure at 3.5 p.s.i.g. Umbilical
capability is designed to be used in checkout operations and as a backup to
the PLSS.
3. Portable Life Support System Recharge System
Fill and Dump - Gox for the PLSS recharge system is stored
in one 3-cubic foot, 3000 p.s.i.a., high pressure PLSS oxygen storage sphere (2)
which is located outside the airlock on the supporting structure. F ill is
accomplished through fill self-sealing quick disconnect coupling (15A), filter (17),
and PLSS sphere fill check valve (18A). Relief valve (3C) prevents overpressurization of the sphere or system. Gox also flows through isolation check
valve (18B) to isolation hand valve (5B) which remains closed until after CSM
turnaround and docking. The isolation check valve prevents loss of SAAS gox
in the event of a PLSS vent valve malfunction or a system leak. PLSS sphere
dump valve (4B) is provided for the dumping of gox in the event of a launch
4-51

�abort. Since there is no requirement for system dump during boost or in
orbit, the sphere dump valve is manifolded back to the fill line where the
self-sealing quick disconnect coupling seals the line upon umbilical disconnect.
Operation - When an astronaut's PLSS requires recharging,
the cap will be removed from the PLSS recharge valve and coupling assembly
(16) and the PLSS will be coupled to the outlet. To utilize the recharge
system, the isolation hand valve must be opened. This permits 3000 p.s.i.a.
gox to flow to the regulator (7) where the pressure is reduced to 900 p.s.i.a.
The valve on the PLSS recharge valve and coupling assembly will be opened
and 900 p.s. i.a. gox will flow into the PLSS. Upon completion of a PLSS
recharge cycle, both the isolation hand valve and the valve on the PLSS
recharge valve and coupling assembly must be closed. An intersystem
check valve (18C) in the interconnecting line allows gox flow from the SAAS
system to charge the astronaut's PLSS, if necessary; but prevents flow out
of the PLSS recharge system when gox in the SAAS spheres is used.
4. Pressure Display
A pressure display panel containing pressure and temperature
gages is provided in the airlock. The gages are as follows:
No.
PI
P2
P3
P4
P5
Tl
T2
T3
T4
T5

Direct Reading

Integral in airlock

Remote Reading
From transducer on spheres 1A &amp; IB
From transducer on spheres 1C &amp; ID
From transducer on PLSS sphere
From
From
From
From

tank
transducer on spheres 1A &amp; IB
transducer on spheres 1C &amp; ID
transducer on PLSS sphere

Integral in airlock
From tank

Gages PI, P2, Tl, and T2 are used to compute total amount of SAAS gox aboard.
Gages P3 and T3 are used to compute total amount of PLSS gox aboard. Gages
P4, P5, T4, and T5 are used for monitoring environmental conditions.
5. C09 Control
Several methods are available to monitor leakage or C02
levels. Flowmeters (19) in the gox supply lines would give an indication
leakage. Calculating the amount of gox onboard from the available pressure
and temperature displays and recording the amounts will give an indication
of the gox loss. CO2 partial pressure sensors will also give an indication of
the CC&gt;2 concentration. S-IVB LH2 tank leakage will be minimized by plugging
the tank outlets. The leakage will then be established by adjusting handvalve (210).
4-52

�TABLE 4.3-1
ECS SYSTEM COMPONENT REQUIREMENT

ITEM NO.

NOMENCLATURE

1A
IB
1C
ID
2
3A
3B
3C
4A
4B
5A
5B
6A
6B
7
8
9A
9B
10
11A

Bottle (ECS Supply)
Bottle (ECS Supply)
Bottle (ECS Supply)
Bottle (ECS Supply)
Bottle, gox, PLSS
Valve, Vent
Valve, Vent
Valve, Vent
Valve, Solenoid
Valve, Solenoid
Valve, Hand Op., ECS Shutoff
Valve, Hand Op., PLSS Shutoff
Orifice, Airlock Quick Fill
Orifice, Workshop Quick Fill
Regulator, PLSS Supply
Regulator, 1st Stage ECS Supply
Regulator, Airlock Pressure
Regulator, Workshop Pressure
Valve, Airlock Vent
Valve, Relief

1 IB
12A
12B
13
14A, B, C, D,
15AB
16
17
18A
18B
18C
19
20A
20B
20C
20D
21A

Valve, Relief
Valve, Equalization, Airlock Fwd
Valve, Equalization, Airlock Aft
Valve, Metering, Manual O2
Disconnect Couplings
Disconnect Couplings
Valve, Backpack Shutoff
Filter, Supply Fill
Valve, Check
Valve, Check
Valve, Check
Flowmeter, Workshop Supply
Valve, Check
Valve, Check
Valve, Check
Valve, Check
Valve, Hand Op., Airlock
Quick Fill
4-53

SIZE
19.5 Ft3
19.5 Ft3
19.5 Ft3
19.5 Ft3
3.0 Ft3
0.5" Tube Size
0.5" Tube Size
0.5" Tube Size
0.75" Tube Size
0. 75" Tube Size
0.5" Tube Size
0.5" Tube Size
0.38 Tube Size
0.38 Tube Size
0.25 Tube Size
0.25 Tube Size

1.0"

0.75" Tube Size
0.50" Tube Size
0.50" Tube Size
0.50" Tube Size
0.75" Tube Size
0.75" Tube Size
0.75 " Tube Size
0.75" Tube Size
0.38" Tube Size

�TABLE 4.3-1 (Cont'd)

ITEM NO.
21B
21C
21D
21E
22
P-1,2,3
P-4,5,6
T-1,2,3,4,5

NOMENCLATURE
Valve, Hand Op., Airlock Regulator S.O.
Valve, Hand Op., Airlock Workshop S..O.
Valve, Hand Op., Workshop Vent
Valve, Hand Op., Workshop Quick Fill
Valve, Suit Relief
Transducer, Pressure
Gage, Pressure
Pickup, Temperature

4-54

SIZE
0.38" Tube Size
0.38" Tube Size
0. 38" Tube Size
0.38" Tube Size
0.38" Tube Size

�4.4

ELECTRICAL SYSTEM

The electrical system is composed of power sources, a lighting system,
control panel, portable display panel, and cabling (Figures 4.4-1A and 4.4-1B).
These elements are described in the following paragraphs along with the
electrical portion of the S-IVB stage passivation subsystem, measurement and
instrumentation subsystem, and electrical interfaces. The electrical support
equipment is also covered in the subsequent paragraphs.
4.4.1 Power Sources
Power sources consist of twenty-one 28-volt batteries, of silverzinc oxide type, and rated at 500 ampere hours each. Battery dimensions are
approximately 8.5 by 10.5 by 23 inches, and weigh approximately 140 pounds
each. Twenty of the batteries are arranged in banks of ten each, Figure 4.4-2,
which will provide 5, 000 ampere hours of power per bank. The two banks
will be used on a predetermined sequence established to utilize the available
power most efficiently and reliably. Present estimated load on the system
is approximately 7, 000 ampere hours, exclusive of experiment power, as
shown in the load profile of Figure 4.4-3. The twenty-first battery is
provided as a source of emergency power and as a reference voltage source.
Two low voltage detectors, one on each battery bank bus, are used to detect
low voltage of these banks. Emergency power will automatically be applied
to the emergency bus when low voltage is detected on either battery bank bus.
Capability of manually switching to emergency power is also provided.
4.4.2 Lighting System
A lighting system is required to provide lighting associated
with the SSESM. Expected lighting requirements consist of acquisition lights
(40 watts), airlock lights (40 watts), and LH2 tank lights (400 watts) which will be
divided into two loads of approximately 200 watts each.
The tank and airlock lights will consist of 28 Vdc fluorescent
fixtures with an overall efficiency, including power converters, of approxi­
mately 40 lumens per watt. Each fixture will weigh approximately 2 pounds,
have a volume of approximately 50 cubic inches, and be sized between 10
to 40 watts, depending on the final lighting patterns required.
All lights are connected to the power buses through circuit
breakers. These circuit breakers can be used to turn the lights on and off.
Sensing of low voltage by a voltage detector will cause automatic transfer
of one airlock light and one LH2 tank light to the emergency bus. This
provides the astronauts with emergency lighting for return to airlock in
case of a power failure .
4-55

���BATTERY BANK

BATTERY BANK
NO. I

NO. 2

BATTERIES^ITO

BATTERIES'^!-20

A

TTf~S

-o o
CB-I

* i a •»
7DC0M

7DC0M
CB;£

r

+ 7D30

+ 7DIO
9

&lt;i

*• + - 7 D I O

CB-^&gt;

CB-5

T

Q

S + 7D30
")h

TYPICAL OF

LOAD

12 LOAD

CIRCUITS

s &amp; s
7D COM

FIGURE 4.4-2 POWER DISTRIBUTION

4-58

,_l

�taaoni am

4-59

�The requirement for light outside the airlock has not been
completely defined. Portable lighting, with a separate battery system,
will be included as required.
4.4.3 Control Panel
The control panel (Figure 4.4-4) mounted in the airlock unit,
consists of switches, circuit breakers, relays, meters, lights, and a
distribution system for operation and control of the electrical power sub­
system. This panel also provides for distribution of commands and
measurements between measurement equipment and electrical support
equipment (ESE) during preflight checkout. Visual displays include warning
lights, ammeters, a voltmeter, a pressure indicating meter, and a temperature meter. Five temperatures and five pressures may be individually
displayed through selector switches.
Power distribution will be accomplished by circuit breakers
as shown in Figure 4.4-2. Battery bank buses +7D10 and +7D30 are controlled
by two 100 ampere main circuit breakers (CB-2 and CB-3). A 100 ampere
battery tie circuit breaker (CB-1) may be used to interconnect battery banks
No. 1 and No. 2 should one of the main circuit breakers fail in the open
position. This will allow full utilization of all available power from the
batteries.
Each load may be switched to either of the two battery bank
buses by means of two separate circuit breakers (CB-4 and CB-5). This
provides the astronauts with manual on and off control of the equipment.
Failure of one of the switches in the closed position could be overcome by
using the main circuit breakers.
The four blowers and four heaters of the ECS are operated
through the control panel and controlled by separate circuit breakers.
The two suit oxygen heaters require 225 watts each, the LH 2 tank oxygen
heater requires 20 watts continuous, and the heater used to heat the airlock
oxygen each time the airlock is pressurized requires 450 watts.
4.4.4 Portable Display Panel
The display panel, Figure 4.4-5, is a portable unit for use
inside the S-1VB LH2 tank and is stored in the airlock. This unit contains
a temperature meter, a pressure meter, and a warning light. Four temp­
eratures and four pressures may be individually displayed through selector
switches. The warning light indicates the presence of emergency power.

4-60

�CURRENT

VOLTAGE

CURRENT

LOW VOLTAGE
DETECTOR

orr
" RC«T

COW VOLTAGE
DETECTOR

Vl

iusToit
Jmaw,
Sreakert

•US TOM

•US TO 50

sggmviTv
lo-jo"*;
BREAKE*

TEMPERATURE

BUS 7D30 LOAD BREAKERS

S-IVB FfcSSIVATlON
START TANK GHj
CONTROL H«
ENGNE CONTROL MB
VENT
LOX COLO Mt
/?~Ss
VENTS
/7_1_V\

PRESSURE

ENERGIZED

ENERGIZED

ENERGIZED

fVCSSlVATTOffREApy
CONNECTED CONCCTED L.
TO »US TDK) TO BUS TD50
AIRLOCK

'ARMED

AIRLOCK
•US 7010

FIGURE 4.4-4 |

CQNTRQl

pan£l

4-61

W

7Q|A|

|

��4.4.5 Cabling
Cabling consists of that necessary for interconnecting power
sources, the control panel, and the display panel with lighting, blowers,
measuring racks, sensors, and telemetry.
4.4.6 S-IVB Stage Passivation Subsystem
The passivation electrical subsystem consists of an arming
plug, manual control switches, and indicator lights which are located on the
airlock control panel. In addition, the system consists of a cable which
interfaces with various valves on the S-IVB stage. Existing stage circuitry
and sequencing will be used to vent residual lox and LH 2 from the propellant
tanks. The stage destruct system will be passivated by turning the destruct
system power off through an RF command from range control.
Premature activation of the S-IVB stage passivation subsystem
is prevented by removing an arming plug from the arm position which opens
circuits to all the valves. The arming plug will be installed in the arm
position during prelaunch checkout as required. The plug will be installed
in the safe position prior to liftoff. The astronaut will install the arming
plug in the arm position after S-IVB burn when the stage is ready for passi­
vation. The receptacle that arms the passivation subsystem will double
as prelaunch test points when the arming plug is removed.
Two indicator lights are provided on the diaplay panel. One
light indicates that the arming plug is installed and that the circuit breaker
supplying power from bus +7D10 is closed. The other light indicates that
the arming plug is installed and that the circuit breaker supplying power
from bus +7D30 is closed. The stage is ready for passivation when either
indicator light is illuminated. The redundant power source and circuit
breaker will be used only in the event of primary circuit failure. The
passivation system controlled from the airlock control panel uses approxi­
mately 14 amperes when all valves are energized.
The following three four-pole, double-throw switches control
components in the stage passivation subsystem:
1. Switch SI controls the start tank vent pilot valve, the
helium emergency control solenoid, and the cold helium dump valve.
2. Switch S2 controls the ambient helium dump valve.
4-63

�3. Switch S3 controls both APS No. 1 and APS No. 2 fuel tank
and oxidizer tank helium vent valves.
The operational procedure requires that valves controlled by
switch SI be activated before the remaining valves. To ensure adherence
to the operational procedure, switch covers must be removed from switches
S2 and S3 before they are actuated.
During checkout, each bottle to be dumped by the passivation
circuitry will be pressurized with pneumatics. The bottle dump valves
will then be energized from the airlock control panel. Observation of the
porting of gases from the bottle vents, and telemetry monitoring of the
bottle pressure decay, will be used to verify integrity of the passivation
circuitry. The S-IVB/ESE circuits in parallel with the passivation circuits
are to be isolated during functional testing of the passivation system.
4.4.7

Measurement and Instrumentation Subsystem

The F3 RF assembly is supplied 28 Vdc power by redundant
load buses through two circuit breakers. The circuit breakers will be
used to alternate load buses furnishing power to the RF assembly. The
circuit breaker supplying power from the +7D10 battery bank bus is closed
on the ground prior to liftoff. During checkout, power to the RF assembly
is inhibited by ESE control during periods of RF silence.
The F3 IM assembly, the 5 Vdc power supply, and two measuring
racks are supplied power through another set of circuit breakers and through
an inhibit relay. Power is supplied to these components in the same manner
as that supplied to the F3 RF assembly.
The remaining three measuring racks are supplied power through
another set of circuit breakers. Power is supplied to these racks by two
circuit breakers which alternate the battery bank buses that supply power.
There are no inhibit relays in the power supply circuit to the three measuring
racks. The three measuring racks will be turned on as required for checkout
and after the system is in orbit.
The 5 Vdc power supply furnishes 5 Vdc to the F3 TM assembly,
all measuring racks, and 11 pressure measurements. Nine measurements,
specified in the instrumentation program and components list, are capable
of being switched by ESE controlled relays from telemetry to ESE via hard­
wire for checkout.
4-64

�Certain critical measurements are paralleled to telemetry and
to the control panel. Measurements routed to the control panel are monitored
visually.
4.4.8 Interface Requirements
Marshall Space Flight Center will control the following electrical
interfaces in addition to the Saturn IB launch vehicle interfaces:
1. Airlock to spacecraft.
2. Airlock to S-IVB stage (passivation).
3. Airlock to IU (RF output to IU antennas).
4. Airlock to ESE (utilize connection No. 14 of IU/ESE interface
control document).
4.4.9 Electrical Support Equipment
The Electrical Support Equipment (ESE) will provide means of
controlling and monitoring the on-board equipment as required during the
checkout and launch up to the time of umbilical separation. Insofar as
possible the SSESM ESE will be separate from the existing ESE and facilities,
to minimize interfacing problems and the resulting impact on the existing
contractor supplied ESE. System documentation will be an inhouse effort.
The following is a list of the required new hardware and the
source of procurement:
1. SSESM Control and Monitor Panel - This panel will contain
the necessary lights, meters, switches, etc. as required. This panel will
be designed, documented, and procured as an inhouse effort.
2. SSESM Distributor - This distributor will contain the relay
logic and patching necessary for the system. The basic hardware already
exists as surplus from other programs and will only require that the necessary
documentation and patching be accomplished inhouse.
3. 15 Amp Power Supply in AGCS - At the present time there is
an existing spare module available in the Saturn IB ESE at KSC. It is proposed
to utilize this module. This will require an interface change with the resulting
change in the documentation supplied by G . E . .
4-65

�• OEE-6 Recording - The existing Saturn IB system has the
capacity to accept the additional requirements. This will require an inter­
face change with the resulting change in the documentation supplied by G.E..
4

5. KSC. Strip Chart Recording - KSC must make available the
necessary recording facilities. Assuming that the KSC facility has the small
number ol spares that will be required then this will only mean changing the
interface control document (Figure 4.4-6).
6- Interior Cables - A total of 6 interior type cables will be
required and these will be supplied inhouse. It is planned that cables of
the correct type and length can be found as surplus for a portion of these
cables.
7. Facility Cables - One 60c cable from the LCC to the AGCS
must be made available by KSC. One 60c cable from the AGCS terminal
distributor up the tower to the I.U. umbilical level must be made available
by KSC. One 60c cable across the swing arm to the I.U. umbilical must
be built. These cables have been supplied by KSC in the past and it is
anticipated that KSC would supply this.
It is planned that only one set of the above equipment will be
built. This set will be supplied in time for checkout of the SSESM and
that the ESE will then be shipped to KSC for the checkout or launch. The
necessary facility power, cables, and recording equipment will be supplied
inhouse.

4-66

�ELECTRICAL SUPPORT EQUIPMENT INTERFACE CONTROL DOCUMENT
FIGURE 4.4-6
I.U. UMBILICAL
PLATE

60C SHIELDED

KSC

EXISTING ESE
15 A
POWER
MODULE

DEE-6
(RECORDING
ONLY)

MSFC
SSESM
CONTROL &amp;
MONITOR
PANEL

FACILITY
T. D.

SSESM
DISTR.

FACILITY
T.D.

MSFC

MSFC
an MSFC
ZZ»These cables will be supplied by MSFC
These cables will be made available by KSC
4-67

/ ^ \ These cables must be built by KSC

�4. 5

INSTRUMENTATION AND COMMUNICATION SYSTEM
4.5.1

Approach

The primary function of the SSESM instrumentation system is to
acquire and present "housekeeping" date to the astronauts and to ground
personnel. The term "housekeeping" data includes airlock. ECS. electrical,
and other parameters. In addition, the basic system has expansion capabili­
ties to accept and transmit data from inflight experiments. The system
concept was developed using the following guidelines:
1. System components must be flight-proven, off-the-shelf items.
2. Minimum interface with existing stage instrumentation systems.
3. Low cost.
A PAM FM/FM Telemetry System was selected to utilize its large
opacity for slow (12 sps) sampled data and capability for continuous data if
required for experiments. The measuring rack concept was used to provide
maximum flexibility in changing the system to meet additional requirements.
4.5.2 System Description
The instrumentation system is comprised of previously flight
qualified Saturn components shown in Figure 4.5-1. All major components
of the instrumentation system are located on available IU mountings. The
IU antennas will be utilised if the SLA panels are folded back so that they
do not interfere with RF transmission; otherwise, separate SSESM antennas
will have to be mounted on the forward end of the airlock.
The purposes of the on-board instrumentation are to provide:
condition.

1. On-board displays to the astronaut to determine SSESM

2. Data regarding the operation of on-board systems and experi­
ments for real-time and postflight analysis.

systems.

3. Data prior to launch which is used for checkout of the SSESM

4-68

��Based on the guideline to use flight qualified hardware wherever
possible, it is recommended that Gemini or Apollo voice systems be utilized.
The following requirements for voice communication are visualized:
1. SSESM and/or command module to EVA.
2. SSESM to command module.
3. Within SSESM and LH 2 tank.
The present MSFC guidelines does not include requirement for
television. In order to minimize training time, it is recommended that any
film camera coverage utilize (and MSC furnish) cameras that the astronauts
are familiar with.
4.5.3 Component Descriptions
1 he major components are described in the following paragraphs
and a detailed parts list is included in the Appendix.
TM Oscillator Assembly (Figure 4.5-2) - The FM Telemeter
converts analog measurement signals into proportional frequency-intelligent
signals for subsequent modulation of an FM transmitter. All input signals
are 0 Vdc to 5 Vdc range. Input signals come to the FM Telemeter from
transducers, measurement racks, and the Model 270 multiplexer. The FM
Telemeter (model C-l) can accept a total of 15 signal inputs, including the
Model 2/D multiplexer. The Telemeter weighs 17.5 pounds, has a power
input of 30 watts, and its dimensions are 12.0x6.8x4.8 inches.
R . I - . A s s e m b l y ( F i g u r e 4 . 5 - 3 ) - The transmitter accepts frequencyintelligent data from the frequency modulation telemeter. The unit contains
dc-to-dc converter circuitry to produce regulated power for the transmitter and
power amplifier subassemblies. The incoming signal is first applied to the
solid-state transmitter assembly. The output carrier from the transmitter
subassembly is then processed through the power amplifier and lowpass output
filter. The carrier has a power of 22 watts and a deviation of 125 kHz. The
R.F. assembly weighs 15 pounds, has a power output of 225 watts, and its
dimensions are 128 x 10.5 x 3.5 inches.
TM Multiplexer Model 270 (Figure 4.5-4) - The Model 270 is a
two-stage multiplexer that sequentially monitors many input signals, and
4-70

�°O.

3

l i g S
A

UJ
IT

X I- UJ

&lt;oo

X
HO2
H X

I

I

S§l

o
&gt;_1

OJ
-1
UJ
z
z

X
UJ
X
CE
&lt;
o

CO
2
LU
CO
CO
&lt;

X X
IO UJ
O

X
o
H
&lt;

_J 5
&lt;
UJ
z &lt; ZJ

_J
_J
&lt; CD O
X —5 CO
O CO
o

z " r:
&lt; m ^
X
o CO°

q:

o

co
B
TO

H
&lt;

o

CO
0-

&lt; 3

O &lt;

IS £j

£2
&gt;

z
o
l&lt;
X
m
_i
&lt;
o

z
o

y-

&gt;&lt;
_i
UJ

X _l
CO UJ
X

h*

o

-S&lt;

CN

CO

&lt;

X
O UJ
O yo X
1- UJ
&gt;

o z
o

O o

X

IO

o3

X
&lt; X
H (g C\J

X
o
co 2 &lt;
3t-X
CD _ CD
2—
JOJ
&lt;X&lt;

CO _ |-

O U- O

_l

UJ

&lt;

X
CJ

&lt;

a

4-71

o

+ &lt;

&gt;-

&lt; &lt;

X

35

CO O
CM Z

O
CO

2

co

UJ
CO

co

o
U.

�3
CL

H
U. ZD

or o

N

CD
CD
&lt;
Q_

&lt;

2 QZ
7 UJ
UJ H

o

|-

O

_1

O 2 UL
_l &lt;

CD

CVJ CD

in
OJ

QZ
O UJ
o LiJ
O
f- &gt;

r
±j _J

i.
•

Q. &lt;

° 1

&lt;/)
CO

£
m
2
UJ
CO CO
lOI CO
&lt;
UJ
S u3 o:

o

1 fc

O
Q
_
O
1-

QZ
UJ
H
QZ
LLl
&gt;

p-

^ O
Q o

U_
—r—
—L&gt;

TRANSMITTER

u. tr

&lt;O
6S

CO
CVJ

io
^5

UJ
CD
CD

— LL.

4-72

UJ
l—
UJ
2
UJ
-j
UJ
h-

�SCO
70 KC
+30%

MIXER
AMP.

o
Q-

o
N

—L

C\J
Q
O

o
2
y
&lt;0

o
•o
&gt;

UJ
&lt;
o:
l.
ce
*
o

o
-J

u

10

CO
_J
UJ
z
z
&lt;
X
o
o
to

CO
_i
UJ
z
z
&lt;
i
o
rO
CM

X
UJ
X
zH
&lt; a.
2b

3
2

1&lt;
n
UJ
1
a.
£ 5
o &lt;
H 0)
X
O
&lt;
UJ
—J

o
UJ
\

CO
UJ
z
ho
CM

LL.

o
CO
-J
UJ
z
z
&lt;
X
o
*

A

*

CO
_l
UJ
z
z

&lt;

X
o
to

o
o
IO
N

a:
LU
X
LU
_l
Q_
H
_l
3

fa:
UJ
X
UJ
_l
0.
r_J
3
2
CD
3
(/&gt;

lO
X
3
2
1
CD
3
(O

tr
III
CL
&lt;/)

X
o
&lt;
UJ
UJ

v
3 A
I I I 3 Ui &lt;
z 2
z X
|
z z z o
&lt;1
X &lt; X 2
o o 2 O &lt;/)

b UJ
&lt; to

d

Pi
UJ ^
LLl

Li.

X I
2 I£ N

N

£
O {O a.
a. pJ y
3 CVI 5

X
*7
cvi

£
o
Q

4-73

�produces two parallel repeating pulse trains, with each pulse a sample of
an input signal (PAM). Tlie input signals must be preconditioned to a range
of 0 to 5 Vdc.
Tlie Model 270 is basically a 30-channel component. Channels
1 through 27 of these 30 primary channels are data channels, 28 is the frame
ill- ntifit nion channel, and 29 and 30 are amplitude reference channels.
Pt iniary channels I through 23 can be sub-multiplexed with 10 subchannels
i a&gt; h. This gives the Model 270 the capability of accepting 23 x 10 + 4 or
234 different measurements. Channels 29 and 30 carry a precise 5 Vdc
relerence level and are bridged together to form a constant amplitude and
location reference.
Primary channels 1 through 30 are repeatedly monitored in
sequence. One complete sequence constitutes a frame. Primary channels
1 through 23 each introduce a different subchannel into the frame for 10
consecutive frames. These 10 frames are a master frame. Primary
channel 28 is held to a zero output level except during frame 10, when a
s \ &lt;ic level is inserted. This change in reference level provides master
frame identification. One master frame is necessary to sample all 234
inputs to the Model 270. When commanded from an external source, the
Model 270 will perform a calibration sequence. Upon receipt of a calibrate
i ommand, the internal calibrator generates a 5-step series of precise
voltages at levels of 0 Vdc, 1.25 Vdc, 2.50 Vdc, 3.75 Vdc, and 5 Vdc.
At the start of the next master frame, each step is applied for the duration
"i one masti r frame (83.3 milliseconds). These stepped voltages are
applied to the output isolation amplifier and replace the pulse train from
the main multiplexer that is normally routed through the isolation amplifier.
n inhibit calibration signal from the sync circuit stops the calibration
during channels 28, 29, and 30, allowing the frame identification pulses
r " pass. After the live master frames of calibration the circuit is reset
and is ready for the next calibration command.
Measuring Rack (Figure 4.5-5) - The purpose of each Measuring
Rack is to house the channel selectors and signal conditioning modules. Each
Measuring Rack contains two channel selectors, plug-in slots for 20 signal
conditioning modules, and the wiring necessary to route the electrical signals
to these modules.
Any of the several types of signal conditioning modules can be
used in any of the Measuring Rack channel slots. Each slot is furnished
the same complement of power, signal, and command wiring. Each signal
4-74

�UJ
5 Z
UJ o
X ^

3H
3

V)

&lt; FFL

&lt;
&lt;r

UJ Z
2 H
O«
H Q

to
3

O
to OJ
-1 _

to
_l o
—

zx
&lt;E
i H-

z ^
&lt; i-

c\j
oX

O cvj

_—t

&lt;

3

o
CO o
_J CVJ to
UJ 3 H

A

-J

3
O

&lt;

Z

UJ 3
Z ?

UJ
Z 3

z en 3
zX a
h3
X
o CVJ O
&lt; H

O CVJ O

(D
&lt;
a

_L
UJ

z
z
&lt;
X

o

u
2
2
&lt;
X
C

z

o
I—

o

UJ

z
z
&lt;
X

o
O
_L

cD to
UJ
XO

cs o
x 2

*
o
&lt;
a:

IT
3o
UJ tz
z
&lt; _J
I UJ
o CO

o

E

z&gt;

0)

&lt;
UJ
m

I

1/5

UJ

&gt;a:
UJ

2

UJ to

01 UJ
3 O

2 to cr

o &lt;3
a: UJ O
u_ 2 to

UJ
H

CD

2

cC

a.
A.
3
to
&gt;
in

E&gt;

&lt; O X

3
^3
— to ^

IR

o

O
UJ
UJ ID &lt; CJ _J
to 2 UJ &lt; UJ
UJ 3 2 a: to

to
UJ
to
to

4-75

a:
3
C9

U.

�conditioning module is wired to accept its required signals. The weight
is JI pounds, size is 13 x 9.8 x 6.5 inches, and the power input is 60 watts.
Telemeter Calibrator (Figure 4.5-6) - A simplified calibrator
will be used for manual calibration of the telemetry system by the astronaut.
•'•3.4 Instrumentation Program and Components List Summary
The housekeeping measurement estimates are:
1. Temperature

30

2. Pressure

11

3. Flow

1

4. Vibration

5

5. Events

9

6. Voltage

4

7. Current

3

8. Acoustics

2

The spare capacity of the instrumentation system which may be used
to support onboard experiments is as follows:
1. Signal Conditioned Measurements - 55 signal conditioning slots
available.
2. Assuming Maximum Commutation
a. Telemetry channels at 12SPS
b. Telemetry channels at 120SPS
c. Telemetry channels continuous (FM/FM)

4-76

170
4
15

��4.6

GROUND SUPPORT EQUIPMENT

Described here are the mechanical support equipment, gox provisioning,
and umbilical requirements. Electrical support equipment is defined in
paragraph 4.4.
4.6.1

Mechanical Support Equipment
1. Access Levels Provided by Existing Equipment

a. Station 441.0 (See Figures 4.6-1 and 4.6-2) - Model
DSV-4B-402, Access Kit, Vertical Forward Interstage, gives 360° access.
This is the lower level of the 402 access kit.
b. Station 477.0 - Model DSV-4B-402, Access Kit, Vertical
Forward Interstage, has the capability of providing 360° access. This is
the second or upper level of the 402 access kit.
c-

Station 525.0 (See Figures 4.6-1 and 4.6-3) - The SA/LEM
internal platform (lower) provides access for checkout of the O spheres. The
access provided by the platform sections at this level is dependent on the
airlock orientation.
d. Station 603.0 (See Figures 4.6-1 and 4.6-4) - The H14176 platform (NAA) gives 360° access at this level. The airlock structure
interferes with three platform sections. Modification of these sections or
complete removal will be necessary to give complete or partial access.
e-

Station 639. 0 - The auxiliary platform section of the
H14-176 platforms (NAA) give partial access at position + Y. Interference
with the airlock structure occurs at this level, but minor modifications can
eliminate this interference.
f. Station 660. 5 - The auxiliary platform section at this
level provides partial access at position -Y.
g- Station 697.5 (See Figures 4.6-1 and 4.6-5) - The second
major level of the H14-176 platform gives access to the forward end of the
airlock unit.
2. Ladders Provided
a. Station 441.0 to 525.0 (3 provided)
4-78

�b. Station 525.0 to 603 . 0 (1 provided)
c. Station 603 . 0 to 639.0 (1 provided)
d. Station 603.0 to 660.5 (1 provided)
e. Station 638.5 to 697.0 (1 provided)
3. Access Door Locations (center line and size of doors)
a. Instrument unit (IU) area, station 485.5. The access door
size is 32.89W X 32.5L (REF).
b. LEM Area (2 provided):
(1) Position + Z, station 634.88, 34.0W X 34. 0L (REF)
(2) Position - Z, station 634.88, 28.0W X 34.0L (REF)
4. Handling Equipment Required
a. Handling Sequence - is described in the separate Appendix.
b. Airlock Handling Equipment (See Figure 4.6-6) - The assembly
of the airlock unit within the LEM Adapter will be performed at Kennedy Space
Center (KSC). Investigation into the possibility of using handling equipment and
tooling that was used in manufacturing for the assembly of the unit and handling
at KSC will be conducted after manufacturing procedures and requirements have
been defined.
c. Component Handling Equipment (See Figure 4.6-7) - The
batteries for the airlock unit will be installed during the last day of the count­
down sequence. Transportation from the storage to the vehicle, handling
fixtures for lifting, and transportation inside the vehicle must be provided.
Two access doors are possible means of transferring the
batteries into the vehicle: One in the instrument unit area and the other in
the LEM area.
Existing dollies for battery transportation to the vehicle
will be utilized. These transporters are provided for S-IVB and IU battery
transport and the battery installation sequences would determine the
possibility of their use in transporting the airlock batteries.
4-79

�By entering through the access door in the IU area the
component hoist can be used and the hoist at the 603.0 level can be utilized
to transfer the batteries to the level of installation. This procedure can be
used only if a trap door is provided in the shield platform. By entering
through the access door in the LEM area they will be at the level of installation.
A mechanical hoisting unit must be provided for battery
installation. The points of installation, weight of the batteries, and the
criteria of the bulkhead protection study (D5-12802) required a mechanical
means of handling these components.
Fixtures must be provided for battery handling that are
compatible with the hoisting unit. Modifications to existing designs for the
S-1VB or IU battery fixtures may be possible.
4.6.2 Gox Provisioning
A gox supply at ambient (80°F) temperature is required for:
(1) fill of the four 3, 000 p.s.i. storage bottles; (2) 20 p.s.i.g. leak check;
and (3) vent capability to 5 p.s.i.g. for flight.
4.6.3 Umbilical Requirements
Quick disconnect couplings are required to service the gox
spheres and the airlock. Present requirements indicate a 3/4-inch coupling
will be required to purge and pressurize the gox spheres and two 1/2-inch
coupling for the airlock purge, pressurization, and vent system. It is
assumed that couplings designed and qualified on the Saturn V umbilical
program will be adequate for these requirements.
Drag on lines with manual connections will be utilized to service
the experiment with disconnect accomplished manually sometime prior to
launch. Since there will not be an umbilical plate to interface with the
Kennedy Space Center facility lines, a coordination effort will be required
to assure the proper lines are available to the quick disconnect couplings
to provide for manual connection and drag on.
The requirement exists for only one electrical umbilical connector
and this is presently planned to be met by utilizing the spare connector in the
instrument unit umbilical plate. A coordination effort will be required to
assure this requirement is met and the IU umbilical modified to include this
connector. Specific electrical support equipment requirements are discussed
in paragraph 4.4.
4-80

�4.6.4

Fluid Requirements (Figure 4.6-8)

Covered herein are the requirements for fluid to be transferred
from ground to checkout, activate, service, or operate the Spent Stage
Experiment subsystems. These requirements are given for media conditions
at the stage to ground equipment interface (i.e., at the interface of the
umbilical service line and the ground side of the umbilical disconnect).

4-81

�\
UNIT ROTATED 45° FOR CLARITY
4-82
FIGURE 4.6-1

4-Y

�PLATFORMS AT-

PLATFORMS AT
STA.44i

STA.477

-Y

SECTION A-A
3SO°

PLATFORM ACCESS AT

STATIONS 477 AND 441
FIGURE 4 . 6 - 2
4-83

�AIRLOCK

+Y

T-02 SPHERES (5 RECTO)
\ 3 LOCATIONS

SECTION B-B
PLATFORM ACCESS AT STA 525.&lt;
4-84

FIGURE 4.6-3

�I

SECTION C-C
PLATFORM ACCESS AT STATION 603.5
WITH LEVELS 639.0 AND 660.5 SHOWN
BY DASHED LINES

FIGURE 4.6-4
4-85

�TOP VIEW
AIRLOCK

Cy

SECTION D-D
PLATFORM ACCESS AT STA. 697.5

4-86

FIGURE 4.6-5

�FIGURE 4.6-6
4-87

AIRLOCK HANDLING EQUIPMENT

�COMPONENT HANDLING EQUIPMENT

VEHICLE
SKIN

BATTERY
HANDLING
CART

BATTERY
TRANSPORT
CA RT

°c oooo o

FIGURE 4.6-7 COMPONENT HANDLING EQUIPMENT
4-88

�CL -

:a r
X O 3
3- CO Q.

Leak Check is to be accomplished inl
conjunction with purge (Item 5)

&lt;

&lt;

&lt;

&lt;

2

z

z

2

Z

«;
00
3
k

.x
u
o3 83
v X
J U

£1
k k

03
03 S
h l
k k

83
DC
3H
3
k

o
03 V
8) J=
J O

Q
CQ
k

m
o3 _

«S

0)
03

TT
f*

to ~

£ £
S a
to •-

to —

c
c
— -C

c

* . •
- i
* •?

to
a:
a:
&lt;
2
u
a:

o a
l

§

S

£

c

z

s

1
u
3
o u
J &lt;

§ 2
U. (£•&gt;2
tfl U k
5 N &lt;
i

s

to
h
2
u
2
u
2
5
0
u

&gt;*
k
k
2
&lt;
D
O

J
&lt;
2
0
h
U
2

kP
2o

§

.

i"

x

® —

r .2p5 c
l i = i

16
E £
o i:
w

? § | i
•o — « 3

£
&lt;0 «
CO
&lt;u

*

I

i

2 x

?• « 2
« -2 c

•s s

' 5 ?
S ! '
, C3 T3

11

**

Sg
* .2.
J» °
^
C

&lt;

2

a.

S'
03 "O
03 83

-v

IH
3
cr
4/
»H
c
o

5 |
i

&lt;

x

03
-X
»rt
£
V
a
83
83
tO

c
3

O

Z

C—Y

£ £

2 o
•8 B
N J

0.
_
i
§
^

V

5

03
03
£

o 2 2"
- -O '•=
C »J
5 .2 «
•S 5 «
g-S u.
°*
t; ^
«&gt; in

•2 = ^ '3
^
M J2
CL 5 CL £

—'—C

0*
2
D

X

•°

.2

to
f~
2
b
u
er

•o
83

V

:

*3

£
Q» ?
C

M
i

l

i

ffl

^
05
»-

05

0
—

X

iC ^
2 8.
•o £

£

3
03
03
83
V"
Q.

y
C
83
00
o
&gt;•
U

X

0

— u
&gt; .2
^ s . i
o • •r x *o
2 «C 03
^.

-o

2

03
03 k
£2
k k

z

Q
CO
k

£ £
« ii
to «

I £
S2
to -•
•*

Q
tl
3
•

»&lt;
&lt;0
£
83
a
83
8)
to

8; £
« «
to K

•*

°r
&lt; -a 5
13
h
k
t

X

83
Q
CO
k
03

x

k
k
^k
&gt;

&lt;

X

•b
c
&gt;
o
u
a
a
&lt;

03
* ^

£ £
%

2 £ i
1 CO ^

DC

X
u
rC

« £
to a

Q
CO
k

o
CO
CO

X
03
2
o
CO

Q
CO
k

8&gt;
83
to

Q
CO
k

Q
CO
k

03
ot
03
« E
11 £
w K

Q
CO
k
U

l&gt;

U.
£ U
0 k
j &lt;
k a:

X
03
s
CO
(M

rt
X

V

2
OJ
ro
OJ

M

3
to

k
2 k
u •
k —

co
2
&lt;

CO
2
&lt;

to
to
U
a:
0.

x
f«
2
o
o
lT&gt;

x

x

2
o
o
lO

2
o
o
ir*

S fa
Q .U
w *w
2
k
10

u
0 I-

Pi
k

- H U J

rt

X
03
2
CO
CO
co

O
CO
+1
o
r-

o
CO

rt

x
cd
2
o
o
fC

•H
o
r-

o
S , &amp; cc
a U u O

3
to

CO
2
&lt;

CO
2
&lt;

o
CO
+1
o
r~

X
03
2
o
CJ

X
(D
2
o
CO

x"
&lt;«
2
m

a

o£ , «*

»-H
&lt;

°
*r

8 . 7
Q-u u
83 k k
I CO k
O 2 to

&lt;
k
J
to
k
a
u

E«

£
K 2
k O

!S^
I K
k ^

X u
O X
u u

X k
Oa
U k

CO

ro

Q
CO
k

Q
CO
k

.

S s S s
o 2 to o
'J
0
a
D
a.
to
k
a
k
1
a.
to
X
o
o

o

5
-i
[ii
cn
k

i a
k
W to
X k
o tf
O k

k
u

m

C3

&amp;u

U 2
X o. u «
o « a J
U 2 n l 3

X

7.

u
u:
s
j

g

g

3
£
&lt;

3
£
&lt;

lO

o

Z

r&gt;

^
p
u

X

D
k

w
s
Cd
C3S
•—*
o

g
k
2
O
to k
!S &lt;

z

0
k
&lt;

gl
O w
«1
&lt; k
r-

00
i
&lt;3

w
03
D
O
—

��SECTION V. MANUFACTURING AND QUALITY &amp; RELIABILITY ASSURANCE PLAN
5.1

MANUFACTURING PLAN

This manufacturing plan describes the proposed manufacturing sequence
of the Spent Stage Experiment Support Module (SSESM). The basic discussions
on the following pages include: (a) description of the general configuration of
the SSESM; (b) description of the basic fabrication and assembly procedures
for the canister portion of the module; (c) description of the fabrication and
assembly procedures for the module support structure; (d) description of the
assembly procedures for the canister; and (e) outline of the proposed assembly
and procedure required to assemble the SSESM.
5.1.1

General

Canister . (See Figures 5.1-1 and 5.1-4.) The canister is 65 inches
in diameter and approximately 204 inches long with vertical T-section stringers
riveted to milled lands on the outside of the skin panels for stiffness. Four
skin sections are required for the canister. Each skin section is comprised
of four skin segments. The two forward skin sections (No. 1 and No. 2) are
milled to provide 16 vertical stringers on the outside surface. The number
one skin section is approximately 51 inches wide and 45 inches long. The
number two skin section is approximately 51 inches wide and 50 inches long.
The number three skin section is composed of four skin segments approximately
51 inches wide and 68 inches long. Two of the skin segments will be mechanically
milled with vertical stringers and the remaining two skin segments will be
milled with vertical weld pads. The number four skin section will be composed
of four skin segments approximately 51 inches wide and 28 inches long and
will be of the same configuration as the skin segments for the number one
and number two skin sections. All skin segments will be contour formed
and age hardened in a simultaneous operation. Three I-beam shaped rings
will be spaced between the four skin sections and welded in place. The
forward end of the canister will be equipped to receive the CSM and will
have a sealed hatch for access to the CM. The aft end will have a bellows
assembly for attachment to the S-IVB workshop and will also have a sealed
hatch for access to the S-IVB spent stage. Also in the aft portion of the
canister will be an escape hatch for access to the LEM adapter area.
Module Support Structure . (See Figures 5.1-1 and 5.1-2.) The
module support structure consists of four tripod-style strut assemblies.
Each strut assembly consists of a vertical strut and two horizontal struts
with machined attach fittings. The vertical strut is manufactured from
aluminum alloy tubing which is approximately three inches in outside diameter
with a 1/4-inch thick wall. The two horizontal struts are manufactured from
5-1

�aluminum alloy I-beams which have three-inch wide flanges with a thickness
of 1/4-inch. Each of the four strut assemblies were assembled in an assembly
fixture.
5• 1 • 2

Typical Skin Section Fabrication and Assembly

Skin Segment Fabrication - The proposed procedure for the task
is as follows:
1. Locate plate material on skin mill; pull vacuum on plate
material using the skin mill vacuum chucks, locking the plate material in
place for milling.
2. Mill plate material to the required configuration.
3. Repeat operations for the three remaining skin segments.
4. Locate the milled skin segment on the age form fixture;
clamp the skin to the age form fixture, forming the skin to contour.
u , • 5 ' P u aCe t h e S k i n a n d a g e f o r m
form the skin to the required condition.

f i x t u r e in to

the autoclave; age

6. Repeat operations for the three remaining skin segments.
Skin Section Assembly - The proposed procedure for this task
is as follows:
1. Adjust the dimensions on all skin segments, allowing for weld
shrinkage to determine the amount of trim at the edge of each skin segment
and to enable the completed skin section to be welded to the I-beam and end
rings.
2. Position a 90-degree skin segment on air bearing blocks on
skin section assembly fixture.
3. Align the skin segment, pull vacuum, and lock in place.
4. Mount the router head on weld manipulator and make a vertical
cut on the right edge of the skin segment to the predetermined dimension.
5. Release and rotate the skin segment 90-degrees clockwise.
5-2

�-

��CO
i
in
CQ

cd
D

��6. Repeat similiar procedure to cut left edge of section.
7. Hoist the next 90-degree skin segment in place locating the
right edge of the skin segment against the skin segment already installed on
the weld fixture.
8. Pull vacuum and lock segment in place.
9. Release and rotate trimmed segment to facilitate cleaning.
10. Make a vertical cut on the right edge of the untrimmed skin
section.
11. Release and rotate segment to facilitate cleaning.
12. Clean the weld edges of the two skin segments by removing
the conversion coating, inside and outside.
13. Make three test welds on samples. Inspect and make
proper settings.
14. Locate the two skin segments for welding. Pull vacuum and
lock the skin segment in place.
15. Install the finger clamping device, tack weld the two skin
segments together, and remove the finger clamping device.
16. Tack weld tabs on top and bottom of the weld joint.
17. Automatically weld the two skin segments together.
18. Shave the weld bead to 0.015-inch high using the microshaver.
19. Release and rotate the segments 90 degrees clockwise and
remove weld tabs.
20. Repeat proceeding operations outlined above for each of the
two remaining 90-degree skin segments.
21. Repeat previous procedures in a similiar manner for the two
welded skin segments.
5-7

�22. Release and remove the skin section from the weld fixture.
23. Machine the top and bottom edges of the skin section parallel
and to the required length using router fixtures.
5.1.3 I-Beam Rings Fabrication
The three I-beam rings are utilized in the assembly of the canister
and are completely machined parts. The aft I-beam ring is machined to include
the aft bulkhead escape hatch fitting.
5.1.4

1'orward Bulkhead Section Fabrication and Assembly (See Figure 5.1-3)

Command Module Attach Ring Fabrication - The attach ring will
be machined complete from raw material that is 44 inches outside diameter
by seven inches thick by seven inches wide.
Bulkhead Center Fitting Ring Fabrication - The center fitting
ring will be machined complete from raw material that is 44 inches outside
diameter by seven inches thick by seven inches wide.
Bulkhead Outer Fitting Ring Fabrication - The outer fitting ring
will be machined complete from raw material that is 72 inches outside
diameter by seven inches thick by seven inches wide.
Bulkhead Skin Section Fabrication - The skin section will be
fabricated from plate material and formed to the required dimensions.
After forming, the skin material will be routed to the final dimensions.
Bulkhead Center Tunnel Fabrication - The center tunnel will be
fabricated from two pieces of plate material which will be formed to 30 inches
inside diameter. The two 180-degree cylinder halves will be vertically
welded together to form the 360-degree 30-inch inside diameter center tunnel.
The tunnel will then be trimmed to the required length.
Bulkhead Reinforcement Struts Fabrication - The reinforcement
struts attach between the center fitting ring and the outer fitting ring. The
raw material for the reinforcement struts will be sawed to the required length.
Forward Bulkhead Section Assembly - The proposed procedure
for this task is as follows:
5-8

�1. Position the outer fitting ring in place on the forward bulkhead
section assembly fixture and clamp in place.
2. Position the command module attach ring in place on the
assembly fixture and clamp to the center post of the assembly fixture.
3. Locate the skin section in place on the outer fitting ring and
the command module attach ring and clamp in place.
4. Weld the skin section to the outer fitting ring and to the
command module attach ring.
5. Locate the center tunnel in place on the command module
attach ring and clamp in place.
6. Weld the center tunnel to the command module attach ring.
7. Locate the center fitting ring in place on the aft end of the
center tunnel; clamp in place.
8. Weld the center fitting ring to the aft end of the center tunnel.
9. Locate the reinforcement struts in place between the center
fitting ring and the outer fitting ring; clamp in place.
10. Weld the reinforcement struts to the center fitting ring and
to the outer fitting ring.
NOTE: The forward escape hatch will be attached during
final assembly of the module.
11. Remove the forward bulkhead section from the assembly
fixture.
5.1.5

Aft Bulkhead Section Fabrication and Assembly. (See Figure 5,1-3)

Bellows Fabrication - The bellows will be a complete fabricated
procured item.
S-IVB Manhole Attach Ring Fabrication - The attach ring will be
machined to the required configuration from raw material.
5-9

�Aft Bulkhead Section Assembly - Following is the proposed
procedure for this task:

in place.

1. Locate bellows in place on the assembly fixture and clamp

2. Locate the attach ring in place on the aft end of the bellows
and clamp in place.
3. Drill required holes through the attach ring and bellows.
4. Remove the attach ring from the bellows.
5. Apply adhesive to the attach ring and bellows mating surfaces.
6. Relocate the attach ring in place on the bellows: attach with
the required attaching hardware.
7. Remove aft bulkhead section from the assembly fixture.
5 -'- 6

Module Support Structure Fabrication and Assembly ISee Figures
5.1-2 and 5.1-4)

Vertical Strut Fabrication - The vertical struts are fabricated from
aluminum alloy tubing which is approximately three inches in outside diameter
with a 1/4-inch thick wall. The struts will be sawed to the required length and
the attach ends are sawed to the required configuration for attachment to the
support structure fittings.
Horizontal Strut Fabrication - The horizontal struts are fabricated
from aluminum alloy I-beams which have three-inch wide flanges with a
thickness of 1/4-inch. The struts will be sawed to the required length and
the attach ends are sawed to the required configuration for attachment to the
support structure fittings.
Support Structure Attach Fitting Fabrication - The attach fittings
for the support structure will be machined complete from aluminum alloy forging.
Assembly of Strut Assemblies - The proposed procedure for this
task is as follows:
1. Locate four support structure attach fittings in place on the
positioning and holding fixture; clamp in place.
5-10

�2. Locate the two horizontal struts and the vertical strut in
place between the attach fittings on the positioning and holding fixtures.
3. Secure the horizontal and vertical struts to the attach fittings
with the required hardware.
4. Remove the strut assembly from the positioning and holding
fixture.
5. Repeat operations previously outlined for three remaining
strut assemblies.
Micro-Meteoroid Shield Fabrication - Four 90-degree sections
of honeycomb material will be utilized for the micro-meteoroid shield. The
lower skin, which will be 0.010-inch thick, will be placed in a bond form
fixture; the honeycomb material will then be placed onto the lower skin;
the adhesive and the upper skin will then be located in place. The entire
assembly will then be placed in the autoclave for bond forming. After bond
forming, the honeycomb panel (90-degree section) will be sawed to the
required dimensions.
5.1.7

Assembly of the Canister (See Figure 5.1-4)
The proposed assembly procedure is as follows:

1. Locate and secure the number two skin section in place on
the tooling ring of the turntable, with the aft end down.
2. Mechanically clean the top edge of the number two skin
section and the aft edge of the forward I-beam ring for welding.
3. Install a roundout ring-backup bar in the forward end of
the number two skin section.
4. Locate the forward I-beam ring in place on the number two
skin section and expand the roundout ring-backup bar against the I-beam ring
and number two skin section.
5. Prepare test weld samples and verify the weld settings before
each weld; analyze the results before proceeding.
6. Weld the I-beam ring and the number two skin section together.
5-11

�7. Repeat the preceeding operations outlined until the number
one, number three, and number four skin sections and the remaining two
I-beam rings are welded together and inspected.
NOTE: The vertical T-section stringers will be welded and
riveted to the lands on the skin sections during assembly of the module.
5.1.8

Module Assembly (See Figures 5.1-1 and 5.1-2)
The proposed assembly procedure is as follows:

1. Mechanically clean the forward end of the canister and the
aft end of the forward bulkhead outer fitting ring for welding.
2. Locate and clamp the forward bulkhead in place.
3. Weld the forward bulkhead to the forward end of the canister.
4. Locate the aft bulkhead in place. Apply adhesive and secure
the aft bulkhead (bellows and S-IVB manhole attach ring) to the aft end of the
canister.
5. Locate and clamp the four I-beam vertical struts in place
on the number three skin section of the canister.
6. Weld the I-beam vertical struts to the vertical weld lands
of the number three skin section.
7. Locate and clamp the vertical T-section stiffeners in place on
the milled lands of the canister.
8. Rivet the vertical T-section stiffeners to the milled lands of
the canister rivets.
9. Locate and clamp the four support structure strut assemblies
in place.
10. Weld the support structure fittings to the I-beam rings on
each end of the number three skin section.
11. Locate and clamp the four 90-degree honeycomb panels of
the micro-meteoroid shield in place on top of the horizontal struts of the module
support structure.
5-12

�12. Drill and ream the required holes through the honeycomb
panels and the horizontal struts and install the required hardware.
13. Locate the escape hatch (to the LEM adapter area) in place
on the number three skin section of the canister, lay out the opening, and
remove the escape hatch.
14. Lay out and saw the required opening in the number three
skin section for the escape hatch.
15. Install the sliding track for the escape hatch on the inside
of the canister.
16. Install the forward escape hatch in place on the forward
bulkhead section.
17. Install the aft escape hatch in place on the aft bulkhead
section.
18. Install the escape hatch in the opening in the number three
skin section of the canister.
19. Locate and attach the 21 batteries around the outside of the
canister between the first and second I-beam rings on the number two skin
section.
20. Locate and attach four 42-inch diameter oxygen bottles (two
each 180 degrees apart) on the outside of the number three skin section of
the canister.
21. Apply Alodine coating and paint the module in accordance with
the spacecraft color code.

5-13

�5.2

QUALITY AND RELIABILITY ASSURANCE PLAN
5.2.1 General

This plan describes those inspections, analyses, and tests planned
to provide maximum assurance of the acceptability of the SSESM.
5.2.2 Analyses and Inspection Operations
Source Control - Source control is required to assure the most
efficient interfacing of quality assurance testing operations performed by
vendors and MSFC. Contractual documents, work statements, etc., will be
reviewed for adequate quality requirements and source controls to be imposed
on the selected supplier. Generally, Government concern for control of
procurement sources will be described in one of the following documents:
NPC 200-2; NPC 200-3; NPC 250-1; others as called for by contract.
Receiving Inspection - Receiving analysis activities and require­
ments are to plan and perform effective receiving inspection, analysis, and
testing operations which will assure the degree of quality for all procured
items satisfactory for the purpose intended, and that only those materials
and items that meet the required standards and specifications are procured
and stocked for the SSESM. In order to assure the receipt of acceptable raw
material and hardware at MSFC, it is required that all such items intended
for the SSESM be routed through Receiving Inspection.
Articles shall not be accepted unless they are qualified or designated
for qualification. Hardware for the SSESM program will be qualified in accordance
with test requirements and schedules established by the contract. Facilities
and trained personnel for inspection and analysis are available and will be
committed to this program.
Specifically, the criteria to be applied to the various materials
include:
1. Structural shapes: dimensions, physical tests of samples,
composition, heat treatment, identification, and certification.
2. Plate and sheet metal: dimensions, physical test of samples,
composition, heat treatment, documentation submittal flatness, surface scratches,
protective coatings, identification.

5-14

�3. Pressure tubing: dimensions, roundness, concentricity,
surface (outer and inner) composition, physical properties, identification,
and certification.
4. Bellows: visual, cure date, dimensions of attaching surfaces,
identification, and certification.
5. Fasteners: visual, physical tests of samples, thread forms
and size, identification, and certification.
6. Machined and formed parts: dimensions, surface finish,
cracks, visual, identification and certification.
7. Pressure vessels: dimensions, certification, and other documen­
tation, identification, cleanliness, proof pressure, surface finish, protective
finish, location and dimensions of bosses and parts, and thread form and size.
Component and Subassembly Analysis - As previously noted in
planning material, the key to successful SSESM will be the individual
reliability of the functional components comprising the module's systems.
It is essential, therefore, that a most discriminating and demanding component
functional test be performed on all hardware prior to installation on the module.
Components shall be functionally tested in as near test mission environment as
practical. The Test and Training module and flight SA-209 module canister
assemblies will be leak tested following assembly. The Test and Training
module canister assembly will also be inspected and tested following structural
testing.
Mechanical Components Tests - The purpose of these tests is
to establish confidence in the ability of each component to perform satisfactorily
when incorporated into the module. It is therefore necessary to functionally
test these components in as near a mission mode as possible. The basic type
of tests shall include:
1. A visual inspection;
2. Cleanliness of components;
3. Components conformance to documentation;
4. Mark assembly data and cure date of oldest seal on component;
5. Check safety wiring, lubrication, and electrical connector pins;
5-15

�6. Check in instrumented electrical and mechanical test setup;
7. Operating pressure tests;
8. External leakage;
9. Internal leakage;
10. Valve operation.
Ii 1 ectrical/Electronic Component and Subsystem Functional
Testing - These tests and the selection, evaluation, maintenance and control
of the associated test equipment are discussed below:
1. Functional testing is necessary to insure that adequate manu­
facturing procedures were utilized to produce an acceptable component or
package. Performing functional vertification testing under simulated operating
conditions assures its ability to satisfy mission requirements.
2. Electrical functional tests shall be performed on all
electrical/electronic components and subsystem such as telemetry packages;
measuring devices consisting of AC and DC amplifiers; pressure and temper­
ature transducers; communication systems components; power supplies;
heaters; lights; blowers; and all other instrumentation components or sub­
systems that comprise the life support system, airlock system, docking
structure and complete experiment packages or systems as required.
3. The selection, evaluation, approval, maintenance and control
of the test equipment used for functional testing will be in accordance with
the requirements of NASA Quality Publication NPC-200-2, Section 9. Test
equipment will be an order of magnitude more accurate than the specified
tolerance on parameters it is measuring or providing.
Failure Analysis - The objectives of a failure investigation program
are to determine the specific cause and origin of the various failures that occur
to components and to eliminate further failures of the same or related natures.
A failure analysis will be conducted on all components that fail after assembly
to the module. Failure of components during receiving inspection and subsequent
bench functional tests will also require failure analysis when the failure indicates
a design or quality problem, the failure occurs to a critical component or involves
long lead time components, or failure of components has been experienced on
previous lots of a particular component. Components will be submitted for
failure investigation for any of the following conditions: (1) actual observance of
component failure; (2) suspicion of component failure with reasonable basis.
5-16

�A program is presently established to feed back information
and take corrective action on troubles, malfunctions, deficiencies, and
failures discovered during inspection and test at the plant, field site, etc.
Fabrication Analysis - These operations provide the mechanical
and electrical inspections and analysis to be performed during the various
fabrication and assembly operations on the SSESM. End items or intermediate
operations shall be subjected to the tests and inspections which are appropriate
to determine acceptability. In-process inspection shall only be used where
the quality of the part or operation cannot be verified by an end item inspection.
During fabrication all drawings, specifications, processes,
procedures, and integration analysis planning shall be reviewed continuously
in order to eliminate errors and omissions and improve efficiency without
compromising quality.
Sheet Metal or Machined Parts - A complete inspection of each
part such as the canister skin shall be performed. The item shall be
inspected for conformance to applicable drawings and specifications and
shall include: dimensional analyses, hardness tests, dye penetrant of
formed areas, surface finish, cleanliness, X-ray, and other non-destructive
testing.
Structural Fabrication - Major subassemblies including the
forward and aft bulkheads and canister assembly shall be inspected to
include dimensional analysis, rivets and fasteners for proper installation,
interference fit holes for proper diameter prior to insertion, physical
appearance and surface finish, alignment, and status compliance to applicable
drawings and specifications.
Welding - Preparation for the welding on the canister assembly
and other welded structures will be in accordance with standard procedures
and must be inspected prior to commencing the welding operation. Test
specimens of the type of joint to be welded will be made prior to the welding
operation. Strength tests and bead analyses will be performed, and failure
to meet the minimum requirements of any specimen will be cause for
recommending production welding not to take place. Upon successful
completion of the specified tests an inspection tests report containing the
essential information will be completed and signed by the quality control
representative.
5-17

�All welds will be radiographically inspected. Examination
of welds will demonstrate that the inspection technique positively establishes
the defects. Where radiographic inspection is determined to be inconclusive,
ultrasonics, etch, and dye-penetrant shall be used. Visual inspection of all
welds will be made.
Cabling and Trunking - All cabling and trunking shall be inspected
for compliance to applicable documentation and proper functioning. These
inspections shall include visual inspection of the completed assembly for proper
length, lacing and ties, connector condition, hy-ring installation, shield breakout,
cable size, ground wire installation and potting or molding. Functional tests
shall be made of each cable, trunk, J-box to include continuity, leakage between
pins, and insulation resistance.
Electrical Connectors - All connectors attached by methods
such as potting and molding or crimping shall be inspected for proper
assembly. A visual inspection shall be made of each crimped connector
for damage of conductor or terminal, proper gap, deformation, tarnish,
proper pin taper, broken strands and functional insertion capability.
A visual inspection of potted connectors shall be performed for appearance,
surface condition, bond integrity, and alignment of contracts.
Cleaning - Rigid tubing, flexible hose assemblies, containers,
components, and SSESM pressure bottles shall be inspected to MSFC specifi­
cations for cleanliness by monitoring the operation, recording and analyzing
operational data, and by laboratory analyses of samples pulled from the
operation. A visual inspection shall be performed on completed items.
Assembled SSESM Analysis - The assembled module analysis
shall be accomplished immediately following completion of assembly. This
analysis consists of a series of nonfunctional analytical operations that are
performed to assure the delivery of an end item conforming to design require­
ments. Additionally, these operations establish the base line status of the
module and are prerequisite to the module functional test.
All Spent Stage Experiment Support Modules will be subjected
to the assembled module analysis. The test and training article will be
examined closely for damage resulting from structural and vibration testing.
The Zero g" mockup will only undergo an examination of sufficient depth to
assure completeness and astronaut safety.

5-18

�Electrical Installation Analysis - This operation will:
(1) Ascertain that all cables have been installed, routed, tied, and laced
in accordance with applicable installation drawings, and applicable require­
ments; (2) verify that all cable and connector reference designation markers
are legible and correspond with reference designation markers on mating
component connectors; (3) verify that all electrical components have been
installed as specified; (4) verify that grounding methods used are in accordance
with the installation drawings and applicable provisions.
Module Electrical Systems Continuity/Compatibility Tests Continuity/compatibility testing of electrical/electronic systems utilized
in the airlock, environmental control, experimental and life support systems
shall be performed to meet test parameters specified by design and/or quality
assurance requirements.
Torque Verification - The torque values of all pressure system
connections utilizing gaskets will be checked. Pressure system connections
utilizing a metal-to-metal contact will be checked following any major structural
movement resulting from transportation, attitude change, or structural test.
All types of bolted connections having metal-to-metal contact will be checked
at least once after the initial installation. Connections utilizing gaskets must
be checked at scheduled intervals.
Component Identification - Age control of individual elastic
type parts will be maintained by verifying that the cure data limits are
not exceeded.
Pressure System Continuity - All tubing (including pneumatic,
hydraulic, propellant systems, etc.) will be traced from end to end to
assure that the system is properly installed and to determine if tubing
and/or components have been damaged during or subsequent to installation.
Weighing - The complete assembly will be weighed by a
single suspension load cell at the time of removal from the assembly fixture
and after experiments have been installed. Electronic load cells will be of
tension type and all operations will meet the basic requirements presented
in procedure 6-OH-MA-5A. A weight log will be initiated following completion
of the weighing operation. Weighing will require a maximum of one day.
Preparation of Shipment - Upon successful completion of checkout
and tests at MSFC, the SSESM shall be prepared for shipment. The preparation
for shipment shall be monitored and a final visual inspection performed to verify
that the SSESM has been properly prepared for shipment to the test site.
5-19

�Receiving Inspection at Vacuum Facility and KSC - Personnel
shall be sent to the vacuum facility and KSC to perform receiving inspection
and damage assessment of the SSESM and to witness unloading and preparation
for the transfer of the SSESM to the vacuum chamber and launch site. Status
information and test results gathered during fabrication, assembly, and check­
out at MSFC shall be consolidated and transmitted to the vacuum facility and
KSC test personnel prior to receipt of the SSESM itself.
Pressure Functional Analysis - The objective of performing the
following pressure and functional tests on the mechanical systems of the
support module is to assure the integrity and functional capability of the
mechanical systems. The checkout shall be an opeia tional test performed
r
in :» nrpcciirr&gt; /*4 &gt;I I
. '",TeSt l° ver'fy pressure switch operation, leak test at system
pressure, check for internal and external leakage, verily actuation and
deactuatlng pressure settings, and make a break repeatability of the switches.
CheCk minimum Pressure required for component
oner-Hor
' uT
operation and relief settings of high pressure regulator and system relief
In adf,t,0n' che&lt;* resP°nse
f

and repeatability of component
operation, test system and components at normal system operating pressure,
and repeatability of control component.
h f ri a' A Ieakif,heck ofaI1 lines' fittings, and connections shall be
conducted under a suitable test pressure using lead detector solution or
tracer gas as applicable.
4. A support module functional analysis will be performed whereby
pressure chambers are attached to each end of the module and side hatch, and
the pressure differentials established sequentially in each module chamber to
simulate operation in the space environment.
5. Heaters - apply power and cycle each unit three times
measuring voltage, amperage, actuations-deactuations.
Environmental Checkout and Analysis in a Vacuum Chamber Following the ambient analyses described above at MSFC, the SSESM will be
shipped to a suitable man-rated vacuum chamber. A man shall enter the
chamber and perform a complete functional and operational check of all
mechanical and electromechanical systems including access hatches.
5-20

�5.2.3 Systems Electrical Checkout
A comprehensive checkout program will be performed to verify
satisfactory operation of the individual systems or subsystems, and to
ensure that no problems result from interaction of the systems. Test
operations will incorporate fail-safe provisions which assure return to
a safe condition in the event of power failure or other emergency. The
tests are summarized below.
Power Distribution Tests - These tests will verify the proper
control and distribution of electrical power in the SSESM. Bus resistance
measurements will be made prior to application of power, and the independence
of the busses will be checked. Redundant circuitry will be verified, where
possible.
Component Functional Tests - These tests will verify the
operation of all controlled components from the instrument panels. In
addition, the various inteface functions - S-IVB, CSM, and GSE, will be
checked. Among the components tested are the gox Dump Valves, the
acquisition light, the airlock lights, the oxygen heaters, the tank lights,
the blowers, and the display panel.
Measuring System Tests - These tests are performed to verify
the calibration of all transducers and signal conditioners on the SSESM and
to assure conformance to proper channel assignments. In all practicable
cases, the systems will be operated of stimulated for every flight measurement.
Telemetry System Tests - These tests will determine that the
telemetry system operates in compliance with applicable specifications while
installed in the SSESM and controlled by its electrical networks. Calibration
of sub-carrier oscillators will be checked and adjusted as necessary.
Experiment Tests - These tests will be conducted primarily to
verify the interface between the experiments and the SSESM systems. These
tests may include power distribution, operation of the experiment or portions
thereof, and retrieval of experiment data through the SSESM telemetry systems.
Electromagnetic Compatibility (EMC) Tests - These tests will
essentially parallel other testing operations and will determine if all electrical,
electronic, and electromechanical systems and subsystems will operate, both
individually and simultaneously, without degraded performance due to EMC.
5-21

�5.2.4

Facilities

Facilities and inspection stations presently exist that would
provide adequate space for performing all tests and inspections except as
required for vacuum chamber testing.
5.2.5 Schedule
A schedule is presented in Figure 5.2-1 summarizing the
operations associated with the Quality and Reliability Assurance Plan.

5-22

���SECTION VI. RESOURCES AND SCHEDULES
6.1

RESOURCE REQUIREMENTS

This section defines the resources required by MSFC to design,
fabricate and test the SSESM design described in this proposal. All
MSFC manpower required for the SSESM will be available within the
current manpower allotments of the organizations involved, with assign­
ments being made within each area of responsibility as required to
support the proposed effort. As the project status advances to include
systems and operational support, it is planned that personnel partici­
pation will increase and the additional manpower required will be
phased in from existing personnel.
The resources requirements peak during the following phases:
Tool fabrication, parts fabrication, and structural assembly, which
all occur during the 2nd and 3rd quarters of FY-67; manpower require­
ments will extend into the 3rd and 4th quarters of FY-68 for the purpose
of reduction of flight data and mission reporting.
The total material cost of the proposed SSESM is $3, 275, 000.
This cost includes:
1. Mechanical GSE.
2. Installation Hardware and Testing.
3. Structural Components for Testing.
4. Vibration and Acoustical Test.
5. Sphere Development.
6. LSS Components Development.
7. ECS for Test and Flight Article.
8. Experiment Installation.
9. Electrical Power System.
10. Control Panels.
6-1

�11. Integration of Experiments.
12. Modification of Existing Consoles, Distributors.
13. Electrical Simulators for CSM and S-IVB.
14. Miscellaneous Cables and Break-In Boxes.
15. Weight and Alignment Tooling.
16. Handling and Pressure Test Fixtures.
17. Hardware for Mock-up, Test Article, and Flight Article.
The hardware cost of the zero-g mock-up is $87.5K, the test article
is $138K, and the flight article is $138K. The test article is identical to the
flight article except for some qualified hardware.
The material cost for an additional flight article would be $743, 000.
This cost includes:
1. Hardware for Flight Article.
2. Environmental Control System.
3. Electrical Power System.
4. Life Support Equipment.
5. Integration of Experiments.
These costs do not include experiment procurement.
Refer to the following tables and figures for a further breakdown of the
resource requirements:
1. Table 6.1-1 - Resource Requirements by Laboratory
2. Table 6.1-2 - Resource Requirements by Article and Function
3. Figure 6.1-1 - Manpower Requirements
4. Figure 6.1-2 - Material Requirements

�a)
i—i
o

•r&lt; O
&gt; O
&lt; °-

•s&amp;
•u

r-t (n
aj
C

o

O
O

-a
U r-C
•H

o

X) o
&lt; 3

u

o
o

4J

nJ
^
-u
c
&gt; o
^ U
a&gt;
oj
o

(0

_ qj .
M

-rJ &gt;

O
a. aj
a. *-&gt;
3

« *
-=

I
I
I
I

I
I
I
I

51
U CO 2
I
I
I
I

CO CJ H S,
• •
C_

U W

6-3

�z
o

uQ
Z
&lt;3

w
j
CJ
•—I
&lt;N
I
•o
W
J
CQ
&lt;
h

fe
&lt;

&gt;&lt;
cn
w

W
2
w
eS

5

6
taS
w
W
u
OS
D

8
w

6-4

�6-5

�CI

&lt;y.
co
eg

co
vo

evO

u~l
O
ro

vO
vO

N
I

O

o
o
o
e-&gt;

O
O
O
eg

o
o
o

H3
£
c

tSHVTIOa 10

£

SONVSflOEL

fi-6

�6.2

SCHEDULE

This section defines the overall schedule for design, fabrication, and
test of the three SSESM hardware articles to be delivered by the MSFC.
Detail manufacturing and quality assurance functions are scheduled for the
Flight Article, the Test and Training Article, and the Zero "g" Mockup.
In addition, the major technical functions are scheduled defining also the
documentation release dates and subsystems delivery dates. These items
are shown in Figure 6.2-1.
The schedule shown reflects an April 1, 1966, initiation date and a
December 1, 1967, ship date for the first flight article allowing for flight
on AS-209 in early 1968. This schedule has been implemented and all
aspects are on schedule as of June 1, 1966. Effort is continuing to main­
tain this schedule to assure the capability for delivery as AS-209 flight
article. Additional flight articles can be provided on a timely basis to
meet anticipated flight schedules.

6-7

��SECTION VII. MANAGEMENT PLAN
7.1

SCOPE

This section briefly outlines the major management functions and
organizational interfaces involved with the development of the SSESM.
These interfaces are shown in the function chart, Figure 7.1-1. It shows
how MSFC will maintain control of the various SSESM activities.
7.2

MANAGEMENT RESPONSIBILITIES

MSFC will maintain overall responsibility for the design, fabrication,
and assembly, and test of the SSESM. These activities would be in addition
to the MSFC responsibility for the overall planning, systems design, and
integration for the S-IVB Spent Stage Experiment. Overall MSFC responsi­
bility for the SSESM development will be vested in the Industrial Operations
(10) Saturn/Apollo Applications Office (S/AA). However, the actual development
will be accomplished by the various Research &amp; Development Operations
(R&amp;DO) Laboratories through a technical control element responsible to
the Director, R&amp;DO.
The S/AA Office will be responsible for overall funding and scheduling
for the S-IVB Spent Stage Experiment. The office will also be responsible
for all inter-Center and NASA Headquarters management interfaces. The
S/AA Office will relay funding and overall direction applicable to the develop­
ment of the SSESM to the designated technical control element representing
R&amp;DO. This technical control element will exercise technical and resources
management for the SSESM development among the various R&amp;DO Laboratories.
This element will also establish and maintain the funding distribution,
schedules, and technical interfaces.
Normal technical interfaces among the three involved Centers will
be handled through the existing Apollo Interface Panels. Specific MSFC
technical data requirements on the procurement of Gemini or Apollo
components will be submitted to the applicable MSC program office through
the MSFC S/AA Office.
7.3

FUNCTIONAL RESPONSIBILITIES

Design, development, and manufacturing of the SSESM will be accom­
plished within the MSFC R&amp;DO Laboratories. Identification of the overall
7-1

�ssvt oa^a

•SXD3H &gt;8 DNIdNna
S3DVJH31MI- -loVr'

�functional responsibilities among the various laboratories is shown on
Table 7.2-1. Each area has been further subdivided into the various
sub-element tasks. These tasks are then assigned through the normal
organizational arrangement: Division, Branch, and Section. Experienced
technical and management personnel are available at all these levels to
accomplish these tasks, and additional technical Laboratories and
Divisions are available to support this program in specific technical
areas as requirements develop.

7-3

�TABLE 7.2-1
MSFC LABORATORY FUNCTIONAL RESPONSIBILITIES

PROPULSION &amp; VEHICLE ENGINEERING LABORATORY
1. Vehicle Systems Division: Systems engineering
2. Structures Division: Structural design
3. Propulsion Division: Environmental control subsystem
4. Materials Division: Adaptation and selection of materials
AERO-ASTRODYNAMICS LABORATORY
1. Dynamic &amp; 1-lighi Mechanics Division: Flight mechanics and
dynamics analyses
2. Flight Test Analysis Division: Flight evaluation
ASTRIONICS LABORATORY
1 • Instrumentation &amp;• Communications Division: TM instrumentation
and communication; voice communication

2. Electrical Systems Integration Division: Electrical systems
(power, networks, control panels); electrical support equipment; lighting
system design
MANUFACTURING ENGINEERING LABORATORY
1. Planning and Tool Division: Tool planning, design and processing;
planning and processing of integration effort.
2. Manufacturing Development Division: Module and tooling manufacture;
experiment integration.
3. Industrial Support Branch: Component procurement.

7-4

�TABLE 7.2-1 (Cont'd.)

TEST LABORATORY
1. Components and Subsystems Division: Operation of altitude chamber.
2-

Control and Instrumentation Division: Special instrumentation
development.
QUALITY &amp; RELIABILITY LABORATORY
1. Source control and receiving and inspection.
2. Fabrication analysis.
3. In process inspection.
4. Assembled SSESM checkout.
5. End item assembly analysis.
6. Component and subassembly checkout.
7. Failure effects analysis.

7-5

��SECTION VIII. ALTERNATE DESIGNS AND SYSTEM FLEXIBILITY
8.1

GENERAL

The basic SSESM design proposed has, as previously described,
substantial capabilities for supporting crew and experiments for up to a
20-day mission. To maintain simplicity and low program cost this approach
requires no major interfaces with the CSM and consequently makes no
provisions for extending the CSM life time beyond its inherent capability.
The basic design does lend itself to alternate approaches, flexibility for
growth, sophistication and flexibility for mission extension. These
adaptations can be accomplished by several methods and in all instances
utilize the nucleus of the basic design. The alternate designs, with pre­
dominate emphasis upon ECS and fuel cell reactant storage alternates, are
discussed in the following paragraphs.
8.2

30-DAY SYSTEM CONCEPT
8.2.1

Approach

This design approach, proposed by MSC, constitutes supply
fuel cell reactants and life support oxygen to the CSM by a fluid umbilical
attached to the CSM service umbilical, and primary electrical energy
furnished to the SSESM power distribution system from the CSM. Elimination
of primary power sources on the SSESM permits the installation of cryogenic
containers. The required umbilical attachments would be accomplished by EVA.
8 . 2 . 2 ECS
As previously noted and implied the "slug" ECS concept is
proposed on the 20-day concept for reasons which include the following:
1.
2.
3.
4.
5.
6.

209 schedule adherence;
Low costs;
Simplicity;
Reliability;
Minimum hardware with maximum utility of available components;
Weight capability permits non-optimized approach.

However, extended missions deem the slug leakage contaminate control concept
to be excessively weight penalizing for desirable astronaut lab occupancy
schedules. A comparison of an atmospheric revitalization system with the
8-1

�slug approach, shown in Figure 8.2-1 determines a respective weight
requirement of 575 and 1950 pounds for an astronaut occupancy cycle of
4/11 hours. A similar comparison for the 20-day system shown in
Figure 8.2-2 shows the slug to be acceptably competitive for the shorter
mission. The 1375 pound weight penalty for 30 days is considered excessive
thereby establishing the need for atmospheric revitalization. Existing
flight equipment such as the Gemini ECS suit loop module would be employed.
This module would be stripped of excess equipment and would serve only to
remove CO2 from the Lab/airlock volume. The heat exchanger normally
used for water vapor removal would be inactive due to the absence of
SSESM active coolant loops. The silica gel concept of H2O removal used
on the 20-day concept would remain.
8.2.3 Electrical Power System
Changes to the basic 20-day SSESM power system design will
involve the removal of most batteries which now supply power to the SSESM.
The remaining batteries will be used to satisfy telemetry requirements from
liftoff to docking and emergency power source requirements during orbit.
The retained batteries will provide power for operation of the motor-driven
switch and the SM umbilical separation circuits without sending control power
through the CM/SSESM interface. The SM umbilical separation circuits may
be operated directly through a modified SSESM control panel utilizing SSESM
battery power (see Figure 8.2-3).
8.2.4 Cryogenic Storage
For the extended mission the life capability of the cryogenic
vessel becomes a formidable concern. Analyses were performed to determine
the amount of cryogen remaining in the 14-day Gemini RSS vessels at various
mission periods. These vessels were initially considered primarily due to
potential spare/test equipment availability. As can be observed in Figure 8.2-4,
relief venting causes the stored mass to decrease quite rapidly although mission
duration was initiated with a one atmosphere ullage pressure. The hydrogen
vessel shows a maximum mission capability of 20 days obviously establishing
the need for potential solution investigation. These potential solutions include:
1.
2.
3.
4.
5.

Flow management between the CSM and SSESM;
Radiation shields;
Boil-off shields;
Slush;
Improved cryogenic insulation for storage vessel.
8-2

�5000-

FIGURE 8 . 2 - 1

ATMOSPHERIC REVIT ALIZATION VS.
SLUG CONCEPT-30 DAY MISSION

8-3

�2500 -

OCCUPANCY

FIGURE 8.2-2

SCHEDULE (hrs Sr./tors out)

ATMOSPHERIC REVIT ALIZATION VS.
SLUG CONCEPT-20 DAY MISSION
8-4

�8-5

�Boil-off shields would comprise series connection of vents
from each vessel terminated into a jacket placed around each container.
This approach inclusive of slush utilization would offer the maximum
extension of Gemini vessels. Since high use rate periods require use
of CSM vessel heaters, the omission of this heater use and pressure
feeding from the SSESM tanks could offer meaningful extension. The
use of CSM tanks rather than Gemini is to be studied; however, this is
not expected to offer satisfactory solution. The CSM tank affords
considerable (factor of 3 for LH9) heat leak reduction by the employment
of demand flow dependent vapor cooled shields. Should these or other
promising solutions be inadequate, MSFC proposes application of current
development on cryogenic insulated vessels to meet the 30-day mission
requirement.
An inhouse MSFC super insolation development program for
prolonged storage exists and could be applied to the SSESM. A potential
flight configured 105-inch diameter LH2 tank has been designed, manu­
factured, and tested with a potentially applicable super insulation system.
Propellant evaporation rate was less than 2-1/2% per day during the
simulated space vacuum test inclusive of support heat leak. The insulation
system successfully demonstrated is the NRC helium purged system. This
experience affords MSFC the capability of developing inhouse with minimum
cost the required SSESM cryogenic tankage.
8 . 2 . 5 Design Summary
This design would utilize the same configuration and structural
design as the MSFC basic design with local modifications which would provide
for attachment of cryogen bottles, and the environmental control assembly.
The proposed electrical power distribution system would be used with little
or no modifications depending on the power levels and voltage control. Most
of the 21 batteries would be removed. The instrumentation system would be
supplemented to provide monitor and control for the additional cryogen
storage system and environmental control components. The telemetry system
and on-board voice system would remain unchanged. The PLSS storage system
would be retained with additional 02 in the container. The gaseous oxygen
storage for pressurization of the LH2 tank would most likely be retained with
the elimination of two gox tanks.
This approach would have a major impact on the schedule and
significant impact on the resource requirements. The prime advantage of
this approach is the potential mission duration without resupply. Additional
8-6

�MISSION DURATION

(DAYS)

20 H
KYDRCGZN
P = 250 ps;3
V = 5 AS ft 3

SPEC

o

o.

10

20
MISSION DURATION

30
(DAYS)

FIGURE 8.2-4 CRYOGENIC MASS VS. MISSION TIME
FOR GEMINI 14-DAY RSS CONTAINERS
8-7

�studies, cognizant of schedule requirements, would be conducted on a
cryogenic storage system. The CSM electrical power availability, the
need for cryogenic servicing established by fuel cell reactants, and
schedule relaxation deems the cryogenic storage of life support O2 to
be more feasible. Also, the use of life support oxygen from the cryogenic
storage would be re-evaluated because of: the availablility of CSM power;
cryogenic servicing would be available because of fuel cell reactant require­
ments; and the schedule relaxation.
8.3

14-DAY CSM DEPENDENT SYSTEM

The supply of electrical energy by the CSM to the SSESM but without
SSESM fuel cell reactant storage would afford an approach similar to the
described MSFC 20-day concept. Mission life time is paced by the CSM
cryogenic storage system and is within a 10 to 20-day period dependent upon
power profile. Supplementary batteries would be maintained on the SSESM
to handle peak power loading and to supplement power as required for minor
adjustments in mission duration. An electrical umbilical, Figure 8.2-3,
from the CSM to the SSESM would be added and minor modifications might
be required to the SSESM power distribution network for voltage control
compatibility. All other systems on the basic 20-day SSESM design proposed
would remain unchanged.
The major advantage of this design is the additional weight available
for corollary experiments which is gained by deleting a number of the
batteries. The disadvantages include a probable shortening of the mission
duration, a significant interface with the CSM, and potential impact on the AS-209
schedule contingent upon design choice establishment date. The resource require­
ments are projected as comparable with the basic design proposed, being
decreased by the deletion of some batteries and being increased by the develop­
ment of the electrical umbilical and CSM modification.
8.4

REUSABLE SYSTEMS

The 10-20 day CSM dependent concept eliminates the CSM/SSESM
cryogenic dependence and incorporates SSESM/CSM electrical dependence.
The difference for reuse comprises the resupply or initial additional gaseous
oxygen storage needed for a subsequent CSM/workshop link-up. Removal of
the batteries, as required in the design, would permit more initial gaseous
oxygen storage; these vessels to be used for the second use period would be
isolated from use by burst diaphrams, thereby, circumventing leakage detection.
8-8

�Resupply techniques require study but could include effective replacement
of the SSESM by a version of the SSESM containing gaseous oxygen vessels,
logistics furnishings, and a CM docking probe on the lower section. This
approach at resupply would also be applicable to the basic 20-day design
proposal.
8.5

20-DAY SYSTEM GROWTH FLEXIBILITY

For more significant extension of mission capability, the basic 20-day
SSESM could accept the Gemini ECS suit loop module as add-on equipment.
Full time occupancy of the Lab could be realized in addition to reduction of
02 leakage from 30 lb/day to values dictated by leakage prevention techniques.
The basic SSESM design could also accept a power system sophistication
such as supplementary power and recharge capability from the addition of
solar cells. The use of fuel cells to replace the battery system would be
feasible without the loss of a development effort since the proposed batteries
are readily available components. This would, however, require the purchase
and integration of fuel cells and a cryogenic storage system. Significant
resource and schedule impacts are anticipated with the inclusion of any of
these items on the initial design; however, it is expected that resources would
be the only major obstacle for subsequent missions.

8-9

����</text>
                  </elementText>
                </elementTextContainer>
              </element>
            </elementContainer>
          </elementSet>
        </elementSetContainer>
      </file>
    </fileContainer>
    <collection collectionId="199">
      <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="213262">
                  <text>Richard Heckman 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="213679">
                <text>sdsp_skyl_000054</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="213680">
                <text>"SPENT STAGE EXPERIMENT SUPPORT MODULE PROPOSAL."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="213681">
                <text>United States. National Aeronautics and Space Administration</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="213682">
                <text>1966-06-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="213683">
                <text>1965-1970</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="213684">
                <text>George C. Marshall Space Flight Center</text>
              </elementText>
              <elementText elementTextId="213685">
                <text>Skylab Program</text>
              </elementText>
              <elementText elementTextId="213686">
                <text>Apollo applications program</text>
              </elementText>
              <elementText elementTextId="213687">
                <text>Spent Stage Workshop</text>
              </elementText>
              <elementText elementTextId="213688">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="213689">
                <text>Experimentation</text>
              </elementText>
              <elementText elementTextId="213690">
                <text>Space habitats</text>
              </elementText>
              <elementText elementTextId="213691">
                <text>Airlock modules</text>
              </elementText>
              <elementText elementTextId="213692">
                <text>Multiple docking adapters</text>
              </elementText>
              <elementText elementTextId="213693">
                <text>Life support systems</text>
              </elementText>
              <elementText elementTextId="213694">
                <text>Extravehicular mobility units</text>
              </elementText>
              <elementText elementTextId="213695">
                <text>Human factors in engineering design</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="213696">
                <text>Reports</text>
              </elementText>
              <elementText elementTextId="213697">
                <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="213698">
                <text>Richard Heckman Collection</text>
              </elementText>
              <elementText elementTextId="213699">
                <text>Box 1, Folder 12</text>
              </elementText>
              <elementText elementTextId="215959">
                <text>University of Alabama in Huntsville Archives and Special Collections, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="213700">
                <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="213701">
                <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="213702">
                <text>Skylab Document Scanning Project Metadata</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="22">
        <name>Skylab 50th Anniversary</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="14405" public="1" featured="0">
    <fileContainer>
      <file fileId="10954">
        <src>https://digitalprojects.uah.edu/files/original/20/14405/sdsp_skyl_000070_001.pdf</src>
        <authentication>6f3336e8a030ae106ffaa691253d0a67</authentication>
        <elementSetContainer>
          <elementSet elementSetId="6">
            <name>PDF Text</name>
            <description/>
            <elementContainer>
              <element elementId="101">
                <name>Text</name>
                <description/>
                <elementTextContainer>
                  <elementText elementTextId="215907">
                    <text>n

SPER^Y RAI\D
EARTH ORBITAL WORKSHOP
CAPABILITIES BROCHURE

SPACE SUPPORT
DIVISION

���=6=

^SPER^Y RAfSD

SECTION I
INTRODUCTION

SPACE SUPPORT DIVISION

�I
I

Hm
•I

.

I
I1
I

I

I

�INTRODUCTION
The Sperry Rand Space Support Division presents t h i s brochure t o depict
a competence and capability in the area of

large earth-orbita I workshops.

Workshops that are:
®

In

fabrication (ATM)

•

Proposed

for Saturn V Vehicles (B0 6

• Conceptually designed
(Nuclear Power)

for specific advanced applications

Sperry's ability to offer a depth of

experience in the orbital workshop

area is directly attributable to the technical
Division is
technical

Mx)

support the Space Support

p r o v i d i n g t o t h e MSFC A s t r i o n i c s L a b o r a t o r y .

In this role a

foundation and competence in design and deveIopment of

orbital

workshops has been established. The Apollo Telescope Mount provided the
hardware, subsystem and system experience. Then

follow-on studies developed

the necessary mission analysis experience. Hence, an overall
capability has evolved.
The areas of demonstrated proficiency are:
I.

EXPERIMENTATION
X-Ray Telescope Design
X-Ray Camera Design
Television System Design
Laser Research

I I .

POWER
Solar Array Design
Nucleonics Analysis
Fuel Cell Design

I I I .

COMMUNICATIONS
Data Compression Studies
Information Coding Techniques Studies
Modulation Techniques Studies
Phase lock Loop Analysis
Phase Compensat ion Analysis
Hardware Design
Antenna Systems
Pulse Code Modulated Data Acquisition Systems
Telemetry Ground Station

i

workshop

��270-ChanneI

Multiplexer

Single Side Band Double Side Band Filters
Airborne Telemetry Pouier Supplies
IV.

CONTROL
Control Moment Gyro System Analysis
Experiment Pointing Control Analysis
Control

System Analysis and Design

ATM
Orbital Workshop
Reaction Control

Jets

Sizing
Fuel Consumption
Momentum Dumping
Optimal
Backup
Star Tracker Anulysis
A summary of
ience

the engineering effort related to orbital workshop exper­

is presented in the Capabilities

tion there are

four

Section (Section

II). In that sec­

s u b s e c t i o n s w h i c h a r e u n i q u e l y c a t e g o r i z e d by NASA's

Phased Project Planning. The

four steps of

Phased Project Planning are

Advanced Studies, Project Definition, Design. and DeueIopment and Ope­
rations Categorized as Phase A. B. C and D respectiueIy.
The remainder of

the brochure

provides an insight

background, organization makeup and manpower

into the Division's

level.

The capabilities reported herein were developed by the Space Support
Division under Contract NAS8-20055 t o the National
Administration. George C. Marshall
oratory. Huntsv i I le . Alabama.

Aeronautics and Space

Space Flight Center. Astrionics Lab­

����II.

WORKSHOP CAPABILITIES SUMMARY
TABLE OF CONTENTS

Phase

Page

A

Advanced Studies

2-1

B

Project Definition

2-0

C

Design

2-/5

0

Deuelopment and Operations

2-23

iu

��WORKSHOP CAPABILITIES SUMMARY

PHASE A - ADVANCED STUDIES
In the Advanced Study Phase concept
mission approaches are made. Requirements

feasibility studies of

for each are analyzed, engineer­

ing assessed and exper iment programs grossly defined.
written detailing all

various

From t h i s a report

analytical work, alternate solutions, tradeoff

is

cri­

teria and recommendations.
The Phase A definition adequate I y defines the work
Space Support Division's Advanced
onics

Studies Group

Laboratory's Advanced Studies Office.

performed by the

in support of

the Astri-

The recent studies as docu­

mented by Sperry are:
/I S t u d y o f
Eq u i p m e n t s '

the Backup Saturn I Workshops

Potential

(AS2I0 Wet

Launch) Astr ionic

for use in an Austere Dry Launch Saturn V IVorbshop (B)

An investigation into the system and sub-system modifications required
t o ad a p t t h e S a t u r n I

u

Wet Launch" workshop's backup eauipment to an aus­

tere Saturn V "Dry Launch" workshop was

performed. Convers ion time, cost

and mission scheduling were traded off against versatiIity and

l i f t capa­

bility.
SP 590-0132

Completion date:

Selected Studies of

9/68

Some Conceptual Earth-OrbitaI Workshops

Systems analysis and trade-off

studies were made on a number of

con­

ceptual earth-orbital workshops in an effort t o size systems and obtain the
best configuration. Areas studied
tems.

included experiment payload,

instrumentation and communications, thermal

power sys­

controls, control and

display, and video imaging.
SP 590-0098

Completion date:

Attitude Control

System Synthesis

for Conceptual

7/68

Saturn V

Launched

Earth-Orbita I Workshop/Space Stations
Identified Eight Conceptual Workshop/Space Station configurations and
studied

in detail

four t o determine overall

attitude control

requirements

to be expected. Then, using these requirements two potential attitude con­
trol

systems are synthesized.

2-1

��General concepts were derived

from NASA's current Saturn V Earth-Orbital

Workshop/Space Station planning a c t i v i t i e s .
Disturbance torques considered are gravity gradient, aerodynamic, solar,
magnetic and man motion. The c o n t r o l
jets, control

systems

included reaction control

moment gyros and various combinations of both.

SP 590-0097

7 68

Completion date:

Microwave Power Transmission Study for Space Applications
Considered the feasibility of transmission of

power by microwave beaming

from a master s a t e l l i t e t o one or more smaller s a t e l l i t e s . Theoretical
quantitative results are presented detailing the efficiency of

and

each sub­

system plus total system efficiency using either the e l l i p t i c or the para­
bolic reflector antenna.
SP 590-0072

Completion date:

4/68

Signal-to-Noise Considerations for Orbiting Astronomical
Presented data that helps provide fundamental

X-Ray Telescope

information on establish­

ment of c r i t e r i a t o postulate on the temperature, density and composition
of matter

in the galactic and intergaI act i c space, presence and strength

of magnetic and electric fields in space, the origin and distribution of
cosmic rays and the creation of matter.
SP 599-0110

Completion date:

8 68

Large Aperture Telescope: Phase I , 2 , 3 . 4 and Summary
Performed control

system analysis on suggested high accuracy

large

aperture telescopes. The studies were confined t o the fine pointing control
cf

a one meter diameter

large aperture telescope mounted on an SIVB type

orbital workshop. The pointing accuracy of

the systems analyzed

is 0.01

arc second maintained for extended periods of time.
A two body analog simulation was developed t o t e s t the various hardware
configurations and evaluate the effects of disturbances,
motion, on pointing accuracy.
SP 5 9 0 - 0 0 3 4 - 0 . I . 2 . 3 . 4

Completion date:

2 - 3

including man

5/68

�H—
O
C
&lt;3

n.
E

—

- —.

*—

*S.
E

3
U
CN
3

&lt;/L

T3

&lt;3
L.

3%
3&gt;
L.
CM
C

1

X
3*

-a
"«3
TU

E

E

L.
O

I—
O O
M—. 4a

E

"3
CM
V*
3

H—.
O

CM
TCM

A

E

&lt;3

B

V*

&lt;3

3&gt;
3
U

T3

4a

3&gt;
«-

3

Ci.
C

»—

c o
CM o
o
•&gt;
c
o «/-&gt;

•—

CN

4* ——
3 N—w
3 CM
&lt;/»
a.
o
L. o
-C CM
3* —
&lt;M
% 4a

2-4

�Phased Array Antenna Study - Phase
A comprehensive study of

I and

II

the characteristics of

phased arrays was per­

formed. State-of-the-art information is presented

from the literature on

weight, s i z e . gain, number of elements, scan and efficiency. Also detailed
is the pattern effect due to radiator mis location caused by manufacturing
errors and thermal

gradients.

SP 590-0108

Completion date:

8 68

SP 590-0134

Completion date:

9/68

Boom Extended Nuclear (Orbiting) Reactor Control
In suggesting nuclear reactors
of

vehicle control

came t o the

for

Study

large space stations the question

forefront. This

study endeavers

to answer

that question by considering the reactor mounted on a boom extended
the side or end of

from

the vehicle.

An investigation into the

i n t e r r e l a t i o n s between the boom mounted re­

actor and the vehicle control

system was

performed. Analog and Digital

s imulation programs were developed t o compute external disturbance torques,
composite mass and

inertia data.

In addition, a complete two-body vehicle

dynamic simulation containing a vehicle control
verify analytical

system was developed t o

results.

SP 209-01

Completion date:

An investigat ion of
Sensors
S trapdown inertial
stations of

the

12/68

Redundancy Concepts Applied to Strapdown

navigators appear to have a place

in large

put with the mean output of

trade-offs

&lt;aturn

sensor out­

all the sensors.

program was developed t o study various approaches and evaluate

in the detection and isolation of

SP 590-C084

Mod i f i e d

space

future. A study input, t o system development, was a method

to detect and isolate defective sensors by comparing individual

A digital

Inertial

sensor ma I f u n c t i o n s .

Completion date:
IV

Six Degree Dynamical

Simulations with

7/68
Iterative Guidance

for Advanced Vehicles and Missions

Strap-on solid

fuel e n g i n e s .

and variable thrust liquid

Saturn V vehicles without the SI I stage

fuel engines are analyzed to determine impact on

��the

present guidance modes.

veloped utilizing the

Full

scale digital

simulations haue been de­

l a t e s t MARVESS t r a j e c t o r y techniques making l i f t - o f f

to injection studies possible.
SP 209-TD-04

Completion date:

I

69

��W O R K S H O P C A P A B I L I T I E S SUMMARY

PHASE 8 - PROJECT DEFINITION
In the project defin i t ion phase selected concepts are refined, assess­
ments o f t o t a l miss ion requirements are made and a system analysis

prepared.

From the study results presented a project plan emerges which specifies a
single concept,

recommends a plan for

phase C and presents a preliminary

Project DeueIopment Plan.
The Sperry Rand Space Support Diuision by supporting the Astrionics
Laboratory on the Apollo Telescope Mount Vehicle (ATM) was an integral

part

of t h e ATM Phase B endeauor. T h i s produced e x p e r i e n c e by a s s o c i a t i o n w h i c h ,
in our opinion, gives a depth of

knowledge

in the area of

large orbital

space station technology obtainable only by day-to-day contact with the
cognizant NASA o r g a n i z a t i o n s . A sampling of r e p o r t s a p p l i c a b l e t o the phase
B planning process

is presented below.

Antenna Pattern Measurements
Analyzed three methods of measuring antenna patterns in relation t o the
antenna attitude

in a 200 nautical m i l e o r b i t . The study was made t o e v a l ­

uate a c o n t r a c t o r ' s proposal t o NASA f o r measuring the c h a r a c t e r i s t i c s of a
large space erectable parabolic antenna. Comparison studies were conducted
and recommendat ions submitted f o r the most accurate method of

measuring

antenna patterns.
RL # 16-022
Discussion of

Completion date:

5/66

t h e Torque R e c t i f i c a t i o n Dump Scheme

Scrutinized contractor's proposal

f o r a g r a v i t y gradient dump scheme

designed f o r momentum r e l i e f of the Control Moment Gyros. The scheme u t i ­
lized the rectification of the c y c l i c gravity gradient torques by changing
signs of

the commanded maneuver angles a t specified times

in the orbit.

T h e a t t r a c t i v e a n d u n a t t r a c t i v e f e a t u r e s o f t h e s c h e m e urns p r e s e n t e d
a f t e r a detailed analytical and computer simulation study was performed.
OWS-2-1

Completion date:

Double Gimbal Control Moment Gryos
The System for

4/67

in Vehicle Attitude Control

I n e r t i a l Experiment P o i n t i n g a n d A t t i t u d e C o n t r o l

PAC) os proposed by NASA (Langley F i e l d , V i r g i n i a )

2-9

is investigated.

(OIX-

�T3
CD

+-»

3
3&gt;
3
o

CD
CD
-3
*-•

3
O
•a
3
vt

CD
3
3"

!_

O

cn
3
i"3
CJ

—

E
3
3
31
"3
O
l_
CD
3
O

+-

CD
3
"3

•

cu
——

o

*—

-C
3
o&gt;
a.
3&gt;
4-»
—N
K«
4-*
C
3
O
CL
o
O

CD «/»
3l cu
3
3
•C K—
u
O
E ——
3 —
o
3 n.
CD •s:
E
Q ~
E a
L.
3

—

3

c

2-10

o
«/»
*—

X
a

�The

fundamentals of

the equations

t h e CMG s y s t e m are

for a space v e h i c l e using t h e SIXPAC conf iguration is devel­

oped. Along with this a block diagram of
developed

presented and the derivation of
t h e CMG a n d u e h i c l e d y n a m i c s a r e

for system study.

The characterist ics of

t h e CMG a s a n a t t i t u d e c o n t r o l d e v i c e a r e a l s o

discussed and a comparison with other attitude control
Then advantages of

the various systems are

SP 517-67-1

schemes

is made.

presented in cone I usion.

Completion date:

1/67

Charaer-batteru Regulator Module - Prototupe Test Model
4n engineering a n a l y s i s was
for the thermal, mechanical

performed to establish design requirements

and vibration prototype of

battery - regu I ator -modu I e . The

packaging design required compliance with

MSFC Document 50M02408. E n v i r o n m e n t a l
teria

t h e ATM c h a r g e r -

Design and Qualification Test Cri­

f o r ATM C o m p o n e n t s . T h e t h e r m a l

and vibrational

analysis of

the

prototype charger-battery regulator was conducted t o v e r i f y the packaging
design per requirements of

50M02408.

RF # 10-004

Completion date:

Generation of

Orbital

7/68

Coordinate Systems and Aerodunamic and Gravitu

Gradient Torques
T o e v a l u a t e and c o n f i r m t h e ATM c o n t r o l
face a detailed soft mockup of

system configuration and

inter­

the vehicle pointing and control system was

deve loped.
The developed
earth orbital

program

presents a complete MathematicaI

Model

space station. The Earth-sun-sate 11ite motion model

lated along with all

external

of

an

is simu­

torques acting on the vehicle. The control

system containing control moment gyros and reaction
making i t possible to do detailed

jets is also simulated

fuel studies of any earth orbital

control

system. Presently this simulation

digital

and 8900 hybrid computers.

SP 522-0058

is

vehicle

programmed on both the 7094

Completed:

4/67

Updated:

4/68

ATM Command a n d T e l e m e t r y A n t e n n a s
Originated the design concept and
types of

ATM a n t e n n a s .

fabricated scale models and

proto­

The antennas are mounted on t h e solar wings. An

edge-mounted scimitar antenna was used

2 - II

for t h e 450 MHz command s y s t e m and

�Q_
O
O
v»
&lt;u
—1•
KQ
—•

O
SL
"t

UJ

a
&lt;
£E

O

&gt;H

&gt;
&lt;

cr
o

C
a
L_
o
H—.
E
3
4-»
C
E
o
E
c
a
4-*
3
v»
u
•3
C
a

3

cu
3
3Lo
4-»

Q

+-»

z

- •—

o
o
OJ

800

400

0

UJ

3

C
cu

T3
&lt;3
L.
&lt;S&gt;

»

UJ

Z

o

/
o

UJ
CO

_

i x

+-

•
a
t- 01
w&gt; ——

« -e
e &lt;u
u a
&lt;U
+- &lt;u
X a.
&lt;11 a
*-&gt;

y

—

-—s,

*

o s—

o
o

o
o

to

o
o
ID

03S-13W-M3N

13W-M3N

2-/2

ut +-&gt;
H- C
Q 3
O
a.

�an edge-mounted dipole antenna
was

for t h e VHF t e l e m e t r y . The d e s i g n c o n c e p t

formulated by building 1:20 scale models of

the proposed antennas and

checking the radiation characteristics on a 1:20 scale model

of

the Apollo

Telescope Mount cluster.
RL # 16-006

Completion date:

A—Techn i que
By use of
If

f o r S t a b i l i z i n g t h e ATM V e h i c l e

11/68

for Extended Time Periods

Momentum Exchange Devices

a n ATM r e u i s i t i s e n v i s i o n e d t h e r m a l

supply thermal

control

a source of

control will be necessary. To

power will be required.

If

t h i s power

is provided by solar cells

facing the sun a control system will

either active or inactive.

If an active system is used the system described

in this report

be required

is applicable.

The study presents a momentum management scheme t o permit control
t h e ATM w i t h c o n t r o l moment g y r o s d u r i n g t h e unmanned phase o f
The momentum management scheme reverses the direction of

of

the mission.

disturbance torque

through simple CMG-controlled maneuvers, thus eliminating the requirement
for reaction
control

jets to relieve the

unidirectional

stored momentum of

the

moment gyros.

Presented to

May 1967

American AstronauticaI
National

Society

Symposium

SIVB Stage Digital
An al I-digital

Filter

flight controller

detail. Several mechanizations of
and comparisons made by means of

for the SIVB stage is considered

the digital

in

compensator are designed

frequency response measurements and hybrid

simulation.
SP 551-0045

Completion date:

2-13

4/24/68

�2-14

�WORKSHOP CAPABILITIES SUMMARY

PHASE C - DESIGN

In this

phase the

final

concepts are developed: designs are made t o

required specifications: and a total

system analysis made. From this an ana­

lytical report is assembled and the
(PDP) released.

finalized Project CeveIopment Plan

The Apollo Telescope Mount (ATM), as the

first

large orbital workshop,

has been through this phase. The Space Support Piuis ion's contribution in
this phase, as documented, is presented
ATM 50-56 X-Rau T e l e s c o p e :
Final analysis of

following paragraphs.

Final Report

the optical

is presented. Analysis

in the

the SO-56

X-Ray Telescope

includes ray tracing with special

emphasis on ray

diagrams, spot diagrams and

properties of

point spread

functions. All

aspects of

the

X-ray reflection dynamics were considered.
0BS-3-I

Completion date:

3/69

ATM Conf_[quration Manaqement
Established a system

for configuration control

for t h e ATM p r o g r a m . The c o n c e p t of
plan and documentation control

and documentation

a workable configuration management

plan was

presented t o and approved by the

MSFC ATM P r o j e c t O f f i c e ; t h e n d o c u m e n t e d and i m p l e m e n t e d . T e c h n i c a l
mentation is generated
determine a basic

flow

docu­

from research and data gathering, as required, t o

for t h e ATM program. The c o n f i g u r a t i o n management

keeps engineering management

plan

informed on the program status.

RL # 18-002

Completion date:

This

i s a con­

tinuing program.
ATM E x p e r i m e n t

Interface Control

Documents

R e v i e w e d and a n a l y z e d e x p e r i m e n t e r a n d ATM e l e c t r i c a l c i r c u i t s , a n d
maintained electrical

systems c o m p a t i b i l i t y between experimenters. MSFC.

and Manned Spacecraft Center by generating electrical
documents and electrical

interface control

interface defining documents. Reviewed experi­

menter s proposed changes and recommended acceptance or refusal by the Con­
figuration Control Board.
R L ft 0 9 - 0 1 2

Completion date:

2-15

4th Quarter/70

��Cable and D i s t r i b u t i o n Sus tern
A 700-cable distribution system
control, power

distribution. and data transmission

a 52-rack. 260-panel
ATM.

is currentIy being designed

electrical

support

An analysis has been made of

interconnections between

equipment checkout

the entire cable and

out system t o establish design goals and c r i t e r i a .
500FS system was

made t o determine u s a b i l i t y o f

continuing systems
control

is

interface study

is

to provide

system and

the

distribution check­

A study of
cables

for

the Saturn V,
the design.

being performed and cable

A

interface

being maintained.

RL # 09-006

Comp l e t ion d a t e :

11/68

ATM D i s t r i b u t o r s
Pre Iiminary studies of
bution requirements

ATM power, measuring, and command signal

established the

butors. The distributors route

need

commands,

between the command capsule control
and the electrical
of

the ATM.

especially designed distri­

measurements,

panel,

and electrical

t h e ATM experiment

support equipment. both prior

Designed the complete distributors

and components. Thermal
reduction

for

distri­

to

power

packages,

and subsequent to
include housing,

launch

cabling,

uacuum tests are performed t o v e r i f y the design.

i n the number

of

distributors required

is

A

achieved through the

u t i l i z a t i o n of TO-5 type relays.
R L if 9 - 0 0 4

Optimal

Completion date:

Desaturation of Control

Space vehicles

on missions

Moment Gyro Systems

that

u t i l i z e Control Moment Gyros (CMGs)

require

for a

precise pointing capabiIity offered by
systems. CMGs
by

do run out of

CMG g i m b a l

fuel

tank)

External
gimbal

angles).

torques must

angles.

problem of

CMG c o n t r o 1 1 e r s
problem.

in this application

condition (analogous

gimbal

angles

to the vehicle/CMG

free "fuel" source available
momentum desaturation of

is cast

into the

The system model

with a state and control

has

the

format of
form of

independent,

OWS-3-4

of

the

in the

to

an empty

a minimal

limits.

reset the

process

is de­

gravity gradients.

pointing control

a linear

is measured

system to

systems with

energy optimization

time-varying equation

time-varying forcing function.
Completion date:

2-17

perhaps

approach their

A systematic approach to this "refueling"

scribed using the
The

pointing will

a continuous controller. Like other

The "saturated"

be applied

in Orbit

long time t o come because

"fuel" (which,

i s r e a c h e d w h e n t h e CMG

fine

8/68

1/69

�TELESCOPE TO WORKSHOP MAGNETIC SUSPENSION DYNAMICS

/.TELESCOPE

COUPLING FROM WORKSHOP TO
TELESCOPE THRU SUSPENSION

FORCE = K | i ( S )
K| [Ei(S)-(^jsd(S)]
(TS+I)

A magnetic
an almost

suspension of
perfect

this

T=

type can be

isolator, expecially when

L|
A +R|

feedback principles are applied. Coupled

K|=I.47

force due t o workshop motion

K2=l.65

open

loop gain A.

is reduced by

In addition, the

characteristics are essentially

isolation

frequency

invariant.

2-18

A &gt; 1000

�ATM C l o c k
Designed the

logic and

stable time references
of

packaging of

t h e ATM c l o c k t o p r o v i d e u l t r a -

for u a r i o u s ATM e x p e r i m e n t s . The c l o c k

prouiding time references

days, with a stability of

I

in milliseconds,

is capable

seconds, minutes, hours, and

x 10^ throughout the temperature range of

-20

degrees to 85 degrees Celsius. The clock can be reset to any time period
by ground command signals, and has a r e l i a b i l i t y of
unit was fabricated and tested.
RL # 17-008

0.99965. One prototype

Completion date:

9 67

ATM S w i t c h S e l e c t o r Panel
Prepared Class
panel

is required

design of

I documentation of

t h e ATM s w i t c h s e l e c t o r p a n e l . T h e

f o r ATM s e l e c t o r s w i t c h t e s t and c h e c k o u t . The

the panel

(component layout) was

ments. Documentation was
00224A.

completed

Completion date:

12,67

System Networks

The electrical

circuitry to

perform switching, control,

interconnect all

five control

ATM s u b s y s t e m s a n d t o

power distribution, and

functions is currently being designed.
distributors .

prepared t o meet MSFC r e q u i r e ­

i n accordance w i t h MSFC Drawing 40M-

RL # 10-013
ATM E l e c t r i c a l

packaging

signal

conditioning

The system consists of

three power

d i stributors. three measuring distributors, a

transfer assembly, a controls and display logic distributor, and approxi­
mately 500 interconnecting cables. The
specifications.
RL # 09-011

s u b s y s t e m s a r e d e s i g n e d t o ATM

Completion date:

1/69

Time - Division Multiplexer
A time-division multiplexer was designed to accept up t o 270 data inputs
of

0 to 5 volts

in amplitude, and to provide

two parallel

output wave

trains. The multiplexer has 30 primary channels with a sampling
120 samples per second. Principal
the dc dc converter and

subassemblies of

regulators that

provide

missile power grounds: an isolation amplifier

rate of

the multiplexer are:

isolation of

signal

and

for each output: main channel

multiplexer cards: calibrator: ana clock and timing subassembly. One multi­
plexer was breadboarded and successfully tested. Documentation and
type

fabrication are

used o n t h e second ATM
RF # 16-025

in process. Several

of

these multiplexers

flight.
Completion date:

2-19

9/68

proto­

shall

be

��Control Circuitry

for Data Acquisition Sustem

D e s i g n e d t h e a m p l i f i e r a n d s w i t c h a s s e m b l y t o b e u s e d o n t h e ATM t o
amplify and select the proper output of

r e d u n d a n t PCM d i g i t a l d a t a a c q u i s i ­

t i o n s u b s y s t e m s . S w i t c h i n g b e t w e e n t h e t w o PCM s u b s y s t e m s

is accomplished

by commands to internal control c i r c u i t r y . These control c i r c u i t s employ
electro-optical

devices t o provide maximum isolation between the external

command signal c i r c u i t r y and the control
RL # 17-005

circuits.
Completion date:

11/67

Charger-Batteru Regulator-Module Documentation
This effort

involves

preparation of

the specification. and the accept­

ance preliminary and qualification test procedures

for the Apollo Telescope

Mount (ATM) charger-battery-regu I ator module. A review of
requirements and

prototype circuitry provided detail

three documents. The specif icat ion establishes
requirements; the acceptance test procedure sets
standards: and the qualifications test
operating requirements

t h e ATM

requirements

forth module acceptance

procedure details environmental

Completion date:

2-21

for the

purchasing manufacturing

for the modules.

RL # 10-001

power

4/68

�Kft

-3
3

»—

3
o
*—

•3
3
O
O
Cy
V&gt;
O
L.
3
m
—.

4-»
o

"3
cw
v. 4-*
L_ ——
•—

•w

3

»—

•3
»—

4-»
0
3 ——
cu
0
E -3
iC
3&gt;
*—
3.
——
3»
3 -3
ITi
-3

1

"3

3.
O
O

u
3
"3
O
L.
4-*
3
•—

"3
3
3
-3

—

+-»

H—«
O
«/»

3

—

•—
+•&gt;

LO
4-»
V*
»—

&lt;3

X
3
——

Cy
-3
4-*

4-»
3
Cy
E
cy

3
O

•

v&gt;

•—

3s
3
L.
*—

2-22

&lt;/»

&lt;y

Cy
3

«—

4-»
O
cy
—

"V^
cy
u

3
O
•—

4-»
3_
O
Cy
-3
4-*
O
4-»
4U
Cy
3.
v&gt;
Cy
L.
-3
•w
•—

3

�WORKSHOP CAPABILITIES SUMMARY

PHASE D - DEVELOPMENT AND OPERATIONS
In this

final

phase the tasks of developing. manufacturing, testing and

operating the products designed to achieve the mission goals are carried
out. The Space Support Division s capabiIity in this area is readily demon­
strated by presenting assigned tasks and describing the design deveIopment
and testing effort

put

forth on each. The

the Apollo Telescope Mount (ATM)

following paragraphs describe

Phase D effort.

X-Rau Telescope - Camera and E lectronics Desian:
The X-ray teIescope-camera and electronics

S-056 Design

for the S-056 X-ray telescope

experiment which will measure soft X-ray radiation originating in the solar
atmosphere has been designed, deve I oped. and produced. The X-ray telescope
system comprises

an X-ray telescope with

film camera and an X-ray event

analyzer (X-REA).
The X-REA and teIescope-camera are two independent measuring systems
w h i c h w i l l b e a t t a c h e d t o t h e ATM i n a m a n n e r w h i c h w i l l
to measure radiation

from the same source. The

these two measuring systems will
flares and the physical

allow both systems

information obtained

provide a better understanding of

processess which take place in the

OBS-4-1

Complet ion date :

from
solar

sun.
I 69

ATM T e l e v i s i o n S y s t e m D e s i g n
A television system

for the Apollo Telescope Mount (ATM) has been de­

signed and developed. This
naut viewing of

system is installed

solar activity

telescopes and consists of

i n t h e ATM t o e n a b l e a s t r o ­

from earth orbit through several different

two (2)

Iow-light-1eve I

TV cameras, two ( 2 )

v i d i c o n T V c a m e r a s , a n F. I A s y n c g e n e r a t o r , a n d t w o ( 2 ) w i d e b a n d v i d e o
switches.
The
of

low-light-level

excellent

usable

t e l e v i s i o n camera u t i l i z e s a SEC v i d i c o n c a p a b l e

picture quality

p i c t u r e q u a l i t y ( 2 0 0 TV

can be used as a
candles .

( 6 0 0 TV

lines) at 3 x 10'3

lines) at 5 x /0"5

footcandles and

footcandles. The camera

Iight-integrating device down t o levels below 10'7

2-23

foot­

��T h e ATM v i d i c o n camera i s a h i g h r e s o l u t i o n ( 8 0 0 TV l i n e s ) s y s t e m u t i l i ­
zing a standard 5403 ruggedized uidicon with excellent
I

x lO'l

footcandles. Usable

performance down t o

pictures can be obtained down t o 5 x

10

footcandles.
OBS-4-2

Completion date:

E l e c t r i c a l Power Subsystem

for Apollo Telescope Mount (ATM)

This task comprised the design and deuelopment of
power subsystem which

I 69

furnishes the electrical

t h e ATM e l e c t r i c a l

power required by all other

ATM s u b s y s t e m s a n d e x p e r i m e n t s .
T h e ATM e l e c t r i c a l poiuer s u b s y s t e m c o n s i s t s o f
energy conversion
and the required

sources.
interface

18

18

photovoltaic direct

power conditioning-energy storage groups.

interface networks and power distribution c i r ­

cuitry that provides remote system control

capability, system monitoring,

and power management information.
OWS-4-3

Completion date:

I 69

270 Channel Multiplexer
The 270 multiplexer was designed t o accrue data and channel

the data

via 270 lines to the data acquisition system. The multiplexer utilizes the
latest circuit configurations.

including integrated circuits. To develop

the multiplexer, the electromechanical
grated circuits with weldable
through the motherboard and

leads.

flexible

package was designed using inte­

Interconnections were accomplished
printed circuit cabling. The

flight

housing was designed utilizing three configurations-almag sand casting,
aluminum sheet weldment and an aluminum dip brazed housing: of
latter was selected

for implementation. The multilayered circuit boards are

attached in an accordion
padding inserted

fashion with

flexcabling and with shock-resistant

into a cavity configuration. The module is currently des­

ignated as backup
for t h e second ATM

for the

f i r s t ATM

flight and will maintain a prime status

flight upon completion of

RL # P4-008

AC DC

which the

prototype development.

Completion date:

6/68

Power Suoolu

An ac dc electronic
d c power t o t h e ATM
motor. The dc

power supply was designed and
platform modules and ac

portion of

the

power

supply

fabricated to

furnish

power t o t h e 4TM g y r o s p i n
is equipped with a

step-up

switching prereguIator. a dc-to-dc conuerter and a pulse regulator. The

2-25

�ACCEPTABLE S/N RATIO

The performance a t t a i n a b i l i t y of
brightness. as a function of

a star tracker, for a particular guide s t a r

the acceptable signal

J-26

to noise ratio.

�ac output

is equipped with a crystal-control led oscillator,

followed by a

binary countdown. The dc input uoltage is required to remain between 24 to
32 volts to maintain a dc

power output of

250 watts and 35 volts ac at

1600 Hz.
RL # 22-009

Completion aate:

Ground Support Electrical

Power Sustem

A power system is currently being designed t o
solar bus and or load bus and t o the electrical
forming ground checkout of

12 66

f u r n i s h power t o t h e ATM

support equipment when per­

the ATM. The design e f f o r t

includes an overall

system analysis to establish design criteria, an evaluation of
s y s t e m s t o d e t e r m i n e t h e i r a d a p t a b i l i t y t o t h e ATM
comprehensive study of
paration of

existing

requirements, and a

each subsystem to provide details needed

for

pre­

the preliminary design drawings. Fabrication drawings and pre­

liminary early-order parts lists are also being prepared.
R L # 09-009

Completion date:

11 68

Hudrogen-Oxuaen Fuel Cell Resign and Test
Four

years of

detailed experience has

operation and test of

Hydrox

fuel

been obtained

in the design,

cells. Approximately 8000 hours of

ope­

r a t i o n of 2-kilowatt A11 i s-ChaImers (AC) systems have been logged by d i v i ­
sion personnel

in the study and test of

developments have resulted

these power sources. Significant

from research conducted on single

sections on evaluation consoles developed and
OWS-4-4

fuel

cell

fabricated by this Division.

Completion date:

A continuing
effort

Sun Sensor and Star Tracker Computer Simulator
A computer simulator is currently being developed
of

the sun

sensor and

similar to that of

star tracker. The

simulator

internal electronics of

the

the data.

the direction and magnitude of

solver zero, and
tested when

flight:

function
i t gene­

pulses, that are used

fine sun sensor and star tracker

purposes, gating, and shifting of
data of

performs a

the on-board digital computer during

rates an interrogate pulse, together with clock
the

for ground checkout

for timing

It also accepts serial

binary

the resolver rotation and the re-

presents them to the display panel. The simulator will

fabrication is completed.

RL # 13-001

Completion date:

2-27

in

Estimated 6 68

be

�2-28

�P a c h ac l i n g P e s i g n _ f o r t h e C h a r g e r B a t t e r y _ R e g u l a t o r M o d u l e ( C P R M )
Performed the packaging design and documentation of

t h e ATM C B R M . w h i c h

included engineering design, drafting, and checking. The packaging design
required compliance with the EnuironmentaI
Criteria for

ATM Components s p e c i f i c a t i o n . The purpose o f

prouide regulation, conuersion.
while

and storage of

solar-cell

t h e CBRM

is

to

power t o t h e ATM

in an earth orbit.

RL # 10-006

Completion date:

S-Band Helical

with a gain of

68

II

Arrau Antenna

Designed a S-band helical

of

Design and Dualif ication Test

array. The array consists of

a single helix,

8 db. mounted upon a common base p l a t e , adjacent t o an array

four helices. The array has a gain of

12 db. The dual

gain feature was

utilized to prouide hemispheric earth coverage from an altitude of
t o 2 3 . 0 0 0 s t a t u t e m i l e s . ,1 c o a x i a l
antenna radiator. A four helical
because of

antenna height

switch directs the rf

signal

8.000

to either

array was used for the high gain radiator

restrictions on the Saturn V Instrument Unit. A

laboratory

model

verified

the design dimensions.

A shop prototype was

fabricated

from design drawings. Qualif ication tests to flight certify

the

antenna were performed and the quaI i f i c a t i o n test report published.
RL # I 6 - 0 I 2

Completion date:

10/66

Power Control and Monitor Panel
A control

panel,

distribution of

for

monitoring and controlling the

ATM e l e c t r i c a l

support equipment power,

generation and

is currently

in the

preliminary stage of deuelopment. The subsystem w i l l

s i m u l a t e t h e ATM s o l a r

sources and control

Modules

(CBRM) during

also has override control

capabi I i t y for

the Charger-Battery-ReguIator

ground checkout. The control

panel

controlling the switch selector encoded assembly.
RL # 09-003

Completion date:

2/68

Solar Simulator
A solar

simulator,

gineered and designed
simulator

tube

mw cm- i n t e n s i t y
Celsius.

for

testing solar cell

for use

capable of

performance, has been en­

i n t h e ATM q u a l i t y a s s u r a n c e program.

illuminating a 24- by 26-inch area,

has

The

a 100

capabiIity at any temperature setting between 100 and90°

RL # 10-022

Completion date:

) - 70

II

67

�radiated power.
2-30

�Portable Solar Reflectometer
A portable

solar reflectometer

for measuring reflective

property of

materials in space is currently under deueIopment. The instrument will make
measurements over a wave-length range of
bands.

Data obtained

from measurements

tape recorder, which is an integral
of

2500 A to 2.5 microns in eleuen
is to be recorded on a magnetic

part of

the reflectometer. The

the reflectometer is t o make refIectance measurements of

paint

purpose
samples

and or other materials which may be affected by the space environment.
PL - 16-027

Completion date:

8 68

Advanced Optical Communications Systems Research and Development
Research
perimental

in this area involves state-of-the-art theoretical
studies of

the eventual
cluded

visible and

development of

in this program are

infrared

and ex­

laser systems, with an aim to

a deep-space laser communications
projects that involve

link.

In­

laboratory photomixing

experiments. beam steering and alignment technique studies, the design and
testing of

signal

processing and information retrieval electronics,

laser

stability and control studies, and the development of transmitting optical
systems.
R L •• 0 1 - 0 0 1

Completion date:

This is a con­
tinuing program.

Aavanced Optical Tracking Systems Research and Development
Under t h i s

program, research and development is being conducted on a

precision optical

tracker that utilizes a visible laser transmitter

for

monitoring the elevation and azimuth angles, angular rates, range, and
range rate of

a spacecraft during the critical

launch phase which occurs

immediately after l i f t o f f . Current activity in this program involves the
prototype development of

laser amplitude modulations, modulator drivers,

and diverse detection and demoduI ation eIectronics.
RL •• 0 1 - 0 0 2

Completion date:

4th Quarter/68

Gas Laser Research
This research and development program is directed
parameters of

gas

laser photomixing systems

at optimizing the

for potential use in tracking

and communication applications. Current program activities
involved in the measurement of
ment of

include projects

laser mode s t a b i l i t y , the prototype develop­

scanning interferometers

for monitoring laser mode patterns, and

the experimental and theoretical research on the dependence of photomixing
on optical path length difference.
RL # 0 1 - 0 0 3
. •
r
Completion date: This is a con­
tinuing program.
2-31

��Laser Atmospheric Propagation Studies
These studies

involve the experimental and theoretical

random phase variations in laser radiation during

research on the

Iong-distance atmospheric

propagation. Activities are oriented to the design and development of
laser system that is to be employed in the measurement of
ations of

an amp Iitude-moduIated

a

the phase vari­

laser beam as i t traverses various atmo­

spheric path lengths.
RL " 01-005

Completion date:

This is a con­
tinuing program.

Optical Component Development
This RSD e f f o r t i s

organized to provide optical

systems-components

integration and correlation technology. The program consists of

an optical

systems design study that is being conducted in con j unction with an optical
components design and development activity (mirrors. lenses): which in turn
results
tical

in the integration of

the individual components

into complex op­

s y s t e m s . /I c u r r e n t d e s i g n a n d d e v e I o p m e n t p r o j e c t i s t o d e s i g n l a r g e

f-number lenses with minimal

low-order Seidel abberations.

R L -- 0 1 - 0 0 4

Completion date:

This is a con­
tinuing program.

Advanced Semiconductor Memoru Devices Research
Theoretical and experimental

research studies into the use of

a metal-

insulator- semi conductor (MIS) device, as a bistable active memory element,
were performed. The device utilizes the tunneling effect between the semi­
conductor and the insulator to store trapped charges.
RL

H

01-009

Completion date:

This is a con­
tinuing program.

Advanced Semiconductor Materials Research
Research studies involve state-of-the-art epitaxial
niques. Current

research includes development of

transistors, deposition of
growth of

and diffusion tech­

deep diffusion

for power

silicon nitrides and oxides, and epitaxial

semiconductor materials.

RL - 01-006

Completion date:

This is a con­
tinuing program.

2-33

�The Zeta angle uersus time plot depicts the angular change the solar vector makes
with its projection on t o the orbital

plane during a one year period. The high

frequency variations are caused by orbital

regression while the

I cycle per year - variation is caused by the earths
inclination of
degrees.

the orbital

journey about the sun. The

plane referenced to the equator

2-34

low frequency -

for this plot

is 28.5

�Non-linear Magnetics Memory Research and Deuelopment
This research effort is inuolued uiith state-of-the-art studies of

mag­

netic t h i n - f i l m memory materials and deuice techniques. Areas researched
include magnetic material

properties, techniques of

deposition, and the

deuelopment of aduanced memory systems.
RL ' 01-008

Completion date:

This is a con­
tinuing program.

2 - 35

����I I I . ORGANIZATION PROFILE

The Space Support Division i s an operating unit of
the Sperry Rand Corporation as illustrated in

figure

the Sperry Group of
I . The division was

founded in Huntsvi11e. Alabama in 1965 t o support the National
and Space Administration. George C. Marshall
trionics Laboratory,
sion is

in all

Aeronaut i cs

Space Flight Center. 4s-

technical disciplines. The Space Support Divi­

fulfilling i t s mission by designing and producing, to the exacting

requirements of

the Astr ionics Laboratory. many complex systems in support

of the Apollo Telescope Mount. Orbital Workshop and Saturn/Apo11o programs.
The division is also

furnishing spacecraft reliability and test engineering

services to the Goddard Space Flight Center.
recently signed with the Army Corps of
cation of

In addition, a contract UKJS

Engineers that requires the appli­

aerospace technology to the tactical

facilities of

the SENTINEL

Anti-ballistic Missile System.
From July 1966 through June

1968 the Space Support Division

engineering services to the Jet Propulsion Laboratory

furnished

for the design of

spacecraft and spacecraft systems.
FACILITIES AND STAFFING
The staff of

the Space Support Division is currently at the level of

employees. This staff
facilities of

840

includes 600 employees working in direct support in

the Marshall

Space Flight Center (MSFC) Astrionics Laboratory

in Huntsville, Alabama. There are 235 employees working in direct support
of

the Goddard Space Flight Center

portion of

in Greenbelt. Maryland. 4 substantial

our employees are housed in Space Support Division

Huntsville, Alabama, consisting of

facilities in

three buildings containing 53.000 square

feet of floor space. These facilities provide administrative, engineering.
Iaboratory, and prototype manufacturing areas.
T h e e n g i n e e r i n g a r e a i n c l u d e s a we1 1 - e q u i p p e d
perimental

laboratory in which ex­

and prototype models are developed and tested.

A Sperry Rand Corporation computation
Support Division engineering

facility is located near the Space

facilities. 4 Univac 1108 computer is avail­

able t o support simulation requirements. data reduction, and budget and
payment records.

3-1

�I
I
I
I
I

�SPERRY RAND CORPORATION

SPEP.RY RAND
RESEARCH CENTER

UN I VAC D I V I S I O N

SPERRY MARINE AND ELECTRONICS
DIVISION

SPERRY FLIGHT SYSTEMS
DIVISION

SPERRY SYSTEMS MANAGEMENT
D I V I S I ON

SPERRY MARINE SYSTEMS
DIVISION

SPERRY GYROSCOPE
DI V131 ON

REMINGTON. RAND
DIVISION

FORD INSTRUMENT
DIVISION

NEW HOLLAND GROUP

SPACE SUPPORT
DIVISION

SPERRY ELECTRONIC TUBE
DIVISION

SPERRY MICROWAVE
ELECTRONICS D I V I S I O N

INTERNATIONAL OPERATIONS

CHAPT S

!O-25-:960

SPERRY RAND CORPORATION
Figure 1

REMINGTON ELECTRIC SHAVER
DIVISION

��-6nrSFER*Y RAND

Figure 2 . Space Support Division

�mBsSSm

NHBRHBHH

BBhBHHI

�ENGINEERING
Approximately half

of

our engineering employees

Alabama are engaged in on-site support of
remainder of
of

located

in Huntsuille.

the Astr i on i cs Laboratory. The

the Engineering Department employees occury 23.SOD square

the Space Support Division

scientific employees

facility. This staff

responsible

feet

includes engineering and

for study, deuelopment. t e s t and docu­

mentation work related to Space Support Diuision programs. In engineering
design department provides design and drafting
groups. The engineering staff
fifty masters

for development engineering

includes two doctorate degrees, approximately

degrees, over two hundred bachelor degrees and over one

hundred associate degrees.
PAST PERFORMANCE
Sperry Rand Space Support Division
a technical

performance rating of

management rating of

for the past three years has achieved

excellent or better, and a technical

superior on support services contracts.

COST REDUCTION AND CONTROL
Sperry Rand Space Support Division i s currently involved in an effective
cost reduction program (ORBIT)

in which all

employees are consistently

urged to participate. This program meets the cost reduction guidelines as
set

f o r t h b y b o t h DOD a n d NASA. T h e

program is coordinated by an assigned

individual and is guided by an established procedural manual which complies
with both government and corporative guidelines.
its

inception, a gross savings of

In the 2 1/2 years since

$1,170,134 has been reported. Through

F e b r u a r y 2 8 . I 0 6 8 . 53 8 s u g g e s t i o n s h a v e b e e n s u b m i t t e d r e p r e s e n t i n g a n
employee participation of 66%.
PROJECT MANAGEMENT
The Space Support Division has developed a project management point-ofview as

the result of

i t s three and a half

years experience in support of

aerospace agencies and has evolved an organization geared to the achieve­
ment of

project goals on time, within budget, and within predetermined

performance spec i f icat ions. The management techniques deueloped cover the
planning, control, and supervision of

engineering and design resources and

include the whole range of

systems engineering, project control, configu­

ration and data management

t e s t , and procurement. The result is the inte­

gration of

the several

functional departments of

management system. Each contracted task

the division into a

is assigned to a

total

project manager

who assumes complete responsibility and accountabiIity t o divisional man­
agement ana to t h e customer

for successful accomplishment of the program.
3-4

��SECTION IV

SUMMARY

SPACE SUPPORT

��IV.

SUMMARY

The qualifications, f a c i l i t i e s , and capabiI i t i e s of
Support Division may be summarized as

PersonneI

840 total

FaciI ities

S p e r r y R a n d S pa c e

follows:

- of which 40 percent are engineers.

S3.000 square feet of modern well

equipped fa­

cilities.
Qua I i t y

Dedicated by pol icy and

practice to the highest

attainable level of quality control
with the cost
enced

in

aspects

complying

consistent

of the program. Experi­

with

DOD and N1SA q u a l i t y

specifications.
Control s

A modern

UNIVAC

1108

computer

is utilized in

the management of man-hours schedules and cost
control.
Experience

Proven
for

success

the

Marshall

on support

Astrionics

services

Laboratory,

Space Flight Center;

Jet

contracts
George

C.

Propulsion

Laboratory and Goddard Space F l i g h t Center.
Security

Secret

facility

Contract

clearance

aamin istratiue

granted

services

by

Defense

region,

At­

lanta, Georgia
Cost Savings

Gross savings of si,170,134 in 2 1/2 years with
66 percent employee participation.

Additional ly, through the corporate policy of
the Space Support Division can draw on a l l
nical

consuI t a t i o n . manpower,

or

synergistic operations

corporate resources when tech­

equipment are needed.

4-1

���•EBIQN . DEVELOPMENT* STUDIES •
ENGINEERING
RANGE

SUPPORT
INSTRUMENTATION

AUTOMATIC

CHECKOUT

GUIDANCE AND

CONTROL SYSTEMS

TELEMETRY
-0"

ELECTRONIC POWER
CONFIGURATION

-$•

SYSTEMS

MANAGEMENT

FLIGHT DYNAMICS AND SIMULATION
ELECTRICAL AND ELECTRONIC SYSTEMS
SPACE AND SATELLITE

COMMUNICATIONS

NAVIGATION SYSTEM ANALYSIS
&gt;$•

RELIABILITY

ANALYSIS

FABRICATION

°^SPER^Y RAND

SPACE SUPPORT ixvson

•&lt;AWTSVLU!.

�</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="214005">
                <text>sdsp_skyl_000070</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214006">
                <text>"Sperry Rand Earth Orbital Workshop Capabilities" Brochure.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214007">
                <text>Sperry Rand (Corporation)</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="214008">
                <text>1969-02-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="214009">
                <text>1965-1970</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214010">
                <text>Sperry Rand (Corporation)</text>
              </elementText>
              <elementText elementTextId="214011">
                <text>Skylab Program</text>
              </elementText>
              <elementText elementTextId="214012">
                <text>Apollo applications program</text>
              </elementText>
              <elementText elementTextId="214013">
                <text>Space habitats</text>
              </elementText>
              <elementText elementTextId="214014">
                <text>Saturn launch vehicles</text>
              </elementText>
              <elementText elementTextId="214015">
                <text>Apollo Telescope Mount</text>
              </elementText>
              <elementText elementTextId="214016">
                <text>Huntsville (Ala.)</text>
              </elementText>
              <elementText elementTextId="214017">
                <text>George C. Marshall Space Flight Center. Astrionics Laboratory</text>
              </elementText>
              <elementText elementTextId="214018">
                <text>Sperry Rand (Corporation). Space Support Division</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214019">
                <text>Brochures</text>
              </elementText>
              <elementText elementTextId="214020">
                <text>Still Image</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="214021">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="214022">
                <text>Box 30, Folder 18</text>
              </elementText>
              <elementText elementTextId="215975">
                <text>University of Alabama in Huntsville Archives and Special Collections, Huntsville, Alabama</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="214023">
                <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="214024">
                <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="214025">
                <text>Skylab Document Scanning Project Metadata</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="22">
        <name>Skylab 50th Anniversary</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="10388" public="1" featured="0">
    <fileContainer>
      <file fileId="9665">
        <src>https://digitalprojects.uah.edu/files/original/20/10388/Sperrandmontprog_092910151001.pdf</src>
        <authentication>58bfca722e3194e3d8b28a6736195772</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="155781">
                <text>Sperrandmontprog_092910151001.pdf</text>
              </elementText>
              <elementText elementTextId="155782">
                <text>spc_stnv_000844</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155783">
                <text>"Sperry Rand monthly progress report for July, 1969."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155784">
                <text>The following pages contain reports for each of the individual contract appendices covering technical progress and accomplishments, related problems, and staffing progress. The report of manhours expended against each appendix by schedule order is being submitted as a part of the financial management report.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155785">
                <text>Sperry Rand Corporation. Space Support Division</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="155786">
                <text>1969-07-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155787">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155788">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155789">
                <text>Report</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155790">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155791">
                <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="155792">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155793">
                <text>Box 32, Folder 25</text>
              </elementText>
              <elementText elementTextId="210198">
                <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="155795">
                <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="155796">
                <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="155797">
                <text>spc_stnv_000825_000849</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="155798">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18213</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="10390" public="1" featured="0">
    <fileContainer>
      <file fileId="9075">
        <src>https://digitalprojects.uah.edu/files/original/20/10390/Stabanalofapol_101310150040.pdf</src>
        <authentication>ea24045bfb16b894f4159afe56302b22</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="155817">
                <text>Stabanalofapol_101310150040.pdf</text>
              </elementText>
              <elementText elementTextId="155818">
                <text>spc_stnv_000846</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155819">
                <text>"Stability analysis of Apollo - Saturn V propulsion and Structure feedback loop."</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155820">
                <text>The propulsion and the structure of a space vehicle form a feedback loop through inertial coupling referred to as the pogo phenomenon and experienced with the Thor , Titan, and Apollo-Saturn V space vehicles.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155821">
                <text>Von Pragenau, George Landwehr</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="155822">
                <text>1969-08-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="82">
            <name>Temporal Coverage</name>
            <description>Temporal characteristics of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="155823">
                <text>1960-1969</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155824">
                <text>Saturn project</text>
              </elementText>
              <elementText elementTextId="155825">
                <text>Propulsion</text>
              </elementText>
              <elementText elementTextId="155826">
                <text>Propellants</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155827">
                <text>Text</text>
              </elementText>
              <elementText elementTextId="155828">
                <text>Design 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="155829">
                <text>Saturn V Collection</text>
              </elementText>
              <elementText elementTextId="155830">
                <text>Box 32, Folder</text>
              </elementText>
              <elementText elementTextId="210200">
                <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="155832">
                <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="155833">
                <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="155834">
                <text>spc_stnv_000825_000849</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="155835">
                <text>http://libarchstor.uah.edu:8081/repositories/2/archival_objects/18220</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
