\documentclass[10pt]{scrartcl}
%%
%
% This is a poster template with latex macros and using
% the University of Florida Logo.  For further information
% on making postscript, resizeing, and printing the poster file
% please see web site
% http://www.phys.ufl.edu/~pjh/posters/poster_howto.html
%
% N.B. This format is cribbed from one obtained from the University
% of Karlsruhe, so some macro names and parameters are in German
% Here is a short glossary:
% Breite: width
% Hoehe: height
% Spalte: column
% Kasten: box
%
% All style files necessary are part of standard TeTeX distribution
% On the UF unix cluster you should not need to import these files
% specially, as they will be automatically located.  If you
% run on a local PC however, you will need to locate these files.
% At UF try /usr/local/TeTeX...
%
% P. Hirschfeld 2/11/00
%
% The recommended procedure is to first generate a ``Special Format" size poster
% file, which is relatively easy to manipulate and view.  It can be
% resized later to A0 (900 x 1100 mm) full poster size, or A4 or Letter size
% as desired (see web site).  Note the large format printers currently
% in use at UF's OIR have max width of about 90cm or 3 ft., but the paper
% comes in rolls so the length is variable.  See below the specifications
% for width and height of various formats.  Default in the template is
% ``Special Format",  with 4 columns.
%%
%%
%% Choose your poster size:
%% For printing you will later RESIZE your poster by a factor
%%        2*sqrt(2) = 2.828    (for A0)
%%        2         = 2.00     (for A1)
%%
%%
\def\breite{450mm}     % Special Format.
\def\hoehe{319.2mm}      % Scaled by 2.82 this gives 110cm x 90cm
\def\anzspalten{4}
%%
%%\def\breite{420mm}     % A3 LANDSCAPE
%%\def\hoehe{297mm}
%%\def\anzspalten{4}
%%
%% \def\breite{297mm}     % A3 PORTRAIT
%% \def\hoehe{420mm}
%% \def\anzspalten{3}
%%
%% \def\breite{210mm}     % A4 PORTRAIT
%% \def\hoehe{297mm}
%% \def\anzspalten{2}
%%
%%
%% Procedure:
%%   Generate poster.dvi with latex
%%   Check with Ghostview
%%   Make a .ps-file with ``dvips -o poster.ps poster''
%%   Scale it with poster_resize poster.ps S
%%   where S is scale factor
%%     for Special Format->A0 S= 2.828 (= 2^(3/2)))
%%     for Special Format->A1 S= 2 (= 2^(2/2)))
%%
%% Sizes (European:)
%%   A3: 29.73 X 42.04 cm
%%   A1: 59.5 X 84.1 cm
%%   A0: 84.1 X 118.9 cm
%%   N.B. The recommended procedure is ``Special Format x 2.82"
%%   which gives 90cm x 110cm (not quite A0 dimensions).
%%
%% --------------------------------------------------------------------------
%%
%% Load the necessary packages
%%
\usepackage{palatino}
\usepackage[latin1]{inputenc}
\usepackage{epsf}
\usepackage{graphicx,psfrag,color,pstcol,pst-grad}
\usepackage{amsmath,amssymb}
\usepackage{latexsym}
\usepackage{calc}
\usepackage{multicol}
%%
%% Define the required numbers, lengths and boxes
%%
\newsavebox{\dummybox}
\newsavebox{\spalten}
%\input psfig.sty

%%
%%
\newlength{\bgwidth}\newlength{\bgheight}
\setlength\bgheight{\hoehe} \addtolength\bgheight{-1mm}
\setlength\bgwidth{\breite} \addtolength\bgwidth{-1mm}

\newlength{\kastenwidth}

%% Set paper format
\setlength\paperheight{\hoehe}
\setlength\paperwidth{\breite}
\special{papersize=\breite,\hoehe}

\topmargin -1in
\marginparsep0mm
\marginparwidth0mm
\headheight0mm
\headsep0mm


%% Minimal Margins to Make Correct Bounding Box
\setlength{\oddsidemargin}{-2.44cm}
\addtolength{\topmargin}{-3mm}
\textwidth\paperwidth
\textheight\paperheight

%%
%%
\parindent0cm
\parskip1.5ex plus0.5ex minus 0.5ex
\pagestyle{empty}




