Status on services controls

1. Status on services controls DCS Workshop

2. Introduction • To operate, detectors will interface to a number of services such as: • Gas • Cooling and ventilation • Electricity • Magnets • Safety • This presentation tries to summarize the DCS aspects of the interface Thanks to service groups for their input DCS Workshop

3. Gas systems Primary gas Detector gas systems Detector DCS Workshop

4. Gas systems[responsibilities] • Primary gas • Build and maintained by TS/LEA • Gas Distribution and Supply (GDS) group • Detector gas systems • Build by the Gas Working Group (GWG) • According to specifications by the detectors • Controls is collaboration GWG and IT/CO • Maintenance and operation by GWG • Except very few specific operations DCS Workshop

5. Gas systems[primary gas] • Primary gas is stored in dewars or batteries at the surface (SG or outside) • Dewars are backed up by batteries • Batteries are usually doubled with automatic switchover • Information is available to the gas control system, and can, from there, be made available to the experiment DCS Workshop

6. Gas systems[detector gas systems] • A detector gas system consists of several ‘modules’ • mixer, pump, distribution, purification, etc. • The control of each gas system will be based on a PLC (one per system) • GWG is responsible for control of each gas system • Closed loop control, software in PLC • Guarantees autonomous and safe operation • Detector gas systems are maintained and operated by the GWG • according to well defined operational procedures (decided between GWG and user) DCS Workshop

7. Gas systems[detector gas systems] • A dedicated supervisory system will provide user interfaces etc. for the local operation (by GWG) of the gas systems • Based on PVSSII • Full control for gas experts and maintenance team • The experiment (detectors) is expected to have only limited interaction with the gas systems DCS Workshop

8. Gas systems[detector gas systems] • Read access to ‘any parameter’ in the gas control system from the DCS • The detectors to express their needs • No actions (control) are expected • ‘Meta commands’ available to the detector and experiment (to trigger a predefined sequence) • E.g. restart after power cut • Some control might be required for special monitoring equipment • E.g. drift velocity measurement DCS Workshop

9. Gas systems[detector gas systems] • Exchange of information via software • Mechanism and protocol to be defined • Common effort for all experiments • Access through ‘gateway’ (PC), no direct access to PLC’s • Interlocks (open/close contact) can be generated DCS Workshop

10. Gas systems ALICE DCS, global supervision and operation (PVSSII) Gateway PC PC GWG ALICE LAN (local) supervisionand operation byGWG (PVSSII) Global commands (restart) Monitoring (status, alarms, data) PLC High Voltagepower supply Interlock Gas System Detector DCS Workshop

11. Cooling and Ventilation Ventilation Air conditioning Primary Cooling Detector cooling Detector DCS Workshop

12. Cooling and Ventilation[responsibilities] • Primary cooling • Full responsibility of TS/CV • Detector cooling • Build and maintained by TS/CV, including controls • ‘Day to day’ operation by the experiment • Ventilation (including air conditioners) • Full responsibility of TS/CV DCS Workshop

13. Cooling and Ventilation[primary cooling & ventilation] • Both operated and maintained by TS/CV • Operated through their control systems (wizcon) • No interaction with experiment expected • Possibility for experiment to get information on these systems through ‘DIP’ (Data Interchange Protocol) DCS Workshop

14. Cooling and Ventilation[detector cooling units] • The control of the cooling units will be based on a PLC (one per cooling unit) • We assume a major part of the controls as an intrinsic part of the cooling units: • TS/CV is responsible for the cooling unit control (closed loop control, software on the PLC). • This will guarantee autonomous and safe operation • TS/CV provides a supervisory system for their own use (based on wizcon) during commissioning, test and maintenance. • This allows full control for cooling experts DCS Workshop

15. Cooling and Ventilation[detector cooling units] • The baseline assumptions are: • The cooling units will deliver cooling water of a pre-defined temperature (and defined stability) to the sub-detector • This temperature can be defined by the sub-detector (within given limits) • The control system of the cooling unit will take care of the regulation of this temperature • No external system (e.g. DCS) will be involved in the regulation loop DCS Workshop

16. Cooling Circuit 1 Cooling Circuit 2 Cooling and Ventilation[detector cooling units] PC TS/CV (local) supervision and operation by TS/CV (WIZCON) PLC Water at x°C ± y°C Cooling Unit Detector DCS Workshop

