FirstFirst ideas for the ideas for the ATATLAS LAS CControl ontrol RRoom designoom design

Outcome of “brainstorming sessions” in a small working group:H. Burckhart, B. Chauchaix, B. Di Girolamo, I. Efthymiopoulos, O.

Jonsson, D. Liko, L. Mapelli, G. Mornacchi, M. Nessi

Areas we discussed: mandate, functionalities, layout, organization,

technologies, software

More input after the workshop and today’s discussion …

Ilias EfthymiopoulosATLAS Plenary Meeting

February 26, 2004

10/10/2003 ie-acr 2

Few remarksFew remarks

Personal history and experience creates a strong bias to almost everybody typical starting words in many conversations:

“In (CDF, D0, OPAL, ALEPH, DELPHI, H1, UA2, …) we had … “

and most likely, any of these options could also work for ATLAS!!!

Control Room operations the CR design should reflect the way we will do operations in ATLAS

the requirements of the operation model will put constraints to the CR design

The requirements for the CR vary a lot with time from installation & commissioning phase, to steady operation

The CR should in principle evolve as the detector builds up

Note: none(?) of the LEP CRs was modified in their lifetime ; same for D0 , not for CDF

10/10/2003 ie-acr 3

… … Few remarksFew remarks The difficulty is find the right balance

between this …

certainly tempting during commissioning

And something like this …

more attractive design better suited for the long term running

of the experiment

We must also respect the space, budget and time constraints we have!

10/10/2003 ie-acr 4

ATCR - SCX1 buildingATCR - SCX1 building

3 floors ~200 m2 / floor

10/10/2003 ie-acr 5

… … SCX1 buildingSCX1 building

Important point to consider:Important point to consider:

The Globe of innovation will be located just next door!

Point-1 / ATLAS and ATCR will be a major visit point for CERN handling visitors is also an important constraint for

the design – visitors may come already from startup!

10/10/2003 ie-acr 6

Design considerations - objectivesDesign considerations - objectives

Control Room Operations

Control and operate the ATLAS detector 24h/day operation while LHC is running

interaction with CERN Control Center (CCC) LHC machine status and data/information exchange ; cooling, cryogenics, electricity, general services

supervisory operation during beam-off periods maintenance, services and safety surveillance

consider all phases of the experiment: installation, commissioning, steady running

Access control to the experiment and overall Experimental Area at IP1

Outreach aspects technologically and architecturally attractive to external visitors

remote access (browsing) and information on ATLAS/LHC experiment

10/10/2003 ie-acr 7

Overall layoutOverall layout

Offices – coffee area

Conference room – ATLAS Expo

Control Room –Visitor gallery

Open air ATLAS Expo

Additional space in nearby barracks and possibly in the 1st floor, if ATLAS Expo would be

deferred

Car parking close to the entrance and behind SCX1

10/10/2003 ie-acr 8

ATCR layout (ground floor) – one possibility…ATCR layout (ground floor) – one possibility…

Quite generous in space, more working units (at least two) can be added No geographically assigned area per sub-detector Well adopted for “central” or steady running operations

still we have to understand how to operate in the commissioning phase

Wall displays

Working unit:

• 3(7) working posts

• a keyboard and

• ≥ 1 displays

• repeated 5 times

Visitor reception

Visitor area

• Glass window to view the CR

• “copy” of a working unit ; “hands-on” experience of ATLAS operations - training Path - Connection

with the globe

10/10/2003 ie-acr 9

How to organize “operations” in ATLAS?How to organize “operations” in ATLAS?

Key elementsKey elements

Operating model for each sub-detector what is expected from the shift crew? should they intervene to fix problems

based on given instructions or just call the first-line experts?

try as much as possible to get the shift crew “involved”

How much (if at all) of the CR functions can be exported to outside labs? e.g. data quality monitoring security issues?

Formal obligations supervising the access to experiment area patrols safety shifts even during shutdown?

Gradually form an “operations team” within the collaboration

Provide continuity of responsibility authority availability of people

Organize training of newcomers training and formation of patrol teams update of documentation

Time of “service” to be defined as a member of the operations crews as a member with advanced

responsibilities based on acquired experience and training

10/10/2003 ie-acr 10

ATCR Functions – what the CR should do?ATCR Functions – what the CR should do?

GlobalGlobal Interaction with LHC machine

Observe and monitor the beam quality

Interaction with sub-detector experts organize interventions and maintenance

activities

Supervise the access control list of people in underground areas

Operate the experiment data taking using the DAQ system data quality monitoring alarms and safety status displays interaction with general services (TCR) fill the logbook (electronic) of operations

Sub-Detector dependentSub-Detector dependent Monitor status of detector HW

Handle detector DCS alarms

Allow sub-detectors to: access and operate their hardware

e.g. a particular ROD crate via RODCrate DAQ

calibrate, debug, commission a sub-detector or one of its partitions

Guidelines for ATCR designGuidelines for ATCR design Global - non sub-detector oriented

approach for steady running Space for sub-detector work in the CR but

not geographically assigned Avoid hardwired consoles and displays

possibility to do everything from any console

but fixed consoles and displays for some tasks

10/10/2003 ie-acr 11

ATCR - Hierarchy of operationsATCR - Hierarchy of operations Local access – from ATCR

shift crew and local experts – maximum freedom to access HW

define types of tasks to be performed by shift crew arrange and project important information in wall displays

Remote access to CR functions expert access to CR functions and/or export of CR functions to remote centers

upon authorization from shift leader - deliver personal and time limited(?) tokens

network security issues

Remote access to experiment status inquiry (browse) on experiment status

read-only functionality of specialized equipment

no security restrictions (?)

10/10/2003 ie-acr 12

ATCR - ManningATCR - ManningOperations Manager

monthly shift / 3 month duty

Detector & EA supervisor

weekly shift / monthly duty

Data Quality supervisor

weekly duty

shift leader

8h shift / monthly duty

shift crew (≥2)

8h shift / monthly duty

shift leader

8h duty

shift crew

8h duty

Sub-detector supervisors

Experts on call (first line)

Data analysis teams

Software experts

ATCR Briefings (daily)

• report from sub-detector supervisors

• report from LHC liaison

• invited experts

• remote participation

sub-detector shift

•Time spans for duty are only indicative

•Exact number of shift crews to be defined

10/10/2003 ie-acr 13

Con

trol R

oom

ATCR Software architecture and TechnologiesATCR Software architecture and Technologies Physical Components

consoles

wall screens

ACR Architecture - software connection to ATLAS (“services”)

via a control network CR is cable-less

except whatever has to be hardwired for safety

CR is remote to experiment - can be done from anywhere:

SXC1, USA15, barracks, office,

generic consoles hierarchy of consoles in CR(?)

console gateway for remote access configurations

Control networkControl networkgateway

External access

console console consoleconsole

“Virtual”

“Remote”

Control Room

10/10/2003 ie-acr 14

SummarySummary

CERN Library: “Typical control room of an electronic experiment” – Nov. 1964