Alarm Handling Oliver Holme 7 th November 2007

Guidelines & Strategies All provide recommendation to use Framework Classes Standard severities/behaviour/colours Warning (Yellow) Error (Orange) Fatal (Red) All provide recommendation to use Framework tools Library functions, panels etc. Alarm console runs on a separate PVSS system/computer ATLAS - Iterative approach used to reduce alarms LHCb - Not using acknowledgeable alarms

Requirements & Priorities Requested FeatureALICEATLASCMSLHCb AS1 Lock line position (do not jump to the bottom of the table when a new alert arrives) YESHIGH YES AS2 Support for filters on different Acknowledge states  Acknowledged alerts  Acknowledged & pending alerts  Not acknowledgeable alerts  Not acknowledgeable & pending alerts YES NO AS3 Avoid blocking pop-up messages, such as when a remote system connection is lost YESHIGH YES AS4 Show only one row for multiple severity alarms from the same DP element NO HIGH (show latest) NO YES (show latest) AS5 If alarm is WENT, show CAME line in a different colour  In order to see the time of the CAME event --YESNO AS6Forced comment for alerts higher than a certain priority -YESNO AS7 Drop down list of common saved filters for easy access in JCOP Alarm Screen (ATLAS persistent filters) -YESHIGHYES AS8Display of online value in a column in JCOP Alarm Screen YESHIGHNO AS9Summary display of distributed system status in JCOP Alarm Screen NOYESNO AS10Severity colour should be used for whole row --NOYES AS11Simple version of the Alarm Screen with no filtering options and no option to move open sub-panels - Web based NO, if AS1+16 HIGH No filtering, but allows AS12

Requirements & Priorities Requested FeatureALICEATLASCMSLHCb AS12 Options to go from an alarm row to:  a - The FSM panel  b - An improved details panel  c - A trend including alarm limits  d - The alarm help HIGH YES (c, d) HIGH (c, d) HIGH (b, c) AS13 A single column which shows:  DPE Description  If no comment, show alias  If no alias, show DPE name --NOHIGH AS14 Temporary removal of alarms from the Alarm Screen  Mark an alarm as not to be displayed any more  Should default back to visible after user logout  Can force to persist after logout  Should be possible to view a list of all hidden alarms YES (require AS16) HIGHNO AS15 Access Control  a - Check rights for acknowledge  b - Real user required for commenting – root user should not be allowed to comment  c - Resetting any filters on logout  d - Restricting access to filters based on current user HIGH (a) YES d - HIGH filters stored per user HIGH (a) NO AS16Timeout in panel to remove any filters if the Alarm Screen is untouched for a certain number of minutes YESNOHIGHNO With alarm limits in the trend

Requirements & Priorities Requested FeatureALICEATLASCMSLHCb AH1Search for help files based on Description YES -NO AH2Search for help files based on Alias YES - AH3Ability to define a help file for a group of channels YES - AH4Allow help files in other format, such as PDF YES-- AH5 Pass parameters in the Help File URI, such as alarm limits. This would be helpful in the case that the help pages are not static saved files, but are dynamic and can change depending on the parameters passed. -YESHIGH- AH6 Allow for inter-linking between help files. Allow for global replace in help files, such as changing an expert/contact person. YES -- AH7Storing of the custom help settings in the ConfigDB YES

Other Points - ALICE Archiving & retrieval of alerts from ORACLE is too slow How to inject alarms from external systems – Sniffer? How to handle alarm help for these external alarms? System for checking & testing alarms inside the DCS Tool for looking at (remote) systems to see the alarm configuration Gather statistics on numbers of alarms, groupings, thresholds etc. Test trigger of alarms in the DCS (not from hardware level)

Other Points - ATLAS Some method to categorize alarms Move/classify alarms into categories Option to provide a comment when moving category Filter on category of alarm View number of alarms in each category Web based alarm screen required

Other Points - CMS Passing parameters for the Alarm Help Possible parameters should include Trigger Value, Alarm limits, Alias, Description, DpName Tool to assign help URI to many DPs Distinction between alarms seen at sub-detector only or on central system Could be based on two different ranges of priorities INFO class for alarms

Other Points - LHCb How to inject alarms into PVSS? PVSS functions to inject & clear alarms Either clear alarms manually or after a period of time New details panel should show alarm limits and current online value How to avoid viewing alarms from systems “above” in the distributed system?