17. Cooling and Ventilation[detector cooling units] • DCS will be in charge of ‘day-to-day’ operation • The cooling system will operate autonomously, independent of the status of the DCS • The control will be on a relatively global level (system level), rather than on the device level • Switch on and off a cooling unit(or switch from one running mode to another) • Switch on/off a single cooling circuit within a cooling unit • Define the water temperature set-point for each cooling circuit within a cooling unit DCS Workshop

18. Cooling and Ventilation[detector cooling units] • Any information requested will be available to DCS • parameters, status, alarms • Detectors to express their requirements • Hardwired interlocks can be generated • DCS will interface directly to the PLC’s • Probably modbus TCP/IP • Arbitration mechanism to prevent confusion or worse (operation from DCS and TS/CV) DCS Workshop

19. Cooling and Ventilation[detector cooling units] • For the majority of the cooling units there will be only very limited (active) interaction with the DCS during normal operation • One could think of a restart command that launches a pre-defined start-up procedure after a power outage • During normal operation DCS will be mainly monitoring • Small and slow corrections on water temperature are possible for specific needs (e.g. TPC) • Should not disturb primary control loop DCS Workshop

20. Recalculatesetpoint TPC-specific Temperaturemonitoring T1 Cooling Circuit 1 Cooling Circuit 2 T3 T2 Cooling and Ventilation[detector cooling units] ALICE DCS, global supervision and operation (PVSSII) PC PC TS/CV ALICE LAN (local) supervision and operation by TS/CV (WIZCON) Global commands (on/off, setpoint) Monitoring (status, alarms, data) PLC Low Voltagepower supply Interlock Water at x°C ± y°C Cooling Unit Detector DCS Workshop

21. Electricity Transformer “Tableau BT” Primary electricity Is EDF / EOS racks “Hazemeyer” DCS Workshop

22. Electricity[responsibilities] • Primary electricity • Full responsibility of TS/EL • Distribution of power to the racks • Build and maintained by TS/EL, including controls • ‘Day to day’ operation by the experiment • Control of (power to) equipment inside the racks • Crates and other equipment • Responsibility of DCS DCS Workshop

23. Electricity[primary electricity] • Completely installed (refurbished), maintained and operated by TS/EL • Controlled and monitored by their own supervision system (ENS), delegated to TCR • Experiments can get information through DIP DCS Workshop

24. Electricity[distribution to racks] • Each rack (UX) or pair of racks (CR) is powered from a ‘drawer’ • Electrical protection and control • Under full control of DCS “Hazemeyer drawer” (TDM) “Hazemeyer cupboard” DCS Workshop

25. Electricity[distribution to racks] • Hazemeyer drawers are controlled and monitored from a PLC (one for CR, one for UX) • Interface to DCS through Rack Control Application • common JCOP activity (driven by CMS) • based on modbus TCP/IP • DCS can switch on/off racks, monitor state • Through rack monitor (ELMB) RCA will also monitor other parameters from rack: temperatures, turbine status … DCS Workshop

26. Electricity ALICE DCS, global supervision and operation (PVSSII) PC PC TS/EL ALICE PLC LAN supervision and operation by TS/EL (ENS) Commands (on/off) Monitoring (status, alarms, data) No commandsonly monitor! PLC Racks “Hazemeyer” DCS Workshop

27. Electricity[distribution inside the racks] • TS/EL does not foresee any control inside the rack • Lower granularity of power control on the equipment level • Use facilities of the equipment (Wiener VME) • Use special power outlets • WG is looking at powering PC racks • Make inventory of needs, monitor technology DCS Workshop

28. Magnets • L3 solenoid and dipole • Responsibility ALICE, TS/LEA and PH/TA3 • Control systems by PH/TA3 group • Similar for solenoid and dipole • PLC based control system, hardwired safety system • Own supervision system, based on PVSS • No control expected from experiment • Interaction DCS with MCS hardwired (via DSS) • If needed via software via ‘gateway’ • No direct access to PLC’s DCS Workshop

29. Magnets ALICE DCS, global supervision and operation (PVSSII) Gateway PC PC PH/TA3 ALICE LAN (local) supervisionand operation byMCR (PVSSII) Monitoring (status, alarms, data) PLC DSS PLC Interlock L3 Solenoid Dipole DCS Workshop

30. Safety • Has been covered in previous workshops • Level 3 system by TS/MA: CSAM • ‘Secure’ part of DCS: DSS • CSAM information available to DCS via DIP • DSS is integral part of DCS • A common tool to group safety relevant information DCS Workshop

31. Summary • Contacts with service groups well established • Responsibilities in interface well defined • Interface (technical) in most cases being defined now • Need your requirements (gas, cooling) DCS Workshop