1. LARP Collaboration Meeting 26- 28 April 20061 BNL -FNAL - LBNL - SLAC LHC@FNAL: Status Report E. Harms 28 March 2006

2. LARP Collaboration Meeting 26- 28 April 20062 BNL -FNAL - LBNL - SLAC LHC@FNAL: Status Introduction to LHC@FNAL LHC@FNAL status and renderings Summary

3. LARP Collaboration Meeting 26- 28 April 20063 BNL -FNAL - LBNL - SLAC LHC@FNAL - Background Remote access to CERN has been a topic of discussion at previous LARP meetings Low-key conversations and demonstration of proof of principle Serious discussions began at Fermilab ~1 year ago Utility for both LHC and CMS experiment and ? Committee formed at request of Director Endorsed by current director Requirements document put together and reviewed Control Room visits, refinement of requirements Preparation of WBS and formal presentations at end of CY05

4. LARP Collaboration Meeting 26- 28 April 20064 BNL -FNAL - LBNL - SLAC What is LHC@FNAL? A Place That provides access to information in a manner that is similar to what is available in control rooms at CERN Where members of the LHC community can participate remotely in CMS and LHC activities A Communications Conduit Between CERN and members of the LHC community located in North America An Outreach tool Visitors will be able to see current LHC activities Visitors will be able to see how future international projects in particle physics can benefit from active participation in projects at remote locations.

5. LARP Collaboration Meeting 26- 28 April 20065 BNL -FNAL - LBNL - SLAC What is LHC@FNAL? Allow experts located at Fermilab to participate in CMS and LHC commissioning and operations. Hardware and software necessary to participate effectively in CMS and LHC. Facilitate communication and help members of the LHC community in North America contribute their expertise to CMS and LHC. An extension of the CERN Control Centre (CCC). For example, to assist members of US/LARP in training and data analysis. An extension of the CMS Control Room. For example, to provide a call center for US-CMS collaborators to access information about CMS and the LHC accelerator. A unique opportunity to have detector and accelerator experts in close proximity to each other solving problems together.

6. LARP Collaboration Meeting 26- 28 April 20066 BNL -FNAL - LBNL - SLAC LHC@FNAL Task Force Erik Gottschalk – Chair (FNAL-PPD) Kurt Biery (FNAL-CD) Suzanne Gysin* (FNAL-CD) Elvin Harms* (FNAL-AD) Shuichi Kunori (U. of Maryland) Mike Lamm* (FNAL-TD) Mike Lamont* (CERN-AB) Kaori Maeshima (FNAL-PPD) Patty McBride (FNAL-CD) Elliott McCrory* (FNAL-AD) Andris Skuja (U. of Maryland) Jean Slaughter* (FNAL-AD) Al Thomas (FNAL-CD) LHC@FNAL also has an advisory committee with members from Universities, FNAL, CERN-PH, CERN-AB, and CERN-TS. * Accelerator Subgroup

7. LARP Collaboration Meeting 26- 28 April 20067 BNL -FNAL - LBNL - SLAC LHC@FNAL – LARP needs LARP Accelerator Systems Tasks Commissioning Hardware Beam Instrumentation (deliverables) Schottky Luminosity PLL/BBQ Accelerator Physics Design of future IR’s

8. LARP Collaboration Meeting 26- 28 April 20068 BNL -FNAL - LBNL - SLAC LHC@FNAL - LARP/LHC Requirements Four broad categories of Requirements (requirements scale up as scope of activity changes) Overarching (defined as ‘to extend over or throughout’) Confidentiality Space Hardware Commissioning Access to data as U.S. hardware – magnets and instrumentation - is installed and commissioned Link to Field Control rooms in LHC tunnel Beam Commissioning More activity in CCC Software development Sector test First beam Post-LHC commissioning activities Support of LARP deliverables Beam studies LHC upgrades

9. LARP Collaboration Meeting 26- 28 April 20069 BNL -FNAL - LBNL - SLAC LHC@FNAL – LARP/LHC needs CCC Model the CCC at CERN speed assimilation prior to stays at CERN ease in remote participation in studies ‘service after the sale’

10. LARP Collaboration Meeting 26- 28 April 200610 BNL -FNAL - LBNL - SLAC LHC@FNAL - Scope

11. LARP Collaboration Meeting 26- 28 April 200611 BNL -FNAL - LBNL - SLAC LHC@FNAL - Scope

12. LARP Collaboration Meeting 26- 28 April 200612 BNL -FNAL - LBNL - SLAC LHC@FNAL - Scope

13. LARP Collaboration Meeting 26- 28 April 200613 BNL -FNAL - LBNL - SLAC LHC@FNAL - Budget

14. LARP Collaboration Meeting 26- 28 April 200614 BNL -FNAL - LBNL - SLAC LHC@FNAL - Current status Space Identified Layout endorsed by Fermilab Directorate/CMS/AD/CD GPP money ‘reserved’ Conceptual Design Report & review complete Minimal comments Project Execution Plan written and submitted Project Managers Elvin Harms/AD – construction Erik Gottschalk/PPD – consoles Weekly meetings to prepare construction drawings Color selection and other details in progress Approval working its way towards DOE Office, expect same within 10 days Begin work in spring/summer Construction complete by end of FY06

15. LARP Collaboration Meeting 26- 28 April 200615 BNL -FNAL - LBNL - SLAC LHC@FNAL – Floor plan

16. LARP Collaboration Meeting 26- 28 April 200616 BNL -FNAL - LBNL - SLAC LHC@FNAL – renderings

17. LARP Collaboration Meeting 26- 28 April 200617 BNL -FNAL - LBNL - SLAC LHC@FNAL – Floor plan

18. LARP Collaboration Meeting 26- 28 April 200618 BNL -FNAL - LBNL - SLAC LHC@FNAL – Isometric view

19. LARP Collaboration Meeting 26- 28 April 200619 BNL -FNAL - LBNL - SLAC LHC@FNAL – Consoles

20. LARP Collaboration Meeting 26- 28 April 200620 BNL -FNAL - LBNL - SLAC LHC@FNAL – view from Atrium

21. LARP Collaboration Meeting 26- 28 April 200621 BNL -FNAL - LBNL - SLAC LHC@FNAL – Wall display

22. LARP Collaboration Meeting 26- 28 April 200622 BNL -FNAL - LBNL - SLAC LHC@FNAL – Window display

23. LARP Collaboration Meeting 26- 28 April 200623 BNL -FNAL - LBNL - SLAC SummarySummary LHC@FNAL has benefits for LARP Designed with LARP in mind Intimately tied to CCC design Project design well on its way Time for feedback is now Remarkable pace We expect to have space this fall