Skip to Content.
Sympa Menu

usatlas-hllhc-l2deputymgmt-nsf-l - [[Usatlas-hllhc-l2deputymgmt-nsf-l] ] Preliminary contingency numbers

usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov

Subject: U.S. ATLAS HL-LHC Upgrade Level 2 and Deputies-NSF only Management Mailing List

List archive

Chronological Thread  
  • From: Gustaaf Brooijmans <gusbroo AT nevis.columbia.edu>
  • To: usatlas-hllhc-l2deputymgmt-nsf-l AT lists.bnl.gov
  • Subject: [[Usatlas-hllhc-l2deputymgmt-nsf-l] ] Preliminary contingency numbers
  • Date: Sat, 21 Jun 2025 14:09:48 -0400


Hello all,

Please see attached. We are still running some checks, but at this stage
it’s also good if you all take a look. There are some features:

-Tile 90% CL schedule contingency is > available float, but available float
is calculated from the end of LVPS production to the start of installation.
If we take something more reasonable, eg completion of batch 1 production,
the available float jumps to ~220 days. (see “working summary” tab)

-I’m not sure what we should take for trigger. Both global and EF Tracking
have comfortable float, but L0Calo does not. It has 0 in the sheets, but
there are a couple of wait tasks that add up to 178 days. L0Calo is more
crucial to the start of commissioning I would think, so maybe we should use
that?

Cost books and schedules have been posted on the review website.

Best,

Gustaaf

Attachment: 2025-07-nsf-ipr-details_v3a.xlsx
Description: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet



  • [[Usatlas-hllhc-l2deputymgmt-nsf-l] ] Preliminary contingency numbers, Gustaaf Brooijmans, 06/21/2025

Archive powered by MHonArc 2.6.24.

Top of Page