Adapting the city. Building & Infrastructure Dr Tim Whitley Associate Director, Arup.
Technical Infrastructure Monitoring (TIM) and CCC
description
Transcript of Technical Infrastructure Monitoring (TIM) and CCC
TS/CSE – TIM and CCC
Technical Infrastructure Monitoring (TIM)
and
CCC
TS WorkshopMay 4, 2004
P. Sollander, M. Batz – TS/CSE
4 May, 2004 P. Sollander, M. Batz TS/CSE 2
TS/CSE – TIM and CCC
Outline
• Introduction to TIM• Architecture• Redundancy and availability• Integrating TIM in CCC• Project status and planning• Conclusion
4 May, 2004 P. Sollander, M. Batz TS/CSE 3
TS/CSE – TIM and CCC
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
4 May, 2004 P. Sollander, M. Batz TS/CSE 4
TS/CSE – TIM and CCC
19711991199420032006
4 May, 2004 P. Sollander, M. Batz TS/CSE 5
TS/CSE – TIM and CCC
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
4 May, 2004 P. Sollander, M. Batz TS/CSE 6
TS/CSE – TIM and CCC
TIM Software Architecture
PLCExt.
sourceScada x 20x 60
Data Processing
TIMmimics
LoggingExt.
client
Conf.DB
LoggingDB
Scadamimics
Alarmsystem
DIP
DIP
DIP/TIM
http
4 May, 2004 P. Sollander, M. Batz TS/CSE 7
TS/CSE – TIM and CCC
TIM Hardware Architecture
Data processing
cluster
Databasecluster
Dataacquisition
TCR/CCCconsoles
Scada x 20PLC x 60
Office users
Home usersCERN VPN
Gateway
Technical Network
CERN General Network
File servercluster
4 May, 2004 P. Sollander, M. Batz TS/CSE 8
TS/CSE – TIM and CCC
TIM HP racks
4 May, 2004 P. Sollander, M. Batz TS/CSE 9
TS/CSE – TIM and CCC
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
4 May, 2004 P. Sollander, M. Batz TS/CSE 10
TS/CSE – TIM and CCC
Different control systems in the CCC
TIM AcceleratorControls
Cryogenics Vacuum
Serverhardware
HP ProLiant, Sun fireAB/CO, IT/CO
HP ProLiant,Sun fire
HP ProLiant PC-shop server
Server software
OC4J, SonicMQ, OracleIT/DB, AB/CO, IT/DB
OC4J, SonicMQ,Oracle
PVSS PVSS
Mimics diagrams
JViewsTS/CSE, AB/CO
JViews + own PVSS PVSS
Alarm system
LASERAB/CO
LASER PVSS, LASER PVSS, LASER
Datalogging
LHC/TCRAB/CO, TS/CSE
LHC/TCR PVSS,LHC/TCR PVSS,LHC/TCR
4 May, 2004 P. Sollander, M. Batz TS/CSE 11
TS/CSE – TIM and CCC
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!?)
4 May, 2004 P. Sollander, M. Batz TS/CSE 12
TS/CSE – TIM and CCC
TIM
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb
2004 2005
Project status & planning
Database Mimics Drivers ADMIN/other
HW installation
GTPM migration
Data processing
TDS driver
PLC driver design + impl.
DIP driver
Configuration design
System configuration
Remaining driver design + impl. (SCADA, PLC, OPC, …)
UMMI migration
System tests
GTPM development
Editor and viewer design
Gen. driver design
Rules design and implement
SonicMQ, OC4j setup
SW setup accounts, file servers system software
LASER alarm integration
GTPM pilot TDS switch off
Tuning
Operation andMaintenance
4 May, 2004 P. Sollander, M. Batz TS/CSE 13
TS/CSE – TIM and CCC
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)
4 May, 2004 P. Sollander, M. Batz TS/CSE 14
TS/CSE – TIM and CCC
More information on TIM
http://ts-project-tim.web.cern.ch/ts-project-tim/