1 / 11

Andreas Lüdeke

Paul Scherrer Institut. Andreas Lüdeke. Controls tools for operation management at the Swiss Light Source at the EPICS collaboration spring meeting 2010 in Aix-en-Provence. Operation Management: Beam Failure Analysis. Event : defined beam distortion → “bad lifetime”, “downtime”

donat
Download Presentation

Andreas Lüdeke

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. Paul Scherrer Institut • Andreas Lüdeke Controls tools for operation management at the Swiss Light Sourceat the EPICS collaboration spring meeting 2010 in Aix-en-Provence

  2. Operation Management: Beam Failure Analysis • Event: defined beam distortion → “bad lifetime”, “downtime” • Infos: related data of event → logbook entries, alarms, archived data • Cause: failure category of event → what caused it, where was it caused Storage ring beam current Beam lifetime 4 hour limit 50 mA limit Time bad lifetime downtime Andreas Luedeke 2.June.2010 Page 2 of 12

  3. Operation Management: Beam Failure Statistics Andreas Luedeke 2.June.2010 Page 3 of 12

  4. Operation Management: Failure Reports • What type of failures happened? • How often did they occur? • How long where they? • Example: show me all downtime caused by magnet power supplies Andreas Luedeke 2.June.2010 Page 4 of 12

  5. Controls Tools needed for Failure Analysis • What controls tools are needed to do the job? • Automatic beam event detection • Tools to analyse beam events • Means to categorize beam events by their cause • Database of beam events • Tools to create statistics, reports, run overviews, ... • Develop an “Operation event logging system” • Event Logger • Defining events by rules, based on process variables • Automatic recording of events • Automatic collection of a set of infos • Event Browser: provide access to event data • Event Cause: assignment of causes to an event • Event Database: Automated statistics, User-run overviews, ... Andreas Luedeke 2.June.2010 Page 5 of 12

  6. Andreas Luedeke The Operation Event Logging System Andreas Luedeke 2.June.2010 Page 6 of 12

  7. Event Logger: “Event” creation • State diagram for each event • events depend on shift type (EPICS DB stores yearly schedule in array) • events may have precedence ordering (e.g. downtime stops lifetime event) • State machine: event logging process (tcl/tk) monitored by cronjob • All configuration and event data stored in oracle database Event inactive Start-rule “true” for t > t(start-delay) Event entry Stop-rule “true” for t > t(stop-delay) Event active Change of shift-type insert event entry ● store start-date evaluate event infos Event of precedence activated ● and shift-type insert event infos ● Andreas Luedeke 2.June.2010 Page 7 of 12

  8. Event Logger: “Info” creation • The event data: • Shift summaries (electronic logbook) • Alarm lists • Selected signals from channel archiver (e.g. beam current for downtime) • Create data references instead of copying data • No inconsistencies, safes bandwidth, no data conversion • Use of native application to view, export or extend data • Data references as “Uniform Resource Locators” (URLs) • All data sources have to be accessible by a web browser • Electronic logbook → anyway • Alarmhandler → via oracle database table • Channel archiver → generic PSI web interface to channel archiver • Web interfaces have to support data selection by time range • URLs are easy to communicate: just copy links into your e-mails! Andreas Luedeke 2.June.2010 Page 8 of 12

  9. Channel Archiver Web Interface • Web interface to channel archive • Features • Up to one 100 channels per plot • One interface to all channel archives • PHP function suite • Easy to extend • “oscilloscope view” of waveform data • Full functionality in URLs • Define archive to read: DIRECTORY=/archiver-data/LT/index& • Define time range: startDate=05/18/2009&startTime=17:00& • Define channel list: NAMES=FRED:test\nTED:ai.RVAL& • Define axis for each channel TED:test=y2& Andreas Luedeke 2.June.2010 • Web interface to channel archive • Features • Up to one hundred channels per plot • Two Y-axis: linear/log, fixed range or auto-scale • One interface to all channel archives • Implemented as PHP function suite • Easy to extend • Full functionality interfaced in URLs! • Supports waveform “oscilloscope view” • URL functionality • Define time range • startDate=09/11/2009& • Define channel list: • NAMES=FRED:test\nTED:ai.RVAL& • Define axis for each channel • TED:test=y2&

  10. Browser demo Andreas Luedeke 2.June.2010

  11. Acknowledgement • Archiver web interface: Gaudenz.Jud@psi.ch, Werner.Portmann@psi.ch • Event logger, Alarmhandler web interface: Andreas.Luedeke@psi.ch • More details see PRST-AB EPAC'08 Special Edition: • A. Lüdeke: The Operation Event Logging System of the Swiss Light Source • Thank you for your attention!

More Related