2. 16 December 2003 LHC Logging Review Meeting LHC Logging Review R. Billen, M. Marczukajtis, M. Peryt AB-CO-DM

3. R. Billen 16 December 2003LHC Logging Review Meetingslide 2 Agenda  Introduction  Recapitulation Architectural Overview  Current Implementation – Necessary modifications  Outcome logging of TT40 extraction tests  Needs for QRL milestone April 2004  Proposed Logging Data Retrieval Interface  Necessary Resources for next milestones  Further needs for TI8 and Hardware Commissioning milestones  Next steps

4. R. Billen 16 December 2003LHC Logging Review Meetingslide 3 Introduction  Mandate: Analysis, design, procurement of Logging Facilities for future LHC Controls System Information management for LHC performance improvement Information management for LHC performance improvement Meet INB requirements for recording beam history Meet INB requirements for recording beam history Make available long term statistics for management Make available long term statistics for management Avoid duplicate logging efforts Avoid duplicate logging efforts  Scope: Analyze experience, capture requirements Analyze experience, capture requirements Implement first version to support QRL Implement first version to support QRL Logging data from TT40 extraction tests. Logging data from TT40 extraction tests. The request was presented at the LHC-CP meeting of 08 Oct 2002.The request was presented at the LHC-CP meeting of 08 Oct 2002. Investigate interface with Alarms and Post-Mortem systems Investigate interface with Alarms and Post-Mortem systems  Objectives: Establish logging facility for TT40 and QRL, scalable to LHC Establish logging facility for TT40 and QRL, scalable to LHC Major project review after initial validation Major project review after initial validation

5. R. Billen 16 December 2003LHC Logging Review Meetingslide 4 Milestones  Software Specifications: Functional & Design Specifications: Functional & Design Implementation Implementation Testing & validation Testing & validation  Database Design Taking advantage of Oracle 9i new features Taking advantage of Oracle 9i new features  Hardware for Database & Application Server Development environment Development environment Production environment Production environment  Project Management Interactions with clients, peers & management Interactions with clients, peers & management Progress follow-up, decision making Progress follow-up, decision making Acceptance Acceptance  All slipped due to change in QRL planning, priority changes and TT40 extraction tests as surprise client

6. R. Billen 16 December 2003LHC Logging Review Meetingslide 5 LHC Logging Architecture Data Extraction Station with the Thin Client Web Browser with the Thin Client LHC Logging Application Server – Oracle9iAS (ABOFS1) Data Extraction and Manipulation (Struts, Servlets) Data Loading Servlets Container for J2EE (OC4J 9.0.3, Oracle9iAS) Data Extraction Station with the Fat Client LHC Logging GUI Application LHC Logging Data Server Oracle 9.2 (DEVDB9) LHC Logging Schema and Code Data Producer Station LHC Logging Data Input API 4 Java Data Loading Client LHC Logging Schema and Code Data Loading Servlets LHC Logging Data Input API 4 Java Data Loading Client LHC Logging GUI Application Web Browser with the Thin Client Data Extraction and Manipulation (Struts, Servlets) Container for J2EE (OC4J 9.0.3, Oracle9iAS)

7. R. Billen 16 December 2003LHC Logging Review Meetingslide 6 Current Implementation  Database Server Need for Oracle 9i instance (as specified in design) Need for Oracle 9i instance (as specified in design) Use of DEVDB9: First central/public Oracle9i instance Use of DEVDB9: First central/public Oracle9i instance Development environment… quota of 4 GB… Development environment… quota of 4 GB… …Production environment required for QRL commissioning …Production environment required for QRL commissioning Evolution of space requirements estimations Evolution of space requirements estimations 2003 0.5 GByte  1.0 GByte used2003 0.5 GByte  1.0 GByte used 2004 50 GByte2004 50 GByte 2005 500 GByte2005 500 GByte 2006 1,000 Gbyte2006 1,000 Gbyte  Application Server Need for server and servlet container (web, java) Need for server and servlet container (web, java) Operational server purchased ABJAS4 (PC) Operational server purchased ABJAS4 (PC) Current deployment on ABOFS1 (HP-Proliant) Current deployment on ABOFS1 (HP-Proliant) Final version and configuration to be established Final version and configuration to be established

