++++++++++++++++++++++++++++++++++++++++++++++ The immediate (MTCC) requirements include: +++++++++++++++++++++++++++++++++++++++++++++++ General: (1) Run control status monitoring (real time or almost real time) (e.g. trigger, run number, shift personnel, etc.) (Suzuki/Meyers) (2) Webex screen displays/ alternatives (Suzuki/Gottschalk) - Mirrored screen images (3) Webcam/polycam (Austin Ball/Lazic at CERN -- ??) (4) Configuration data base via DCS -- CERN will provide tools (5) HLT level monitoring (Emilio Meschi) (6) Online/Offline databases (7) e-log: A choice of an e-log system should be made ASAP (Sergio ??) (8) Data transfer to FNAL from CERN using output of Global DAQ (Baurdick) (9) Monitoring of Offline data (general/subsystem) (10) No Storage Manager monitoring at CERN for MTCC Sub-detector level: HCAL: (a) Configuration (HV, LV, etc) status from real time DCS status pages. Serguei Sergeev will implement CERN tools (at CERN) Stoyan Stoynev will assist and provide infor for calibration (at CERN) (b) Almost real time monitoring of HCAL (DQM) at the HLT level (requires CERN assistance from Emilio Meschi's group) Wade Fisher working on this at FNAL. Copies of all Histograms at FNAL. (c) Off-line monitoring -- exists for HCAL: modify 2005 H2 scripts for CMSSW Shuichi Kunori/ Michal Szleper (mostly done) (d) Local DAQ runs at CERN (Mans) (e) Transfer of Local DAQ data to FNAL (calibration data ??) (Lazic/Mans) (f) Cataloging capabilities (global/local) (Hadley/Sanders) Requires CERN headers, etc (??) (g) e-log access at the HCAL level (??) (h) Mapping of calorimeter/electronics (Ratnikov) Similar task-list for each of: ECAL EMU MUON BARREL TRACKER, etc. OTHER (??) Need names and tasks associated with each of these subdetectors (Hadley will try to get names in the US. We also need CERN contacts.) The HCAL solutions probably will be adapted for the Test Beam run in the summer of 2006 as well. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Long Term ROC Requirements: ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Long Term Goal: The FNAL CMS ROC should resemble the CMS Meyrin Site ROC as much as possible. Build on the short term solutions to MTCC requirements: Include CERN requirements. Interface with the FNAL LHC@FNAL group. Real Time Control Monitoring includes such information as: - Current state & history of shift - Current state & history of DAQ/Run - Current state & history of trigger - Current state & history of detector - Current state & history of data quality (DQM) - Current state & history of LHC (not for MTCC) - etc. Access methods to those information are essentially same as those in the main CMS control room. - e-logbook - Audio communication with shifters and viewing SX5-CR. - two types of consoles. 1) mirror image of all consoles at the SX5-CR for monitoring. 2) "operation console" for accessing particular information. Very preliminary list of tasks: The extent of our tasks depends a lot on the status of DAQ/Run Control, trigger framework, PVSS. And also it depends on how much the CMS groups can provide at CERN. In any case here is a preliminary list. - Understanding the design and status of SX5-CR (what we will have for DAQ/Run Control/..../HCAL monitoring and operation). And then do the high level design for ROC. - Implementation and operation of e-logbook. Shift log, daq/run log, detector log, DQM log, calibration log, etc. This is a key component to organize all the effort. - Selection and implementation of video/audio systems. Telephone, web cameras, VRVS/ESNET/WebEX, etc. - Creating mirror image of consoles, including both monitoring and operation Console at SX5-CR. Those console should show state of DAQ/Run, trigger, detector i.e. PVSS/DCS, DQM. - Creating operation console to get additional information, e.g. access to PVSS/DCS, database, etc. - Implementation and operation of calibration data handling system. - DQM and event display - data transfer from CERN to FNAL and catalogue.