David Lissauer ATLAS Technical Coordination ATLAS Upgrade Project Office

1. David LissauerATLAS Technical CoordinationATLAS Upgrade Project Office ATLAS Upgrade Project Office. July 5th 2006 Status of the Upgrade PO D. Lissauer, Upgrade Steering group, May 17th 2006

2. General Organization The Upgrade organization has a Steering group – and a Project Office. • Upgrade Steering Group – Nigel Hessey • Upgrade Project Office – David Lissauer (Report to Technical Coordinator) • Review Office - Mike Tyndel (PO-deputy for reviews) • Layout Advisory Group - Nigel Hessey • Simulation- Jeff Tsang D. Lissauer, Upgrade Steering group, May 17th 2006

3. Project Office - functions • Overall planning (schedule and follow-up office) • Develop and maintain for each upgrade project Schedule. • Ensure that the schedules are coordinated. • Review process • Regular reviews of the upgrade R&D project • Configuration control: • Maintain layout drawings. • Maintain a 3D model of the experiment • ECR’s • Envelope checks – configuration control • Safety organization: deals with materials ,structures certification etc. • Maintain existing ATLAS facilities at CERN : (for example SR1), in term of infrastructures and services that will be needed for the upgrade. • Radiation, activation compliance with INB regulation: Access, removal of active components, zoning inside the cavern and traceability D. Lissauer, Upgrade Steering group, May 17th 2006

4. R&D Organization “Directed” / ”Coordinated” R&D: • R&D be applicable to the ATLAS upgrade plans. (NOT Generic R&D.) • Distinguish between R&D that is initiated by the PO and R&D that is coming from the community and submitted to the SG. • R&D submitted to the Steering group will be reviewed and the PO will help in integrating the effort in to the general ATLAS structure. Make sure the interfaces are defined etc. • Items like Cooling, Large Mechanical structure, electronics integration etc. will be initiated by the PO. • As the number of options are reduced -support for dropped options R&D will be terminated in an orderly fashion. • Use the R&D period to foster collaboration and avoid as much as possible “shoot outs” . • The PO will take an active part in coordinating and reviewing the R&D proposals. D. Lissauer, Upgrade Steering group, May 17th 2006

5. Project Office functions • Integration: • R&D and construct all major support structure • Construct Installation and access structures. • redesign all services layout, their routing and installation strategies • installation scenario of the detector components and services • Coordinate the R&D and implementation of the next generation of cooling plants • Be a true technical point of contact for the upgrade and facilitate technical collaboration and distributed responsibility within the Collaboration • A forum for technical and engineering discussions of all possible upgrades projects and their interaction with the existing detector. (Complimentary and in coordination with physics simulations) • Layout studies • R&D Monitoring D. Lissauer, Upgrade Steering group, May 17th 2006

6. Development of a WBS & Schedule • Development of a baseline schedule to be used for planning the R&D program. • Develop a WBS structure for the Upgrade program. • Each deliverable will have: • R&D • Prototypes • Constructions (Pre-series, Series production) • Integration/Installation (In to the next level) • Installation in ATLAS • Conform to the overall upgrade schedule. D. Lissauer, Upgrade Steering group, May 17th 2006

7. Schedule • The ATLAS upgrade will include upgrade and or modification to: • ID • LAr • Muons • Beam pipe • Shielding • Trigger • DAQ Note: To keep to the schedule we need: TDR on ’09 time scale. Assume Beam Stops: Mid ’13 Beam on early ’15 Expect that the Sch. will slip by 9-12 month in the coming years. Schedule will have to include ALL of the above. D. Lissauer, Upgrade Steering group, May 17th 2006

8. Scope – Working Groups • Simulation:Detector geometry, readout granularity. • Layout: Layout of the system, envelopes, Services routing • Mechanical Support :Main Support of the ID, “Mass less”. • Thermal Management: Thermal management of the system. • Sensors: Material, industrial contact. (Pixel, SS, LS) • Module Integration: Modules integration, “Stave” • Electronics: Cabling, Multiplexing, Power Distribution, Readout Architecture and components. • Assembly and Installation:Assembly on the surface, Installation in the experimental hall. D. Lissauer, Upgrade Steering group, May 17th 2006

9. ID -Schedule • Schedule organized as follows: D. Lissauer, Upgrade Steering group, May 17th 2006

10. Cooling -What happened so far • Charge: • Evaluation present systems for Muon system, Calorimeter, ID • ATLAS Tracker Upgrade: • Review the ATLAS Tracker Upgrade requirements • Compare the expected performance and the implication to ATLAS for different solutions. • Identify integration issues affecting the future cooling ID design (in collaboration with the relevant working groups) • Prepare an outline first conceptual solutions for a final system • Clarify ATLAS interfaces • Description and outline plan of the R&D • Develop an a baseline Schedule for the R&D effort (With PO) • “As a first step the R&D group will prepare a short specification for the cooling system, develop an R&D plan, and identify groups and individual interested in working on the Project.” • “We hope that this plan can be developed by the Upgrade workshop planned for early October at CERN.” Viehhauser, Georg D. Lissauer, Upgrade Steering group, May 17th 2006

