Managed by UT-Battelle for the Department of Energy Quest for the Best Ever Alarm System Tool Kay Kasemir Oct. 2008

2Managed by UT-Battelle for the Department of Energy IOC Log Files ALH -Display -Beeping -Acknowledgement -Logging -Masking ALH -Display -Beeping -Acknowledgement -Logging -Masking Status Quo: ALH  “Works”, stable  Beautiful? Ugly? –X11 only, fixed layout  Only full-feature view is “Tree” –“Active alarms only” is one-time filter –Alarm “history” list limited to 10 entries, no guidance/ack/…  No online editing of configuration –Change masks etc. in running instance, or edit file & restart all instances  Is 1996 Motif code worth major rework?

3Managed by UT-Battelle for the Department of Energy GUI JMS CSS Other RDB LOG ALARM JMS2RDB IOC LDAP Interconnection Server DESY Alarm System Filters Filt.Alrm

4Managed by UT-Battelle for the Department of Energy Design Choices  All IOCs send all alarms? –That would be SNS PVs. Instead of more alarms, we need useful alarms.  LDAP for configuration/state –Choice was based on available infrastructure. For SNS that would be Oracle, for others MySQL or...  Filter Mechanism details –Enable, latch, annunciate, chatter delay/count?

5Managed by UT-Battelle for the Department of Energy GUI JMS CSS Archive Engine Other RDB LOG TALK ALARM JMS2Speech JMS2RDB IOC Alarm Server Alarm Logic: -Current? Acknowledged? -Guidance, Links -Transient? -Annunciated? Alarm Server Alarm Logic: -Current? Acknowledged? -Guidance, Links -Transient? -Annunciated? RDB Channel Access Log Messages Log History Config, State New Alarms, Ack. ‘This’ Alarm System

6Managed by UT-Battelle for the Department of Energy Alarm GUI

7Managed by UT-Battelle for the Department of Energy Alarm GUI Ideas  Tree (‘all’ or ‘current’)  and/or Table (current)  Both allow configuration of current alarm items –Tree can also configure items which aren’t in alarm  Hierarchy used for guidance, related links (http, edm, …), commands –Tree elements inherit guidance etc. from parent entries  BNL/RHIC type acknowledge and un-acknowledge

8Managed by UT-Battelle for the Department of Energy CSS Context Menus Connect the Tools

9Managed by UT-Battelle for the Department of Energy General Alarm Behavior Ideas  Latch highest severity, or non-latching? –like ALH “ack. transient”  Annunciate?  Chatter filter ala ALH  Alarm only if severity persists some minimum time .. or alarm happens >=N times within period  When acknowledging MAJOR alarm, subsequent MINOR alarms not annunciated –ALH would again blink/require ack’

10Managed by UT-Battelle for the Department of Energy Message History  Alarm updates use JMS ‘ALARM’ topic –Alarm state changes, ack’, config changes, …  Alarm history via generic JMS-to-RDB tool and log viewer –Could be combined with ‘LOG’, ‘TALK’, … messages

11Managed by UT-Battelle for the Department of Energy Next TODOs  RDB schema for alarm config/state –Tweak current MySQL schema, port to Oracle –Add Web Tools to report state, edit config  Alarm Server, GUI –User/password to edit config? –Testing –Filters: Show only “Vacuum” alarms…

12Managed by UT-Battelle for the Department of Energy Unresolved Issues  “Alarm Config” is really Hierarchy of Channels to alarm on Description, Guidance, Related Displays, Commands o Alarm Limits and severities  Machine mode switch can require changes to a)List of channels (“Alarm System”) b)Limits & severities (“EPICS Database”)  Use DESY Idea, one big “bumpless” file?