1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  1. Plans for the US-CMS
  2. Remote Operations Center
  3. LHC@FNAL
  4. Erik Gottschalk
  5. Fermilab
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  6. Overview
  7. Overview
  8. Remote operations for CMS & LHC
  9. What is LHC@FNAL?
  10. Planning
  11. Status
  12. Needs
  13. Summary
  14. LHC@FNAL website:
  15. http:
  16. //cd-amr
  17. gov/remop/remop
  18. .html
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  19. support both CMS and
  20. Goals for 
  21. Joint CMS & LHC Remote Operations
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  22. Remote Operations for US-CMS
  23. Remote Operations for US-CMS
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  24. Remote operations for LHC
  25. Remote operations for LHC
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  26. What is LHC@FNAL?
  27. What is LHC@FNAL?
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  28. LHC@FNAL Location & Layout
  29.  
  30. Operations
  31. Center
  32. (Phase 1)
  33. Office Space
  34. (Phase 2)
  35. Conference
  36. (Phase 1)
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  37. LHC@FNAL Construction
  38. LHC@FNAL Construction  
  39. Status
  40. Status
  41. Construction is almost complete (photo taken Nov. 30, 2006).
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  42. Planning for LHC@FNAL
  43. Planning for LHC@FNAL
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  44. Current Status of LHC@FNAL
  45. Current Status of LHC@FNAL
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  46. An approach to restrict system access to authorized users
  47. What is a
  48. What is being 
  49. What type of 
  50. Requirements have been written
  51. Status:  
  52. Code development in progress
  53. This is a
  54. CERN/Fermilab
  55. collaboration working on RBA for the LHC control system.
  56. Role Based Access (RBA)
  57.  
  58. The software infrastructure for RBA is
  59. crucial for
  60. remote operations. Permissions can be setup to
  61. allow experts outside the control room to
  62. read or
  63. monitor a device safely
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  64. An approach to provide a snapshot of a graphical interface to remote users.
  65. What is a snapshot?
  66. What is the role of the service
  67. How will this work?
  68. Status:
  69. SSS is being developed at
  70. Fermilab
  71. for CMS, and 
  72. may be applicable to the LHC.
  73. Screen Snapshot Service (SSS)
  74. Screen Snapshot Service (SSS)
      1. snapshots
      2. snapshots
      3. requests
      4. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  75. Future Capabilities for HEP
  76. Future Capabilities for HEP
      1. Presentation to OHEP, OFES, OASCR: Nov 7, 2006
      2. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  77. Summary
  78. Summary
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  79. Additional Slides
  80. Additional Slides
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  81. Site Visits
  82. Site Visits
  83. (TRECC)
  84. – West Chicago, Illinois
  85. – Hilo, Hawaii
  86. http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=425
  87.  
  88. http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=505
  89. – Baltimore, Maryland
  90. – Livermore, California
  91. http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=532
  92. – San Diego, California
  93. – Oak Ridge, Tennessee
  94. http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=570
  95. – Argonne, Illinois
  96. – Darmstadt, Germany
  97. http://docdb.fnal.gov/CMS-public/DocDB/ShowDocument?docid=622
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  98. LHC Sequencer
  99. LHC Sequencer
  100. Automates the very complex sequence of operations required to operate the LHC.
  101. Typical commands
      1. Set, get, check devices
      2. Wait for conditions
      3. Execute more complex operations
      4. Start regular programs
      5. Start plots
      6. Send data to shot log
  102. Step through commands
      1. Stops on error
      2. Allow restart at failed command
  103. Sequencer is used for:
      1. Normal operations
      2. Studies or special cases
  104. Working with CERN on requirements
      1. Explore existing implementations:
      2. FNAL, LEP, RHIC, NIF, HERA, SMI++
      3. http://cd-amr.fnal.gov/remop/Sequencer.htm
  105. This is a
  106. CERN/Fermilab
  107. collaboration working on the LHC Sequencer.
  108. LHC State Diagram
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  109. SDA is a software system for collecting, storing and analyzing data in terms
  110. of the stages of a complex process.
  111. SDA 1
  112. SDA 2
  113. SDA 2 for LHC
  114. This is a
  115. CERN/Fermilab
  116. collaboration.
  117. Sequenced Data Acquisition (SDA)
  118. Sequenced Data Acquisition (SDA)
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  119. Identity Database (IDDB)
  120. Identity Database (IDDB)
  121. A lightweight user authentication framework.
  122. Motivation
  123. Identity Database
  124. Features
  125. IDDB is being developed at
  126. Fermilab
  127. for an electronic logbook for ILC.
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  128. LHC  
  129. Beam Instrumentation Software
  130. Beam Instrumentation Software
  131. Dedicated applications for LHC beam instrumentation need to be written.
  132.  
  133. application software for the LHC tune measurement system by providing
  134. panels for device configuration/setup and measurement displays:
  135. This is a
  136. CERN/Fermilab
  137. collaboration working on LHC beam instrumentation software.
      1. Shaping Collaboration 2006: Dec. 11 - 13, 2006
  138. Some assumptions (CMS
  139. Some assumptions (CMS
  140. operations)
  141. operations)
  142. For CMS
  143. For both CMS & LHC

