 |
Workers: Proposal |
Statement from Mary Anne
I have talked with most of you recently regarding project renewals. For renewals,
the usual approach is to submit a renewal application at least six months before the
completion of the original project term. (For most of you that would be by the end
of January 2004.) For projects that include university participants, you need to refer
to the first two notices on the DOE SC Grants and Contracts page. The first outlines areas
of research for which unsolicited proposals can be submitted and the second addresses the
renewal grants. These are
http://www.sc.doe.gov/grants/Fr04-01.html
http://www.sc.doe.gov/grants/Fr04-02.html
For the latter, please note the three items called out in addition to the standard contents - these
are on:
- research changes
- anticipated unexpended funds
- the progress report section
I would expect that there would be minimum unexpended funds. The length of the progress report
section can be minimized by referencing your web pages for the quarterly reports. However, I would
expect that reviewers would like to see a strong summary statement.
You should also be aware that we now deal with electronic proposals. The Grants and Contract page
covers that issue as well. If your project does not include a university participant, the renewal
applications should be sent directly to me.
All renewal applications will be peer-reviewed.
Proposal Outline
The Complete Application Guide is available.
Note, the DOE Guide to Application Contents is
available here.
Last time our limit was 20 pages for the Project Description. I am assuming the same limit applies
for our renewal but I am checking with Mary Anne.
For your writing: Times, 10 pt, line spacing exactly 12 pt, first line indent 0.25".
Name next to each item is the responsible person but clearly some writing will
have to be jointly conducted.
My thoughts are in italics.
FusionGrid: An Enhanced Collaborative Environment for Magnetic Fusion Research
Version 1 of Technical Narrative (1/18/04)
Version 1a of Technical Narrative (1/20/04)
Version 2 of Technical Narrative (1/22/04)
Version 2a of Technical Narrative (1/23/04)
Version 3a of Technical Narrative (1/27/04)
Version 3b of Technical Narrative (1/29/04)
- Face Page
- Budget: include report on unexpended funds
- Progress Report
- Project Description (19 out of 20 pages total allocated)
- Executive Summary (1 page, Schissel)
- For the busy person, one page that tells it all
- Introduction, Vision, and Architecture (2 page, Schissel)
- The Collaborative Control room and how all apects of our work
are involved. Pre-experiment computing include large simulations,
the experiment with comparison to simulation real time, post-experiement
computing. Press here the comparison of experiment and simulations.
- Applicability to other sciences? Put this as different section, say at the end.
- We engage user community - take credit for this either here or later.
- Collaborative Computation and Control Room: Presentation Technology (7 pages)
- New Computational Services (1 page)
- TORIC (0.5 pages, Greenwald)
- Gyro (0.5 pages, Schissel)
- Visualization (1 page, Sanderson)
- Robust, easy to use SCIRun.
- Control Room Presence
- Application Sharing (2 page, Papka/Wallace)
- Collaborative Computation and Control Room: Supporting Technologies (4 pages)
- Authentication/Certificates (0.5 pages, Thompson)
- GT2 to GT3, certificates easier to use.
- Authorization, Resource Management, Enforcement (1 page, Thompson)
- Monitoring of Fusion Grid Services (0.5 pages, McCune)
- Better interface (Flanagan), Elvis
- Data Management (1 page, Fredian)
- MDSplus at NERSC testing, XIO, GridFTP
- Agreement Based Resource Management (1 page, Keahey)
- Between shot data processing including simulations.
- User Support, Documentation, and Software Release (2 page, Burruss)
- This is mostly the GA writeup but clearly there are pieces for
others here as well.
- Research changes that effect original research endeavor (0.5 page, Schissel)
- What changes have been made between grant 1 and grant 2 in direction (size, scope).
- Management Plan (0.5 pages, Schissel)
- User oversight committee, etc.
- Statement of Work and Schedule-Task based,
User based (2 page, Schissel)
- High level but clear Year 2 deliverables. Link to Web for details.
- Biographical Sketches of Key Personnel
- Facilities and Resources
- Current and Pending Support
- Appendix
- Letters of Support
- Definitions and/or Glossary of terms
- Figures