1. the experiment cms 2. architecture, what is dcs in cms? 3. joint controls project

1. The Experiment CMS

2. Architecture, what is DCS in CMS?

3. Joint controls project

4. SCADA system (supervisory controls and data acquisition)

5. Framework

6. Partioning

7. Further tools to build a control system

8. Applications

9. Milestones and future

The Detector Control System of the Experiment CMS at CERN

MENU:

Wolfgang Funk -CERN CMS09/2001 1

CMS detector


Wolfgang Funk -CERN CMS09/20015

Wolfgang Funk -CERN CMS09/20017

DCS environment:

DCS

CMS Security System

CMS Magnet

LHC

Infrastructure: cooling ventilation electricity

sensors

CMS

Level 3 safety CMS

TCR,pompiers


DB

Architecture of the CMS control system (functional block diagram):

Run CTRL

ext.communication(LHC,infrastructure,magnet,

safety,…)

LAN (ethernet)

FE electronics

Calibration events(T, rad. source, …)

Downloading and

reading of constants

and programs

DAQ

Selection of runtype

resource manager (selection of needed resources)

Communi

cation with

sub

detector controllers

Standard

slow

control

SCADA System

Supervision

of

subdetector controllers

Classsical

slow

control

Supervisory System

Subdetector 2 controller

Subdetector 1controllerD

B

Wolfgang Funk -CERN CMS

fieldbus devices, PLCs, VME,

HV+LV power supplies

fieldbus (CAN, Profibus, ..)

(OPC, others)

Device Server

Devices

Sensors,Actuators

09/2001 9

JCOP (Joint Controls Project):

1.) Use commercial hard- and software components where possible to economise manpower for development and maintenance as industry is doing it everywhere


Some years ago the 4 LHC experiments decided to try to do as much as possible in common for building their respective DCS system

Basic ideas:

2.) use one unique system for all controls within each experiment, which implies that system is


Basic ideas (cont.):

• scalable • hierachical• partionable (easily integratable)• modular• open to outside (extensible)

Functions of a SCADA system:

• HMI• Logging and archiving• Handles distribution and redundancy• Report generation• Automation (scripting, recipes, ..), FSM added• Access control• Alarms• Trending• …


After intensive evaluation, the four LHC experiments selected PVSSII, market is rapidly evolving

(Supervisory controls and data acquisition)

PVSSII (1):

• Device oriented (structure of data, graphical representation)• All data + configuration is stored in “objects”, which are

accessible through scripts, template panels and API, therefore complete control from outside possible

• Mix and match of operation systems (NT, Linux, HPUX)• Complex devices built up out of several “objects”• Event driven• Network access (with special software installed)• Actions e.g. when value above threshold (call back feature)• We have connected a FSM to product• “C” is scripting language (next version VB, Java-scripting)


PVSSII (2):

• System of systems (distributed, hierarchical, partitioned), therefore no limits of number of procs to build up system

• All panels are ASCII files (can generate them algorithmically)• Alarm grouping• Changes can be done online (scripting language is

interpreted)• Timestamps


08/09/1999 Wolfgang Funk - CERN CMS 15

Basic architecture of PVSSII:Basic architecture of PVSSII:

User Interface LayerUser Interface Layer

Processing LayerProcessing Layer

Driver LayerDriver Layer

CtrlCtrl APIAPI

EVEV

DD DDDD

UIMUIM UIMUIM UIMUIM

DMDM Communication and Communication and Memory LayerMemory Layer

Scripts

09/2001 Wolfgang Funk -CERN CMS

What are the Benefits of SCADA?• Standard framework « homogeneous system (with engineering)

• Support for large distributed systems (networking + redundancy)

• Follow evolution of market

• Buffering against technology changes, Operating Systems, platforms, etc.

• Saving of Development Effort (50-100 man-years)

• Stability and maturity

• Experience of companies built into products

• Support and maintenance, including documentation and training

• Reduction of work for the sub-detector teams


What are Engineering Tasks?• Templates, symbols libraries, e.g. power supply,

rack, etc.• Guidelines on use of colours, fonts, page layout,

naming, ... • Guidelines on partitioning• Guidelines for alarm priority levels, access

control levels, etc.• Model standard device behaviour• Definition of system architecture (distribution of

functionality)• Development of configuration tools

17Wolfgang Funk -CERN CMS09/2001

Framework:

All templates, standard elements and functions in order to build a homogeneous supervision system.


Finally:

• Finite state machine (SMI)• DIM interface• CAEN PS (127,527,1527) interface• Generic analog and digital channels• Hierarchy• External alarm handling• ELMB Interface to PVSSII• Configuration utilities for all above

1.Version:

1

1.2

1.1.2 1.2.11.1.1

1.1 1.3

1.2.2 1.3.1 1.3.2

1

1.2

1.1.2 1.2.11.1.1

1.1 1.3

1.2.2 1.3.1 1.3.2

09/2001 Wolfgang Funk - CMS 19

RootOperator

RootOperator

Operator A

Operator B

Partioning

Runctrl

DCS general


Partioning with DAQ

DCS HCAL DCS ECAL...

DAQ generalRctrl ECAL

... DAQ ECAL DAQ HCAL

Resource manager

Resource manager distributes available resources and allows possible partioning

