+ All Categories
Home > Documents > 1 ALICE Detector Control System (DCS) TDR 28 January 2004 L.Jirdén On behalf of ALICE Controls...

1 ALICE Detector Control System (DCS) TDR 28 January 2004 L.Jirdén On behalf of ALICE Controls...

Date post: 18-Dec-2015
Category:
View: 216 times
Download: 0 times
Share this document with a friend
Popular Tags:
19
1 ALICE Detector Control ALICE Detector Control System (DCS) TDR System (DCS) TDR 28 January 2004 L.Jirdén On behalf of ALICE Controls Coordination (ACC): A.Augustinus, P.Chochula, G. De Cataldo, S.Popescu, R.Vand Der Vlugt and the ALICE Collaboration
Transcript

1

ALICE Detector Control ALICE Detector Control System (DCS) TDRSystem (DCS) TDR

28 January 2004L.Jirdén

On behalf of ALICE Controls Coordination (ACC):

A.Augustinus, P.Chochula, G. De Cataldo, S.Popescu, R.Vand Der Vlugt

and the ALICE Collaboration

2

OutlineOutline

Context Architecture System implementation Schedule & milestones, status

today Responsibilities, cost

3

Controls ContextControls Context

DCS

ITS

hv hv hvhv

hv

lvlv lvlv

lvpT Tpixel driftstrip

TPC MUON

Detectors

Servicespower

cooling

gas

magnets

infrastructure

safety

access

ExternalSystems ECS

LHC

DAQ

Trigger

HLT

Ctrl

Ctrl

Ctrl

4

Hardware architectureHardware architecture

Sup

erv

isor

y layer

Sensors, devices

Field-buses, nodes

PC-PCI/W-Linux, PLC, VME, etc.

Communication(OPC, DIM)

SCADA (PVSS)

Technologies

Framework

Layers Structure

User applications

Pro

cess

co

ntr

ol

layer

Field

la

yer

Supervisory consoles

Experimental equipment

DCS LAN

WAN

Oth

er

syste

ms:

TR

G,

DA

Q,

etc

.

Configuration DB,Archives, Log, etc.

PLCVME

Field-bus

DCS LAN

Node Node

Storage

5

Software architecture Software architecture (1)(1)

sub-sys 1

device a

Control Units

DeviceUnits

To physical devices

sub-det B

detector

sub-det A

sub-sys 2

device b

gas

DCS

ECS

power

sub-det Esub-det D

racks

sub-sys 1 sub-sys 2

device e…

6

Software architecture Software architecture (2)(2)

PVSS

CU Behaviour(FSM)

configurationarchiving

PartitioningAlarmhandling

access, ownership

dB

operator

parent

child child

commands

states

commands

states

PVSS

FSMinterface

configurationarchiving

Alarmsdevicedriver

access, ownership

dB

operator

parent

settingsreading

s device

Partitioning

OFF

ERROR

ON

STANDBY

GO_STANDBY

GO_READY

GO_STANDBY

RESET

Alarm

GO_OFFCONFIG

RAMP_UP RAMP_DW

7

Back-end and front-Back-end and front-end componentsend components

Field-bus

Front-end application

DEVICE DRIVERS

DEV 1 DEV 2

COMMUNIC

DCS Front-end

DBaccess

ALARM

PVSS CONFIGARCHIV

WEB

ARCHIV

COMMUNIC

FSM

DCS Back-end

DCS network

CONDIT

PVSSCONFIG

FEE CONFIG

User application

Process layer

Field layer

Supervisory layer

8

Distributed PVSS Distributed PVSS systemsystem

UIM

Ctrl API

EVMDBMDB

UIM UIM

DCS

Dist

Dist Dist

Dist……

UIM

Ctrl API

EVMDBM

D DD

DB

UIM UIM

… SSD

UIM

Ctrl API

EVMDBM

D DD

DB

UIM UIM

TPC

UIM

Ctrl API

EVMDBM

D DD

DB

UIM UIM

…TRD

operator

DEVICE

9

DCS

Su

b-

dete

cto

rs

FC

TOF

SPD SDD SSD

TPC TRD ZDC PMDHMP

RO

ITS PHO

CPVCAL

FMD V0T0

TRATRI

MU COSEMC

Common solutions

HV

LV

FEE

GAS

MON

COOSu

b-s

yste

ms

LSR

HV

LV

FEE

GAS

MON

TS

HV

LV

FEE

HV

LV

FEE

GAS

MON

HV

LV

FEE

GAS

MON

HV

LV

FEE

MON

HV

LV

FEE

MON MON

ROD

VHV

HV

LV

GAS

MON

