From lri-general-Request@N3.SP.CS.CMU.EDU Thu Feb  2 11:39:17 1995
Date: Thu, 2 Feb 95 11:33:08 EST
From: Eric.Krotkov@IUS4.IUS.CS.CMU.EDU
To: lri-general@IUS4.IUS.CS.CMU.EDU
Subject: new proposal due data (from lavery)
Content-Length: 5347
Status: RO
X-Lines: 102

Date: Thu, 02 Feb 95 00:22:06 EST
To: triwgmem@telerobotics.jpl.nasa.gov, triwgbig@telerobotics.jpl.nasa.gov
Subject: Proposal preparation

Dear TRIWGers: 

Dave Akin made me aware of a typo in the proposal abstract response
message I sent out last week.  The message incorrectly says that
proposals are due on February 20.  However, we had all agree at the
December TRIWG that proposals would be submitted by February 10 to
allow enough time for everyone to review the submissions prior to the
meeting at KSC.  This was restated in the proposal abstract call
message on December 15, 1994.  The February 20 date in the last
message was a typo, and does not reflect the agreed submission date.

However, this may have caused some confusion already, so I would like
to suggest a compromise (OK, it is not really a suggestion as much as
a directive, but hey, somebody has to do it...).  All proposals must
be submitted by close of business on February 15.  This will allows
those who were working toward the Feb 10 date to have a little bit of
slack, while those who read the Feb 20 date can still get their
proposals done without killing themselves in the effort.

As discussed at the December TRIWG, we will use the same process for
proposal submission as last year.  Proposals are to be submitted
electronically via anonymous ftp to robotics.jpl.nasa.gov, to the
/incoming/ directory.  In the event that you do not have anonymous ftp
access to the JPL site, you can alternately e-mail the proposals to
Chuck Weisbin and myself by the deadline (please consider this a
second choice submission method, use the ftp process if at all
possible).  Access to the /incoming/ directory will be suspended at
the end of the day on the 15, so your proposals must be in on time.
LATE PROPOSALS WILL NOT BE ACCEPTED - NO EXCEPTIONS!

The proposals must be in Microsoft Word-compatible format, and are
limited to no more than 10 pages in length.  Any displayed schedules
or pictures should be included in the transmitted Microsoft Word file
to allow faithful inclusion in the final package.

Each proposal should contain the following sections:

    -   OBJECTIVES (describing the technical challenges)
    -   JUSTIFICATION (identifying the customer)
    -   APPROACH (how the work will be conducted)
    -   PARTICIPANTS (partnerships)
    -   DELIVERABLES (a schedule with proposed quantifiable milestones:
        quantifiable in terms of increased speed of operation, increased
        operational accuracy, reduced cost, etc.)
    -   COMMERCIALIZATION POTENTIAL (technology transfer opportunities)
    -   FUNDING (requested $/yr for all participants)
    -   FACILITIES (where the work will be performed)
    -   PRINCIPAL INVESTIGATORS (name, organization, phone, fax, e-mail,
        mail address)

Proposals will be evaluated on the basis of metrics which include:
    a. degree of user support
    b. technical innovation
    c. time required for operational use
    d. commercialization potential
    e. required budget
    f. deliverables (quantifiable improvements: increased speed of operation,
increased operational accuracy, reduced cost, etc.

Please ensure that the metrics are highlighted in the proposal descriptions. 

Full proposals for all new activities and continuation tasks are
required.  Continuation proposals should highlight any significant
changes in milestones, schedules or funding from last year's
submission.  Continuation proposals for the university baseline grant
activities are also to be prepared.  Although we will do the detailed
university reviews at the summer meeting, we need to get proposals in
to plan placeholders for the budget and milestone activities.

JPL will integrate the received proposals together into a single
package, and make it available for electronic distribution by February
17.  A file containing this package will be available for ftp
retrieval from robotics.jpl.nasa.gov in directory /home/pub/triwg.

For the TRIWG meeting itself, the majority of the time will be given
to reviewing the new proposals, with approximately 30 minutes
discussion per proposal (this may be modified to fit the schedule
based on the final submission count).  Continuation proposals will be
reviewed for approximately 10 minutes each, with an emphasis on any
changes from last year's plan.  For each proposal, you should only
bring two charts to the TRIWG meeting; a quad chart using the standard
format (illustration or photo in the upper left, objectives and
deliverables in the upper right, principal investigator, participants
and facilities in the lower left, schedule, milestones and budget in
the lower right), and a full-page photo or drawing of the subject (I
will be collecting the two charts, so bring extra copies if you only
have one set of originals).

There will be no "presentation" of the proposals - the entire time
will be dedicated to review comments and discussion.  As with prior
years, this means that everyone will have to come to the meeting fully
prepared, with all proposals read and questions/comments ready.  A
tentative agenda for the meeting will be put together shortly and sent
out, along with details on hotels, meeting room location, etc.
Non-NASA employees planning to attend the meeting should contact Todd
Graham at KSC soon to arrange access to KSC for the meeting.

-dave