Trigger as DAQ, DCS has to run 365 days/year (has to work as well independently)

OPC


Set of DCOM interfaces to connect applications (EXEL, SCADA,..) with devices

OLE for Process Control

Client/server:

Tag oriented

Well supported by industry Server (standalone, SCADA,…)Client (office application, SCADA, batch system,…)Toolkit

client client

server serverFrom devices

DIM-Distributed Information Management system


Communication System - main features:Services

Sets of data (any type or size), identified by a namePublish/Subscribe Mechanism

Servers publish Services.Clients subscribe to Services (and send Commands)Services can be received at regular intervals or on change

TransparencyName serviceClient Server connections are automatically (re)establishedClients do not need to know where their servers areClients and Servers can move from one machine to another.

Available on multiple (mixed) environments:Unix , Linux, Windows NT, VMS, some Real-time OssDIM client/server available in “C”, C++ and Delphi (Kylix)

Interface between custom s/w and PVSS


-DIM is supported and will not change, when new PVSSII versions arrive, customs s/w would not be affected (buffer!)

PVSSII

Cu

sto

m s

/w-work naturally separated, debugging of both sides independently possible

PVSSII API

DIMDIMH/W

simulator debugger

Fieldbuses


CERN recommends and supports 3 fieldbuses:

CAN-bus with the protocol CANOPEN (simple, flexible)

Profibus with the protocol Profibus DP (a lot of actuators available)

Worldfip (deterministic, mostly for accelerators, big data rate)

PLCs


• Front end computer• Reliable, used in industry• Specific standardised program languages• Used in distributed control• Communication PLC - device: fieldbus

PLC - PLC: fieldbus, ethernetPLC - SCADA: fieldbus, ethernet

CERN recommends to use PLCs from 2 companies (Siemens, Schneider), CERN support

Sensors and actuators

We try to standardize sensors and actuators in the field of:

• T-measurement• Humidity sensors• Valves, gas mixers etc.• Radiation measurements• Strain gauges• ...

They have to work in difficult environment: radiation, magnet field


OPC Server configuration and connection to HV P.S.

OPC Server

NT with A303 (High Speed CAENET Controller)

SY527 SY127

System0 System1

CAENET

Cr#n Cr#m

SY1527

System2

SY1527

System3

SY1527

System4

IP#a

IP#b

RS232

TCP/IP

System0 CAENET Crate #n

System4 TCP/IP

System1

System2

System3

CAENET

RS232

TCP/IP

Crate #m

COM1

IP #a

IP #b

HV P.S. Path Param.


HCAL HV system control


to HV crates

Gas-control


SCADAwith OPC client

OPC server

ethernet

PLC PLC PLC PLC

Profibus

Valves, etc. represents a system moduleas mixer, distributor, purifier

Gas working group at CERN will do all including hardware and controls

Cooling-control


SCADAwith OPC client

OPC server

ethernet

PLC PLC PLC PLC

sensors, actuators.

I/O I/OI/OI/O

Cooling and ventilation working group at CERN will do all regulation and controls (hardware and software)

Rack-control


PC

Control unit with power distribution box, fieldbus node, ADC, safety, local control, relais, etc.

racks

Thumiditycontact

Fieldbus, ethernet

Integration of Alignment in DCS


-API manager provides integration of alarming, trending, access control, filtering of unchanged data, etc., connection to main system

~10000 coordinates (datapoints)

Interface to PVSS (API manager)

to laser from sensors

DAQ and analysis

PVSSII

PC (Linux, NT)

Internal database

HTML server PCCo

nd

ition

s da

taba

se

of C

MS

-Master data set of alignment data inside PVSSII, PVSSII transfers regularly all data needed for reconstruction into external conditions database

DIM

TRACKER FE configuration

SCADAcontrols/GUI

Database

parameters

download request

brow

sin

g

user/process ra

ises

ala

rm

read back values

FEsupervis

or

API


FE electronics configuration (2)


User

DB

SCADA

1

2

34 Write a new version

Register the new version

(with a description for logbook)

Revok

e writ

e per

miss

ion

for t

he ver

sion

Log

Access to a registered version

HCAL source control system


Thermal Screen Control TRACKER:


Milestones and future for DCS

2006 integration, full system ready (3/06)2004 engineering, individual subdetectors build up their . subdetector DCS, GIF and later H2 should be used to 2001 test DCS in real environment, ready to use in UXC (7/04) and in USC (10/04)

}


• Most of the subdetector groups have started to use PVSSII for testing the pieces of the detectors, where procedures will be reused in the final experiment.

• Test beams are essential for development of DCS and provide rigorous testing ground in order to demonstrate that the concept works.

• Almost everything has to be ready when detectors are put together on surface

Milestones and future for DCS (2)

• All what is needed for DCS by more than 1 LHC experiment should be developed and maintained in common within a CERN activity.

• Architecture is fully modular, development of control of all devices can be done individually and finally put together to a big system (development of individual vertical slices).

• Structure of DCS system will be completely scalable, therefore, if control of 1 device of certain kind works, control of n devices works.


1. the experiment cms 2. architecture, what is dcs in cms? 3. joint controls project

Documents

unique system

evolvingsupervisory

javascripting pvssii

joint controls project4

data acquisition5

complete control

control system8

online scripting language