CERN LASER Alarm System Katarina Sigerud CERN ACS

  • Slides: 15
Download presentation
CERN LASER Alarm System Katarina Sigerud, CERN ACS workshop, 9 October 2005 CERN LASER

CERN LASER Alarm System Katarina Sigerud, CERN ACS workshop, 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud

Content l Introduction l Scope l System overview l Status 9 October 2005 CERN

Content l Introduction l Scope l System overview l Status 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 2

Introduction The LHC alarm service l Delivers an alarm service for the operation of

Introduction The LHC alarm service l Delivers an alarm service for the operation of the CERN accelerator chain and technical services l 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 3

Scope l Deals with abnormal situations – Fault states (FS) – Range from severe

Scope l Deals with abnormal situations – Fault states (FS) – Range from severe alarms to warning states l Provides – FS collection, analysis and distribution, definition and archiving – Dedicated alarm consoles l Does not perform surveillance – Responsibility of user surveillance programs (USP) –alarm sources – Provided by application writers and equipment specialists 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 4

System overview A distributed, layered system l Layers communicate via well -defined interfaces l

System overview A distributed, layered system l Layers communicate via well -defined interfaces l Resource tier l – Dispersed set of sources (USP’s) detecting FS changes l Business tier – Implements business logic and services l Client tier – Dedicated consoles and software clients 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 5

Resource tier Consists of a dispersed set of sources (USP’s) l Communicates with business

Resource tier Consists of a dispersed set of sources (USP’s) l Communicates with business tier via the LASER Source API l – Triggers FS changes – Sends ‘Keep-alive’/Synch message l Implemented on a variety of platforms and OS 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 6

Close up on FS triggering try { Fault. State fs = Alarm. System. Interface.

Close up on FS triggering try { Fault. State fs = Alarm. System. Interface. Factory. create. Fault. State(ff, fm, fc); fs. set. Descriptor(Fault. State. ACTIVE); fs. set. User. Timestamp(new Timestamp(System. current. Time. Millis())); Properties props = new Properties(); props. set. Property(Fault. State. ASI_PREFIX_PROPERTY, "prefix"); props. set. Property(Fault. State. ASI_SUFFIX_PROPERTY, "suffix"); props. set. Property("TEST_PROPERTY", "TEST_VALUE"); fs. set. User. Properties(props); alarm_source. push(fs); } catch (ASIException e) {. . . } 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 7

Business tier services l FS collection, analysis and distribution – FS changes are asynchronously

Business tier services l FS collection, analysis and distribution – FS changes are asynchronously and sequentially collected from sources – Different techniques are used to reduce the number of alarms distributed – FS’s are distributed into a hierarchy of domains of interest l l FS definition – FS definition inserts, deletes, updates – FS relationships, used for reduction l FS archiving – FS and FS definition changes Source monitoring – ‘Watch-dog’ mechanism based on source’s ‘keep-alive’ message l Alarm console client configuration 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 8

Business tier technology l Relies on the Java 2 Enterprise Edition (J 2 EE)

Business tier technology l Relies on the Java 2 Enterprise Edition (J 2 EE) specifications – Java Messaging System (JMS) – Enterprise Java Beans (EJB) – Hibernate/Spring l Deployed on – Oracle Application Server Containers for J 2 EE (OC 4 J) integrated with Sonic. MQ 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 9

Close up on FS definition Mandatory attributes l FS static information – Id l

Close up on FS definition Mandatory attributes l FS static information – Id l FS relationships – Source • Fault family (System name) • Fault member (Identifier) • Fault code (Problem description) – Priority – Information Unique name Brief description Connection timeout Definition responsible – Categories • Cause • Action • Consequence – Piquet information • Help URL • Piquet GSM • Piquet email – Definition responsible – Location 9 October 2005 • • • Connect alarms to nodes and/or leaves in the category tree – Multiplicity reduction • Create the multiplicity parent and set the threshold value • Connect children alarms to the parent – Node reduction • Select the node parent • Connect children alarms to the parent CERN LASER Alarm System, ACS workshop - Katarina Sigerud 10

Close up on FS reduction l Multiplicity reduction l – A <threshold> number of

Close up on FS reduction l Multiplicity reduction l – A <threshold> number of multiplicity children FS are activated the multiplicity parent FS is activated The active multiplicity children are reduced – The multiplicity parent FS is a ‘dummy’ FS Node reduction – The node parent FS is activated the active node children FS are reduced – The node parent FS is a real FS Multiplicity parent Reduced multiplicity children 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 11

Client tier l l Dedicated alarm consoles and software clients Communicates with the business

Client tier l l Dedicated alarm consoles and software clients Communicates with the business tier via – The LASER Client API • FS changes are sent asynchronously, based on the set of categories and filters passed to business tier – The LASER Console API • Login and configuration facilities for the dedicated alarm consoles l The dedicated alarm consoles are based on the Net. Beans platform 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 12

Close up on alarm console 9 October 2005 CERN LASER Alarm System, ACS workshop

Close up on alarm console 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 13

Status l First version operational – CERN technical services – LHC power converters commissioning

Status l First version operational – CERN technical services – LHC power converters commissioning – More detail at First operational experience with LASER at ICALEPCS, TH 2. 3 -7 O l Next – Continuously provide alarm service – Prepare for startup of accelerator complex in 2006 – On-line FS definition updates 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 14

Alarm. Service@cern. ch 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina

Alarm. Service@cern. ch 9 October 2005 CERN LASER Alarm System, ACS workshop - Katarina Sigerud 15