# Presentation: 542652

** ****Patricia McBride****July 21, 2005**

** **

## LHC@FNAL: Goals for CMS

**Commissioning**
**Provide access for experts in North America**
**Participate in a diverse set of activities that may not all be at the same location at CERN.  (For example, the Cosmic Challenge and test beam)**
**Operations**
**Participate in shifts and studies  (particularly useful during the nighttime hours at CERN)**
**Provide access for detector experts**
**Monitor data quality**
**Computing (requirements similar to operations)**

## CMS: Assumptions

**The CMS Collaboration will have a shift schedule, a run plan, and a protocol that defines the roles and responsibilities of shift personnel. We assume that a shift leader is responsible for CMS shift activities.**
**LHC@FNAL will have shift operators who will be able to assist US-CMS collaborators with CMS activities during commissioning and operations.**
**LHC@FNAL will participate in CMS shifts. Neither the duration nor the frequency of the LHC@FNAL shifts has been determined.**
**The CMS Collaboration will have a protocol for access to the CMS control system (PVSS), and a policy for how access to the control system will vary depending on the physical location of an individual user.**
**The CMS Collaboration will have a policy that defines how DAQ resources are allocated. This includes allocation of DAQ resources to various detector groups for calibration and testing.**
**The CMS Collaboration will have a protocol that defines how always-on video conferencing will be used in CMS control rooms and LHC@FNAL.**
**The CMS Collaboration will provide web access to electronic logbook and monitoring information to collaborators worldwide.**
**The CMS Collaboration will maintain a *****call tree***** that lists on-call experts worldwide for each CMS subsystem during commissioning and operations.**

## CMS General Requirements

**We will follow the policies established by the collaboration.**

**We plan to provide facilities for shift operators and experts during a variety of commissioning and operations activities for CMS.   These activities  could include debugging, test beam, and calibration for the various sub-components. There may be additional facilities needed for computing (production, network and grid monitoring).**

## Communications and Access

**LHC@FNAL will provide facilities and tools to allow participation in “global” CMS meetings related to commissioning and operations.   **
**Some tools are easily available; others may require some development.  **

**We have developed detailed scenarios that make use of these technologies.  **
**Most have already been used in HCAL test beam remote operations.**

## Communications and Access

**This center will most likely be part of a global system (CERN, FNAL and other CMS collaborating institutes.)**

**Video access during critical operations may need to be “always-on.”**
**These audio/video communications should be private to CMS  collaborators.  CMS will need to develop a policy.**

**It will be useful to monitor some CMS equipment by video/audio.  **

## CMS Controls (PVSS)

**Remote access to the CMS control system is a critical issue for operations and commissioning: **
**Will remote experts have access to the control system?**
**How is the system protected?  **
** **
**We examined several scenarios developed by local tracker experts and HCAL experts.  It is not yet clear what is the appropriate level of access.  The spirit of the requirement is that access is restricted, but should be available when it is needed.**
**A policy will be needed for different activities/detectors.****  **

## CMS Operations

**Requirements for CMS operations include the previous of requirements, plus the following:**

**Shift operators at the LHC@FNAL facility will want access to monitoring data in a manner similar to shifters at the main CMS control room at CERN.    **
**Some monitoring information should be viewable whenever shifters are present.**
**This does not mean that ALL data available in the CMS control rooms needs to be transferred to FNAL, but it should be available when needed by an expert or a shift operator.  **

## Operations planning

**Experts will want to initiate special runs and calibration runs for testing detector components.   LHC@FNAL and CMS will need to coordinate operations so these requests can honored with appropriate priority.   We assume this coordination will be primarily be done by the CMS shift leader.**
**The details will need to be worked out in some other forum.**

## Software requirements for CMS operations

- development.

**For smooth operations, it will be important to have key elements of the CMS online, controls and monitoring software operational and up-to-date at LHC@FNAL.   Some software development may be required for remote access, but this has not yet been specified.**

## LHC@FNAL: Common Constraints

**Computing and Networking for LHC@FNAL:  Detailed requirements are not yet known - noted as an Incomplete Requirement.**

**Communications for LHC@FNAL: common requirement (CMS, LHC)**

## Common Software requirements

**Common Requirements for all software developed for LHC@FNAL:**

**Most software will be developed by the collaborations and it is assumed that their software rules will be followed when LHC@FNAL users work on software for the collaboration.   These requirements apply to software developed explicitly for LHC@FNAL.**

## Security and Safety

**Common Requirements for Safety**

**Common Requirements for Security**