Remote Operations Erik Gottschalk 7 September, 2005

Slides:



Advertisements
Similar presentations
1 US CMS ASCB (Advisory Software & Computing Board) u Function u Membership u Activities u Future Plans.
Advertisements

J. Patrick - Major Challenges/MOPA021 – a new Remote Operations Center at Fermilab J. Patrick, et al Fermilab.
October 24, 2000Milestones, Funding of USCMS S&C Matthias Kasemann1 US CMS Software and Computing Milestones and Funding Profiles Matthias Kasemann Fermilab.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
US CMS Collaboration Meeting: April 7-8, LHC Remote Operations Center Erik Gottschalk Fermilab.
Test Organization and Management
HEPAP and P5 Report DIET Federation Roundtable JSPS, Washington, DC; April 29, 2015 Andrew J. Lankford HEPAP Chair University of California, Irvine.
LHC Accelerator Coordination Meeting: March 28, Remote Operations for CMS Erik Gottschalk.
J. Patrick - Major Challenges/MOPA021 – a new Remote Operations Center at Fermilab J. Patrick, et al Fermilab.
Presentation to OHEP, OFES, OASCR: Nov 7, Remote Operations and Collaborative Technologies for Distributed Science --- HEP & FES --- Erik Gottschalk.
Requirements Review – July 21, Requirements for CMS Patricia McBride July 21, 2005.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
US CMS/D0/CDF Jet/Met Workshop – Jan. 28, The CMS Physics Analysis Center - PAC Dan Green US CMS Program Manager Jan. 28, 2004.
© 2006 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Gathering Network Requirements Designing and Supporting Computer Networks – Chapter.
Mid-Decade Assessment of the United Nations 2010 World Population and Housing Census Program Arona L. Pistiner Office of the Associate Director for 2020.
Assessment Entry Module (AEM) Kick-off November 15, 2012 interRAI Preliminary Screener Toronto Central LHIN.
Accelerator Physics Department Meeting July 26, 2006 Jean slaughter1 Status Report APD Meeting July 26, 2007 Jean Slaughter.
IAEA International Atomic Energy Agency. IAEA Outline LEARNING OBJECTIVES REVIEW TEAM AMD COUNTERPARTS Team Composition Qualification PREPARATORY PHASE.
News Y2K June 25, Summary of June 12 Face-to-Face Meeting.
1 Future Circular Collider Study Preparatory Collaboration Board Meeting September 2014 R-D Heuer Global Future Circular Collider (FCC) Study Goals and.
LARP Collaboration Meeting April BNL -FNAL - LBNL - SLAC Status Report E. Harms 28 March 2006.
Client Senior Design Electrical and Computer Engineering Iowa State University Introduction Abstract Architectural plans are currently being developed.
Remote Monitoring for Hardware & Beam Commissioning E. Harms/FNAL 7 April 2005 Port Jefferson, New York bnl - fnal- lbnl - slac US LHC Accelerator Research.
LARP meeting – 2 August, Update Meeting II with Pier E. Harms 3 November, 2005.
11/3/2010 CM15 Controls for LARP and LAFS - 1 Terri Lahey LARP/LAFS/CERN and SLAC.
CD Strategy Session/Briefing on Collaboration Tools: Sept. 12, Collaboration Tools Erik Gottschalk.
Committee – June 30, News from CERN Erik Gottschalk June 30, 2005.
Remote Operations Committee – May 12, Subgroups and Scenarios Erik Gottschalk May 12, 2005.
UEC Meeting: May 6, Remote Operations Center Erik Gottschalk.
September 8, 2005M. Lamm HC and Install US Deliverables1 Installation and Commissioning Project Present Participation How we might participate.
Operations Coordination Team Maria Girone, CERN IT-ES GDB, 11 July 2012.
Remote Operations Committee – May 26, Committee News Erik Gottschalk May 26, 2005.
CMS Centre Project - Green Light Meeting
TEXAS NODAL (ERCOT REVISIONS)
CMGT 410 aid Education Begins/cmgt410aid.com
Project Management PTM721S
LHC Science Goals & Objectives
Remote Operations Erik Gottschalk Fermilab
Remote Operations For High Energy Physics
Erik Gottschalk for Jean Slaughter
Remote Operations Erik Gottschalk 5 October, 2005
Assessment of Our Status After 183 Days (6 months)
11 ii. Develop a plan for aDSM
Systems Implementation,
Remote Operations for CMS & LHC Erik Gottschalk Fermilab
Remote Operations at Fermilab
CLAS Collaboration Organization for 12 GeV Operations
Update Erik Gottschalk.
Operations Model Thursday, October 20, 2005 October 13, 2005 Jean Slaughter.
Chapter 1 The Systems Development Environment
CMGT 410 Possible Is Everything/snaptutorial.com
CMGT 410 Education for Service-- snaptutorial.com.
CMGT 410 Perfect Education/ cmgt410.com.
CMGT 410 AID Perfect Education/ cmgt410aid.com.
CMGT 410 HOMEWORK Perfect Education/ cmgt410homework.com.
CMGT 410 Teaching Effectively-- snaptutorial.com.
CMGT 410 HOMEWORK Education for Service-- cmgt410homework.com.
Introduction to Projects
Project Management Process Groups
Nada Al Dosary Edited By: Maysoon AlDuwais
Presentation to Project Certification Committee, DoIT August 24, 2008
LHC External Collimation Review
CBMS4303: Management Information System
FCC study – Fire collaboration WP4 Status & Update
Preliminary Project Execution Plan
Joint Application Development (JAD)
Introduce myself & around table
Review of hardware commissioning
LHC Computing, RRB; H F Hoffmann
Presentation transcript:

