1 / 14

Alarm Management at Jefferson Lab

Alarm Management at Jefferson Lab. A New Configuration and Extended Capabilities B. Bevins , M. Joyce, J. Sage. Outline. New Requirements ALH Usage ALH Modifications CDEV Modifications Other Development Status. New Requirements. Motivated by a new control room design

ramona
Télécharger la présentation

Alarm Management at Jefferson Lab

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Alarm Management at Jefferson Lab A New Configuration and Extended Capabilities B. Bevins, M. Joyce, J. Sage

  2. Outline • New Requirements • ALH Usage • ALH Modifications • CDEV Modifications • Other Development • Status

  3. New Requirements • Motivated by a new control room design • Global acknowledgement • Global disabling • Smarter automatic disabling • Centralized logging • Geographical view of accelerator • Make alarms “more meaningful” • Motivated by maintainability • Automatic generation of configuration files • Separate configs for operators and experts

  4. Old Control Room

  5. New Control Room

  6. Changes to ALH Usage • Thorough review of alarm parameters • Removed extraneous alarms • Determined where to ignore transients and of what duration • Readable alias names used throughout • Use ALH in global mode • Master copy manages alarm logic • Operators open copies to acknowledge • Logs to CMLOG • FORCEPV’s to disable (automatic and manual) • SEVRPV’s to summarize alarm state in MEDM

  7. ALH Modifications • Uses CDEV transparently • Wasn’t quite working before • Uses CHANNEL keyword rather than CDEVkeyword • Also works for FORCEPV, SEVRPV, etc. • Unacknowledged Severity PV’s • New keyword UASEVRPV works like SEVRPV • Disabling a group/channel updates parent group severity PV’s (both types)

  8. Why CDEV? • Legacy: high level RF system diagnostics calculated in CDEV-based RF Alarm Server • Allows alarms on other CDEV-based high level beam applications servers • Slow locks, real-time optics model, etc. • Alarm states can now be monitored and acknowledged directly from Tcl-CDEV applications.

  9. CDEV Modifications • CA Service Enhancements • Supports ack and ackt messages • Allows unAckSevr and ackTranstags (along with severity, status, etc.) • Allows correct canceling of monitor requests • Now matches the documentation • Prevents buffered callbacks from being delivered after a monitor has been canceled

  10. Other Development • makeALHConfig - Perl scripts to generate config files and sponsor FORCEPV and SEVRPV soft channels on a Proxy IOC (PIOC) • 15,372 alarms • 11,463 PV’s on PIOC • alhDisable - Tcl program to manage FORCEPV’s and manually disable alarms • Generates reports of all currently disabled alarms for shift changes, etc. • Makes an entry in the Logbook.

  11. Alarm Summary Screen

  12. Alarm Disable Tool

  13. Status • New automatically-generated configuration has been in use for several months. • Vast improvement: alarms are no longer silenced and ignored. • Global alarm management is being tested and should be fully deployed in May. • Modified CDEV will be released soon after through the CDEV website http://www.jlab.org/cdev/. • ALH changes will be submitted for inclusion in new releases.

  14. Alarm Management at Jefferson Lab A New Configuration and Extended Capabilities B. Bevins, M. Joyce, J. Sage

More Related