1. 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/20011

2. CMS detector Wolfgang Funk -CERN CMS09/20012

3. Wolfgang Funk -CERN CMS09/2001 3

4. Wolfgang Funk -CERN CMS09/20014

5. Wolfgang Funk -CERN CMS09/2001 5

6. Wolfgang Funk -CERN CMS09/2001 6

7. Wolfgang Funk -CERN CMS09/2001 7

8. DCS environment: DCS CMS Security System CMS Magnet LHC Infrastructure: cooling ventilation electricity sensors CMS Level 3 safety CMS TCR, pompiers Wolfgang Funk -CERN CMS 09/20018

9. 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 1 controller DB 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

10. 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 Wolfgang Funk -CERN CMS 09/200110 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:

11. 2.) use one unique system for all controls within each experiment, which implies that system is Wolfgang Funk -CERN CMS 09/200111 Basic ideas (cont.): scalable hierachical partionable (easily integratable) modular open to outside (extensible)

12. Functions of a SCADA system: HMI Logging and archiving Handles distribution and redundancy Report generation Automation (scripting, recipes,..), FSM added Access control Alarms Trending … Wolfgang Funk -CERN CMS 09/200112 After intensive evaluation, the four LHC experiments selected PVSSII, market is rapidly evolving (Supervisory controls and data acquisition)

13. 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) Wolfgang Funk -CERN CMS 09/200113

14. 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 Wolfgang Funk -CERN CMS 09/200114

15. 15 Basic architecture of PVSSII: User Interface Layer Processing Layer Driver Layer Ctrl API EV D D D UIMUIMUIM DM Communication and Memory Layer Scripts 09/2001Wolfgang Funk -CERN CMS

16. 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 Wolfgang Funk -CERN CMS 09/200116

17. 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 17 Wolfgang Funk -CERN CMS09/2001

18. Framework: All templates, standard elements and functions in order to build a homogeneous supervision system. Wolfgang Funk -CERN CMS 9/200118 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:

19. 1 1.2 1.1.2 1.2.1 1.1.1 1.1 1.3 1.2.21.3.11.3.2 1 1.2 1.1.2 1.2.1 1.1.1 1.1 1.3 1.2.21.3.11.3.2 09/2001Wolfgang Funk - CMS19 RootOperator Operator AOperator B Partioning

20. Runctrl DCS general 09/2001Wolfgang Funk - CMS20 Partioning with DAQ DCS HCALDCS ECAL... DAQ general Rctrl ECAL... DAQ ECALDAQ 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)

21. OPC 09/2001Wolfgang Funk - CMS21 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 server From devices

22. DIM- Distributed Information Management system 09/2001Wolfgang Funk - CMS22 Communication System - main features: Services Sets of data (any type or size), identified by a name Publish/Subscribe Mechanism Servers publish Services. Clients subscribe to Services (and send Commands) Services can be received at regular intervals or on change Transparency Name service Client Server connections are automatically (re)established Clients do not need to know where their servers are Clients and Servers can move from one machine to another. Available on multiple (mixed) environments: Unix, Linux, Windows NT, VMS, some Real-time Oss DIM client/server available in “C”, C++ and Delphi (Kylix)

23. Interface between custom s/w and PVSS 09/2001Wolfgang Funk - CMS23 -DIM is supported and will not change, when new PVSSII versions arrive, customs s/w would not be affected (buffer!) PVSSII Custom s/w -work naturally separated, debugging of both sides independently possible PVSSII API DIM H/W simulatordebugger

24. Fieldbuses 09/2001Wolfgang Funk - CMS24 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)

25. PLCs 09/2001Wolfgang Funk - CMS25 Front end computer Reliable, used in industry Specific standardised program languages Used in distributed control Communication PLC - device: fieldbus PLC - PLC: fieldbus, ethernet PLC - SCADA: fieldbus, ethernet CERN recommends to use PLCs from 2 companies (Siemens, Schneider), CERN support

26. 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 09/2001Wolfgang Funk - CMS26

27. 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 CAENETCrate #n System4 TCP/IP System1 System2 System3 CAENET RS232 TCP/IP Crate #m COM1 IP #a IP #b HV P.S. PathParam. 09/2001Wolfgang Funk - CMS27

28. HCAL HV system control 28 Wolfgang Funk -CERN CMS 09/2001 to HV crates

29. Gas-control 09/2001Wolfgang Funk - CMS29 SCADA with OPC client OPC server ethernet PLC Profibus Valves, etc. represents a system module as mixer, distributor, purifier Gas working group at CERN will do all including hardware and controls

30. Cooling-control 09/2001Wolfgang Funk - CMS30 SCADA with OPC client OPC server ethernet PLC sensors, actuators. I/O Cooling and ventilation working group at CERN will do all regulation and controls (hardware and software)

31. Rack-control 09/2001Wolfgang Funk - CMS31 PC Control unit with power distribution box, fieldbus node, ADC, safety, local control, relais, etc. racks T humidity contact Fieldbus, ethernet

32. Integration of Alignment in DCS 09/2001Wolfgang Funk - CMS32 -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 laserfrom sensors DAQ and analysis PVSSII PC (Linux, NT) Internal database HTML server PC Conditions database of CMS -Master data set of alignment data inside PVSSII, PVSSII transfers regularly all data needed for reconstruction into external conditions database DIM

33. TRACKER FE configuration SCADA controls/GUI Database parameters download request browsing user/ process raises alarm read back values FE supervisor API 33 Wolfgang Funk -CERN CMS 09/2001

34. FE electronics configuration (2) 09/2001Wolfgang Funk - CMS34

35. HCAL source control system 35 Wolfgang Funk -CERN CMS 09/2001

36. Thermal Screen Control TRACKER: Wolfgang Funk -CERN CMS 9/200136

37. 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) } Wolfgang Funk -CERN CMS 09/200137 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

38. 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. Wolfgang Funk -CERN CMS 9/200138