Wir schaffen Wissen – heute für morgen
Paul Scherrer Institut
Controls tools for operation management at the Swiss Light Sourceat the EPICS collaboration spring meeting 2010 in Aix-en-Provence
Andreas LüdekePaul Scherrer Institut
Operation Management: Beam Failure Analysis
Event: defined beam distortion → “bad lifetime”, “downtime”Infos: related data of event → logbook entries, alarms, archived dataCause: failure category of event → what caused it, where was it caused
Beam lifetime
Storage ring beam current
50 mA limit
4 hour limit
Timebad lifetime downtime
Page 2 of 122.June.2010Andreas Luedeke
Operation Management: Beam Failure Statistics
Page 3 of 122.June.2010Andreas Luedeke
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
Page 4 of 122.June.2010Andreas Luedeke
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, ...
Page 5 of 122.June.2010Andreas Luedeke
2.June.2010Andreas Luedeke
The Operation Event Logging System
Page 6 of 122.June.2010Andreas Luedeke
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 active
store start-date and shift-type
Event inactive
Event entry
● insert event entry● evaluate event infos● insert event infos
Start-rule “true” for t > t(start-delay)
Stop-rule “true” for t > t(stop-delay)
Event of precedence activated
Change of shift-type
Page 7 of 122.June.2010Andreas Luedeke
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!
Page 8 of 122.June.2010Andreas Luedeke
Page 9 of 12
Channel Archiver Web Interface
Web interface to channel archive- Featureso Up to one 100 channels per ploto One interface to all channel archives
- PHP function suiteo Easy to extendo “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&
2.June.2010Andreas Luedeke
Page 10 of 12
Browser demo
2.June.2010Andreas Luedeke
Page 11
Acknowledgement Archiver web interface: [email protected], [email protected] Event logger, Alarmhandler web interface: [email protected] 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!
Top Related