\definecolor{recoilcolor}{rgb}{1,0,0}
\definecolor{occolor}{rgb}{0,1,0}
\definecolor{pink}{rgb}{0,1,1}





\def\UberStil{\normalfont\sffamily\bfseries\large}
\def\UnterStil{\normalfont\sffamily\small}
\def\LabelStil{\normalfont\sffamily\tiny}
\def\LegStil{\normalfont\sffamily\tiny}

%%
%% Define some commands
%%
\definecolor{JG}{rgb}{0.1,0.9,0.3}

\newenvironment{kasten}{%
  \begin{lrbox}{\dummybox}%
    \begin{minipage}{0.96\linewidth}}%
    {\end{minipage}%
  \end{lrbox}%
  \raisebox{-\depth}{\psshadowbox[framesep=1em]{\usebox{\dummybox}}}\\[0.5em]}
\newenvironment{spalte}{%
  \setlength\kastenwidth{1.2\textwidth}
  \divide\kastenwidth by \anzspalten
  \begin{minipage}[t]{\kastenwidth}}{\end{minipage}\hfill}

\renewcommand{\emph}[1]{{\color{red}\textbf{#1}}}


\def\op#1{\hat{#1}}
\begin{document}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%               Background                     %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
{\newrgbcolor{gradbegin}{0.5 0.5 1}%
  \newrgbcolor{gradend}{1 1 1}%{1 1 0.5}%
  \psframe[fillstyle=gradient,gradend=gradend,%
  gradbegin=gradbegin,gradmidpoint=0.1](\bgwidth,-\bgheight)}
\vfill
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%                     Header                   %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\hfill
\psshadowbox{\makebox[0.95\textwidth]{%
    \hfill
    \parbox[c]{2cm}{\includegraphics[width=6cm]{wvu.eps}}
    \hfill
    \parbox[c]{0.8\linewidth}{%
      \begin{center}
        \textbf{\Huge {Long-Term Electronic Storage, Retrieval and Use of Complex Engineering Information}}\\[0.5em]
        \textsc{\LARGE T. Menzies$^a$, V. Mucino$^b$, J. Mooney$^a$ and T. McGraw$^a$}\\[0.3em]
        {\large $^a$Lane Department of Electrical Engineering and Computer Science, West Virginia University, Morgantown, WV 26506-6109, USA\\
$^b$Mechanical and Aerospace Engineering, West Virginia University, Morgantown, WV 26506-6109, USA
}
      \end{center}}
\hfill}}\hfill\mbox{}\\[1.cm]
%\vspace*{1.3cm}
\begin{lrbox}{\spalten}
  \parbox[t][\textheight]{1.3\textwidth}{%
    \vspace*{0.2cm}
    \hfill
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%                 first column                 %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{spalte}
     \begin{kasten}
    \section*{ \hspace{0.1cm} {\color{red} \underline{OUR QUESTIONS}} }
            \begin{center}
             \includegraphics[width=5cm]{questions.eps}
            \end{center}
Imagine the scene: some widely-used devices fails decades after it was
designed.  A new one must be designed.

Engineers turn to the archival
storage to learn what they can from the old design. What problems
would they encounter? How can we support them in that activity?
      \end{kasten}
      
\begin{kasten}
    \section*{ \hspace{0.1cm} {\color{red} \underline{CHALLENGES}} }
Based on surveys of engineering data sets, we assert that it is highly
unlikely that a decades-old design exists in one particular
format. Rather, technical documents like those seen in the
STEP/EXPRESS format are stored along side a much larger set of
supporting documents in multiple formats. A recent study concluded
that :

\begin{itemize}
\item
 80 percent of business is conducted on unstructured information.
\item 85 percent of all data stored is held in an unstructured format.
\item Unstructured data doubles every three months.
\end{itemize}
That is, if we can learn how to understand large heterogeneous collections that include
STEP/EXPRESS knowledge as well as numerous other products in a wide variety of
formats, it would be possible to reason and learn from a very wide range of data. 
      \end{kasten}

\begin{kasten}
    \section*{ \hspace{0.1cm} {\color{red} \underline{APPROACHES}} }
            \begin{center}
             \includegraphics[width=5cm]{Simplex-method-3-dimensions.eps}
            \end{center}
\begin{itemize}
\item
We need to understand {\em what information is lost}, using current methods,
when engineers document their designs and those designs are added to a repository. This is the
role of the {\em Tools Assessment} part of our work and is the
current task of Victor Mucino and Jim Mooney. 

\item
Our results to date show that we need to increase the amount of contextual and associational
knowledge captured with STEP designs when we add those designs to an archive.  Various 
{\em semantic visualization}
tools will be useful for this work and this is the current task of Tim McGraw.

\item
Even with our best knowledge capture tools, it is highly likely that some percentage of the technical
documents in the archive will be missing associational and contextual knowledge.
Information retrevial methods can be used to recover part of that missing knowledge. This is the
task of the {\em anything browser} work by Tim Menzies.

\item
Lastly, looking {\em over the horizon}, there are many other tools being developed to enhance
capture of semantic information; e.g. the {\em semantic web} work. Exploring this next generation of tools
is the task of Jim Mooney.
\end{itemize}
      \end{kasten}

    \end{spalte}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%               second column                  %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{spalte}

      \begin{kasten}

        \section*{1 \hspace{0.1cm} {\color{red} \underline{TOOL ASSESSMENT}} }

The STEP format (ISO-10303) for data exchange supports interoperability between
CAD/CAM tools. Yet only a few of the application protocols (APs) developed for
STEP are widely supported by mainstream CAD/CAM Software and industry. We
ask: how much relevant engineering data is lost through the use of STEP for archival
purposes?

To answer this question, we are building a framework architecture to provide a test-bed
for using STEP APs in conjunction with various commercial CAD/CAM software which
support STEP. Using the framework, we exercise various scenarios that require the
generation and transmittal of data and information amongst engineering tasks. We then
ask ``how much of the information in those scenarios is captured in STEP?''

            \begin{center}
             \includegraphics[width=8cm]{fig1.eps}
            \end{center}

      \end{kasten}

%      \begin{kasten}
%              \section*{2 \hspace{0.1cm} {\color{red} \underline{Support and Administration}}}
%                This task is responsible for the day-to-day coordination and communications of the project.  Among other logistical and reporting deliverables, this task oversees the creation of a website facilitating project coordination and synergy.
%
%            \begin{center}
%             \includegraphics[width=10cm]{fig2.eps}
%            \end{center}
%       \end{kasten}

      \begin{kasten}
        \section*{2 \hspace{0.1cm} {\color{red} \underline{THE ANYTHING BROWSER}}}
      %      \begin{center}
       %    \includegraphics[width=9.75cm]{fig3.eps}
        %    \end{center}
The anything browser is a {\em recommender system}.
Automatic constrast set and classification tools assist the user in finding relevant materials and excluding irrelevant materials.
Using the browser, some of the lost contextual and associational knowledge of a design can be recovered. 
The browser supports users
in their
 decision-making while interacting with large information spaces.
 They recommend items of interest to users based on preferences
 they have expressed, either explicitly or implicitly. 

Recommendation technology represents a new paradigm of search: 
interesting items find the user instead of the user explicitly searching for them: 
\begin{quote} {\em [We are.. ] leaving the era of search and entering one of discovery. What's the difference? Search is what you do when you're looking for something. Discovery is when something wonderful that you didn't know existed, or didn't know how to ask for, finds you. }-- M. O'Brien 
\end{quote}
            \begin{center} \includegraphics[width=9.75cm]{cycle.eps} \end{center}

      \end{kasten}

    \end{spalte}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%               third column                   %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{spalte}

      \begin{kasten}
        \section*{3 \hspace{0.1cm} {\color{red} \underline{SEMANTIC VISUALIZATION}}}
           This work levers the anything browser work. Recall that the anything browser team will build parsers for a diverse range of materials. Using mostly automatic methods, that range of materials will be explored for clusters and common classifications.
An alternative to the automatic filtering methods of the anything browser are visualization tools that display connections for users to browse.  That is, in the anything browser, the filtering intelligence is in the algorithms. In the semantic visualizer, on the other hand, the filter intelligence resides with the operator while the tool offers alternative views.

            \begin{center}
            \includegraphics[width=12cm]{multiresolution.eps}
            \end{center}
        
           The structure of large networks is typically conveyed by explicitly rendering nodes and arcs as geometric 
           entities. We propose to additionally utilize color and texture to convey structural information.
            \begin{center}
            \includegraphics[width=12cm]{stepgraph.eps}
            \end{center}

The graphical browser will permit visualization of the hierarchical
and semantic relations found in large document databases. New visual
representations of graphs will be developed to enhance understanding
of complex datasets. Fast response to user input will be achieved by
exploiting the parallel processing power of the modern graphics
processing unit (GPU).

       \end{kasten}
       
             \begin{kasten}
        \section*{4 \hspace{0.1cm} {\color{red} \underline{OVER THE HORIZON}}}
           This project will continue to track and analyze STEP as it is
evolving, and to identify future development most relevant for
long-term data retention (LTDR). The team will develop proposals for
extensions for STEP that may be presented to STEP developers for
consideration.

One area of active investigation among STEP researchers today is the
use of alternate representation schemes that may capture additional
semantic information, such as the OWL Web Ontology Language.
Participation in this study will determine the suitability of OWL or
related forms for capturing engineering information.

It is also recognize that STEP is not the only representation scheme
for engineering LTDR. An evident weakness in the use of STEP for
archiving engineering product data is that, with a few notable
exceptions, STEP is not being widely used as a representation for
current projects.  Among the reasons for this are:

\begin{itemize}
\item most aspects of STEP are not widely known,
\item the actual specifications are not available at reasonable cost,
and
\item there are few tools to enable the use of the full range of
STEP product data.
\end{itemize}
       \end{kasten}

    \vspace{0.5cm}

         \end{spalte}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%               fourth column                  %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    \begin{spalte}

      \begin{kasten}
        \section*{5 \hspace{0.1cm} {\color{red} \underline{SEMANTIC WEB}}}

        Much of the proposed research is focused on the STEP specifications as represented in the EXPRESS specification language.  However, it is expected that the work performed in 2008 will result in a detailed analysis of the STEP specifications as they exist today, and their suitability for long term retention of engineering data.  This project will continue to track and analyze STEP as it is evolving, and to identify future development most relevant for long-term data retention (LTDR). The team will develop proposals for extensions for STEP that may be presented to STEP developers for consideration.
One area of active investigation among STEP researchers today is the use of alternate representation schemes that may capture additional semantic information, such as the OWL Web Ontology Language1. Participation in this study will determine the suitability of OWL or related forms for capturing engineering information.
It is also recognize that STEP is not the only representation scheme for engineering LTDR. An evident weakness in the use of STEP for archiving engineering product data is that, with a few notable exceptions, STEP is not being widely used as a representation for current projects. Among the reasons for this are:

    \begin{itemize}
      \item most aspects of STEP are not widely known,
      \item the actual specifications are not available at reasonable cost, and
      \item there are few tools to enable the use of the full range of STEP product data.
    \end{itemize}

             \begin{center}
              \includegraphics[width=8.5cm]{fig5.eps}
             \end{center}
      \end{kasten}
      \begin{kasten}
         \section*{ \hspace{0.1cm} {\color{red} \underline{FOR MORE INFORMATION}}}
             Contacts:
           \begin{enumerate}
           \item Tool Assessment: Victor Mucino, Ph.D. \texttt{(victor.mucino@mail.wvu.edu)}
           \item Anything Browser: Tim Menzies Ph.D. \texttt{(tim@menzies.us}
           \item Advanced Graphics Tim McGraw, Ph.D. \texttt{(Tim.McGraw@mail.wvu.edu)}
           \item Over the horizon: James Mooney, Ph.D. \texttt{(James.Mooney@mail.wvu.edu)}
           \end{enumerate}
      \end{kasten}

      \begin{kasten}
         \section*{ \hspace{0.1cm} {\color{red} \underline{SUPPORT}}}
            \begin{center}
              \includegraphics[height=2.5cm]{era-logo.eps}~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              \includegraphics[height=2.5cm]{netl-c.eps}
             \end{center}
             This research as carried out at West Virginia University under a
            contract with the National Energy Technology Laboratory with funding
            from the National Archives Electronic Records and Archives.

            Reference herein to any specific commercial product, process, or
            service by trade name, trademark, manufacturer, or otherwise, does not
            constitute or imply its endorsement by the United States Government or NETL or
            the National Archives.
      \end{kasten}
    \end{spalte}
    }
    \end{lrbox}
\resizebox*{0.98\textwidth}{!}{%
  \usebox{\spalten}}\hfill\mbox{}\vfill
\end{document}