HV

LV

FEE

TMP

HV

LV

MON

HV

LV

FEE

MON

HV

LV

GAS

MON

HV

LV

FEE

HV

LV

GAS

MON

HV

LV

FEE

HV

LV

FEE

HV

LV

FEE

LIQ

GAS

HV

LV

GAS

MON

ALITS

COOCOO COO COOCOO COO COO COO COO COO COO COO

MON MON MON MONMON

PLS

ALI

~10 Common

~10 Specific

10

PVSS

CU Behaviour(FSM)

configurationarchiving

PartitioningAlarmhandling

access, ownership

dB

operator

PVSS

FSMinterface

configurationarchiving

Alarmsdevicedriver

access, ownership

dB

operator

device

Partitioning

Agreed set of standard devicesStandard interfaces – OPC, DIM

Common tools

OFF

ERROR

ON

STANDBY

GO_STANDBY

GO_READY

GO_STANDBY

RESET

Alarm

GO_OFFCONFIG

RAMP_UP RAMP_DW

Standard FSM’s

What is a common solution?What is a common solution?

11

HV & LV Common solution

Console PC

Server PC

Powersupply 1

Detector equipment

CANbus or ethernet

DCS LAN

firmware

Powersupply n

firmware

Powersupply 2

firmware…

PS OPC-server

PVSS OPC-client

OPC standard

PS proprietary

Supervisory application using FSM and PVSS

12

SPD HV control panels

13

Common solution for Common solution for FEE FEE

ALICE CONTROL ROOMPVSS

console

Common interface?Common interface?

many different FEE architectures

ON DETECTOR

VME

SPD FEE

JTAG

HMPID FEE

DDL

TPC FEE

ETHERNET

TRD FEE

ETHERNET

MXI …

Front End Device (FED)

DIM server

interfaces

FEE H/W

MXIDDLETHERNETEtc.

FEE specific

FEE commo

n

DIM client

14

ALICE CONTROL ROOM

ON DETECTOR

CAVERN

COUNTING ROOMS

DevicesSensors

DevicesSensors

DevicesSensors

Services:

PLC

process control applications

Fieldbus or direct I/O

DCS LAN

supervisory applications

Power & racksCoolingGasMagnetsSafety (DSS)

15

Oxygendeficiency

Dead-mandevice

Fire brigadeto point 2

Secure the zone

CERN Safety AlarmMonitoring (CSAM)

Flooding

Evacuationalarm

Gasdetection

Emergencycall

Blockedlift

Emergencystop

Fire/smoke

Level 3alarms

Safe

ty a

ctio

ns

Cut equipmentgracefully

Cut a singlerack

DCS

Infrastructure

Front-endelectronics

Cooling &gas

TempPower

supplies

Experimentequipment

DC

S a

ctio

ns

Safety systemsCut group of

racks

Interlock spec.equipment

Detectorstatus

Waterleak

Powerstatus

TempCoolingwater

Experimentenvironment

DSS a

larm

act

ions

DSSRedundant

PLC’s

DSS system

I/O units

Hardwired interlock

16

Pre-installation on surface

Final installation in UX

Commissioning

Schedule & Schedule & MilestonesMilestones2004 20052003 20072006

HW infrastructureBack-end + servicesDetector sub-systemsIntegration with DAQ/TRG/HLT

M1M2

HW infrastructureBack-end + servicesDetector sub-systemsIntegration with DAQ/TRG/HLT

M3 M4

Individual detectorsGroups of detectorsWhole experiment

M5 M6 M7 M8

17

Status today (1)Status today (1)

Back-end system All main components are available in prototype

form An ALICE back-end system is being prototyped

Detector applications Requirements defined to ~70% (URD’s) Prototypes;

~ 10% 1st version implemented ~ 70% started ~ 20% not started or unknown

18

Status today (2)Status today (2) Services applications

Power & rack control: prototyping started Cooling control: prototyping started Gas control: TPC prototype ready Magnet control: 1st prototype installed Safety: 1st prototype being installed Infrastructure: requirements being defined

Interface to external systems Interface to 1st implementation

TRG/DAQ/HLT: via ECS tested

19

RESPONSIBILITIESOverall coordination CERN Alice Controls Coordination

(ACC)

Basic software tools CERN JCOP project (IT, EP departments)

Back-end system CERN Alice Controls Coordination (ACC)

Services CERN ST, EP, IT departments

Detectors Detector groupsCOST

DCS infrastructure 514 kCHF

Services Magnets 664 kCHF

Power, cooling, gas 660 kCHF

Safety, site infrastructure 240 kCHF

Total 2078 kCHF


Recommended