8. R. Billen 16 December 2003LHC Logging Review Meetingslide 7 TT40 Logging Outcome  Feedback presented by Brennan Goddard at the SPS2001 Review meeting: Day 1: Results underwhelming, despite lots of preparatory list-making and detailed ‘user requirement’ collection System failed to log essential data (p+ on TED) Inhomogeneous (dare one even say ‘ad-hoc’?) solutions Some data types not catered for (arrays) Some equipment not included Insufficient process monitoring Generic data retrieval methods poor (i.e. non-existent) Day 2: System improved somewhat Succeeded to log essential data Still difficulties with some data types Most (all?) specified equipment was included… Process monitoring still not good Still some difficulties with changes to beam mode Prototype data retrieval system deployed ~on day of test In Summary: Patchy at the outset - some improvement for second test Logging system status management (or at least information) required Logging appears non-trivial; problems will multiply for TI 8 and beyond Data retrieval and viewing not great Recommendations: Should be considered as a system and not as a load of processes which happen to be bunging data into some database, sometime, somewhere. Need to consider higher level requirements like surveillance, data retrieval, process control, status. Earlier and more extensive tests required Facts, impressions and constructive comments by ‘Mister TI8’

9. R. Billen 16 December 2003LHC Logging Review Meetingslide 8 Requirements for QRL  QRL originally identified as first client of the Logging System  Interviews at the end of 2001 Cryogenics: M. Sanmarti, L. Serio Cryogenics: M. Sanmarti, L. Serio Vacuum: I. Laugier, R. Gavaggio Vacuum: I. Laugier, R. Gavaggio General Services: U. Epting, R. Martini General Services: U. Epting, R. Martini Alarms: M. Tyrrell Alarms: M. Tyrrell Post Mortem: J. Wenninger Post Mortem: J. Wenninger  None of these clients are using the Logging today  Dedicated meetings with Alarms and Post-Mortem continued, but no conclusion is reached   … take your chance for an update!

10. R. Billen 16 December 2003LHC Logging Review Meetingslide 9 Data Retrieval Interface  Lightweight Browser-based GUI for LHC Logging Data Visualization  Draft Functional Specification LHC-CL-ES-0003 General user requirements based on: General user requirements based on: Initial interviewsInitial interviews Experience from GUILS & JavaGUILS (LEP era)Experience from GUILS & JavaGUILS (LEP era) Experience from STRIDE (String2 era)Experience from STRIDE (String2 era) Illustrated by prototype implementation Illustrated by prototype implementation  Draft Architectural Design LHC-CL-ES-0004 Design details Design details

11. R. Billen 16 December 2003LHC Logging Review Meetingslide 10 Specifications Outline  Chapter 2 - Getting Started: How to start up the GUI  Chapter 3 – Choosing Data Representation: Making the choice for the data output to be presented in summarized, graphical or textual format  Chapter 4 - Selecting Logging Channels: Making the user selection of logging channels  Chapter 5 - Defining Time Window: Set the start time and end time for the user selection of logging channels  Chapter 6 - Retrieving Logged Data Summary: Get the data output in a summarized format  Chapter 7 - Retrieving Logged Data to Chart: Get the data output in a graphical chart-type format  Chapter 8 - Retrieving Logged Data to File: Get the data output in an exportable file format  Chapter 9 - Administering Metadata: Manipulating and saving specifications on logging channels  Chapter 10 - Customizing User Profile: Manipulating and saving your user profile with personal specifications on charting parameters

12. R. Billen 16 December 2003LHC Logging Review Meetingslide 11 Development Resources  Maciej Peryt: since September 2001 01.01.2004: Will move to Configuration Management 01.01.2004: Will move to Configuration Management  Maciek Marczukajtis: since May 2002 30.07.2004: final end of Fellowship contract 30.07.2004: final end of Fellowship contract  So… that’s it???  Chris Roderick: as from 01.01.2004 31.03.2004: final end of Fellowship contract 31.03.2004: final end of Fellowship contract  QRL commissioning in April 2004 is a major milestone for the Logging System  As from summer 2004 things better be in place! Including production environment for DB and AS Including production environment for DB and AS

13. R. Billen 16 December 2003LHC Logging Review Meetingslide 12 TI8 and Hardware Commissioning  TI8 extraction tests September 2004  Sector 7-8 Hardware Commissioning May 2005  Is there anything that we missed?  …Speak up now or remain silent forever…

14. R. Billen 16 December 2003LHC Logging Review Meetingslide 13 Next Steps  Update Specification documents  Establish correct check & approval lists  Make browser-based GUI as functional as possible  Major evaluation of overall system during QRL commissioning  Decide on need for dedicated GUI application  Possibly seek for help from CO/AP and extra resources  Thank you…