Eric Prebys LARP Program Director 1/8/09.  Background  Summary of review findings  Partial response  Coordination with CERN  New initiatives  Lumi.

Slides:



Advertisements
Similar presentations
Facilitated by Joanne Fraser RiverSystems
Advertisements

Identify Problems, Planning Objectives and Constraints.
US CMS DOE/NSF Review: May 8-10, US CMS Cost & Schedule Mark Reichanadter US CMS Project Engineer DOE/NSF Review 8 May 2001.
Campus Improvement Plans
Developing a Basic Program Budget Harkmore Lee, CALCASA.
Decision Making Tools for Strategic Planning 2014 Nonprofit Capacity Conference Margo Bailey, PhD April 21, 2014 Clarify your strategic plan hierarchy.
Chesapeake Bay Program Goal Development, Governance, and Alignment Carin Bisland, GIT6 Vice Chair.
Chesapeake Bay Program Goal Development, Governance, and Alignment Carin Bisland, GIT6 Vice Chair.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Cost, Schedule & Funding Closeout Jan Joint DOE/NSF CD2/3a Review 1 DOE/NSF Review of the Dark Energy Survey (DES) Project SC 6/7 Cost, Schedule.
1 LBNL Enterprise Computing (EC) January 2003 LBNL Enterprise Computing.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Project Management Session 7
Iterative development and The Unified process
Release & Deployment ITIL Version 3
S/W Project Management
Eric Prebys LARP Program Director 1/8/09.  This meeting will be both and update and an official response to the review of LARP which took place at LBNL.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
Global Design Effort U.S. ILC Cost Translation R. Stanek, et al. Vic Kuchler 1/26/07.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
PLANNING AND SCHEDULING
December 14, 2011/Office of the NIH CIO Operational Analysis – What Does It Mean To The Project Manager? NIH Project Management Community of Excellence.
AARD Sub-panel at Fermilab Feb , 2006 LARP Magnet R&D Program - S. Gourlay1 BNL -FNAL - LBNL - SLAC LARP Magnet R&D Program Steve Gourlay AARD Sub-Panel.
OFFICE OF SCIENCE 1 3. Cost Estimate Gines, Fisher 2.Are the estimated cost and proposed schedule ranges realistic, consistent with the technical and budgetary.
Private & Confidential1 (SIA) 13 Enterprise Risk Management The Standard should be read in the conjunction with the "Preface to the Standards on Internal.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
Eric Prebys LARP Program Director Jaunary 14, 2009.
J. G. Weisend II Deputy Head of Accelerator Projects April 2, 2014 Actions at ACCSYS Resulting from the Recommendations of the Annual Review.
 Guidance from DOE  $13M with a 6 month continuing resolution at 84%.5*.84*13+.5*13 = $11.96M  Separate money ($1-2M) found for APL planning!  General.
January LEReC Review 12 – 13 January 2015 Low Energy RHIC electron Cooling Kerry Mirabella Cost, Schedule, Personnel.
 Good  LARP has grown significantly in size since it started  Gained credibility both here and at CERN US Labs like it as a way to support work CERN.
