OSG Project Manager Report for OSG Council Meeting August 5, 2008 Chander Sehgal

August 5, OSG Annual Report In partnership with Paul Avery and with great support from the OSG team and the Science stakeholders, we completed and submitted the OSG Annual Report on July 18, 2008; the report is stored in DocDB as document number 770-v2 and can be viewed at Next year we plan to complete the report in mid-June.

August 5, Endorsement of Agreement VDT Support for WLCG An agreement has been proposed between OSG and WLCG to provide support of the VDT The OSG Council is asked to review and endorse this agreement.

August 5, Financial Update OSG supplemental proposals to DOE approved & funding to UW- Madison is in-progress  Move Security work from SLAC to UIUC-NCSA ($138K per year)  Restore $78K metrics holdback DOE Funding for 4/1/2008 to 3/31/2009  HEP received across universities and national labs  NP received for national labs  ASCR funding received for universities; needs to be confirmed for national labs NSF Funding for year3 expected very shortly NSF institutional sub-contract “no cost extensions” processed for all continuing institutions (not RENCI nor Cornell) till 3/31/2009 Overall institutional spending at 65-70% of plan for first 7 quarters (complete analysis pending inputs from certain institutions on costs incurred as of 30Jun08)

August 5, Budget Planning for Year3 Cornell funding terminated due to staff loss RENCI funding not needed due to CI-Team Award Columbia funding for South Africa outreach on-hold pending change control request (most likely to be re- directed to South America outreach program via another OSG institution) Draft year3 budget suggests adequate funds to meet currently understood work needs; and we can tap into “savings” from institutions to meet additional needs as they become evident

August 5, OSG Year3 Planning - Overview Goals and Work Plans developed by Area Coordinators with support from Project Manager based on  Strategic Drivers from OSG-ET and their own experience and expertise with OSG and Grid Computing  Feedback from OSG DOE/NSF Review  Original OSG Proposed Work Plan  Process improvements based on year1 and year2 experience and feedback  Incomplete work items from current year OSG-ET provides strategic input, reviews high-level goals, and approves the WBS, budget, and staffing OSG Council endorses WBS, budget, and staffing plans

August 5, Approach to Work Items OSG Work items can be classified into four categories 1.Maintaining and Sustaining the OSG 2.Work directly supporting the Science Communities (e.g. LIGO, US-CMS, ATLAS, etc.) covering immediate and long-term needs 3.Enhancing the OSG based on experience and feedback from stakeholders, technology evolution, and best practices 4.Addressing the feedback from the Jan 23 NSF/DOE review Flag work items with these categories to enable traceability and provide handles for prioritization, if needed; evaluate total work program for coverage against these categories

August 5, OSG Year3 Planning - Status Kick-off at Area Coordinators Meeting on June 5 Key Project Drivers shared on June 26 at OSG-ET V2.ppt Discussions with Area Coordinators completed to frame high-level goals Reviews of high-level goals with OSG-ET in-progress and expected to completed Aug 7 Progress is currently ~3 weeks behind planned schedule

August 5, OSG Area Coordinators * 1.0 Science Goals and Requirements – Ruth Pordes * 2.0 Facility – Miron Livny * 2.1 Software – Alain Roy * 2.2 Operations – Rob Quick * 2.3 Integration & Sites – Rob Gardner * 2.5 Engagement - John McGee * 2.6 Campus Grids – Sebastien Goasguen * 3.0 Security – Mine Altunay * 4.0 Extensions, Applications, & Users - Frank Wuerthwein, Torre Wenaus * 4.1 Scalability, Reliability and Usability – Frank Wuerthwein * 4.2 Work Load Management – Maxim Potekhin * 4.3 Users Support – Abhishek Rana & Britta Daudert * 4.4 Storage Management – Ted Hesselroth * 4.5 Internet2 Network Monitoring – Richard Carlson * 5.0 Education & Training – Alina Bejan * 6.0 Project Administration – Ruth Pordes * 6.1 Metrics – Brian Bockelman * 6.2 Communication & Coordination – Ruth Pordes * 6.3 Resource & Project Management – Chander Sehgal

August 5, Year3 Planning Mechanics a.Capture the Key Project Drivers & Share with Area Coordinators as input and catalysts for their year3 goals b.Area Coordinators work with Project Manager to document high-level goals for review and approval c.Project Manager works with each Area Coordinator to detail WBS, staff, and budget across institutions d.Project Manager prepares draft staff plan, budget plan, and WBS for review by OSG-ET and OSG Council e.Project Manager writes SOWs and baselines budget and WBS f.Project Manager and Executive Director write project execution plan

August 5, Year3 Planning High-level Schedule Work ItemPlanned Completion Date Document Key Project Drivers a.Goals & Plans of the experiments b.OSG Strategic Drivers c.Feedback from DOE/NSF review d.Input from Original Proposal of Work June 15 Share Key Project Drivers with Area Coordinators to guide their goals; capture high level Area Coordinator Goals; complete review of these goals by OSG-ET June 30 Year3 draft WBS, staff plan, budget planJuly 30 Year3 WBS, staff plan, budget plan approved by OSG CouncilAug 30 Draft SOWs ready for approvalSept 30 Project Execution Plan Document Ready for OSG-ET ApprovalOct 15 Baseline Budget, WBS, Project Execution PlanOct 30 85% of SOWs ready for Institutional SRO sign-offNov 15

August 5, Year3 Planning – Next Steps Complete Review of Area Goals with OSG-ET Detail deliverables (WBS) and staffing by area Construct draft institutional budget Review Plan with OSG-ET and OSG Council Write SOWs and execute approval process Write Project Execution plan  baseline WBS and Budget