Shaping Collaboration 2006: Dec. 11 - 13, 2006
1
  

Back to top


Plans for the US-CMS

Back to top


Remote Operations Center

Back to top


LHC@FNAL

Back to top


Erik Gottschalk

Back to top


Fermilab
LHC at CERN - Geneva, Switzerland
Fermilab
- Batavia, Illinois

Shaping Collaboration 2006: Dec. 11 - 13, 2006
2

Back to top


Overview

Back to top


Overview

Back to top


Remote operations for CMS & LHC

Back to top


What is LHC@FNAL?

Back to top


Planning

Back to top


Status

Back to top


Needs

Back to top


Summary

Back to top


LHC@FNAL website:

Back to top


http:

Back to top


//cd-amr
.
fnal
.

Back to top


gov/remop/remop

Back to top


.html

Shaping Collaboration 2006: Dec. 11 - 13, 2006
3
1.
Build a dedicated remote operations center to

Back to top


support both CMS and
LHC
commissioning and operations.
Remote shifts for CMS
Enable CMS and LHC experts to access information in real time
Participate remotely in studies, commissioning, and operations
Training
 
for CMS & LARP (LHC Accelerator Research Program)
2.
Facilitate communication with CMS and LHC control rooms.
Call center
 
in the US - to help contact experts, answer questions.
T
est collaboration tools to improve communication
3.
Take advantage of a unique opportunity to have detector and accelerator
experts working together to solve problems.
4.
The
principal goal
is to enable people to participate in commissioning &
operations when they are unable to
 
travel (cost, family, visa issues, etc.).

Back to top


Goals for
 

Back to top


Joint CMS & LHC Remote Operations

Shaping Collaboration 2006: Dec. 11 - 13, 2006
4

Back to top


Remote Operations for US-CMS

Back to top


Remote Operations for US-CMS
The remote operations center will serve the US-CMS community.
There are nearly 50 US institutions
in CMS and approximately 600 signing
physicists/engineers/guest scientists in
the US.
The LHC Physics Center (LPC) will provide
a place in the US for physics/analysis
discussions and meetings.
The
 
LHC@FNAL remote operations center
will provide a US hub for operations
activities.
The goal is to provide a facility
 
that will
enable CMS collaborators to take remote
shifts (for example, data-quality monitoring)
C
M
S
 
H
e
a
d
 
C
o
u
n
t
,
 
P
h
.
D
 
P
h
y
s
i
c
i
s
t
s
,
 
4
3
8
 
T
o
t
a
l
Boston Univ., Boston
Brown Univ., Providence
UC Davis, Davis
UCLA, Los Angeles
UC Riverside, Riverside
UC San Diego, La Jolla
UC Santa Barbara, Santa Barbara
California Inst. of Tech., Pasadena
Carnegie Mellon Univ., Pittsburgh
University of Colorado at Boulder, Boulder
Cornell University, Ithaca
Fairfield Univ., Fairfield
Fermi National Accelerator Lab., Batavia
Univ. of Florida, Gainesville
Florida International University, Miami
Florida State Univ., Tallahassee
Florida Inst. of Tech., Melbourne
Univ. of Illinois at Chicago, Chicago
The Univ. of Iowa, Iowa City
Iowa State Univ., Ames
Johns Hopkins Univ., Baltimore
The Univ. Of Kansas, Lawrence
Kansas State Univ., Manhattan
LLNL, Livermore
Univ. of Maryland, College Park
Mayaguez, Puerto Rico
Massachusetts Inst. of Tech., Cambridge
Univ. of Minnesota, Minneapolis
U
Fermilab

Shaping Collaboration 2006: Dec. 11 - 13, 2006
5

Back to top


Remote operations for LHC

Back to top


Remote operations for LHC
CCC
Remote operations center for LHC:
provide
training before going to CERN
support LHC components built in US
 
participate remotely in LHC studies
access monitoring information
 
