<?xml version="1.0" standalone="yes"?>
<Paper uid="X96-1004">
  <Title>Some Technology Transfer: Observations from the TIPSTER Text Program</Title>
  <Section position="5" start_page="31" end_page="31" type="concl">
    <SectionTitle>
8. Conclusion
</SectionTitle>
    <Paragraph position="0"> I have outlined in this paper much of what I have learned, from working in the TIPSTER Program, about transferring technology from the research stage to daily use in an operational environment. In working jointly on this endeavor we have all learned these things and many of the ideas recorded here have been or are being incorporated into the Program to help guide future technology transfer. It is in the nature of a lessons learned, to support these future efforts, that I have recorded here, at the close of Phase II, so many of the difficulties that we have encountered and in many cases also overcome.</Paragraph>
    <Paragraph position="1"> I have included in this paper many suggestions for dealing with the problems that arise in technology transfer. Technology transfer is a complex process and the number of issues that must be addressed is large.</Paragraph>
    <Paragraph position="2"> Thus, I hesitate to say that one set of issues is more important than any other. However, two of the issues I have discussed are of paramount importance. The first is making sure that the technology is ready to transfer - does it offer significant new capability and is it sufficiently well understood so that it can be made robust, fast, and be integrated with other necessary capabilities. The second is collaboration with the user. The technologist is neither a servant nor a savior, that is, neither the user nor the technologist has all the answers. What we have to do to transfer technology successfully, and what we have done in the TIPSTER Program, is make a place where the two can meet, user and technologist, to work collaboratively in a joint effort to tame the &amp;quot;text monster&amp;quot; and improve the way textual information is handled in our operational environment.</Paragraph>
  </Section>
class="xml-element"></Paper>