1. DCS for LHC IF
Peter Chochula
28 june 2019

2. Outline LHC IF in the context of the DCS DCS LHC (IF) interactions
Handshake
Permits Controls
Data exchange

3. LHC IF in the DCS context
LHC IF is hosted on the DCS
Shares the DCS infrastructure and technologies (WINCC OA)
LHC IF is installed as a dedicated distributed system
Strong dependency on DCS data flow
Treated as a detector project
Integrates various parts :
BPTX
Lumi & Background
Handshake
BCM

4. DCS handshake Under the responsibility of the DCS team Clear evolution
From nightmare in 2009
Through excellent stability since the second half of RUN1
To fully automated operation in 2017
And then to some instabilities towards the end of RUN2
Several false injection handshake triggers that we received received scared the shift crews
Source not yet understood

5. Bulletproof procedure
The handshake procedure is well understood (if no improvements will be introduced)

6. HS procedure simplification
Present procedure HS
PREPARE
INFORM
GO SAFE
CONFIRM
WAIT
OVER
Goal (hide protocol details from operator) HS
NEXT
OVER

7. Granting of permits (recovery after anomaly)
Recovery procedure clear
Performed by the DCS operator
… well, or maybe the Shift Leader?...
Need to clarify the procedures

8. DCS Data exchange DCS acts as a gateway between ALICE and LHC
Transmission of LHC data and signals (handshake, post mortem…) to ALICE
Redistribution of LHC information in ALICE
Transmission of ALICE feedback to LHC
DCS operates on isolated network
Setup of services requires precise information and planning

9. DCS Data Flow - RUN 2 LHC Teleport OFFLINE AMANDA (via shuttle) ORACLE
DARMA
Web GUI
DataBase Manager
DIM, DIP
LHC, DAQ…
Data Manager
Event Manager
User Interface
User Logic
Driver
Device

10. DCS Data Flow – RUN 3 LHC Teleport OFFLINE AMANDA (via shuttle) ORACLE
DARMA
Web GUI
DataBase Manager
DIM, DIP
LHC, DAQ…
Data Manager
Event Manager
User Interface
User Logic
Driver
Device

11. DCS Data Flow – RUN 3 Delayed processing “Real-time” processing NEW!
ORACLE
DARMA
Web GUI
DataBase Manager
DIM, DIP
LHC, DAQ…
Data Manager
Delayed processing
“Real-time” processing
NEW!
Event Manager
ADAPOS Publisher
ADAPOS ENGINE
ADAPOS TERMINAL
ADAPOS O2 Client
User Interface
User Logic
Driver
Device

12. Getting data out of the WINCCOA, novel approach WINCC OA 3
Getting data out of the WINCCOA, novel approach WINCC OA 3.16 and NextGen Archiver (NGA)
ADAPOS Publisher
NextGen
Event Manager
ADAPOS ENGINE
ADAPOS TERMINAL
ADAPOS O2 Client
User Interface
User Logic
Driver
New (not yet released) WINCC OA extension offers possibility to use the Next Gen Archiver
Prototype delivered to ALICE in 2018
Impressive efforts put by BE-ICS into NGA development
V 1.0 relerased
ALICE works closely with BE-ICS to validate NGA
Device
NEXT
GEN
ADAPOS 0MQ
Backend
ADAPOS DIM
Backend
ORACLE
Backend
INFLUX DB
Backend

13. Some remarks on DCS data
DCS is built to
Process commands, statuses and to control devices
DCS is not built to
Process large volumes of fast changing data
Technical limitations of WINCC OA and its storage do not allow for continuous processing of fast changing counters etc.
Any requirements shall be discussed with the DCS team before new developments are launched

14. TODO and open questions
Simplification of the Handshake procedure
Need information about foreseen changes in the protocol
Clarification on internal ALICE procedures (permits control, BCM, Post Mortem…)
Details on new requirements:
What data goes to O2
AMANDA, FXS and related teleport will not exist anymore
Archival
Bunch by bunch creates anomalies, but no one is using it
Any hardware changes? (what about TELL1?)
What happens to (Massi) teleport?