1 / 14

Technical Infrastructure Monitoring (TIM) and CCC

Technical Infrastructure Monitoring (TIM) and CCC. TS Workshop May 4, 2004 P. Sollander, M. Batz – TS/CSE. Outline. Introduction to TIM Architecture Redundancy and availability Integrating TIM in CCC Project status and planning Conclusion. Introduction to TIM.

trinh
Télécharger la présentation

Technical Infrastructure Monitoring (TIM) and CCC

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. Technical Infrastructure Monitoring (TIM)andCCC TS Workshop May 4, 2004 P. Sollander, M. Batz – TS/CSE

  2. Outline • Introduction to TIM • Architecture • Redundancy and availability • Integrating TIM in CCC • Project status and planning • Conclusion P. Sollander, M. Batz TS/CSE

  3. Introduction to TIM • Control system for technical infrastructure • Technical Control Room (TCR) • CERN Control Centre (CCC) • Replaces current operational Technical Data Server (TDS) • Standard CERN hardware & software components for cost reduction and support optimization • Standardized user interfaces for smooth integration in CCC P. Sollander, M. Batz TS/CSE

  4. 2006 1971 1991 1994 2003 P. Sollander, M. Batz TS/CSE

  5. TIM Functionality • Data acquisition from heterogeneous equipment • TS (electrical distribution, water, safety) • External (magnets, RF, vacuum, cryo…) • Mimic diagrams • Applications for fast accelerator start-up (GTPM) • Overview diagrams where no specialist view is available • Navigation to proprietary system interfaces • Alarms • Single alarm list for CCC • Logging • Archiving data • Display of archived data in histograms P. Sollander, M. Batz TS/CSE

  6. TIM Software Architecture Alarm system Logging TIM mimics Ext. client Scada mimics DIP Data Processing http Logging DB Conf. DB DIP/ TIM DIP PLC Ext. source Scada x 60 x 20 P. Sollander, M. Batz TS/CSE

  7. TIM Hardware Architecture CERN VPN Home users Office users CERN General Network Gateway TCR/CCC consoles Database cluster File server cluster Data processing cluster Technical Network Data acquisition PLC x 60 Scada x 20 P. Sollander, M. Batz TS/CSE

  8. TIM HP racks P. Sollander, M. Batz TS/CSE

  9. Redundancy & Availability • Design for 99% availability • Safety Integrity Level (SIL) 1 • Development, configuration and maintenance guidelines • Redundant • Processes • Servers • Disks • Racks • Electrical supplies • Network components P. Sollander, M. Batz TS/CSE

  10. Different control systems in the CCC P. Sollander, M. Batz TS/CSE

  11. Standardized mimic diagrams • The future CCC operators will use many user interfaces • A standardization is absolutely necessary! • Scada Application Support Group (SASG) • Mandate to unify CERN user interface standards • Layout, colours, symbols, navigation, … • Includes, TCR, PCR, vacuum and cryo people • PCR white book • Being written • A compilation of all PCR operator requirements for their control room (including user interfaces) • No collaboration with TCR and cryo operators (yet!?) P. Sollander, M. Batz TS/CSE

  12. 2004 2005 Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Project status & planning TIM HW installation SW setup accounts, file servers system software SonicMQ, OC4jsetup Gen. driver design GTPM pilot TDS switch off TDS driver Rules design and implement PLC driver design + impl. DIP driver Configuration design System configuration Editor and viewer design GTPM migration GTPM development Remaining driver design + impl. (SCADA, PLC, OPC, …) Operation and Maintenance UMMI migration LASER alarm integration System tests Tuning Database Mimics Data processing Drivers ADMIN/other P. Sollander, M. Batz TS/CSE

  13. Conclusion • Integration in CCC • TIM Hardware and Software architecture choices made in view of integration • Must be integrated with other systems in CCC • Safety, access, accelerator, cryogenics and vacuum controls • CCC operator consoles must be agreed by all future operators • Choice of operating system • User interface standards • AB operations white book • Successful integration depends on departmental commitment and inter-departmental collaboration • Availability • System designed for 99% availability, but • Overall availability depends on the connected systems • Planning • On time, pilot in July and switch off TDS in December • Budget • 20 % below budget (grouped purchasing and own development) P. Sollander, M. Batz TS/CSE

  14. More information on TIM http://ts-project-tim.web.cern.ch/ts-project-tim/ P. Sollander, M. Batz TS/CSE

More Related