The LHC Alarm Service.

Transcription

1 LASER (Lhc( Alarm SERvice) ) Project Report November 7th cern/proj-laser M. W. Tyrrell. 7 November

2 Talk Outline: What is the LASER Project? History Mandate change? Work to be done Manpower planning. Conclusions. 7 November

3 What is the LASER Project: Provides: Naming of alarm states Accepts alarm states from any part of the LHC complex Structures the received information Processes this information Offers the processed information to interested parties 24/365 day operation Does NOT provide: Management of INB Level 3 safety alarms CSAM project But will accept INB Level 3 alarms. Software to detect faults and generate alarms Acceptance of normal events 7 November

4 History: Project launch - Mandate prepared: 12/09/00 User Requirement (UR) Survey prepared: 11/09/01 UR Document released: 4/3/02 Technology survey: > 2002 Decision not to use PVSS: 14/5/02 Decision not to use COAST: 4/9/02 Decision to use new technology: Java, J2EE platforms Enterprise Java Beans, Net Beans Platform Java Web Start JMS, Sonic middleware, hierarchical topic structures Controls Middle Ware (CMW), OPC 7 November

5 Mandate Change? ST has requested to be formally included in the Mandate description. PS has requested to be included in the scope of the project. If accepted, a possible solution would be: To consider LHC as encompassing both ST and PS, and mention them directly in the Mandate, together with SPS to be discussed 7 November

6 Work to be done: We have an operational Alarm System (AS): It covers all technical services and SPS Supplies PCR, TCR and Fire Station with alarms. ~45K alarm states defined Connects to ~70 front-ends ~60 different User Surveillance Processes () ~ 29 Common Alarm Processing Environments - (CAPE) Parts of this surveillance system will remain until?? CONCLUSION: We need a bridge from the old to new AS 7 November

7 Work to be done: We have an operational Alarm System (AS): Plan: Use the current (old) AS to verify the new Pass ALL alarms into both the new and old AS s Provides a graceful transition from old to new Already need a bridge from old to new Will also need a bridge from new to old Finally switch off the old chain, this will remove: Central Alarm Server - CAS RPC XMotif, X-protocol 1553 will remain 7 November

8 Alarm Console X Protocol Alarm Console X Protocol New Alarm Console Pub-Sub OLD system in BLACK NEW system in RED 45k alarm definitions CAS RPC CAS RPC New Alarm Manager Relay points CAPE 29 CAPE s LAS SSP LAS SSP 2 O/P Calls SSP Pub-Sub Relay m_alarm New SPS PVSS LLAS 1553 RPC AlrmSrv LocAlrm 70 front-ends 60 different s OLD LocAlrm m_alarm 1553 LLAS AlrmSrv OLD + NEW m_alarm 7 November RPC 2 O/P Calls LocAlrm

9 New Alarm Console OLD system in BLACK NEW system in RED Pub-Sub 200k alarm definitions! New Alarm Manager Business layer Pub-Sub LAS type O/P SSP LLAS AlrmSrv 1553 LAS type O/P LocAlrm m_alarm NEW ST.. PS.. LHC.. LHC EXPT.. PVSS ONLY THE NEW SYSTEM 7 November

10 Work to be done: Work to be done: Rewrite the NODAL s: ~28 The new alarm system: Finalise lib I/P, O/P interfaces to LASER Continue developing the business layer Continue developing the alarm console GUI Build the database support for the alarm system: Configuration, naming service, archive / statistics Verify the PVSS alarm system connection. Work with the users to: Perform Alarm Reviews reduce alarm definitions Interface and integrate their alarms to the new alarm system Verify the scaling of the alarm system with time Maintain the alarm system as technology changes 7 November

11 Manpower planning: To build the LEP alarm system: Period staff, 1 contract engineer, 1 fellow, 1 coorporant To build LHC alarm system + maintain existing: Period 2000, 3 staff, 1 student, GTD software contract (GTD/SC) Period 2001, 3 staff, 1 fellow, 1 cooperant, 1 student, GTD/SC Period 2002, 3 staff, 1 fellow, 1 cooperant, 1 student, GTD/SC: Placed a request for an OP support post? Period 2003, 2 staff, 1 fellow,? - (first prototype) Period 2004, 1 staff,??? - (operational system) Period 2005,???? To maintain the LHC alarm system through: Installation, commissioning & operation: : 2 staff, 1 fellow, 1 student > onwards: AS Domain specialist(s), software support. 7 November

12 Conclusions: Since the project was launched: LHC schedule changed twice. LHC beam now scheduled for 2007: This is a LONG way down the line! Which technologies will be available in 2007? AND which technologies of today will NOT be supported! We must keep an open mind We must stay as flexible as possible WE MUST STRIVE FOR COMMON SOLUTIONS Middleware: CMW / template, no template, SONIC, RMI, HTTP, Smart Sockets, CORBA, DIM, tcpip, UDP,.. Software BUS: push / pull, a bi-directional lib. 7 November

13 Conclusions:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! THE ALARM PROJECT WILL NEED AN IMPORTANT INJECTION OF PEOPLE FROM NEXT YEAR ONWARDS.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 7 November