FWWG

Wednesday 7 Nov 2007, 16:00 → 18:00 Europe/Zurich

304/1-001

Slides AlarmHandlingRequirements.pdf AlarmHandlingRequirements.ppt

Present: Frank, Clara, Olivier, Oliver, Lennart, Peter, Helfried, Lucas, Bobby, Stefan, Wayne 1) Alarm Handling and Display Oliver had discussed with each of the experments in advance and produced a very nice summary presentation detailing for each requirement what the position of the respective experiments was. His presentation can be found under: http://indico.cern.ch/conferenceDisplay.py?confId=23628 It is clear that there are not yet any fixed guidelines for the sub-detectors for which elements to define alarms on. The questions was raised as to whether it was necessary to reduce the number of defined alarms. Wayne felt that these should be reduced to what is really necessary and the experiments not to rely on alarm suppression only at the level of the alarm display to reduce the number of alarms seen by the operator, as this does not eliminate the various levels of processing required at the level of the EV, DM and RDB, but not all agreed. However, all experiments agreed that a tool to be able to see what alarms (and also archive configs) are defined for a project (remotely) would be very useful. As it turned out there was no general agreement on most of the requirements regarding the alarm display - some being discussed in quite some detail. However, the following was agreed: - The experiments should prioritise the 6 changes required from ETM (AS1-AS6 in Oliver's presentation). Once we have a prioritise list this will be sent to ETM for discussion. - Oliver estimated that the remaining changes would be about 4 week's development work and given his current commitments could be finished in early January. Therefore, it was decided not to prioritise these developments any further. Nonetheless, if Oliver discovers that the implementation of any change, not required by all, will impact those not requiring it he should flag this immediately. Similarly if the work will take significantly longer than foreseen he should also flag this. 2) Next meeting The next meeting will discuss s/w and application installation/maintenance, backup and restore strategies. Wayne will complete his discussions with the experiments on 9th November. We could aim for a meeting on the 21st November.