develop
 
software for LHC
CCC at CERN
LARP:
The US LHC Accelerator Research
Program (LARP) consists of four US
laboratories, BNL, FNAL, LBNL and SLAC, who
collaborate with CERN on the Large Hadron
Collider (LHC).
The LARP program enables U.S. accelerator
specialists to take an active role in the LHC
accelerator during its commissioning and
operations, and to be a major collaborator in
LHC performance upgrades.

Shaping Collaboration 2006: Dec. 11 - 13, 2006
6

Back to top


What is LHC@FNAL?

Back to top


What is LHC@FNAL?
A Place
That provides access to information in a manner that is similar to
what is available in control rooms at CERN
Where members of the LHC community can participate remotely in
LHC and CMS activities
A Communications Conduit
Between CERN and members of the LHC community located in
North America
An Outreach tool
Visitors will be able to see current LHC activities
Visitors will be able to see how future international projects in particle
physics (such as the ILC) can benefit from active participation in
projects at remote locations.

Shaping Collaboration 2006: Dec. 11 - 13, 2006
7

Back to top


LHC@FNAL Location & Layout
LHC@FNAL Location & Layout

Back to top


Back to top


Operations

Back to top


Center

Back to top


(Phase 1)

Back to top


Office Space

Back to top


(Phase 2)

Back to top


Conference
Room

Back to top


(Phase 1)
      
LHC@FNAL is located in
 
Fermilab
s
Wilson Hall (1
st
floor)

Shaping Collaboration 2006: Dec. 11 - 13, 2006
8

Back to top


LHC@FNAL Construction

Back to top


LHC@FNAL Construction
 
 

Back to top


Status

Back to top


Status

Back to top


Construction is almost complete (photo taken Nov. 30, 2006).

Shaping Collaboration 2006: Dec. 11 - 13, 2006
9
We formed a task force with members from all
F
ermilab
 
divisions, university groups,
CMS, LARP, and LHC. The advisory board had an even broader base.
The LHC@FNAL task force developed a plan with input from many sources including
CMS, LHC, CDF, D0, MINOS, MiniBoone and Fusion Energy Sciences (FES).
We worked with CMS and US-CMS management, as well as members of LARP and the
LHC machine group at all steps in the process.
A detailed requirements document for LHC@FNAL was prepared and reviewed in 2005.
We visited 9 sites (e.g. Hubble, NIF, ESOC) to find out how other projects build control
rooms and do remote operations.
We have
 
a Collaboration Agreement between CERN and FNAL to work on LHC software
development.
We are engaged in construction, integration, software development and outreach activities.
The CMS Remote Operations Center (ROC) is already in operation.
The goal is to have LHC@FNAL ready for detector commissioning and startup of beam in
2007.
We plan to work with the ILC controls group to develop plans for ILC remote operations.
We
 
hope to collaborate with
 
the
 
Fusion
community (FES) to develop collaborative tools.
Together we are exploring connections to OSG
 
and other GRID projects.

Back to top


Planning for LHC@FNAL

Back to top


Planning for LHC@FNAL

Shaping Collaboration 2006: Dec. 11 - 13, 2006
10

Back to top


Current Status of LHC@FNAL

Back to top


Current Status of LHC@FNAL
Construction of a joint CMS and LHC remote operations center
(LHC@FNAL) is nearing completion - Spring 2007
LHC@FNAL Software (LAFS) development effort for LHC
accelerator software has been successfully launched. This
is a collaboration between CERN and
Fermilab
.
Software development for LHC, CMS, ILC:
1.
Role Based Access for LHC (RBA)
2.
LHC Sequencer
3.
Sequenced Data Acquisition (SDA)
4.
Screen Snapshot Service (SSS)
5.
Identity Database (IDDB)
6.
LHC Beam Instrumentation Software
7.
Electronic Logbook for ILC

Shaping Collaboration 2006: Dec. 11 - 13, 2006
11

Back to top


An approach to restrict system access to authorized users
.

Back to top


What is a
ROLE
?
A role is a job function within an organization.
Examples: LHC Operator, SPS Operator, RF Expert, PC Expert, Developer,
A role is a set of access permissions for a device class/property group
Roles are defined by the security policy
A user may assume several roles

Back to top


What is being
 
ACCESSED
?
Physical devices (power converters, collimators, quadrupoles, etc.)
Logical devices (emittance, state variable)

Back to top


What type of
 
ACCESS
?
Read: the value of a device once
Monitor: the device continuously
Write/set: the value of a device

Back to top