LHC@FNAL Remote Operations Erik Gottschalk 7 September, 2005

Overview Charge for our committee What is LHC@FNAL? Committee members Requirements document Recent Events Current Status

Charge Charge from Fermilab Director Mike Witherell (April 2005): Define the high level requirements for a remote operations center for commissioning and operations of CMS and the LHC accelerator. Develop cost and schedule estimates for the implementation of a remote operations center. I would like the committee to prepare a preliminary report by the end of July 2005, describing the requirements and scope of a remote operations center located at Fermilab. The committee should prepare its final report, including a resource loaded schedule, by the end of 2005.

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.

LHC@FNAL Functions A Place A Communications Conduit An Outreach tool 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.

LHC@FNAL Task Force Erik Gottschalk – Chair (PPD) Elvin Harms* (AD) Shuichi Kunori (U. of Maryland) Mike Lamm* (TD) Mike Lamont* (CERN-AB) Kaori Maeshima (PPD) Patty McBride (CD) Elliott McCrory* (AD) Suzanne Panacek* (CD) Jean Slaughter* (AD) Al Thomas (CD) * Members of the accelerator subgroup

LHC@FNAL Advisory Committee Alvin Tollestrup (PPD) Austin Ball (CERN) Avi Yagil (PPD) Bob Mau (AD) Dan Green (PPD) David Rice (Cornell) Dragoslav Lazic (Boston U.) Frank Glege (CERN) Hans Falk Hoffmann (CERN) Hermann Schmickler (CERN) Jim Kowalkowski (CD) Jim Patrick (AD) Joel Butler (PPD) Katherine Copic (U. of Mich.) Lothar Bauerdick (CD) Margaret Votava (CD) Mike Church (AD) Mike Syphers (AD) Mike Tartaglia (TD) Roberto Saban (CERN) Roger Bailey (CERN) Sandor Feher (TD) Steve Peggs (BNL) Vladimir Shiltsev (AD) Wesley Smith (U. of Wisc.) William Trischuk (U. of Toronto)

LHC@FNAL Activities for LHC We have developed various scenarios and envision the following types of activities for LHC@FNAL: Participate in LHC hardware & beam commissioning and operations Monitor LHC accelerator components (e.g. systems built in the U.S.) Analyze the monitoring data for LHC Develop software for the LHC Provide access to monitoring data and analysis results Provide training and data-analysis facility for members of US/LARP Provide a rapid response call center to get experts located in North America connected to CERN (data access, operational status, etc.)

LHC@FNAL Requirements We used LHC and CMS scenarios to develop the requirements document for LHC@FNAL. The requirements document has an Executive Summary followed by four sections: Section 3.1 – CMS Experiment Requirements Section 3.2 – LHC Accelerator Requirements Section 3.3 – CMS/LHC Combined Requirements Section 3.4 – Constraints

Recent Events Requirements reviewed July 21, 2005 Revisions made in response to recommendations from reviewers Document submitted to FNAL Director July 29, 2005 Meeting with Pier Oddone August 1st Enthusiastic response …“comprehensive document” Discussed space for LHC@FNAL (FESS) Presentation to CERN AB Management August 8, 2005 (presented by Mike Lamont) “…project should receive some support from CERN but in view of limited benefits to us, the level of activity should be kept to a bare minimum.”

Review Recommendations All of the material for the review and recommendations from the review committee are available on our website: http://home.fnal.gov/~eeg/remop.html Two of the seven recommendations: #5: There should be a strong requirement that the Remote Operations Centre should maintain to the greatest extent possible consistency in hardware and software with CERN and CMS. #6: More work needs to be done on the details of how this facility would be used… The project team should develop an operations model soon for both CMS and LHC that explains how the personnel at the Remote Operations Centre will interact with CERN and CMS staff (and members of the LHC community in North America).

Status & Summary Status: We are working on the physical layout for LHC@FNAL and concentrating on hardware and tools needed for remote operations. This is needed for cost and schedule estimates. We are starting to develop an operations model for LHC. We are researching CERN computer and networking security issues. Our primary focus is on defining how an operations centre can be used to help members of the LHC community (in North America) contribute their expertise to LHC activities at CERN.

Additional Slides

Scenarios LHC requirements were developed from six scenarios for LHC accelerator commissioning and operations: Hardware commissioning of a U.S./LARP deliverable Software contributions to LHC Beam studies from both CERN and U.S. perspectives (2) Diagnostics contributions to LHC via LARP First beam in the LHC

Assumptions For LHC For both CMS & LHC Individuals working in a Field Control Room (FCR) in the LHC tunnel will have access to telephone communications with international calling capabilities. Individuals working at the CERN Control Centre (CCC) will have access to telephone communications with international calling capabilities. US/LARP personnel will be at CERN to coordinate activities between the CCC and LHC@FNAL. The degree to which LHC@FNAL users have access to the LHC control system will be determined by LHC management. The LHC will have a shift schedule and a protocol that defines the roles and responsibilities of CCC shift personnel. The LHC will have a protocol that defines how machine commissioning and development activities are scheduled and carried out. For both CMS & LHC LHC@FNAL will comply with all CERN and Fermilab safety and security standards.

LHC Requirements Overarching Hardware Commissioning Beam Commissioning post-Commissioning activities

CMS/LHC Requirements General Capabilities Environment