<?xml version="1.0" standalone="yes"?>
<Paper uid="H91-1040">
  <Title>Current Status</Title>
  <Section position="2" start_page="0" end_page="0" type="metho">
    <SectionTitle>
TRANSPORTATION PLANNING
</SectionTitle>
    <Paragraph position="0"> Logistical transportation planning is the process of determining how to get people and cargo from where they are to where they need to be. Inter-theatre movements of personnel and supplies around the world are currently planned for the Army, Navy, Air Force, and other services by USTRANSCOM (the US TRANSportation COMmand) which operates under the Joint Chiefs of Staff. The transportation plarming process is quite complex, involving very large databases of movement requirements, and information about personnel, cargo, transportation assets, and geographic locations. Currently, the human interface to military planning systems is relatively enmbersome and unintelligent, which adds extra complexity to the planner's task.</Paragraph>
    <Paragraph position="1"> As a domain for the application of spoken language, military transportation planning has a number of advantages:  1. Transportation planning is an essential military function and successful application of spoken language would be both useful to TRANSCOM and visible to other potential military users of SLS technology.</Paragraph>
    <Paragraph position="2"> 2. The concept of planning movements of people and supplies can be understood by a wide audience.</Paragraph>
    <Paragraph position="3"> 3. The application is non-trivial and, in the DART context that we will describe, affords opportunities for applying spoken language understanding at many levels of sophistication.</Paragraph>
    <Paragraph position="4"> 4. Current efforts to improve the planning process using non-speech technology have been weU-received, and cooperative users may be available as close as Scott Air Force Base near St. Louis.</Paragraph>
    <Paragraph position="5"> 5. An unclassified development database is available in Oracle on a Son.</Paragraph>
  </Section>
class="xml-element"></Paper>