Abstract

Modern 3rd generation synchrotron light sources aim for 100% availability. No single beam interruption is acceptable and every beam disturbance should be investigated: what caused the interruption? Can it be avoided in the future? If it cannot be avoided, how can the recovery be accelerated? An automated event recording system has been implemented at the Swiss Light Source (SLS) in order to simplify beam distortion investigations with respect to a well-defined metrics. The system identifies beam disturbances and records automatically the type and duration of the event. Relevant information of the event, like control system archive data or shift summaries, is linked to the event and presented in Web pages. Tools for the automated evaluation of alarm logs are provided that generate summaries of a beam distortion. On the basis of this information each event will be assigned to a failure cause. The means to filter the events are provided. We will describe the concept and the implementation of the system at the SLS and our experiences with it. Finally, the SLS operation event logging system will be compared with failure analysis at other light sources.

Highlights

  • No single beam interruption is acceptable and every beam disturbance should be investigated: what caused the interruption? Can it be avoided in the future? If it cannot be avoided, how can the recovery be accelerated? An automated event recording system has been implemented at the Swiss Light Source (SLS) in order to simplify beam distortion investigations with respect to a well-defined metrics

  • This hierarchy is visible to the operator when he acknowledges the alarm in the interactive user interface, but it is not visible in the flat alarm log

  • Several facilities do keep a manual database of beam outages and distortions

Read more

Summary

MOTIVATION

A large fraction of the work of an operations manager is dedicated to the analysis of operations data. A light source wants to know all about loss of the stored beam and about problems with a short beam lifetime. We define the two event types: a ‘‘downtime’’ event starts, when the beam current is below 50 mA and stops when 400 mA is stored. A beam loss is handled by the operator in the control room He normally does not need to fully understand what caused the beam loss, he just refills the storage ring. A beam loss where an alarm shows that a magnet power supply in the storage ring failed will be assigned to the system ‘‘magnet power supplies.’’ The magnet power supply group will use the collected data to find out which power supplies caused beam losses in the past, how often, and how long. The operations manager will use the data to keep himself up to date with the machine operation, to find out when problems reoccur, for the planning of resources, for upgrade plans, and so on

BASIC SPECIFICATION
System overview
Automatic event logging
Event cause assignment
Event alarm evaluator
Event browser
Automated event statistics
Automated operation reports
Technology of the implementation
Definitions of categories
Event rules and precedence
Event rule variables
Event information data references
EPICS channel archiver Web interface
EPICS alarmhandler Web interface
DUO logbook for SLS shift summaries
Event alarm evaluator configuration
EVENT DATABASE EXPERIENCE
SURVEY ON FAILURE ANALYSIS AT LIGHT SOURCES
Operation metrics
Failure documentation
Survey conclusions
SUMMARY
VIII. OUTLOOK
Findings
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.