1. Linac4 Timescale 2  Technical design report issued December 2006  Project approved by CERN Council June 2007  Official start of project January.

Slides:



Advertisements
Similar presentations
CFS TIME SCHEDULE EDR - CFS Europe – Kick-Off Meetings Kick-Off Meetings, CERN, 3, 4, 5 September ILC PROJECT ENGINEERING DESIGN REPORT CFS Europe.
Advertisements

Dmitry Kekelidze Software Engineer JINR – LIT/ CERN - GS-AIS.
Management’s preliminary comments to the ERC Report.
CSC, Status of HIPPI – September 2006 Maurizio Vretenar Alessandra Lombardi.
Chapter 7: Project Cost Management
Iterative development and The Unified process
Time and Cost Estimation
Information Technology Project Management, Sixth Edition Note: See the text itself for full citations.
XII- COST CONTROL, MONITORING & ACCOUNTING
Cost Management Week 6-7 Learning Objectives
EARNED VALUE MANAGEMENT SYSTEM A Project Performance Tool
Helmholtz Centre for Ion Research D. Krämer, 2nd Lab Directors Meeting, Protvino, January 15-16, 2008 Design and Engineering Issues; Standardization and.
Role of Management and Technical Coordination
October 24, 2000Milestones, Funding of USCMS S&C Matthias Kasemann1 US CMS Software and Computing Milestones and Funding Profiles Matthias Kasemann Fermilab.
© Robotics - 1 Process Analyzed ABB robotics Cost Management Assignment Group: JAMBO1 Federico Rosales Federico Tagliabue Jesper Jarnhall Panthep Pengniti.
WU1 - Management S. Gammino (INFN). WU1 Management and TDR preparation: overview and criticalities 2 The WP6 aim is to define the best design of the Warm.
4 th European Project Management Conference, London, 6-7 June 2001 Resource Critical Path Approach to Project Schedule Management Vladimir Liberzon, PMP.
Global Design Effort U.S. ILC Cost Translation R. Stanek, et al. Vic Kuchler 1/26/07.
© The McGraw-Hill Companies, Inc., 2007 McGraw-Hill/Irwin Chapter 21 Cost Allocation and Performance Measurement.
Gek 16/6/041 ITRP Comments on Question 19 GEK 9/06/04 19) For the X-band (warm) technology, detail the status of the tests of the full rf delivery system.
Project management tools Tiia Uusimäki. Agenda Activity Planning Tool and Earned Value Management – Why are the tools needed? – Activity Planning tool.
Project Cost Management
Project Management Part 6 Project Control. Part 6 - Project Control2 Topic Outline: Project Control Project control steps Measuring and monitoring system.
© The McGraw-Hill Companies, Inc., 2002 Slide 22-1 McGraw-Hill/Irwin 22 Cost Allocation and Performance Measurement.
HLRF DRAFT Global Design Effort 1 Defining EDR* Work Packages [Engineering Design Report] Ray Larsen SLAC ILC Division for HLRF Team DRAFT April.
Project Cost Management
CLIC Implementation Studies Ph. Lebrun & J. Osborne CERN CLIC Collaboration Meeting addressing the Work Packages CERN, 3-4 November 2011.
Hall 180 Cryogenic test facility: Project management: Project Change Request, EVM and Interface Sheet L. Serio.
CLIC cost estimate Hans-H. Braun, CLIC-GDE meeting, February 8, 2008  Cost model goals  Methodology  Cost distribution  Future improvements.
PS Days, January 2001 The “Plan” B.W.Allardyce The Medium Term Plan is presented at the June FC meeting by the Management and covers 4 years (I.e. in June.
Corporate Technical Infrastructure Management From MP5 to a Corporate Technical Infrastructure Management System.
1 1. Some recent views ( ) 2 Linac tunnel
Introducing Project Management Update December 2011.
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.
Technology Department WP2 Progress Report Th. Otto
1 Global Design Effort: Controls & LLRF Controls & LLRF Working Group: Tuesday Session (29 May 07) John Carwardine Kay Rehlich.
J. Pedersen, ST/EL Consolidation of the CERN technical infrastructure and civil engineering. J. Pedersen ST 6 th ST workshop, Thoiry, 1 – 3 April 2003.
Management’s preliminary comments to the ERC Report FINANCE COMMITTEE June 19, 2002.
Evaluating EVM January 13, EVM Issues and Opportunities ▪ EVM Basics ▪ EVM Issues ▪ EVM ETC and EAC Calculations ▪ EVM Cost and Schedule Value Calculations.
Report Performance Monitor & Control Risk Administer Procurement MONITORING & CONTROLLING PROCESS.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
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.
Linac4 Project Meeting 1/2011 3/3/2011 M. Vretenar Update on schedule and structure 1.
Information Technology Project Management, Six th Edition Kathy Schwalbe Copyright Disampaikan Oleh : Wiwid Dolianto S.Kom, MT Universitas Muhammadiyah.
CERN GS Department CH-1211 Genève 23 Switzerland cern.ch/gs-dep Internet Services GS AIS General Services Department GS Advanced Information Services EVM.
McGraw-Hill/Irwin © The McGraw-Hill Companies, Inc., Cost Allocation and Performance Measurement Chapter 21.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
Linac4 Project Meeting 1/ /01/ st priority 2  First priority: from the Linac4 project, the best wishes to you and your families for a 2010.
Welcome. Contents: 1.Organization’s Policies & Procedure 2.Internal Controls 3.Manager’s Financial Role 4.Procurement Process 5.Monthly Financial Report.
Workshop summary Outline  Workshop’s aims  Highlights from the presentations (my selection!)  Costing Exercise – What we learnt  Summary - Roadmap.
1. Baseline – from LMC  Presentation by F. Bordry at LHC Machine Committee 5.10 on LS1 Organisation: 1. Linac4 is not going to be connected.
CNGS Review 15 July 2003 M. Meddahi1 EVM for CNGS Definitions Pre-requisites Application to CNGS.
Monitoring and Information Systems
Chapter 9 Cost Planning and Performance
The CERN Linac4 history, performance, perspectives
Completion and Pre-Exploitation Costs for the Initial ATLAS Detector
East Hall under construction
Complementary ISTC Projects #3888, 3889p
Second SPL Collaboration Meeting, Vancouver May 2009
Renovation of the 45-year old PS magnets
Chapter 7: Project Cost Management
LIU Wire Scanner Series Costs
Monitoring and Reporting Project Progress
Benoît DAUDIN (GS-AIS-PM – CERN) 22-March-2012
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Managing Project Work, Scope, Schedules, and Cost
Charge and Agenda of the 18th TAC meeting
Chapter 9 Cost Planning and Performance
Presentation transcript:

1

Linac4 Timescale 2  Technical design report issued December 2006  Project approved by CERN Council June 2007  Official start of project January 2008  Groundbreaking ceremony October 2008  Building and tunnel delivered November 2010  End of infrastructure installation summer 2012  Beam commissioning 3 MeV summer 2013  Scheduled end of beam commissioning summer 2014

Linac4 budgets Preliminary budget (mostly top down) Execution budget (bottom up) Revised execution budget Note that in 2004/2007 was active a (small) R&D budget for Linac4, which allowed a smooth transition between R&D and construction (exemples: the MEBT was paid with the R&D budget, but part of the DTL R&D was paid with the construction budget).

Linac4 Execution Budget – 2008 All costs in CHF (1€=1.5CHF in 2008, 1.2 CHF now )

5 Linac4 original budget breakup NOTES: R&D program 2006/07 covered MEBT construction, RFQ design, structures R&D Not included 13 klystrons recuperated from LEP + circulators and some waveguides.

Linac4 budget Procedure: 1. Identify Workpackages (and responsible!), Workunits and Deliverables; 2. Negotiate the budget with WP holders; define together the general approach (for example, share outsourcing/in-house/in-kind); 3. In particular, agree that contingencies have to be centralized at project level. But CERN accounting “tradition” does not allow to have an explicit contingency. Therefore: 1.15% contingency added only to Civil Engineering (as “finishing works”); 2.small additional reserve at project management level (0.5%), some margin (another 0.5%) in some WPs “under construction”; 3.5% contingency provided at the CERN planning level (not included in project budget) → the project was starting with an overall contingency of some 9%. Note that CERN costs do not include manpower, but: - include temporary labor – at different levels - include subcontractors when relevant - include visitors and some additional personnel (some “fellows”=2.5 years post-docs) in a special budget under “project management” of 2.3 MCHF – 2.3%.

Insourcing or Outsourcing ? 7  CERN has some production capabilities, which are extremely good but overloaded and expensive (internal billing on hourly basis) - but they do not charge overheads!  Chosen Strategy: mix of insourcing/outsourcing, build in industry all what could be built there at a reasonable price, keep in house productions that are not interesting/possible in industry. In all cases, maintain in house the overall control of the productions (reduces considerably the costs, but increases the level of risk).  In kind contributions are welcome, but filtered (approved) by the project and proven (after prototyping). They are included in the budget with their real or equivalent cost.  Result of these construction choices: lower costs but higher risks, in particular for WPs with more insourcing (accelerating structures, beam instrumentation, LLRF, etc.).

Earned Value Management 8 EVM Methodology developed in ’60s by US DoD – enormous amount of experience in the US, is a PMBOK standard (finding: cost performance stabilizes when project is >20% complete…) Applied for LHC at CERN after the financial crisis of 2001; improved version (following LHC experience) implemented for Linac4 in 2009 Allows comparing expected financial evolution (Planned Value) with actual evolution (Earned Value) and real costs (Actual Cost). Workpackages Workunits Deliverables Original budget and planning → Planned Value Regular (monthly) reporting → Earned Value Budget follow-up → Actual Cost

Linac4 and EVM 9  Linac4 went into EVM from a very early stage (consequence: different level of refinement for different WPs);  The EVM tool for Linac4 was an improved version of the LHC tool, modified, simplified and adapted to a project of Linac4 size. It was integrated into the general CERN Planning Tool.  It was decided (after long discussions) to separate Personnel from Material: the WUs under EVM concern only material (and the follow up is done on the material expenditures) whereas separate WUs contain the personnel part, which are in the Planning Tool but not under EVM.

Workplan and budget into EVM 10 Long and tedious process, needs to be explained to and accepted from the WP holders

Example of Workunit 11 Manufacturing of DTL drift tubes: includes an in-kind contribution (charged to a special budget code) and a CERN part. Divided into 9 deliverables.

Project cost by year 12 up-to-date budget tables can be generated in a few clicks

Project execution Workunit Holders asked for Progress Reporting: Earned Value (EV)

PV/EV table 14 expenditures can be easily tracked and compared to planned ones

Four years later… 15

Situation in  2012: 4 years after start of project.  Projects evolve: schedule was « stretched » several times, the PS Booster part went into a separate project, new problems appeared → need to frequently update the EVM baseline, so far every year. May 2012: frozen Baseline4, should be the last one!  At May 2012, 51% of budget spent, 20% engaged, in-kind contributions defined → more than half-way through, only some 25% of budget remains to be engaged.  and our contingency is gone!  special contingency (5%) absorbed by the variation in the exchange rate: we profit of the better exchange rate for all purchases in Euros, but CERN material budgets are indexed accordingly to a weighted exchange rate and should have been reduced → decided to compensate the negative material index with the financial contingency → practically, the contingency has been distributed to the WPs (but those who pay more in EUR have a higher advantage!)  civil engineering went well, without overcosts thanks to the careful follow-up → the 15% contingency on civil engineering was made available to the project at end 2010  but at the same time problems with the ion source forced to start a new (and expensive) in-house source development → the costs of the new ion source have completely absorbed the CE contingency.

The 2012 budget 17

Budget breakdown (linac only!) 18

2 nd level for RF and acc. structures 19 w/o LEP klystrons, HPRF would need 8 additional 2.8 MW klystrons with circulators ≈ 5.2 MCHF

Budget evolution 20

What does EVM tell about the project? 21 Linac4 (global) on delay of 5 months EV agrees well with AC

EVM report CE and infrastructureLinac systems

EVM report LINAC4 2.4 – Accelerating Structures LINAC4 2.6 – Radio Frequency Systems

EVM report LINAC4 2.7 – Beam Instrumentation LINAC – Power Converters

25

Earned Value Management 26 The EVM tool has been: - an essential ingredient for a correct definition of the required budget and the associated schedule - an extremely useful management tool for the follow-up of the project - an invaluable help in the relations with the stakeholders (top management, finance, auditors): the fact that all data are available and (freely) accessible enormously contributes to the reputation of the project. However, the present implementation still presents some problems when used for the preparation of the yearly budgets. EVM data tend to be overoptimistic. The cost performance so far is not too bad (overall CPI = EV/AC = 1.02) Dr. Christensen & associates’ findings: CPI stabilizes when project is 20% complete |CPI(final) – CPI(20%)| ≤ 0.10

Conclusion: The 6 Linac4 Theorems 27 1)Problems always appear where you don’t expect them (example: ion source) 2)Problems do not appear where you expect them (Corollary of the previous theorem, example: civil engineering) 3)Most of problems appear at the interfaces between WPs (went well for Linac4: we were expecting problems there -Theorem 2- and we had in place a strong structure to follow the interfaces) 4)The size of a problem is inversely proportional to the size of the equipment that is causing it (small details stop big machines…) 5)The overcosts in the production of an equipment are directly proportional to its technological content. In Linac4, conventional systems costed less than foreseen, but all high-tech systems costed more than foreseen. This looks like a general rule. 6)Every activity takes 50% more time than what allocated, independently from the amount of time originally allocated.