André Augustinus 22 June 2004 DCS Workshop Status on services controls.

DCS Workshop

André Augustinus22 June 2004

Status on services controls

22 June 2004DCS Workshop 2André Augustinus

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


Gas systems

Detector

Detector gas systems

Primary gas


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


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


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)



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



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



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


Gas systems

PLC

PC

Gas System

(local) supervisionand operation byGWG (PVSSII)

Detector

ALICE DCS, global supervision and operation (PVSSII)

High Voltagepower supply

Global commands (restart)Monitoring (status, alarms, data)

Gateway PC

LAN

Interlock

GWG ALICE


Cooling and Ventilation

Detector

Detector cooling

Primary Cooling

VentilationAir conditioning


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


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)


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



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



PLC

PC

Cooling Unit

(local) supervision andoperation by TS/CV(WIZCON)

Cooling Circuit 1

Cooling Circuit 2

Water at x°C ± y°C

TS/CV

Detector



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



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)



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



PLC

PC

Cooling Unit

(local) supervision and operation by TS/CV (WIZCON)

Cooling Circuit 1

Cooling Circuit 2

Water at x°C ± y°C

TS/CV ALICEPC


LAN

Low Voltagepower supplyInterlock

Global commands (on/off, setpoint)Monitoring (status, alarms, data)

Detector

Temperaturemonitoring

T1

T2

T3

Recalculatesetpoint

TPC-specific


Electricity

“Hazemeyer”

Transformer

Is

racks

“Tableau BT”

Prim

ary e

lectricity

EDF / EOS


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


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


Electricity[distribution to racks]

“Hazemeyercupboard”

“Hazemeyerdrawer” (TDM)

Each rack (UX) or pair of racks (CR) is powered from a ‘drawer’

Electrical protection and control

Under full control of DCS


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 …


Electricity

PLC

PC

“Hazemeyer”

supervision and operation by TS/EL (ENS)

TS/EL ALICEPC


LAN

Commands (on/off)Monitoring (status, alarms, data)

Racks

PLC

No commandsonly monitor!


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


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


Magnets

PLC

PC

L3 Solenoid

(local) supervisionand operation byMCR (PVSSII)

Dipole


DSS

Monitoring (status, alarms, data)

Gateway PC

LAN

Interlock

PH/TA3 ALICE

PLC


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


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)

André Augustinus 22 June 2004 DCS Workshop Status on services controls.

Documents

Transcript of André Augustinus 22 June 2004 DCS Workshop Status on services controls.