11. Next step: Workshop ID Cooling • August or September at CERN, 2 days • Started to contact potential speakers • Result in first version of answers to the charge • Suggested agenda: • Experiences • ATLAS SCT thermal management during assembly • ATLAS pixel thermal management during assembly • ATLAS assembly evaporative system operational experience • CO2 cooling at LHCb and AMS • CMS tracker cooling • Requirements • Sensor thermal requirements (speaker from sensor group?) • Front-end architecture and thermal requirements (speaker from electronics group?) • Existing structure: constraints and possibilities • New concepts • ‘Open’ evaporative cooling system • CO2 evaporative cooling system • Other coolants • Highly thermally conductive materials • Fittings • Resources & Tools • Tasks & Work plan D. Lissauer, Upgrade Steering group, May 17th 2006

12. Read-out of the Tracker • What are the important points to be kept in mind • Whatever the elected technology it will be expensive • Limit the number of iterations/designs • Services volume will have to be kept as low as possible • Power consumption must be optimized • Power distribution needs major R&D • Serial powering or DC-DC or both • TTC and data transmission optimization • The more commonalities between sub-systems the better • Could be common ASICs or common blocks of ASICs • Interfaces, TTC and control parts, opto-links • Can we define a common architecture and then common blocks? PhilippeFarthouat and Alex Grillo D. Lissauer, Upgrade Steering group, May 17th 2006

13. Power • Options: • Shunt or LinearRegulators • DC-DC • I/O • Options: • Optical vs Copper • Serial/Parallel • AC or DC coupling • Bandwidth • TTC interface • Slow Control Interface • Pipeline • & • digitisation • Options: • Analog or digital pipeline • Binary vs Digital • #bits? • Data compression • Data Format • Front-End part • Options: • Technology(CMOS, SiGe) • Pixel/Strip Basic Building Blocks Example 1 D. Lissauer, Upgrade Steering group, May 17th 2006

14. Power • Options: • Shunt or LinearRegulators • DC-DC • I/O • Options: • Optical vs Copper • Serial vs Parallel • etc. • Processing • Options: • Data compression • Data Format • DCS stuff • Input part • Options: • Copper • Optical • Bandwidth • Serial vs parallel Basic Building Blocks Example 2 D. Lissauer, Upgrade Steering group, May 17th 2006

15. Review Process (overview) • 1) Review of new R&D proposals • Build on the review process already existing within the SG by having PO involvement • 2) Preview ( typically end 2006/early2007 ) • Review Office to work with the R&D proponents and the activities initiated by PO to have a documented Preview approx 6 months after submission: • Goals • Establish that the proposed R&D/activity is relevant to ATLAS. • Reach a common understanding of the physics requirements, the subsystem specifications, how the subsystem interfaces into ATLAS, the scope, timescale and cost of the R&D and a first estimate of the design and cost and production time for the final system. The dates for taking decisions and providing status reports to be agreed. (see attached template) • FDR to launch pre-series (typically end 2008 ) • PRR to launch production on the basis of PRR results (typically end 2010) Mike Tyndel D. Lissauer, Upgrade Steering group, May 17th 2006

16. Radiation - Plans What is needed for the upgrade ? • New beampipe design • New shielding design for the inner detector • New shielding design for the muon spectrometer • New dipole magnet design • New activation study • New study of radiation in USA15 • New nuclear zoning Vincent Hedberg D. Lissauer, Upgrade Steering group, May 17th 2006

17. Possible locations of D0 magnet Discussion with the Machine – Ongoing. LHC – Upgrade machine workshop in September. D. Lissauer, Upgrade Steering group, May 17th 2006

18. Layout Group – Develop a baseline Layout group – started. Will meet ~ 1/mont. Looks like lots of nice ideas – is it consistent with Schedule? e.g: Conical Structure? Split at Z=0? D. Lissauer, Upgrade Steering group, May 17th 2006

19. ID Straw-man Layout (3 SS layers) 3 Pixel Layers 14,32,48 f Sectors 5,12,18 R Location 3 Short strip layers 22,32,40 fSectors 27,38,50 R Location 2 Long Strip layers 28,42 fSectors 70,95 R Location Moderator D. Lissauer, Upgrade Steering group, May 17th 2006

20. Summary • PO is starting to take shape – Some key positions still need to be identified. • Schedule is under development – LAr, ID Drafts exist. • Baseline Layout for ID by Dec. ’06 • Baseline Readout Architecture Dec ’06. • Cost Model needs to be developed and agreed. • October general Upgrade workshop a 1st pass of an schedule • December ID workshop aim to have a baseline schedule. • Schedule and milestones still have LOTS of Inconsistencies. D. Lissauer, Upgrade Steering group, May 17th 2006