In addition, to provide direction to the RFP and subsequently to the proposal developer (the professor and/or students), please define the requirement (if any) for the use of the particular task:

if a particular task/approach is to be followed and proposals that do not plan to use this task will not be considered, so state;
if a particular task is suggested but alternate tasks can be proposed, so state;
if the task is to be determined by the proposer (the professor and/or students), so state, e.g., include a statement like the following:

· [ ] The anticipated task must be used in this study,

· [ ] alternative tasks may be proposed (by the professor and/or students), and will be considered,

· [ ] best task is unknown at this time and is to be included in proposal (by the professor and/or students).

Include a list of the major tasks that will likely need to be completed by the professor and/or students in order for the research to yield the desired results. This list will help in the determination of the size/scope of the project and help assure that it is properly evaluated for inclusion in this program’s RFP, preparation of efficient proposals by the professor and/or students, and will help in the evaluation of any/all proposals received by the professor and/or students. Any/all information concerning the tasks (existing/previous studies/data, …) will enable a more efficient project, if funded.

Below is a list of example activities included for your use (but are not limited to):

{You can leave in the ones you want to keep, cut the ones you will not use and add others that you desire to have}

Kick-off and other Meetings/Interactions with OC-ALC Sponsor
Development and Review of Methodology and Data Requirements
Data Gathering – Current Operations

Interviews
Observation
Use/Conversion of Existing Data

Generation of Solution Alternatives
Review/Preliminary Evaluation of Alternatives
Data Gathering for Selected Alternatives

Interviews
Observation
Use of Existing Data
Construction and Evaluation of Prototypes

Number to be Constructed
Evaluation/Testing of Prototypes

Analysis of Selected Alternatives
Selection of “Best” Alternative
Development and Submission of Final Report and Briefing

4.0 Anticipated Schedule

Please provide the anticipated Project Period of Performance. For the 2003 CASI program, the following schedules/periods of performance are allowed if you have no idea then so state and it probably can be figured out by your expected tasks descriptions (you may wish to include this list and check all of the periods of performance that you would accept, i.e.) (note: during the summer the professors can work on the project fulltime but during the academic year they can only work part time):

[X] Execution and Completion of Project between June 1 and August 31, 2003.

[ ] Execution and Completion of Project between June 1 and May 31, 2004

[ ] Executed as a single project, or

[ ] Executed in two or more phases with an intermediate set of deliverables and successful completion of the intermediate deliverables required before funding successive phase(s). NOTE: CASI research phases will normally have completion dates that correspond to the academic researcher’s semester schedule, i.e., August 15 or December 31.

[ ] Execution and Completion of Project between August 15, 2003 and May 31, 2004

[ ] Executed as a single project, or

[ ] Execution as the first phase of a multi-year project. NOTE: Due to funding mechanisms, only the effort between June 1, 2003 and May 31, 2004 can be funded by the 2003 CASI program. The project must produce a set of intermediate deliverables at the end of the 2003 funding cycle and funding of successive phases/years is contingent upon funding availability, project priority, and performance.

5.0 Anticipated Deliverables

List the potential deliverables of this project, what you expect to get when this project is over (report, plans, prototype, proof of concept, etc.)

6.0 Anticipated Benefits

List the potential benefits offered by this project and quantify them if possible.