PI Institution: <INSTITUTION>
ECSS Expert: <ECSS staff> (Lead expert 1st) [Other ECSS experts can be identified after plan is finalize.]
Allocation Start/End dates: <START DATE – END DATE> (This is at most 1 year.)
Objective: (Give a concise statement of the objectives (goals) for the extended collaborative support project.)
Sustainability: (Give a statement addressing the sustainability (perpetuation) of the products of the collaborative support. Quite important for ESCC and ESGW.)
Final Goals: (A tangible product of the collaborative support. These may include but are not limited to application software (installation, optimization, porting, or feature incorporation), documentation, and reports. Optionally, if these goals can be categorized into multiple tracks which belong to different areas within ECSS such as ECRT, ECCC, or ECGW then identify the membership of each deliverable.)
- <GOAL #1> - <Optional area such as ECRT, ECCC, or ECGW>
Intermediate goals (milestones) with anticipated timetable: (At least one milestone should be provided for each quarter. The intent is that all final goals must be addressed by at least one milestone. The fulfillment of all milestones should result in the delivery of project final goals. A milestone is a quantifiable metric used to gauge progress toward a deliverable. Optionally, if deliverables can be categorized into multiple, simultaneous tracks then identify the membership of each milestone. Final two milestones concerning Final Reports and PI Interview are static and required.)
- <MILESTONE #1> - <Optional reference to deliverable number>
- Success: <SUCCESS METRIC> (Give a short description of the metric used to gauge success. This should be quantifiable and not subjective.)
- Effort: <EFFORT ESTIMATE> (Give a short description of the effort expected for this task in terms of time and tasks)
- Estimated completion: <DATE/QUARTER> (Give the expected completion date or quarter.)
- Final Report creation and submission
- Success: Creation and submission of a final report detailing scope, impact, and nature of work performed during the project period.
- Effort: no more than 2 weeks of effort
- Estimated Completion: <MONTH after END DATE>
- PI Interview by ECSS management
- Success: Participation in an interview with ECSS management to access and give feedback concerning the quality and impact of work performed during the project.
- Effort: no more than 1 hour
- Estimated Completion: <3 MONTHs after END DATE>
Resources: (Resources list the personnel, their percent effort, and assigned tasks in order to complete project milestones and deliverables. All project milestones must be addressed by at least one assigned personnel from ECSS Staff or Project Group. This should be a collaborative effort with equitable tasks/responsibilities from ECSS staff and the project group.)
- ECSS Staff – <STAFF with timeframe and % Effort> (Give a list of ECSS staff and their expected % efforts) If staff is not yet identified, that is ok; just use a placeholder with the expected tasks.
- <TASK/RESPONSIBILITY #1> - <RESPONSIBLE EXPERT(S)> (Give the task or responsibility and the assigned staff.) (List sub area of ECSS)
- <TASK/RESPONSIBILITY #2> - <RESPONSIBLE EXPERT(S)> (Give the task or responsibility and the assigned staff.) (List sub area of ECSS)
- Project Group – <PROJECT GROUP MEMBERS and Timeframe> (Give a list of Project group members (distinct from ECSS Staff) who will collaborate on the project and their availability in terms of dates or quarters.)
- <TASK/RESPONSIBILITY #1> - <RESPONSIBLE CONTACT(S)> (Give the task or responsibility and the assigned group member or members.)
- <TASK/RESPONSIBILITY #2> - <RESPONSIBLE CONTACT(S)> (Give the task or responsibility and the assigned group member or members.)
Benchmark: If you will be doing any optimization or efficiency improvements, please pick a representative benchmark problem that you will run at the beginning of the project to set a baseline (or keep around the original code base to the end) and at the end of the project to quantify speedup. It might be best if you quantify the speedups for both the individual routines touched AND the entire code for the benchmark problem.
Risks Analysis: [Optional] (The risk analysis lists reasonable risks that would cause complications in the successful fulfillment of milestones and/or deliverables by their expected completion dates. The mitigation gives the expected action or actions necessary to either complete the milestone/deliverable or to ensure other milestones/deliverables are not adversely impacted. These may include changing expected completion dates, the removal of deliverables/milestones, or the inclusion of additional milestones/deliverables.)