1. Creating a common understanding on Adverse events information requirements CCC-TI Isabelle Laugier Nov 2 nd 2012

2. Apologies Join CCC-TI 3 months ago so no detail on historical decision; why it has been chosen like that? 02/11/2012I. Laugier BE/OP

3. BE-OP-TI environment The TI operates 24 hours a day, 365 days a year monitoring the entire technical infrastructure of CERN.TI Different domains: – the electrical distribution network including energy consumption (works only if your computer has the rights).energy consumption – heating, cooling, ventilation and air conditioning equipment – safety installations and cryogenic systems – coordination and reporting after major infrastructure disruptions – Corrective maintenance => A simple software to deal with all these very different domains. 02/11/2012I. Laugier BE/OP

4. Main software: TI-Logbook Home made software using Apex technology developed in 2009 Updated constantly since then, following the introduction of new products at Cern level (Infor EAM, impact, etc…) and the new requirements or requests The main request : Must be user friendly to be useable during rush! For each phone call, lots of different information may be entered in the logbook. 02/11/2012I. Laugier BE/OP

5. TI-Logbook: Main page 02/11/2012I. Laugier BE/OP

6. BE/OP Webpiquets Home made application with APEX and PHP. 02/11/2012I. Laugier BE/OP

7. During operation… The more useful pages are : – Today’s event => a dashboard – Create Work Order => to send a request to Infor EAM – Global list => list of already created item 02/11/2012I. Laugier BE/OP

8. For post mortem usage… Logbook is also used for post mortem analysis. In this case, the more useful pages are: – MERI: Major Event Report Interface – Global list : with all minor events, notes, major events useful to prepare meeting like TIOC, FOM – Meeting Wizard: items pre-selection for meetings – One internal blog (outside logbook application) for a week summary. 02/11/2012I. Laugier BE/OP

9. BE-OP-TI context 02/11/2012I. Laugier BE/OP

10. Links between Logbook and Infor EAM Done by Web Services inside Apex Bidirectional, we send Work Order details, Infor EAM sends us back a WO number. Recently, the main problem was solved: individual connection and expirable session id was replaced by an indeterminate authorization for a group of people. 02/11/2012I. Laugier BE/OP

11. Links between Logbook and Impact Data are seen inside Ti-Logbook using views in impact db. Data is used to help during TIOC meeting Ongoing works included inside TI-Logbook will be moved to Impact A bidirectional link between Impact and Ti- Logbook must be foreseen for the future: – an ODM creation does not send information to Impact. – A change of Impact Approval state for TIOC meeting Approval must be possible inside TI-Logbook. 02/11/2012I. Laugier BE/OP

12. Links between Logbook and other Cern database Direct link to Snow db to link snow number and ODM number Direct link to geosip for “batiment” checking Direct link to foundation for personnel data checking Direct link to EN-EL database for their equipment checking. Direct view on EDH to get IS37 information 02/11/2012I. Laugier BE/OP

13. Usage of TI-Logbook for a Major Event A Major Event is created by BE-OP-TI when this event affects Beam operation. One or more equipment groups can be concerned by this ME. They will have to comment on this event. Each ME follows a process ( change of state between its creation and its closure) Each ME is discussed during TIOC meetings and an EDMS document is created and archived. 02/11/2012I. Laugier BE/OP

14. Courtesy of Peter Sollander Process 02/11/2012I. Laugier BE/OP

15. Future Project to use a common logbook between CCC and equipment groups Interested by some “Frequentis” ideas concerning Integrated Incident and Crisis Management (ICM) http://www.frequentis.com http://www.frequentis.com – Introduction of processes – improvement of communication management – « Single point » of data management with high quality data, available during incident. 02/11/2012I. Laugier BE/OP