Requirements have been written
Authentication
Authorization

Back to top


Status:
 

Back to top


Code development in progress

Back to top


This is a

Back to top


CERN/Fermilab

Back to top


collaboration working on RBA for the LHC control system.

Back to top


Role Based Access (RBA)
Role Based Access (RBA)

Back to top


Back to top


The software infrastructure for RBA is

Back to top


crucial
for

Back to top


remote operations. Permissions can be setup to

Back to top


allow experts outside the control room to

Back to top


read or

Back to top


monitor a device safely
.

Shaping Collaboration 2006: Dec. 11 - 13, 2006
12

Back to top


An approach to provide a snapshot of a graphical interface to remote users.

Back to top


What is a snapshot?
An image copy of a graphical user interface at a particular instance in time.
Examples: DAQ system buffer display, operator control program,
A view-only image, so there is no danger of accidental user input.
Initially envisioned for application GUIs but could be expanded to desktops.

Back to top


What is the role of the service
?
Receives and tracks the snapshots from the monitored applications.
Caches the snapshots for short periods of time.
Serves the snapshots to requesting applications/users.
Prevents access from unauthorized applications/users.
Acts as a gateway to private network applications for public network users.

Back to top


How will this work?
Applications capture and send snapshots to the service provider in the background.
Users would access snapshots using a web browser.

Back to top


Status:
The capturing of snapshots from Java applications has been demonstrated.
The transfer of snapshots
 
is
 
being investigated.

Back to top


SSS is being developed at

Back to top


Fermilab

Back to top


for CMS, and
 

Back to top


may be applicable to the LHC.

Back to top


Screen Snapshot Service (SSS)

Back to top


Screen Snapshot Service (SSS)
Monitored
Application(s)
Snapshot
Service
Web
Browser(s)
snapshots
snapshots
requests

Shaping Collaboration 2006: Dec. 11 - 13, 2006
13

Back to top


Future Capabilities for HEP

Back to top


Future Capabilities for HEP
Although we are making good progress on the development of remote operations
capabilities for high-energy physics (HEP), there is
room for improvement
.
 
Better
collaborative tools
 
will contribute significantly to our ability to participate in LHC,
and plan for
 
the International Linear
Collider
(ILC).
We can benefit from improved
communications tools
by
exploiting convergence of
 
telecom and internet technologies (e.g. SIP),
deploying integrated communications (voice, video, messaging, email, data)
and advanced directory services for identification, location and scheduling.
We can benefit from a
 
true
collaborative control room
by
 
deploying distributed, shared
 
display walls for remote collaborative visualization.
We can benefit from security enhancements (role-aware & easier-to-use security).
Some of these needs are already being addressed by Fusion (FES) community.

Presentation to OHEP, OFES, OASCR: Nov 7, 2006
14
Approaches to OASCR
Fusion Energy Sciences
High Energy Physics
New
FusionGrid
  
Computational
  
Services
MDSplus
Collaborative Displays
Federated Security
Role Based Access
Sequenced Data Acquisition (SDA)
SIP Communication Tools
LHC Sequencer
LHC Beam
Instrumentation
Identity Database (IDDB)
Electronic
Logbook
Screen Snapshot Service (SSS)
FusionGrid
Parallel
  
Computational
  
Services
   
Substantial Overlap Between FES and HEP Needs

Shaping Collaboration 2006: Dec. 11 - 13, 2006
15

Back to top


Summary

Back to top


Summary
 
The goals of LHC@FNAL are to support both CMS and LHC
commissioning and operations, and to take advantage of an
opportunity to have detector and accelerator experts work together.
The LHC@FNAL remote operations center is under construction,
and will be completed by
 
Spring 2007.
A collaborative effort between CERN and
Fermilab
to develop LHC
accelerator software has been successfully launched.
There is an urgent need for better collaborative tools to improve our
ability to work on the LHC.
There is substantial overlap between the needs for High Energy
Physics (HEP) and Fusion Energy Sciences (FES) for collaborative
tools.

Shaping Collaboration 2006: Dec. 11 - 13, 2006
16

Back to top


Additional Slides

Back to top


Additional Slides

Shaping Collaboration 2006: Dec. 11 - 13, 2006
17

Back to top


Site Visits

Back to top


Site Visits
Technology Research, Education, and Commercialization Center

Back to top


(TRECC)

Back to top


West Chicago, Illinois
(Aug. 25, 2005)
Gemini Project remote control room

Back to top


Hilo, Hawaii
(Sept. 20, 2005)

Back to top


http://docdb.fnal.gov/C