How could the CMS control room be improved? Greg Rakness University of California, Los Angeles

Collecting raw data 20 June 2013: brainstorming session – 23 people invited, 12 attended – “Raw data” summarized here: Discussion items ranged far and wide, and can be grouped into four loosely-coupled topics… – Layout – Workstations (planned to be replaced in 2014 in any case) – Laptops – Environment This is a summary of the problems, focusing on the layout, and an attempt to address most of them 16 July 2013G. Rakness (UCLA)2

Layout: problems 1.Central shifter communication impeded a.Location of DCS shifter is detached from central crew b.Location of Shift Leader not “central” c.Meeting area presently in “central” area d.Back-to-back layout forces crew to turn away from screens to see each other 2.Visitor groups can impede CMS operations a.Plug hallway at entrance b.Pass through center of control room 3.Overview of CMS running state not easy to obtain a.Rationale of present summary screens is not clear b.Have to look at several screens located in different places 4.Subsystem rooms are rarely used, particularly during running 5.2 nd floor coffee/relaxation area is not used effectively, if at all 16 July 2013G. Rakness (UCLA)3

Couplings and constraints The layout… – Depends on the footprint of each workstation – Should be consistent with environment solutions The workstations… – Should include laptops – Need wants/needs of subsystems and central shifts – Should have limited options Minimal changes to infrastructure – In discussions w/Austin Ball, as he will be paying for it 16 July 2013G. Rakness (UCLA)4

2012 layout 16 July 2013G. Rakness (UCLA)5

16 July 2013G. Rakness (UCLA) layout

16 July 2013G. Rakness (UCLA) layout Problem 1a: DCS shifter is detached from central crew

16 July 2013G. Rakness (UCLA) layout Problem 1b+1c: Meeting area is central, not shift leader

16 July 2013G. Rakness (UCLA) layout Problem 2: Visitors pass through center of room

16 July 2013G. Rakness (UCLA) layout Problem 3: CMS running state on multiple walls

Can we fix it? Getting close… Next slide is after several iterations with multiple people 16 July 2013G. Rakness (UCLA)11

Proposal v July 2013G. Rakness (UCLA)12

Proposal v2.1 bird’s-eye view 16 July 2013G. Rakness (UCLA)13

Coffee area 16 July 2013G. Rakness (UCLA) Proposed 2015

Still to follow up… Workstations: ping subsystems and central – Common workstation type would add flexibility Safety: need sign-off from Christoph Schaefer – Better to know constraints early rather than late Iterate with smaller crew Bring to XEB 16 July 2013G. Rakness (UCLA)15

Backups 16 July 2013G. Rakness (UCLA)16

Workstations: problems Too many screens (~140) – Feeling that we must not be using screen-space effectively – Where does one look for the essential information? Hard for sys-admins to maintain – Each workstation has a unique configuration – Desktops hard to access Not ergonomic – Which mouse goes with which screen? – Hard for those with bifocals to look at upper screens – Not clear what function goes with each workstation 16 July 2013G. Rakness (UCLA)17

Laptops: problems Can block view of workstation screens Electrical outlets – In same place as desktop plugs – Difficult to access – Not enough, as they are used by everybody 16 July 2013G. Rakness (UCLA)18

Environment: problems Messy – Champagne bottles make it look like a dorm room – Food is often left on the central table – Printer area always cluttered Temperature not regulated well – Too hot sometimes and too cold other times – Sensitive to the double doors being open or not Very dry (low humidity) in winter White noise from speaker system bothersome Not much natural light 16 July 2013G. Rakness (UCLA)19

2012 bird’s-eye view 16 July 2013G. Rakness (UCLA)20

16 July 2013G. Rakness (UCLA)21 Proposal v1.0

Proposal v1.0 bird’s-eye view 16 July 2013G. Rakness (UCLA)22

16 July 2013G. Rakness (UCLA)23 Proposal v2.0

Proposal v2.0 bird’s-eye view 16 July 2013G. Rakness (UCLA)24