Preparing for EGEE-III PEB meeting, 29 May 2007

Goals for today Transition from “review-mode” to “proposal mode” Discussion of NA1/EGEE-III mgmt structures Review of open issues Please communicate any developments in your activity PEB EGEE-III meeting, 29.05.07

Timelines May 31st: Deadline for partner bids June: Discuss partner bids with activity managers June 4/5: EB retreat June 11: PEB input on issues discussed today due Document ownership remains with EB; please provide text snipplets for integration June 18: call publication (provisionally) June 18/19: PMB retreat to discuss JRA1/SA3 and partner bids July 5/6: All-Activity meeting Review recommendations EGEE-III workshop together with PMB July 18/19: EB retreat Late August/Early September: PMB retreat (prov.) September 20: call closing (provisionally) PEB EGEE-III meeting, 29.05.07

FP7 Funding rules EGEE-III will be a I3 Requires SAs, NAs, and JRAs (mandatory!) SAs: 60% overhead, 100% funding (max) Mgmt: 60% overhead, 100% funding (max); max 7% of total budget (negotiable) JRAs: 60% overhead, 75% funding (max) NAs: 7% overhead, 100 funding (max) Might result in re-definition of certain NAs into SAs (NA3, NA4) We are currently ~10% over with PMs Further reductions might come due to partners policies with overhead! PEB EGEE-III meeting, 29.05.07

NA1 in EGEE-III PEB meeting, 29 May 2007

NA1 Management of the project Federation structure remains More Joint Research units (one partner per country model for academic institutes) Quality Assurance and Security Coordinators in NA1 Must ensure QA tasks are included in each activity New: Two scientific Officers will complete the picture PEB EGEE-III meeting, 29.05.07

New Boards Activity Managers Board (AMB) Evolution of current PEB Led by Project Director, scientific officer in charge of coordination and follow up Includes all activities, plus QA head, security head, RPLO Meets bi-weekly Technical “Administrative” matters: deliverable and milestone monitoring, events coordination, relations with collaborating projects, etc.) PEB EGEE-III meeting, 29.05.07

New Boards Technical Management Board (TMB) Evolution of current TCG Led by Technical Director, scientific officer in charge of coordination and follow up Builds on TCG experience: oversight and coordination of technical direction of the project Includes applications representatives, business representatives, members from the OAG, UIG, taskforces and other technical bodies Coordinate user community requirements Standards awareness Meets weekly to bi-weekly Quarterly: All Activity Meetings (combining TMB and AMB) PEB EGEE-III meeting, 29.05.07

Schematically Project Director, Technical Director Activity Managers’ Board Meets bi-weekly/Once per month All activities (Deliverable and milestone monitoring; QAG; Links to RPs, outside world; Reporting; Reviews; conferences) Project Director, Technical Director Technical Management Board Meet bi-weekly All activities Includes overlap with equivalents of OAG, UIG, SCG (MWSG, JSPG), taskforces Infrastructure Middleware Applications “Support” activities Training, dissemination, Policy, etc. PEB EGEE-III meeting, 29.05.07

Global management Project Director: Scientific strategic direction Project Oversight Board (TBC): advises PD EAC Collaboration Board Administrative Federation Committee PEB EGEE-III meeting, 29.05.07