1LHC COOP, Uwe EPTING, CERN, ST/MO LHC - Technical Infrastructure Monitoring Uwe EPTING CERN, ST/MO
2LHC COOP, Uwe EPTING, CERN, ST/MO Today’s Services Electricity HT, MT, BT, Energy Consumption, ENS Water Pumping Stations, Raw, Prim, Chilled, Demi,... Thermal Air-conditioning, Ventilation, Heating Vacuum Pumps, Pressures Safety Fire, Gas, Emergency Stop,... Hardware Front ends, Servers Control Network Cryogenics Pumps, Temperatures TCR 24h/day 365days/year Supervision Breakdown and stand-by services Troubleshooting coordination
3LHC COOP, Uwe EPTING, CERN, ST/MO Some Numbers TODAY: – ~ signals ~ alarms ~ others – ~ 440 Equipment types (Classes) – ~ 800 Mimic diagrams –Interaction with 8 Divisions, 22 groups more than 70 responsibles
4LHC COOP, Uwe EPTING, CERN, ST/MO Schedule TDS InstallationTIM Specification Publish/Subscribe Mechanism Message Oriented Data Transmission Event Driven Data Reference Database TDS Operation Integration of New Alarms Removal of Old Equipment Definition of Equipment Drivers LEP operation Upgrade LHC operation User Requirements System Requirements Interface Definition Network Specifications HCI Conventions Alarm Integration Procedure Year ST/EL - ENS (12/1999) ST/CV - Wizcon ( 06/2000) Safety Alarms (CSAM)... Data Exchange Services Object Oriented Data TIM Integration Maintenance Contract for Software Support TIM Operation
5LHC COOP, Uwe EPTING, CERN, ST/MO Architecture TDRefDB reference database Excel Sheet Alarm Integration Procedure Accelerator/ Experiments SCADA PLCs MMD Multipurpose Monitoring Device PLCI/O DigitalI/O Analog EC Equipment Controller EC Equipment Controller EC Equipment Controller TDS Technical Data Server TCR SCR PCR XCR ANS Alarm Notification Server ELS Event Logging System CAS CERN Alarm System
6LHC COOP, Uwe EPTING, CERN, ST/MO Interfaces I/O - PLC - Fieldbus TCP/IP integration of PLCs and SCADA Middleware Operator Console CDIB CERN Data Interchange Bus Remote Access Raw Data WWW
7LHC COOP, Uwe EPTING, CERN, ST/MO Tag oriented vs. Device Oriented –TODAY: “device oriented tagnaming” –example: Naming Device Attributes Device Type Device Name System | Subsystem || Equipment Class ||| Localization ||| | Code ||| | | Name ||| | | | +--- Type ||| | | | | +- Attributes ||| | | | | | fwre01_ba6ci600regul_tmtr Class Member Attribute
8LHC COOP, Uwe EPTING, CERN, ST/MO Networking TODAY: –Physical networks pass mostly via PCR –Domain Name Servers are located in PCR –Maintenance done by SL/CO but they rely on Division IT ATTENTION: –Avoid Dependencies –Christmas Shutdown + Maintenance –Coordination Problems between responsible services
9LHC COOP, Uwe EPTING, CERN, ST/MO Hardware and OS TODAY: –All control software is HP-UX based –already first Linux Installation (JavaGUILS) –industrial PLCs (Siemens and Schneider) at equipment level BUT: –PCs and Windows NT tomorrow?
10LHC COOP, Uwe EPTING, CERN, ST/MO Software TODAY: –MMI with DataViews –Transmission with SmartSockets 5 (Middleware) on publish/subscribe basis –Data acquisition with industrial PLCs and standard software (ISEC - Industrial System Equipment Controller) –DataLogging with ELS (Event Logging System) in Oracle, JavaGUILS as user interface TREND: –SCADA Systems vs. Component Ware
11LHC COOP, Uwe EPTING, CERN, ST/MO Data Exchange Timing/Synchronization –Correlation of data –Granularity of time: Seconds.. Milliseconds? “Middleware” –SL/CO middleware project Working Groups: –CIWG - LHC Communication Infrastructure WG –LDIWG - LHC Systems Data Interchange WG –TimWG - Timing Working Group
12LHC COOP, Uwe EPTING, CERN, ST/MO Conclusion AIM: –provide a high quality monitoring of the services Requirements: –Define the role of the TCR for the LHC era –Which services should we provide? –Unique Alarm Display (today: CAS) –Coherent Mimic Diagrams –Clear Procedures for Operators –Unique Data Logging –Link to Maintenance Management Systems –Integration into Operator’s Console
13LHC COOP, Uwe EPTING, CERN, ST/MO Questions? More info: –