Lab Coordination Meeting 9/25/13Introduction – G. Sabbi 1 Magnet Development Plan Update Overview GianLuca Sabbi LARP Lab Coordination Meeting September.
Eric Prebys LARP Program Director 4/8/09.  All meetings will take place in Chardonnay room (partitioned for parallel sessions).  Wireless available.
Commodity Node Procurement Process Task Force: Status Stephen Wolbers Run 2 Computing Review September 13, 2005.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Project Management Methodology
Eric Prebys LARP Program Director 7/13/09.  Background  Summary of findings from last review  Partial response  Coordination with CERN  New initiatives.
Eric Prebys Accelerator Physics Center Program Director, LARP December 7, 2009.
1 BNL LARP Accelerator Physics Program Resources BNL role in national program BNL Accelerator Physics Program.
Lesson 1: Examining Professional Project Management Topic 1A: Identify Project Management Processes.
J. Strait Fermilab 16 October 2006 Consideration on LHC upgrade from A US perspective.
Eric Prebys 10/28/2008.  Generally, I thought this was a productive meeting  Lots of useful discussion  Would still rather have all plenary More specifically.
1 Voluntary and Community Sector Review Voluntary & Community Sector Review Grants Strategy Working Party Participative Session 28 September 2006 Appendix.
LARP Accelerator Systems 6-Year Plan FY09-FY14 10 April 2009 LARP CM12 Napa, CA Tom Markiewicz/SLAC BNL - FNAL- LBNL - SLAC US LHC Accelerator Research.
US LHC Accelerator Research Program (LARP) Background  Proposed in 2003 to coordinate efforts at US labs related to the LHC accelerator (as opposed to.
1 Global Design Effort: Controls & LLRF Controls & LLRF Working Group: Tuesday Session (29 May 07) John Carwardine Kay Rehlich.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
Eric Prebys LARP Program Director January 14, 2009.
LARP Collaboration Meeting April BNL -FNAL - LBNL - SLAC Status Report E. Harms 28 March 2006.
MGT 461 Lecture #27 Project Execution and Control Ghazala Amin.
Management February 20, Annual Review of the Muon Accelerator Program (MAP) Subcommittee members: Ron Prwivo, Ron Lutha, and Jim Kerby.
U.S. Activities on the High-Luminosity LHC: LARP Sustainability & Evolution as a Construction Project HiLumi-LARP Collaboration Meeting October 26, 2015.
Eric Prebys LARP Program Director July 14, LARP FY10 and Beyond - E. Prebys 2 Guidance: LARP funding decreases $1M/yr Assume: $13 M LARP total for.
LARP Review, June 12-14, 2006 Prebys, Todesco, Zisman 1 Accelerator Systems Eric Prebys Ezio Todesco Mike Zisman.
 Presented ongoing activities in LARP  Magnet Systems  Accelerator Systems  Program Management  Also presented plan for “spinning off” construction.
Implementing Program Management Standards at Duke Energy.
Eric Prebys, Fermilab Director, US LHC Accelerator Research Program (LARP) May 16, 2011.
Eric Prebys, Fermilab Program Director, LARP July 10, 2012.
The HiLumi LHC Design Study is included in the High Luminosity LHC project and is partly funded by the European Commission within the Framework Programme.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
Outcomes, Values and Priorities Workshop 1 Redesign Board 10 th May 2016.
LARP Crab Cavities Cryomodule Integration Meeting Final Notes A.Ratti LBNL.
Eric Prebys Accelerator Physics Center Program Director, LARP Important material Contributed by Elliott McCrory (FNAL), Ryoichi Miyamoto (BNL), Alan Fisher.
LARP Accelerator Systems D. Rice, J. Rosenzweig, M. White LARP 2009 review.
MQXF Planning Paolo Fessia, Frederic Savary, Ezio Todesco, Lucio Rossi - CERN Mike Anerella, Peter Wanderer - BNL Giorgio Ambrosio, Mark Kaducak - FNAL.
S4 will be a “big” Collaboration:
Project Management Process Groups
Presentation transcript:

Eric Prebys LARP Program Director 1/8/09

 Background  Summary of review findings  Partial response  Coordination with CERN  New initiatives  Lumi situation  FY09 Budget  Budgeting process  Budget status  Planning for the future  FY10 and beyond  Base lining LARP  crabs cavities?  PS2?  Relationship with APUL (or eq.) 1/8/09 E. Prebys, LARP DOE Meeting 2

 This meeting will be both and update and an official response to the review of LARP which took place at LBNL in June  Although the report was only recently released, the contents are largely consistent with the closeout comments from the review, so there are no big surprises.  For the most part, we are in agreement with the recommendations, and feel we have taken significant steps to address them.  We have our annual LARP/CERN meeting at CERN on Jan. 14, and are interested in useful feedback for this meeting. 1/8/09 E. Prebys, DOE/LARP Meeting 3

 Generally impressed with LARP progress on technical fronts.  Particularly success of Schottky and tune tracker  As usual, reminded us that the Nb 3 Sn magnet program is a world class effort which must be sufficiently supported.  Some concern over convergence of the shell and collar efforts.  Some specific comments on conductor choice.  Concern over communication with CERN  Particularly regarding the JIRS work  Concern about managerial oversight  Primarily regarding the lumi project, which was news at the time.  Although there was some frustration during the review about how LAUC (now “APUL”) was “thrown at them”, they generally felt it was a good idea and should be separately and sufficiently funded.  The exact relationship between LARP and APUL will be one of the topics for discussion at this meeting. 1/8/09 4 E. Prebys, DOE/LARP Meeting

 The bulk of the criticism in the report focused on the perceived “disconnect” between LARP and CERN regarding prioritization of LARP activities.  I believe this disconnect largely referred to activities related to the abortive attempt to get Nb 3 Sn magnets into the Phase I proposal (specifically, the JIRS group).  It's now realized this is not (and likely never was) realistic. We have suspended activities of the JIRS group, with the idea of restructuring it with an emphasis on the relationship between our magnet program and the phase II upgrade. 1/8/09 5 E. Prebys, DOE/LARP Meeting

 General  LARP Liaison: Oliver Bruening Serves as primary “sounding board” for LARP proposals De-facto veto power over LARP projects (No CERN interest= non-starter)  US/CERN meeting Once a year (Coming up Jan 14) Discuss general priorities and strategy Should we do this more often?  LTV/Toohig fellows Establish a significant body of “man on the street” impressions of CERN interest 1/8/09 6 E. Prebys, DOE/LARP Meeting

 Specific  Alex Ratti has been working closely with Enrico Bravin (responsible for LHC luminosity measurement) on the completion and handoff of the lumi monitor  Rama Calaga is working closely with CERN people to coordinate crab cavity effort  Tom Markiewicz is working closely with Ralph Assmann (head of LHC collimation) on the potential use of the rotatable collimators  Uli Wienands has been working with Oliver Bruening and CERN in general to identify the best ways for LARP to contribute to the PS2 effort. 1/8/09 7 E. Prebys, DOE/LARP Meeting

 In response to comments from the review committee and LARP members, Tom Markiewicz developed a more formal and transparent process for choosing among new initiatives.  Proposals were weighted by a number of factors, including CERN interest (necessary), potential luminosity improvement, technical risk, and cost.  LARP collaboration was ed a prioritized list of approved activities along with an explanation of the procedure.  Improvements for the future  All proposals should include a multi-year profile  Largely moot point this year  Already badly overcommitted  No possibility of new initiatives for FY10 1/8/09 8 E. Prebys, DOE/LARP Meeting

 In spite of some missteps, LARP activities are closely coordinated with CERN.  CERN interest is a necessary condition for any LARP project.  As you will see, LARP is resource limited:  In the absence of an unexpected funding windfall, there are more activities of interest to both LARP and CERN than we can possibly undertake.  CERN will probably be of limited use in further prioritizing LARP activities.  We will need to make decisions based on our own risk analysis. 1/8/09 E. Prebys, DOE/LARP Meeting 9

 Began bi-weekly meetings with Alex Ratti, LARP and LBL management, and Enrico Bravin (CERN) to stay up to closely monitor progress.  Working with the CERN controls group and LAFS on the software end.  Draft requirements specification created.  Enrico and Alex working on document to formally specify the handoff to CERN.  Working with CMS luminosity group, who will contribute some manpower to do the deconvolution microcoding necessary for high intensity operation.  For more details on Lumi status, see Markiewicz talk 1/8/09 10 E. Prebys, LARP DOE Meeting

 Original plan  $2.5M  Finished in FY07  Currently  Spent $3.6M  Need to spend ~$800k more  Finished in FY09??  Bottom line  These sorts of overruns are not unusual in real projects!  LARP contingencies are far from sufficient to cover overruns in significant deliverables.  More about this shortly… 1/8/09 11 E. Prebys, LARP DOE Meeting

 Guidance from DOE  $13M with a 6 month continuing resolution at 84%.5*.84*13+.5*13 = $11.96M  Separate money ($1-2M) found for APL planning!  General breakdown (informed by Steve’s exit advice)  Accelerator Systems: $2.9M  Magnet Systems: $5.0M  Program Management: $2.1M Includes LTV and Toohig Fellows (of which we have 4)  Contingency: $2M  In then end, had to give up some continency to increase Program Management 10/19/ E. Prebys - LARP Meeting

 Luminosity monitor was expected to be complete by end of FY08  Instead had significant overruns, and needs significant funds on FY09 (original request $1M -> $800k)  Still consider it absolutely vital for lumi to work!  Rotating collimators still a big budget item  Still consider it important to complete a prototype this year in time to at least be considered a solution by CERN.  Strong feeling that LARP should take a leading role in crab cavity development  Led by Rama Calaga  Support by CERN  General feeling that “the train is leaving the station”.  Magnet program still has to funded at a level that will insure a working magnet for the LHC Phase II upgrade 10/19/ E. Prebys - LARP Meeting

 Accelerator Systems  Iterative process, primarily involving Wolfram, Tom, Alex, and myself, to converge on the bottom line. Key component: relying on labs to contribute labor in accordance with their core competencies (i.e. not charged directly to LARP)*  Key casualty: No real money for PS2, for which there was a great deal of excitement within LARP and at CERN Will continue with contributed labor while we decide what to do for next year.  Magnet Systems  Much more monolithic than AS  L1 and L2 managers worked to stay within the budget 10/19/ E. Prebys - LARP Meeting

 Not much leeway  Management costs determined by historical usage  Need to honor commitments to LTV’s and Toohig fellows  Only discretionary is Programmatic travel, which I have reduced by trying to include travel with the appropriate project. 10/19/ E. Prebys - LARP Meeting

 Crab cavities  Original request: $700k Cavity design Cryomodule design LLRF  Budget: $300k Rely on “off books” help in cavity design from LBNL and Jlab Defer cryomodule and LLRF work  PS2  Uli Wienands developed a number of plans under various funding scenarios  In the end, budgeted $100K, primarily for travel and M&S, assuming that most scientific time would be contributed. 10/19/ E. Prebys - LARP Meeting

10/19/ E. Prebys - LARP Meeting

1/8/09 E. Prebys, LARP DOE Meeting 18

1/8/09 E. Prebys, LARP DOE Meeting 19

1/8/09 E. Prebys, LARP DOE Meeting 20 Had to make two more practice coils than planned. Fin plan in progress.

1/8/09 E. Prebys, LARP DOE Meeting 21

 Lumi and rotatable collimator should ramp down considerably, allowing concentration on other significant commitments  Candidates:  Crab cavity effort Crab cavities deflect the beam to compensate for crossing angle. Potential to dramatically increase luminosity under most likely Phase II upgrade scenario  PS2 Activities CERN has requested LARP help in the design (white paper study) of the PS2, which will replace the PS for the phase II upgrade. 1/8/09 22 E. Prebys, LARP DOE Meeting

 Pros  Potentially a big impact on luminosity  Lots of intellectual interest in US community  Can be divided into well-defined tasks that are straightforward to monitor.  Cons  Barring a budget windfall, LARP will not have the resources to take a significant role in construction, so must coordinate with multiple labs/countries/funding agencies.  Current plan relies on SBIR grants  If badly managed, potentially a black hole of resources that never accomplishes anything. 1/8/09 23 E. Prebys, LARP DOE Meeting

1/8/09 24 E. Prebys, LARP DOE Meeting

1/8/09 25 E. Prebys, LARP DOE Meeting

 Pros  Lots of opportunities to make contributions  Well aligned with US interests and expertise, particularly Project X  Involvement “scalable”  Cons  Activity and goals not as well defined  Danger of funding a lot of people to “think about stuff”  Potential areas of focus  Injection issues  Electron cloud  Laser stripping? 1/8/09 26 E. Prebys, LARP DOE Meeting

 Assume flat-flat budget over next year or so  Will work on this, but don’t expect miracles  ~$12-$13M/yr  Lumi and Rotating collimators will ramp down  Would be naïve to assume they go to zero  Several things positioning to take their place  Existing efforts (Ecloud, beam beam, jirs)  New things (PS2, crab cavities)  Either PS2 or crab cavities could easily use out AS budget  And it would be well spent.  Have to make tough choices  Can’t do everything we want  Strong pressure to shrink MS budget 10/28/2008 E. Prebys, LARP PS2 Session DRAFT 27

1/8/09 E. Prebys, LARP DOE Meeting 28

1/8/09 E. Prebys, LARP DOE Meeting 29 LARP had a period of rapid growth in the earlier yeas, which led to some over- optimism

 Official LARP change control policies essentially ignored.  No consistent rules for dealing with burdens at different labs  Budget and schedule not integrated  Earned value reporting must be done by hand, if it’s done at all  No systematic way of dealing with different types of contingency  “deliverables” should have significant assigned contingency  R&D projects should have “scope contingency”, possibly adjusted by an uncommitted unassigned contingency pool.  No formal accounting for “off books” contributions from member labs.  Developing future budget profile a nightmare. 1/8/09 30 E. Prebys, LARP DOE Meeting

 From LARP “Management Plan”:  Problem  LARP doesn’t even have an informal base line  Large changes can sneak in at the annual budget without being noticed  Example: in order to see the budget and schedule problems with the lumi monitor, it’s necessary to forensically examine old task sheets. 1/8/09 31 E. Prebys, LARP DOE Meeting

 Reminder: the entire AS + MS budget is $3M+$5M, which is ~10+20 FTE’s or so.  We get a significant amount of additional scientific effort contributed in two ways:  Explicit LHC work supported through the unassigned “core” program ~6 FTE’s at SLAC ~6 FTE’s at FNAL Some CBP time from LBNL  Time which benefits LARP through common interest ~2 FTE’s at BNL working on RHIC projects which benefit the LHC as well  This is primarily for the AS, for which it is a large part. 1/8/09 E. Prebys, LARP DOE Meeting 32

 What is the model for “off books” contributions to LARP?  None? In the absence increased funding, LARP would have to dramatically reduce its activities  Ongoing? Could all scientific time be supported out of core budgets?  “Venture capital” Could some amount of commitment out of the core program be expected to develop proposals to the point where LARP could fund them. 1/8/09 E. Prebys, LARP DOE Meeting 33

 Put LARP budget and schedule into a single MS Project file  Define burdens and labor rates correctly for the four member labs  Eg, “BNL engineer”, “SLAC scientist”, etc…  For every labor category, have an equivalent “off books” category with an appropriately PC name (“common effort”?), which is not included in the normal roll-up, but can be rolled up separately.  Progress is updated monthly by designated L2 and L3 managers.  Implement formal change control and change logging.  Project used to formulate long term plan and budget profile. 1/8/09 34 E. Prebys, LARP DOE Meeting

 Ken Domann has agreed to translate the currrent WBS chart, as well as other information, into a fully loaded MS Project file.  Budget expenses will be charged against rolled project line items  Need to identify FNAL person to do this once a month  For each subtask, a responsible person will be identified.  Ken will him an Excel spreadsheet each month on which he will report progress on his tasks and milestones  Ken will generate standard earned value reports on a monthly basis.  For schedule or budget changes beyond those specified on 3.4, we will generate proper CR’s which must be approved by the Executive Committee(?) 1/8/09 35 E. Prebys, LARP DOE Meeting

 Currently translating budget into this format.  Have the tools fully in place by our April collaboration meeting.  Use as a tool for real time budget discussion. 1/8/09 36 E. Prebys, LARP DOE Meeting

 Get lumi monitor working prior to 2009 start up  LARP reputation depends on it  Protect core magnet program  Insure that LARP produces a prototype Nb 3 Sn magnet on a time scale that makes it a viable choice for the Phase II upgrade.  Complete rotating collimator prototype  This has been a significant LARP activity, and it’s important that we produce a prototype on a time scale that will allow it to be part of the collimation solution.  Continue to support Toohig Fellows and Long Term Visitors  Very important link to CERN  LARP supported visitors making significant and well received contributions.  Choose from remaining AS activities based on a risk reward analysis 1/8/09 37 E. Prebys, LARP DOE Meeting

 LARP has done and continues to do good work  eg, 3 invited talks and 36 contributions to PAC09  The scope has grown beyond where it can be effectively managed in the informal way in which it began.  We are taking steps to formalize the baseline and develop a credible long term plan. 1/8/09 E. Prebys, LARP DOE Meeting 38