TERENA Planning Cycle

1. TERENA Planning Cycle Claudio Allocchio TERENA VP Technical Programme TERENA GA Copenhagen

2. One year ago, GA 18 in Prague • Brainstorming discussion about the Geoff McMullen report • Still a lot of uncertainities about FP6 activities • Common Understanding of problems existing in the financial support for TERENA Porjects • Attempt to Create an adaptive mechanism for the Project discussion, and Support gathering. • First revision to happen in GA 19, Zagreb • First year experience review in GA 20, here NOW! TERENA GA Copenhagen

3. Recommendation 5 • Implement the recommended approach in 2003 (as year 0 of the recommended cycle), to have its full effect for 2004. Again, we agree in principle. We would, however, like the views of the GA on the question of whether TERENA should adopt a fixed cycle (say 3 years) or a continuous (“rolling”) cycle. TERENA GA Copenhagen

4. Recommendation 7 • Seek a system of collaboration with DANTE for project planning at the level of Chairman of the Technical Committee. This seems to be a good idea, and will be pursued. TERENA GA Copenhagen

5. Proposed 2003 schedule • Call for proposals for activities in the 2004 Technical Programme – to be issued in January 2003 • Session in the Zagreb Conference where all activities (~10??) are presented • Strengthened TTC (and TAC or Technical Committee?) deliberations, leading to recommendations on projects to be supported in the 2004 budget. Final recommendation prepared by the Technical Committee (or re-mandated TAC?) the day before the Autumn GA meeting. • Final decisions on 2004 Technical Programme and 2004 TERENA budget taken at the GA meeting in ~October 2003 TERENA GA Copenhagen

6. Annual cycle consists of:- • Open meeting at Annual Conference for Information Exchange • Session at Annual Conference for new ideas and review of SIAs • General lines discussed and approved by GA • Over Summer- • Scientific review • interactions and clarification with people pushing new ideas or responsible for general areas of activity • If needed organise a meeting in TERENA office at end-Sept/early Oct to look at priorities. Paper to GA • Open meeting day before GA, with recommendations TERENA GA Copenhagen

7. Recommendation 5 • Implement the recommended approach in 2003 (as year 0 of the recommended cycle), to have its full effect for 2004. We decided to implement a 3 years rolling cycle and to verify its viability and effects. TERENA GA Copenhagen

8. Recommendation 7 • Seek a system of collaboration with DANTE for project planning at the level of Chairman of the Technical Committee. We started a more global interaction, also at the level of TEC/BoD. We will however go further also on the specific suggestion above. TERENA GA Copenhagen

9. 2003 schedule (1) • Call for proposals for activities in the 2004 Technical Programme – to be issued in January 2003 • 3 proposals received • 2 were off-topic • 1 was already a full blown project proposal • People engaged in FP6 preparation • Informal requests from FP6 projects TERENA GA Copenhagen

10. 2003 schedule (2) • Session in the Zagreb Conference where all activities are presented • 1 project proposal for TERENA funding (PAPI/PERMIS integration) • 3 FP6 proposals • EGEE, GARDEN, GRANDE • Good interaction with audience and among proposal presenters TERENA GA Copenhagen

11. 2003 schedule (3) • Strengthened TTC (and TAC or Technical Committee?) deliberations, leading to recommendations on projects to be supported in the 2004 budget. Final recommendation prepared by the Technical Committee (or re-mandated TAC?) the day before the Autumn GA meeting. • Joint meeting TEC/TTC in June • The only TERENA project proposal was considered "not elegible for funding" • Useful discussion about FP6 projects and more close TEC/TTC interactions TERENA GA Copenhagen

12. 2003 schedule (4) • Final decisions on 2004 Technical Programme and 2004 TERENA budget taken at the GA meeting in ~October 2003 • … here we are… • But no proposals for TERENA funded projects to discuss • The big scenario has quite changed • TERENA inside EGEE, GN2, GARDEN, GRANDE, MOME • In next years (less FP6 impact) might be different TERENA GA Copenhagen

13. Theory vs Reality • We must be realistic, and adapt plans to circumstances • Our activities depends a lot also on "external factors" (EU, International collaborations, …) • Some pieces of the plan resulted in positive results • Some other pieces could work better in near future, under different scenarios TERENA GA Copenhagen

14. To keep… or not to keep? • Call for new ideas and proposals • In non FPx years it might get more answers! • Useful to stimulate GN2 JRA proposals? • Helps preparing TAC and TNC session • Open Meeting/Session at annual conference • Depends on previous result of the call • Useful also as large project or JRA interaction TERENA GA Copenhagen

15. To keep… or not to keep? • Spring GA discussion of proposals • If we have proposals ! • Summer TTC/TEC joint meeting and review • Useful more for general awarness and information exchange • It helps also for hard decisions TERENA GA Copenhagen

16. To keep… or not to keep? • September TEC/TTC joint meeting for priorities • Given current and probable future funding pattern, no! • Autumn GA discussion of budget for proposals • … see above TERENA GA Copenhagen

17. Conclusion (?) • Do not adopt a "rigid" planning schema • Save and use portions of the schema, at the time when they are useful • TERENA budget is currently much more influenced by other factors • Follow the community attitude of the moment, and try to serve it, also in this field. TERENA GA Copenhagen

18. Thanksor Vegetables? TERENA GA Copenhagen