LHC production data expected for the LHC Control

LHC production data expected for the LHC Control System Ronny BILLEN SL/MR/DBS for the LHC Controls Project Data for LHC-CP - slide LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Outline 1. LHC Controls Project 2. Data management for LEP 3. Databases for LEP Controls Layout, Controls, Measurement, Logging, Alarms 4. How will LHC be different than LEP 5. Conclusions and Recommendations Part 2: LHC as an INB installation Data for LHC-CP - slide 2 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LHC Controls Project Ø Mandate, scope & objectives: Ÿ Design & implementation of future LHC control system Ÿ Overall architecture of HW & SW Ÿ Manage production of application SW Ø Intermediate objective: control system for Sector Test Ÿ it should not be different than the final system Ø Project Leader: Robin Lauckner + core team, link-people in equipment groups and projects Ø Ø LHC-CP reports to SLTC and member of Controls Board web site: Ÿ http: //lhc-cp. web. cern. ch/lhc-cp/ Ÿ EDMS site for documents (LHC Machine LHC Controls) Data for LHC-CP - slide 3 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Let’s look back: Data Management for LEP F Identified as a major issue before LEP construction F In 1982 Oracle RDBMS was purchased for this reason F Important data management projects: þ project planning ü +40000 activities; worst-case scenarios þ cables installation ü thousands of kilometres; selecting best access path þ equipment specification ü different constructors, teams of experts, project phases F F Machine experts specified and built their own data management applications. Standardised DBMS allows sharing of data Data for LHC-CP - slide 4 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Databases for LEP Controls Data for LHC-CP - slide 5 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Layout database: the machine blue-print Ø Ø Off-line Database Relatively static data, mostly numeric dimensions & relative positions of all components Information must be in place before real installation Ä allow computer simulations Ø Ø yearly update after technical stop Versioning for comparison between years Main users: accelerator physicists Data subset copied to Controls Database Data for LHC-CP - slide 6 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Databases for LEP Controls Data for LHC-CP - slide 7 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

The LEP Controls Ø Controlling thousands of parameters Ÿ Ÿ Ÿ Ø open/close vacuum valves switch on/off cooling circuits set magnet currents tweak high-voltage equipment … All controls information stored in Controls Database Ÿ names, actions, actual settings, references Ø History of actions and settings over time stored as well Ä allowed heuristic approach of fine-tuning LEP Ø Software 100% data driven Ÿ mainly Pro*C with graphical interfaces running on UNIX Data for LHC-CP - slide 8 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LEP Databases for Controls Data for LHC-CP - slide 9 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Measurement Database Ø Ø Equipment control requires adequate feedback There is no uniform measurement feedback Ÿ different measurement rates Ÿ different data structures Ÿ different communication methods Ø Ø Same information requested by many users or systems simultaneously causing real bottlenecks How did we solve this bottleneck? Ÿ Disable direct access to equipment for these measurements Ÿ put the real-time measurement data in the Oracle database Ø The data is generally overwritten (on-line use) Ÿ archiving is possible (using Oracle triggers) Data for LHC-CP - slide 10 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LEP Databases for Controls Data for LHC-CP - slide 11 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Data Logging - Graphical visualisation Data for LHC-CP - slide 12 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LEP Databases for Controls Data for LHC-CP - slide 13 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Alarm messages via database Data for LHC-CP - slide 14 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

How different will LHC be? Ø Ø Of course, LHC will be more complex and difficult with newer technologies and ideas. . . …but we do have the experience with LEP …and we will surely build on this experience From (my) data management point of view, LHC will not be very different, except for: Ÿ Configuration data: the structure will be in the database as well (meta-data for the control system itself) Ÿ Post Mortem data: combine and correlate huge amounts of data from different systems, synchronised with millisecond precision Data for LHC-CP - slide 15 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

What does controls need from production? Ø From Layout database Ÿ naming for addressing equipment Ÿ geometric, magnetic data on all installed elements Ÿ optics data Ø From Survey Database Ÿ alignment errors, corrections Ø From Magnetic Measurement database Ÿ calibration curves, hysteresis, temperature effect, . . . Ø From Powering database Ÿ powering circuits, magnet correspondence, actions Ø From other Equipment databases (vacuum, cryo) Ÿ naming, actions, settings, measurements Ÿ logging and post-mortem analysis Data for LHC-CP - slide 16 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

Conclusions and Recommendations þ þ þ J Similar to the control of LEP, data for LHC controls will be managed with a set of centralised databases In order to feed these LHC Controls databases, data from various production databases will be needed Oracle is the chosen RDBMS We will push Oracle to the limits, real time capabilities LHC could be controlled through the database as much as possible: The database is the machine (i. e. my vision) LHC-CP will need to look into your data, so please keep your data in a reasonable structure If your data is already in Oracle, we can work it out. . . Data for LHC-CP - slide 17 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

So much for control of the LHC. . . … now for some real problems! Traceability for LHC in the INB framework Data for LHC-CP - slide LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LHC Quality Assurance Plan Ø Ø G Ä è Implement a Total Quality Management System based on defect prevention & continuous process improvement Quality Assurance Plan defines quality activities & responsibilities, procedures, standards Quality is essential to make LHC a great success All LHC parts that will be manufactured and installed must be identified according to the QAP rules, ensuring traceability through its entire lifecycle However, traceability in the INB framework is slightly different. . . Data for LHC-CP - slide 19 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LEP Traceability Ø Ø Ø Ø Ø LEP is being dismantled completely We have to follow the rules for dismantling an “Installation Nucléaire de Base (INB)” for French authorities Track all equipment movements coming out of LEP Know exact location at any time Conventional and Radioactive material (zoning!) Use only Authorised disposal channels Temporary storage for reused equipment Radioactive waste remains at CERN for the moment Subject to INB inspections Data for LHC-CP - slide 20 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LEP Dismantling Traceability database Ø Ø Ø è 30000 tons of material to be evacuated 18 -month period, carefully planned Full-proof INB traceability Inventory & barcode stickers Ä Dedicated traceability Database Ÿ UML modelling; Java, C++ & PL/SQL implementation Ÿ barcode readers with remote database connectivity Ÿ result-oriented contract for tracking personnel Data for LHC-CP - slide 21 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

SPS Traceability Ø Ø Ø SPS is an INB since July 2000 (surprise!) Temporary system put in place for equipment that comes out of SPS (a lot!) Working Group is active on the future system Ÿ no complete inventory Ÿ there is too much Ÿ component going in component coming out Ÿ components can be conditioned Ÿ identification when it comes out Ÿ implies less work Ÿ naming can change Ÿ labels can deteriorate Data for LHC-CP - slide 22 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LHC Traceability K For LEP traceability, we started 15 years too late K For SPS traceability, we started 25 years too late J … For LHC traceability, we could start on time G Again, we should learn from our experience $ How (read mistakes) could the data management look like? Data for LHC-CP - slide 23 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

How could LHC traceability look like? Distributed database data administrator LHC INB Trace data LHC Installation & Layout data LHC Components Production data Data for LHC-CP - slide 24 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS

LHC Traceability K K J G For LEP traceability, we started 15 years too late For SPS traceability, we started 25 years too late … For LHC traceability, we could start on time Again, we should learn from our experience (read mistakes) $ How ¹ J could the data management look like? There is no hurry yet but it should be considered If the data is available in Oracle, we can work it out. . . Data for LHC-CP - slide 25 LHC Production database Workshop - 1 March 2001 R. Billen, SL/MR/DBS