1 / 11

Creating a common understanding on Adverse events information requirements

Creating a common understanding on Adverse events information requirements. CCC-TI Isabelle Laugier Nov 2 nd 2012. BE-OP-TI environment. The TI operates 24 hours a day, 365 days a year monitoring the entire technical infrastructure of CERN. Different domains:

takoda
Download Presentation

Creating a common understanding on Adverse events information requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. BE-OP-TI environment • The TI operates 24 hours a day, 365 days a year monitoring the entire technical infrastructure of CERN. • Different domains: • the electrical distribution network including energy consumption (works only if your computer has the rights). • 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. I. Laugier BE/OP

  3. 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. I. Laugier BE/OP

  4. TI-Logbook: Main page I. Laugier BE/OP

  5. BE/OP Webpiquets • Home made application with APEX and PHP. I. Laugier BE/OP

  6. 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 I. Laugier BE/OP

  7. 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. I. Laugier BE/OP

  8. BE-OP-TI context I. Laugier BE/OP

  9. 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. I. Laugier BE/OP

  10. Process Courtesy of Peter Sollander I. Laugier BE/OP

  11. 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 • Introduction of processes • improvement of communication management • « Single point » of data management with high quality data, available during incident. I. Laugier BE/OP

More Related