Transcript No Slide Title

Ethernet for cryogenic
Keep Cool, everything is under
Control
Presentation Outline
Covered equipments
Milestones
What is cryogenics
Control Specification
Communication infrastructure
Conclusions/questions
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Covered equipments
LHC RING
The eight LHC main ring cryoplants, their infrastructure
The cryogenic equipment in the machine cryogenics tunnel
Cryogenics for the reference magnets (not included in the present
contract)
LHC EXPERIMENTS
The ATLAS helium external common cryoplant
The ATLAS liquid Argon cryogenic system (external and proximity)
The ATLAS proximity and internal helium cryogenics for all
superconducting magnets
The CMS helium external cryoplant
The CMS proximity and internal helium cryogenics
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Project Milestones
Project start-up May 99
Technical Specification emitted December 99
Contract Awarded in June 2000
First prototype March 2001
First application (1.8K PM18) June 2001
First sector implementation 2003
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Typical LHC Cryogenic Architecture
Gaseous helium storage
Surface
QSV
1.8K Cryoplant 4.5K Cryoplant
QSCC
4.5K Cryoplant 1.8K Cryoplant
QSCB
QSCA
Underground
5
QSCC
3
QSRB
6
2
QSRA
7
1.8
QURC
QURA
QURC
QUI
QRL
Ring
4
Sector
28/09/2001
Interconnection box
QRL
Sector
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
1
8
I/O Channel Volume & Repartition
DI
DO
AI
AO Total I/O
Point 2
1195 198 2452 633
4478
Point 1.8
1430 271 2317 669
4687
Point 4/6/8 2499 399 4684 1276
8858
Point 3/5/7
80
27
36
2
145
Total Acc. 10362 1747 18929 5136 36174
Atlas He
1674 622 1236 253
3785
Atlas Ar
599 215
337
93
1244
CMS
431 184
487
80
1182
TOTAL
13066 2768 20989 5562 42385
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Data exchange with other systems
Cryo provide
Quench Diagnostics (cryo origin)
Temperature history (sampling time 10s)
Time stamping at 10ms of events
Recovery evaluation
Helium filling & magnet cool-down trend curves
Typical trends for comparison & estimation
Magnet powering
1 Cryo OK status per sector
Cryo needs
 beam injection status , beam intensity, Beam squeezing status.
 Vaccum system status
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Control Constraints & Limits
 The Human & equipments safety is not the mandate of
the cryogenics control system
 The cryogenic system is slow (PCU cycle time =500 ms)
communication delay is not a issue
 The process safety is performed in the control system
hence :
 The cryogenic control loop can survive to a short interruption of the
communication (between 1 to 5 seconds) more time can lead to a
cryoplant stop
 In case of communication failure a process failure information cannot
be transmitted to the PLC the process can be affected and the
cryoplants stopped
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Cryoplant/Utility failures effect
Effect
no more pumping > pressure rise in magnet>
temperature rise > preventive current ramp down.
No helium loss within magnet if stop <5h and
quench valves not leaking (wishful thinking)
Recovery
Stop
duration
1.8 K
cryoplant
Magnet
cooling
Total
1 second
4.5K
cryoplant
recovery
1 hour
2 hours
3 hours
6 hours
2 hours
1 hour
3 hours
5 hours
11 hours
5 hours
2 hour
4 hours
8 hours
19 hours
 time recovery < 6+3*stop duration (LEP2 2h+7*stop duration)
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Hardware Architecture (Specified)
Integration in CERN
backbone
Supervision Layer
Cent. Supervision
Plant Net work
Local & Central
Operation Capabilities
Local Supervision
Control Layer
Engineering Workstation
Control Network
1.8K
PCU
28/09/2001
Field interface
Field Network
Field interface
Common
PCU
PCU
Field Network
Field Network
Field Layer
Sector
Field interface
PCU
Field Network
4.5K
PCU Information
exchange & Common
Programming Tool
Field interface
Field interface
Field interface
Field interface
Field interface
Field interface
Field interface
Field interface
Field interface
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
1 Unit per cryogenic
subsystem executing the
process control activity
Distributed Field
Interfaces Linked by
standard field bus to
connect the sensors/
actuators
Communication specification



Networks/ Protocols
 Plant Network must be integrated into the
CERN Backbone (ethernet TCP-IP)
 Control network based on ethernet TCP-IP
 The requested field network was
PROFIBUS DP
 nor true for the tunnel due to the
radiative environment
Access to data
 An external system shall be allowed to
access selected real-time information in
the supervision layer
 It shall be possible to access external ‘realtime’ data at the supervision level
 data exchange shall be possible at the
field Level
Synchronization
 It shall be possible to synchronize each
Control network to a CERN based timing
system with a minimal resolution of 10
ms.
 Each PCU, OWS, DS, and field interface
shall be synchronized to the Control
network time within less than 10 ms
28/09/2001

Data rate transfer
 2 PCU connected to a control network
must be able to exchange 100 floating
variable at 2 hz
 Up to 5000 process data (trends) shall be
transmittable from each Control network
every 2 (two) minutes to the CERN longterm data storage (at present Oracle®)
 Up to 2000 process data in floating format
shall be extractable from each Control
network to CERN WAN per period of 10
seconds
 Alarms and events must be transmitted to
OWS within 2 seconds
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Typical Implementation (IP8)
Ethernet backbone (IT-CS)
Local Cryogenic control room
OWS
EWS
SCADA data servers
Ethernet local connection (LHC-IAS/IT CS)
LHCCa
Sector A
LHCA
Common
LHCB
LHCCb
Sector b
Ethernet surface infrastucture (IT-CS)
SH8
SD8
QSRA
SDH8
QSCA
QSCCa
QSCCb
QSCB
US IP8
QSRB
QSD
QSV
QURA
US IP7
Alcove
Alcove
QUI
QURCa
sector
sector
28/09/2001
Alcove
US IP1
sector
sector
sector
QURCb
sector
sector
Alcove
sector
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Conclusion
 Ethernet will be extensively used in the cryogenic
control infrastructure
 It will be use with operational constraints
Maximum downtime allowed for control loop (1 to 5 sec) etc..
Intervention on network shall be coordinated
The powering & the interaction with the Emergency switch must
be carefully studied to be compatible with the communication
infrastructures
 In case of failure of the communication the process
safety in not guaranteed
 Human & equipment Safety is not going through
Ethernet and guaranteed at a lower level
 Management of the communication infrastructure by
IT/CS
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS
Questions
How can we protect the access to control
equipment via network?
Will my neighbor eat my bandwidth?
Is Private network solution a better solution for
my system?
How much I will pay for the connection to the
control infrastructure?
…..
28/09/2001
Ethernet for Cryogenics
Ph.Gayet-LHC-IAS